[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#992237: marked as done (general: dpkg broken, so no security updates available)

Your message dated Mon, 16 Aug 2021 10:49:44 +0200
with message-id <878s11wz87.fsf@hands.com>
and subject line Re: Bug#992237: general: dpkg broken, so no security updates available
has caused the Debian Bug report #992237,
regarding general: dpkg broken, so no security updates available
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.)


-- 
992237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992237
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: general
Severity: important

Dear Maintainer,

see below:


Get:1 http://security.debian.org/debian-security bullseye-security InRelease [44.1 kB]
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://deb.debian.org/debian bullseye-backports InRelease
Fetched 44.1 kB in 0s (93.7 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@wp:~# dpkg -S /bin
dpkg-query: no path found matching pattern /bin
root@wp:~# dpkg -l
root@wp:~#

After upgrading to stable, dpkg does not know anything about installed packages. This means that security patches will not be installed.

--- End Message ---
--- Begin Message --- 
Olaf Zaplinski <oz42@oz42.eu> writes:

> Package: general
> Severity: important
>
> Dear Maintainer,
>
> see below:
>
>
> Get:1 http://security.debian.org/debian-security bullseye-security InRelease [44.1 kB]
> Hit:2 http://deb.debian.org/debian bullseye InRelease
> Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
> Hit:4 http://deb.debian.org/debian bullseye-backports InRelease
> Fetched 44.1 kB in 0s (93.7 kB/s)
> Reading package lists... Done
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> root@wp:~# dpkg -S /bin
> dpkg-query: no path found matching pattern /bin
> root@wp:~# dpkg -l
> root@wp:~#
>
> After upgrading to stable, dpkg does not know anything about installed packages. This means that security patches will not be installed.
>

I'm afraid you're going to have to do rather more research about what
you did there, because if I look at one of the many systems I've
upgraded I see:

=-=-=-
root@sheikh:~# apt update 
Hit:1 http://debian.hands.com/debian bullseye InRelease
Hit:2 http://security.debian.org bullseye-security InRelease
Reading package lists... Done              
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
root@sheikh:~# dpkg -S /bin
kbd, tar, psmisc, net-tools, login, bash, busybox, console-setup, systemd, systemd-container, util-linux, startpar, mount, cpio, coreutils, udev, debianutils, sysvinit-utils, procps, nano, iputils-ping, netcat-traditional, netcat-openbsd, bzip2, sed, dash, base-files, grep, fuse, hostname, gzip, iproute2, kmod: /bin
root@sheikh:~# dpkg -l | wc -l
1149
root@sheikh:~# dpkg -l | head
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                 Version                                                Architecture Description
+++-====================================-======================================================-============-==================================================================================
ii  acpi                                 1.7-1.1                                                amd64        displays information on ACPI devices
ii  adduser                              3.118                                                  all          add and remove users and groups
ii  adwaita-icon-theme                   3.38.0-1                                               all          default icon theme of GNOME
ii  alsa-topology-conf                   1.2.4-1                                                all          ALSA topology configuration files
ii  alsa-ucm-conf                        1.2.4-2                                                all          ALSA Use Case Manager configuration files
root@sheikh:~# 
=-=-=-

That being the case there must be something specific about your setup
that has caused your issue, rather than a general bug in Debian.

If there is really a bug causing this, then you should attempt to
establish which package is at fault, and report a bug against that
package, including details about how one might reproduce the bug so that
the package maintainer has some sort of hope of fixing it.

If on the other hand, there is something awry with the state of your
machine, then you should probably ask for help via one of the several
channels that we have for that:

  https://www.debian.org/support

Either way, a bug reported against Debian in general is not going to
help you or us I'm afraid, so I'm going to close this bug immediately.

Good Luck fixing your system.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/    http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,    GERMANY

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: