Bug#644138: Bug 644138: kcc and heimdal-client both install /usr/bin/kcc
Hi devel, These packages do not remotely have the same functionality: kcc: Kanji code filter heimdal-clients: Heimdal Kerberos - clients kcc appears to have shipped /usr/bin/kcc approximately since 1997. heimdal-clients introduced /usr/bin/kcc in September 2011 and #644138 was filed shortly thereafter. The bug was closed by upload: * Add conflicts with kcc to heimdal-clients. Closes: #644138 and reopened the next day as not an appropriate use of Conflicts. Quoting policy 10.1: 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 Section 3.9, `Maintainer Scripts' and Section 7.4, `Conflicting binary packages - `Conflicts'' 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. It has now been five months without either maintainer raising this. -- Edward Allcutt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644138: Bug 644138: kcc and heimdal-client both install /usr/bin/kcc
On Sat, 2012-03-03 at 18:41 +, Edward Allcutt wrote: These packages do not remotely have the same functionality: kcc: Kanji code filter heimdal-clients: Heimdal Kerberos - clients kcc appears to have shipped /usr/bin/kcc approximately since 1997. heimdal-clients introduced /usr/bin/kcc in September 2011 and #644138 was filed shortly thereafter. Thanks for bringing this up. I think it would be reasonable for Heimdal to rename kcc to kcc.heimdal or something like that. Heimdal upstream has been shipping kcc since 2010, but we haven't included it in Debian before, so that probably causes the least upgrade issues. Cheers, Jelmer signature.asc Description: This is a digitally signed message part
Bug#644138: Bug 644138: kcc and heimdal-client both install /usr/bin/kcc
Jelmer Vernooij jel...@debian.org writes: Thanks for bringing this up. I think it would be reasonable for Heimdal to rename kcc to kcc.heimdal or something like that. Heimdal upstream has been shipping kcc since 2010, but we haven't included it in Debian before, so that probably causes the least upgrade issues. I would contact Heimdal upstream and ask if they'd be willing to change the name of the binary, given that it's a relatively new program and is much more recent than the other package. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644138: Bug 644138: kcc and heimdal-client both install /usr/bin/kcc
Hi, Wait a moment ... what about removing kcc package. (See below) On Sat, Mar 03, 2012 at 01:07:28PM -0800, Russ Allbery wrote: Jelmer Vernooij jel...@debian.org writes: I think it would be reasonable for Heimdal to rename kcc to kcc.heimdal or something like that. This is, as I understand, our standard procedure but ... what about removing kcc package after seeing how it is now. Heimdal upstream has been shipping kcc since 2010, but we haven't included it in Debian before, so that probably causes the least upgrade issues. I would contact Heimdal upstream and ask if they'd be willing to change the name of the binary, given that it's a relatively new program and is much more recent than the other package. There are so many encoding convertes. This one seems to be outdated and not so popular and not maintained. (It used to be popular as I remember but that may be as old as in 1998 when nkf was in non-free ...) Reality checks: I locally have 2 of them: libc-bin: /usr/bin/iconv (The most basic one without huristics) nkf: /usr/bin/nkf(The best huristic Japanese optimized one) As I quickly checked for japanese optimized ones, I found 3: nkf popcon = about 2000 last upload [2011-05-31] active kcc popcon 200 last upload [2004-11-29] no change from oldstable ack popcon 100 last upload [2008-07-24] no change from oldstable http://qa.debian.org/popcon-graph.php?packages=kcc+ack+nkfshow_installed=onwant_legend=onwant_ticks=onbeenhere=1 nkf: UTF-8 supported (in Description) kcc ack: UTF-8 not supported (in Description) Both kcc and ack maintainers are not active these dya as I vaguely recall. (CCed) Regards, Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
