Bug#954807: marked as done (apt upgrade sometimes marks packages as manually installed)
Your message dated Mon, 23 Mar 2020 20:51:40 +0100
with message-id <20200323204831.GA669918@debian.org>
and subject line Re: Bug#954807: apt upgrade sometimes marks packages as manually installed
has caused the Debian Bug report #954807,
regarding apt upgrade sometimes marks packages as manually installed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
954807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954807
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 2.0.0
Severity: normal
When a package listed as an argument to apt upgrade is already at the
requested version, it is marked as manually installed:
# apt-mark showmanual libc6
# apt upgrade libc6
Reading package lists... Done
Building dependency tree
Reading state information... Done
libc6 is already the newest version (2.30-2).
libc6 set to manually installed.
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# apt-mark showmanual libc6
libc6
#
Please do not mark packages listed as arguments to apt upgrade as
manually installed.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8),
LANGUAGE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages apt depends on:
ii adduser 3.118
ii debian-archive-keyring 2019.1
ii gpgv 2.2.19-3
ii libapt-pkg6.0 2.0.0
ii libc6 2.30-2
ii libgcc-s1 10-20200312-2
ii libgnutls30 3.6.12-2
ii libseccomp2 2.4.3-1
ii libstdc++6 10-20200312-2
Versions of packages apt recommends:
ii ca-certificates 20190110
Versions of packages apt suggests:
ii apt-doc 2.0.0
pn aptitude | synaptic | wajig <none>
ii dpkg-dev 1.19.7
ii gnupg 2.2.19-3
pn powermgmt-base <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Mar 23, 2020 at 08:26:06PM +0100, Piotr Engelking wrote:
> Package: apt
> Version: 2.0.0
> Severity: normal
>
>
> When a package listed as an argument to apt upgrade is already at the
> requested version, it is marked as manually installed:
>
> # apt-mark showmanual libc6
> # apt upgrade libc6
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> libc6 is already the newest version (2.30-2).
> libc6 set to manually installed.
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> # apt-mark showmanual libc6
> libc6
> #
>
> Please do not mark packages listed as arguments to apt upgrade as
> manually installed.
This is not a bug, but a feature. You ran the equivalent of
apt install libc6 && apt upgrade, and that causes libc6 to be
manually installed, because you manually requested it to be
installed.
It's not a feature I agree with, even in the "install" case, but I
can understand the argument for having it. But then, I do have to
use that a bit more often than the average user probably, because
I do need to tweak the solver choices or help it along by giving it
more hints.
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
--- End Message ---
Reply to: