** Changed in: bash (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1997093
Title:
bash 5.2 regression too-aggressive
https://launchpad.net/ubuntu/+source/bash/5.2.15-2ubuntu1
** Changed in: bash (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://lists.gnu.org/archive/html/bug-bash/2022-12/msg00050.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1997093
Title:
bash 5.2 regression too-aggressive optimizing
https://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel=94d25f57f124a9b2268a3af0a0915871032f426e
** Summary changed:
- bash 5.2 regression in optimize_connection_fork
+ bash 5.2 regression too-aggressive optimizing of forks in an `eval' command
inside a (command) subshell
--
You received
https://lists.gnu.org/archive/html/bug-bash/2022-11/msg00078.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1997093
Title:
bash 5.2 regression in
** Description changed:
For some reason, when the test is executed using bash 5.2 on Debian
- experimental/Kinetic/Lunar, the `eval` [0] in the `counter_delta_`
- function misinterprets successful execution of commands [1], leading to
- a false negative for the 'ovn-controller incremental
Public bug reported:
For some reason, when the test is executed using bash 5.2 on Debian
experimental/Kinetic/Lunar, the `eval` [0] in the `counter_delta_`
function misinterprets successful execution of commands [1], leading to
a false negative for the 'ovn-controller incremental processing' test
** Patch added: "rsyslog-zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4944790/+files/rsyslog-zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Marking Won't fix for Yakkety as it is EOL.
Removing sts-sru-needed tag until patches are ready.
** Changed in: rsyslog (Ubuntu Yakkety)
Status: New => Won't Fix
** Tags removed: sts-sru-needed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@cyphermox Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1668639
Title:
Add a trigger to reload rsyslog when a new configuration file is
dropped in
@slashd Thank you! I will start work on debdiffs for the SRU's ASAP.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1668639
Title:
Add a trigger to reload rsyslog when a
@andreserl
There are severe security implications of doing 2) from now until all
future, and unfortunately I have seen that this is being done in the
wild.
I would be much more comfortable by actually finding the root cause of
the issue at hand and fixing that.
This is what I am currently
This problem has surfaced again with recent MAAS Ubuntu images. One
report in bug 1701297. I have information about at least two other end
users hit by the problem.
Adding a workaround by setting apparmor=0 kernel parameter in MAAS 2.2
will not help users that are running previous versions.
** Patch removed: "rsysog-artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4903402/+files/rsysog-artful.debdiff
** Patch added: "rsysog-artful.debdiff"
** Patch added: "rsysog-artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4903402/+files/rsysog-artful.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
** Patch removed: "rsyslog-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900262/+files/rsyslog-trusty.debdiff
** Patch removed: "rsyslog-xenial.debdiff"
** Patch added: "rsyslog-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4901471/+files/rsyslog-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
** Patch removed: "rsyslog-aa.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900261/+files/rsyslog-aa.debdiff
** Patch added: "rsyslog-artful.debdiff"
** Patch added: "rsyslog-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900273/+files/rsyslog-xenial.debdiff
** Tags removed: sts-sponsor
** Tags added: sts-sru-needed
--
You received this bug notification because you are a member of Ubuntu
Touch
** Patch added: "rsyslog-zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900271/+files/rsyslog-zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
** Patch added: "rsyslog-yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900272/+files/rsyslog-yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in
** Patch added: "rsyslog-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900262/+files/rsyslog-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
** Patch removed: "rsyslog-zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4842263/+files/rsyslog-zesty.debdiff
** Patch removed: "rsyslog-yakkety.debdiff"
Thank you back for swift action on this, making us all look good :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1676380
Title:
Update to cups-daemon 2.1.3-4ubuntu0.2
** Summary changed:
- package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
+ [still occurs with package version 2.1.3-4ubuntu0.2] package cups-daemon
2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned
The package that was just SRU'ed caused this very error. Apport-info in
LP: #1676380
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package cups-daemon
Public bug reported:
Even though LP: #1642966 states that this is now fixed, the very update
that was SRU'ed in that bug-report caused this error just now.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.10.0-13.15~16.04.2-generic
** Patch removed: "rsyslog-zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4842248/+files/rsyslog-zesty.debdiff
** Patch added: "rsyslog-zesty.debdiff"
** Patch added: "rsyslog-zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4842248/+files/rsyslog-zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
** Patch added: "rsyslog-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4828298/+files/rsyslog-trusty.debdiff
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "rsyslog-yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4828296/+files/rsyslog-yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in
** Patch added: "rsyslog-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4828297/+files/rsyslog-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
** Description changed:
- rsyslog should reload its configuration when other packages drop
- configuration in /etc/rsyslog.d
+ [Impact]
+ Servers or cloud instances will not log important messages after initial
deployment. Manual reboot or restart of services is necessary to get expected
Public bug reported:
rsyslog should reload its configuration when other packages drop
configuration in /etc/rsyslog.d
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337
https://anonscm.debian.org/cgit/collab-
maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f
**
34 matches
Mail list logo
