I thought I'd share a blow-by-blow account this time. Ubuntu Server Triage helper Symbols: '*': ubuntu-server is directly subscribed '+': last bug activity is ours Please be patient, this can take a few minutes... Team 'ubuntu-server' currently subscribed to 313 bugs --- Bugs last updated between 2021-10-29 (Friday) and 2021-10-31 (Sunday) inclusive Date range identified as: "Monday triage"
> LP: #1452089 - +(Incomplete) [numactl] - package libnuma1:amd64 > 2.0.9~rc5-1ubuntu2 failed to install… > LP: #1946862 - +(Incomplete) [jq] - Merge jq from Debian > unstable for 22.04 > LP: #1946871 - +(Incomplete) [libvirt-python] - Merge libvirt-python > from Debian unstable for 22.04 > LP: #1946879 - +(In Progress) [numactl] - Merge numactl from > Debian unstable for 22.04 > LP: #1948880 - *+(Triaged) [libvirt] - libvirt should not use > user tss for swtpm These were all correct triaging activity by previous triagers, and so there was no further triage to do. I verified them this time, but usually I just ignore the ones marked '+' as they have by definition had all their activity seen by a triager. > LP: #1941842 - (Expired) [mysql-8.0] - package > mysql-server-8.0 8.0.26-0ubuntu0.20.04.2 failed to … Correctly expired. Nothing to do unless the reporter provides more information, as has already been explained by the previous triager. > LP: #1942048 - (Expired) [rpcbind] - package rpcbind > 0.2.3-0.2ubuntu0.16.04.1 failed to install/… Correctly expired. Nothing to do unless the reporter provides more information, as has already been explained by the previous triager. > LP: #1949266 - (New) [openssh] - package openssh-server > 1:8.2p1-4ubuntu0.3 failed to install… I'm so certain this is a user who has broken their system by deleting things that I used my "not a bug - invalid" template and set it straight to Invalid, but also subscribed myself just in case as I do when I do this. > LP: #1949287 - (New) [blinker] - Sync blinker > 1.4+dfsg1-0.4 (main) from Debian unstable (mai… This is a sync request from a community member. I'm treating as a "patch on a plate" and so tagged it server-next. It is also correctly in the sponsorship queue. I did wonder what "blinker" was and why it is in main with a server team subscription. Looks like it comes in via python3-oauthlib which is used by launchpadlib and cloud-init amongst others. I might look into reviewing and sponsoring this as it shouldn't take long, but for right now, triage stops at "server-next". > LP: #1949288 - (New) [mysql-8.0] - package > mysql-server-8.0 8.0.27-0ubuntu0.20.04.1 failed to … /etc/mysql/my.cnf appears to have recursive symlinks. I used my "local misconfiguration -> Incomplete" template and renamed the bug. > LP: #1949298 - (New) [apache2] - package apache2 > 2.4.41-4ubuntu3.8 failed to install/upgrade… The reporter admits themselves that they broke their system and how, so I used my "not a bug - invalid" template, subscribed myself, but otherwise left it. This is an example of where apport just assumes that a maintainer script failure is a bug and encourages the user to file a bug report, but this assumption is wrong for server packages. It's damaging because the user might now expect to receive help, but they're far better off getting help from actual community support sources (where there are many willing helpers) instead of bug triagers (where there are very few helpers with limited time). My template hopefully sends them somewhere where they can get better help. --- Bugs tagged "server-next" and subscribed "ubuntu-server" and not touched in 60 days Found 0 bugs --- Bugs subscribed to ubuntu-server and not touched in 180 days Found 3 bugs > LP: #1868127 - (Fix Committed) [openvpn] - [SRU] OpenVPN will not > reload due to misconfigured .service… I went down a rabbit hole on this one. The bug was never marked Fix Released for Focal because it was removed from -proposed but errantly never got copied to -updates. However the subsequent .2 security update included the patch, and the current .3 security update still contains the patch, so it is actually fixed in Focal and so I marked it Fix Released with a comment. LP: #1913851 - (Triaged) [samba] - pam_winbind should reject disabled users Previously triaged by a team member. It's a valid bug but requires upstream work. It was in the backlog, but I don't think we'd ever do it in Ubuntu even with infinite time as it is currently intended upstream behaviour, so I removed it from the backlog. My thinking is that there isn't anything actionable for Ubuntu here. LP: #1908638 - (Triaged) [libpam-mount] - mounts to polydirs not working Previously triaged by a team member. I have a similar opinion on this one. It's valid, but is an upstream behaviour issue, and I'm not sure we'd agree to carry an Ubuntu delta even if we spent time on this low priority issue. Therefore it's not appropriate for our backlog, so I removed it. Again, I don't think there's any action to be taken in Ubuntu here. Robie
signature.asc
Description: PGP signature
-- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
