Monday Triage 2025-07-07

[Renan Rodrigo Barbosa]

### Bug Triage ###
Found 20 bugs
Quite a few updates on bugs people are already looking at. Then those which
I looked at:
2116034
<https://bugs.launchpad.net/ubuntu/+source/php-league-html-to-markdown/+bug/2116034>,
(php-league-html-to-markdown)
2116035
<https://bugs.launchpad.net/ubuntu/+source/php-lorenzo-pinky/+bug/2116035>,
(php-lorenzo-pinky)
2116037
<https://bugs.launchpad.net/ubuntu/+source/php-tijsverkoyen-css-to-inline-styles/+bug/2116037>,
(php-tijsverkoyen-css-to-inline-styles)
2116038 <https://bugs.launchpad.net/ubuntu/+source/symfony/+bug/2116038>
 (symfony)
Those are packages which have dep8 tests failing because of the libxml2
transition (which affects php8.4). They were open based on the debian bugs,
now open because libxml2 hits experimental. I am taking a look into these,
as we are already seeing this in -proposed.

2115935 <https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2115935> (sssd)
Reporter is getting DENIED by apparmor when authenticating against Active
Directory. I referenced 2109673
<https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2109673> there,
although the logs are different, and show samba getting denied.
As this is not the simplest setup, I asked for more logs or a reproducer.

#### Bugs not touched in 180 days ####
2092715
<https://bugs.launchpad.net/ubuntu/+source/ruby-defaults/+bug/2092715>
 (php-defaults)
Reporter asks for ruby 3.4. It's not in Debian yet, so we wait.

2059859 <https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2059859>
(gdm3)(and
others)
This is already fixed for openssh and pam. Still open for gdm3, and the
desktop team seems to have this on track. Foundations (enr0n) is subscribed.

2071722 <https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/2071722>
 (tftp-hpa)
Still on hold, as we decide on what to do with ftp overall. This is being
tracked in Jira, and probably will be rediscussed for next cycle.

2092779 <https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/2092779>
 (unbound)
Valid bug, slyon asked the reporter if they could send their solution as a
patch, or send bug+patch to the debian maintainer. None of those seem to
have happened. What to do in this case? How to keep traction? Should me (or
anyone) open the debian bug or prepare the patch?

### Discourse Triage ###
Nothing there.

### Documentation Triage ###
Nothing to act on.

### Server Excuses Triage ###
The ruby stack stuck there is being worked on. pcs is the next piece, and
it's in process of being uploaded. Wathcing closely.

[]s
Renan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-server/attachments/20250707/d970524f/attachment.html>