I've investigated and I don't understand the issue. Has something
changed in the archive?
On a Jammy system I was able to install python2, python2.7, python3-yaml
and python3-six, as well as manually install the python-is-python2
package from Impish. I didn't hit any co-installability problems. The
versions I now have installed are:
python-is-python2 2.7.18-9
python2 2.7.18-3
python2.7 2.7.18-13
python3-six 1.16.0-3
python3-yaml 5.4.1-1
> python3-yaml in jammy breaks on python (<2.7.18). The python-is-
python2 package in focal is version 2.7.17-4 and in impish it is
2.7.18-9 and thus will be forcefully removed when going to jammy.
I don't see how that Breaks is relevant. "python" != "python-is-
python2", so python3-yaml having a breaks on *python* (<< 2.7.18)
doesn't have any direct impact on the python-is-python2 package. And
Jammy ships python2 2.7.18-3 anyway.
> OK, so it's an obsolete package as was pointed out in the original
ticket description #0. I don't see a reason here to intentionally break
users.
Packages not actually shipped in Jammy aren't supported and it's in
general acceptable for packages that _do_ ship to break them. But I
agree with you that there's no need to do so gratuitously. So I tried to
reproduce your use case to better understand what we might be able to do
to accommodate before drawing any conclusions, but I couldn't.
It may be correct to drop the Breaks as Stefano did in your link, but
I'd like to properly understand the implications of that, and what
benefit it might bring, before uploading a delta to Ubuntu.
Please could you provide exact steps to reproduce your scenario in
Jammy, and then change the bug status back to New or Confirmed? Or is it
the case that something has changed in the archive since you reported
this, and no further changes are necessary for your use case to work?
** Changed in: pyyaml (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: six (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1958720
Title:
python3-yaml and python3-six are not co-installable with python-is-
python2 in jammy
Status in pyyaml package in Ubuntu:
Incomplete
Status in six package in Ubuntu:
Incomplete
Bug description:
The packages python3-yaml and python-is-python2 are not co-installable
in jammy and I believe they should be. This currently prevents me
from upgrading one of my machines from focal to jammy.
Further analysis with the help of Stefano Rivera revealed that what-
is-python no longer produces a python-is-python2 package and the
changelog hints at that being intentional. Jammy still has a python2
package, though.
python3-yaml in jammy breaks on python (<2.7.18). The python-is-
python2 package in focal is version 2.7.17-4 and in impish it is
2.7.18-9 and thus will be forcefully removed when going to jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+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
