On 2015-04-18 12:34, Ole Streicher wrote: > Package: pyfits-utils > Version: 1:3.3-2 > Severity: wishlist > > Dear Aurelien, > > the package pyfits-utils contains the binaries fitscheck and fitsdiff. > > I am just preparing a new package "astropy-utils" [1], which will contain > the same binaries, but based on the astropy package. Since pyfits is going > to be deprecated, it would be useful to remove the pyfits-utils (since the > new ones are almost identical), or to lower the package priority to "extra". > > Usually, Debian handles conflicts on a "first-comes" base; however since > astropy is the successor of pyfits, I would ask that I can take priority in > this case. > > I am not sure how to make a smooth transition here. Since you have more > experience: could you please give me an advise? >
If you want to provide a smooth transition to users, the best is to add breaks and replaces in astropy-utils: Breaks: pyfits-utils (<< 1:3.3-2) Replaces: pyfits-utils (<< 1:3.3-2) As soon as it is done, I'll upload a new pyfits version with an empty pyfits-utils depending on astropy-utils. That way users of pyfits-utils will automatically get astropy-utils installed and nothing will break on their systems. The pyfits-utils package will be marked as transitional so it can be automatically removed from users's installation once astropy-utils is installed. The pyfits-utils package can then be removed from the archive in Buster. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
