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? -- Ludovic Brenta. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
