Processing of nfs-utils_2.6.4-4_sourceonly.changes

2024-04-06 Thread Debian FTP Masters
nfs-utils_2.6.4-4_sourceonly.changes uploaded successfully to localhost along with the files: nfs-utils_2.6.4-4.dsc nfs-utils_2.6.4-4.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1067829: marked as done (nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-We

2024-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 07 Apr 2024 05:21:43 + with message-id and subject line Bug#1067829: fixed in nfs-utils 1:2.6.4-4 has caused the Debian Bug report #1067829, regarding nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but

nfs-utils_2.6.4-4_sourceonly.changes ACCEPTED into unstable

2024-04-06 Thread Debian FTP Masters
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Apr 2024 07:01:47 +0200 Source: nfs-utils Architecture: source Version: 1:2.6.4-4 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By:

Bug#1068515: linux: nolapic makes live image in VM unbootable

2024-04-06 Thread Roland Clobus
Source: linux Version: 6.7.9-2 Severity: normal Hello maintainers of the Linux kernel, Since the upgrade from 6.6.15-2 to 6.7.9-2 in sid, I've noticed in openQA [1] that in grub the boot option intended for safe booting does not result in a bootable VM any more. I've reduced the kernel boot

Bug#1067829: Fails to build on arm{el,hf} with 64bit time_t: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-We

2024-04-06 Thread Chuck Lever III
> On Apr 6, 2024, at 3:15 PM, Salvatore Bonaccorso wrote: > > Hi Chuck, hi Steve, > > In Debian, as you might have heard there is a 64bit time_t > transition[1] ongoing affecting the armel and armhf architectures. > While doing so, nfs-utils was found to fail to build for those >

Processed: bug 1067829 is forwarded to https://lore.kernel.org/linux-nfs/zhgfupxclzeoz...@eldamar.lan/T/#u

2024-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1067829 > https://lore.kernel.org/linux-nfs/zhgfupxclzeoz...@eldamar.lan/T/#u Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4

Processed: tagging 1067829

2024-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1067829 + confirmed pending Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’}

Bug#1067829: Fails to build on arm{el,hf} with 64bit time_t: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-We

2024-04-06 Thread Salvatore Bonaccorso
Hi Chuck, hi Steve, In Debian, as you might have heard there is a 64bit time_t transition[1] ongoing affecting the armel and armhf architectures. While doing so, nfs-utils was found to fail to build for those architectures after the switch, reported in Debian as [2]. Vladimir Petko from Ubuntu

Processed: tagging 1067829

2024-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1067829 + upstream Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=] Added

Bug#1068356: linux-image-6.1.0-18-amd64: it's working as expected - please delete this bug report

2024-04-06 Thread Veek M
Package: src:linux Followup-For: Bug #1068356 X-Debbugs-Cc: vek.m1...@gmail.com Please ignore this bug report - it's working as expected and isn't a bug