Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #66517 > unrolled thread
| Started by | jim_p <pitsiorisj@gmail.com> |
|---|---|
| First post | 2020-03-12 10:00 +0100 |
| Last post | 2020-03-30 15:50 +0200 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.debian.kernel
Bug#953680: linux-image-5.5.0-rc5-amd64: When will the stable version of 5.5 reach the repos? jim_p <pitsiorisj@gmail.com> - 2020-03-12 10:00 +0100
Bug#953680: marked as done (linux-image-5.5.0-rc5-amd64: When will the stable version of 5.5 reach the repos?) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-03-30 10:20 +0200
Bug#953680: linux-image-5.5.0-rc5-amd64: When will the stable version of 5.5 reach the repos? jim_p <pitsiorisj@gmail.com> - 2020-03-30 14:00 +0200
Bug#953680: linux-image-5.5.0-rc5-amd64: When will the stable version of 5.5 reach the repos? Laurence Parry <greenreaper@gmail.com> - 2020-03-30 15:50 +0200
| From | jim_p <pitsiorisj@gmail.com> |
|---|---|
| Date | 2020-03-12 10:00 +0100 |
| Subject | Bug#953680: linux-image-5.5.0-rc5-amd64: When will the stable version of 5.5 reach the repos? |
| Message-ID | <zJrR7-6ho-1@gated-at.bofh.it> |
Package: linux-image-5.5.0-rc5-amd64 Severity: normal Kernel 5.5 was released more than a month ago, on January 26th 2020, and it has not reached the repos yet. There is only its rc5 revision, which isn't the last rc, and it is on experimental only. Why? Meanwhile, 5.6, now on rc5, will be released in a couple of weeks, so maybe you should skip 5.5 altogether. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-5.5.0-rc5-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.136 ii kmod 27-1 ii linux-base 4.6 Versions of packages linux-image-5.5.0-rc5-amd64 recommends: pn apparmor <none> ii firmware-linux-free 20200122-1 Versions of packages linux-image-5.5.0-rc5-amd64 suggests: pn debian-kernel-handbook <none> ii extlinux 3:6.04~git20190206.bf6db5b4+dfsg1-2 ii grub-pc 2.04-5 pn linux-doc-5.5 <none>
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2020-03-30 10:20 +0200 |
| Subject | Bug#953680: marked as done (linux-image-5.5.0-rc5-amd64: When will the stable version of 5.5 reach the repos?) |
| Message-ID | <zPXOj-4vw-47@gated-at.bofh.it> |
| In reply to | #66517 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Mon, 30 Mar 2020 08:10:09 +0000 with message-id <E1jIpUn-000G7D-Hy@fasolo.debian.org> and subject line Bug#953680: fixed in linux 5.5.13-1 has caused the Debian Bug report #953680, regarding linux-image-5.5.0-rc5-amd64: When will the stable version of 5.5 reach the repos? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 953680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953680 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | jim_p <pitsiorisj@gmail.com> |
|---|---|
| Date | 2020-03-30 14:00 +0200 |
| Message-ID | <zQ1fc-6qz-9@gated-at.bofh.it> |
| In reply to | #66517 |
Source: linux Followup-For: Bug #953680 I just got the email that notified me that this bug report was closed because kernel 5.5 (5.5.13 in fact) has reached unstable. Kernel 5.6 was released yesterday from upstream, so isn't it a bit late now for 5.5? Normally, I install it as soon as it hits the repo, then I let dkms fail in building nvidia legacy 340 for it, so I file a bug report for the driver, along with the needed patches. I think I will skip it this time and wait for 5.6, sorry. On top of that, I think that you should have built at least one minor update of 5.4 all that time, because the 5.4 is now at 5.4.28, 9 minor versions ahead than the one on the repo. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
[toc] | [prev] | [next] | [standalone]
| From | Laurence Parry <greenreaper@gmail.com> |
|---|---|
| Date | 2020-03-30 15:50 +0200 |
| Message-ID | <zQ2XE-7vC-3@gated-at.bofh.it> |
| In reply to | #66654 |
[Multipart message — attachments visible in raw view] — view raw
> Kernel 5.6 was released yesterday > from upstream, so isn't it a bit late > now for 5.5? From what I've seen, it's not unusual for Debian's kernel team to wait several minor point releases until there is a kernel they're happy with - indeed, I wouldn't be surprised if the policy is to wait until the initial version of the *next* major release is out. Often early kernel revisions have a fair share of issues - often not limited to the new features added in that major release. They are typically also backported to otherwise stable systems, so picking a good revision has some importance. Meanwhile, most fixes do make it into earlier stable kernels. To take one example, 5.5.9 had a fix for btrfs' new checksum feature, which didn't work properly with direct I/O. So if you updated to 5.5 on its initial release and made a new FS to use it, you might have had an unpleasant surprise and spent a lot of time debugging a problem. There was also a nasty bug in early 5.2 releases which led to delayed writes not being flushed to disk, and ultimately data loss. Unfortunately in that case it was fixed too late and made it into Debian backports. But usually, the delay helps to avoid that kind of thing. Of course, if you really want a new feature, you can download and compile a kernel yourself, either from kernel.org - which is what I ended up doing to get those checksums - using Debian's git repo. But that has the risk of not-fully-working code, so I'll probably be sticking with the 5.5.13 I have rather than going to 5.6 right away. As for a later release of 5.4, one of the Debian kernel team members indicated on the list a few weeks ago that they preferred to go to 5.5, which is what has ended up happening: https://lists.debian.org/debian-kernel/2020/03/msg00086.html Best regards, -- Laurence "GreenReaper" Parry
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web