Re: Details of what is happening with python3.8 in Ubuntu?

Hey Michael, thanks for the reply.

Le 23/10/2019 à 01:01, Michael Hudson-Doyle a écrit :

- Could someone explain why those .install tricks are needed exactly?

It's because the "abi tag" for python c extensions has changed in a way that makes it a bit annoying / impossible to write a glob that matches 3.7 and 3.8 release build extensions and not the debug extensions.

 

Couldn't the issue be solved in the python packaging tools instead?

Yes, probably.

Ok, thanks, that's useful information about the naming/matching. If it could probably be fixed in the tooling shouldn't we have looked at that first rather than dumping a stack of delta in the archive which is going to bite us back later by having to deal with manually reviewing/merging those packages later?

I've made a bug report for cracklib2 now.*

Thanks!

- Is that a transition we are under pressure to get through?

Well we want it to complete before opening the archive and I assume people want the archive to open...

Ok, I didn't know that it needed to be complete before archive opening since we have proposed and I though it could be handle as a normal transition and blocked in there still after opening.

 

Should we
maybe take the time to document what's going on

Well there was this mail: https://www.mail-archive.com/ubuntu-devel@lists.ubuntu.com/msg09144.html

 

And there is a transition tracker: https://people.canonical.com/~ubuntu-archive/transitions/html/python3.8-add.html (not sure this has been advertised but it's not hard to find).

Right, the first one is the one I referred to. I was more looking to an email that explained e.g the technical of e.g the abi/naming change and the problem it creates on .install matching and the recommended solution. I think it's important to share knowledge in such cases so other developers understand what is being done and why and then can be helping.

Maybe roping in more people would help, maybe not. The plan was for Matthias and I to work on this more or less full time and just crank through it.

Well, cranking through it is only one side of the story. Then we need to maintain those changes. Do you&Mathias plan to keep on maintaining those packages you touched, doing Debian merges when needed, etc? If not and the expectation is that the team 'owning' the packages deal with the maintainance then the changes need to be understood by the people who are going to maintain them...

Cheers,
Sebastien Bacher