** Changed in: landscape-client (Ubuntu Artful)
Status: Confirmed => In Progress
** Changed in: landscape-client (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: landscape-client (Ubuntu Trusty)
Status: Confirmed => In Progress
--
You received this bug notifi
** Description changed:
[impact]
On a trusty system, if using MODULES=dep with lvm-on-nvme then update-
initramfs fails to rebuild the initramfs. This prevents using
MODULES=dep for building an initramfs on trusty, with a rootfs that uses
lvm on nvme.
[test case]
install a
** Description changed:
- The HDD enclosure causing this is the 'ORICO 2.5 inch USB 3.0'
- As seen here http://www.amazon.co.uk/dp/B00BH83LYG/
+ [Impact]
+
+ Scenario #1:
+ * When there is an external USB External Drive[1] is connected to system,
lshw command segfaults.
+
+ Scenario #2:
+ * I
** Description changed:
[Impact]
Scenario #1:
- * When there is an external USB External Drive[1] is connected to system,
lshw command segfaults.
+ * When there is an external USB External Drive[1] connected to the system,
'lshw' command segfaults.
Scenario #2:
* In the Landscape c
debdiff - lshw for Trusty/14.04 LTS
** Patch added: "lshw-trusty-lp1471983.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/lshw/+bug/1471983/+attachment/4966702/+files/lshw-trusty-lp1471983.debdiff
--
You received this bug notification because you are a member of STS
Sponsors Team,
** Tags added: sts
--
You received this bug notification because you are a member of STS
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1471983
Title:
USB HDD makes lshw seg-fault when run as root
Status in lshw package in Ubuntu:
Fix Released
Status i
** Description changed:
[Impact]
Scenario #1:
* When there is an external USB External Drive[1] connected to the system,
'lshw' command segfaults.
Scenario #2:
- * In the Landscape context, 'lshw' is use for Landscape clients HW inventory
... if an USB External Drive[1] is connecte
debdiff V2 - lshw for Trusty/14.04 LTS
** Patch added: "lshw-trusty-lp1471983_V2.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/lshw/+bug/1471983/+attachment/4966834/+files/lshw-trusty-lp1471983_V2.debdiff
--
You received this bug notification because you are a member of STS
Spons
** Description changed:
[Impact]
Scenario #1:
* When there is an external USB External Drive[1] connected to the system,
'lshw' command segfaults.
Scenario #2:
* In the Landscape context, 'lshw' is use for Landscape clients[2] HW
inventory ... if an USB External Drive[1] is conne
** Description changed:
[Impact]
Scenario #1:
* When there is an external USB External Drive[1] connected to the system,
'lshw' command segfaults.
Scenario #2:
* In the Landscape context, 'lshw' is use for Landscape clients[2] HW
inventory ... if an USB External Drive[1] is conne
Sponsored, the package is now waiting in the Trusty upload queue for the
SRU verification team approval before it starts building in trusty-
proposed.
Thanks Dan !
** Tags added: sts-sponsor-done-slashd
--
You received this bug notification because you are a member of STS
Sponsors Team, which i
** Also affects: landscape-client (Ubuntu Bb-series)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1721383
Title:
Update landscape-client with up
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1719671
Title:
[SRU] include recent version containing fips and livepatch
Status in ubuntu-advantage-tools p
** Description changed:
+ [New upstream microreleases]
+
+ https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
+
+ ...
+ > a reliable and credible test suite for assuring the quality of every commit
or release
+ YES, testsuite is in tox (python virtual test env)
+ > the test
** Description changed:
- [New upstream microreleases]
-
- https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
-
- ...
- > a reliable and credible test suite for assuring the quality of every commit
or release
- YES, testsuite is in tox (python virtual test env)
- > the test
** Also affects: ubuntu-advantage-tools (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: ubuntu-advantage-tools (Ubuntu Artful)
Status: New => Fix Released
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the
Sponsored for Zesty, Xenial & Trusty in their respective upload queue.
Now waiting for SRU verification team to approve the upload for the packages to
enter in the test phase ($RELEASE-proposed)
- Eric
** Tags removed: sts-sponsor-slashd
** Tags added: sts-sponsor-slashd-done
--
You received t
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1699179
Title:
PackageReporter kicks in during do-release-upgrade
Status in Landscape Client:
New
Status i
** Tags removed: sts-sponsor-slashd
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1699179
Title:
PackageReporter kicks in during do-release-upgrade
Status in Landscape Client:
New
Status
** Changed in: ubuntu-advantage-tools (Ubuntu Artful)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: ubuntu-advantage-tools (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: ubuntu-advantage-tools (Ubuntu Artful)
Status: Fix Released => In Progre
As we speak 'ubuntu-advantage-tools' is stuck in the autopkgtest ...
auto-sync and there are transitions still in progress and put the
autopkgtest environment under heavy load.
It may take severals day and maybe weeks before it catch-up.
Current status :
ubuntu-advantage-tools (10 to 13)
Mai
Based on the above discussion about Trusty package
A new version of "ubuntu-advantage-tools [10ubuntu0.14.04.2]" has been
uploaded for Trusty :
* Skipping tests during package builds.
- d/rules: Disabling the tests.
- d/control: Removing tests dependencies.
- Eric
--
You received this
** Changed in: cups (Ubuntu Artful)
Status: Triaged => In Progress
** Changed in: cups (Ubuntu Artful)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1729910
Title:
lp ignores ~/.cups/lpoptions in 17.10
Status in cups package in Ubuntu:
Fix Released
Status
Sponsored for Artful.
* Applied cleanly
* Autopkgtest is successfull :
--
adt-run [09:26:47]: summary
cups-core-driversPASS
cups PASS
--
*...
- Eric
** Tags removed: sts-sponsor-slashd
** Tags added: sts-sponsor-slashd-done
--
You received this bug not
Sponsored for Artful.
* Manual run of autopkgtest has been successful :
--
adt-run [09:26:47]: summary
cups-core-drivers PASS
cups PASS
- Eric
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs
** Description changed:
[Impact]
Reference:
https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
This SRU contains minor updates for landscape-client as follow :
- Fix regression in configuration hook under install-cd chroot (LP: #1699789)
- Report autorem
** Tags removed: sts sts-sponsor-slashd-done
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1729910
Title:
lp ignores ~/.cups/lpoptions in 17.10
Status in cups package in Ubuntu:
Fix Rele
** Description changed:
[Impact]
Reference:
https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
This SRU contains minor updates for landscape-client as follow :
- Fix regression in configuration hook under install-cd chroot (LP: #1699789)
- Report autorem
** Summary changed:
- Request to backport upstream release v3.5
+ Request to backport sosreport v3.5
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1734983
Title:
Request to backport sosrep
* autopkgtest result (All manual autopkgtest runs (pre-SRU )passed)
[ARTFUL]
$ /usr/bin/adt-run 'sosreport_3.5-1~ubuntu17.10.1.dsc' --- lxc adt-artful-amd64
adt-run [14:16:01]: summary
sos-run-nonroot.py PASS
sos-run.py PASS
[ZESTY]
$ /usr/bin/adt-run 'sosreport_3
** Description changed:
*** DRAFT in progress ***
[Impact]
Canonical support team (AKA STS) largely depend on sosreport package to
troubleshoot system.
sosreport is always in constant development including new bugfixes, new
features such as new plugins[1], that can be intere
** Description changed:
*** DRAFT in progress ***
[Impact]
Canonical support team (AKA STS) largely depend on sosreport package to
troubleshoot system.
sosreport is always in constant development including new bugfixes, new
features such as new plugins[1], that can be intere
I can reproduce the situation as well with sosreport upstream and v3.5
debian package that I have built for pre-SRU testing.
Example:
Plugin such as [acpid], [boot], ... are no longer running with 'sosreport -a'
even if "packages=" are installed.
Let's put the SRU on hold until we or upstream
Seems like something is broken in the "package=" mechanism behaviour.
The no longer running plugins that we have identified coincide with recent
package add commit :
18ab068 [dbus] add missing packages list
3d0ea25 [cron] add missing packages list
0348833 [acpid] add missing packages list
A
** Also affects: sosreport via
https://github.com/sosreport/sos/issues/1155
Importance: Unknown
Status: Unknown
** Description changed:
*** DRAFT in progress ***
[Impact]
Canonical support team (AKA STS) largely depend on sosreport package to
troubleshoot system.
sosr
** Bug watch added: Debian Bug tracker #883537
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537
** Also affects: sosreport (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537
Importance: Unknown
Status: Unknown
--
You received this bug notification becau
** Description changed:
*** DRAFT in progress ***
[Impact]
Canonical support team (AKA STS) largely depend on sosreport package to
troubleshoot system.
sosreport is always in constant development including new bugfixes, new
features such as new plugins[1], that can be intere
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720627
Title:
Segfault when using docker and overlay2
Status in sysstat package in Ubuntu:
Fix Released
S
Based on my irc conversation with Dariusz... it seems like Debian and
Ubuntu devel release (bionic) only has half of the upstream commit. Only
fixing "count.c" and not "rd_stats.c".
Seems like there is a potential of 2 separate segfault scenario depending on
sadc usage:
https://github.com/sysstat
** Changed in: sysstat (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
** Changed in: sysstat (Ubuntu)
Importance: High => Medium
** Changed in: sysstat (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of
** Tags removed: sts-sponsor-slashd
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720627
Title:
Segfault when using docker and overlay2
Status in sysstat package in Ubuntu:
In Progress
Here's the debdiff fixing the regression found by Bryan Quigley.
I talked with the SRU team and it is okay to proceed with the upload of
this fix in Devel and Stable release if waiting too long for upstream to
merge.
In this case, the fix will likely be merge in April 2018 for v3.6, and
by then w
** Changed in: sosreport (Ubuntu Bionic)
Status: Fix Released => In Progress
** Changed in: sosreport (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug not
** Changed in: sosreport (Ubuntu Bionic)
Status: In Progress => Fix Released
** Tags removed: patch
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1734983
Title:
Request to backport
New => In Progress
** Changed in: sosreport (Ubuntu Trusty)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Zesty)
Assignee: (unassigned) => Er
Following bionic sponsorship from Christian + commitment to report to Debian.
I have now sponsored the affected Stable releases: Artful, Zesty and Xenial
(which including the rd_stats.c change, mentioned above).
Unapproved: sysstat (artful-proposed/main) [11.5.7-1ubuntu1 => 11.5.7-1ubuntu2]
(ku
** Tags added: sts-sponsor-slashd-done
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720627
Title:
Segfault when using docker and overlay2
Status in sysstat package in Ubuntu:
Fix Relea
Output of "/var/log/dist-upgrade/screenlog.0"
---
Preparing to unpack
.../ca-certificates-java_20160321ubuntu1~16.04.1testb2_all.deb ...^M
Unpacking ca-certificates-java (20160321ubuntu1~16.04.1testb2) over
(20130815ubuntu1) ...^M
dpkg: openjdk-7-jre-headless:amd6
debdiff for xenial (2nd iteration).
This is the debdiff I'll ask foundation to review before the upload.
** Patch added: "lp1723198_xenial_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1723198/+attachment/5022858/+files/lp1723198_xenial_V2.debdiff
--
You received this bug n
** Description changed:
+ [Impact]
+
+ * ca-certificates-java depend on openjdk-7 which no longer exist after
Trusty which
+triggers a failure while doing release upgrade, due to the triggers loop.
+
+ [Test Case]
+
+ 1. Install Ubuntu server 14.04.5 + all the updates
+
+ (I used "uvt-k
** Changed in: dpkg (Ubuntu Zesty)
Status: New => Confirmed
** Changed in: dpkg (Ubuntu Zesty)
Importance: Undecided => Medium
** Changed in: dpkg (Ubuntu Zesty)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a
** Patch added: "lp1723198_zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1723198/+attachment/5022883/+files/lp1723198_zesty.debdiff
** Changed in: dpkg (Ubuntu Zesty)
Status: Confirmed => In Progress
** Description changed:
[Impact]
ca-certificates-java cur
ficates-java (Ubuntu Zesty)
Importance: Undecided => Medium
** Changed in: ca-certificates-java (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: ca-certificates-java (Ubuntu Zesty)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Descriptio
The "default-jre-headless" might be a good approach to look at to avoid
to have to maintain Debian/Ubuntu ca-certificates-java package for
situation like this or others possible scenarios.
IMHO, I think it's better to stick with the actual fix for now and maybe
submitting a bug to Debian (if no al
If I compare a pure installation via apt-get install ca-certificates-
java in Xenial (no upgrade involve) I see a behaviour change between the
package currently in the archive and the one I have fix in a PPA.
# Current ca-certificates-java (from archive) #
It is in
** Description changed:
[Impact]
ca-certificates-java currently depend on openjdk-7 which no longer exist
after Trusty. It triggers failures while doing release upgrade, due to
triggers loop.
[Test Case]
# Install Ubuntu server 14.04.5 + all the updates.
(I used "uvt-kvm cre
I have quickly test, and haven't had any problem to upgrade from actual
package of "ca-certificates-java" from the archive to the "ca-
certificates-java" (including the openjdk-8 fix) on my PPA.
Seems like in this case openjdk-9 remain and openjdk-8 is discard.
Keeping the most recent openjdk vers
** Description changed:
[Impact]
ca-certificates-java currently depend on openjdk-7 which no longer exist
after Trusty. It triggers failures while doing release upgrade, due to
triggers loop.
[Test Case]
# Install Ubuntu server 14.04.5 + all the updates.
(I used "uvt-kvm cre
# Discussion with foundation team.
slashd: interesting that this is a behavior difference; we
actually *would* want it to pull in openjdk-8-jre-headless by default
instead of -9- in xenial, since 9 is in universe and 8 is in main. It
is a behavior change that we should call out as part of the SR
Uploaded for Xenial and Zesty.
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1723198
Title:
[SRU] upgrade from 14.04 to 16.04 fails with: ca-certificates
20170717~16.04.1 failed to instal
[JUSTIFICATION XENIAL]
--
The upgrade has been tested in 2 ways :
- Release upgrade using the fix package via a local archive.
- Release upgrade using the fix package via xenial-proposed.
In both cases, the upgrade went well installing "ca-certificates-java"
version "20160321u
[JUSTIFICATION ZESTY]
--
Release upgrade using "ca-certificates-java" package from xenial-proposed (part
of the current SRU) and upgraded to "ca-certificates-java" from zesty-proposed
during the release upgrade.
To simulate the situation once both packages will land in $RELEA
[JUSTIFICATION ZESTY]
--
Release upgrade using "ca-certificates-java" package from xenial-proposed (part
of the current SRU) and upgraded to "ca-certificates-java" from zesty-proposed
during the release upgrade.
To simulate the situation once both packages will land in $RELEA
[JUSTIFICATION ZESTY] (Part 2)
--
Release upgrade using "ca-certificates-java" package currently found in
-updates and upgraded to zesty-proposed during the release upgrade.
The upgrade went well installing "ca-certificates-java" version
"20161107ubuntu1" which now depend on o
[JUSTIFICATION ZESTY] (Part 2)
--
Release upgrade using "ca-certificates-java" package currently found in
-updates and upgraded to zesty-proposed during the release upgrade.
The upgrade went well installing "ca-certificates-java" version
"20161107ubuntu1" which now depend on o
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1723198
Title:
[SRU] upgrade from 14.04 to 16.04 fails with: ca-certifica
** Tags added: sts sts-sponsor-ddstreet
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1739033
Title:
Corosync: Assertion 'sender_node != NULL' failed when bind iface is
ready after corosy
** Changed in: corosync (Ubuntu)
Status: New => Fix Released
** Changed in: corosync (Ubuntu Trusty)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: corosync (Ubuntu Xenial)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: corosync (Ubuntu Xenial)
** Tags removed: sts-sponsor-ddstreet
** Tags added: sts-sponsor-ddstreet-done
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1739033
Title:
Corosync: Assertion 'sender_node != NULL' failed
To re-enforce Victor's answer (comment #6) and help answering Brian's
question (comment #5) :
## corosync upstream commit :
# git describe aab55a004bb12ebe78db341dc56759dfe710c1b2
v2.3.5-45-gaab55a0
# rmadison corosync
corosync | 2.4.2-3build1| zesty | source, amd64, arm64, armhf,
** Also affects: corosync (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: corosync (Ubuntu Zesty)
Status: New => Fix Released
** Changed in: corosync (Ubuntu Artful)
Stat
v3.5 sponsored for AZXT, waiting for SRU verification team to approve to
start building in -proposed.
- Eric
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1734983
Title:
Request to backpor
For SRU,
I have already contacted sil2100 that should take care of it, but just
in case of someone else have a look at the upload and wonder why there
is 2 uploads for the same thing.
I have uploaded the sosreport package twice for each release because I
forgot to add the (LP: #) syntax in th
sil2100 has rejected the first upload and kept the second which include
the (LP: #X) syntax in d/changelog.
Things are a bit blocked everywhere. Accepting the uploads now will do
nothing as we have no builders. sil2100 will review the uploads later
when there will be some builders available.
Hi Seyeong,
As we speak the LP build farm and autopkgtest request.cgi are disabled for
maintenance; no ETA yet.
No new uploads are allowed during this temporary freeze cause by the
maintenance.
We will gladly review your patch when everything will back to normal.
- Eric
** Description changed
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: pacemaker (Ubuntu Trusty)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
** Changed in: pacemaker (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: pacemaker (Ubuntu Trusty)
Sta
** Also affects: apparmor (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Zest
** Description changed:
[Impact]
If PID is larger than 6 digits.
apparmor denies process.
this fix is committed, but not released. so all supporting version are
affected.
[Test Case]
1. making pid over 6 digits
- i used touch command to do it
2. snap install canoni
Hi Seyeong,
As we speak the LP build farm and autopkgtest request.cgi are disabled for
maintenance; no ETA yet.
No new uploads are allowed during this temporary freeze cause by the
maintenance.
We will gladly review your patch when everything will back to normal.
- Eric
--
You received this
Hi Seyeong,
Here's some sponsoring notes that will require minor change. While
waiting for the build farm ...
#1 - Can you make sure (if not already) to forward/submit the patch to
debian upstream against apparmor ? Which is a requirement for the patch
to land in Ubuntu.
Then we can request a co
I apologize, for #2 above in comment#14, the good commit containing the
fix seems to be "630cb2a981cdc731847e8fdaafc45bcd337fe747", please make
sure #3 "Origin:" reflect that.
- Eric
** Description changed:
[Impact]
If PID is larger than 6 digits.
apparmor denies process.
this f
Not quite sure now if apparmor upstream is found in launchpad[1] or
gitlab[2].
[1] https://launchpad.net/apparmor
[2] https://gitlab.com/apparmor
If it's launchpad then the URL is good.
If #2 & #3 are good (After your confirmation), then only #1, #4 and #5
are missing.
Im simply trying to antic
Thanks Seyeong !
I'll do a 2nd review when the build farm will be back and will do the
other changes if necessary.
- Eric
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pi
Meanwhile, please make sure you have submitted the patch to Debian and
link the debbug in this LP.
- Eric
** Changed in: apparmor (Ubuntu Trusty)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
** Changed in: apparmor (Ubuntu Xenial)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
**
I note that the Seyeong's Artful debdiff proposed version
"2.11.0-2ubuntu18" and bionic "2.11.0-2ubuntu19"
# Current rmadison output
apparmor | 2.11.0-2ubuntu17 | artful
apparmor | 2.11.0-2ubuntu18 | bionic
Bionic version is good.
No need to change the debdiff,
** Description changed:
[Impact]
- If PID is larger than 6 digits.
+ If PID is larger than 6 digits apparmor denies process which only affect
+ 64-bit systems[1] where the PID_MAX_LIMIT can be generated up to 7
+ digits at the maximum.
- apparmor denies process.
+ This fix is committed, bu
** Description changed:
[Impact]
If PID is larger than 6 digits apparmor denies process which only affect
64-bit systems[1] where the PID_MAX_LIMIT can be generated up to 7
digits at the maximum.
This fix is committed, but not released. so all supporting version are
affected.
Attaching "lp1717714_bionic_V2.debdiff":
- Nitpicking stuff related to d/changelog and DEP3 patch header.
** Patch added: "lp1717714_bionic_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5035841/+files/lp1717714_bionic_V2.debdiff
--
You received this
I have contacted a coredev to hopefully sponsor the development bit
(Bionic) today, so I can proceed with the stable release update myself
next week.
- Eric
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchp
** Changed in: apparmor (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pid_max m
bionic sponsoring done.
Thanks to sil2100.
Ill monitor the bionic build, and then start the SRU once everything
good.
- Eric
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1717714
Title:
Another verification that IMHO can be done more easily and faster than
the touch approach explain above is to directly change the pid_max and
ns_last_pid via sysctl in the 7 digit range (<4millions), and then try
to reproducer.
For instance:
sysctl -w kernel.pid_max=300
sysctl -w kernel.ns_las
** Description changed:
[Impact]
If PID is larger than 6 digits apparmor denies process which only affect
64-bit systems[1] where the PID_MAX_LIMIT can be generated up to 7
digits at the maximum.
This fix is committed, but not released. so all supporting version are
affected.
** Tags added: sts
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1742531
Title:
New Amazon AWS C5 instances are not recognised as a VM
Status in Landscape Client:
Fix Committed
Status in
l/24/files
** Affects: landscape-client
Importance: Undecided
Status: New
** Affects: landscape-client (Ubuntu)
Importance: Medium
Assignee: Eric Desrochers (slashd)
Status: In Progress
** Affects: landscape-client (Ubuntu Trusty)
Importance: Medium
Assignee:
I have reported a separate bug for digitcalocean :
https://bugs.launchpad.net/bugs/1743232
- Eric
** Changed in: landscape-client (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: landscape-client (Ubuntu Artful)
Assignee: (unassigned) =>
The patch for bionic (devel release) has been sponsored but it is stuck
in bionic-proposed for now waiting for the non amd64/i386 builder to be
operational -> ppcel64, arm, s390x, ..
#rmadison
apparmor | 2.11.0-2ubuntu18 | bionic | source, amd64, arm64, armhf,
i386, ppc64el, s390x
appar
"lp1742531-lp1743232-bionic.debdiff"
** Patch added: "lp1742531-lp1743232-bionic.debdiff"
https://bugs.launchpad.net/landscape-client/+bug/1742531/+attachment/5037361/+files/lp1742531-lp1743232-bionic.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, whi
lp1742531-lp1743232-bionic_V2.debdiff
** Patch added: "lp1742531-lp1743232-bionic_V2.debdiff"
https://bugs.launchpad.net/landscape-client/+bug/1742531/+attachment/5037369/+files/lp1742531-lp1743232-bionic_V2.debdiff
--
You received this bug notification because you are a member of STS
Sponso
1 - 100 of 677 matches
Mail list logo
