Public bug reported:
The following fixes are in 2.32 and also need to be backported to
bionic, artful, and xenial:
https://github.com/karelzak/util-linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd
https://github.com/karelzak/util-linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2
This
Closing this as that's a kernel thing, and it was reverted anyway as
pointed out.
** Changed in: util-linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
Merged 2.32, should be building and hitting proposed soon.
** Changed in: util-linux (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
** Description changed:
- The following fixes are in 2.32 and also need to be backported to
- bionic, artful, and xenial:
+ [Impact]
+ lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU
frequency arrays and can call atof() on them, leading to crashes. It seems
that's
Public bug reported:
[Impact]
systemd used to pre-depend on the libraries used by systemctl or something, but
now systemctl uses libsystemd-shared, and there are no pre-depends for that,
meaning that systemctl fails in maintainer scripts of other packages.
[Test case]
Grab the apt-clone file
xenial: 3.4 prints (null), 3.5 crashed, and 3.6 fixed it -> verified
artful: 4.1 in release crashes; 4.2 fixes it -> verified
bionic: 3 in release crashes, 3.1 fixes it -> verified
Sample log from bionic belog:
jak@jak-t480s:~/Downloads$ echo lscpu -s /home/jak/Downloads/segvtest | lxc
exec b
** Tags removed: verification-failed-xenial
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1732865
Title:
ppaid...@in.ibm.com Can you check with the new util-linux in proposed
(2.27.1-6ubuntu3.6)? This should fix the crash.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
Test case
** Attachment added: "segvtest.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1771345/+attachment/5140350/+files/segvtest.tar.gz
** Description changed:
[Impact]
lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU
frequency arrays
OK, so archive.ubuntu.com has 4 and 4 A entries, meaning that
16.04 waits 16 minutes (8 * 2 minutes)
18.04 waits 2 minutes, 2 seconds (2 minutes + 8 * 250 milliseconds)
Now we can shorten that further to one of the following:
* 12 seconds (10 + 8 * 250 ms)
* 22 seconds (20 + 8 * 250 ms)
*
Upstream now contains more fixes:
https://github.com/karelzak/util-linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd
https://github.com/karelzak/util-linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2
So artful, bionic, cosmic should be broken as well, at least if CPU#0 is
offline.
--
bionic:
tracker/i386: retriggered, passed
tracker/armhf: retriggered, passed
systemd/amd64: timeout in boot-smoke test -> does not seem to be a regression,
for example, the most recent boot-smoke also fails.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
germand/armhf also fails when triggered by gearmand/1.0.6-5.1build2, so
it's broken in release.
In summary, I don't think any of the autopkgtest regressions are related
to these SRUs. It was not expected anyway, given that they only change
lscpu code.
--
You received this bug notification
xenial:
nplan/{amd64,i386}: timed out waiting for NetworkManager to settle down, common
error
nplan/armhf: times out during reboot, also seen for nplan/0.32~16.04.5
postgresql-9.5/armf: fails with stderr "Not all processes could be identified"
since 2016-10-17
gearmand/armhf: Unknown failure,
artful:
nplan/amd64: time outs, reproduce with other triggers too (like
systemd/234-2ubuntu12.4)
open-iscsi/amd64: times out waiting for network to be configured (same for
cloud-utils/0.30-0ubuntu2.1 and others)
network-manager: time outs in failure, also happen with systemd trigger, hence
not
do-release-upgrade worked as well, so what I'd need for further
investigation is /var/log/dpkg.log from after the failed upgrade. That
might be dpkg.log.1 or dpkg.log.2 or something.
** Changed in: apt (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because
I don't see how we can achieve an overall timeout. We only have per
connect() timeouts available, and we run multiple apt processes /
fetches. We can limit the individual connect() timeout to 30s, but
overall? I think we do one attempt for archive.ubuntu.com / mirror and a
another for security, so
Ran the dist-upgrade:
with bionic, bionic-updates:
Unpacking bluez (5.48-0ubuntu3) over (5.37-0ubuntu5.1) ...
systemctl: error while loading shared libraries: libcryptsetup.so.12: cannot
open shared object file: No such file or directory
with bionic, bionic-updates,
It seems we are experiencing a bug in apt in bionic WRT the 90s timeout.
With happy eyeballs, we added a new place where stuff can timeout; and
we did not mark these IP addresses as failed, hence they were always
retried, and thus you saw it attempting to connect 3 times to
tw.archive.ubuntu.com.
I don't think we can realistically go lower than 2x30s - I think the
intention is to add the mirror and security separately and comment them
out if they don't work or something, so they need to be in seperate apt
runs. Unless, of course, we write a tool in python or something that
does update
For the apt side, that's the first commit in
https://salsa.debian.org/apt-team/apt/merge_requests/18/
I'll also upload that to bionic eventually; but xenial would also need
the happy eyeballs changes, which were a bit large (although, isolated).
--
You received this bug notification because
Oh, you got a working result? I tried aspcud in various variants, but I
don't get any solutions. https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=897330
Of course the autopkgtest-sat-dep package should have versioned
dependencies and/or on the command-line, versions should be specified
IMO.
**
I restored the apt-clone file in a container (with rc-policy.d disabling
services), tried a straight apt dist-upgrade, and that worked. Will
check with do-release-upgrade tomorrrow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Minimal test case, unpacking python3-minimal and python3-apt from artful
on xenial:
root@lp1768379:~# dpkg --unpack
/home/jak/Downloads/python3-minimal_3.6.3-0ubuntu2_amd64.deb
(Reading database ... 25653 files and directories currently installed.)
Preparing to unpack
I have not heard about any regressions in proposed, so I think we should
start releasing the update for bionic and artful now and watch out for
those in the release pocket. If we don't see issues with that, we can
then roll out xenial next week to give it some more time to mature in a
less used
** Tags removed: verification-needed-artful verification-needed-bionic
** Tags added: verification-done-artful verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Empty Packages files work just fine, e.g. cosmic-updates is empty and
works. Check whether your Release file is correct, listing the
uncompressed file as 0 bytes and debug with -o Debug::Acquire::http=1
and/or -o Debug::pkgAcquire::Worker=1 why the file is being downloaded
and that fails.
**
I also ran unattended-upgrades and aptdcon --system-upgrade, both of
which performed normally.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1773316
Title:
Object of
Fix works fine:
root@bionic:~# python3 -c "import apt; c=apt.Cache(); p=c['aptitude'];
c.open(); p.mark_install()"
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/apt/package.py", line 1469, in
mark_install
** Changed in: apt (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1773992
Title:
apt-key adv should gpgconf --kill all
I think it's a fundamental problem that interest triggers are not
considered for ordering packages, and hence cannot be used reliably.
Fixing this bug is probably a matter of making all the triggers noawait,
although I can't reproduce it, so I can't test any SRU.
--
You received this bug
** Changed in: apt (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1766542
Title:
Installation blocks when the machine is
I could not reproduce this with that file in my lxd testing setup
either. It might depend on PPA packages changing the order. That said,
fixing the trigger to be noawait is definitely the right thing to do-
** Changed in: menu (Ubuntu)
Status: Confirmed => In Progress
--
You received
** Description changed:
+ [Impact]
+ Breaks some upgrades, depending on install order.
+
+ [Test case]
+ N/A. After consultation with the dpkg maintainer and investigating the
situation, it's reasonably safe to assume that noawait is the right thing to do:
+
+ * the intended use for the
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
** Changed in: menu (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1768905
Title:
package menu 2.1.47ubuntu2 failed to
python 3.7 is not a supported version, hence modules are not built for
it.
** Changed in: python-apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
So apport needs to catch the exception and do nothing / not register an
excepthook on unsupported python versions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1774843
** Description changed:
+ [Impact]
+ python-apt 1.6 raises an exception when objects of an old cache are passed to
a apt_pkg.DepCache methods for a different cache. Prior to that, those would
either segfault, succeed, or silently operate on a different object, as they
use package/version ids,
*** This bug is a duplicate of bug 1773316 ***
https://bugs.launchpad.net/bugs/1773316
** This bug has been marked a duplicate of bug 1773316
Object of different cache passed as argument to apt_pkg.DepCache method
--
You received this bug notification because you are a member of Ubuntu
** Also affects: python-apt (Ubuntu)
Importance: Undecided
Status: New
** Also affects: python-apt (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: update-manager (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: python-apt
** Summary changed:
-
/usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install
+ Object of different cache passed as argument to apt_pkg.DepCache method
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
So, we should do gpgconf --kill for everything and not just for gpg-
agent? Hmm. Sounds like a job for a for loop.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1773992
Title:
** Changed in: apt (Ubuntu)
Status: New => In Progress
** Changed in: apt (Ubuntu)
Importance: Undecided => Medium
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubu
In order to debug this further, we need a copy of /var/log/apt/term.log.
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Won't fix as before
** Changed in: apt (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/710618
Title:
Please support libkibi
Status
Closed as it has been fixed as mentioned in previous comment.
** Changed in: apt (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
figuration system)
- Support for attaching a terminal to the underlying dpkg call
.
This package contains the aptd script and all the data files required to run
the daemon. Moreover it contains the aptdcon script, which is a command
line client for aptdaemon. The API is not s
We made things work better for unreadable files, so I think that's fixed
in cosmic and probably bionic.
** Changed in: apt (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I think we have gotten better at this, but it seems pointless to
constantly keep a bug open here. When we add a new symbol it is usually
not used by anything and it will eventually get added to the file.
If there are any specific instances where packages use new symbols we do
not declare, file a
*** This bug is a duplicate of bug 1697120 ***
https://bugs.launchpad.net/bugs/1697120
** This bug is no longer a duplicate of bug 975312
duplicated sources list entry
** This bug has been marked a duplicate of bug 1697120
artful's apt-file and aptitude complains about Ubuntu
*** This bug is a duplicate of bug 1697120 ***
https://bugs.launchpad.net/bugs/1697120
** This bug has been marked a duplicate of bug 1697120
artful's apt-file and aptitude complains about Ubuntu sources.list
--
You received this bug notification because you are a member of Ubuntu
Touch
These days we mostly fetch based on what the InRelease file tells us, so
this message is seen less. In any case, it's not an error, otherwise it
would tell you, it's just progress logging.
** Changed in: apt (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification
** Changed in: apt (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1723761
Title:
unattended-upgrade hangs on shutdown when
** Also affects: apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Bionic)
Status: New => In Progress
** Changed in: apt (Ubuntu Bionic)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of
Closing this, as that's been fixed with by-hash repository support in
apt.
** Changed in: apt (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
This should be fixed in apt since some time as well, so closing.
** Changed in: apt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Public bug reported:
[Impact]
System lock unrefing is broken, off-by-one error. Locking twice opens a second
fd for the lock file, and the old fd gets lost and remains open for the
remaining duration of the program
[Test case]
TODO
[Regression potential]
TODO
** Affects: apt (Ubuntu)
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 Ubuntu
Touch seeded packages,
)
(LP: #1762766)
[ Julian Andres Klode ]
* Fix lock counting in debSystem (LP: #1778547)
* apt.conf.autoremove: Catch some new Ubuntu module packages (LP: #1778551)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt
** Changed in: apt (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1778547
Title:
Broken system lock counting
Status in
** Description changed:
- When the machine is behind a proxy server, the installation will block
- for a while (several minutes) to retrieve the package lists. The
- timeouts are too long and makes user feels the machine may have some
- problems.
+ [Impact]
+ APT takes a long time to notice when
** Description changed:
[Impact]
System lock unrefing is broken, off-by-one error. Locking twice opens a
second fd for the lock file, and the old fd gets lost and remains open for the
remaining duration of the program
[Test case]
- TODO
+
+ Executing the following script should show
** Description changed:
+ [Impact]
+ dirmngr processes are left hanging around
+
+ [Test case]
+ apt-key adv --recv-keys "8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092"
< /dev/null ; ps aux
+
+ should not show a dirmngr process after exit (except for any that was
+ there before running
** Changed in: apt (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1766542
Title:
Installation blocks when the machine is
Not sure if bug or feature. Will need to investigate a bit more
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1778366
Title:
apt.package.Version.raw_description
OK, so let's roll out xenial as well. We waited our week.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: apt (Ubuntu)
Status: New => In Progress
** Changed in: apt (Ubuntu)
Importance: Undecided => High
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubu
** 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
** Changed in: apt (Ubuntu Artful)
Status: Confirmed => In Progress
** Changed in: apt (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
** Changed in: apt (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1762766
Title:
apt-get update hangs when
The system seems to be in a broken state. awk is pseudo-essential, as
base-files depends on it, so it should not be (possible to) removed
(it).
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
*** This bug is a duplicate of bug 1764858 ***
https://bugs.launchpad.net/bugs/1764858
** This bug has been marked a duplicate of bug 1764858
Can't update / install / delete packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: apt (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1764858
Title:
Can't update / install / delete packages
Thanks for your bug report. Unfortunately, the log files show that your
install did not complete - it failed to install the bootloader; probably
due to being booted in EFI mode and installing to a disk that is missing
an ESP partition.
To solve the issue, reinstall from the final 18.04 image
@Dave Goldsbrough
Thank you for your suggestion, but unfortunately i tried this approach
already multiple times and it didn't help. I also thought it probably is
an issue due to battery saving mode so I tried the following command
without any positive result:
sudo sed -i 's/wifi.powersave =
This is a safety check added in python-apt to prevent old package
objects being reused in new (dep)caches. since the cache operates on
package ids, and the package ids might change, there are three things
that can happen:
(1) If # of packages in new cache < # in old cache: SEGV
(2) If id changed,
libvirt-bin should not be necessary. gnome-boxes recommends qemu-
system-x86 so it should be installed on most systems; and libvirt-daemon
recommends qemu-kvm so that should be installed too. Both are not
integral parts of gnome boxes though, it works fine without it (e.g.
managing remote
gitlab-ee is a third party package and failed to restart during upgrade
or whatever. I suggest you contact them for further help.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I have verified that none of these failures are regressions; they all
appear in previous apt uploads/run against other triggers too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Public bug reported:
[Impact]
This release fixes the test suite failures with dpkg 1.19, updates two
translations, fixes an error message, and finally makes apt-key not fail
silently if some files are in the wrong format.
[ Julian Andres Klode ]
* travis: CI: Test 1.5.y on artful
* Fix
** Changed in: apt (Ubuntu)
Importance: Undecided => Low
** Changed in: apt (Ubuntu)
Importance: Low => Medium
** Changed in: apt (Ubuntu)
Status: Confirmed => In Progress
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Bug
** Changed in: apt (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/310262
Title:
APT::Acquire::Retries only applies to
Well the virtualbox.list file has a wrong second line as the error
message says, you probably have to delete this line.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: apt (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/937951
Title:
Dir::Cache::archives="" places archives in /
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1613184
Marked xenial as verified, because, while the problem itself does not
exist, it still fixes the same underlying bug from an API perspective.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1734104
Title:
'upgrade' in bio
** Changed in: apt (Ubuntu)
Status: New => Triaged
** Changed in: apt (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1734104
Really? It should print that it could not reach the server. Transient
errors like that are ignored success-state wise so you don't end up with
tons of error messages when you are offline or your connection is
broken. I want to rework this eventually to give more control on what
constitutes an
So, that's not a bug then. I eventually want to add a feature where you
can switch between a one-source-must-update and a all-sources-must-
update mode, but as mentioned before, that's way off - it probably
requires quite a few changes.
** Changed in: apt (Ubuntu)
Status: New => Triaged
OK, so I think we let this sit for a few more weeks and see what else we
get. So far we have 4 people affected by this. Does not happen for me,
BTW, and yes, I use the mirror method (from -proposed, the old one does
not work and the new one is much better :D).
Now, as to documentation: There is
Marking as released since we use the systemd timer now and are thus
independent of cron.
** Changed in: unattended-upgrades (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
You should get the same popup when running apt as you do with update-
manager or any other package management tool for that matter.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
** Changed in: lvm2 (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1741986
Title:
Please merge lvm2 from Debian unstable
package descriptions
-- Julian Andres Klode <juli...@ubuntu.com> Thu, 11 Jan 2018 20:51:25
+0100
** Changed in: ncurses (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Fixed that for now in unattended-upgrades and update-notifier by adding
case "$DPKG_MAINTSCRIPT_PACKAGE::$DPKG_MAINTSCRIPT_NAME" in
linux-image-extra*::postrm)
exit 0;;
esac
We can then still decide if we want to run postinst.d scripts in linux-
image-extra removals or not, but let's
or well, use an explicit if
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1742378
Title:
Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in
apt-1.2.24
Status
I'd rather use if ! on_ac_power; then return 1; fi
** Changed in: apt (Ubuntu)
Importance: Undecided => Low
** Changed in: apt (Ubuntu)
Status: New => Triaged
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received
801 - 900 of 2559 matches
Mail list logo
