Michael, are you still actively working on this issue?
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
Public bug reported:
Bug 1849682 tracks the temporarily revert of the fix for this issue,
while this bug tracks the re-application of that fix once we have a full
solution.
Users of RAID0 arrays are susceptible to a corruption issue if:
- The members of the RAID array are not all the same
I just tried to reproduce the bug as outlined in the bug description. I
can confirm it is now fixed and working as expected. I'm marking the
snappy task as fix released.
** Changed in: snappy
Status: In Progress => Fix Released
--
You received this bug notification because you are a
I inspected snapd and noticed that we don't invoke "userdel" or
"deluser" in any production code. We have some tests that do use it and
we now support --extrausers there.
I'm inclined to mark the snappy task as fix released, given that we
inherit the relevant tools from core and core18 snaps
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको
This has been fixed and is available in snapd for multiple releases now.
I'm marking it as fix released.
** Changed in: snappy
Status: In Progress => Fix Released
** Project changed: snappy => snapd
--
You received this bug notification because you are a member of नेपाली
भाषा
This bug was fixed while snap-confine was a separate package. I'm
marking the snappy task as fix-released.
** Changed in: snappy
Status: In Progress => Fix Released
** Project changed: snappy => snapd
--
You received this bug notification because you are a member of नेपाली
भाषा
This bug was fixed in the package python-certbot -
0.27.0-1~ubuntu18.04.1
---
python-certbot (0.27.0-1~ubuntu18.04.1) bionic; urgency=medium
* Backport to bionic (LP: #1837673):
- d/letsencrypt.postrm: purging the transitional package shouldn't
remove the logs (Closes:
This bug was fixed in the package python-certbot -
0.27.0-1~ubuntu16.04.1
---
python-certbot (0.27.0-1~ubuntu16.04.1) xenial; urgency=medium
* Backport to xenial (LP: #1837673):
- d/control, d/compat: go back to debhelper 9, and drop R³
-
This bug was fixed in the package python-acme - 0.31.0-2~ubuntu18.04.1
---
python-acme (0.31.0-2~ubuntu18.04.1) bionic; urgency=medium
* Backport packaging to build on Ubuntu Bionic (LP: #1836823)
python-acme (0.31.0-2) unstable; urgency=medium
* Backport POST-as-GET support
This bug was fixed in the package python-acme - 0.31.0-2~ubuntu19.04.1
---
python-acme (0.31.0-2~ubuntu19.04.1) disco; urgency=medium
[ James Hebden ]
* Backport packaging to build on Ubuntu Disco (LP: #1836823)
[ Andreas Hasenack ]
* d/p/series: drop unused -p1
python-acme
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
12 matches
Mail list logo
