Bug#503367: [Debian-med-packaging] Bug#503367: plink: file conflict with putty-tools
On Tue, Oct 28, 2008 at 2:59 AM, Brian May [EMAIL PROTECTED] wrote: Steffen Möller wrote: Teodor happened to have nicely explained my objections to rename plink. Except what he said is wrong, puttygen hasn't been renamed. Yes, puttygen hasn't been renamed. It was a wrong assumption from me .. Dear Colin, if you don't mind too much, or if you could be bribed with a few beers, please be so kind to rename the plink binary package. If we rename plink in putty (I think that is what you are asking?), that it going to make our version of putty inconsistent with every other putty package out there. This program is often used by scripts, they will break too. I still believe it is best to rename 'plink' to 'puttylink' in putty-tools binary package. Anyway, this should be fixed for squeeze since in lenny there is no conflict (plink is not included in lenny). Thanks
Bug#503367: [Debian-med-packaging] Bug#503367: plink: file conflict with putty-tools
Hello, plink has just made it to the archive. Teodor happened to have nicely explained my objections to rename plink. Dear Colin, if you don't mind too much, or if you could be bribed with a few beers, please be so kind to rename the plink binary package. Many thanks and best regards, Steffen (who should have checked and asked prior to his upload) Teodor schrieb: On Sat, Oct 25, 2008 at 12:24 PM, Charles Plessy [EMAIL PROTECTED] wrote: Both programs are intended for command line, and could be used in scripts. We may even find users who want to install both at the same time. Very annoying… Since Plink is younger than Putty, I think that the burden of the renaming is for us (the Debian Med packaging team). I plan to rename /usr/bin/plink to /usr/bin/Plink, that would be a symbolic link to /usr/lib/plink/plink so that with an appropriate PATH, users can rescue their scripts. Since renaming seems to be the only solution, than IMO it is more appropriate to rename 'plink' in putty-tools than in the plink packages since this is exactly the source/binary package name. This has been done already in putty-tools for the 'puttygen' binary. Thanks piti:~# dpkg -L putty-tools [snip] /usr/bin/pscp /usr/bin/psftp /usr/bin/plink /usr/bin/puttygen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503367: [Debian-med-packaging] Bug#503367: plink: file conflict with putty-tools
Le Sat, Oct 25, 2008 at 08:40:59AM +0200, Sven Joachim a écrit : Package: plink Version: 1.03p1-1 Severity: serious The /usr/bin/plink name is already taken: , | # aptitude install plink | [...] | Selecting previously deselected package plink. | (Reading database ... 134796 files and directories currently installed.) | Unpacking plink (from .../plink_1.03p1-1_i386.deb) ... | dpkg: error processing /var/cache/apt/archives/plink_1.03p1-1_i386.deb (--unpack): | trying to overwrite `/usr/bin/plink', which is also in package putty-tools | dpkg-deb: subprocess paste killed by signal (Broken pipe) | Errors were encountered while processing: | /var/cache/apt/archives/plink_1.03p1-1_i386.deb | E: Sub-process /usr/bin/dpkg returned an error code (1) ` Hi Sven, thank you for reporting this bug. Both programs are intended for command line, and could be used in scripts. We may even find users who want to install both at the same time. Very annoying… Since Plink is younger than Putty, I think that the burden of the renaming is for us (the Debian Med packaging team). I plan to rename /usr/bin/plink to /usr/bin/Plink, that would be a symbolic link to /usr/lib/plink/plink so that with an appropriate PATH, users can rescue their scripts. But before doing so, I would like to ask the readers of debian-devel: - if it is not a bad idea to have to programs whose name only differs by case (do we support file systems à la Macintosh?), - if they have a better idea in general. Have a nice day. (By the way, are you interested in genetics ?) -- Charles Plessy Debian Med packaging team, Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503367: [Debian-med-packaging] Bug#503367: plink: file conflict with putty-tools
On Sat, Oct 25, 2008 at 12:24 PM, Charles Plessy [EMAIL PROTECTED] wrote: Since Plink is younger than Putty, I think that the burden of the renaming is for us (the Debian Med packaging team). I plan to rename /usr/bin/plink to /usr/bin/Plink, that would be a symbolic link to /usr/lib/plink/plink so that with an appropriate PATH, users can rescue their scripts. This *upercase first letter* thinghy is no annoying and ugly .. But before doing so, I would like to ask the readers of debian-devel: - if it is not a bad idea to have to programs whose name only differs by case (do we support file systems à la Macintosh?), - if they have a better idea in general. IMO a simple Conflicts: putty-tools is enough. If they provide the same functionality than an alternative is better than conflicting with each other. Cheers
Bug#503367: [Debian-med-packaging] Bug#503367: plink: file conflict with putty-tools
Le Sat, Oct 25, 2008 at 06:07:11PM +0300, Teodor a écrit : IMO a simple Conflicts: putty-tools is enough. If they provide the same functionality than an alternative is better than conflicting with each other. Hello Tedor, thanks for the feedback, but this would be against our Policy, because the two files competing for the same name do not provide the same functionality: Two different packages must not install programs with different functionality but with the same filenames. (The case of two programs having the same functionality but different implementations is handled via alternatives or the Conflicts mechanism. See Maintainer Scripts, Section 3.9 and Conflicting binary packages - Conflicts, Section 7.4 respectively.) If this case happens, one of the programs must be renamed. The maintainers should report this to the debian-devel mailing list and try to find a consensus about which program will have to be renamed. If a consensus cannot be reached, both programs must be renamed. http://www.debian.org/doc/debian-policy/ch-files.html#s10.1 Have a nice weekend, -- Charles Plessy Debian Med packaging team, Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503367: [Debian-med-packaging] Bug#503367: plink: file conflict with putty-tools
On Sat, Oct 25, 2008 at 6:21 PM, Charles Plessy [EMAIL PROTECTED] wrote: Le Sat, Oct 25, 2008 at 06:07:11PM +0300, Teodor a écrit : IMO a simple Conflicts: putty-tools is enough. If they provide the same functionality than an alternative is better than conflicting with each other. Hello Tedor, thanks for the feedback, but this would be against our Policy, because the two files competing for the same name do not provide the same functionality: Yes, it seems to be the case. I'm a newcomer to Debian but IMO this restriction about Conflicts in s10.1 seems a little unpractical. The Conflicts section of the policy [1] does not specify anything about the restriction of packages that should conflict on each other *only* if they provide the same functionality. The *alternative* mechanism is the most natural way to handle the conflicts between packages that provide the same functionality. Otherwise, the Conflicts directive could help for packages that doesn't provide the same functionality. Thanks [1] http://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts
Bug#503367: [Debian-med-packaging] Bug#503367: plink: file conflict with putty-tools
On Sat, Oct 25, 2008 at 12:24 PM, Charles Plessy [EMAIL PROTECTED] wrote: Both programs are intended for command line, and could be used in scripts. We may even find users who want to install both at the same time. Very annoying… Since Plink is younger than Putty, I think that the burden of the renaming is for us (the Debian Med packaging team). I plan to rename /usr/bin/plink to /usr/bin/Plink, that would be a symbolic link to /usr/lib/plink/plink so that with an appropriate PATH, users can rescue their scripts. Since renaming seems to be the only solution, than IMO it is more appropriate to rename 'plink' in putty-tools than in the plink packages since this is exactly the source/binary package name. This has been done already in putty-tools for the 'puttygen' binary. Thanks piti:~# dpkg -L putty-tools [snip] /usr/bin/pscp /usr/bin/psftp /usr/bin/plink /usr/bin/puttygen
Bug#503367: [Debian-med-packaging] Bug#503367: plink: file conflict with putty-tools
On Sat, 2008-10-25 at 20:18 +0300, Teodor wrote: Since renaming seems to be the only solution, than IMO it is more appropriate to rename 'plink' in putty-tools than in the plink packages since this is exactly the source/binary package name. [...] This has been done already in putty-tools for the 'puttygen' binary. [...] piti:~# dpkg -L putty-tools [snip] /usr/bin/pscp /usr/bin/psftp /usr/bin/plink /usr/bin/puttygen Erm, puttygen isn't renamed. That's what the upstream binary is known as and has been ever since its creation more than four years ago (although more often puttygen.exe for predictable reasons). Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503367: [Debian-med-packaging] Bug#503367: plink: file conflict with putty-tools
On Sat, Oct 25, 2008 at 08:18:23PM +0300, Teodor wrote: On Sat, Oct 25, 2008 at 12:24 PM, Charles Plessy [EMAIL PROTECTED] wrote: Both programs are intended for command line, and could be used in scripts. We may even find users who want to install both at the same time. Very annoying… Since Plink is younger than Putty, I think that the burden of the renaming is for us (the Debian Med packaging team). I plan to rename /usr/bin/plink to /usr/bin/Plink, that would be a symbolic link to /usr/lib/plink/plink so that with an appropriate PATH, users can rescue their scripts. Since renaming seems to be the only solution, than IMO it is more appropriate to rename 'plink' in putty-tools than in the plink packages since this is exactly the source/binary package name. This has been done already in putty-tools for the 'puttygen' binary. As Adam said, puttygen hasn't been renamed; this is the upstream name. Since as Charles said the debian-med plink is younger, and putty's plink may well be embedded in people's environment variables and such, I'd much rather that debian-med's program change its name since they seem to be willing to do so. Thanks, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
