This bug was fixed in the package apt - 1.6.17
---
apt (1.6.17) bionic; urgency=medium
* Bump cache minor version for kernel collection.
The previous update introduced the new kernel autoremoval code which
collects kernels in the cache as providers of a $kernel package.
As told before, the issue seems to be fixed even in apt 1.6.14, but I
tested the proposed 1.6.17 anyway. Autoremove did not (try to) remove
current kernel even with that one, but it removes one more kernel than
the old one (which is desired by developers, I assume).
** Tags removed: verification-n
Hello Jarno, or anyone else affected,
Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.17 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Te
Oh, so I downgraded those packages again to bionic-updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may remove current
@Jarno OK I was wrong, new apt pulls in new libapt-pkg5.0. What happens
instead is that the cache built by the old version does not include
information about available kernels, we essentially need to bump the
cache minor version, if we can do that, I don't know, I lost track of
what major version i
The latter option sounds nicer.
BTW can someone comment on
https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/1392954
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad
But I do believe it's simply the wrong package being upgraded here. The
new apt package removes the conffiles the old library version needs, so
it doesn't protect anything, so we need to make sure that apt Breaks
libapt-pkg6.0 (<< 1.6.15) [or Depends on >= 1.6.15, whatever ends up
nicer).
--
You
Jarno, you do realize that you need to upgrade libapt-pkg6.0, not apt?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may rem
Thereafter I installed the proposed apt by
$ sudo apt install apt -t=bionic-proposed
$ apt --version
apt 1.6.16 (i386)
$ apt autoremove -s
$ uname -r
5.4.0-121-generic
$ apt autoremove -s
NOTE: This is only a simulation!
apt needs root privileges for real execution.
Keep also in mi
For some reason the test case worked even with apt 1.6.14 as the
following shows:
$ apt policy apt
apt:
Installed: 1.6.14
Candidate: 1.6.14
Version table:
1.6.16 400
400 http://mirrors.nic.funet.fi/ubuntu bionic-proposed/main i386
Packages
*** 1.6.14 500
500 http://mir
Hello Jarno, or anyone else affected,
Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.16 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Te
So there is neither /etc/apt/apt.conf.d/01autoremove-kernels nor
/etc/kernel/postinst.d/apt-auto-removal anymore. Anyway I could not make
'apt autoremove' try to remove current kernel anymore. Tested by apt
2.0.8.
--
You received this bug notification because you are a member of Ubuntu
Touch seed
Hello Jarno, or anyone else affected,
Accepted apt into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.0.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Test
This bug was fixed in the package apt - 1.6.13
---
apt (1.6.13) bionic; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[ J
This bug was fixed in the package apt - 2.0.5
---
apt (2.0.5) focal; urgency=medium
[ Julian Andres Klode ]
* private-search: Only use V.TranslatedDescription() if good (LP: #1877987)
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all translations
This bug was fixed in the package apt - 2.1.10ubuntu0.3
---
apt (2.1.10ubuntu0.3) groovy; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP
The autopkgtests for apt have passed, so testing succeeded. I retried
the failures, I expect them to be unrelated: apport one already happened
with binutils/2.30-21ubuntu1~18.04.5, the i386 retry succeeded; and
reprotest fails in its normal way, a few retries should get it working.
** Tags removed
Hello Jarno, or anyone else affected,
Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.13 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Te
Hello Jarno, or anyone else affected,
Accepted apt into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.0.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Test
Hello Jarno, or anyone else affected,
Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
** Changed in: apt (Ubuntu Groovy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may r
** Description changed:
[Impact]
APT will try and fail to remove the currently running kernel, when booted
into an older kernel that is not protected. May wreak some havoc if mixed with
other operations to the point that apt goes weird and needs manual fixing up.
[Test case]
+ For the S
** Also affects: apt (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: unattended-upgrades (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: unattended-upgrades (U
** Description changed:
+ [Impact]
+ APT will try and fail to remove the currently running kernel, when booted
into an older kernel that is not protected. May wreak some havoc if mixed with
other operations to the point that apt goes weird and needs manual fixing up.
+
+ [Test case]
+ - Install
This bug was fixed in the package apt - 2.1.18
---
apt (2.1.18) unstable; urgency=high
* pkgcachegen: Avoid write to old cache for Version::Extra (Closes: #980037)
* Adjust apt-mark test for dpkg 1.20.7
-- Julian Andres Klode Wed, 13 Jan 2021 17:37:30
+0100
** Changed in: apt
** Tags added: fr-747
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may remove current kernel
Status in apt package in Ubun
I have code to fix that just need to merge it and like update tests
** Changed in: apt (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bu
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may remove current kernel
Status in apt package in Ubuntu:
@mathew-hodson apt still does that.
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unatte
** No longer affects: apt (Ubuntu Artful)
** No longer affects: apt (Ubuntu Xenial)
** No longer affects: apt (Ubuntu Trusty)
** No longer affects: apt (Ubuntu)
** Changed in: unattended-upgrades (Ubuntu Trusty)
Status: New => Won't Fix
--
You received this bug notification because you
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
* test/test
@jarnos, this is a separate issue fixed later, calculating upgradable packages
leaves the upgradable packages in the cache, and u-u counts them as the reverse
dependencies of the first kernel to be removed.
This keeps the first kernel on the system, but when there are no upgradable
packages in a
I do not understand why u-u keeps linux-modules-4.15.0-36-generic. How
do those packages depend on that?
--
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/1615381
Title:
apt-get
Verified 1.1ubuntu1.18.04.7~16.04.2 on Xenial.
Installed a few linux packages, marked them auto-installed, ran
/etc/kernel/postinst.d/apt-auto-removal , then booted to a old kernel.
Apt would have removed it, but u-u did not. (The -34- kernel.)
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ uname
** Changed in: unattended-upgrades (Ubuntu)
Importance: Undecided => High
** Changed in: unattended-upgrades (Ubuntu Artful)
Importance: Undecided => High
** Changed in: unattended-upgrades (Ubuntu Trusty)
Importance: Undecided => Low
--
You received this bug notification because you a
Hello Jarno, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.0 in a few hours, and then
in the -proposed repository.
Please help us by test
** Changed in: unattended-upgrades (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autore
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may remove current kernel
Status in apt package in Ubuntu:
Thanks for the heads-up Balint.
I saw the "full backport" discussion in the ML, thanks !
For now, I'm setting Xenial as 'high' priority as it has been brought to
my attention that 'uu' in Xenial removed a running kernel recently :
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
...
Rem
On Thu, May 24, 2018 at 1:24 PM, Eric Desrochers
wrote:
> Any particular reason why the fix hasn't been SRU'd ? I'll start looking
> at SRU'ing it into the rest of Stable Release.
>
> >From what I read the reporter first filed the bug against Xenial 16.04
> LTS. Anyone still affected by this issue
Any particular reason why the fix hasn't been SRU'd ? I'll start looking
at SRU'ing it into the rest of Stable Release.
>From what I read the reporter first filed the bug against Xenial 16.04
LTS. Anyone still affected by this issue on Xenial or Artful ?
--
You received this bug notification bec
This bug was fixed in the package unattended-upgrades - 1.0ubuntu1
---
unattended-upgrades (1.0ubuntu1) bionic; urgency=medium
* Merge from Debian unstable
- Remaining changes:
- unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu un
** Changed in: unattended-upgrades (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autor
... /etc/kernel/postinst.d/apt-auto-removal was run.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
--
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/1
In default configuration booted kernel does not become newly unused, but
when u-u is configured to remove all autoremovable packages the booted
kernel can be removed in case it was not running when was run.
** Also affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
** Tags added: kernel-autoremove
--
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/1615381
Title:
apt-get autoremove may remove current kernel
Status in apt package in Ubuntu:
In my case autoremove wants to delete the second-latest regular kernel
version. Maybe because I have a bunch of mainline kernels installed
also.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launc
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
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/
Julian, it protects the kernel currently booted at the time of running
/etc/kernel/postinst.d/apt-auto-removal. If you later boot another
kernel that is not protected, it may be removed. Not a likely case,
though.
--
You received this bug notification because you are a member of Ubuntu
Touch seed
This should not happen...
# Mark as not-for-autoremoval those kernel packages that are:
# - the currently booted version
# - the kernel version we've been called for
# - the latest kernel version (as determined by debian version number)
# - the second-latest kernel version
Not sure what went
** Description changed:
This may happen, if you boot one of the older kernels, that is not
protected by /etc/apt/apt.conf.d/01autoremove-kernels
- Workaround: run
- /etc/kernel/postinst.d/&apt-auto-removal
+ Workaround: run
+ /etc/kernel/postinst.d/apt-auto-removal
during each boot (e.g.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
I suppose this may happen with unattended-upgrades, too, if user has
configured removing of old kernels.
--
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/1615381
Title:
apt-get
53 matches
Mail list logo