reopen 656997
thanks

I found that when I upgraded to 1.7.3-6 the conffiles were not removed:

(Reading database ... 165610 files and directories currently installed.)
Preparing to replace libogre-1.7.3 1.7.3-5sam1 (using 
libogre-1.7.3_1.7.3-6sam1_amd64.deb) ...
Unpacking replacement libogre-1.7.3 ...
dpkg: warning: unable to delete old directory '/etc/OGRE-1.7.3': Directory not 
empty
Preparing to replace libogre-dev 1.7.3-5sam1 (using 
libogre-dev_1.7.3-6sam1_amd64.deb) ...
Unpacking replacement libogre-dev ...
Preparing to replace ogre-tools 1.7.3-5sam1 (using 
ogre-tools_1.7.3-6sam1_amd64.deb) ...
Unpacking replacement ogre-tools ...
Setting up libogre-1.7.3 (1.7.3-6sam1) ...
Processing triggers for man-db ...
Setting up libogre-dev (1.7.3-6sam1) ...
Setting up ogre-tools (1.7.3-6sam1) ...

Though it's not mentioned in the above messages, /etc/OGRE/plugins.cfg
also still exists.

I think this is because dpkg-maintscript-helper rm_conffile is only
called in libogre-1.7.3.preinst; the man page says it should be called
in the preinst, the postinst and the postrm scripts.

This may be complicated by the local version number's I've added to the
package in order to rebuild it against Boost 1.48. I'm not going to
remove the files in /etc for now in case you want me to test the upgrade
process.

BTW, I noticed that debian/libogre-dev.README.Debian advises users to
specify /etc/OGRE/plugins.cfg when they create their Ogre::Root
instance. I think this file should be removed, or have its contents
replaced with a warning that users should decide which plugins they use
when they build their software, and ship their own plugins.cfg or just
load their chosen plugins manually after creating their Root.

Regards,

-- 
Sam Morris <s...@robots.org.uk>




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to