Triage/Migration report of the day

[Christian Ehrhardt]

Hi,
as usual monday triage efforts are a bit bigger and I thought I try
letting everyone know what was going on, especially in regard to
proposed migration blockers which we had a few.

Triage
- 20 bugs to triage, mostly due to
  - our friday triage work
  - some teams doing mass triage
  - Rafael's massive set of bugs related to simple streams
- 2 new entries added to the workqueues, but both actively worked on already

Proposed migration
- libvirt test broken by new systemd 243
  Worth to be aware of new systemd coming for Eoan in general (bug 1843755)
  => https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844879
  Debugged the case and engaged both involved upstreams.
  All discussion reachable from the bug.

- resource-agents blocks new glibc
  Test output of good/bad is exactly the same
  => Retriggered which resolved the case.

- python-django had a security update, but blocks on
python-django-gravatar2 autopkgtest
  Reason: py2 was removed, but the test still wants to test it.
  Reported a bug to Debian and Launchpad.
  https://bugs.launchpad.net/ubuntu/+source/python-django-gravatar2/+bug/1844999
  Uploaded fix (trivial and no one else around to review atm).
  Fixed tests worked for its own migration, the one for the new
python-django are triggered

- Same as gravatar but for django-ranged-response
  Same actions taken (Debian + LP bug, debdiff and upload)
  https://bugs.launchpad.net/debian/+source/django-ranged-response/+bug/1845002
  Since I found two of those in one day, there could be more keep your eyes open
  Fixed tests worked for its own migration, the one for the new
python-django are triggered

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd