The linked commit was included in 1.3~exp1 in yakkety
** Changed in: apt (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
This is somewhat expected. The code to setup partial was deprecated in
APT, we only set the Log in python-apt anymore.
I think I need to provide a binding for GetLock(), which is now supposed
to create the partial directory.
** Package changed: apt (Ubuntu) => python-apt (Ubuntu)
** Changed in:
As I wrote two months ago, this seems to be wontfix for xenial, at least
for know. We can eventually re-evaluate that at some point, once we can
grant acceptions in 1.3 or 1.4 ,but it does not seem likely; as the
changes are likely very invasive.
** Changed in: apt (Ubuntu Xenial)
Status:
Moving this to the xenial series where it belongs.
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह,
** Also affects: apt (Ubuntu Xenial)
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
https://bugs.launchpad.net/bugs/1573547
This also fails with the upgrade to xenial of course, as stated in bug
1662115. So we can either just SRU the patch (if it applies - I hope it
does), or just save ourselves some trouble and update the package
wholesale from 1.59-6 to 1.60-3:
https://anonscm.debian.org/git/collab-
ohn R. Lenton ]
* bash-completion: Only complete understood file paths for install
(LP: #1645815)
[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport
[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
Public bug reported:
In 1.2.15 the unit tests (which run at build time) fail with an error
message in the atomic files test, because I picked a commit that
improved the error handling a bit (a previous error now propagates into
further calls).
I'll revert that for 1.2.16, as it depends on
This never affected any other release than xenial
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
OK, the reason this happens is that some of your key files are not
readable (I'm not sure, but it might be running as _apt). The commit
mentioned introduced a regresssion in that it does not ignore failures
from unreadable key files.
This was fixed in 1.3~rc3 in commit
Let's clean this up.
** Package changed: python-apt (Ubuntu) => apt (Ubuntu)
** Changed in: apt (Ubuntu)
Status: Triaged => Fix Released
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: gdebi (Ubuntu Xenial)
Importance: Undecided
the
kernels not to be autoremoved or something. We have this code in Debian
testing and unstable since 1.3~pre1 early July and its in yakkety, and
are reasonably sure it's stable now.
apt (1.2.15) xenial; urgency=medium
(Most bugfixes until to and including 1.3.1)
[ Julian Andres Klode ]
* methods
** No longer affects: apt (Ubuntu Trusty)
** Changed in: apt (Ubuntu Yakkety)
Status: Confirmed => Triaged
** Changed in: apt (Ubuntu Xenial)
Status: Confirmed => Triaged
** Changed in: apt (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug
These are different bugs.Or rather, we definitely fixed the
if float(percent) != self.percent or status_str != self.status:
Aug 8 13:49:44 ubuntu /plugininstall.py: ValueError: could not convert string
to float: '0,'
thing here. And to keep our sanity (especially WRT to the SRU fixing
** No longer affects: gdebi (Ubuntu)
** No longer affects: gdebi (Ubuntu Xenial)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1592817
So, we've seen this on yakkety and zesty from what I can tell, but it
likely also affects earlier versions. I plan to basically SRU -4 to
yakkety and zesty, but I'd like to get some more information for the
xenial and trusty, as that's a bit more involved (especially the
latter).
There are also
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Xenial)
Importance:
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Xenial)
Status: New => Triaged
** Changed in: apt (Ubuntu Xenial)
Importance: Undecided => Low
--
You received this bug notification because you are a member of नेपाली
भाषा
OK, so the problem is that the triggers for the old package could be
triggered, and that apparently needs some Breaks magic
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854554#62
** Changed in: cracklib2 (Ubuntu)
Status: Fix Released => Triaged
** Bug watch added: Debian Bug tracker
** Bug watch added: Debian Bug tracker #861357
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861357
** Also affects: apt (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861357
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
** Bug watch added: Debian Bug tracker #863911
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863911
** Also affects: unattended-upgrades (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863911
Importance: Unknown
Status: Unknown
--
You received this bug
Public bug reported:
[Impact]
apt-daily.timer is enabled on every boot and pulls in network-online.target via
Wants and After. While nothing has an After=apt-daily.timer (or rather an
After=timers.target) and this should thus not impact boot performance, the
rc-local.service specifies an
ool
[ David Kalnischkies ]
* use port from SRV record instead of initial port
=> Might have picked the wrong port
[ Julian Andres Klode ]
* Reset failure reason when connection was successful
=> Some failures were only treated as warnings, not errors
* debian/gbp.c
We should SRU that to xenial as 1.60-4ubuntu1~16.04.1 for the HWE
kernels.
** Also affects: ndiswrapper (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: network-manager (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu Xenial)
Status: New => Triaged
** Changed in: network-manager (Ubuntu
Adding tasks for down to xenial, but not sure what we want to do. I
don't foresee any trouble with that change, but we can't test it, and
even if we get a failing upgrade, we can only test for that release.
** Changed in: menu (Ubuntu)
Status: In Progress => Fix Committed
** Also affects:
** Bug watch added: Debian Bug tracker #900838
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900838
** Also affects: menu (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900838
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Yup. We probably want an easier test case, though?
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Xenial)
Status: New => Triaged
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह,
** Also affects: apt (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Artful)
Status: New => In Progress
** Changed in: apt (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of
** Also affects: python-pyvmomi (Ubuntu Xenial)
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
OK, I checked it myself now, bionic + artful are OK, so all we need is
the backport to xenial.
** Also affects: util-linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu Artful)
Status: New => Fix Released
** Changed in: util-linux (Ubuntu)
OK, so I need to dig a bit further into this. I think if I move the if I
break things elsewhere. IIRC, I added the if that early because, when
apt received a redirect with Content-Length: 0, it started hanging, and
that fixed it. But maybe it breaks some other stuff now.
** Changed in: apt
decided => High
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: apt (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: apt (Ubuntu Artful)
Assignee: (unassigned) => Julian Andres Klode
OK, so:
xenial: affected
artful, bionic: NOT affected
So I might just want to revert this commit in an apt 1.2.26 release and
look at it again later.
** Changed in: apt (Ubuntu Artful)
Status: New => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा
@Bojan The fix would have been in 1.4.8, but zesty is not supported
anymore - please upgrade to artful.
** Changed in: apt (Ubuntu Zesty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is
Same for bionic with:
Get:17 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64
intel-microcode amd64 3.20180425.1~ubuntu0.18.04.2 [1143 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64
amd64-microcode amd64 3.20180524.1~ubuntu0.18.04.2 [32.3 kB]
** Tags
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-menus (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed
Nothing actionable here for apt, so I'll close this. We should consider
making frontend locking more flexible for scripts using apt, though, so
scripts can hold the lock all the time and drive apt.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification
Fixed in 1.7.0~alpha1 in cosmic
** Changed in: apt (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
** Changed in: pike7.8 (Ubuntu)
Status: New => Fix Released
** Changed in: pike7.8 (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions:
** Changed in: pike7.8 (Ubuntu Xenial)
Status: New => In Progress
** Changed in: pike7.8 (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: pike8.0 (Ubuntu)
Status: New => Fix Released
** Changed in: pike8.0 (Ubuntu Bionic)
Cherry-picked the change into xenial's 1.2.y branch for the next SRU.
Will do that in trusty too.
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects:
Marking gosa as Won't fix, as newer versions moved to interest-await
explicitly. The plugins depend on gosa, so the trigger being await is
fine.
** Changed in: gosa (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: gosa (Ubuntu)
Assignee: Łukasz Zemczak (sil2100) =>
Nothing installs the files that trigger reconf-inetd, so not fixing
that.
** Changed in: reconf-inetd (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: reconf-inetd (Ubuntu Bionic)
Status: Triaged => Won't Fix
** Changed in: reconf-inetd (Ubuntu Xenial)
Status: Triaged
** Also affects: guile-2.2 (Ubuntu)
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
https://bugs.launchpad.net/bugs/1780996
guile-2.2 is also affected by these triggers, but probably not that
urgent, as it's not in xenial and not used as much as 2.0 in
bionic/cosmic.
** Changed in: guile-2.2 (Ubuntu)
Status: New => Triaged
** Changed in: guile-2.2 (Ubuntu Xenial)
Status: New => Triaged
** Changed in:
** Description changed:
+ [Impact]
+ Some applications, like unattended-upgrades or update-manager, reopen the apt
cache. They also keep around old apt.Package objects however, and operate on
them after reopening. Under the hood, this means that apt_pkg.Package objects
belonging to an old
** Description changed:
- == xenial / trusty ==
- [Impact]
- Some applications, like unattended-upgrades or update-manager, reopen the apt
cache. They also keep around old apt.Package objects however, and operate on
them after reopening. Under the hood, this means that
Public bug reported:
This is a bug collecting all remaining packages that need to be
converted to noawait in xenial or bionic.
[Impact]
"await" triggers are run before a package is configured. If B activates A, then
A's trigger code in the postinst must be run before A can be configured.
Missing in this bug:
kubuntu-settings
ubuntu-gnome-defaults/xenial
ubuntu-mate-artwork/xenial
these are tracked in bug 1750465.
** Also affects: hicolor-icon-theme (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mate-icon-theme (Ubuntu)
Importance: Undecided
** Changed in: mate-icon-theme (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: mate-icon-theme (Ubuntu)
Status: New => Fix Released
** Changed in: mate-icon-theme (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: mate-i
** Changed in: appstream (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: appstream (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in
** Changed in: gdk-pixbuf (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: gdk-pixbuf (Ubuntu)
Status: New => Fix Released
** Changed in: gdk-pixbuf (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: gdk-pixbuf (Ubun
ntu Bionic)
Status: New => Fix Released
** Changed in: packagekit (Ubuntu Xenial)
Status: New => In Progress
** Changed in: appstream (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: appstream (Ubuntu)
Assignee: Julian Andres Kl
** Changed in: postgresql-common (Ubuntu Xenial)
Status: New => Triaged
** Changed in: postgresql-common (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: postgresql-common (Ubuntu Bionic)
Status: New => Fix Released
*
clutter-imcontext declares an interest on /usr/lib/clutter-
imcontext/immodules, but no package ships files in there, so not fixing
that in a stable release. Not sure about devel.
** Changed in: clutter-imcontext (Ubuntu Xenial)
Status: Triaged => Won't Fix
** Changed in:
** Changed in: dochelp (Ubuntu Xenial)
Status: New => Triaged
** Changed in: dochelp (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: dochelp (Ubuntu)
Status: New => Fix Released
** Changed in: dochelp (Ubuntu Bionic)
St
** Changed in: syslog-ng-incubator (Ubuntu)
Status: In Progress => Fix Released
** Changed in: bumblebee (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: django-countries (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: maxima (Ubuntu Bionic)
** Changed in: wokkel (Ubuntu Xenial)
Status: New => In Progress
** Changed in: wokkel (Ubuntu Bionic)
Status: New => In Progress
** Changed in: wokkel (Ubuntu)
Status: In Progress => Fix Released
** Changed in: bumblebee (Ubuntu Xenial)
Status: New => In Progress
** Also affects: python-apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: update-manager (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: python-apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects:
I'm not sure when we fixed that, but we did. So bionic works fine. Not
sure about artful.
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Xenial)
Status: New => Triaged
** Bug watch added: Debian Bug tracker #870675
I think so, but I don't think it's worth pushing out an update just for
that change. It's been broken since forever, so it's not like it's
fixing a regression or something; so I'd probably wait for something
else to attach it to.
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
t; Fix Committed
** Changed in: update-notifier (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: update-notifier (Ubuntu Xenial)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of नेपाली
भाषा
** Changed in: ndiswrapper (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1724869
Title:
Public bug reported:
[Impact]
Releases prior to cosmic mark almost all packages manually installed, meaning
that obsolete packages are not autoremoved when they should. We fixed this in
cosmic, in trunk r1695, by including a new script that marks as automatically
installed all dependencies of
It actually did not fix the issue.
** Changed in: apt (Ubuntu)
Status: Fix Released => Triaged
--
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:
[Impact]
The switch to frontend locking in 1.2.28/1.6.5/1.7~ caused scripts registered in
DPkg::Pre-Install-Pkgs
DPkg::Pre-Invoke
DPkg::Post-Invoke
To be run with the frontend lock held. This caused problems with some
installer packages like libdvd-pkg which install a
Public bug reported:
[Impact]
foo
[Test case]
bar
[Regression potential]
baz
** Affects: python-apt (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: python-apt (Ubuntu Xenial)
Importance: Undecided
Status: Triaged
** Affects: python-apt (Ubuntu
** No longer affects: dpkg (Ubuntu)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1781169
Title:
frontend locking
Status in apt package
** Also affects: packagekit (Ubuntu Xenial)
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:
[Impact]
PackageKit needs an adjustment for frontend locking, so it does not release the
frontend lock during dpkg invocations, but only the normal dpkg lock.
[Test case]
1. Install a package
2. Modify prerm to sleep
3. Remove package via pkcon and check that packagekitd
Oh misread, xenial was not affected.
** Changed in: packagekit (Ubuntu Xenial)
Status: New => Invalid
** No longer affects: packagekit (Ubuntu Xenial)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching
dpkg is moving to its own bug to be able to better track the SRUs
** No longer affects: dpkg (Ubuntu Xenial)
** No longer affects: dpkg (Ubuntu Bionic)
** Summary changed:
- frontend locking
+ apt frontend locking
--
You received this bug notification because you are a member of नेपाली
भाषा
Public bug reported:
[Impact]
Frontends of dpkg such as apt and programs using the apt libraries currently
acquire the dpkg "lock" lock file. They need to release it before running dpkg,
as dpkg also acquires it. Therefore, there is a race condition: In case the
application needs to run dpkg
how far code relies on that regression. That said,
any potential regression should be easily noticable, as it would be a
case of not unlocking where we were unlocking before.
** Affects: apt (Ubuntu)
Importance: High
Assignee: Julian Andres Klode (juliank)
Status: In Progress
** Affects
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is
** No longer affects: apt (Ubuntu)
** No longer affects: apt (Ubuntu Xenial)
** No longer affects: apt (Ubuntu Artful)
** No longer affects: apt (Ubuntu Bionic)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Broken again in disco, let's update the state.
** Also affects: linux (Ubuntu Disco)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: Fix Released
** Also affects: linux-hwe (Ubuntu Disco)
Importance: Undecided
Status: Confirmed
** Also affects: linux
Public bug reported:
[Impact]
Backport auth.conf.d support to allow specifying per-repository authentication
data in separate files, so packages can setup authenticated repositories.
[Regression potential]
We ignore errors from opening auth.conf.d files, so regressions can only occur
when
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-meta (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-meta-hwe (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu
@Mathew Hodson please stop messing with tasks. It's important we have
those invalid tasks to say that it does not apply to that branch vs. we
just forgot about it.
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Trusty)
Status:
SRUs uploaded for bionic and cosmic. Since we do not use packagekit in
gnome-software in xenial, not fixing it there.
Also not fixing it in trusty, as it's close to EOL.
** Changed in: packagekit (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: packagekit (Ubuntu Bionic)
** Changed in: apt (Ubuntu Trusty)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1815760
Title:
Sure
** Changed in: apt (Ubuntu Disco)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1814727
** Description changed:
[Impact]
These are not driven from a direct user experience, but are related to other
developments:
(1) unattended-upgrades could use the never pinning to disable
repositories rather than switching candidates. That would simplify code
quite a bit.
(2)
** Also affects: apt (Ubuntu Trusty)
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
https://bugs.launchpad.net/bugs/1815760
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux-meta (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux-meta-hwe (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Xenial)
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Cosmic)
Importance:
Yes, I know they're broken in xenial, and it's fixed in git, and will be
part of the next SRU.
** Changed in: apt (Ubuntu Bionic)
Status: New => Invalid
** Changed in: apt (Ubuntu Cosmic)
Status: New => Invalid
** Changed in: apt (Ubuntu Trusty)
Status: New => Invalid
--
Public bug reported:
[Impact]
Dpkg::Post-Invoke is run only when dpkg had to be run. We'd like to be able to
show some extra output even if no changes had been made. Imagine "the user
disabled the security repo, and does not get any updates shown scenario" - we'd
like to be able to tell them
Public bug reported:
[Impact]
We want to write some scripts for apt that run on update if apt shows an update
count, to provide further details about the new cache.
[Test case]
Specify a APT::Update-Post-Invoke-Stats script and check that
(1) it shows in apt update
(2) it does not show in
Public bug reported:
[Impact]
The last SRU introduced a regression in error handling, where apt_pkg.Error is
being caught - but that class is not available in xenial - it still uses
SystemError
[Test case]
Run python3 -c "import apt; apt.Cache().update()" while running apt
update.
You should
** Also affects: apport (Ubuntu Xenial)
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
https://bugs.launchpad.net/bugs/1766740
This was fixed before 1.6, so only xenial and trusty affected at most.
** Changed in: python-apt (Ubuntu)
Status: In Progress => Fix Released
** Also affects: python-apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: python-apt (Ubuntu Xenial)
Status:
** Changed in: gnome-menus (Ubuntu)
Status: Confirmed => Invalid
** Changed in: gnome-menus (Ubuntu Xenial)
Status: Confirmed => Invalid
** Changed in: gnome-menus (Ubuntu Bionic)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member
I think I vaguely recall some issues that occured after this SRU in
bionic, but I'm not sure anymore. It certainly means that tools stop
working for people behind proxies in quite a few cases (e.g. various apt
proxies not allowing https connect; or access to changelogs.ubuntu.com).
So we need to
Definitely bionic, I just can't recount the alphabet order today; I
meant to say it was also fixed in artful (not "cosmic")
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: apt
** Also affects: cryptsetup (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: cryptsetup (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to
This should have been fixed in xenial by the merge from unstable. Nvidia
stuff is likely a different bug. If you experience this in a later
release, consider opening a new bug, thanks!
** Changed in: plymouth (Ubuntu Xenial)
Status: Triaged => Fix Released
** Changed in: plymouth (Ubuntu)
Public bug reported:
[Impact]
cache.commit() does not release all the locks it acquires as part of
committing. This is a regression of locking fixes in bug 1795407.
[Test case]
This script should work:
#!/usr/bin/env python
import apt
import subprocess
cache = apt.Cache()
pkg = cache["hello"]
1 - 100 of 127 matches
Mail list logo
