th a banner like "We need you for
> SRUs!" (lol, just kidding) prompting people to volunteer for
> fixes/SRUs to help with their own review/sponsoring practice, would
> help! :-)
>
> cheers,
>
> On Fri, Mar 27, 2020 at 10:50 PM Eric Desrochers
> wrote:
> >
&
** Also affects: lxcfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: lxcfs (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: lxcfs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: lxcfs (Ubuntu Bionic)
I like the tag idea. What about "sts-sponsor-padawan" ?
On Fri, Mar 27, 2020 at 5:19 PM Dan Streetman
wrote:
> going thru my old watched bugs, here are some bugs that should be easy
> to handle. Maybe we should figure out a LP bug tag to use for bugs
> that we find that are good for potential
** Changed in: containerd (Ubuntu Bionic)
Assignee: (unassigned) => Jorge Niedbalski (niedbalski)
** Changed in: containerd (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug
[FOCAL]
Note: lxd only available via SNAP.
# lsb_release -cs
focal
# snap list lxd
Name Version RevTracking Publisher Notes
lxd 3.0.411348 3.0/stable/… canonical✓ -
# ls -altr /sos_commands/lxd/lxd.buginfo
-rw-r--r-- 1 root root 22017 Mar 25 16:41
Pushed into focal along with LP: #1865212.
--
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/1868215
Title:
SRU: [lxd] Drop db collection and introduce lxd.buginfo
Status in sosreport package
Sponsored in Eoan
Thanks Simon !
** 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/1850205
Title:
AttributeError: module 'apt_pkg' has no attribute
** Description changed:
[Impact]
[Test Case]
Scenario #1
* Deploy a machine (Xenial) with lxd installed as a DEB package
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data
** Changed in: landscape-client (Ubuntu Eoan)
Status: New => In Progress
** Changed in: landscape-client (Ubuntu Eoan)
Assignee: (unassigned) => Simon Poirier (simpoir)
** Changed in: landscape-client (Ubuntu Eoan)
Importance: Undecided => Medium
** Tags added: sts
** Tags
Sponsored by dgadomski. Unsubscribing sts-sponsor team.
Thanks for your contribution Seyeong.
Thanks for the sponsoring Dariusz.
- 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/1794478
** Changed in: network-manager (Ubuntu Bionic)
Status: Confirmed => In Progress
** Tags added: sts-sponsor-dgadomski
--
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/1794478
Title:
** Description changed:
[Impact]
Current bionic d/control doesn't include "python3-sss" or "python-sss"
as runtime dependency:
Package: sssd-tools
Architecture: any
Depends:
python,
sssd-common (= ${binary:Version}),
${misc:Depends},
${shlibs:Depends}
Description:
Sponsored for B/E
Thanks Simon !
--
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/1758529
Title:
landscape-package-changer crashed with io.UnsupportedOperation in
pulse(): fileno
Status
Thanks Lukasz,
$ lsb_release -cs
bionic
$ apt-cache policy python-sss
python-sss:
Installed: (none)
Candidate: 1.16.1-1ubuntu1.4
Version table:
1.16.1-1ubuntu1.4 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
--
You received this bug notification
** Changed in: landscape-client (Ubuntu Disco)
Status: Confirmed => Won't Fix
** Changed in: landscape-client (Ubuntu Eoan)
Assignee: (unassigned) => Simon Poirier (simpoir)
** Changed in: landscape-client (Ubuntu Bionic)
Assignee: (unassigned) => Simon Poirier (simpoir)
**
util-linux uploaded in focal.
Thanks Mauricio !
--
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/1862846
Title:
Crash and failure installing focal
Status in subiquity:
New
Status in
** Tags added: sts-sponsor-dgadomski
--
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/1862226
Title:
/usr/sbin/sss_obfuscate fails to run: ImportError: No module named
pysss
Status in sssd
** 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/1843044
Title:
firefox crashes on a FIPS enabled machine
Status in Mozilla Firefox:
New
Status in firefox
Sponsored in focal.
* Fix approved upstream
* Bug reported and patch submitted to upstream Debian.
Please keep an eye on the excuses page for util-linux.
- Eric
** Tags removed: sts-sponsor-slashd-focal
--
You received this bug notification because you are a member of STS
Sponsors, which is
** Tags added: sts-sponsor-slashd-focal
--
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/1858802
Title:
libblkid: no bcache UUID due to ambivalent detection of bcache and
xfs_external_log
A current landscape-client SRU (LP: #1855522) prevents me to upload
19.12 in the archive.
Let's circle back in Jan 2020 for the sponsoring of 19.12 lds-client.
- Eric
** Changed in: landscape-client (Ubuntu Eoan)
Status: In Progress => Confirmed
--
You received this bug notification
** Changed in: landscape-client (Ubuntu Eoan)
Status: New => In Progress
** Tags added: sts-sponsor-slashd
** 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/1855756
I also reported a LP bug about the lua-lpeg modernisation:
LP:
https://bugs.launchpad.net/debian/+source/lua-lpeg/+bug/1851854
Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944360
- Eric
--
You received this bug notification because you are a member of STS
Sponsors, which is
[sts-sponsor]
Sponsored for E, D, B & X. Packages are now waiting in their respectives
upload queues for approval in order to start building in -proposed for
the testing phase of the SRU.
Thanks again Victor
- Eric
--
You received this bug notification because you are a member of STS
Another note on the focal package of lua-lpeg ... (and this also implies
to debian) the src package still uses v7 debhelper compat version which
is 11 years old and obviously deprecated nowadays.
I have reported a bug against lua-lpeg debian as follows:
** Changed in: lua-lpeg (Ubuntu Eoan)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: lua-lpeg (Ubuntu Disco)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: lua-lpeg (Ubuntu Bionic)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in:
** Changed in: lua-lpeg (Ubuntu)
Status: In Progress => Fix Committed
--
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/1580385
Title:
[sts-sponsor]
Sponsored in focal.
# Nitpick:
I have appended the changelog to add the LP bug.
# Upstream project have no vcs, therefore no commit available. Upstream
just release tarballs.
# No merge/sync needed. Debian and Ubuntu package are already at same
version level.
# Since this is
** Changed in: lua-lpeg (Ubuntu)
Importance: Undecided => Critical
** Changed in: lua-lpeg (Ubuntu)
Importance: Critical => 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/1580385
** Changed in: lua-lpeg (Ubuntu)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: lua-lpeg (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
Sponsored for Xenial.
The package is now waiting for SRU approval in order to start building
in xenial-proposed for the testing phase of the SRU.
Thanks for your contribution Matthew !
** Tags removed: sts-sponsor sts-sponsor-slashd
--
You received this bug notification because you are a
** 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/1840686
Title:
Xenial images won't reboot if disk size is > 2TB when using GPT
Status in cloud-init:
Simon and I are working on delivering a more recent lds-client codebase
(ofc including the code to fix this particular bug) and modernising the
actual src package (e.g. compat v7 to v12) for focal.
Once everything is found in focal-release, we will SRU PR#57 and PR#70
into stable releases.
-
** Changed in: landscape-client (Ubuntu Eoan)
Assignee: (unassigned) => Simon Poirier (simpoir)
** Changed in: landscape-client (Ubuntu Disco)
Assignee: (unassigned) => Simon Poirier (simpoir)
** Changed in: landscape-client (Ubuntu Bionic)
Assignee: (unassigned) => Simon Poirier
$ pull-lp-source cups-filters xenial
debian/control:
.
Package: cups-filters
Architecture: any
Depends: ${shlibs:Depends},
${misc:Depends},
cups-filters-core-drivers (>= ${binary:Version}),
bc,
ghostscript (>= 9.02~),
imagemagick (>= 6.4~),
poppler-utils
$ pull-lp-source
$ pull-lp-source cups-filters xenial
debian/control:
.
Package: cups-filters
Architecture: any
Depends: ${shlibs:Depends},
${misc:Depends},
cups-filters-core-drivers (>= ${binary:Version}),
bc,
ghostscript (>= 9.02~),
imagemagick (>= 6.4~),
poppler-utils
$ pull-lp-source
** 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/1848210
Title:
ghostscript: ensure update of cups-filter
Status in cups-filters package in Ubuntu:
New
I will be more favourable to do the other way around by adding a
"Depends:" in cups-filters package for ghostscript version "X" ?
Especially if cups-filters always needs ghostscript ?
It will force ghostscript to get updated instead of making the package
install to fails/breaks.
At least it's
I will be more favourable to do the other way around by adding a
"Depends:" in cups-filters package for ghostscript version "X" ?
Especially if cups-filters always needs ghostscript ?
"Depends: ghostscript (>= CUPS_FILTER_VERSION)"
to force ghostscript to get updated instead of making the
** Also affects: mdadm (Ubuntu Ff-series)
Importance: Undecided
Status: New
** Changed in: mdadm (Ubuntu Ff-series)
Status: New => Confirmed
** Changed in: mdadm (Ubuntu Ff-series)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: mdadm (Ubuntu
[VERIFICATION XENIAL - Part 2]
* Feedback #3:
"
I also tested and now it works perfectly, I can count the seconds which I
configure for the handshake timeout and the connection is terminated exactly
when the handshake timeout expires
Great job!
"
--
You received this bug notification because
[VERIFICATION XENIAL]
* Feedback #1:
>From an impacted user:
"
They confirmed that from their perspective the test is OK, and the apache2
packages are delivering expected result
"
* Feedback #2:
>From SustEng Mauricio (mfo):
"
The backport in xenial-proposed worked exactly as eoan
(with the
** Description changed:
[Impact]
When running TCP Defensics suite which sends corrupt packages towards
vip__public port 443, the suite is hanging after the half suite because
there are no free connections. The connections will be in state
"established" ~ 2 hours.
1.2. Detailed
** Description changed:
## DRAFT ##
[Impact]
When running TCP Defensics suite which sends corrupt packages towards
vip__public port 443, the suite is hanging after the half suite because
there are no free connections. The connections will be in state
"established" ~ 2 hours.
** Description changed:
## DRAFT ##
[Impact]
When running TCP Defensics suite which sends corrupt packages towards
vip__public port 443, the suite is hanging after the half suite because
there are no free connections. The connections will be in state
"established" ~ 2 hours.
-
** Changed in: apache2 (Ubuntu Xenial)
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/1846138
Title:
backport mod_reqtimeout with handshake support
** Changed in: apache2 (Ubuntu Disco)
Status: New => Fix Released
** Changed in: apache2 (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: apache2 (Ubuntu Bionic)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of STS
** Changed in: apache2 (Ubuntu)
Status: New => Fix Released
** Changed in: apache2 (Ubuntu)
Assignee: Jesse Williamson (chardan) => (unassigned)
** Changed in: apache2 (Ubuntu Xenial)
Assignee: (unassigned) => Jesse Williamson (chardan)
** Description changed:
- Backport the
** Tags added: 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/1796501
Title:
systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes
Status in systemd
[STS-Sponsor]
Sponsored in Bionic.
Thanks Mauricio for your great work on this bug and the FTBFS situation.
- 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/1842437
Title:
Xenial:
[sts-sponsor]
Since this is a "HWE/new feature", please read
https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
and see if your patch fits inside the policy.
Also, I would like to see more justification/testings (detailed steps,
output, ...) using a micron nmve drive type, local
** Changed in: nvme-cli (Ubuntu)
Status: New => Fix Released
--
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/1838555
Title:
nvme-cli 1.5 in Bionic does not support Micron NVME drives
@mfo,
I will gladly resume the sponsoring as soon as LP: #1844504 is "Fix
Released" and util-linux builds fine.
Thanks for your good work on this Mauricio !
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
Sponsored in Bionic.
--
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/1836635
Title:
Bionic: support for Solarflare X2542 network adapter (sfc driver)
Status in debian-installer package in
LP: #1844504
** Tags added: ftbfs
--
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/1842437
Title:
Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem
with udev
Status
Maybe a kernel change between your successful built and my today
sponsoring build failure ?
--
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/1842437
Title:
Xenial: libblkid: fix
@mfo,
Unfortunately the build ftbfs as follow:
https://launchpadlibrarian.net/443016838/buildlog_ubuntu-xenial-amd64.util-linux_2.27.1-6ubuntu3.9_BUILDING.txt.gz
...
masks:
script: openpty failed: No such file or directory
Makefile:11211: recipe for target 'check-recursive' failed
make[3]:
** 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/1842437
Title:
Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem
with udev
Status in
** Description changed:
[IMPACT]
It has been brought to me the following:
Some hosts have started to cause UNKNOWN return values in Nagios for
checks on their disks. This is because these hosts are no longer
reporting their disks as part of the SNMP table hrStorageTable
** Description changed:
[IMPACT]
It has been brought to me the following:
Some hosts have started to cause UNKNOWN return values in Nagios for
checks on their disks. This is because these hosts are no longer
reporting their disks as part of the SNMP table hrStorageTable
There is discussion to push systemd 241 to Eoan:
https://launchpad.net/bugs/1841790
--
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/1668771
Title:
[SRU] systemd-resolved negative caching for
** 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/1681909
Title:
kdump is not captured in remote host when kdump over ssh is configured
Status in The
Hi Andrew Cloke,
Yes, I'm currently sponsoring D/B for cascardo/gpicolli.
Disco is already uploaded waiting for SRU team approval:
https://launchpad.net/ubuntu/disco/+queue?queue_state=1_text=makedumpfile
Bionic debdiff needs some rework before I do the final upload.
- Eric
--
You received
** 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/1681909
Title:
kdump is not captured in remote host when kdump over ssh is configured
Status in The
** Also affects: asterisk (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mailsync (Ubuntu)
Importance: Undecided
Status: New
** Also affects: prayer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
makedumpfile merge to "1:1.6.6-2ubuntu1" sponsored in Eoan.
I appended the changelog to add the entry block[0] currently found in
eoan-proposed that was missing to keep track of everything that has been done
on the package:
Since it was made by cascardo before 1:1.6.5-1ubuntu3 exist.
Note:
- I
Sponsored for Bionic.
* Patch already found in Cosmic onwards.
* Patch has been tested pre-SRU with an impact user.
* Nitpick: I have added the upstream bug link in the DEP3 header ->
+Bug-Upstream: https://github.com/ibus/ibus/issues/2002
Thanks Matthew !
** Bug watch added:
** Description changed:
[Impact]
The following has been seen in a VMware Horizon VDI. I cannot reproduce this
issue myself.
When a user interacts with any password field in Firefox, gnome-shell
and Firefox both freeze and the system becomes unusable. If you ssh into
the system
Quick update:
It seems to fail the same way with 1:1.6.5-1ubuntu2, so NOT introduced
by this SRU via 1:1.6.5-1ubuntu3
We still have to test the autopkgtest locally on ppc64el arch and
instrument/monitor the test to understand why no crash is found in
/var/crash at the end of the test.
--
You
Quick update
# excuses... page:
makedumpfile (1:1.6.5-1ubuntu2 to 1:1.6.5-1ubuntu3)
Maintainer: Louis Bouchard
0 days old
autopkgtest for kpatch/0.5.0-0ubuntu2: amd64: Ignored failure
autopkgtest for makedumpfile/1:1.6.5-1ubuntu3: amd64: Pass, arm64: Pass, armhf:
Pass, i386: Pass, ppc64el:
Sponsored for 'Eoan'.
We'll be able to start the SRU sponsoring as soon as it lands in
-releases.
Notes:
* Patch lands in debian unstable ~2 weeks ago :
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f
* Patch have been "Signed-off-by" by a member of
** Description changed:
[Impact]
* Kdump over network (like NFS mount or SSH dump) relies on network-
online target from systemd. Even so, there are some NICs that report
"Link Up" state but aren't ready to transmit packets. This is a
generally bad behavior that is credited probably
Marking Cosmic as 'Won't fix'.
Ubuntu 18.10 (Cosmic Cuttlefish) End Of Life reached on July 18 2019.
** Changed in: makedumpfile (Ubuntu Cosmic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the
Sponsored in stable release for D/C/B/X.
Note: The fix is already merged into Debian and Eoan (Current devel
release).
Thanks Steven for your patch contribution, and Ioanna for producing the
debdiffs and all the SRU related work.
Regards,
Eric
** Tags removed: sts-sponsor-slashd
--
You
xnox will upload to debian experimental and will sync to eoan.
I'll take care of the stable release once the above ^ is completed.
- Eric
** 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.
** Description changed:
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific
domain, further attempts at resolving A records for that same domain fail.
This has been fixed upstream in v240.
Sponsored for Bionic 'd-i'.
The new kernel version used "4.18.0-20" (aka HWE) and "4.15.0-50" are
both available in the archive for Bionic in -updates.
$ rmadison linux-image-4.18.0-20-generic
linux-image-4.18.0-20-generic | 4.18.0-20.21~18.04.1 | bionic-security |
amd64, arm64, armhf, i386,
Sponsored for Disco 'd-i'. - No-Change rebuild
Will review C/B 'd-i' soon (which involve master kernel change)
- 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/1817321
Title:
[sts-sponsor]
There is an SRU in progress for systemd already for Bionic. It will have
to wait for LP: #1814373 and #1825997 to be 'Fix Released' before
sponsoring that particular bug.
Thanks Heitor for your contribution.
Let's circle back later.
- Eric
--
You received this bug notification
Sponsoring for 'E'.
Considering libguestfs maintainer and Ioanna answers to my concern that
this code can never run outside the appliance and that can't create any
harm inside the appliance as well.
Also trusting that Ioanna will soon file a bug and submit the patch to
Debian as well.
-Eric
**
to continue my comment #16
Looking further and if I understand this correctly, this piece of code
seems to only operate inside supermin appliances which doesn't use
systemd inside it ?
Is there any other circumstances where this piece of code can be run
outside a non-systemd appliance ?
--
Thanks Ioanna for providing a patch and work with upstream maintainer.
I have some concern that I want to address before talking about sponsorship.
I haven't tested libguestfs, so my observation are only base on the patch you
have provided upstream, and my concern inside Ubuntu.
I would have
Ok I'll review the debdiff for 'Eoan' tomorrow.
Thanks Ionna.
--
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/1824236
Title:
supermin/liguestfs fails to configure network
Status in
Sponsored 'd-i' for Eoan, now that both hw-detect and partman-iscsi have
been built and land in release.
- Eric
** Changed in: debian-installer (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of STS
Sponsors, which is
Sponsored for Eoan, considering that Mauricio has submitted the patch to Debian
already.
debbugs are "bug watches" in the LP.
Everything looks good me.
The only thing missing is the d-i rebuild with no modification but that
have to wait until hw-detect/parman-iscsi are both built.
- Eric
**
** Changed in: partman-iscsi (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: partman-iscsi (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: hw-detect (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: hw-detect (Ubuntu Eoan)
Status:
[sts-sponsor]
I have some concern about the patch being more or less suggested by
upstream, but never merged upstream. I see they previously merge a
workaround for Ubuntu, can you discuss with them and see if that can be
merged again upstream ? I'm trying to avoid to have to carry a patch in
[sts-sponsor]
I have some concern about the patch being more or less suggested by
upstream, but never merged upstream. I see they previously merge a
workaround for Ubuntu, can you discuss with them and see if that can be
merged again upstream ? I'm trying to avoid to have to carry a patch in
I marked Trusty as 'Won't Fix' in it reached EOL.
--
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/1828467
Title:
[sru] remove juju-db stop/start service interactions
Status in sosreport
I marked Trusty as 'Won't Fix' as it reached EOL.
** Description changed:
[Impact]
The juju plugin will stop and start the juju-db service during data
collection.
sosreport should not impact running services, or attempt to recover them.
This has been reported upstream[0] and will
** Changed in: sosreport (Ubuntu Trusty)
Status: New => Won't Fix
--
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/1828467
Title:
[sru] remove juju-db stop/start service interactions
Sponsored for D/C/B/X.
Thanks Victor !
** Changed in: sssd (Ubuntu Xenial)
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/1572908
Title:
sssd-ad
Sponsored for 'eoan', considering the patch is merged upstream and
already part of debian.
Nitpick:
- Rename quilt patch d/p/GPO_CROND-customization.diff to
d/p/GPO_CROND-customization.patch
- Rework the DEP3 header
Note for next sponsoring (Disco debdiff) I haven't look others yet.
A quick
There is a debian->ubuntu sync right now in eoan-proposed.
I'll sponsor it once the actual sync is completed and found in eoan-
releases.
Meanwhile, could you please report a bug and forward the patch to debian
to make sure the problem is fix to prevent re-introducing the issue at
next
Sponsored for 'eoan' considering that the:
1) Both upstream fixes are merged upstream
2) Bug is reported in debian against resource-agents (debbugs #927311)
3) Eoan is now open (#ubuntu-release topic: ... Archive: Open | Eoan Release
Coordination...)
Nitpick:
d/changelog was mentionning
** Changed in: resource-agents (Ubuntu Eoan)
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/1825250
Title:
ethmonitor does not list interfaces
Sponsored in disco.
** Changed in: openldap (Ubuntu)
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/1821343
Title:
slapd process failure is not
** Description changed:
[Impact]
Systemd service reports slapd as active, even though it may have failed
[Description]
The slapd package for OpenLDAP is shipped with a SysV-style init script
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service
by generating
[sts-sponsor note]
I am concerned about just adding the service unit, and not making your package
work
with systemd, especially for maintainer scripts (may break package upgrade...
would be good to test and add this to the [test case].
May I suggest you look at debian/control and debian/rules
https://launchpad.net/ubuntu/+source/gdm3/+publishinghistory
Deleted Bionic proposedmaingnome 3.28.3-0ubuntu18.04.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/1817738
201 - 300 of 530 matches
Mail list logo
