On Sat, Jan 27, 2024 at 10:35:55PM -0500, Jim Rosenberg wrote: > Wow, thanks for the lightning quick response!! > > > When reporting problems like this it is really quite important to > > include complete output. > > 127% apt-cache policy firefox-esr > firefox-esr: > Installed: 115.6.0esr-1~deb10u1 > Candidate: 115.6.0esr-1~deb10u1 > Version table: > *** 115.6.0esr-1~deb10u1 500 > 500 http://security.debian.org buster/updates/main amd64 Packages > 500 http://security.debian.org/debian-security buster/updates/main > amd64 Packages 100 /var/lib/dpkg/status > 91.12.0esr-1~deb10u1 500 > 500 http://deb.debian.org/debian buster/main amd64 Packages > > 128% sudo apt update > [sudo] password for jr: > Hit:1 http://deb.debian.org/debian buster InRelease > Hit:2 http://security.debian.org buster/updates InRelease > Hit:3 http://security.debian.org/debian-security buster/updates InRelease > Hit:4 http://deb.debian.org/debian buster-updates InRelease > Hit:5 https://dbeaver.io/debs/dbeaver-ce InRelease > Reading package lists... Done > Building dependency tree > Reading state information... Done > 66 packages can be upgraded. Run 'apt list --upgradable' to see them. > > 130% apt-get -s upgrade | grep upgraded > 0 upgraded, 0 newly installed, 0 to remove and 66 not upgraded. > > 131% apt-get -s --with-new-pkgs upgrade | grep upgraded > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >
Your system doesn't seem to know anything of an unavailable firefox-esr package (it seems to think that the candidate is 115.6.0esr-1~deb10u1). I'll repeat what I said in my last message: > > When reporting problems like this it is really quite important to > > include complete output. You have chosen to run the output of 'apt-get -s upgrade' through 'grep' so that it is not possible to tell what problem apt-get may have encountered or what choice it made in deciding the viable upgrade path(s). By sending the output through 'grep' you have only allowed us to determine that 'apt-get' decided it could not upgrade 66 packages, but it is not possible to determine how or why apt reached that conclusion. Also, note that you have a third-party source in the mix (dbeaver.io) and since you didn't provide the output of 'apt-get -s upgrade' it isn't clear what influence (if any) the presence of that source is having on the situation. Please provide the full output so that we can help you determine what is going on. Regards, -Roberto -- Roberto C. Sánchez
