Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #265138
| Path | csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod |
|---|---|
| From | Charles Curley <charlescurley@charlescurley.com> |
| Newsgroups | linux.debian.user |
| Subject | Re: Is there a problem with Linux-image-6.1.0-16? |
| Date | Fri, 22 Dec 2023 05:50:01 +0100 |
| Message-ID | <HNFDX-feAt-3@gated-at.bofh.it> (permalink) |
| References | <HNwU1-f9jj-1@gated-at.bofh.it> |
| X-Mailbox-Line | From debian-user-request@lists.debian.org Fri Dec 22 04:49:01 2023 |
| Old-Return-Path | <charlescurley@charlescurley.com> |
| X-Amavis-Spam-Status | No, score=-6.811 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no |
| X-Policyd-Weight | passed - too many local DNS-errors in FROM A lookup for charlescurley.com |
| X-Authority-Analysis | v=2.4 cv=fda+dmcF c=1 sm=1 tr=0 ts=6585151f a=NgvI/wQFGgfv1u5PwVnSLQ==:117 a=NgvI/wQFGgfv1u5PwVnSLQ==:17 a=OWjo9vPv0XrRhIrVQ50Ab3nP57M=:19 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=jNgewbD4JndfM4UX:21 a=kj9zAlcOel0A:10 a=e2cXIFwxEfEA:10 a=0MQ0SXDd6YYA:10 a=jxrieLU6AAAA:8 a=xNf9USuDAAAA:8 a=UPwgjlzBAAAA:8 a=KH_-Fj22USvAXkb_besA:9 a=CjuIK1q_8ugA:10 a=TfaunOexjHoA:10 a=GmvXTHKmlJoA:10 a=kxKMlZqHyt1nwbGoqFYG:22 a=SEwjQc04WA-l_NiBhQ7s:22 a=IJG1HS28PhTFVN2WG8Av:22 |
| Organization | occasionally |
| X-Mailer | Claws Mail 4.1.1 (GTK 3.24.24; x86_64-pc-linux-gnu) |
| MIME-Version | 1.0 |
| Content-Type | text/plain; charset=US-ASCII |
| Content-Transfer-Encoding | 7bit |
| X-Antiabuse | This header was added to track abuse, please include it with any abuse report |
| X-Antiabuse | Primary Hostname - box5635.bluehost.com |
| X-Antiabuse | Original Domain - lists.debian.org |
| X-Antiabuse | Originator/Caller UID/GID - [47 12] / [47 12] |
| X-Antiabuse | Sender Address Domain - charlescurley.com |
| X-Bwhitelist | no |
| X-Source-IP | 67.218.77.85 |
| X-Source-L | No |
| X-Exim-ID | 1rGXSY-001HSI-3D |
| X-Source-Sender | (jhegaala.localdomain) [67.218.77.85]:50954 |
| X-Source-Auth | charlescurley@charlescurley.com |
| X-Email-Count | 1 |
| X-Org | HG=bhshared;ORG=bluehost; |
| X-Source-Cap | Y2hhcmxpYTM7Y2hhcmxpYTM7Ym94NTYzNS5ibHVlaG9zdC5jb20= |
| X-Local-Domain | yes |
| X-Cmae-Envelope | MS4xfBh4On9IlY1819J0z71wWazabYngFtZHYTnnMtXX+ZFeM+xyu4GBIffrcgVGT6S2SEK7L416mH/Q19NIlgZCsQ2ZVjak9Kt88dRzdt2whHyuwxT6DaEP QugNLubTCBh04Or/2Yr9P10HfPjUykK2dZhfHBlrlhV4/FhGGd2ddbN2LXZCEhXH2Sj8TmwIPfK0SObgn0G9tg/QdQj6OeNo6lzMhHW67r4vLxyAfQTvg8iF |
| X-Mailing-List | <debian-user@lists.debian.org> archive/latest/806946 |
| List-ID | <debian-user.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-user/> |
| List-Archive | https://lists.debian.org/msgid-search/20231221214828.7b35e343@jhegaala.localdomain |
| Approved | robomod@news.nic.it |
| Lines | 44 |
| Sender | robomod@news.nic.it |
| X-Original-Date | Thu, 21 Dec 2023 21:48:28 -0700 |
| X-Original-Message-ID | <20231221214828.7b35e343@jhegaala.localdomain> |
| X-Original-References | <1ec07054-1e32-4b2b-baab-c4561f20e58b@extremeground.com> |
| Xref | csiph.com linux.debian.user:265138 |
Show key headers only | View raw
On Thu, 21 Dec 2023 09:02:34 -0500 Gary Dale <gary@extremeground.com> wrote: > Several days ago my main server upgraded to kernel 6.1.0-16 but > various other devices that are also running Bookworm seem stuck at > 6.1.0-13. They are all using the same architecture. Some are using > the same mirror as the server that upgraded. I haven't set any > special policies on upgrades. I saw similar here. Of four machines here running Bookworm, three have kernels: linux-image-6.1.0-15-amd64 6.1.66-1 linux-image-6.1.0-16-amd64 6.1.67-1 but one has: linux-image-6.1.0-13-amd64 6.1.55-1 linux-image-6.1.0-15-amd64 6.1.66-1 However, I found that the latter machine has the following in /etc/apt/sources.list: # bookworm-updates, to get updates before a point release is made; # see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports # Line commented out by installer because it failed to verify: #deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware # deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware whereas the others three have: # bookworm-updates, to get updates before a point release is made; # see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware # deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware Uncommenting the bookworm-updates line got me the missing kernel. You might try the same. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
Is there a problem with Linux-image-6.1.0-16? Gary Dale <gary@extremeground.com> - 2023-12-21 20:30 +0100 Re: Is there a problem with Linux-image-6.1.0-16? Greg Wooledge <greg@wooledge.org> - 2023-12-21 21:00 +0100 Re: Is there a problem with Linux-image-6.1.0-16? Charles Curley <charlescurley@charlescurley.com> - 2023-12-22 05:50 +0100
csiph-web