Public bug reported: Hi, we know that the new python-django python-django | 2:3.2.12-2 | jammy-proposed | source is blocked by mini-buildd
The problem is that in mini-buildd in focal someone went ahead and since then we are on the bleeding edge track. mini-buildd | 1.0.49 | unstable | source mini-buildd | 1.9.98 | buildd-experimental | source, all mini-buildd | 1.9.98 | experimental | source, all On Ubuntu we are kind of stuck in between now, 1.0.49 seems as if it would be the right thing. And checks with the people involved two years ago it sounded like it would be ok to consider going back (to something like 1.1.19+really1.0.49ubuntu1) We tried to have a look at 1.9.x still (thanks Lena) just to know how it would be. https://launchpad.net/~lvoytek/+archive/ubuntu/mini-buildd-update-to-newest Trying the builds from there fails me for various reasons: root@j-buildd:~# systemctl status mini-buildd.service × mini-buildd.service - custom Debian build daemon Loaded: loaded (/lib/systemd/system/mini-buildd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2022-03-21 06:25:18 UTC; 19min ago Docs: man:mini-buildd(8) Process: 8084 ExecStart=/usr/sbin/mini-buildd $MINI_BUILDD_OPTIONS (code=exited, status=1/FAILURE) Main PID: 8084 (code=exited, status=1/FAILURE) Mar 21 06:25:17 j-buildd I[8084]: Adding route: /static/events.attach -> <mini_buildd.httpd.Events object at 0x7fb4c09af160> [mini_buildd.httpd:168, thread=MainThread] Mar 21 06:25:17 j-buildd I[8084]: Site starting on 8066 [mini_buildd.httpd:81, thread=MainThread] Mar 21 06:25:17 j-buildd I[8084]: Starting factory <mini_buildd.httpd.Site object at 0x7fb4c09aebc0> [mini_buildd.httpd:81, thread=MainThread] Mar 21 06:25:18 j-buildd I[8084]: (TCP Port 8066 Closed) [mini_buildd.httpd:81, thread=httpd] Mar 21 06:25:18 j-buildd I[8084]: Stopping factory <mini_buildd.httpd.Site object at 0x7fb4c09aebc0> [mini_buildd.httpd:81, thread=httpd] Mar 21 06:25:18 j-buildd I[8084]: Main loop terminated. [mini_buildd.httpd:81, thread=httpd] Mar 21 06:25:18 j-buildd D[8084]: <HttpD(httpd, started 140414300833344)>: FINISHED [mini_buildd.httpd:1009, thread=httpd] Mar 21 06:25:18 j-buildd E[8084]: mini-buildd failed (try '-vv' to debug): {'email_address': ['Enter a valid email address.']} [mini_buildd.cli:137, thread=MainThread] Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 581, in get_or_create return self.get(**kwargs), False File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 435, in get raise self.model.DoesNotExist( mini_buildd.models.daemon.Daemon.DoesNotExist: Daemon matching query does not exist. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mini_buildd/cli.py", line 179, in run self.runcli() File "/usr/sbin/mini-buildd", line 230, in runcli mini_buildd.misc.attempt(mini_buildd.get_daemon().mbd_start) File "/usr/lib/python3/dist-packages/mini_buildd/__init__.py", line 54, in get_daemon return Daemon() File "/usr/lib/python3/dist-packages/mini_buildd/misc.py", line 157, in __call__ cls.__INSTANCES[cls] = super(Singleton, cls).__call__(*args, **kwargs) File "/usr/lib/python3/dist-packages/mini_buildd/daemon.py", line 90, in __init__ self.builder = mini_buildd.builder.Builder(self.model.build_queue_size) # TODO: adapt max parallel builds on_model_change ? File "/usr/lib/python3/dist-packages/mini_buildd/daemon.py", line 84, in model return mini_buildd.models.daemon.get() File "/usr/lib/python3/dist-packages/mini_buildd/models/daemon.py", line 355, in get model, created = mini_buildd.models.daemon.Daemon.objects.get_or_create(id=1, defaults={"ftpd_bind": mini_buildd.config.default_ftp_endpoint()}) File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 588, in get_or_create return self.create(**params), True File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 453, in create obj.save(force_insert=True, using=self.db) File "/usr/lib/python3/dist-packages/mini_buildd/models/daemon.py", line 172, in save super().save(*args, **kwargs) File "/usr/lib/python3/dist-packages/mini_buildd/models/base.py", line 146, in save self.full_clean() File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 1251, in full_clean raise ValidationError(errors) django.core.exceptions.ValidationError: {'email_address': ['Enter a valid email address.']} Mar 21 06:25:18 j-buildd systemd[1]: mini-buildd.service: Main process exited, code=exited, status=1/FAILURE Mar 21 06:25:18 j-buildd systemd[1]: mini-buildd.service: Failed with result 'exit-code'. In comparison the old combination of python-django | 2:2.2.24-1ubuntu1 | jammy | source mini-buildd | 1.1.19 | jammy/universe | source, all works and gets up a running mini-buildd right after install with a config UI at localhost:8066. P.S. In Debian-sid as of now dependency issues block installation of 1.0.49 mini-buildd : Depends: python:any Depends: python-mini-buildd (= 1.0.41) but it is not going to be installed Depends: python-daemon (>= 2.0.5) but it is not installable Depends: python-cherrypy3 but it is not installable Depends: python-pyftpdlib (>= 1.2.0) but it is not installable Recommends: python-apt but it is not installable P.P.S. 1.9.97 is the latest from git, but in the Debian archive there is also 1.9.98, but I do not think we should go this way. ** Affects: mini-buildd (Ubuntu) Importance: Undecided Status: New -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
