Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1148724 > unrolled thread

Bug#1037087: chromium-l10n: The following packages have unmet dependencies: chromium-l10n : Depends: chromium (< 112.0.5615.138-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed

Started byAttila Hammer <hammera@pickup.hu>
First post2023-06-04 13:50 +0200
Last post2023-06-04 22:50 +0200
Articles 5 — 5 participants

Back to article view | Back to linux.debian.bugs.dist


Contents

  Bug#1037087: chromium-l10n: The following packages have unmet dependencies: chromium-l10n : Depends: chromium (< 112.0.5615.138-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed Attila Hammer <hammera@pickup.hu> - 2023-06-04 13:50 +0200
    Bug#1037087: chromium-l10n: The following packages have unmet dependencies: chromium-l10n : Depends: chromium (< 112.0.5615.138-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed Andres Salomon <dilinger@queued.net> - 2023-06-04 18:10 +0200
      Bug#1037087: chromium-l10n: The following packages have unmet dependencies: chromium-l10n : Depends: chromium (< 112.0.5615.138-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed Moritz Muehlenhoff <jmm@inutil.org> - 2023-06-04 19:30 +0200
        Bug#1037087: chromium-l10n: The following packages have unmet dependencies: chromium-l10n : Depends: chromium (< 112.0.5615.138-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed Salvatore Bonaccorso <carnil@debian.org> - 2023-06-04 20:50 +0200
    Bug#1037087: chromium-l10n: The following packages have unmet dependencies: chromium-l10n : Depends: chromium (< 112.0.5615.138-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed inasprecali <inasprecali@disroot.org> - 2023-06-04 22:50 +0200

#1148724 — Bug#1037087: chromium-l10n: The following packages have unmet dependencies: chromium-l10n : Depends: chromium (< 112.0.5615.138-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed

FromAttila Hammer <hammera@pickup.hu>
Date2023-06-04 13:50 +0200
SubjectBug#1037087: chromium-l10n: The following packages have unmet dependencies: chromium-l10n : Depends: chromium (< 112.0.5615.138-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed
Message-ID<GCUpb-dB5l-5@gated-at.bofh.it>
Package: chromium-l10n
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
sudo apt install chromium chromium-l10n command results me following error
message:
"Reading package lists... Done
Building dependency tree... Done
Reading state information... 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 (< 112.0.5615.138-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed
E: Unable to correct problems, you have held broken packages."


   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Simple ran sudo apt install chromium chromium-l10n command.

   * What was the outcome of this action?
Previous Chromium and Chromium related language packages are right installed.

   * What outcome did you expect instead?

The quoted error message since yesterday.
I am not using pinned repositoryes, holded packages,
simple used standard Bullseye related repositories.


*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 11.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-23-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium-l10n depends on:
pn  chromium  <none>

chromium-l10n recommends no packages.

chromium-l10n suggests no packages.

[toc] | [next] | [standalone]


#1148748

FromAndres Salomon <dilinger@queued.net>
Date2023-06-04 18:10 +0200
Message-ID<GCYsN-dDOV-1@gated-at.bofh.it>
In reply to#1148724
Hi Security Team,

Looking at 
https://security.debian.org/debian-security/pool/main/c/chromium/ , I 
see that chromium-l10n built for bookworm (deb12u1) but not for 
bullseye (deb11u1). I'm guessing that the arch:all build was 
interrupted or is still in a needs-build state or something, but since 
it's the security infra I can't see it. Can you please do a giveback or 
whatever is needed to get it building, or if something is reproducably 
broken with the build please send me the build log?

Thanks,
Andres

On Sun, Jun 4 2023 at 10:25:26 AM +00:00:00, Attila Hammer 
<hammera@pickup.hu> wrote:
> Package: chromium-l10n
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where 
> appropriate ***
> 
>    * What led up to the situation?
> sudo apt install chromium chromium-l10n command results me following 
> error
> message:
> "Reading package lists... Done
> Building dependency tree... Done
> Reading state information... 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 (< 112.0.5615.138-1~deb11u1.1~) but 
> 114.0.5735.90-2~deb11u1 is to be installed
> E: Unable to correct problems, you have held broken packages."
> 
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> Simple ran sudo apt install chromium chromium-l10n command.
> 
>    * What was the outcome of this action?
> Previous Chromium and Chromium related language packages are right 
> installed.
> 
>    * What outcome did you expect instead?
> 
> The quoted error message since yesterday.
> I am not using pinned repositoryes, holded packages,
> simple used standard Bullseye related repositories.
> 
> 
> *** End of the template - remove these template lines ***
> 
> 
> -- System Information:
> Debian Release: 11.7
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), 
> (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.10.0-23-amd64 (SMP w/4 CPU threads)
> Locale: LANG=C.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=ANSI_X3.4-1968) 
> (ignored: LC_ALL set to C), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages chromium-l10n depends on:
> pn  chromium  <none>
> 
> chromium-l10n recommends no packages.
> 
> chromium-l10n suggests no packages.
> 

[toc] | [prev] | [next] | [standalone]


#1148751

FromMoritz Muehlenhoff <jmm@inutil.org>
Date2023-06-04 19:30 +0200
Message-ID<GCZId-dEtl-1@gated-at.bofh.it>
In reply to#1148748
On Sun, Jun 04, 2023 at 12:06:01PM -0400, Andres Salomon wrote:
> Hi Security Team,
> 
> Looking at https://security.debian.org/debian-security/pool/main/c/chromium/
> , I see that chromium-l10n built for bookworm (deb12u1) but not for bullseye
> (deb11u1). I'm guessing that the arch:all build was interrupted or is still
> in a needs-build state or something, but since it's the security infra I
> can't see it. Can you please do a giveback or whatever is needed to get it
> building, or if something is reproducably broken with the build please send
> me the build log?

I sent a giveback, let's see what comes out of it.

Cheers,
        Moritz

[toc] | [prev] | [next] | [standalone]


#1148755

FromSalvatore Bonaccorso <carnil@debian.org>
Date2023-06-04 20:50 +0200
Message-ID<GD0XD-dFbc-1@gated-at.bofh.it>
In reply to#1148751
Hi Moritz,

On Sun, Jun 04, 2023 at 07:22:47PM +0200, Moritz Muehlenhoff wrote:
> On Sun, Jun 04, 2023 at 12:06:01PM -0400, Andres Salomon wrote:
> > Hi Security Team,
> > 
> > Looking at https://security.debian.org/debian-security/pool/main/c/chromium/
> > , I see that chromium-l10n built for bookworm (deb12u1) but not for bullseye
> > (deb11u1). I'm guessing that the arch:all build was interrupted or is still
> > in a needs-build state or something, but since it's the security infra I
> > can't see it. Can you please do a giveback or whatever is needed to get it
> > building, or if something is reproducably broken with the build please send
> > me the build log?
> 
> I sent a giveback, let's see what comes out of it.

Incidently it was asked about it already this afternoon, and did gave
back as well earlier today. But the build failed again. If your
give-back fails as well then we need to fetch the build logs to
understand the failures.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]


#1148765

Frominasprecali <inasprecali@disroot.org>
Date2023-06-04 22:50 +0200
Message-ID<GD2PL-dGjt-1@gated-at.bofh.it>
In reply to#1148724
Hi,

I tried installing chromium-l10n again on a freshly updated
Bullseye machine (with the bullseye-security and bullseye-updates
repositories enabled, of course) and this time the operation
succeeded with no conflicts.

Unless there are new reports about this problem persisting, I
think this bug can be closed.

Best regards.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web