On Tue, 01 Jun 2010, Ryan Niebur wrote: > Preparing to replace midori 0.2.2-1 (using midori_0.2.6-1_i386.deb) ... > Moving obsolete conffile /etc/midori/extensions/libadblock.so/config out of > the way... > Unpacking replacement midori ... > dpkg: warning: unable to delete old directory > '/etc/midori/extensions/libadblock.so': Directory not empty > dpkg: warning: unable to delete old directory '/etc/midori/extensions': > Directory not empty > dpkg: warning: unable to delete old directory '/etc/midori': Directory not > empty > Setting up midori (0.2.6-1) ... > Removing obsolete conffile /etc/midori/extensions/libadblock.so/config ... > > This gives a lot of output and leaves the > /etc/midori/extensions/libadblock.so directory for no reason. > > Is there any nice (using dpkg-maintscript-helper) way to solve this > problem?
It would require storing the backup conffile somewhere else which I don't think is a good idea. dpkg -S /etc/midori/extensions/libadblock.so should still return midori and the directory should also be listed in dpkg -L midori. The directory would be removed on purge but it can't be removed at upgrade time since it's not empty. But you can add the appropriate command in the postinst if this matters to you (after the dpkg-maintscript-helper call). Cheers, -- Raphaël Hertzog Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/ My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
