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

Groups > linux.debian.bugs.rc > #377833

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

Show all headers | View raw

[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

Back to linux.debian.bugs.rc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

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

csiph-web