[15:26] <Laibsch> Am I correct to think that at least in theory, packages python3-yaml and python-is-python2 should be co-installable and that it's a bug if they aren't?
[15:26] <Laibsch> bug 1958720
[15:30] <tumbleweed> Laibsch: jammy doesn't have a python-is-python2
[15:30] <tumbleweed> also the bug doesn't say *why* they aren't co-installable
[15:31] <Laibsch> Indeed, no such package
[15:31] <Laibsch> well, I am still looking into the exact chain of dependencies making them uninstallable
[15:32] <Laibsch> I came here to confirm if maybe this isn't expected behavious and the package having been dropped kind of hints at that
[15:33] <tumbleweed> python3-yaml has some extra breaks in it, to help upgrades: https://tracker.debian.org/news/1243453/accepted-pyyaml-531-5-source-into-unstable/
[15:33] <Laibsch> The changelog for what-is-python states that python-is-python2 was dropped, but not the reason for it.  As such, the what-is-python source package becomes kind of unnecessary, it appears to me.
[15:34] <tumbleweed> if you want a /usr/bin/python you still need python-is-python3
[15:35] <tumbleweed> the reason it was dropped, is I assume to make it clear that 2.7 isn't supported any more
[15:35] <Laibsch> I still have some old python2 packages installed that are no longer part of official Debian/Ubuntu and as such, I could see an argument be made that my installation is unsupported.  Then again, I'm wondering why from a logical POV python-is-python2 from focal has to be removed rather than keeping it as an obsolete package when going to jammy.
[15:36] <Laibsch> removed from the machine when going focal2jammy
[15:37] <Laibsch> tumbleweed: that would sound reasonable if there weren't a python2 package in jammy IMVHO
[15:37] <tumbleweed> that's the provides on python-is-python2 clashing with the Breaks on python3-yaml
[15:39] <JackFrost> python-yaml is a source of pain for people stuck with py2 stuff, yeah. :/
[15:40] <tumbleweed> it wasn't intentional that those Breaks would break python-is-python2
[15:52] <Laibsch> I figured out the path of breakage: 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 since there is no path to upgrade beyond 2.7.18 python-is-python2 will be forcefully removed when going to jammy.
[15:53] <tumbleweed> we could remove those breaks in jammy
[15:53] <tumbleweed> I just removed them in git
[15:54] <Laibsch> did you put them in previously?
[15:55] <Laibsch> I just assume they were put in there for a reason
[15:59] <tumbleweed> the reason is described in the changelog
[16:00] <Laibsch> I just now found the commit and saw the "no longer needed" comment in the changelog so I will assume all is good and taken care of.  Thank you.  Maybe you want to reference LP: 1958720 in the changelog, tumbleweed?
[16:01] <Laibsch> I was looking in launchpad git, not Debian.  Do you expect pyyaml version 6 to make it to jammy as well?
[16:01] <tumbleweed> it'll take a while before that hits jammy (it's the new version in experimental
[16:01] <tumbleweed> so yeah, if you want to fix this in jammy now, do an upload there
[16:02] <Laibsch> OK, I will prepare a debdiff
[16:02] <Laibsch> Thanks
[16:22] <Laibsch> tumbleweed: I prepared https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+attachment/5556392/+files/1958720.debdiff and added the sponsors team to the ticket.
[16:25] <tumbleweed> I see those breaks missed focal, maybe it does make sense to keep that until the next Ubuntu LTS, I don't know
[16:25] <tumbleweed> certainly debian doesn't need them any more
[16:36] <Laibsch> Maybe it's best to introduce those Breaks to focal via an SRU, just to be sure?
[16:37] <Laibsch> and upload the debdiff to jammy as proposed
[16:45] <tumbleweed> too late for that, I think. But it could also probably be handled in the upgrader. Not really my realm of expertise
[17:43] <Laibsch> tumbleweed: same issue with python3-six (bug ticket updated)
[20:48] <ItzSwirlz> am i the only one playng with germinate (configuring ubuntu cinnamon seeds) and getting git+ssh://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ not found?