Re: how to implement a renamed package
Thanks, - I know this and have done it previously in the case of zicq and krolden. However, what I really wanted to know is, how this (or any other) procedure can take care that the users of the old package will get the renamed package automatically updated with 'apt-get upgrade'? Oh, I see, the simple replaces and conflicts won't work there (I just tested it on some dummy packages because I thought it would, but you are right, it doesn't.) Otherwise, the new (renamed) upstream version could be easily overlooked and the users would just wonder why the old package is removed from the archives. As far as I know the standard procedure depends on the active selection of the renamed package, and the only replacement-effect is that it will remove the old package when it is installed. But the problem is: How shall the user know that the new package replaces another package with a different name? I haven't found anything better than Ben Burton's suggestion of the dummy package foo that depends on newfoo, that isn't very graceful, I'll admit. David
Re: how to implement a renamed package
Hello, On Sat, May 05, 2001 at 10:23:47PM -0500, Ben Burton wrote: Hi.. I've never done this myself, but I'm sure I've seen it happen in the past: If you're replacing foo with newfoo, you upload a new dummy package foo that contains absolutely nothing, but depends on newfoo. This way apt-get upgrade will get the latest (empty) foo and thus drag in newfoo with it. Many thanks. That is probably the best solution currently possible. I will do it this way, and will request the removal of the dummy package from the archives after a sufficiently long transition period. Cheers, Guenter -- Linux: Who needs GATES in a world without fences?
how to implement a renamed package
Hello, I am maintaing the Debian package puzzle and have a problem with the new upstream version. The package and program has been renamed by upstream to tree-puzzle, because there was a conflict with another program named puzzle. I was considering to make a new package tree-puzzle which conflicts and replaces puzzle, but this way the users of puzzle would not get the automatical upgrade of this new upstream version with 'apt-get upgrade'. Thus, how can I automatically replace the package puzzle with the new package tree-puzzle? Greetings, Guenter -- Linux: Who needs GATES in a world without fences?
Re: how to implement a renamed package
Sat, May 05, 2001 at 08:43:30PM +0200 wrote: Hello, I am maintaing the Debian package puzzle and have a problem with the new upstream version. The package and program has been renamed by upstream to tree-puzzle, because there was a conflict with another program named puzzle. I was considering to make a new package tree-puzzle which conflicts and replaces puzzle, but this way the users of puzzle would not get the automatical upgrade of this new upstream version with 'apt-get upgrade'. Thus, how can I automatically replace the package puzzle with the new package tree-puzzle? This is discussed in the Developer's Reference [1]: 9.3 Replacing or renaming packages Sometimes you made a mistake naming the package and you need to rename it. In this case, you need to follow a two-step process. 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 that 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. [1] : http://www.debian.org/doc/developers-reference/ch-archive-manip.en.html#s9.3 Greetings, Guenter -- Linux: Who needs GATES in a world without fences? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to implement a renamed package
On Sat, May 05, 2001 at 12:39:48PM -0700, David Whedon wrote: Sat, May 05, 2001 at 08:43:30PM +0200 wrote: Hello, I am maintaing the Debian package puzzle and have a problem with the new upstream version. The package and program has been renamed by upstream to tree-puzzle, because there was a conflict with another program named puzzle. I was considering to make a new package tree-puzzle which conflicts and replaces puzzle, but this way the users of puzzle would not get the automatical upgrade of this new upstream version with 'apt-get upgrade'. Thus, how can I automatically replace the package puzzle with the new package tree-puzzle? This is discussed in the Developer's Reference [1]: 9.3 Replacing or renaming packages Sometimes you made a mistake naming the package and you need to rename it. In this case, you need to follow a two-step process. 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 that 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. Just out of curiosity: what happens if an unrelated package with the old, obsoleted name is introduced into the archive? In the case in hand, upstream renamed puzzle - tree-puzzle precisely because there exists something with the name puzzle. If that other puzzle got put into debian, there could be great confusion. Has this ever happened? -S
Re: how to implement a renamed package
Hi, On Sat, May 05, 2001 at 12:39:48PM -0700, David Whedon wrote: This is discussed in the Developer's Reference [1]: 9.3 Replacing or renaming packages Sometimes you made a mistake naming the package and you need to rename it. In this case, you need to follow a two-step process. 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 that 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. Thanks, - I know this and have done it previously in the case of zicq and krolden. However, what I really wanted to know is, how this (or any other) procedure can take care that the users of the old package will get the renamed package automatically updated with 'apt-get upgrade'? Otherwise, the new (renamed) upstream version could be easily overlooked and the users would just wonder why the old package is removed from the archives. As far as I know the standard procedure depends on the active selection of the renamed package, and the only replacement-effect is that it will remove the old package when it is installed. But the problem is: How shall the user know that the new package replaces another package with a different name? Cheers, Guenter -- Linux: Who needs GATES in a world without fences?
Re: how to implement a renamed package
Thanks, - I know this and have done it previously in the case of zicq and krolden. However, what I really wanted to know is, how this (or any other) procedure can take care that the users of the old package will get the renamed package automatically updated with 'apt-get upgrade'? Otherwise, the new (renamed) upstream version could be easily overlooked and the users would just wonder why the old package is removed from the archives. Hi.. I've never done this myself, but I'm sure I've seen it happen in the past: If you're replacing foo with newfoo, you upload a new dummy package foo that contains absolutely nothing, but depends on newfoo. This way apt-get upgrade will get the latest (empty) foo and thus drag in newfoo with it. Of course you should take this with disclaimers because I'm just going on what I think I remember seeing from past upgrades on my own machine. Ben. -- Ben Burton ([EMAIL PROTECTED]) http://baasil.humbug.org.au/bab/ Director of Training Australian Informatics Olympiad Committee Feminism... is about a social, anti-family political movement that encourages women to leave their husbands, kill their children, practice witchcraft, destroy capitalism and become lesbian. - Pat Robertson, candidate for the Republican presidential nomination, 1988
