Build fails against bzr 2.5 stable, rebuild or new upstream requested
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bzr-git (Debian) |
Fix Released
|
Undecided
|
Unassigned | ||
bzr-git (Ubuntu) |
Fix Released
|
Undecided
|
Jelmer Vernooij | ||
bzr-svn (Debian) |
Invalid
|
Undecided
|
Unassigned | ||
bzr-svn (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
You may mark this invalid for what I'm about to say, don't.
A couple of days ago, bzr 2.5 went stable. So because I maintain a repo for bzr Oneiric builds. I decided it was time to backport bzr-git, bzr-svn, and bzrtools from the Precise/Debian repos for the 2.5 release. bzrtools built successfully, bzr-git and bzr-svn weren't so lucky.
So looking at the build logs, I thought all it needed was python-testtools. bzr-svn (I believe) got a little further in the build (but still failed). It needed a file, after I used Google to see what package(s) needed, I uploaded, let it build, and rebuild bzr-svn. Failed again. Again, I'm building for/against Oneiric.
Decided to move bzr-git & bzr-svn to my stage PPA and build against Precise, just in case. I was shocked to find out that bzr-git & bzr-svn both failed to build against bzr 2.5.0 & Precise. The bzr-git & bzr-svn packages currently in Precise were built against bzr 2.5.0 beta 5.
I am requesting a rebuild of bzr-git & bzr-svn against bzr 2.5.0 stable or a new upstream release that fixed the build problems with bzr 2.5.0.
Attached are the partial build logs for my bzr-git & bzr-svn Precise builds
Please file a separate bug for the bzr-svn issue, these are two different issues.