Based on case history, to fully address this to all still supported
Ubuntu releases:
autofs | 5.1.2-1ubuntu3 | bionic |
autofs | 5.1.2-1ubuntu3.1 | bionic-updates |
autofs | 5.1.2-4ubuntu2 | disco |
autofs | 5.1.5-1ubuntu1 | eoan|
autofs | 5.1.6-2
** Also affects: autofs (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: autofs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: autofs (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: autofs (Ubuntu Eoan)
Status: New =>
Simon,
Could you please help identifying the current status of this bug ? Your
original merge requests were postponed to the next SRU for rsyslog in
Bionic, Disco and Eoan, correct ?
During verification time you discovered the difference between "bin" and
"sbin" for the apparmor rule, is that it
Marking as Fix Released for Disco:
+rsyslog (8.32.0-1ubuntu7.1) disco; urgency=medium
+
+ [ Simon Deziel ]
+ * d/usr.sbin.rsyslogd: allow reading/mmap'ing rsyslog binary
+This is required for usage inside containers (LP: #1827253)
+
+ -- Christian Ehrhardt Mon, 14 Oct 2019
08:53:03 +0200
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
user@box:~$ date
Mon Apr 13 17:11:35 EDT 2020
"box" machine -> Apr 13 17:11 EDT
user@box:~$ ./reset-power-consumption-meter
+ sudo ipmi-oem dell reset-power-consumption-data
** Description changed:
This affects focal which is at 9.16.1 at the moment.
Upstream MP: https://gitlab.isc.org/isc-
projects/bind9/-/merge_requests/3343
- Upstream released 9.16.2 with the fix, and of course other changes.
+ Upstream released 9.16.2[1] with the fix, and of course
Public bug reported:
This affects focal which is at 9.16.1 at the moment.
Upstream MP: https://gitlab.isc.org/isc-
projects/bind9/-/merge_requests/3343
Upstream released 9.16.2 with the fix, and of course other changes.
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
