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

Groups > linux.debian.bugs.rc > #377767 > unrolled thread

Bug#1089181: chromium: Stable update wants to remove chromium package itself

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

Contents

  Bug#1089181: chromium: Stable update wants to remove chromium package itself Santiago Vila <sanvila@debian.org> - 2024-12-06 20:20 +0100
    Bug#1089181: chromium: Stable update wants to remove chromium  package itself Nate Bargmann <n0nb@n0nb.us> - 2024-12-07 01:10 +0100
    Bug#1089181: chromium: Stable update wants to remove chromium package itself Santiago Vila <sanvila@debian.org> - 2024-12-07 01:30 +0100
      Bug#1089181: chromium: Stable update wants to remove chromium package itself Alex Volkov <alex@bootes.sytes.net> - 2024-12-07 19:00 +0100
        Bug#1089181: chromium: Stable update wants to remove chromium package itself Stephen Kitt <skitt@debian.org> - 2024-12-07 19:40 +0100
          Bug#1089181: chromium: Stable update wants to remove chromium package itself Cyril Brulebois <kibi@debian.org> - 2024-12-08 00:00 +0100
            Bug#1089181: chromium: Stable update wants to remove chromium  package itself Nate Bargmann <n0nb@n0nb.us> - 2024-12-08 01:00 +0100
    Bug#1089181: chromium: security update wants to remove chromium package itself Neil Van Dyke <neil@neilvandyke.org> - 2024-12-10 20:50 +0100
    Bug#1089181: marked as done (chromium: security update wants to  remove chromium package itself) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-12-12 20:30 +0100
    Bug#1089181: chromium still not installable via debian-live Thierry <debian_bugreport@sagedebianlive.metelu.net> - 2024-12-17 00:30 +0100
    Bug#1089181: chromium still not installable via debian-live Thierry <debian_bugreport@sagedebianlive.metelu.net> - 2024-12-17 02:30 +0100

#377767 — Bug#1089181: chromium: Stable update wants to remove chromium package itself

Package: chromium
Version: 131.0.6778.108-1~deb12u1
Severity: grave

Hi.

Today's chromium update in stable wants to remove "chromium" and "chromium-l10n":

------------------------------------------------------------------------------------
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
   libopenh264-7
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
   chromium chromium-l10n
The following packages have been kept back:
   chromium-common
The following packages will be upgraded:
   chromium-sandbox
1 upgraded, 0 newly installed, 2 to remove and 1 not upgraded.
Need to get 97.7 kB of archives.
After this operation, 387 MB disk space will be freed.
Do you want to continue? [Y/n]
------------------------------------------------------------------------------------

Also, on a VM where chrome is not installed yet, chrome may
not be installed at all:

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 : Depends: libc++1-19 (>= 1:19.1.4) but it is not installable
             Depends: libc++abi1-19 (>= 1:19.1.4) but it is not installable
             Depends: libunwind-19 (>= 1:19.1.4) but it is not installable
             Depends: chromium-common (= 131.0.6778.108-1~deb12u1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Thanks.

[toc] | [next] | [standalone]

#377787 — Bug#1089181: chromium: Stable update wants to remove chromium package itself

[Multipart message — attachments visible in raw view] — view raw

On Fri, 6 Dec 2024 14:49:07 -0500 Andres Salomon <dilinger@queued.net> wrote:
> Hi,
> 
> For the time being you'll have to add bookworm-proposed-updates to your 
> /etc/apt/sources.list. For example the following line:
> 
> deb http://deb.debian.org/debian/ bookworm-proposed-updates main

Is this really a work-around?  Looking at

https://deb.debian.org/debian/dists/bookworm-proposed-updates/

I see the latest version of chromium is 131.0.6778.85-1~deb12u1 which is
already installed on my Bookworm system.  131.0.6778.108-1~deb12u1 is
not present in that directory that I can see.

- Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

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

#377788

> Is this really a work-around?

Yes, it is. (try it!)

The problem is that the new chrome package is in security but
some of its dependencies do not exist at all in security and
are only in bookworm-proposed-updates.

So you need both security + bookworm-proposed-updates.

Thanks.

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

#377819

[Multipart message — attachments visible in raw view] — view raw

On Sat, 7 Dec 2024 01:18:41 +0100 Santiago Vila <sanvila@debian.org> wrote:
> > Is this really a work-around?
> 
> Yes, it is. (try it!)
> 
> The problem is that the new chrome package is in security but
> some of its dependencies do not exist at all in security and
> are only in bookworm-proposed-updates.
> 
> So you need both security + bookworm-proposed-updates.
> 
> Thanks.
> 
> 

No, it's not a "workaround". The problem is that security chromium update is built
against the new version of libc from "testing". Adding "proposed-updates" repo just makes installing
the new libc possible. Which 1) can be also achieved by just adding "testing" repo and
2) can be not desirable for the users of STABLE repository.

(WTF this distro has fallen down to...)

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

#377822

[Multipart message — attachments visible in raw view] — view raw

On Sat, 07 Dec 2024 22:27:52 +0500, Alex Volkov <alex@bootes.sytes.net> wrote:
> On Sat, 7 Dec 2024 01:18:41 +0100 Santiago Vila <sanvila@debian.org> wrote:
> > > Is this really a work-around?  
> > 
> > Yes, it is. (try it!)
> > 
> > The problem is that the new chrome package is in security but
> > some of its dependencies do not exist at all in security and
> > are only in bookworm-proposed-updates.
> > 
> > So you need both security + bookworm-proposed-updates.
> 
> No, it's not a "workaround". The problem is that security chromium update
> is built against the new version of libc from "testing". Adding
> "proposed-updates" repo just makes installing the new libc possible. Which
> 1) can be also achieved by just adding "testing" repo and 2) can be not
> desirable for the users of STABLE repository.

proposed-updates contains the updates which will be added to stable in the
next point release. It’s perfectly reasonable for users of the stable
repository, and *nothing* like adding the testing repository.

Regards,

Stephen

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

#377833

[Multipart message — attachments visible in raw view] — view raw

Stephen Kitt <skitt@debian.org> (2024-12-07):
> On Sat, 07 Dec 2024 22:27:52 +0500, Alex Volkov <alex@bootes.sytes.net> wrote:
> > On Sat, 7 Dec 2024 01:18:41 +0100 Santiago Vila <sanvila@debian.org> wrote:
> > > > Is this really a work-around?  
> > > 
> > > Yes, it is. (try it!)
> > > 
> > > The problem is that the new chrome package is in security but
> > > some of its dependencies do not exist at all in security and
> > > are only in bookworm-proposed-updates.
> > > 
> > > So you need both security + bookworm-proposed-updates.
> > 
> > No, it's not a "workaround". The problem is that security chromium update
> > is built against the new version of libc from "testing". Adding
> > "proposed-updates" repo just makes installing the new libc possible. Which
> > 1) can be also achieved by just adding "testing" repo and 2) can be not
> > desirable for the users of STABLE repository.
> 
> proposed-updates contains the updates which will be added to stable in the
> next point release. It’s perfectly reasonable for users of the stable
> repository, and *nothing* like adding the testing repository.

bookworm-updates (which is different, recommended, and enabled by
default on at least d-i based installations) is getting the packages as
well:
  https://lists.debian.org/debian-stable-announce/2024/12/msg00000.html

bookworm-proposed-updates is indeed usually reasonable (and developers
should feel free to opt in to help test those updates before they are
published via a point release), even if regressions can happen there
(just like that can happen anywhere else).


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

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

#377837 — Bug#1089181: chromium: Stable update wants to remove chromium package itself

[Multipart message — attachments visible in raw view] — view raw

On Sat, 7 Dec 2024 23:53:36 +0100 Cyril Brulebois <kibi@debian.org> wrote:
> bookworm-updates (which is different, recommended, and enabled by
> default on at least d-i based installations) is getting the packages as
> well:
>   https://lists.debian.org/debian-stable-announce/2024/12/msg00000.html

That message advises "apt full-upgrade" which I am familiar with.  In
this case I was simply using the "u" and "U" commands in the aptitude
TUI which caught me out.  Using the advised command installed the needed
dependencies and upgraded Chromium without adding the
'bookworm-proposed-updates' repository.

Thank you.

- Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

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

#378054 — Bug#1089181: chromium: security update wants to remove chromium package itself

[Multipart message — attachments visible in raw view] — view raw

Are those library updates part of the security update?

    The following packages will be REMOVED:
      libc++1-16 libc++abi1-16 libunwind-16
    The following NEW packages will be installed:
      libc++1-19 libc++abi1-19 libunwind-19
    The following packages will be upgraded:
      chromium chromium-common chromium-sandbox

I don't recall seeing this before in Debian Stable, so I'm hesitant to
install the `chromium` security update.

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

#378229 — Bug#1089181: marked as done (chromium: security update wants to remove chromium package itself)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Thu, 12 Dec 2024 14:25:49 -0500
with message-id <7a93abe5-436e-47b5-9aee-5b879251138e@queued.net>
and subject line Re: Bug#1089181: chromium: security update wants to remove chromium package itself
has caused the Debian Bug report #1089181,
regarding chromium: security update wants to remove chromium package itself
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.)


-- 
1089181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089181
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

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

#378623 — Bug#1089181: chromium still not installable via debian-live

Package: chromium
Version: 131.0.6778.108-1~deb12u1

Dear Maintainer (CC-ing the debian-live mailing-list),

the chromium package seems still not being installable via debian-live
on bookworm. Here is the message i get when trying to build a
debian-live that includes the chromium package:

[2024-12-17 00:02:24] lb chroot_install-packages install
P: Begin installing packages (install pass)...
Reading package lists...
Building dependency tree...
Reading state information...
Package chromium is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  chromium-shell chromium-sandbox chromium-common chromium-bsu

E: Package 'chromium' has no installation candidate
E: An unexpected failure occurred, exiting...
P: Begin unmounting filesystems...
P: Saving caches...

Ciao,
Thierry

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

#378645 — Bug#1089181: chromium still not installable via debian-live

Le Mon, Dec 16, 2024 at 07:47:25PM -0500, Andres Salomon a écrit :
> I don't know how it debian-live works, is it using an outdated mirror or
> something? 131.0.6778.139-1~deb12u1 is currently in both stable-security and
> stable-proposed-updates.

The mirror is http://deb.debian.org/debian (which resolves to an IP from
FASTLY, US).

Looking at the logs, debian-live seems not to completely rely on apt,
since some files like
http://deb.debian.org/debian//dists/bookworm/main/Contents-all.gz seem
to be downloaded by hand (i am not even sure their signature is
verified), though some comments says it is about firmware installation,
so it should not be the problem.

Ciao,
Thierry



> 
> 
> On 12/16/24 18:19, Thierry wrote:
> > Package: chromium
> > Version: 131.0.6778.108-1~deb12u1
> > 
> > Dear Maintainer (CC-ing the debian-live mailing-list),
> > 
> > the chromium package seems still not being installable via debian-live
> > on bookworm. Here is the message i get when trying to build a
> > debian-live that includes the chromium package:
> > 
> > [2024-12-17 00:02:24] lb chroot_install-packages install
> > P: Begin installing packages (install pass)...
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> > Package chromium is not available, but is referred to by another package.
> > This may mean that the package is missing, has been obsoleted, or
> > is only available from another source
> > However the following packages replace it:
> >    chromium-shell chromium-sandbox chromium-common chromium-bsu
> > 
> > E: Package 'chromium' has no installation candidate
> > E: An unexpected failure occurred, exiting...
> > P: Begin unmounting filesystems...
> > P: Saving caches...
> > 
> > Ciao,
> > Thierry
> > 
> 

[toc] | [prev] | [standalone]

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

csiph-web