* Gaudenz Steinlin <[EMAIL PROTECTED]> [2008-02-09 21:01]:
> I tried to fix this today, but quickly discovered that #456971 on
> libsigc++-2.0-dev is blocking this further down the path. As I currently
> don't have the time to fix libsigc++-2.0-dev as well I just subscribed
> to #456971 and added a block. I will look into this again as soon as
> #456971 is fixed.
> 
> What are the current NMU rules for this issue? Would an NMU for #456971
> be acceptable atm?

I'm not sure there's a solution for #456971 yet, although I heard
rumours the problem is fixed in a newer upstream release.

Daniel, did you have any chance to look into this issue?  This is
getting really important because many packages fail to compile with
gcc 4.3 because of this.

-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to