[Monotone-devel] Re: Bug#384565: monotone - FTBFS: Build killed with signal 15

[Shaun Jackman]

On 9/26/06, Ludovic Brenta <address@hidden> wrote:
> The bug still happens with 0.30.  I was browsing the monotone-devel
> archives and something went *tick* in my head:
>
> Shaun Jackman wrote:
> > The monotone-0.30.tar.gz tarball shipped with package_revision.txt set
> > to `unknown'. Should this be fixed?
>
> Thomas Moschny wrote:
> > [it is likely to affect 0.30 users] only in such a way that
> > 'mtn --full-version' says something like "base revision: unknown",
> > and only if they use a binary built from the official tarfile. Other
> > than that purely cosmetic issue it should not cause any problems.
> >
> > However, if you used to do something like 'cat _MTN/revision' in *your
> > own* project, you should change that to 'mtn automate get_revision_id'.
>
> Nathaniel Smith wrote:
> > 'mtn automate get_base_revision_id'
>
> The build failure occurs when you try to call 'mtn automate get_revision'.
> Could you try to change that to get_base_revision_id, and see if it
> improves things?

Both commands exist in fact. get_revision is used to generate
package_full_revision.txt, and get_base_revision_id is used to
generate package_revision.txt. Both of these commands require a
monotone workspace though, and the tarball does not ship with one.
monotone should give an error:

monotone-0.30$ mtn automate get_revision
mtn: misuse: workspace required but not found
monotone-0.30$ mtn automate get_base_revision_id
mtn: misuse: workspace required but not found

I suspect the resulting monotone binary should not be run at all
during the build. Perhaps if I add all the missing .txt files, the
build would succeed again. Although, that doesn't explain why the
current build fails.

Cheers,
Shaun