Am 29.10.2013 10:02, schrieb Matthias Andree: > Am 29.10.2013 09:59, schrieb Matthias Andree: >> Am 24.10.2013 18:18, schrieb Michael Elkins: >>> On Thu, Oct 24, 2013 at 10:42:52AM +0100, Andras Salamon wrote: >>>> Which autoconf/automake versions are expected? I am using fairly >>>> recent versions due to other projects needing them, and would like >>>> to know which older versions to custom install. The build system >>>> gives me a bunch of errors when running >>>> autoreconf --install --include=m4 >>>> which seem potentially related to changed semantics. >>>> >>>> Also, the file VERSION contains 1.5.14; is this still used for >>>> anything? >>> >>> Make sure you have moved to the "default" branch of the repository: hg >>> update -C default >>> >>> You shouldn't need to install older versions of the auto* tools. The >>> goal is to make them work with the most recent versions, while not using >>> features that make older systems which are still supported break (e.g. >>> RHEL/CentOS 5). If you find that the build breaks with newer auto* >>> tools, please file a bug report. >> >> Michael, I also get VERSION 1.5.14 on default. >> It lists 1.5.22 on stable. >> > > ...and it turns out that an explicit "hg pull -b default" fixed this for > now, but I am not sure if there is some other old state (from when the > default branch was HEAD) that prevents this from working in the future > (I am more familiar with git these days). >
...Might this be the problem: $ hg paths default = http://dev.mutt.org/hg/mutt#HEAD If so, would then .hg/hgrc in my checkout have to be modified to remove the #HEAD, and possibly add #stable, or leave it out altogether?
