Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #264564
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: IMPORTANT: do NOT upgrade to new stable point release |
| Date | 2023-12-10 22:30 +0100 |
| Message-ID | <HJzx7-cH2P-1@gated-at.bofh.it> (permalink) |
| References | <HJafn-craF-1@gated-at.bofh.it> |
| Organization | occasionally |
On Sat, 9 Dec 2023 13:09:23 -0500 Dan Ritter <dsr@randomstring.org> wrote: > https://fulda.social/@Ganneff/111551628003050712 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 > > The new kernel release is reported to contain an ext4 data > corruption bug. It's prudent not to upgrade, or if you have > started to upgrade, not to reboot, until a new kernel release > is prepared. > > > -dsr- > It appears the new, repaired, kernel and minor version of Bookworm have landed. Now, who wants to live dangerously? :-) root@tiassa:~# apt update Get:1 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB] Get:2 http://deb.debian.org/debian bookworm InRelease [151 kB] Get:3 http://deb.debian.org/debian bookworm/main amd64 Packages [8,787 kB] Get:4 http://deb.debian.org/debian bookworm/main Translation-en [6,109 kB] Fetched 15.1 MB in 3s (4,432 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 38 packages can be upgraded. Run 'apt list --upgradable' to see them. N: Repository 'http://deb.debian.org/debian bookworm InRelease' changed its 'Version' value from '12.3' to '12.4' root@tiassa:~# apt list --upgradable Listing... Done … libudev1/stable 252.19-1~deb12u1 amd64 [upgradable from: 252.17-1~deb12u1] linux-image-amd64/stable 6.1.66-1 amd64 [upgradable from: 6.1.55-1] linux-libc-dev/stable 6.1.66-1 amd64 [upgradable from: 6.1.55-1] … root@tiassa:~# -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
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