[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-21 Thread Senthil Kumaran
Senthil Kumaran orsent...@gmail.com added the comment: How about the patch attached in the issue11579 -- nosy: +orsenthil ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11421 ___

[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-21 Thread Martin v . Löwis
Martin v. Löwis mar...@v.loewis.de added the comment: I was worried that the fatal error might not trigger anymore when doing something odd with subversion, but I guess this is unfounded worry. So I'm fine with the patch. -- ___ Python tracker

[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-21 Thread STINNER Victor
STINNER Victor victor.stin...@haypocalc.com added the comment: f9763c363cc3 didn't close this issue whereas its message contains Closes #11579. Closes #11421.. This commit closed #11579. -- nosy: +haypo ___ Python tracker rep...@bugs.python.org

[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-21 Thread Martin v . Löwis
Changes by Martin v. Löwis mar...@v.loewis.de: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11421 ___

[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-20 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: What’s the proper way to fix this? Mention in the devguide that 2.5 and 2.6 can’t be built from Mercurial, or commit some text in the place of the keywords in Mercurial? -- nosy: +eric.araujo versions: +Python 2.6 -Python 2.5

[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-20 Thread Martin v . Löwis
Martin v. Löwis mar...@v.loewis.de added the comment: If someone can propose a patch that has zero effect on a subversion checkout or export but fixes the issue with a hg checkout, I'd be fine adding it. OTOH, I fail to see why this issue needs fixing. --

[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-19 Thread Skip Montanaro
Changes by Skip Montanaro s...@pobox.com: -- nosy: -skip.montanaro ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11421 ___ ___ Python-bugs-list

[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-07 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11421 ___

[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-06 Thread Skip Montanaro
New submission from Skip Montanaro s...@pobox.com: Trying to build Python 2.5 from a fresh Mercurial checkout I get the following error trying to build modules using setup.py build: % nice make case $MAKEFLAGS in \ *-s*) CC='gcc' LDSHARED='gcc -L/opt/local/lib -bundle -undefined

[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-06 Thread Martin v . Löwis
Martin v. Löwis mar...@v.loewis.de added the comment: -1. Changing the Mercurial tree will make it more difficult to maintain the subversion tree, which will be the tree from which future 2.5 releases will be made. So if anything is done with this issue, please defer that after September

[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-06 Thread Skip Montanaro
Skip Montanaro s...@pobox.com added the comment: Can you explain how I'm supposed to build Python 2.5 from a Mercurial checkout? What is magic about Sept 2011? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11421

[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-06 Thread Martin v . Löwis
Martin v. Löwis mar...@v.loewis.de added the comment: Can you explain how I'm supposed to build Python 2.5 from a Mercurial checkout? No, I can't. Just don't. Use subversion instead if you want to build Python 2.5 (or use one of the released versions). What is magic about Sept 2011?

[issue11421] Subversion keywords missing on 2.5 checkout

2011-03-06 Thread Skip Montanaro
Skip Montanaro s...@pobox.com added the comment: The workaround turned out to be simple. I just expanded the $HeadURL$ subversion keyword as svn would have done it and committed the change locally. -- ___ Python tracker rep...@bugs.python.org