Ping! ... It was 2 years ago that I posted this bugreport, including: - detailed description of what to do for the bug to occur, - detailed explanation where and why the source is buggy, - patch to fix the problem.
Just a note I haven't mentioned before: this patch has already survived 2 years of intensive testing, since we're using dpkg with this patch to build up and upgrade chroot systems where all the packages of a Linux distribution are being built, and the packages that form these chroot jails are continuously updated to newer or fixed versions. My estimate is that we've upgraded the chroot using dpkg with this patch approximately 50.000 times in these 2 years -- successfully, as opposed to the times when we used an unpatched dpkg and had serious OOM troubles when upgrading e.g. kernel-headers inside the chroot after a kernel version bump. During these 2 years no valuable comments arrived from any Debian/Dpkg developers. I wonder why... Isn't there anyone caring about this bug? (Is there anyone caring about Dpkg at all?) Or you simply lack developer resources? (Well, that could be an excuse for an unreproducible bug report or a bug report without a patch, but I feel I've done everything anyone could have done to locate and fix this bug; all you have to do is verify it and then apply the patch.) Or what else is happening behind the scenes? If you check the bug archives of Debian, you'll see that I already posted several bug reports and patches (well, not very much, maybe a dozen) and some of them were successfully applied, making Debian a slightly better distro. Unfortunately this is not my first bugreport where I have to wait years for anyone to move his fingers. If you continue developing with this approach, all you'll reach is that I'm going to fix these bugs for myself and not send any feedback at all. It's not worth it for me to spend my time explaining the story if noone's listening to me. Is this what you want? I hope not... -- Egmont -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
