Colin Watson wrote: > (If joeyh's idea flies, that would be great ... let it have a file that > lists all the postrms it should be removing in 'PACKAGE MIN-VERSION > MAX-VERSION' format or something.) So what I need to make this fly is mostly to be informed by maintainers when they goof up a postrm purge. After I've collected enough existing brokennesses I can work out how to best structure the package and then add in new ones as they show up on the lists and bts. I've started with man-db's old broken postrm, and will take others in provate email. For now some shell code to fix the problem and a text explination is probably best. -- see shy jo
Attachment:
pgpqLz7yBb1zZ.pgp
Description: PGP signature