[SRU] trying to overwrite '/usr/bin/skip-tracker', which is also in package python-tempest-lib

[Felipe Reyes]

[Impact]

When trying to install python-tempest-lib and python3-tempest-lib in Vivid, I
got the following error

Unpacking python3-tempest-lib (0.4.0-0ubuntu1) ...
dpkg: error processing archive /var/cache/apt/archives/python3-tempest-lib_0.4.0-0ubuntu1_all.deb (--unpack):
 trying to overwrite '/usr/bin/skip-tracker', which is also in package python-tempest-lib 0.4.0-0ubuntu1

I would expect to be able to install both packages and be able to run python
scripts using version 2 or 3 of the interpreter.

The patch renames /usr/bin/skip-tracker generated with '#!/usr/bin/python3.4'
shebang to /usr/bin/python3-skip-tracker

This problem was already fixed in Debian and Wily.

[Test Case]

To reproduce just run:

$ sudo apt-get update
$ sudo apt-get install python-tempest-lib python3-tempest-lib

Expected result: both packages get installed

Actual result:
Unpacking python3-tempest-lib (0.4.0-0ubuntu1) ...
dpkg: error processing archive /var/cache/apt/archives/python3-tempest-lib_0.4.0-0ubuntu1_all.deb (--unpack):
 trying to overwrite '/usr/bin/skip-tracker', which is also in package python-tempest-lib 0.4.0-0ubuntu1

[Regression Potential]

None expected. skip-tracker is registered with update-alternatives, so no changes will be done from a user's point of view.

[Other Info]

None.

[Felipe Reyes (freyes)]

Attaching patch for wily

[Felipe Reyes (freyes)]

Attaching patch for vivid

[Felipe Reyes (freyes)]

Dear Maintainers,

I was taking a look to the debian package and it uses update-alternatives to handle skip-tracker and subunit-trace[0], should I pursue a patch to follow that same behavior? or do you pretend to re-sync the package with Debian during this cycle (wily)?

Best,

[0] http://anonscm.debian.org/cgit/openstack/python-tempest-lib.git/tree/debian/python3-tempest-lib.postinst

[Felipe Reyes (freyes)]

My bad, I just realized that subunit-trace uses alternatives, I'll update my patches.

[Brian Murray (brian-murray)]

It would be good to forward this bug and patch to Debian so that in the future we do not need to carry this patch. Once it is fixed in Debian and we sync the new version then we can perform an SRU for Vivid.

[Sebastien Bacher (seb128)]

Thanks, the package is in sync with Debian, could the work be send to them? Also the current version is https://launchpad.net/ubuntu/+source/python-tempest-lib/0.7.0-1 so the changes need to be rebased. Unsubscribing sponsors, can you subscribe them back if you rebase the work on the current version (ideally get the work in Debian so we can sync directly)

[Felipe Reyes (freyes)]

This is fixed in Debian and Wily, so we just need get Vivid fixed, the patch is already attached to this bug report

[Tim (darkxst)]

This is fixed in Xenial and Wily, doesnt seem critical enough to SRU into vivid this late in its lifecycle.