Your message dated Wed, 5 Mar 2014 11:17:47 -0500
with message-id <[email protected]>
and subject line Re: Bug#740856: docker.io: Please provide the docker command 
instead of docker.io
has caused the Debian Bug report #740856,
regarding docker.io: Please provide the docker command instead of docker.io
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
740856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740856
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: docker.io
Version: 0.8.0+dfsg1-2
Severity: wishlist

Dear Maintainer,

Unfortunately, /usr/bin/docker is provided by the docker package. Thus, I 
imagine, the renaming of the command to docker.io.

This is problematic, though, as a docker.io user tends to use quite a lot the 
docker.io command, and following upstream documentation becomes painful.

In addition, scripts need to be adapted too (see #740855).

I think that maybe the docker tool in docker package isn't a command-line that 
most users would trigger so often, as residing in a desktop environment, and 
could then very well be renamed without anyone noticing (but saved sessions)...

Any opinions ?

Best regards,

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages docker.io depends on:
ii  adduser              3.113+nmu3
ii  init-system-helpers  1.14
ii  iptables             1.4.21-1
ii  libc6                2.17-97
ii  libdevmapper1.02.1   2:1.02.83-2
ii  libsqlite3-0         3.8.3.1-1
ii  lxc                  0.9.0~alpha3-2+deb8u1
ii  perl                 5.18.2-2+b1

Versions of packages docker.io recommends:
ii  aufs-tools       1:3.2+20130722-1.1
ii  ca-certificates  20130906
ii  xz-utils         5.1.1alpha+20120614-2

docker.io suggests no packages.

-- debconf-show failed

--- End Message ---
--- Begin Message ---
On Wed, Mar 05, 2014 at 05:10:54PM +0100, Olivier Berger wrote:
> Dear Maintainer,
> 
> Unfortunately, /usr/bin/docker is provided by the docker package. Thus, I 
> imagine, the renaming of the command to docker.io.
> 
> This is problematic, though, as a docker.io user tends to use quite a lot the 
> docker.io command, and following upstream documentation becomes painful.
> 
> In addition, scripts need to be adapted too (see #740855).
> 
> I think that maybe the docker tool in docker package isn't a command-line 
> that most users would trigger so often, as residing in a desktop environment, 
> and could then very well be renamed without anyone noticing (but saved 
> sessions)...
> 
> Any opinions ?

Heyya Olivier, pleasure as always :)

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)

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.

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte <[email protected]>  |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `-     http://people.debian.org/~paultag/conduct-statement.txt

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to