On Thu, Apr 26, 2012 at 11:22:23PM +0900, Osamu Aoki wrote: > On Sun, Apr 22, 2012 at 06:04:43AM -0700, Josh Triplett wrote: > > On Sun, Apr 22, 2012 at 09:01:03PM +0900, Osamu Aoki wrote: > ... > > > > using dpkg-maintscript-helper. Please see the manpage of > > > > dpkg-maintscript-helper for details. > > > > No, don't hand-roll this; dpkg-maintscript-helper exists for a reason, > > and it does exactly what you need. > > Yah, this is new command from 2010. We only deal these issues every 2 > or more years. Well more abstruct solution is good as long as we know > what it does behind us. So time to learn new trick for a old dog (=me). > > As I read a bit complicated script /usr/bin/dpkg-maintscript-helper, > this seems to require us to use when the conffile change was introduced. > If I use this now, then the stable users who upgrade are handled fine > but the testing/unstable users will not be handled fine. Instead, good > old standard trick of using md5sum check with a set of fixed values > seems to save more cases. Basically, I missed the right moment. I will > use it for my future work but I need to think what is the best...
You can use dpkg-maintscript-helper and still cover all the users of the latest testing/unstable packages as well. When you release version X.Y-Z of the package, use dpkg-maintscript-helper with rm_conffile and tell it to clean up conffiles from any version X.Y-Z~ or older. > I now read: > http://www.dpkg.org/dpkg/ConffileHandling > http://wiki.debian.org/DpkgConffileHandling > > Certainly, many thoughts has been merged from old trick I know. > > Let me think about this for 10 days during our spring long weekend. No problem; not a rush. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
