On Tue, 2010-08-10 at 09:23 -0700, Steve Langasek wrote: > This is a bug in gcj, not in db4.8. It appears to now affect *all* > architectures, it just only manifested on sparc and mips because db4.8 was > later to build there and got caught by the introduction of this bug.
Specifically, this does appear to be another instance of the general problem from #580148. gcc-4.4-base 4.4.4-7 ships /usr/lib/gcc/x86_64-linux-gnu/4.4.4/, 4.4.4-8 ships /usr/lib/gcc/x86_64-linux-gnu/4.4.5/ and the new gcj-4.4-base packages have symlinks pointing to the latter. gcc-4.4-base is already installed in the chroots and often won't be the latest version unless something has forced an upgrade, whereas gcj will be installed each time if the buildd is using lvm snapshot chroots; the end result is that the symlinks end up dangling. afaics, gcj-4.4-jdk's dependency on gcc-4.4 needs to be bumped to >= 4.4.4-8. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
