Friday bug triage
Bugs last updated on 2021-07-01 (Thursday) Date range identified as: "Friday triage" Found 16 bugs Whist most of them seem to be under control, the ones worth mentioning are: 1. LP: #1934381 - (New) [postfix] - package postfix 3.5.6-1 failed to install/upgrade: installed postfix package post-installation script subprocess returned error exit status 75 This is related to LP: #1929786. It "looks" like the hostname of the reporter is "saturn" and because of LP: #1929786, two dots are added and then the upgrade/installation problem happens. Since I couldn't reproduce the problem, I asked for more information and subscribed myself. Simultaneously, asked the reporter to forward this to Debian as well. 2. LP: #1934393 - (New) [openldap] - systemd-logind network access is blocked, and breaks remote authentication configurations Whilst Dan and Michael are having a discussion on this, I did not do anything to the bug. Sergio, could you take a look, please? - u -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Merge Opportunities Report - 2021-07-05
New Mergeable Version in Debian Unstable -- high bind9 1:9.16.15-1 1:9.16.8-1ubuntu3.2 low amavisd-new 1:2.11.1-51:2.11.1-4ubuntu1 low checksecurity 2.0.16+nmu2 2.0.16+nmu1ubuntu1 low corosync 3.1.2-1 3.1.0-2ubuntu4 low crmsh 4.2.1-2 4.2.0-4ubuntu1 low fetchmail 6.4.16-3 6.4.16-1ubuntu1 low kerberos-configs 2.6+nmu1 2.6ubuntu1 low mysql-defaults1.0.7 1.0.5ubuntu2 low nginx 1.18.0-6.11.18.0-6ubuntu10 low pmdk 1.10-21.10-1ubuntu1 low spice 0.14.3-2.10.14.3-2ubuntu3 New Version in Experimental -- high tmux 3.2a-13.1c-1 low at3.2.2-1 3.1.23-1.1ubuntu3 low chrony4.1-2 4.1-1ubuntu1 low dpdk 20.11.1-4 20.11.1-1 low haproxy 2.4.1-1 2.2.9-2 low libapache2-mod-perl2 2.0.11-5 2.0.11-4 low libonig 6.9.7.1-1 6.9.6-1.1 low libpcap 1.10.1-1 1.10.0-2 low libtirpc 1.3.2-1 1.3.1-1build1 low mdbtools 0.9.3-1 0.9.2-2ubuntu2 low python-django 2:3.2.5-1 2:2.2.24-1 low rpcbind 1.2.6-1 1.2.5-9 low ruby-defaults 1:2.7.2~exp1 1:2.7+2 low runc 1.0.0+ds1-1 1.0.0~rc95-0ubuntu1 low spamassassin 4.0.0~0.0svn1890446-2 3.4.6-1 low tidy-html52:5.7.45-1~exp1 2:5.6.0-11 low unixodbc 2.3.9-1 2.3.6-0.1build1 low virglrenderer 0.9.1-1~exp1 0.8.2-5 New Syncs -- New Upstream not in Debian -- high bcache-tools UNKNOWN 1.0.8-4ubuntu1 high procmail UNKNOWN 3.22-26 (Low priority upstream releases skipped) high == Packages seeded for Ubuntu-Server low == Non-seeded packages Server team is subscribed to Merges last authored or uploaded by Server team member or alumnus (via Merge-o-Matic) -- aptdaemon Marc Deslauriers accountsservice Marc Deslauriers python-os-service-types Sahid Orentino FerdjaouiJames Page byobu Dustin Kirkland python-decoratorCorey Bryant python-pypowervmCorey Bryant python-os-client-config Corey Bryant python-microversion-parse Corey Bryant python-django-debreach Sahid Orentino FerdjaouiJames Page migrate Corey Bryant neutron-fwaas Corey Bryant networkxCorey Bryant pyroute2Corey Bryant python-debtcollectorChris MacNaughton Corey Bryant python-osprofiler Corey Bryant python-oslo.i18nCorey Bryant python-os-resource-classes Corey Bryant python-pysaml2 Corey Bryant python-oslo.rootwrapCorey Bryant python-oslo.reports Corey Bryant python-blazarclient
Server Bug Triage - Monday 5th of July
Hi, todays Triage presented me 14 bugs to look at. As it is usually the case most of them were already handled and on the way to be resolved. A few needed a bug state update or a helping comment to lead people the right way. One case was interesting and worth sharing: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1930430 This is about an issue in Focals Apache in regard to chain verification through proxy. Athos and Sergio have handled this bug before, now the reporter was so kind to provide a local repro - I think this can now be worked on and I added the server-next tag. One server-next bug was not touched in 60 days: LP: #1913810 - (Confirmed) [openssh]- restart doesn't test for syntax errors @Athos / @Andreas - you discussed on this bug. To me it is not entirely clear if you did you end up with "ok let us just do just restart" (then ideally we'd assign someone, Athos would you handle this case then?). Or did it actually mean "we can't just do restart as it breaks stop" in which case we are stuck waiting for upstream systemd and should drop the server-next tag for now. -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
