We're now up to 66 cherry-picks. 75%+ of those are asyncio changes. Hopefully I won't have to redo the cherry-picking from scratch again, I can just pile more picks on top of the ones I've got. As before you'll find the results here: http://midwinter.com/~larry/3.4.status/ //arry/
In article <53070A8A.8080101@hastings.org>, Larry Hastings <larry@hastings.org> wrote:
As before you'll find the results here:
Status says that: eef7899ea7ab Doc: do not rely on checked-out Sphinx toolchain from svn.python.org anymore is unmerged, which is what Georg and I agreed upon in Issue20661. Yet, in the current python.3.4.2014.02.21.00.07.42.tgz tarball, that change appears to be present and, as such, causes installer builds to fail. -- Ned Deily, nad@acm.org
On 02/21/2014 01:30 AM, Ned Deily wrote:
In article <53070A8A.8080101@hastings.org>, Larry Hastings <larry@hastings.org> wrote:
As before you'll find the results here:
http://midwinter.com/~larry/3.4.status/ Status says that:
eef7899ea7ab Doc: do not rely on checked-out Sphinx toolchain from svn.python.org anymore
is unmerged, which is what Georg and I agreed upon in Issue20661. Yet, in the current python.3.4.2014.02.21.00.07.42.tgz tarball, that change appears to be present and, as such, causes installer builds to fail.
Whoopsie! My local branch is actually correct. But! I effectively did this in my automation: % hg clone 3.4 python-{time} % cd python-{time} % rm -rf .hg* .bzr* .git* % cd .. % tar cvfz python-{time}.tgz python-{time} Can you spot the error? That's right: when you clone, the clone always starts out in "default". So all the tarballs I've published so far have been wrong. ARGH. Sorry! I've added a "hg branch 3.4" in a judicious spot in my automation. The resulting tarball doesn't have the sphinx toolchain change. Look for a new tarball in a few minutes, once "make test" finishes, //arry/
2014-02-21 11:06 Larry Hastings napisał(a):
On 02/21/2014 01:30 AM, Ned Deily wrote:
In article <53070A8A.8080101@hastings.org>, Larry Hastings <larry@hastings.org> wrote:
As before you'll find the results here:
http://midwinter.com/~larry/3.4.status/ Status says that:
eef7899ea7ab Doc: do not rely on checked-out Sphinx toolchain from svn.python.org anymore
is unmerged, which is what Georg and I agreed upon in Issue20661. Yet, in the current python.3.4.2014.02.21.00.07.42.tgz tarball, that change appears to be present and, as such, causes installer builds to fail.
Whoopsie! My local branch is actually correct. But! I effectively did this in my automation:
% hg clone 3.4 python-{time} % cd python-{time} % rm -rf .hg* .bzr* .git* % cd .. % tar cvfz python-{time}.tgz python-{time}
Can you spot the error? That's right: when you clone, the clone always starts out in "default". So all the tarballs I've published so far have been wrong. ARGH. Sorry!
I've added a "hg branch 3.4" in a judicious spot in my automation.
You can use 'hg clone -u 3.4 3.4 python-{time}'. $ hg clone --help ... To check out a particular version, use -u/--update, or -U/--noupdate to create a clone with no working directory. ... -u --updaterev REV revision, tag or branch to check out -- Arfrever Frehtes Taifersar Arahesis
On Fri, 21 Feb 2014 02:06:07 -0800 Larry Hastings <larry@hastings.org> wrote:
Whoopsie! My local branch is actually correct. But! I effectively did this in my automation:
% hg clone 3.4 python-{time} % cd python-{time} % rm -rf .hg* .bzr* .git* % cd .. % tar cvfz python-{time}.tgz python-{time}
You could use "hg archive". Regards Antoine.
In article <5307250F.3040109@hastings.org>, Larry Hastings <larry@hastings.org> wrote:
Whoopsie! My local branch is actually correct. But! I effectively did this in my automation:
% hg clone 3.4 python-{time} % cd python-{time} % rm -rf .hg* .bzr* .git* % cd .. % tar cvfz python-{time}.tgz python-{time}
Can you spot the error? That's right: when you clone, the clone always starts out in "default". So all the tarballs I've published so far have been wrong. ARGH. Sorry!
I've added a "hg branch 3.4" in a judicious spot in my automation. The resulting tarball doesn't have the sphinx toolchain change.
Look for a new tarball in a few minutes, once "make test" finishes,
Much better - thanks! -- Ned Deily, nad@acm.org
participants (4)
-
Antoine Pitrou -
Arfrever Frehtes Taifersar Arahesis -
Larry Hastings -
Ned Deily