Dev1 Galaxy Forum / [SOLVED] Chromium Upgrade: 3 Packages have been Kept Back

Re: [SOLVED] Chromium Upgrade: 3 Packages have been Kept Back

dummy@example.com (alexkemp) — Tue, 06 Jun 2023 01:04:36 +0000

There is now a chromium-l10n update & this one is SOLVED.

/.local/sbin/update
Hit:1 http://deb.devuan.org/merged chimaera InRelease
Hit:2 http://deb.devuan.org/merged chimaera-security InRelease
Hit:3 http://deb.devuan.org/merged chimaera-updates InRelease                
Hit:4 http://deb.devuan.org/merged chimaera-proposed-updates InRelease       
Hit:5 http://deb.devuan.org/merged chimaera-backports InRelease
Hit:6 https://josm.openstreetmap.de/apt alldist InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  chromium chromium-common chromium-l10n chromium-sandbox josm-latest
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 95.5 MB of archives.
After this operation, 2,050 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://deb.devuan.org/merged chimaera-security/main amd64 chromium-l10n all 114.0.5735.90-2~deb11u1 [6,184 kB]
Get:5 https://josm.openstreetmap.de/apt alldist/universe amd64 josm-latest all 1.5.svn18746 [15.7 MB]
Get:2 http://deb.devuan.org/merged chimaera-security/main amd64 chromium amd64 114.0.5735.90-2~deb11u1 [68.5 MB]
Get:3 http://deb.devuan.org/merged chimaera-security/main amd64 chromium-common amd64 114.0.5735.90-2~deb11u1 [4,970 kB]             
Get:4 http://deb.devuan.org/merged chimaera-security/main amd64 chromium-sandbox amd64 114.0.5735.90-2~deb11u1 [134 kB]              
Fetched 95.5 MB in 9s (10.1 MB/s)                                                                                                    
Reading changelogs... Done
(Reading database ... 201190 files and directories currently installed.)
Preparing to unpack .../chromium-l10n_114.0.5735.90-2~deb11u1_all.deb ...
Unpacking chromium-l10n (114.0.5735.90-2~deb11u1) over (113.0.5672.126-1~deb11u1) ...
Preparing to unpack .../chromium_114.0.5735.90-2~deb11u1_amd64.deb ...
Unpacking chromium (114.0.5735.90-2~deb11u1) over (113.0.5672.126-1~deb11u1) ...
Preparing to unpack .../chromium-common_114.0.5735.90-2~deb11u1_amd64.deb ...
Unpacking chromium-common (114.0.5735.90-2~deb11u1) over (113.0.5672.126-1~deb11u1) ...
Preparing to unpack .../chromium-sandbox_114.0.5735.90-2~deb11u1_amd64.deb ...
Unpacking chromium-sandbox (114.0.5735.90-2~deb11u1) over (113.0.5672.126-1~deb11u1) ...
Preparing to unpack .../josm-latest_1.5.svn18746_all.deb ...
Unpacking josm-latest (1.5.svn18746) over (1.5.svn18744) ...
Setting up chromium-sandbox (114.0.5735.90-2~deb11u1) ...
Setting up chromium-common (114.0.5735.90-2~deb11u1) ...
Setting up chromium (114.0.5735.90-2~deb11u1) ...
Setting up josm-latest (1.5.svn18746) ...
Setting up chromium-l10n (114.0.5735.90-2~deb11u1) ...
Processing triggers for mailcap (3.69) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for shared-mime-info (2.0-1) ...
Processing triggers for menu (2.1.48) ...

Re: [SOLVED] Chromium Upgrade: 3 Packages have been Kept Back

dummy@example.com (soren) — Mon, 05 Jun 2023 08:14:53 +0000

boughtonp wrote:

soren wrote:
I find it odd that stable wants to install chromium 114 as im on unstable and its still only at 113?
Unstable (Ceres/Sid) is on 114 too, it's Testing (Daedalus/Bookworm) that is on 113.

Thats what I meant to say (testing, Daedaulus). Sorry for the confusion.

Re: [SOLVED] Chromium Upgrade: 3 Packages have been Kept Back

dummy@example.com (alexkemp) — Sun, 04 Jun 2023 15:59:44 +0000

soren wrote:

Hi,
Just use the command as so without packages

Nope (but thanks for trying).

$ sudo apt --fix-broken install
[sudo] password for alexk: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

boughtonp wrote:

The page also mentions a bug in the chromium-l10n package, which is about this issue:
https://bugs.debian.org/cgi-bin/bugrepo … ug=1037087

Clearly that is the issue; it is the precise error previously reported by me above. The bug report was made today (I was searching for such a report yesterday but of course, could find nothing

Re: [SOLVED] Chromium Upgrade: 3 Packages have been Kept Back

dummy@example.com (boughtonp) — Sun, 04 Jun 2023 14:12:46 +0000

soren wrote:

I find it odd that stable wants to install chromium 114 as im on unstable and its still only at 113?

Unstable (Ceres/Sid) is on 114 too, it's Testing (Daedalus/Bookworm) that is on 113.

Stable (Chimaera/Bullseye) is on 112, except there's a 114 in the Stable security repo - but not for the locale package.

This can be seen at https://pkginfo.devuan.org/chromium and https://pkginfo.devuan.org/chromium-l10n

Since Chromium is not a Devuan-specific package, this is not a Devuan issue.

Specific versions can be seen in Debian's tracker, as can the fact that v114 entered stable-security yesterday:
https://tracker.debian.org/pkg/chromium

The page also mentions a bug in the chromium-l10n package, which is about this issue:
https://bugs.debian.org/cgi-bin/bugrepo … ug=1037087

In other words, it seems for whatever reason only 5 of the 6 binary packages have been built/deployed - once the Debian Maintainer for Chromium sees the issue they will presumably rectify that.

Re: [SOLVED] Chromium Upgrade: 3 Packages have been Kept Back

dummy@example.com (soren) — Sun, 04 Jun 2023 10:00:17 +0000

Hi,

Just use the command as so without packages, it should/might give options.

sudo apt --fix-broken install

Re: [SOLVED] Chromium Upgrade: 3 Packages have been Kept Back

dummy@example.com (alexkemp) — Sun, 04 Jun 2023 09:57:16 +0000

soren wrote:

Have you tried the following command?
sudo apt --fix-broken install

Essentially, I got the same as the previous attempts:

$ sudo apt --fix-broken install chromium-l10n chromium-shell chromium-driver chromium chromium-common chromium-sandbox josm-latest
[sudo] password for alexk: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
chromium-l10n is already the newest version (113.0.5672.126-1~deb11u1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 chromium-l10n : Depends: chromium (< 113.0.5672.126-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed
E: Unable to correct problems, you have held broken packages.

im on unstable and its still only at 113?

The latest version (albeit Windows) is 116.0.5812.0 (Sunday, June 4, 2023 Revision: 1152969).

Re: [SOLVED] Chromium Upgrade: 3 Packages have been Kept Back

dummy@example.com (soren) — Sun, 04 Jun 2023 07:46:35 +0000

Have you tried the following command?

sudo apt --fix-broken install

I find it odd that stable wants to install chromium 114 as im on unstable and its still only at 113?

[SOLVED] Chromium Upgrade: 3 Packages have been Kept Back

dummy@example.com (alexkemp) — Sat, 03 Jun 2023 20:54:35 +0000

A one-line script is run every day under my Chimaera 4 system:

sudo apt update && sudo apt install -f && sudo apt upgrade

No problems until today, when it reports that 3 of 4 available packages will be held back:

$ ~/.local/sbin/update
Hit:1 https://josm.openstreetmap.de/apt alldist InRelease
Hit:2 http://deb.devuan.org/merged chimaera InRelease
Get:3 http://deb.devuan.org/merged chimaera-security InRelease [26.2 kB]
Get:4 http://deb.devuan.org/merged chimaera-updates InRelease [26.1 kB]
Get:5 http://deb.devuan.org/merged chimaera-proposed-updates InRelease [26.6 kB]
Hit:6 http://deb.devuan.org/merged chimaera-backports InRelease
Fetched 78.9 kB in 3s (28.9 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  chromium chromium-common chromium-sandbox
The following packages will be upgraded:
  josm-latest
1 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 15.7 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

Cue frantic DDG searches.

A 12-year old question has good suggestions:

$ sudo apt-get --with-new-pkgs upgrade chromium chromium-common chromium-sandbox josm-latest
[sudo] password for alexk: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 chromium-l10n : Depends: chromium (< 113.0.5672.126-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed
E: Broken packages

$ sudo apt-get install chromium chromium-common chromium-sandbox josm-latest
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
  chromium-l10n chromium-shell chromium-driver
The following packages will be REMOVED:
  chromium-l10n
The following packages will be upgraded:
  chromium chromium-common chromium-sandbox josm-latest
4 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 89.3 MB of archives.
After this operation, 80.6 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

Nope; not ready for it to be removed yet.

These are the problematic packages waiting to be upgraded:

$ apt list --upgradable
Listing... Done
chromium-common/stable-security 114.0.5735.90-2~deb11u1 amd64 [upgradable from: 113.0.5672.126-1~deb11u1]
chromium-sandbox/stable-security 114.0.5735.90-2~deb11u1 amd64 [upgradable from: 113.0.5672.126-1~deb11u1]
chromium/stable-security 114.0.5735.90-2~deb11u1 amd64 [upgradable from: 113.0.5672.126-1~deb11u1]
josm-latest/unknown 1.5.svn18746 all [upgradable from: 1.5.svn18744]

So, after that blizzard of code, what to do? Is it likely that chromium-l10n may finally get updated if I am patient, or is there any other solution?