** Changed in: linux (Ubuntu)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1856871
Title:
i/o error if n
Public bug reported:
I'm reporting this bug to keep track of it, as of today I'm still
collecting informations.
Here's what I have gathered so far:
Release: Xenial/16.04LTS
Openssh version :7.2p2-4ubuntu2.10
Fuzzer tool used:
https://www.synopsys.com/software-integrity/security-testing/fuzz-tes
Potential fix candidate:
https://github.com/openssh/openssh-portable/commit/2adbe1e63bc313d03e8e84e652cc623af8ebb163
** Tags added: seg sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launc
I have produced a test pkg including the potential fix candidate above
for the impacted UA customer to test in their lab.
Unfortunately, I have no access to a reproducer since this fuzzer is
proprietary and need to be purchased.
Meaning, the testing will rely on UA customer end.
- Eric
** Descr
Hello Seth,
So far no production impact has been reported, for now it is only
reproducible using that particular fuzzer on xenial's openssh version.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
h
UA customer test pkg outcome:
"
We ran the Defensics test suite before and after installing the test packages.
We could observe two core dumps before the test package installation.
But after test package installation, core dumps were not generated.
Can you provide this package as the fix?
"
This
** Changed in: openssh (Ubuntu Xenial)
Status: New => In Progress
** Description changed:
+ [Impact]
Here's what has been brought to my attention by a UA customer:
* Release:
Xenial/16.04LTS
* Openssh version:
7.2p2-4ubuntu2.10
* Fuzzer tool used:
https://www.synop
debdiff to go over the ESM process by security team.
Thanks
- Eric
** Patch added: "xenial_lp1930286.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1930286/+attachment/5502934/+files/xenial_lp1930286.debdiff
--
You received this bug notification because you are a member of
** Description changed:
[Impact]
Here's what has been brought to my attention by a UA customer:
* Release:
Xenial/16.04LTS
* Openssh version:
7.2p2-4ubuntu2.10
* Fuzzer tool used:
https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html
(proprietary
Look like a potential patchset to backport without having to bump
version in stable release:
21ba5b38 ip{,6}tables-restore: Don't accept wait-interval without wait
d89dc47a iptables-restore/save: exit when given an unknown option
65801d02 iptables-restore.8: document -w/-W options
999eaa24 iptable
Look like a potential patchset to backport without having to bump
version in stable release:
I'll test it, and then will alk w/ the SRU verification team to see if
eligible for SRU.
commit 6e2e169eb66b63d2991e1c7ada931e3cdb0ced32
Author: Lorenzo Colitti
Date: Thu Mar 16 16:55:01 2017 +0900
Look like a potential patchset to backport without having to bump
version in stable release:
6e2e169eb iptables: remove duplicated argument parsing code
24f81746 xshared: do not lock again and again if "-w" option is not specified
72bb3dbf0 xshared: using the blocking file lock request when we wai
Thanks Andreas. I'll be working on a minimalistic patch set
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w option
Status in
Thanks Andreas. I'll be working on a minimalistic patch set (if
feasible)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w opt
What about "iptables - 1.6.1-2ubuntu2+testpkg20210629b3" ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w option
Status in
@Khaled El Mously (kmously)
I don't see this piece of code in the klibc upstream project[0]
Is this something you only reproduce in Bionic/18.04LTS ?
Since your fix is not found anywhere else, I would be tempted to assume that it
could be affecting other releases of Ubuntu and possibly more.
Co
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in U
** Description changed:
+ ** SRU TEMPLATE DRAFT **
+
+ [Impact]
+
+
+ [Test Plan]
+
+
+ [Where problems could occur]
+
+
+ [Other Info]
+
+
+ [Original Description]
+
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c,
Khaled El Mously (kmously),
Thanks for the update. I'll review this and talk with sil2100, an SRU
verification member.
Could you please help to fill the SRU template in the description above.
Extra documentations can be found here:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
W
And let them judge if it's worth the adoption or not as a first
exercise. Then we can take a decision for Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
And let them judge if it's worth an upstream adoption or not as a first
exercise. Then we can take a decision for Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
I still believe, it would be a good practice to submit the patch to
upstream.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-req
> I will attempt to upstream this fix to klibc, but I believe the change
to Bionic should happen in parallel/independently since the upstream
patch will not make its way back to Bionic (which is stuck at 2.0.4, as
mentioned above).
Yes that is the plan to SRU the fix on top of what is currently fo
Public bug reported:
systemd-coredump binary package is instructed as follows:
#debian/systemd-coredump.postinst:
adduser --quiet --system --group --no-create-home --home /run/systemd \
--gecos "systemd Core Dumper" systemd-coredump
But one doesn't need this package to be installed to have the s
sudo /bin/systemd-sysusers --cat-config
# /usr/lib/sysusers.d/systemd.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either ve
Home Directory¶
The home directory for a new system user. If omitted, defaults to the root
directory.
Only applies to lines of type u and should otherwise be left unset (or
"-"). It is recommended to omit this, unless software strictly requires
a home directory to be set.
systemd-sysusers only s
https://www.freedesktop.org/software/systemd/man/sysusers.d.html#
u
Create a system user and group of the specified name should they not exist yet.
The user's primary group will be set to the group bearing the same name unless
the ID field specifies it. The account will be created disabled, so t
** Summary changed:
- systemd-coredump user is create by something other than its derived systemd
packages
+ systemd-coredump user is created by something other than its derived systemd
packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
Right, but it doesn't seem right to have it set by default to "/".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1915936
Title:
systemd-coredump user is created by someth
** Bug watch added: Debian Bug tracker #982976
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982976
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982976
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
d/rules:
91 CONFFLAGS_deb = \
92 -Dselinux=true \
93 -Dhwdb=true \
=> 94 -Dsysusers=true \
Would it make sense to turn this off ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubu
The upstream proposal fix that mfo and I worked on has been applied:
https://patchwork.kernel.org/project/linux-
block/patch/20210222154123.61797-1-...@canonical.com/
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to s
** Tags added: sts-sponsors-ddstreet
** Changed in: systemd (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu Groovy)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: systemd
** Changed in: systemd (Ubuntu Groovy)
Assignee: (unassigned) => Ioanna Alifieraki (joalif)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1911187
Title:
scheduled re
** Description changed:
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot
reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
Howeve
** Changed in: systemd (Ubuntu Bionic)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[mas
Matthew,
I was thinking about possibly to declare some package relationships to
not allow the offending packages' combination to occur, when I came
across the exact same thought from cpaelzer.
I don't know if you notice it, here it goes:
"
One suggestion for the coming related uploads.
Do you th
Matthew,
I was thinking about possibly to declare some package relationships to
not allow the offending packages' combination to occur, when I came
across the exact same thought from cpaelzer.
I don't know if you notice it, here it goes[0]:
"
One suggestion for the coming related uploads.
Do you
[sts-sponsors]
adcli option #1 has been sponsored in Bionic with the following
nitpicking:
* Changed version from "0.8.2-1ubuntu2.1" to "0.8.2-1ubuntu1.1"
* Changed debian/control to d/control.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
[sts-sponsors]
cyrus-sasl2 has been sponsored in Bionic.
I have already pinged sil2100 for its SRU verification.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/
I have retried all the FAILED tests.
* postfix/3.3.0-1ubuntu0.3 (amd64) PASSED the 2nd time:
http://autopkgtest.ubuntu.com/packages/p/postfix/bionic/amd64
* kimap/17.12.3-0ubuntu1 (armhf, ppc64el, arm64) are queued and waiting to
retry.
Stay tune ...
- Eric
--
You received this bug notifica
All regression failures, PASSED after a retry. There is no autopkgtest
regression (failures) anymore.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1906627
Title:
GSS
The current situation of python-apt is somewhat critical as no packages
can be pushed via Landscape to machines at the moment. This is causing
landscape-package-changer to segfault as follows:
[apport-retrace]
Core was generated by `/usr/bin/python3 /usr/bin/landscape-package-changer
--quiet'.
Pr
** Description changed:
+ [Impact]
+
USN-4668-1 introduced a regression in python-apt when using certain APIs
with a file handle.
+ [Test case]
+
+ # Landscape scenario:
+ 1) On the Landscape server, create a package profile that installs a single
package, 'hello' is enough.
+ 2) On the
This package is 'native' and I don't want for instance to introduce
'quilt' before talking to the maintainer.
@julian, how do you want to proceed to fix this bug in python-apt ?
- Eric
** Description changed:
[Impact]
USN-4668-1 introduced a regression in python-apt when using certain AP
@julian, thanks for the quick reply. Will do.
** Changed in: python-apt (Ubuntu)
Status: New => Fix Released
** Description changed:
[Impact]
USN-4668-1 introduced a regression in python-apt when using certain APIs
with a file handle.
[Test case]
# Landscape scenario:
This is fixed in active development release (hirsute):
python-apt (2.1.7) unstable; urgency=medium
* SECURITY UPDATE: various memory and file descriptor leaks (LP: #1899193)
- python/arfile.cc, python/generic.h, python/tag.cc, python/tarfile.cc:
fix file descriptor and memory leaks
I have a new test pkg:
This pkg keeps the same behavior for 'iptables'
# Hold the lock:
flock /run/xtables.lock sleep 36000
# It holds and wait until flock() finishes or get killed, and then get executed.
iptables -L
# With 'wait' option, it waits until the wait time is ended:
time iptables -
Version in comment #12 is "iptables - 1.6.1-2ubuntu2+testpkg20210706b4"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w optio
I'll work to re-arrange the fprintf if 'wait' option is used or not and
see the outcome of it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-rest
Both 'iptables' and 'ip*tables-restores' sleep and wait until the lock
is released if no 'wait' option. If 'wait' option is set, it wait for
the amount of time instructed and stop waiting.
I think the printed message make more sense now :
# time cat /etc/rules.v4 | iptables-restore -c
Another ap
New testpackage: iptables - 1.6.1-2ubuntu2+testpkg20210706b8
Note: If that works as expected for Andreas. The only things that needed
would be to update the manpage, which I didn't do on this current test
pkg.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I'm on the same page.
Maybe we should leave the package in -update as is and go with the
flock() alternative.
OR evaluate if, let's say, the Focal's iptables could be backported
(if feasible) in bionic-backports.
That way, one who wants the 'wait' and 'wait-interval' to be available
could r
I think 'backports' would have been a great place to have this behavior
change in Bionic while keep the current one in -updates.
I just came across an email about 'backports' about to die (from
rbasak). Let's see what is the outcome and rely on the flock()
alternative for now.
I'll monitor the "-
Any volunteer to test a package in Bionic in the attempt to support
keepconfiguration ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting s
@maanus, That is a first iteration.
sudo add-apt-repository ppa:slashd/keepconfiguration
sudo apt-get update
Let me know the outcome.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.l
Thanks @Maanus.
So the outcome is positive here then.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks ke
Good catch Dan.
Maanus could you repeat the testing with what Dan brought up ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-n
Uploaded into bionic upload queue, now waiting for SRU approval.
- Eric
** Changed in: systemd (Ubuntu Bionic)
Status: Incomplete => In Progress
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification b
Hi Maanus,
Would you mind perform the 'test cases' now against the systemd's
bionic-proposed package ? And report any outcome.
This is one of the last steps for Lukasz to approve the proposed package
after the baking minimum aging period (7 days) in verification phase.
- Eric
--
You received
Thanks Maanus for all the testing. Much appreciated.
I'll take care of the rest in a couple of days with Lukasz.
Package needs to stay in proposed for a couple more days (minimum 7 days)
- Eric
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received
systemd reaches day 7 wo/ autopkgtest failure nor negative
outcome/feedbacks.
I have asked 'sil2100' to promote the package into bionic-updates.
Stay tuned ...
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
I'll be reviewing the change with my colleague Kellen.
In the meanwhile ...
What is the concern/impact behind not having the version available in ps ?
(Outside it should output/report it) ?
The version can be found in the package version (dpkg -l procps)
Is it for integrity purposes in order to
** Tags added: seg sts
** Also affects: procps (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: procps (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: procps (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: pro
** Tags added: sts-sponsors-slashd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1917148
Title:
ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
Status in procps package
[sts-sponsors]
Debian uses autopkgtest for 'version' w/ restriction superficial as
follows:
Tests: version
Restrictions: superficial
https://people.debian.org/~eriberto/README.package-tests.html
superficial
The test does not provide significant test coverage, so if it passes, that does
not ne
** Description changed:
[Impact]
* Breakage of tools expecting the version number or the number to
substantially match the Debian package version.
* May confuse users expecting the version to substantially match the Debian
package version.
* Restores behavior to that provided in Gr
[sts-sponsors]
Sponsored in Focal upload queue, now waiting for SRU verification team
approval.
Thanks for your contribution, Kellen.
Test case validation (before upload):
root@procpsf:/tmp# pgrep --version
pgrep from procps-ng 3.3.16
root@procpsf:/tmp# ps --version
ps from procps-ng 3.3.1
** Tags removed: sts-sponsors-slashd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1917148
Title:
ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
Status in procps packa
I totally get your concern. In the same time, other procps pkkg in
Ubuntu groovy, ... uses the same approach.
But I leave you to decide what is best for this particular bug.
Let us know.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
[autopkg regression]
All tests are now fine. They needed a second retry.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1917148
Title:
ps version is UNKNOWN in pro
[Verification Focal]
This has been brought to my attention by an impacted user:
"
I was able to apply the fixed procps package from the focal-proposed repo on
servers in a test cluster. The fix resolved the issue with free -V and the
related DataStax OpsCenter error.
Thanks
"
- Eric
** Tags
Don van der Haghen (donvdh),
Seems like you need a sponsor. If I sponsor the patch for you, will you
be amenable to test the packages once found in $RELEASE-proposed ?
If cosmic is impacted, could you also please provide a debdiff for it,
before I proceed.
Regards,
Eric
** Tags added: sts
** C
and could you please fill the SRU template ?
https://wiki.ubuntu.com/StableReleaseUpdates
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1666203
Title:
pam_tty_audit failed in
** Description changed:
+ [Impact]
+
+ * Kernel keystroke auditing via pam_tty_audit.so not working
+
+ * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it
failed in pam_open_session.
+It was triggared by use uninitialized variable in
pam_tty_audit.c::pam_open_sessio
** Changed in: pam (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: pam (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: pam (Ubuntu Cosmic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are
I have provided a test package to an impacted user for Bionic/18.04LTS.
Here's what has been brought to my attention after this user tried the test
package:
"Test results look good. Keystroke logging audit messages are coming through."
--
You received this bug notification because you are a mem
** Changed in: pam (Ubuntu Bionic)
Assignee: Don van der Haghen (donvdh) => Eric Desrochers (slashd)
** Changed in: pam (Ubuntu Bionic)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Don,
I'll take care of patching Bionic and Cosmic, and I will let you handle
Xenial, if you don't mind through the Ubuntu sponsorship.
I have reviewed your Xenial debdiff, and it will need some rework.
The patch requires to be in quilt (debian/patches-applied), and not file
manipulate directly
Uploaded for Bionic and Cosmic.
** Description changed:
[Impact]
- * Kernel keystroke auditing via pam_tty_audit.so not working
-
- * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it
failed in pam_open_session.
-It was triggared by use uninitialized variable in
** Also affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: resolvconf (Ubuntu Disco)
Importance: Undecided => High
** Changed in: resolvconf (Ubuntu Disco)
Status: New => In Progress
** Changed in: resolvconf (Ubuntu Disco)
Assignee: (unassigne
** Changed in: systemd (Ubuntu Xenial)
Assignee: Dimitri John Ledkov (xnox) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1795764
Ti
[VERIFICATION BIONIC]
It has been brought to my attention the following (by an impacted user):
I have enabled the "-proposed" pocket and done the following:
1) Logged into workstation, elevated to root
2) Installed packages from "-proposed": libpam0g libpam-modules
libpam-modules-bin libpam-runti
[VERIFICATION XENIAL]
Using the protocol mentioned in the [Test Case] with systemd from
xenial-proposed, version : 229-4ubuntu21.17. I can no longer reproduce
the situation.
# systemctl list-units --all | grep bind-test
mnt-bind\x2dtest.mount loadedactive mounted
@Donvdh,
Thanks I'll have a look at it probably next week. Thanks !
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1666203
Title:
pam_tty_audit failed in pam_open_session
St
** Description changed:
[Impact]
* Kernel keystroke auditing via pam_tty_audit.so not working
* When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it
failed in pam_open_session.
It was triggared by use uninitialized variable in
pam_tty_audit.c::pam_open_session
Sponsored for Disco, considering that after a discussion with joalif,
she committed to file a debian bug and submit the patchset to debian as
well for stay consistent in the chain Upstream -> Debian -> Ubuntu.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: systemd (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1818282
Title:
systemd-networkd - RoutingP
Previous change reverted and new fix uploaded (after ddstreet discussion
with xnox) in Disco.
- Eric
** Changed in: resolvconf (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
enial
rsyslog | 8.32.0-1ubuntu4 | bionic
rsyslog | 8.32.0-1ubuntu5 | cosmic
rsyslog | 8.32.0-1ubuntu7 | disco
** Affects: rsyslog (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: rsyslog (Ubuntu Xenial)
Importance: Medium
Uploaded into xenial upload queue. Now waiting for SRU verificaition
team to approve the upload for rsyslog to start building into xenial-
proposed for the testing phase.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog
** Description changed:
[IMPACT]
- Xenial uses systemd as default now, debian salsa
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
+ Xenial uses systemd as default now, debian salsa
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
taking advantage
** Description changed:
[IMPACT]
Xenial uses systemd as default now, debian salsa
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
taking advantage of systemctl directly if systemd is active by still keeping
Sysv init script as fallback only.
While there is no 'r
** Description changed:
[IMPACT]
Xenial uses systemd as default now, debian salsa
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
taking advantage of systemctl directly if systemd is active by still keeping
Sysv init script as fallback only.
While there is no 'r
** Description changed:
[IMPACT]
Xenial uses systemd as default now, debian salsa
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
taking advantage of systemctl directly if systemd is active by still keeping
Sysv init script as fallback only.
While there is no 'r
[VERIFICATION XENIAL #1]
It has been brought to my attention the following by a Ubuntu user:
"My team confirms that the package which is in -proposed solves our issue."
This user was having issue doing rsyslog logrotation inside a container
which has SYS_PTRACE turned off. Using the systemctl app
[VERIFICATION XENIAL #3]
$ logrotate -vdf /etc/logrotate.conf: works as expected
...
renaming /var/log/syslog.7.gz to /var/log/syslog.8.gz (rotatecount 7, logstart
1, i 7),
renaming /var/log/syslog.6.gz to /var/log/syslog.7.gz (rotatecount 7, logstart
1, i 6),
renaming /var/log/syslog.5.gz to
** Description changed:
From the PR:
Currently, if there are two /proc/self/mountinfo entries with the same
mount point path, the mount setup flags computed for the second of
these two entries will overwrite the mount setup flags computed for
the first of these two entries. This is the r
*** This bug is a duplicate of bug 1795764 ***
https://bugs.launchpad.net/bugs/1795764
Public bug reported:
[Description]
The following has been brought to my attention :
" Currently, if there are two /proc/self/mountinfo entries with the same
mount point path, the mount setup flags comput
1 - 100 of 770 matches
Mail list logo
