FTBFS: gcc errors; needs sync (+libs)

Bug #151646 reported by Daniel Hahler
6
Affects Status Importance Assigned to Milestone
bayonne (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: bayonne

bayonne (1.2.16-6build2) fails to build from source in Gutsy (see http://people.debian.org/~lucas/logs/2007/08/28/bayonne_1.2.16-6build2_gutsy32.buildlog).

It should probably get synced from Debian unstable, but the build dependencies are not satisfied in Gutsy (libexosip2-dev (>= 3.0.3-2-1)).
Trying to build libexosip2 from unstable, it fails because of libosip2-dev (>= 3.0.3-2-1), but Gutsy has 2.2.2-3.1.

So, libosip2 and libexosip2-4 would also have to get synced from unstable.

I've logged into a pbuilder tar.gz and prepared it by manually building and installing these libs from unstable (using "sudo pbuilder login --save-after-login").

Then, bayonne from unstable builds fine.

bayonne, libosip2 and libexosip2-4 are all supposed to be in "main".

Revision history for this message
Daniel Hahler (blueyed) wrote :
Revision history for this message
Michael Bienia (geser) wrote :

IMHO it's too late to fix this for gutsy. As you found out you need at least three UVF exceptions for it. I looked at it already some weeks ago and came also to this conclusion. I stopped looking at it when I got to libosip2-dev and saw that others packages also depend on it and need to be checked if they still build and work with the new libosip2 version or also need updating.
After discussing the situation on #ubuntu-motu with Sarah Hobbs, I decided that updating bayonne (and the libs) was to much work.

Changed in bayonne:
status: New → Confirmed
Revision history for this message
Luca Falavigna (dktrkranz) wrote :

bayonne builds fine in Hardy.

Changed in bayonne:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.