On Fri, Apr 22, 2005 at 10:39:59PM -0700, H. S. Teoh wrote: > reassign 305874 smurf > thanks > > Oops. You're right, making swami conflict with smurf breaks the > upgrade path. My bad, I had recalled reading something about using > conflicts to force an upgrade, but I guess I didn't remember the > context and thought it was the general procedure to provide an upgrade > path to another package. I was the one who told swami's maintainer to > add the Conflicts line. Oops. > > What's the correct way to handle the upgrade? Make a dummy smurf > package that depends on swami?
Hm, quoting developers reference: | 5.9.3 Replacing or renaming packages | | When you make a mistake naming your package, you should follow a | two-step process to rename it. First, set your debian/control file to | replace and conflict with the obsolete name of the package (see the | Debian Policy Manual for details). Once you've uploaded the package and | the package has moved into the archive, file a bug against | ftp.debian.org asking to remove the package with the obsolete name. Do | not forget to properly reassign the package's bugs at the same time. That's exactly what you did. I admit I'm not sure how apt, aptitude, etc etc are going to handle this, the only time I did a package rename, was via a dummy package, with Replaces:, and certainly not Conflicts:. This isn't discussed at all in the developers reference, and atm I don't intend to dive into how to do this properly. It's even not impossible I was wrong and this way will have the intended effect, but I'm not at all convinced that this way will indeed provide a proper upgrade path. I think you'd best search the archives, and if that fails, ask debian-devel@lists.debian.org, so that more eyes than just my own can look into it. I can be wrong too, it'd be silly to solely rely on my advice, when you can ask the advice of dozens of extra people :). --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
