On Mon, Apr 24, 2017 at 3:50 PM, bugproxy <email address hidden> wrote:
> ------- Comment From <email address hidden> 2017-04-24 09:45 EDT-------
> Thanks Frank for verifying. Intersting, I was thinking from the above
> messages that the package was only available in yakkety-proposed for the
> time being.
>
> Summary: The updated mtx package now installs fine. See details below,
> first negative test by trying from yakkety and failing, then adding
> yakkety-proposed repo:
>
> # apt-get install mtx
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer
> required:
> g++-5 libasprintf0v5 libboost-iostreams1.58.0 libicu55 libjson-c-dev
> libjson0 libstdc++-5-dev
> linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic
> linux-image-4.4.0-21-generic
> linux-image-extra-4.4.0-21-generic
> Use 'apt autoremove' to remove them.
> The following NEW packages will be installed:
> mtx
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 93.9 kB of archives.
> After this operation, 395 kB of additional disk space will be used.
> Get:1 http://ports.ubuntu.com yakkety/main s390x mtx s390x 1.3.12-9 [93.9
> kB]
> Fetched 93.9 kB in 0s (1079 kB/s)
> Selecting previously unselected package mtx.
> (Reading database ... 100030 files and directories currently installed.)
> Preparing to unpack .../mtx_1.3.12-9_s390x.deb ...
> Unpacking mtx (1.3.12-9) ...
> dpkg: error processing archive /var/cache/apt/archives/mtx_1.3.12-9_s390x.deb
> (--unpack):
> trying to overwrite '/usr/share/bash-completion/completions/mtx', which
> is also in package bash-completion 1:2.1-4.3ubuntu1
> Errors were encountered while processing:
> /var/cache/apt/archives/mtx_1.3.12-9_s390x.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> root@s8314003:~# apt-cache policy mtx
> mtx:
> Installed: (none)
> Candidate: 1.3.12-9
> Version table:
> 1.3.12-9 500
> 500 http://ports.ubuntu.com yakkety/main s390x Packages
>
> ____________________________________________________________
> ____________________
>
> After adding yakkety-proposed to the /etc/apt/sources.list file and
> apt-get update
> apt-get install mtx was processing without error.
>
> # apt-get install mtx
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer
> required:
> g++-5 libasprintf0v5 libboost-iostreams1.58.0 libicu55 libjson-c-dev
> libjson0 libstdc++-5-dev
> linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic
> linux-image-4.4.0-21-generic
> linux-image-extra-4.4.0-21-generic
> Use 'apt autoremove' to remove them.
> The following NEW packages will be installed:
> mtx
> 0 upgraded, 1 newly installed, 0 to remove and 31 not upgraded.
> Need to get 93.2 kB of archives.
> After this operation, 392 kB of additional disk space will be used.
> Get:1 http://ports.ubuntu.com/ubuntu-ports yakkety-proposed/main s390x
> mtx s390x 1.3.12-9ubuntu0.16.10.1 [93.2 kB]
> Fetched 93.2 kB in 0s (662 kB/s)
> (Reading database ... 100030 files and directories currently installed.)
> Preparing to unpack .../mtx_1.3.12-9ubuntu0.16.10.1_s390x.deb ...
> Unpacking mtx (1.3.12-9ubuntu0.16.10.1) ...
> Processing triggers for man-db (2.7.5-1) ...
> Setting up mtx (1.3.12-9ubuntu0.16.10.1) ...
>
> --
> You received this bug notification because you are subscribed to Ubuntu
> on IBM z Systems.
> Matching subscriptions: <email address hidden>
> https://bugs.launchpad.net/bugs/1642582
>
> Title:
> mtx package version 1.3.12-9 installation fails with duplicate bash-
> completion via apt-get
>
> Status in Ubuntu on IBM z Systems:
> Fix Committed
> Status in mtx package in Ubuntu:
> Fix Released
> Status in mtx source package in Xenial:
> Fix Committed
> Status in mtx source package in Yakkety:
> Fix Committed
> Status in mtx source package in Zesty:
> Fix Released
> Status in mtx package in Debian:
> Fix Released
>
> Bug description:
> [Impact]
>
> * mtx package has an arch-skew contents. On xenial and yakkety, on
> s390x, the package was build with new enough bash-completion debhelper
> addon that has placed the completion files into /usr which generates file
> conflict with bash-completion package itself
> * on all other architectures in xenial and yakkety the bash completion
> file is shipped by the mtx package, redundantly in /etc, when there is a
> completion file in /usr in bash-completion package already
> * in zesty the bash completion file got remoted from the mtx package in
> favor of bash-completion package one.
> * to avoid file conflict on s390x on xenial/yakkety, I'm proposing to
> rebuild mtx package on xenial and yakkety and remove the redudant bash
> completion file
>
> [Testcase]
> * Co-install mtx package and bash-completion package, without any file
> conflicts
> * Verify that /etc/bash_completion.d/mtx file does not exist and/or is
> removed during the installation of the new mtx package (that should happen
> on non-s390x architectures)
> * Verify that mtx bash completion is still available
>
> [Original bug report]
>
> Summary
> =======
> Machine: IBM z13, Ubuntu 16.04.01. uname -a
> Linux s8314007 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:42:36 UTC
> 2016 s390x s390x s390x GNU/Linux
> We were unable to install the 'mtx' package for control of tape
> autochangers via 'apt-get install mtx'
>
> Details
> =======
> We wanted to install both the mt-st and mtx packages for s390 tape
> support.
> We encountered a problem in the mtx_1.3.12-9_s390x.deb package which was
> downloaded to /var/cache/apt/archives/ location but installation was not
> performed due to duplicate bash completion data being delivered.
> See the console output section below for results and more details about
> the error itself.
> We expect the mtx package to install smoothly with apt-get install mtx.
>
> We worked around with:
> ~~~~~~~~~~~~~~~~~~~~~~
> # dpkg --force-overwrite -i /var/cache/apt/archives/mtx_1.
> 3.12-9_s390x.deb
> (Reading database ... 76609 files and directories currently installed.)
> Preparing to unpack .../mtx_1.3.12-9_s390x.deb ...
> Unpacking mtx (1.3.12-9) ...
> dpkg: warning: overriding problem because --force enabled:
> dpkg: warning: trying to overwrite '/usr/share/bash-completion/completions/mtx',
> which is also in package bash-completion 1:2.1-4.2ubuntu1.1
> Setting up mtx (1.3.12-9) ...
> Processing triggers for man-db (2.7.5-1) ...
> # dpkg -l|grep mtx
> ii mtx 1.3.12-9
> s390x controls tape autochangers
>
> Console output
> ==============
> # apt-get install mtx -y
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following NEW packages will be installed:
> mtx
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 93.9 kB of archives.
> After this operation, 395 kB of additional disk space will be used.
> Get:1 http://ports.ubuntu.com xenial/main s390x mtx s390x 1.3.12-9
> [93.9 kB]
> Fetched 93.9 kB in 0s (0 B/s)
> (Reading database ... 76609 files and directories currently installed.)
> Preparing to unpack .../mtx_1.3.12-9_s390x.deb ...
> Unpacking mtx (1.3.12-9) ...
> dpkg: error processing archive /var/cache/apt/archives/mtx_1.3.12-9_s390x.deb
> (--unpack):
> trying to overwrite '/usr/share/bash-completion/completions/mtx',
> which is also in package bash-completion 1:2.1-4.2ubuntu1.1
> Processing triggers for man-db (2.7.5-1) ...
> Errors were encountered while processing:
> /var/cache/apt/archives/mtx_1.3.12-9_s390x.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> #
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-z-systems/+bug/1642582/+subscriptions
>
Hi Christian, /bugs.launchpad .net/ubuntu/ +source/ mtx/+bug/ 1642582/ comments/ 8 /bugs.launchpad .net/ubuntu/ +source/ mtx/+bug/ 1642582/ comments/ 9
well, the messages that ask for verification are created for all Ubuntu
releases that are affected and currently still in service.
And these msgs look very similar:
The Yakkety msg:
https:/
and the Xenial msg:
https:/
Anyway, good that you were able to do the verification for yakkety as well
- thx for that!
Frank Heimes | Tech. Lead z | Canonical Ltd. on-big- iron.blogspot. com ubuntu- on-big- iron.blogspot. com/?view= sidebar> | fridge. ubuntu. com
mail: <email address hidden>
irc: jfh
P: +49 (0) 7031 415515
www.canonical.com | www.ubuntu.com | ubuntu-
<http://
http://
On Mon, Apr 24, 2017 at 3:50 PM, bugproxy <email address hidden> wrote:
> ------- Comment From <email address hidden> 2017-04-24 09:45 EDT------- iostreams1. 58.0 libicu55 libjson-c-dev 4.4.0-21 linux-headers- 4.4.0-21- generic 4.4.0-21- generic extra-4. 4.0-21- generic ports.ubuntu. com yakkety/main s390x mtx s390x 1.3.12-9 [93.9 1.3.12- 9_s390x. deb ... apt/archives/ mtx_1.3. 12-9_s390x. deb bash-completion /completions/ mtx', which apt/archives/ mtx_1.3. 12-9_s390x. deb ports.ubuntu. com yakkety/main s390x Packages _______ _______ _______ _______ _______ _______ _______ ____ _______ ______ sources. list file and iostreams1. 58.0 libicu55 libjson-c-dev 4.4.0-21 linux-headers- 4.4.0-21- generic 4.4.0-21- generic extra-4. 4.0-21- generic ports.ubuntu. com/ubuntu- ports yakkety- proposed/ main s390x 9ubuntu0. 16.10.1 [93.2 kB] 1.3.12- 9ubuntu0. 16.10.1_ s390x.deb ... 9ubuntu0. 16.10.1) ... 9ubuntu0. 16.10.1) ... /bugs.launchpad .net/bugs/ 1642582 completion. d/mtx file does not exist and/or is 12-9_s390x. deb package which was apt/archives/ location but installation was not ~~~~~~~ ~~~~~~~ ~ apt/archives/ mtx_1. 1.3.12- 9_s390x. deb ... bash-completion /completions/ mtx', ports.ubuntu. com xenial/main s390x mtx s390x 1.3.12-9 1.3.12- 9_s390x. deb ... apt/archives/ mtx_1.3. 12-9_s390x. deb bash-completion /completions/ mtx', apt/archives/ mtx_1.3. 12-9_s390x. deb /bugs.launchpad .net/ubuntu- z-systems/ +bug/1642582/ +subscriptions
> Thanks Frank for verifying. Intersting, I was thinking from the above
> messages that the package was only available in yakkety-proposed for the
> time being.
>
> Summary: The updated mtx package now installs fine. See details below,
> first negative test by trying from yakkety and failing, then adding
> yakkety-proposed repo:
>
> # apt-get install mtx
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer
> required:
> g++-5 libasprintf0v5 libboost-
> libjson0 libstdc++-5-dev
> linux-headers-
> linux-image-
> linux-image-
> Use 'apt autoremove' to remove them.
> The following NEW packages will be installed:
> mtx
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 93.9 kB of archives.
> After this operation, 395 kB of additional disk space will be used.
> Get:1 http://
> kB]
> Fetched 93.9 kB in 0s (1079 kB/s)
> Selecting previously unselected package mtx.
> (Reading database ... 100030 files and directories currently installed.)
> Preparing to unpack .../mtx_
> Unpacking mtx (1.3.12-9) ...
> dpkg: error processing archive /var/cache/
> (--unpack):
> trying to overwrite '/usr/share/
> is also in package bash-completion 1:2.1-4.3ubuntu1
> Errors were encountered while processing:
> /var/cache/
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> root@s8314003:~# apt-cache policy mtx
> mtx:
> Installed: (none)
> Candidate: 1.3.12-9
> Version table:
> 1.3.12-9 500
> 500 http://
>
> _______
> _______
>
> After adding yakkety-proposed to the /etc/apt/
> apt-get update
> apt-get install mtx was processing without error.
>
> # apt-get install mtx
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer
> required:
> g++-5 libasprintf0v5 libboost-
> libjson0 libstdc++-5-dev
> linux-headers-
> linux-image-
> linux-image-
> Use 'apt autoremove' to remove them.
> The following NEW packages will be installed:
> mtx
> 0 upgraded, 1 newly installed, 0 to remove and 31 not upgraded.
> Need to get 93.2 kB of archives.
> After this operation, 392 kB of additional disk space will be used.
> Get:1 http://
> mtx s390x 1.3.12-
> Fetched 93.2 kB in 0s (662 kB/s)
> (Reading database ... 100030 files and directories currently installed.)
> Preparing to unpack .../mtx_
> Unpacking mtx (1.3.12-
> Processing triggers for man-db (2.7.5-1) ...
> Setting up mtx (1.3.12-
>
> --
> You received this bug notification because you are subscribed to Ubuntu
> on IBM z Systems.
> Matching subscriptions: <email address hidden>
> https:/
>
> Title:
> mtx package version 1.3.12-9 installation fails with duplicate bash-
> completion via apt-get
>
> Status in Ubuntu on IBM z Systems:
> Fix Committed
> Status in mtx package in Ubuntu:
> Fix Released
> Status in mtx source package in Xenial:
> Fix Committed
> Status in mtx source package in Yakkety:
> Fix Committed
> Status in mtx source package in Zesty:
> Fix Released
> Status in mtx package in Debian:
> Fix Released
>
> Bug description:
> [Impact]
>
> * mtx package has an arch-skew contents. On xenial and yakkety, on
> s390x, the package was build with new enough bash-completion debhelper
> addon that has placed the completion files into /usr which generates file
> conflict with bash-completion package itself
> * on all other architectures in xenial and yakkety the bash completion
> file is shipped by the mtx package, redundantly in /etc, when there is a
> completion file in /usr in bash-completion package already
> * in zesty the bash completion file got remoted from the mtx package in
> favor of bash-completion package one.
> * to avoid file conflict on s390x on xenial/yakkety, I'm proposing to
> rebuild mtx package on xenial and yakkety and remove the redudant bash
> completion file
>
> [Testcase]
> * Co-install mtx package and bash-completion package, without any file
> conflicts
> * Verify that /etc/bash_
> removed during the installation of the new mtx package (that should happen
> on non-s390x architectures)
> * Verify that mtx bash completion is still available
>
> [Original bug report]
>
> Summary
> =======
> Machine: IBM z13, Ubuntu 16.04.01. uname -a
> Linux s8314007 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:42:36 UTC
> 2016 s390x s390x s390x GNU/Linux
> We were unable to install the 'mtx' package for control of tape
> autochangers via 'apt-get install mtx'
>
> Details
> =======
> We wanted to install both the mt-st and mtx packages for s390 tape
> support.
> We encountered a problem in the mtx_1.3.
> downloaded to /var/cache/
> performed due to duplicate bash completion data being delivered.
> See the console output section below for results and more details about
> the error itself.
> We expect the mtx package to install smoothly with apt-get install mtx.
>
> We worked around with:
> ~~~~~~~
> # dpkg --force-overwrite -i /var/cache/
> 3.12-9_s390x.deb
> (Reading database ... 76609 files and directories currently installed.)
> Preparing to unpack .../mtx_
> Unpacking mtx (1.3.12-9) ...
> dpkg: warning: overriding problem because --force enabled:
> dpkg: warning: trying to overwrite '/usr/share/
> which is also in package bash-completion 1:2.1-4.2ubuntu1.1
> Setting up mtx (1.3.12-9) ...
> Processing triggers for man-db (2.7.5-1) ...
> # dpkg -l|grep mtx
> ii mtx 1.3.12-9
> s390x controls tape autochangers
>
> Console output
> ==============
> # apt-get install mtx -y
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following NEW packages will be installed:
> mtx
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 93.9 kB of archives.
> After this operation, 395 kB of additional disk space will be used.
> Get:1 http://
> [93.9 kB]
> Fetched 93.9 kB in 0s (0 B/s)
> (Reading database ... 76609 files and directories currently installed.)
> Preparing to unpack .../mtx_
> Unpacking mtx (1.3.12-9) ...
> dpkg: error processing archive /var/cache/
> (--unpack):
> trying to overwrite '/usr/share/
> which is also in package bash-completion 1:2.1-4.2ubuntu1.1
> Processing triggers for man-db (2.7.5-1) ...
> Errors were encountered while processing:
> /var/cache/
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> #
>
> To manage notifications about this bug go to:
> https:/
>