On Tue, 2012-02-07 at 15:07 +0000, Manuel A. Fernandez Montecelo wrote: > 2012/2/7 Sam Morris <s...@robots.org.uk>: > > The version check is just there so that the code for removing/renaming a > > conffile is only run once. > > So I still don't understand it very well how it works. > > I uninstall all libogre-*, then remove /etc/OGRE*, as if nothing was > ever installed. Then I install -3, and: > ------------------------------ > # find /etc/OGRE* -type f; echo; tail -n 100 /etc/OGRE*/* > /etc/OGRE/plugins.cfg > > # /etc/OGRE/plugins.cfg - ogre plugins installed on Debian systems > # > # Warning: this file is autogenerated but anything between this line and > # the line saying "-*- ogre-plugins -*-" will be copied as-is on updates. > > PluginFolder=/usr/lib/OGRE > > # default plugins installed with the libogremain package. > Plugin=Plugin_BSPSceneManager.so > Plugin=Plugin_OctreeSceneManager.so > Plugin=Plugin_OctreeZone.so > Plugin=Plugin_ParticleFX.so > Plugin=RenderSystem_GL.so > Plugin=Plugin_PCZSceneManager.so > > # Don't edit anything starting from next line; it was autogenerated. > # -*- ogre-plugins -*- [Please, don't remove or modify this marker] > ------------------------------ > > When I then upgrade to -6, the current in unstable and without config > file, that's what happens: > > ------------------------------ > Preparing to replace libogre-1.7.3 1.7.3-3 (using > .../libogre-1.7.3_1.7.3-6_amd64.deb) ... > Moving obsolete conffile /etc/OGRE/plugins.cfg out of the way... > Unpacking replacement libogre-1.7.3 ... > dpkg: warning: unable to delete old directory '/etc/OGRE': Directory not empty > Processing triggers for man-db ... > (Reading database ... 111898 files and directories currently installed.) > Removing libboost-thread1.46.1 ... > Purging configuration files for libboost-thread1.46.1 ... > Setting up libogre-1.7.3 (1.7.3-6) ... > ------------------------------ > > Now the config files are (notice that it's been renamed to > ".dpkg-remove", but not removed (probably because of the missing > .postrm counterpart): > ------------------------------ > # find /etc/OGRE* -type f; echo; tail -n 100 /etc/OGRE*/* > /etc/OGRE/plugins.cfg.dpkg-remove > > # /etc/OGRE/plugins.cfg - ogre plugins installed on Debian systems > # [... same content as the previous one ...] > ------------------------------ > > Now, if I install 1.7.4-1, since it doesn't conflict with any other > version of the library (I removed Breaks/Replaces, since it's an > undesired feature, and if the files are not installed in the same path > is not a problem), it cannot go wild and remove other binary package's > config files. > > For one, the libogre-1.7.3 can continue to be installed when 1.7.4 is > installed, 1.7.4 shouldn't remove it. And I don't know if because of > this reason or because of the package name changed, when libogre-1.7.4 > is removed but .3-3 (one of the versions still shipping > /etc/OGRE/plugins.cfg) still installed, the file continues there. > When I remove .3-3, the /etc/OGRE/plugins.cfg (unmodified) goes away. > > So I'm starting to get out of ideas about how to solve this.
Ugh, things are getting complex. IMO we just have to worry about the following cases: libogremain-1.6.4 (from stable) -> X (where X is whatever wheezy ends up shipping) libogremain-1.6.4 -> libogre-1.7.3 version 1.6.3-5 (currently in testing) libogre-1.7.3 1.6.3-5 -> X 1.7.3-6 (currently in unstable) -> X Assuming that the severity of this bug is raised to serious to prevent 1.7.3-6 from transitioning into testing. If it transitions then we have to deal with: libogremain-1.6.4 -> libogre-1.7.3 1.7.3-6 libogre-1.7.3 1.7.3-5 -> libogre-1.7.3 1.7.3-6 libogre-1.7.3 1.7.3-6 -> X Maybe that would be easier? I guess the question is what to do with the libogre-1.7.3 package that is about to go away with 1.7.4. While it'd be nice to maintain the co-installability of libogre-1.7.3 and libogre-1.7.4, without any reverse-dependencies I'd be happy for libogre-1.7.4 to conflict with libogre-1.7.3, and for it to steal the other package's conffiles and remove them when installed. Then, with no more conffiles to worry about, going forward libogre-1.7.4 can be co-installable with any later versions. -- 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
