[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
on Ubuntu Xenial this still gives this error: ``` Traceback (most recent call last): File "/usr/bin/click", line 37, in import click_package as click ImportError: No module named 'click_package' dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... Traceback (most recent call last): File "/usr/bin/click", line 37, in import click_package as click ImportError: No module named 'click_package' dpkg: error processing archive /var/cache/apt/archives/click-apparmor_0.3.13.1_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 1 ``` i did a little experiment: `sudo apt update && sudo apt install python3-click-package python3-click libclick-0.4-dev libclick-0.4` then reinstalling: `sudo apt install click click-apparmor --reinstall --force-yes` fixes this now on Xenial Xerus -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: Fix Released Status in click source package in Yakkety: Fix Released Status in click source package in Zesty: Fix Released Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
I get the following error for sudo apt-get -f install Preparing to unpack .../click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb ... Traceback (most recent call last): File "/usr/bin/click", line 37, in import click ImportError: No module named 'click' dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... Traceback (most recent call last): File "/usr/bin/click", line 37, in import click ImportError: No module named 'click' dpkg: error processing archive /var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 1 Job for click-system-hooks.service failed because the control process exited with error code. See "systemctl status click-system-hooks.service" and "journalctl -xe" for details. click-system-hooks.service couldn't start. Errors were encountered while processing: /var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I installed python click with sudo pip3 install click and tried running sudo apt-get -f install Preparing to unpack .../click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb ... Traceback (most recent call last): File "/usr/bin/click", line 55, in from click import commands ImportError: cannot import name 'commands' dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... Traceback (most recent call last): File "/usr/bin/click", line 55, in from click import commands ImportError: cannot import name 'commands' dpkg: error processing archive /var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 1 Job for click-system-hooks.service failed because the control process exited with error code. See "systemctl status click-system-hooks.service" and "journalctl -xe" for details. click-system-hooks.service couldn't start. Errors were encountered while processing: /var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: Fix Released Status in click source package in Yakkety: Fix Released Status in click source package in Zesty: Fix Released Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
This bug was fixed in the package click - 0.4.46+17.04.20170607.3-0ubuntu1 --- click (0.4.46+17.04.20170607.3-0ubuntu1) zesty; urgency=medium * Rename the python package this installs from click to click_package. (LP: #1693226) * Use the correct overlayfs module name for the chroot configuration. (LP: #1696402) -- Sergio SchvezovWed, 07 Jun 2017 18:53:16 + ** Changed in: click (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: Fix Released Status in click source package in Yakkety: Fix Released Status in click source package in Zesty: Fix Released Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
This bug was fixed in the package click - 0.4.46+16.10.20170607.3-0ubuntu1 --- click (0.4.46+16.10.20170607.3-0ubuntu1) yakkety; urgency=medium * Rename the python package this installs from click to click_package. (LP: #1693226) * Use the correct overlayfs module name for the chroot configuration. (LP: #1696402) -- Sergio SchvezovWed, 07 Jun 2017 18:53:16 + ** Changed in: click (Ubuntu Yakkety) Status: Fix Committed => Fix Released ** Changed in: click (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: Fix Released Status in click source package in Yakkety: Fix Released Status in click source package in Zesty: Fix Released Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
This bug was fixed in the package click - 0.4.43+16.04.20170613-0ubuntu1 --- click (0.4.43+16.04.20170613-0ubuntu1) xenial; urgency=medium * Rename the python package this installs from click to click_package. (LP: #1693226) -- Kyle FazzariTue, 13 Jun 2017 17:14:46 + -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: Fix Released Status in click source package in Yakkety: Fix Released Status in click source package in Zesty: Fix Released Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
We tested this in xenial, yakkety and zesty proposed, together with snapcraft for bug #1692102. No issues found with the rename of the package, and now snapcraft can be updated without problems. I've just marked this as verified. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: Fix Committed Status in click source package in Yakkety: Fix Committed Status in click source package in Zesty: Fix Committed Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
On re-evaluation, I have decided to accept the xenial upload - mostly because click is anyway a deprecated technology. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: Fix Committed Status in click source package in Yakkety: Fix Committed Status in click source package in Zesty: Fix Committed Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
Hello Sergio, or anyone else affected, Accepted click into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/click/0.4.46+17.04.20170607.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: click (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed ** Changed in: click (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: Fix Committed Status in click source package in Yakkety: Fix Committed Status in click source package in Zesty: Fix Committed Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
I ran the test cases documented in this bug using a xenial container and the bileto PPA: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/2812 Everything works as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: New Status in click source package in Yakkety: New Status in click source package in Zesty: New Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
** Branch linked: lp:~ci-train-bot/click/click-ubuntu-xenial-2812 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: New Status in click source package in Yakkety: New Status in click source package in Zesty: New Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
** Branch linked: lp:~kyrofa/click/xenial-package-rename -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: New Status in click source package in Yakkety: New Status in click source package in Zesty: New Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
** Also affects: click (Ubuntu Artful) Importance: Undecided Assignee: Sergio Schvezov (sergiusens) Status: Fix Released ** Also affects: click (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: New Status in click source package in Yakkety: New Status in click source package in Zesty: New Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
I sponsored the click packages from https://launchpad.net/~sergiusens/+archive/ubuntu/ppa/+packages?field.name_filter=click_filter=published_filter= which fix this for Yakkety and Zesty. They are in the queue awaiting SRU team review. I did not upload the Xenial package because it is an upgrade from 0.4.43 to 0.4.46 and I think that bears some further discussion. ** Also affects: click (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: click (Ubuntu Yakkety) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Yakkety: New Status in click source package in Zesty: New Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
I ran the test cases documented in this bug using an artful lxc container. Everything works as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
This bug was fixed in the package click - 0.4.46+17.10.20170607.3-0ubuntu1 --- click (0.4.46+17.10.20170607.3-0ubuntu1) artful; urgency=medium * Rename the python package this installs from click to click_package. (LP: #1693226) * Use the correct overlayfs module name for the chroot configuration. (LP: #1696402) -- Sergio SchvezovWed, 07 Jun 2017 18:53:16 + ** Changed in: click (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
I did some preemptive testing with ppa:ci-train-ppa-service/ubuntu/2790 (https://bileto.ubuntu.com/#/ticket/2790) which should land in artful: root@artful:/# dpkg -l snapcraft Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii snapcraft 2.30.1+17.10 all easily craft snaps root@artful:/# dpkg -l click Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii click 0.4.46+17.10 amd64Click packages root@artful:/# snapcraft --help Usage: snapcraft [OPTIONS] COMMAND [ARGS]... Snapcraft is a delightful packaging tool. Options: -d, --debug --help Show this message and exit. Commands: buildBuild artifacts defined for a part. cleanRemove content - cleans downloads, builds or... cleanbuild Create a snap using a clean environment... closeClose for . create-key Create a key to sign assertions. define Shows the definition for the cloud part. enable-ciEnable continuous-integration systems to... gatedGet the list of snaps and revisions gating a... help Obtain help for a certain plugin or topic. init Initialize a snapcraft project. list-keysList the keys available to sign assertions. list-plugins List the available plugins that handle... list-registered List snap names registered or shared with... list-revisions Get the history on the store for . loginAuthenticate session against Ubuntu One SSO. logout Clear session credentials. primeFinal copy and preparation for the snap. pull Download or retrieve artifacts defined for a... push Push to the store. register Register with the store. register-key Register a key with the store to sign... release Release on to the... search Searches the remote parts cache for matching... sign-build Sign a built snap file and assert it using... snap Create a snap. stageStage the part's built artifacts into the... status Get the status on the store for . tour Setup the snapcraft examples used in the... update Updates the parts listing from the cloud. validate Validate a gated snap. root@artful:/# click --help Usage: click COMMAND [options] Commands are as follows ('click COMMAND --help' for more): build Build a Click package. buildsource Build a Click source package. chrootUse and manage a Click chroot. contents Show the file-list contents of a Click package file. framework List available frameworks. hook Install or remove a Click system hook. info Show manifest information for a Click package. install Install a Click package (low-level; consider pkcon instead). list List installed Click packages. pkgdirPrint the directory where a Click package is unpacked. register Register an installed Click package for a user. unregisterUnregister an installed Click package for a user. verifyVerify a Click package. Options: -h, --help show this help message and exit ** Description changed: - click the optparser cannot be installed in parallel with this package. - Please break the conflict so they can be co-installable. + [Impact] + + * python-click and python-click-package conflict as they use the same +python package for its implementation. + + * Since python-click-package is an implementation detail for the click +package and python3-click is a package meant to be used in other +implementations it makes sense to break the conflict by moving the +package name for python-click-package to a different name + + * snapcraft has moved from docopt to python3-click, users that have click +installed don't have an upgrade path.his bug. + + [Test Case] + + * Where snapcraft 2.30 is present: + +- apt install click +- Install snapcraft << 2.30 +- update to snapcraft >= 2.30 +- the upgrade should not be held on any package. +- click and snapcraft commands should work. + + * Install python3-click and click should be possible. The click command + should keep working and python3 -c 'from click import group' shall work. + + + [Regression
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
** Branch linked: lp:~ci-train-bot/click/click-ubuntu-artful-2790 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: New Bug description: click the optparser cannot be installed in parallel with this package. Please break the conflict so they can be co-installable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp