On Fri, Dec 02, 2005 at 01:23:34PM -0500, Nathanael Nerode wrote: > >> And the following library packages haven't built in c2 versions on > >> all architectures, and therefore prevent other packages from > >> transitioning: > >> pdfkit.framework -- m68k (blocks viewpdf.app, gworkspace.app) > >m68k should just be ignored for these purposes; the arch is doing much > >better than in past months, but it's still not quite keeping up to the point > >that we're checking installability counts there. > Yes, but... > I didn't think it was a good idea to reupload the packages > depending on that library, or to queue them for rebuilding on m68k, > since they'd end up linked to the old version of libstdc++ on m68k. > Until the transitioned library built. > Am I right about that? Not in the case of architectures that aren't keeping up. It doesn't make sense to postpone such transitions indefinitely due to one architecture lagging behind, and it already *feels* like "indefinitely" as it stands now. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature