On Thu, Dec 09, 2010 at 11:12:05AM +0100, Cesare Leonardi wrote: > > I just upgraded to the latest lenny perdition package. The upgrade resulted > > in > > the /etc/perdition/popmap.*.db files being removed and not regenerated. > > I confirm this too. > Today i upgraded from 1.17.1-2 to 1.17.1-2+lenny2 and after a reboot for > a kernel upgrade, some user started complaining about authentication > errors. So i observed what Tim reported.
Hi Cesare, Hi Tim, I am a bit confused as to if this is a new problem or not. I initially thought that Tim's idea that this was a result of the change made to resolve #595207 was correct, but now I'm not so sure. The change made for #595207 was to remove the portion of the postrm script that removes the .db files. So its expected (though entirely undesirable) that 1.17.1-2 removes them, while 1.17.1-2+lenny2 should not. However, I don't think that installing (or upgrading) perdition has ever created the .db files. So I'm unsure why this problem hasn't been observed. As for a fix, I wonder if it is appropriate to have perdition run make to create the .db files in its postinst. And having an dependency on make accordingly. Moving forwards this shouldn't be necessary, as the db files aren't removed by postrm any more. But there is no telling what version a user might be upgrading from. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
