why/does bigloo/skribe needs hinting into testing ?

Hi release team, For some reason bigloo and skribe have not yet migrated into testing. The only reason seems to be their quasi-circular build-dependency relationship, so maybe they need hinting. OTOH, shouldn't katie/whoever see them as a single migratable set anyway ? Best regards, -- Yann

Please remove ksetisaver from testing (RoM)

Recent changes to [EMAIL PROTECTED] render ksetisaver unusable until some serious work is done to convert it to BOINC. Please remove it from testing. The same is true for the setiathome package. I'm not the maintainer of that, but I suggest that it be removed from testing since it's currently

Re: Please remove ksetisaver from testing (RoM)

On Tue, Dec 20, 2005 at 06:51:22PM -0500, Nathanael Nerode wrote: Recent changes to [EMAIL PROTECTED] render ksetisaver unusable until some serious work is done to convert it to BOINC. Please remove it from testing. The same is true for the setiathome package. I'm not the maintainer of

Status of GNOME c2 hint

GNOME c2a hint status: buffy didn't rebuild on ia64, for what looks like a binutils bug. (No reverse depends.) tagcolledit failed to rebuild on ia64, for what looks like the same binutils bug. (No reverse depends.) debtags-edit has picked up a different set of dependencies on ia64 from

kdegraphics

New version, 4:3.4.3-4 So the hint needs to be updated in order to give output. :-( -- Nathanael Nerode [EMAIL PROTECTED] A thousand reasons. http://www.thousandreasons.org/ Lies, theft, war, kidnapping, torture, rape, murder... Get me out of this fascist nightmare! -- To UNSUBSCRIBE, email

Re: Status of GNOME c2 hint

On Tue, Dec 20, 2005 at 08:51:25PM -0500, Nathanael Nerode wrote: GNOME c2a hint status: buffy didn't rebuild on ia64, for what looks like a binutils bug. (No reverse depends.) Yes, a binutils bug that required a rebuild of libbuffy; buffy is in dep-wait on the new libbuffy-dev. tagcolledit