On Sun, Nov 19, 2006 at 12:45:46PM -0800, Thomas Bushnell BSG wrote: > On Sun, 2006-11-19 at 05:38 -0800, Steve Langasek wrote: > > On Thu, Nov 16, 2006 at 07:05:01PM -0800, Thomas Bushnell BSG wrote: > > > Currently lilypond 2.8.7 is in unstable. It is blocked waiting for its > > > own timelimit and for guile-1.8 to finish building on other archs and > > > migrate itself.
> > Well, it's waiting for more than just guile-1.8 to "finish building", there > > are guile-1.8 build failures on all the 64-bit architectures that need to be > > resolved before lilypond can be built against it, which means lilypond will > > be out-of-date on these archs until this bug in guile-1.8 is resolved. > > This seems to have been filed as bug #396119. > Yeah, but this is what confuses me. Bug #396119 is not release > critical, because support for those archs is not RC, right? Right. > So I'm confused about why this should delay lilypond 2.8.7? Because lilypond 2.8.7 build-depends on guile-1.8, and lilypond *was* previously built on these architectures where guile-1.8 is unavailable. That still doesn't make 396119 release-critical. It does make it a bug that has to be resolved for lilypond 2.8.7 to be released, AFAICS. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
