unmerge 499096 592331 severity 499096 normal reassign 592331 binutils forcemerge 592332 592331 thanks
On Mon, Aug 09, 2010 at 01:33:25PM +0300, Török Edwin wrote: > severity 499096 grave > merge 499096 592331 > thanks > > Looks like my report is similar to #499096, attempting to merge them. While both are a result of a corrupt /var/lib/dpkg/diversions, the root cause is probably different as the file wasn't empty in the older report. I think they should be handled separately, so unmerging. > Looking at /var/lib/dpkg/diversions I see that it is empty. > Is that normal ?! Or did some buggy package maintainer script wipe it? This definitely isn't normal, and it is not a bug in perl-doc (or libmodule-corelist-perl or binutils for that matter) that its installation fails if /var/lib/dpkg/diversions is corrupt. I see you also filed #592332, currently assigned to binutils, which contains more discussion about this. I'm merging them instead. However, I can't see how the binutils experimental packages could have caused this. I suppose it's most likely a filesystem issue, but we can't really know for sure. I've glared at the dpkg logs you sent but they don't help much. Anyway, as you've been running upstream release candidate kernels and packages from experimental, I don't really think this should be treated as a release critical bug. I suggest closing it as unreproducible but will leave that to you or the binutils maintainers. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
