Hi! On Fri, Mar 23, 2018 at 02:27:15PM -0700, Sean Whitton wrote: > Hello, > > On Fri, Mar 23 2018, Nicholas D Steeves wrote: > > > After many hours trying to work around bug #893598 while attempting to > > transition yasnippet-snippets to a dummy package I have had to > > conclude that yasnippet-snippets must remain the package that contains > > the snippets until buster+1. > > Please justify this conclusion. Someone on debian-mentors might see a > way out. > > -- > Sean Whitton I believe that it is preferable to have two packages with files that upgrade without warnings than the alternative of a dummy package that causes dpkg to emit warnings on upgrade. I tried every combination of maintscript, yasnippet-snippet.maintscript, and elpa-yasnippet.maintscript that I could think of, a variety of postrm experiments, and a variety of ways to treat the two packages in d/control. With yasnippet-snippets as an empty dummy package the following always occurred: Unpacking yasnippet-snippets (0~git20180307.2b4c4d7e-3) over (0~git20161123-1) ... dpkg: warning: unable to delete old directory '/usr/share/yasnippet-snippets/tuareg-mode': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/yasnippet-snippets/scala-mode': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/yasnippet-snippets/ruby-mode': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/yasnippet-snippets/js-mode': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/yasnippet-snippets/clojure-mode': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/yasnippet-snippets': Directory not empty The one exception was when I even tried a yasnippet-snippet.postrm which removed files from elpa-yasnippet-snippet...but that's an unacceptable approach because a dummy package should be safe to remove and shouldn't remove files from another package. Given that these warnings go away when yasnippet-snippets contains the snippets I have concluded that the snippets must remain as part of this package for one release. Given buster will have both an elpa-yasnippet-snippets and a yasnippet-snippets package the most significant reason against seems to be that users lose the ability to remove a dummy package... If someone sees a way around this, please ask if I've tried it :-) Cheers, Nicholas
Attachment:
signature.asc
Description: PGP signature