Paul Tagliamonte <paul...@debian.org> writes: > > A policy refresher for those who stumble on this bug and want to know > more about why it's being closed. > > | 10.1 Binaries > | > | 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. > > (I avoided this, docker was there first. I'm planning on renaming it to > wmdocker, but doing this switch sucks for everyone) >
Maybe we could try to ask for the renaming... lemme file a wishlist bug on docker's side... > node vs nodejs broke (/sbin/node vs /usr/bin/node) and ctte mandated the > change. I see no reason why we're any more special. > AFAIR, the two node programs could be tools that one triggers on the command line often, rendering the conflict more prominent than in this case, where what matters most is the content of docker's menu file command specification AFAIU... Lemme ask on docker's side and report... Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
