© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Thanks for the fix, and the explanations about the process exemption.
Ironically, since the exemption exists and is clearly documented (yay!), it may lead to us being *more* likely to use the upstream packages (since the exemption means we now know that we have to put them on hold and only pull them in after we've tested them, and that's slightly easier with third-party packages.) I know it's not defined this way, but from our perspective, non-current LTS means "if something changes at all, someone thought it was pretty important". So we'd be counted in the "if we wanted a current docker, we'd be running a current ubuntu for it" camp. (I do understand that docker is specifically distinct - that some users may want a new docker to run new images on an old ubuntu - and now that I know about it, I'm not objecting to the policy.)
To be entirely fair, I will admit that it wouldn't have even come up if the upgrade hadn't broken buildkit - it would have just been "oh, that's a pleasant surprise" and we wouldn't have given it much further thought (I certainly wouldn't have found this thread.) On top of that, it looks like the missing packages are percolating through the system rapidly and we might just be able to sneak docker-buildx into our developer-deps before too many people get caught by it.
Thanks for straightening this out and being transparent about it!