Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #264514
| From | "Niall O'Reilly" <niall+lists@no8.be> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: IMPORTANT: do NOT upgrade to new stable point release |
| Date | 2023-12-10 17:00 +0100 |
| Message-ID | <HJunM-cDPO-11@gated-at.bofh.it> (permalink) |
| References | <HJafn-craF-1@gated-at.bofh.it> <HJaS5-crCN-3@gated-at.bofh.it> <HJb1L-crFL-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 9 Dec 2023, at 19:18, Michael Kjörling wrote:
> If you are on 6.1.55-1 (or earlier), just hold off on
> upgrades for now; and if you need to upgrade something else, take
> great care for now to ensure that no Linux kernel packages get
> upgraded to any version < 6.1.66, and preferably not < 6.1.66-1.
TSM for this advice.
As I'm not used to having to "take great care" like this, I would
appreciate confirmation that what I've done is likely to be useful.
I've dropped a file into /etc/apt/preferences.d/ containing
the following text.
Package: linux-image-amd64
Pin: version 6.1.55-1
Pin-Priority: 1100
As I noticed that an upgrade to 6.1.64-1 was also in line for
linux-libc-dev, I did the same for this package too.
As a result, apt-cache policy is telling me
linux-image-amd64:
Installed: 6.1.55-1
Candidate: 6.1.55-1
Version table:
6.1.64-1 500
500 https://ftp.debian.org/debian bookworm/main amd64 Packages
*** 6.1.55-1 1100
100 /var/lib/dpkg/status
6.1.52-1 500
500 https://security.debian.org/debian-security bookworm-security/main amd64 Packages
linux-libc-dev:
Installed: 6.1.55-1
Candidate: 6.1.55-1
Version table:
6.1.64-1 500
500 https://ftp.debian.org/debian bookworm/main amd64 Packages
*** 6.1.55-1 1100
100 /var/lib/dpkg/status
6.1.52-1 500
500 https://security.debian.org/debian-security bookworm-security/main amd64 Packages
Thanks in anticipation of a simple yes or no.
Niall O'Reilly
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
IMPORTANT: do NOT upgrade to new stable point release Dan Ritter <dsr@randomstring.org> - 2023-12-09 19:30 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Nate Bargmann <n0nb@n0nb.us> - 2023-12-09 19:50 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2023-12-09 20:00 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Alexis Grigoriou <alexis@nanoid.net> - 2023-12-09 20:10 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-09 20:20 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Greg Wooledge <greg@wooledge.org> - 2023-12-09 20:30 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Richmond <dnomhcir@gmx.com> - 2023-12-09 21:00 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-09 21:00 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Joe <joe@jretrading.com> - 2023-12-09 22:20 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release "Niall O'Reilly" <niall+lists@no8.be> - 2023-12-10 17:00 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Gary Dale <gary@extremeground.com> - 2023-12-10 18:00 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-10 18:00 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Curt <curty@free.fr> - 2023-12-10 18:10 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-10 18:30 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release <tomas@tuxteam.de> - 2023-12-10 18:30 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release John Hasler <john@sugarbit.com> - 2023-12-10 18:40 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Greg Wooledge <greg@wooledge.org> - 2023-12-10 18:30 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Gary Dale <gary@extremeground.com> - 2023-12-10 19:00 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Curt <curty@free.fr> - 2023-12-10 19:50 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Nicholas Geovanis <nickgeovanis@gmail.com> - 2023-12-10 20:40 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release <tomas@tuxteam.de> - 2023-12-10 20:50 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Gary Dale <gary@extremeground.com> - 2023-12-10 19:30 +0100
6.1.0-15/6.1.66-1 broken too? Kevin Price <kp@osnanet.de> - 2023-12-10 20:20 +0100
Re: 6.1.0-15/6.1.66-1 broken too? "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-10 20:30 +0100
Re: 6.1.0-15/6.1.66-1 broken too? Kevin Price <kp@osnanet.de> - 2023-12-11 00:00 +0100
Re: 6.1.0-15/6.1.66-1 broken too? Kevin Price <kp@osnanet.de> - 2023-12-11 12:20 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Charles Curley <charlescurley@charlescurley.com> - 2023-12-10 22:30 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-10 22:50 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Gary Dale <gary@extremeground.com> - 2023-12-11 17:40 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Махно <mindaugasceliesius@gmail.com> - 2023-12-11 17:50 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Махно <mindaugasceliesius@gmail.com> - 2023-12-11 17:50 +0100
Re: IMPORTANT: do NOT upgrade to new stable point release Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-11 17:50 +0100
csiph-web