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 failed to rebuild on ia64, for what looks like the same > binutils bug. Should have already been queued for rebuild against the new libtagcoll-dev... dunno why it wasn't, but done now. > debtags-edit has picked up a different set of dependencies on ia64 from > everywhere else; it appears to be having a recursive dependency disease > problem, but worse on ia64 (presumably because ia64 was rebuilt more recently > than the others). This is rendering it uninstallable on ia64 > with the hint. It only needs an updated version of gtk+2.0 in testing, which should be set to happen soon. (339419 looks like an overinflated severity, and is the only blocker AFAICS.) > dfsbuild becomes uninstallable on some arches solely because > apt-move becomes uninstallable on those arches. > apt-move becomes uninstallable solely because it just had a new upload. > force apt-move/4.2.24-1.1 ... or remove apt-move/4.2.24-1 dfsbuild/0.6.21. > I'm not quite sure what to do about buffy/tagcolledit/debtags-edit, with > the ia64 breakage; I don't know how to write removal or force hints for > this situation with binNMUs floating around. Perhaps you should just go > ahead and force-hint the thing, and let them catch up on ia64 later. All existing britney hints are source-only. That actually means we'll be in for some fun if we ever break multiple packages on an arch that can't be updated serially. Not an issue in this case. More of an issue if we decide not to wait for hppa to catch up with KDE. -- 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