(Please keep the bug report in copy, it's important for other people to see that the maintainer is acting on RC bugs)
On Sun, 02 Mar 2008, Tormod Volden wrote: > > xscreensaver-data (and -extra) needs at least > > to Replaces: xscreensaver (<< 5.04-3) and probably also Conflicts > > > > xscreensaver-data also needs to Replaces: xscreensaver-gl (<< 5.04-3) > > apparently (If I read the changelog correctly). > > The changelog was wrong! It should be of course: > * (From Ubuntu) Split xscreensaver-gl package into: > - xscreensaver-gl (standard GL hacks) > - xscreensaver-gl-extra (GL hacks not installed by default) > Then xscreensaver-data does not need Replaces: xscreensaver-gl, right? Right, then xscreensaver-gl-extra needs a Replaces: xscreensaver-gl (<< 5.04-3). > Is it allowed to correct a previous changelog entry? To make it less > confusing for the future. Yes. > I have sprinkled on Conflicts and Replaces. Do you think it looks OK > in the attached control file? I am currently doing upgrade tests, but > there might be some use cases that I don't catch. Why did you add a Replaces: xscreensaver-data (<< 5.04-3) to xscreensaver-gl? xscreensaver-gl doesn't take over files from xscreensaver-data since xscreensaver-data is a new package. Same for xscreensaver-gl-extra. > Should I add an urgency=high to the new package? No. There's no need for that, the bug has not yet reached testing. On Sun, 02 Mar 2008, Tormod Volden wrote: > I am reading > http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps > > "A Conflicts entry should almost never have an "earlier than" version > clause. This would prevent dpkg from upgrading or installing the > package which declared such a conflict until the upgrade or removal of > the conflicted-with package had been completed." > > Does that mean that my Conflicts: xscreensaver (<< 5.04-3) are not good? No, it's precisely what we wanted. We want to install xscreensaver-data only after xscreensaver has been upgraded to the version without the conflicting files. That said, you don't need the conflict *if* the installation of xscreensaver-data doesn't break previous versions of xscreensaver package (the scenario is: you run an old version of xscreensaver and you only install xscreensaver-data (with apt-get install or dpkg -i)... does xscreensaver still work ?) The "Breaks" field will replace the "Conflicts:" field for such usage in the future (lenny+1). Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/
