Hi Sven and Michael, thank you for the report and sorry for breaking it. > specifically > > timidity.maintscript > rm_conffile /etc/default/timidity 2.14.0-1~ timidity-daemon > > doesn't look correct either. > dpkg-maintscript-helper does not have support for moving conffiles from > one package to another (and why would you remove the conffile from > timidity-daemon, the package you moved the conffile into?) I'm not removing it from timidity-daemon, but from timidity (timidity.maintscript). In the last column I'm marking timidity-daemon as the owner of the file. In my tests this also worked well, an unmodified file was just moved to the timidity-daemon package, and a modified default file would also stay intact (i.e., your changes are preserved after upgrade). Without the last column the (modified) default file was removed during upgrade and a fresh file was installed by timidity-daemon (your modifications were lost). I'm now just a bit puzzled why it didn't work in the same way for the init.d file. Maybe because the other package (timidity-daemon) was already the owner before (in the old version). > Afaik, the best you can do is to have a versioned Breaks/Replaces > against the package which previously shipped the conffile. The conffiles also need to be cleaned up via a maintscript, because users might not have the timidity-daemon package installed. I think the init.d file should now be handled like this: (Though this will lose changes made to the file before it was moved to the other package (2.13.2-27, long before old-old-stable)) -rm_conffile /etc/init.d/timidity 2.14.0-2~ timidity-daemon +rm_conffile /etc/init.d/timidity 2.14.0-3~ Kind regards, Reiner
Attachment:
signature.asc
Description: PGP signature