Re: Why don't we have linux-5.0 instead of 4.19.0-4 which is the running kernel in Debian 'buster' i.e. testing ?

❦ 6 avril 2019 02:14 +00, shirish शिरीष : > Currently we are using 4.19.0-4 according to the lastest updated > systems on buster . > > $ uname -r > 4.19.0-4-amd64 > > I see that 4.20 has been taken out of the archive and the 5.0 is there > but in experimental - > > $ apt-cache policy linux-image

Why don't we have linux-5.0 instead of 4.19.0-4 which is the running kernel in Debian 'buster' i.e. testing ?

Dear Kernel team, Please CC as I'm not subscribed to the list . I saw the following news item few days back - https://news.softpedia.com/news/linux-kernel-4-20-reaches-end-of-life-users-urged-to-upgrade-to-linux-5-0-525461.shtml http://lkml.iu.edu/hypermail/linux/kernel/1903.2/02285.html Curre

Processed: RE: FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major'

Processing control commands: > severity -1 important Bug #926483 [src:nfs-utils] FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major' Severity set to 'important' from 'serious' > tags -1 unreproducible moreinfo Bug #926483 [src:nfs-utils] FTBFS: utils/blkmapd/device-discove

Bug#895381: rpc.gssd: WARNING: handle_gssd_upcall: failed to find uid in upcall string 'mech=krb5'

On Tue, Apr 10, 2018 at 10:12:35PM +0200, Sergio Gelato wrote: > One of my systems has logged > rpc.gssd[1168]: WARNING: handle_gssd_upcall: failed to find uid in upcall > string 'mech=krb5' > > This turns out to be a known problem, covered extensively in > https://bugzilla.redhat.com/show_bug.cg

Bug#926483: FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major'

Source: nfs-utils Version: 1:1.3.4-2.4 Severity: serious The package fails to build from source (actually current Git branch debian/sid, but that has no changes that I could imagine causing this) in a clean sid chroot on amd64: /usr/bin/ld: device-discovery.o: in function `bl_add_disk': /home/mic

Bug#884562: Enable CONFIG_SND_SOC_SPDIF for cubietruck spdif

Ping ? I have opened a merge request https://salsa.debian.org/kernel-team/linux/merge_requests/137

Bug#926468: linux-image-4.19.0-4-amd64: the k10temp module does not read CPU temperature any more

Package: src:linux Version: 4.19.28-2 Severity: normal I used to read core CPU temperature from /sys/class/hwmon/hwmon0/temp1_input Now that file always reads 0, and the real temperature is found in /sys/class/hwmon/hwmon1/temp1_input Maybe this is due to k10temp not reading the temperature an

Bug#925967: upgrade to linux-image-4.19.0-4-amd64 fails to show login; unresponsive box.

Package: src:linux Version: 4.19.28-2 Severity: important Dear Maintainer, First, I apologize if I have omitted something.  This is my first attempt to file a bug report. *** Reporter, please consider answering these questions, where appropriate ***    * What led up to the situation? routin

Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

> However it might be reasonable to add "nomodeset" to the command line > in GRUB's "recovery" boot menu items. OK, great. Now all that is left is for me to help you figure out why the installer incorrectly detects that the drivers are available, etc. I am able to workaround all this, I just want