[Bug 1693226] Re: Break the conflicts with click the optparser

[Łukasz Zemczak]

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
Foundations Bugs, 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