Right now to me it seems we need to choose between pain, pain and more
pain:
- do a python3 transition with mini-buildd 1.0.49
+ that seems to be the reason we had 1.1.19 in Focal, and 1.0.49
isn't ready yet
+ Back in Apr 2021 v2.0 was called 2 weeks away, still not released
today
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937049
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933751
- Do a django 3.2 transition in mini-buildd 1.>0 e.g. 1.9.98
+ due to various dependency and python3 issues this isn't seen in Debian
yet, but would most likely be a problem there as well, yet we can't wait
on that to resolve there
+ And OTOH there are incompatibilities of 1.9.97 with the new django
that I see not fixed anywhere yet
- remove src:mini-buildd + binaries from Jammy to let things migrate and
work on trying to enable it either of the two ways above independently
to the django transition
+ no reverse dependencies
$ reverse-depends --release jammy src:mini-buildd
No reverse dependencies found
Might be worth to talk to the release team about the preferred route
here?
** Bug watch added: Debian Bug tracker #937049
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937049
** Changed in: mini-buildd (Ubuntu)
Assignee: (unassigned) => Lena Voytek (lvoytek)
** Tags added: server-todo
** Also affects: python-django (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-django (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965724
Title:
1.1.19 blocked in proposed, but 1.9.97 fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mini-buildd/+bug/1965724/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
