Is a fix for Bug 87077 a blocker for accepting an upgrade to a package
that has been upgraded previously in Ubuntu despite this problem, and
has been upgraded by Debian without worrying about this problem? I
suggest not.
Also of course, only XMMS2 has ever reported this as an issue and then
they
Breaking news update: It seems that there may be an acceptable quick
fix that obviates the problem of Bug 87077 (that will be replaced later
when the proper solution is in place). The merge has been proposed for
SCons 1.0.1 which is due out in a few days.
--
SCons package not up to date in
Russel, that bug affected all or at least a high proportion of SCons
using packages - it just happened that xmms was the first one to see it.
It's been updated in Ubuntu because Ubuntu has a workaround in place
which stops the affected code being run.
--
SCons package not up to date in Intrepid
Greg has committed the acceptable quick fix and it is just now awaiting
approval to be part of the 1.0.1 release due out in the next few days.
This should then make everyone happy :-)
My original point was that Ubuntu had been tracking SCons releases
previously so there seems no barrier to moving
I'd like to see if bug #87077 has been fixed in our buildd in a sane way
before proceeding. Change introduced there could be merged as well, but
have this package in sync with Debian again is fine.
** Changed in: scons (Ubuntu)
Importance: Undecided = Wishlist
Assignee: (unassigned) =
