Marking rsyslog invalid, since it's a bug in gzip. zlib might have the same problem, but we don't have a confirmation yet, so leaving that as incomplete. And gzip is confirmed, I rebuilt it with a patch in [1], and, with that build, rsyslog also built fine (test that was previously failing, now passes).
1. https://launchpad.net/~ahasenack/+archive/ubuntu/rsyslog-apparmor ** Changed in: gzip (Ubuntu Noble) Status: New => Confirmed ** Changed in: gzip (Ubuntu Oracular) Status: New => Confirmed ** Changed in: rsyslog (Ubuntu Noble) Status: Confirmed => Invalid ** Changed in: rsyslog (Ubuntu Oracular) Status: Confirmed => Invalid ** Changed in: rsyslog (Ubuntu Plucky) Status: Confirmed => Invalid ** Changed in: gzip (Ubuntu Noble) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: gzip (Ubuntu Oracular) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: gzip (Ubuntu Plucky) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083700 Title: rsyslog FTBFS (s390x only) against zlib 1:1.3.dfsg+really1.3.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2083700/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
