Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #247342 > unrolled thread
| Started by | Tom Browder <tom.browder@gmail.com> |
|---|---|
| First post | 2022-04-18 13:40 +0200 |
| Last post | 2022-04-18 16:50 +0200 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.debian.user
Google Chrome and Bullseye upgrade: stable or bullseye Tom Browder <tom.browder@gmail.com> - 2022-04-18 13:40 +0200
Re: Google Chrome and Bullseye upgrade: stable or bullseye Greg Wooledge <greg@wooledge.org> - 2022-04-18 13:50 +0200
Re: Google Chrome and Bullseye upgrade: stable or bullseye Tom Browder <tom.browder@gmail.com> - 2022-04-19 00:30 +0200
Re: Google Chrome and Bullseye upgrade: stable or bullseye Tixy <tixy@yxit.co.uk> - 2022-04-18 16:50 +0200
| From | Tom Browder <tom.browder@gmail.com> |
|---|---|
| Date | 2022-04-18 13:40 +0200 |
| Subject | Google Chrome and Bullseye upgrade: stable or bullseye |
| Message-ID | <EdxTz-9y7f-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
I have all my apt lists ready for upgrading from Buster to Bullseye except the separate one for Google Chrome. It currently says "stable" and it has been that way through several upgrades. The instructions for the prep for the upgrade say that stable should be bullseye, but the text inside the file says it was automatically installed (I assume by Google years ago when I first downloaded it). My question is: can anyone tell me what my file should say? The best answer would be "it makes no difference" OR "keep it 'stable'." In any event, this time, before the upgrade, I will put an appropriate note in the Google file. Thanks so much for your help. -Tom
[toc] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2022-04-18 13:50 +0200 |
| Message-ID | <Edy3f-9yax-1@gated-at.bofh.it> |
| In reply to | #247342 |
On Mon, Apr 18, 2022 at 06:37:04AM -0500, Tom Browder wrote: > I have all my apt lists ready for upgrading from Buster to Bullseye except > the separate one for Google Chrome. It currently says "stable" and it has > been that way through several upgrades. That's fine. I've done buster to bullseye with that specific third-party repository in place, and it works without any issues. Even after the upgrade to bullseye, it continues to work. unicorn:~$ cat /etc/apt/sources.list.d/google-chrome.list ### THIS FILE IS AUTOMATICALLY CONFIGURED ### # You may comment out this entry, but any other modifications may be lost. deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main unicorn:~$ cat /etc/debian_version 11.3
[toc] | [prev] | [next] | [standalone]
| From | Tom Browder <tom.browder@gmail.com> |
|---|---|
| Date | 2022-04-19 00:30 +0200 |
| Message-ID | <EdI2B-9EpJ-3@gated-at.bofh.it> |
| In reply to | #247343 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, Apr 18, 2022 at 06:40 Greg Wooledge <greg@wooledge.org> wrote: > On Mon, Apr 18, 2022 at 06:37:04AM -0500, Tom Browder wrote: > > I have all my apt lists ready for upgrading from Buster to Bullseye > except > > the separate one for Google Chrome. It currently says "stable" and it has > > been that way through several upgrades. > > That's fine. I've done buster to bullseye with that specific third-party > repository in place, and it works without any issues. Even after the > upgrade to bullseye, it continues to work. Thanks, that’s what I suspected. I’ll leave it as is and press on! Thanks, all, consider this issue closed successfully. -Tom
[toc] | [prev] | [next] | [standalone]
| From | Tixy <tixy@yxit.co.uk> |
|---|---|
| Date | 2022-04-18 16:50 +0200 |
| Message-ID | <EdARr-9zQq-3@gated-at.bofh.it> |
| In reply to | #247342 |
On Mon, 2022-04-18 at 06:37 -0500, Tom Browder wrote: > I have all my apt lists ready for upgrading from Buster to Bullseye except > the separate one for Google Chrome. It currently says "stable" and it has > been that way through several upgrades. > > The instructions for the prep for the upgrade say that stable should be > bullseye, but the text inside the file says it was automatically installed > (I assume by Google years ago when I first downloaded it). > > My question is: can anyone tell me what my file should say? The best answer > would be "it makes no difference" OR "keep it 'stable'." If you install chrome by downloading the deb package from Google's site it creates /etc/apt/sources.list.d/google-chrome.list containing: ### THIS FILE IS AUTOMATICALLY CONFIGURED ### # You may comment out this entry, but any other modifications may be lost. deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main I bet 'stable' is the only release name that exists on their system, don't forget this package is also for Ubuntu and other distributions which use the Debian package format. -- Tixy
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web