[09:22] <slyon> tjaalton: Hey! I'm still pondering about how we can get the migration of all the packages blocked by 389-ds-base moving.. Steve suggested a downgrade (i.e. delete what is in -proposed) https://code.launchpad.net/~slyon/britney/+git/hints-ubuntu/+merge/396858 What do you think about this?
[09:33] <tjaalton> slyon: one option would be to revert the breaking commit for now
[09:33] <tjaalton> if that works
[09:33] <tjaalton> or downgrade and wait for the upstream fix
[09:33] <tjaalton> probably best to do that
[09:36] <slyon> well.. reverting the breaking commit works for dogtag-pki, but I don't know about the side-effects, as it removes quite some functionality. So I'm in favor of removing it from -proposed, as the version in -release still seems to be OK
[09:37] <tjaalton> yeah
[09:37] <slyon> Okay. I'll try to get in touch with #ubuntu-release about the removal then
[13:13] <\sh> Happy New Year Everyone. Short question: Is there any documentation what will happen with Python 3.6.x (default for 18.04 LTS) when Py3.6 is going EOL at the end of 2021? Didn't find anything official on the Ubuntu Interwebs (and no using backports is not an option, and an upgrade to 20.04 is right not an option as well)
[13:15] <rbasak> AIUI, all packages in Ubuntu EOL when the release EOLs, regardless of upstream EOL schedules. Sometimes we might bump versions in stable releases for practicality (eg. Firefox), but I don't believe there are any plans for that in Python. So I don't think there's any documentation or announcement to write? What are you expecting?
[13:16] <rbasak> IOW, I believe the schedule documented at https://wiki.ubuntu.com/Releases holds for Python in 18.04, the same as it does for all other packages in 18.04.
[13:18] <\sh> Depending on the impact (no upstream security updates etc. for 3.6) an upgrade to 3.8 (even when this would be an exception to the normal lifecycle, but we did do that in the past with important software stacks like openssl).
[13:19] <rbasak> I think it's very unlikely we would bump the Python version in 18.04 from 3.6 to 3.8.
[13:20] <rbasak> There would have to be a significant and specific security issue for that I think, and more likely any fix would just be backported.
[13:21] <rbasak> I seriously doubt it would be done just "on principle" because 3.6 EOLs upstream, if that's what you're thinking.
[13:25] <\sh> I am just trying to find some official answers to this issue. If Canonical is taking over the maintainer role for this source, that's more than Ok, but looking for something official in this particular case. But I think I already got my answer :) Thanks
[13:27] <rbasak> Note that I cannot speak for Canonical on your question, and I am not speaking for Ubuntu either.
[13:27] <rbasak> As I say though, I don't think there's a statement that can be made here, as what I expect is the status quo.
[13:28] <tjaalton> slyon: can you test https://github.com/389ds/389-ds-base/pull/4573 ?
[13:31] <cjwatson> Yeah, trying to QA a complete minor version bump of Python in a stable Ubuntu release seems borderline intractable.  All sorts of stuff would break.
[13:34] <\sh> cjwatson: Good to see old known ppl are still here :) So I would not assume something wrong that Ubuntu is taking over the maintainer role of the Py3.6 source till 18.04 EoL, which was my initial assumption
[13:35] <slyon> tjaalton: Yes. I will built it in a PPA and run an autopkgtest against it
[13:36] <tjaalton> much thanks
[13:36] <cjwatson> \sh: Like rbasak I'm not speaking for either Canonical or Ubuntu here, just saying what seems most plausible
[13:37] <rbasak> \sh: all distributions "take over the maintainer role" for everything they package. There would be nothing special going on here.
[13:38] <rbasak> Some upstreams provide plenty of help, sure. Some don't. In this case, help from this specific upstream will be going away. But that's just another day for us. In Python's case, I expect there will be plenty of community sharing of patches for 3.6 that will help with any stability or security requirements for Ubuntu.
[13:43] <\sh> thanks cjwatson, rbasak got what I needed.
[14:14] <slyon> tjaalton: that seems to PASS (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-slyon-testing/hirsute/s390x/d/dogtag-pki/20210127_140849_b37ed@/log.gz) – testing against 389-ds-base 1.4.4.10-1+ppa2 from https://launchpad.net/~slyon/+archive/ubuntu/testing/+packages
[14:14] <tjaalton> slyon: oh cool