Processing of linux-signed-amd64_5.2.17+1+b1_source.changes

linux-signed-amd64_5.2.17+1+b1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_5.2.17+1+b1.dsc linux-signed-amd64_5.2.17+1+b1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#942089: linux-signed-amd64: version number not handled correctly by dpkg-genchanges

Source: linux Source-Version: 5.2.17-1 Severity: important Please do not use "+b1" in versions for the generated source template for linux-signed-* as this confuses dpkg (#942087). I suggest to mangle the version to ".b1" or so instead (debian-installer-netboot-images already uses this scheme).

Bug#940138: linux-image-5.2.0-2-amd64: panic in pci_assign_unassigned_root_bus_resources

Are there any news? Is there any more debug info that I could provide? Kendy On Fri, Sep 13, 2019 at 8:16 AM Kendy Kutzner wrote: > > Attaching the requested output. > > One thing I noted: The crash happens reliably at about 0.6s. The dmesg > output from a 4.19 start looks like this: > > [0.

Bug#866122: kernel resolution

Thank you Barry (and Gustavo) for providing closure on this one. :) On Thu, Sep 12, 2019 at 04:18:00PM -0500, Barry Arndt wrote: One of the problems was introduced in 4.12, and the other in 4.15. For posterity I should note that I first encountered the issue back in 4.9 and bisected it to dc1

Processed: reassign 942004 to src:linux

Processing commands for cont...@bugs.debian.org: > reassign 942004 src:linux 5.2.9-2 Bug #942004 [linux-image-5.2.0-0.bpo.2-marvell] INSTALL: buster-backports linux-image 5.2 fails during installation on QNAP TS-219P II Bug reassigned from package 'linux-image-5.2.0-0.bpo.2-marvell' to 'src:linux

Re: Dependency is not satisfiable

On Tue, 2019-10-08 at 03:21 +0300, john smith wrote: > The package requires > linux-headers-4.19.0-0.bpo.6-common_4.19.67-2+deb10u1~bpo9+1_amd64 > but the corresponding package in stretch-backports is called > linux-headers-4.19.0-0.bpo.6-common_4.19.67-2~bpo9+1_amd64 > which leads to a broken depe

Processed: control

Processing commands for cont...@bugs.debian.org: > tags 940848 patch Bug #940848 [src:nfs-utils] nfs-utils: CVE-2019-3689: root-owned files stored in insecure /var/lib/nfs Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 940848: https://bugs.de

Bug#940848: nfs-utils:CVE-2019-3689: root-owned files stored in insecure /var/lib/nfs

Hi, I submitted the following patch to address this issue: https://salsa.debian.org/debian/nfs-utils/merge_requests/3/diffs The source part of the fix was also submitted at: https://bugzilla.linux-nfs.org/show_bug.cgi?id=338 I intend to push it to LTS/ELTS, I can also prepare an upload for stabl

Processed: control

Processing commands for cont...@bugs.debian.org: > forwarded 940848 https://bugzilla.linux-nfs.org/show_bug.cgi?id=338 Bug #940848 [src:nfs-utils] nfs-utils: CVE-2019-3689: root-owned files stored in insecure /var/lib/nfs Set Bug forwarded-to-address to 'https://bugzilla.linux-nfs.org/show_bug.c

Bug#941122: e1000e is slooow for I219-LM

def4ec6dce39 ("e1000e: PCIm function state support") would be in 5.3-rc1 and above and was not backported. If you test the package from experimental, is the issue gone? If you cherry-pick this commit on top is the issue gone? I tried installing the linux-image-5.3.0-trunk-amd64 package from exp

Bug#942004: INSTALL: buster-backports linux-image 5.2 fails during installation on QNAP TS-219P II

Ok, so I actually took the plunge and tried option 2 above, as follows (it appears the backport-kernel was updated from 5.2.9-2 to 5.2.17-1 overnight): 1. sudo vi /usr/share/flash-kernel/db/all.db    -> /219 -> line 1447:    change   Mtd-Kernel: Kernel    to   Mtd-Kernel: RootFS2 2. sudo