Bug#1067927: Please display changelog for all versions between current and upgrade
Package: fwupd Version: 1.9.14-1 Severity: normal X-Debbugs-Cc: j...@joshtriplett.org When fwupd proposes upgrading firmware (e.g. BIOS), it shows the changelog for the target version. However, typically that changelog only states the changes made in the most recent version. If the user is upgrading from, say, 1.50 to 1.53, showing the changelog for 1.53 does not explain the changes in 1.51 and 1.52. Please consider addressing this by providing a way to view the changelogs for all the versions in between. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 6.7.9-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages fwupd depends on: ii adduser3.137 ii libarchive13 3.7.2-1 ii libc6 2.37-15 ii libcbor0.100.10.2-1.2 ii libcurl3-gnutls8.6.0-3 ii libflashrom1 1.3.0-2.1+b1 ii libfwupd2 1.9.14-1 ii libglib2.0-0 2.78.4-1 ii libgnutls303.8.3-1 ii libgudev-1.0-0 238-3 ii libgusb2 0.4.8-1 ii libjcat1 0.2.0-2 ii libjson-glib-1.0-0 1.8.0-2 ii liblzma5 5.6.0-0.2 ii libmbim-glib4 1.30.0-1 ii libmbim-proxy 1.30.0-1 ii libmm-glib01.22.0-3 ii libpolkit-gobject-1-0 124-1 ii libprotobuf-c1 1.4.1-1+b1 ii libqmi-glib5 1.34.0-2 ii libqmi-proxy 1.34.0-2 ii libsqlite3-0 3.45.1-1 ii libsystemd0255.3-2 ii libtss2-esys-3.0.2-0 4.0.1-7 ii libxmlb2 0.3.14-2 ii shared-mime-info 2.4-1 ii zlib1g 1:1.3.dfsg-3+b1 Versions of packages fwupd recommends: ii bolt 0.9.6-2 ii dbus 1.14.10-4 ii fwupd-amd64-signed [fwupd-signed] 1:1.4+1 ii jq 1.7.1-3 ii python33.11.6-1 pn secureboot-db ii udisks22.10.1-5 Versions of packages fwupd suggests: pn gir1.2-fwupd-2.0 -- Configuration Files: /etc/fwupd/fwupd.conf [Errno 13] Permission denied: '/etc/fwupd/fwupd.conf' -- no debconf information
Bug#1067926: awesfx: kernel warning message when asfxload runs on post 6.8.0 kernels
Package: awesfx Version: 0.5.2-1.1+b1 Severity: normal Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? running asfxload on post 6.8.0 kernel * What exactly did you do (or not do) that was effective (or ineffective)? sound font still loaded but the warning message below appeared * What was the outcome of this action? [ 107.151337] [ cut here ] [ 107.152114] refcount_t: decrement hit 0; leaking memory. [ 107.152871] WARNING: CPU: 3 PID: 1817 at lib/refcount.c:31 refcount_warn_saturate+0xff/0x110 [ 107.153619] Modules linked in: binfmt_misc nf_tables libcrc32c nfnetlink scsi_transport_iscsi exfat it87 hwmon_vid parport_pc ppdev lp parport rtl2832_sdr videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev fc0012 rtl2832 i2c_mux regmap_i2c dvb_usb_rtl28xxu dvb_usb_v2 dvb_core mc snd_emu10k1_synth snd_emux_synth snd_seq_midi_emul snd_seq_virmidi snd_seq_midi snd_seq_midi_event snd_hda_codec_hdmi snd_seq snd_emu10k1 snd_hda_intel snd_intel_dspcfg snd_util_mem snd_hda_codec snd_ac97_codec edac_mce_amd sha512_ssse3 sha512_generic ac97_bus sha256_ssse3 sha1_ssse3 radeon aesni_intel snd_hda_core snd_rawmidi crypto_simd cryptd evdev serio_raw snd_hwdep drm_ttm_helper ttm drm_suballoc_helper drm_display_helper snd_seq_device snd_pcm emu10k1_gp pcspkr k10temp gameport acpi_cpufreq drm_kms_helper drm snd_timer i2c_algo_bit snd video soundcore wmi sp5100_tco button ext4 crc32c_generic crc16 mbcache jbd2 uas usb_storage hid_generic usbhid hid sg sd_mod t10_pi sr_mod crc64_rocksoft crc64 cdrom ata_generic [ 107.153675] ahci pata_atiixp libahci ohci_pci firewire_ohci r8169 libata firewire_core xhci_pci crc32_pclmul crc32c_intel crc_itu_t realtek ohci_hcd ehci_pci xhci_hcd i2c_piix4 ehci_hcd mdio_devres scsi_mod usbcore scsi_common libphy usb_common [ 107.159752] CPU: 3 PID: 1817 Comm: asfxload Not tainted 6.9.0-rc1+ #5857 [ 107.160716] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./F2A78M-HD2, BIOS F2 05/28/2014 [ 107.161668] RIP: 0010:refcount_warn_saturate+0xff/0x110 [ 107.162607] Code: b8 4e c1 a6 c6 05 32 cc 08 01 01 e8 1b ce b8 ff 0f 0b e9 b4 74 54 00 48 c7 c7 10 4f c1 a6 c6 05 16 cc 08 01 01 e8 01 ce b8 ff <0f> 0b e9 9a 74 54 00 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 [ 107.163592] RSP: 0018:9db6c3147c38 EFLAGS: 00010286 [ 107.164587] RAX: 002c RBX: e656c472acc0 RCX: [ 107.165574] RDX: 0002 RSI: 9db6c3147ae8 RDI: [ 107.166559] RBP: 0011cab3 R08: efff R09: a6ea70e8 [ 107.167544] R10: f000 R11: 9db6c27da000 R12: 9db6c28aa000 [ 107.168539] R13: R14: R15: [ 107.169523] FS: 7efd158ceb80() GS:8ba06f98() knlGS: [ 107.170520] CS: 0010 DS: ES: CR0: 80050033 [ 107.171518] CR2: 7efd15523bdd CR3: 0001297d4000 CR4: 000406f0 [ 107.172533] Call Trace: [ 107.173536] [ 107.174533] ? refcount_warn_saturate+0xff/0x110 [ 107.175534] ? __warn.cold+0xa8/0x107 [ 107.176544] ? refcount_warn_saturate+0xff/0x110 [ 107.177542] ? report_bug+0x10e/0x1a0 [ 107.178536] ? handle_bug+0x3a/0x70 [ 107.179527] ? exc_invalid_op+0x1f/0x90 [ 107.180522] ? __wake_up_klogd.part.0+0x56/0x80 [ 107.181508] ? asm_exc_invalid_op+0x16/0x20 [ 107.182493] ? refcount_warn_saturate+0xff/0x110 [ 107.183475] ? refcount_warn_saturate+0xff/0x110 [ 107.184459] free_unref_page_prepare+0x1b3/0x330 [ 107.185434] free_unref_page+0x44/0x1f0 [ 107.186402] __iommu_dma_free.isra.0+0xe5/0x160 [ 107.187372] __synth_free_pages+0x79/0xb0 [snd_emu10k1] [ 107.188365] snd_emu10k1_synth_free+0xa3/0xf0 [snd_emu10k1] [ 107.189343] snd_emu10k1_sample_free+0x28/0x50 [snd_emu10k1_synth] [ 107.190290] snd_sf_clear+0x71/0x110 [snd_emux_synth] [ 107.191212] snd_soundfont_remove_samples+0x6d/0xb0 [snd_emux_synth] [ 107.192142] snd_emux_hwdep_ioctl+0x4f/0x210 [snd_emux_synth] [ 107.193055] snd_hwdep_ioctl+0xc7/0x1d0 [snd_hwdep] [ 107.193955] ? security_file_ioctl+0x3c/0x60 [ 107.194845] __x64_sys_ioctl+0x316/0xae0 [ 107.195735] ? do_sys_openat2+0x80/0xc0 [ 107.196624] do_syscall_64+0x50/0x110 [ 107.197488] entry_SYSCALL_64_after_hwframe+0x6c/0x74 [ 107.198356] RIP: 0033:0x7efd155c432b [ 107.199213] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 107.200121] RSP: 002b:7ffcf350e330 EFLAGS: 0246 ORIG_RAX: 0010 [ 107.201028] RAX: ffda RBX: 0002 RCX: 7efd155c432b [ 107.201923] RDX: RSI: 4882 RDI: 0003 [ 107.202808] RBP: 7ffcf350e588 R08:
Bug#1067715: closed by yokota (Re: Bug#1067715: calibre: doesn't install DeACSM plugin)
Hello, > Please, don't close bugs just because they are fixed upstream, the > fixed-upstream exists exactly for this. I think it's external plugin's bug and not Calibre's bug. But I will keep this bug open as you requested. If you think the bug is fixed, let me know. Or close this bug by yourself. Best regards, -- YOKOTA
Bug#1067895: RFS: emacs-format-all-the-code/0.6.0-1 [Team] -- Auto-format C, C++, JS, Python, Ruby and 50 other languages
Sean Whitton writes: > control: tag -1 + moreinfo > > Looks like the Source: in d/copyright is bogus? Ah indeed. Fixed in [1], recompiled and uploaded to mentors as well. PTAL. [1] https://salsa.debian.org/emacsen-team/emacs-format-all-the-code/-/commit/92cfb4b866bfe4fb3200f13c42850b3febfe -- Xiyue Deng
Bug#1067896: Acknowledgement (libraptor2-0: memcpy integer underflow and heap read overflow)
I rewrote a bit of the first issue to better understand it, and also
provide a patch:
## 1. Integer Underflow in `raptor_uri_normalize_path()`
There's an integer underflow in a path length calculation in
`raptor_uri_normalize_path()`.
This can be triggered by running the PoC below:
```
utils/rapper -i turtle memcpy_int_underflow.poc
rapper: Parsing URI file:///memcpy_int_underflow.poc with parser turtle
rapper: Serializing with serializer ntriples
free(): invalid pointer
Aborted
```
With an ASAN build of `rapper` we can more clearly see the issue without
the need of a debugger:
```
raptor-asan/utils/rapper -i turtle memcpy_int_underflow.poc
rapper: Parsing URI file:///memcpy_int_underflow.poc with parser turtle
rapper: Serializing with serializer ntriples
=
==2406522==ERROR: AddressSanitizer: negative-size-param: (size=-5)
#0 0x5f90a3e1cf33 in __interceptor_memcpy
(/raptor/raptor-asan/utils/.libs/rapper+0x3cf33) (BuildId:
31b11a035fdbbfb23ddb7c1a5db60302956622be)
#1 0x7c902fa96e5a in raptor_uri_resolve_uri_reference
(/raptor/raptor/src/.libs/libraptor2.so.0+0x19e5a) (BuildId:
9edf75a105deaf007b9332b0a0367c8ad4af744d)
#2 0x7c902fa9741c in raptor_new_uri_relative_to_base_counted
(/raptor/raptor/src/.libs/libraptor2.so.0+0x1a41c) (BuildId:
9edf75a105deaf007b9332b0a0367c8ad4af744d)
#3 0x7c902fa9747a in raptor_new_uri_relative_to_base
(/raptor/raptor/src/.libs/libraptor2.so.0+0x1a47a) (BuildId:
9edf75a105deaf007b9332b0a0367c8ad4af744d)
#4 0x7c902fab93fc in turtle_lexer_lex
(/raptor/raptor/src/.libs/libraptor2.so.0+0x3c3fc) (BuildId:
9edf75a105deaf007b9332b0a0367c8ad4af744d)
#5 0x7c902fabc3ec in turtle_parser_parse
(/raptor/raptor/src/.libs/libraptor2.so.0+0x3f3ec) (BuildId:
9edf75a105deaf007b9332b0a0367c8ad4af744d)
#6 0x7c902fabebb9 in turtle_parse turtle_parser.c
#7 0x7c902fabf3ff in raptor_turtle_parse_chunk turtle_parser.c
#8 0x7c902fa92de4 in raptor_parser_parse_chunk
(/raptor/raptor/src/.libs/libraptor2.so.0+0x15de4) (BuildId:
9edf75a105deaf007b9332b0a0367c8ad4af744d)
#9 0x7c902fa92fc1 in raptor_parser_parse_file_stream
(/raptor/raptor/src/.libs/libraptor2.so.0+0x15fc1) (BuildId:
9edf75a105deaf007b9332b0a0367c8ad4af744d)
#10 0x7c902fa93174 in raptor_parser_parse_file
(/raptor/raptor/src/.libs/libraptor2.so.0+0x16174) (BuildId:
9edf75a105deaf007b9332b0a0367c8ad4af744d)
#11 0x5f90a3ed9492 in main
(/raptor/raptor-asan/utils/.libs/rapper+0xf9492) (BuildId:
31b11a035fdbbfb23ddb7c1a5db60302956622be)
#12 0x7c902f7816c9 in __libc_start_call_main
csu/../sysdeps/nptl/libc_start_call_main.h:58:16
#13 0x7c902f781784 in __libc_start_main csu/../csu/libc-start.c:360:3
#14 0x5f90a3e01650 in _start
(/raptor/raptor-asan/utils/.libs/rapper+0x21650) (BuildId:
31b11a035fdbbfb23ddb7c1a5db60302956622be)
(...)
SUMMARY: AddressSanitizer: negative-size-param
(/raptor/raptor-asan/utils/.libs/rapper+0x3cf33) (BuildId:
31b11a035fdbbfb23ddb7c1a5db60302956622be) in __interceptor_memcpy
==2406522==ABORTING
```
The crash occurs because `raptor_uri_normalize_path()`, which does some
complicated jiggling to normalize paths, and fails to take into account
integer underflows. The function will not be shown here as it is quite
complex.
`raptor_uri_normalize_path()` is called from
`raptor_uri_resolve_uri_reference()` to normalize a path, and the crash
occurs in a juicy `memcpy()` inside `raptor_uri_resolve_uri_reference()`
(`raptor_rfc2396.c:664`) where `result.path_len` is the underflowed
integer (ASAN's `negative-size-param`), and `result.path` is attacker
controlled:
```c
if(result.path) {
memcpy(p, result.path, result.path_len);
p+= result.path_len;
}
```
The non-ASAN crash in `free()` shown at the top occurs in line 685:
```c
if(path_buffer)
RAPTOR_FREE(char*, path_buffer);
```
The fix, however, is rather simple! The function contains several of
these checks after each calculation:
```c
#if defined(RAPTOR_DEBUG)
if(path_len != strlen((const char*)path_buffer))
RAPTOR_FATAL3("Path length %ld does not match calculated %ld.",
(long)strlen((const char*)path_buffer), (long)path_len);
#endif
```
If we remove the `#if defined` / `#endif` around this code in lines 396
and 399, we get an error instead of a crash:
`raptor_rfc2396.c:397:raptor_uri_normalize_path: fatal error: Path
length 0 does not match calculated -5.Aborted`
### 1.1 Steps to reproduce
`rapper -i turtle memcpy_int_underflow.poc`
Contents of `memcpy_int_underflow.poc`:
```
@base .
@prefix bdf: <.&/../?D/../../1999/02/22-rdf-syntax-ns#>/dbpe
```
### 1.2 Patch
```diff
diff --git a/src/raptor_rfc2396.c b/src/raptor_rfc2396.c
index 89183d96..f58710c5 100644
--- a/src/raptor_rfc2396.c
+++ b/src/raptor_rfc2396.c
@@ -393,10 +393,8 @@ raptor_uri_normalize_path(unsigned char*
path_buffer, size_t path_len)
}
-#if defined(RAPTOR_DEBUG)
if(path_len !=
Bug#1059262: trilinos: add loongarch64 support
Hi maintainers, On Fri, 22 Dec 2023 09:17:19 + Zhang Na wrote: > Source: trilinos > Version: 13.2.0-5 > Severity: normal > X-Debbugs-Cc: zhan...@loongson.cn > > Dear Maintainer, > > Please add loong64 support in debian/control, thanks! The trilinos itself blocks the compilation of many packages. Based on the attached patch, the trilinos package was compiled successfully on my local loong64 rootfs environment. I have built 132 binary packages from trilinos on local ENV. Could you enable loong64 support in debian/control in the next upload? Your suggestions are always welcome. Thanks, Dandan Zhang
Bug#1067925: RFS: fastfetch/2.8.10 [ITP] -- Fastfetch is a neofetch-like tool for fetching system information and displaying them in a pretty way.
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "fastfetch": * Package name : fastfetch Version : 2.8.10 Upstream contact : [fill in name and email of upstream] * URL : https://github.com/fastfetch-cli/fastfetch * License : Expat * Vcs : [fill in URL of packaging vcs] Section : universe/utils The source builds the following binary packages: fastfetch - Fastfetch is a neofetch-like tool for fetching system information and displaying them in a pretty way. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fastfetch/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/f/fastfetch/fastfetch_2.8.10.dsc Changes for the initial release: fastfetch (2.8.10) unstable; urgency=medium . * Init debian support Regards, -- Carter Li
Bug#1067321: cachy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Hi Lucas, Sorry, I cannot reproduce this error. I tried running the package locally and in the salsa-ci [0] [0] https://salsa.debian.org/python-team/packages/cachy/-/pipelines/658758 -- cheers, Emmanuel Arias ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ eam...@debian.org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1 ⠈⠳⣄ OpenPGP_0xFA9DEC5DE11C63F1.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1067895: RFS: emacs-format-all-the-code/0.6.0-1 [Team] -- Auto-format C, C++, JS, Python, Ruby and 50 other languages
control: tag -1 + moreinfo Looks like the Source: in d/copyright is bogus? -- Sean Whitton
Bug#1067771: cdk.h file location has changed, breaks application build
On Thu, Mar 28, 2024 at 08:55:04PM -0400, Thomas Dickey wrote: > On Thu, Mar 28, 2024 at 11:15:04AM -0500, Steven Robbins wrote: > > Hello Thomas! > > > > Thanks for chiming in on this issue. I had sent a follow-up at about the > > same > > time you did with a few details on the history as I could reconstruct it. > > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067771#18 > > > > In summary: I believe you changed the default location from to > > in 2012, adding a configure option at the same time. When this > > version > > was uploaded to Debian (much later), a debian-specific patch was added to > > retain the original location. Four years ago, the previous debian > > maintainer > > removed that patch - but was never uploaded to debian unstable. I took > > over > > maintenance a month ago and inadvertently uploaded to unstable a version > > where > > the header change from 2012 was exposed for the first time. > > ...yes - I didn't record a reason for the change, so likely what prompted it > was noting that cdk.h includes all of the other files, which makes it > inconsistent to put it in the same subdirectory as the others. fwiw, I do the > same for dialog. > > Just in case someone disagreed, I made it configurable. I suppose that I _could_ have made a symlink in /usr/include/cdk, to address both old/new locations. You might consider that for the package... -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1067924: dgit: can't clone/fetch dockerfile-mode past few days
Package: dgit Version: 11.6 Severity: important spwhitton@chiark:~/tmp>dgit clone dockerfile-mode canonical suite name for unstable is sid fetching existing git history fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. dgit: failed command: git ls-remote -q --refs https://git.dgit.debian.org/dockerfile-mode 'refs/tags/archive/debian/*' 'refs/tags/debian/*' refs/dgit/sid refs/dgit-rewrite/map dgit: error: subprocess failed with error exit status 128 255 spwhitton@chiark:~/tmp> I was able to successfully dgit push the package, after doing an import-dsc for the purposes I wanted to fetch. -- Sean Whitton
Bug#1067771: cdk.h file location has changed, breaks application build
On Thu, Mar 28, 2024 at 11:15:04AM -0500, Steven Robbins wrote: > Hello Thomas! > > Thanks for chiming in on this issue. I had sent a follow-up at about the > same > time you did with a few details on the history as I could reconstruct it. > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067771#18 > > In summary: I believe you changed the default location from to > in 2012, adding a configure option at the same time. When this > version > was uploaded to Debian (much later), a debian-specific patch was added to > retain the original location. Four years ago, the previous debian maintainer > removed that patch - but was never uploaded to debian unstable. I took over > maintenance a month ago and inadvertently uploaded to unstable a version > where > the header change from 2012 was exposed for the first time. ...yes - I didn't record a reason for the change, so likely what prompted it was noting that cdk.h includes all of the other files, which makes it inconsistent to put it in the same subdirectory as the others. fwiw, I do the same for dialog. Just in case someone disagreed, I made it configurable. > I can see a valid argument for retaining the Debian practice. But when I > discovered that the upstream change was 12 years old, I figured that there > are > likely other folks long used to the "new" header location and have adapted > their code. So there is also a valid argument to adhering to the upstream > location and harmonizing the landscape for code using libcdk. > > I actually did a search on github and discovered examples of all three cases: > * code using only > * code using only > * code that probes both locations and uses the one found > > I'm wondering whether you have an opinion on the merits of one path versus > the > other. Do you have any information about how much currently-maintained > software is still using ? not really (actually I don't keep track for any of my programs) In a quick check of other packages that I know about, I don't see any using the subdirectory. (I've corrected the configure option, just for tidiness). > At present, I'm leaning towards retaining the default location . I suppose it depends on how many packages have to be tweaked. (actually in the current set of changes for time_t, I'd suppose that changes like this would be less favored) -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1067923: alsa-ucm-conf: should depend on libasound2t64 instead of libasound2
Package: alsa-ucm-conf Version: 1.2.11-1 Severity: serious Justification: depends on missing package after time_t transition Dear maintainer, After the time_t transition, the libasound2 was renamed to libasound2t64, so the dependencies should be updated. Regards, -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages alsa-ucm-conf depends on: ii libasound2t64 [libasound2] 1.2.11-1+b1 alsa-ucm-conf recommends no packages. alsa-ucm-conf suggests no packages. -- no debconf information
Bug#1067891: nmu: memcached_1.6.23-1
Control: reopen -1 On Thu, Mar 28, 2024 at 04:12:19PM +0100, Sebastian Ramacher wrote: > On 2024-03-28 13:46:14 +, Colin Watson wrote: > > Package: release.debian.org > > Severity: normal > > X-Debbugs-Cc: memcac...@packages.debian.org > > Control: affects -1 + src:memcached > > User: release.debian@packages.debian.org > > Usertags: binnmu > > > > nmu memcached_1.6.23-1 . armel armhf . unstable . -m "Rebuild for time_t" > > Scheduled Argh, I got the version wrong, sorry. My fault for trusting reportbug while running testing ... nmu memcached_1.6.24-1 . armel armhf . unstable . -m "Rebuild for time_t" Thanks, -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#1064765: prometheus: FTBFS: dh_auto_test error
Version: 2.45.3+ds-3 El 28/3/24 a las 23:38, Daniel Swarbrick escribió: On 28.03.24 23:33, Santiago Vila wrote: If you prefer I could report this build failure in a new report (or you can also use the clone command so that the bug has a new number, then close the old bug). Please report a new bug, with just the relevant info regarding the new build failure. Ok, will do. Closing this one, then. We already override the default test timeout for arm, mips64el and riscv64 to 60 minutes, as well as set "-short", because otherwise those archs simply take too long to grind through all the tests. If you expect these tests to pass on a host with only one or two cores, we will certainly need to raise the test timeout, even for fast amd64 hosts. Yes, I expect it to work on all systems on which prometheus itself works. (And as a prometheus user myself, I've used it in all sort of systems, big or small). Thanks.
Bug#1067902: elpa-debian-el: regression regarding apt-sources-mode and still warnings (comp)
Control: retitle -1 elpa-debian-el: regression regarding apt-sources-mode Control: tags -1 pending Xiyue Deng writes: > > BTW, please feel free to file one bug per issue which helps us tracking > those issues. Thanks for your reports! > I have filed a separate bug[1] for tracking the comp warnings issue. Meanwhile, the regression should be handled by this commit[2]. I'll try to request another release with other fixes when ready. [1] https://bugs.debian.org/1067922 [2] https://salsa.debian.org/emacsen-team/debian-el/-/commit/84f1eb293bb57fe888c274fa8533217060651a57 -- Xiyue Deng
Bug#1067909: libc-devtools: please relax Depends on libgd3
On 2024-03-28 20:35, Martin-Éric Racine wrote: > Package: libc-devtools > Severity: normal > > libgd3 pulls an excessive amount of dependencies, including fonts. It would > thus be desirable to downgrade it to a mere Recommends. > The /usr/bin/memusagestat binary is linked against libgd3, so we can't just changes the Depends to a Recommends. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net signature.asc Description: PGP signature
Bug#1067876: dpkg allows installation of malformed .deb packages resulting in corrupt .list file
Hi! On Thu, 2024-03-28 at 09:54:36 +, Grueninger, Tobias wrote: > Package: dpkg > Version: 1.20.12 > Severity: wishlist > In our case we did install a package from a 3rd party which apparently > uses a non-conforming .deb package building tool (unknown to us) > resulting in a malformed data.tar.gz > dpkg did allow this package to be completely installed but generated a > malformed .list file. Ah, not good, indeed. > This as consequence did prevent later installation of any other package > as dpkg's .list file database was broken resulting in the following > error message > > Selecting previously unselected package . > (Reading database ... > dpkg: unrecoverable fatal error, aborting: >files list file for package 'xxx-config--xxx' contains empty filename > > Analysis of the .deb package showed > > dpkg -c xxx-config-xxx.deb > 1 drwxrwxr-x root/root 0 2023-09-07 08:36 ./ > 2 drwxrwxr-x root/root 0 2023-09-07 08:36 .// > 3 drwxrwxr-x root/root 0 2023-09-07 08:36 .//ddd/ > 4 drwxrwxr-x root/root 0 2023-09-07 08:36 .//ddd/fff/ > ... > > * The offending malform is the second line containing './/' which is not > conform to standard, resulting in the following .list file > > cat -v -t -e ./lib/dpkg/info/xxx-config-xxx.list > 1 /.$ > 2 /$ > 3 /ddd$ > 4 /ddd/fff$ > ... > > * the '/$' does break the .list file parsing when later installing other > .deb packages > > Clearly the root cause is the use of 3rd party malformed .deb package > tooling nevertheless my wish to improve would be following: > > 1. As dpkg does parse all existing .list files during installation of >a .deb package and understand if one of them is malformed it shall >do this also for the newly generated .deb package .list file. > 2. If the newly generated .deb package .list file does fail the check >installation shall be aborted and rolled back. Thank you for the detailed and very helpful report! I've prepare a couple of changes to catch these conditions, will check whether there are more things that should be verified, and add some test cases for these. Will queue these file git main and probably mark them as stable candidates. Thanks, Guillem
Bug#1064765: prometheus: FTBFS: dh_auto_test error
On 28.03.24 23:33, Santiago Vila wrote: If you prefer I could report this build failure in a new report (or you can also use the clone command so that the bug has a new number, then close the old bug). Please report a new bug, with just the relevant info regarding the new build failure. We already override the default test timeout for arm, mips64el and riscv64 to 60 minutes, as well as set "-short", because otherwise those archs simply take too long to grind through all the tests. If you expect these tests to pass on a host with only one or two cores, we will certainly need to raise the test timeout, even for fast amd64 hosts. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1064765: prometheus: FTBFS: dh_auto_test error
El 28/3/24 a las 22:42, Daniel Swarbrick escribió: I think you are taking the "FAILED" out of context and misinterpreting the test output. This is very likely, yes, and I'm sorry for that. If you prefer I could report this build failure in a new report (or you can also use the clone command so that the bug has a new number, then close the old bug). Thanks.
Bug#1067922: elpa-debian-el: Comp warnings
Package: elpa-debian-el Version: 37.11 Severity: normal X-Debbugs-Cc: debian-emac...@lists.debian.org, Xiyue Deng , Jörg-Volker Peetz This is the second part of the bug report from Bug#1067902 by Jörg-Volker Peetz : , | And there are still comp warnings when using debian-bug: | | Warning (comp): debian-bug.el:858:29: Warning: reference to free variable | ‘term-exec-hook’ | Warning (comp): debian-bug.el:931:16: Warning: ‘message’ called with 1 args | to fill 0 format field(s) | Warning (comp): debian-bug.el:861:10: Warning: the function ‘term-exec’ might | not be defined at runtime. ` Filing a separate bug here to ease tracking. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (200, 'proposed-updates') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-18-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-debian-el depends on: ii bzip2 1.0.8-5+b1 ii dh-elpa-helper 2.1.2~bpo12+0manphiz1 ii emacsen-common 3.0.5 ii reportbug 12.0.0 ii xz-utils5.4.1-0.2 Versions of packages elpa-debian-el recommends: ii emacs 1:29.3+1-2~bpo12+0manphiz1 ii emacs-gtk [emacs] 1:29.3+1-2~bpo12+0manphiz1 ii wget 1.21.3-1+b2 elpa-debian-el suggests no packages. -- no debconf information
Bug#1064765: prometheus: FTBFS: dh_auto_test error
As expected: === RUN TestQuerierIndexQueriesRace/[m!="0"___name__="metric"] panic: test timed out after 20m0s ... FAILgithub.com/prometheus/prometheus/tsdb 1200.016s On 28.03.24 23:13, Santiago Vila wrote: Ok, I'm attaching one of my build logs for version 2.45.3+ds-3. This one was tried on a m6a.large instance from AWS, which has 2 CPUs. Thanks. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1064765: prometheus: FTBFS: dh_auto_test error
El 28/3/24 a las 22:42, Daniel Swarbrick escribió: Please can you find in your logs the _actual_ failing test or tests, because it is not TestRulesUnitTest. Ok, I'm attaching one of my build logs for version 2.45.3+ds-3. This one was tried on a m6a.large instance from AWS, which has 2 CPUs. Thanks. prometheus_2.45.3+ds-3_amd64-20240325T141933.921Z.gz Description: application/gzip
Bug#1001786: jpeg-xl: Please enable gdk-pixbuf plugin
Hi Andreas, On Tue, 13 Jun 2023 18:00:51 + Debian FTP Masters wrote: > jpeg-xl (0.9.0~git20230612.38b629f-1) experimental; urgency=medium ... >* d/rules: Build gdk-pixbuf plugin. Closes: #1001786 > That version was removed from experimental without being uploaded to unstable. We can see what was done in the snapshot and the maintainer did this by recovering from the snapshot sending to Salsa the work he had done and sent to the experimental. The issue is that we need a volunteer to finish the work, test and send it to unstable to resolve bugs (including CVEs), patches and send new versions of some other packages. A work that I see as delicate and needs to be well tested to guarantee quality. I would have to check if the Salsa snapshot matches the previous one, which it doesn't, new uploads still need to enter the experimental and I would have to check with the maintainer that I'm already pinging if he would be interested in continuing what he was doing given that he already has knowledge. And work has been done, the version 0.10.2 being pending can be upload done, which includes several fixes. But looking at Salsa there are many commits pending. Furthermore, there is a person who is reporting some problems with patch suggestions that would also have to be analyzed, his name is Julian Wollrath. But I want to see if I can help organize everything yet and an upload NMU is possible. https://salsa.debian.org/leandrocunha/libjxl/-/tree/0.9-snapshot?ref_type=heads https://snapshot.debian.org/package/jpeg-xl/0.9.0~git20230623.689da0f-4/
Bug#1064765: prometheus: FTBFS: dh_auto_test error
On 28.03.24 15:00, Santiago Vila wrote: In either case, this is still happening for me in the current version: Lucas Nussbaum wrote: FAILED: 1:48: parse error: unexpected character inside braces: '0' I think you are taking the "FAILED" out of context and misinterpreting the test output. Those are TestRulesUnitTest/* subtests, which are expected to fail. The summary at the end shows the expected results: === RUN TestRulesUnitTest ... === RUN TestRulesUnitTest/Bad_input_series Unit Testing: ./testdata/bad-input-series.yml FAILED: 1:48: parse error: unexpected character inside braces: '0' ... --- PASS: TestRulesUnitTest (0.38s) --- PASS: TestRulesUnitTest/Passing_Unit_Tests (0.22s) --- PASS: TestRulesUnitTest/Long_evaluation_interval (0.13s) --- PASS: TestRulesUnitTest/Bad_input_series (0.00s) --- PASS: TestRulesUnitTest/Bad_PromQL (0.00s) --- PASS: TestRulesUnitTest/Bad_rules_(syntax_error) (0.00s) --- PASS: TestRulesUnitTest/Bad_rules_(error_evaluating) (0.00s) --- PASS: TestRulesUnitTest/Simple_failing_test (0.01s) --- PASS: TestRulesUnitTest/Disabled_feature_(@_modifier) (0.00s) --- PASS: TestRulesUnitTest/Enabled_feature_(@_modifier) (0.00s) --- PASS: TestRulesUnitTest/Disabled_feature_(negative_offset) (0.00s) --- PASS: TestRulesUnitTest/Enabled_feature_(negative_offset) (0.00s) You will see this in the output of _passing_ debci test runs. Please can you find in your logs the _actual_ failing test or tests, because it is not TestRulesUnitTest. If you are running tests on a VM with a single core, it's quite likely that you're hitting the test timeout, which I would find a more reasonable explanation for the dh_auto_test_error, since the Prometheus tests are quite extensive. They will take more than an hour on an 11th gen Intel Core i7 if I set GOMAXPROCS=1. Since debian/rules is setting a test timeout of 20m by default, this would fail. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1067130: modernizr: NMU or update to latest upstream 3.12 or 3.13
The merge request is now updated with the headers. Le 28 mars 2024 19:56:13 GMT+01:00, "Bastien Roucariès" a écrit : >Le jeudi 28 mars 2024, 18:36:54 UTC Fab Stz a écrit : >> To build modernizr an additional source file is required (file.js) this file >> is added to missing-sources (it comes from the npm package of the same name >> from npm server or from upstreams repo). It is required by the build script >> from upstream. >> >> The patch is only here to use that file. That way there is no need to create >> a Debian package for it (packaging npm nodes is beyond my knowledge and I'm >> not really interested in doing that). >> >> Concerning your other question, I don't understand it. The binary packages >> only ships the js & min.js, not the build script. The missing sources is >> required only by the build script iirc. > >Thanks, this should be documented in: >- the comment at the begiging of missing-source/file >- the header of patch see https://dep-team.pages.debian.net/deps/dep3/ >> >> >> Le 28 mars 2024 19:23:08 GMT+01:00, "Bastien Roucariès" a >> écrit : >> >Le jeudi 28 mars 2024, 18:16:09 UTC Fab Stz a écrit : >> >> Hello Bastien, >> >> >> >> Iirc not so many packages depend on it and none seems to use the files >> >> that are not shipped anymore in the binary package (the individual >> >> 'rules'). >> >> >> >> Concerning the build maybe you could look at d/rules on the merge >> >> request. It uses upstream's build script that builds the complete js. >> > >> >I do not understand: >> >- please document the patch using dep format >> >- explain how the build script do not ship in /usr/share >> >debian/missingsources >> > >> >bastien >> >> >> >> Regards >> >> Fab >> >> >> >> Le 28 mars 2024 18:54:27 GMT+01:00, "Bastien Roucariès" >> >> a écrit : >> >> >Le jeudi 28 mars 2024, 17:21:48 UTC Fab Stz a écrit : >> >> >> Dear Maintainers, >> >> >> >> >> >> I'm thinking of doing an NMU for the package by updating it to >> >> >> 3.13.0-0.1. The >> >> >> MR is now open since July 2023 and this bug referencing it has been >> >> >> existing >> >> >> for about 10 days (in case the MR wouldn't have been noticed). >> >> >> >> >> >> There is also bug >> >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001203 >> >> >> which request a newer version since 2021. >> >> >> >> >> >> BTW, I would require a sponsor to upload the NMU. >> >> >> >> >> >> Do you have advice or comment on this?* >> >> > >> >> >What is the state of reverse depends ? >> >> > >> >> >How does it build ? >> >> > >> >> >Bastien >> >> >> >> >> >> Regards >> >> >> Fab >> >> >> >> >> >> On Tue, 19 Mar 2024 08:58:23 +0100 Fab Stz >> >> >> wrote: >> >> >> > Source: modernizr >> >> >> > Version: update >> >> >> > Severity: wishlist >> >> >> > Tags: patch >> >> >> > >> >> >> > Dear Maintainer, >> >> >> > >> >> >> > Please update to latest upstream version 3.12 or 3.13 >> >> >> > >> >> >> > For 3.12 I created a merge request on the VCS at >> >> >> > >> >> >> > https://salsa.debian.org/js-team/modernizr/-/merge_requests/2 >> >> >> > >> >> >> > There is also one for 2.* in >> >> >> > >> >> >> > https://salsa.debian.org/js-team/modernizr/-/merge_requests/1 >> >> >> > >> >> >> > You just have to choose which you prefer or both one after the other. >> >> >> > >> >> >> > >> >> >> > >> >> >> > -- System Information: >> >> >> > Debian Release: 12.5 >> >> >> > APT prefers stable-updates >> >> >> > APT policy: (991, 'stable-updates'), (991, 'stable-security'), >> >> >> > (991, >> >> >> > 'stable'), (990, 'proposed-updates'), (390, 'oldstable-security'), >> >> >> > (390, >> >> >> > 'oldstable'), (389, 'oldstable-updates'), (380, 'oldoldstable'), >> >> >> > (379, >> >> >> > 'oldoldstable-updates'), (370, 'oldoldstable'), (95, 'testing'), >> >> >> > (94, >> >> >> > 'unstable'), (93, 'experimental') >> >> >> > Architecture: amd64 (x86_64) >> >> >> > Foreign Architectures: i386 >> >> >> > >> >> >> > Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) >> >> >> > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, >> >> >> > TAINT_UNSIGNED_MODULE >> >> >> > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), >> >> >> > LANGUAGE=fr:en_US >> >> >> > Shell: /bin/sh linked to /usr/bin/dash >> >> >> > Init: systemd (via /run/systemd/system) >> >> >> > LSM: AppArmor: enabled >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> =<3776087.mvXUDI8C0e.ref@debian> >> >> >> <3776087.mvXUDI8C0e@debian> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> > >> >
Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf
Wookey dixit: >And it worked beatifully. Thanks. Nice! >I'll try doing openjdk-20 next. You’ll want 21 as 20 has not got the t64 treatment. gl hf, //mirabilos -- 15:41⎜ Somebody write a testsuite for helloworld :-)
Bug#1067845: adduser: Reserving uid/gid from the uid/gid pools
On Wed, Mar 27, 2024 at 04:55:35PM +0200, Yair Yarom wrote: > The UID_POOL (and GID_POOL) files contains UIDs that should be used for given > name. It would be helpful to reserve the UIDs for the future, so that the > order > of adding users to the system won't affect the usability of the UIDs/names. > > I.e. if a UID is in the pool, it won't be used unless for the specific name in > the pool. That sounds sensible. Would you mind to contribute test cases as well? The canoncal place for those test cases would probably be debian/tests/f/uidgidpool.t Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#1067908: Acknowledgement (Enable I6300ESB_WDT)
I misspoke - a different watchdog will be provided for arm, so this request is for amd64 only. On Thu, Mar 28, 2024 at 11:15 AM Debian Bug Tracking System wrote: > > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1067908: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067908. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian Kernel Team > > If you wish to submit further information on this problem, please > send it to 1067...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1067908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067908 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems
Bug#1066842: Updating extrepo-offline-data in Debian Stable
Hi, On Thu, Mar 14, 2024 at 09:55:27AM +0200, Wouter Verhelst wrote: > The extrepo-offline-data package, as the name implies, is a data-only > package. Apart from the changelog and copyright in /usr/share/doc, it > only contains metadata files under /usr/share/extrepo/offline-data. I would accept such updates in stable now and in the future. What's the source debdiff this time around? Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Bug#1067921: FTBFS: error: call of overloaded ‘MSString(const time_t&)’ is ambiguous
Source: aplus-fsf Version: 4.22.1-13 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=aplus- fsf=armhf=4.22.1-13=1711588996=0 MSTime.C: In member function ‘virtual MSString MSTime::asDebugInfo() const’: MSTime.C:53:25: error: call of overloaded ‘MSString(const time_t&)’ is ambiguous 53 | result+=MSString(_time); | ^ In file included from ../MSTypes/MSScalarModel.H:37, from ../MSTypes/MSTime.H:15, from MSTime.C:10: -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1067829: 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=]
Emanuele Rocca dixit: >The attached patch by Vladimir Petko was sent upstream and fixes the >FTBFS on armhf/armel. The patch is catastrophically wrong. +- snprintf(flushtime, sizeof(flushtime), "%ld\n", now); ++ snprintf(flushtime, sizeof(flushtime), "%lld\n", now); Change that to: ++ snprintf(flushtime, sizeof(flushtime), "%lld\n", (long long)now); time_t is not guaranteed to be 64-bit (or even integer, by ISO C), it must always be coerced into the expected type for printf. Please forward this upstream as well. Might as well want to check that flushtime is large enough, too. bye, //mirabilos -- When he found out that the m68k port was in a pretty bad shape, he did not, like many before him, shrug and move on; instead, he took it upon himself to start compiling things, just so he could compile his shell. How's that for dedication. -- Wouter, about my Debian/m68k revival
Bug#1067844: c-evo-dh: Depends on dead-upstream mpg321 instead of mpg123
On 28/03/2024 17:26, Andreas Metzler wrote: Hi Andreas, There are loads of old bugs including rather severe ones at first glance. The fact that the packaging is very dated is not the real problem (Updating to dh could probably be done in in an , since it os basically a single binary package.) There is just a lot of technical debt due to missing upstream, it does not need maintainership but a new upstream author. Noted On my local system there simply is no sound output, I suspect it cannot work when pipewire or pulseaudio is used. It works perfectly for me on pulseaudio, however I can see you now raised a bug re pipewire. I'll use something else then, possibly sox, but guess I should wait until the transitions have cleared. Regards, Peter
Bug#1065264: phpseclib 1.0.20-1+deb12u2 flagged for acceptance
package release.debian.org tags 1065264 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: phpseclib Version: 1.0.20-1+deb12u2 Explanation: force system dependency loading; guard isPrime() and randomPrime() for BigInteger [CVE-2024-27354]; limit OID length in ASN1 [CVE-2024-27355]; fix BigInteger getLength()
Bug#1052674: ITS: mu-editor
Sure, please help if you want, I've granted you access to https://salsa.debian.org/python-team/packages/mu-editor/ to salvage this package. For long temps maintainer ship it's better to either join Python Team or adopt package. Greetings
Bug#1055451: prosody: Bug still present in prosody 0.12.4-1~bpo12+1
Package: prosody
Version: 0.12.4-1~bpo12+1
Followup-For: Bug #1055451
X-Debbugs-Cc: mnalis-debian...@voyager.hr
Control: tags -1 patch
Dear Maintainer,
I can confirm the issue is still present in prosody 0.12.4-1~bpo12+1 from
bookworm-backports, and affects all non-systemd installations. E.g.:
# /etc/init.d/prosody stop ; ps auxfw | grep prosod | grep -v grep
Stopping Prosody XMPP Server: prosody.
prosody 3005 0.0 0.1 54900 8344 ?S20:42 0:00 lua5.4
/usr/bin/prosody -D
Attached is a simple patch that fixes it.
In the future, /etc/init.d/prosody should be kept in sync with debian/control
"Depends:" field (i.e. if prosody depends on "lua5.4", then init.d script
should
reference "lua5.4" too).
-- System Information:
Debian Release: 12.5
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages prosody depends on:
ii adduser 3.134
ii init-system-helpers 1.65.2
ii libc6 2.36-9+deb12u4
ii libicu7272.1-3
ii libssl3 3.0.11-1~deb12u2
ii lua-bitop [lua5.4-bitop]1.0.2-7
ii lua-expat [lua5.4-expat]1.5.1-3
ii lua-filesystem [lua5.4-filesystem] 1.8.0-3
ii lua-sec [lua5.4-sec]1.2.0-2
ii lua-socket [lua5.4-socket] 3.1.0-1+b1
ii lua5.4 5.4.4-3
ii ssl-cert1.1.2
Versions of packages prosody recommends:
ii lua-event [lua5.4-event] 0.4.6-2+b1
ii lua-unbound [lua5.4-unbound] 1.0.0-2
pn lua5.4-readline
Versions of packages prosody suggests:
pn lua-dbi-mysql
pn lua-dbi-postgresql
pn lua-dbi-sqlite3
ii lua-zlib1.2-3
-- Configuration Files:
/etc/prosody/conf.avail/example.com.cfg.lua [Errno 13] Permission denied:
'/etc/prosody/conf.avail/example.com.cfg.lua'
/etc/prosody/conf.avail/localhost.cfg.lua [Errno 13] Permission denied:
'/etc/prosody/conf.avail/localhost.cfg.lua'
/etc/prosody/prosody.cfg.lua [Errno 13] Permission denied:
'/etc/prosody/prosody.cfg.lua'
-- no debconf information
--- /etc/init.d/prosody.org-bookworm2020-10-02 11:45:27.0 +0200
+++ /etc/init.d/prosody 2024-03-28 20:38:07.172873463 +0100
@@ -43,7 +43,7 @@
chown prosody:adm "$(dirname $PIDFILE)"
[ -x /sbin/restorecon ] && /sbin/restorecon `dirname $PIDFILE`
if start-stop-daemon --start --quiet --pidfile "$PIDFILE" \
- --chuid "$USER" --oknodo --user "$USER" --name lua5.2 \
+ --chuid "$USER" --oknodo --user "$USER" --name lua5.4 \
$(start_opts) --startas "$DAEMON" -- -D;
then
return 0
@@ -54,7 +54,7 @@
stop_prosody () {
if start-stop-daemon --stop --quiet --retry 30 \
- --oknodo --pidfile "$PIDFILE" --user "$USER" --name lua5.2;
+ --oknodo --pidfile "$PIDFILE" --user "$USER" --name lua5.4;
then
return 0
else
@@ -64,7 +64,7 @@
signal_prosody () {
if start-stop-daemon --stop --quiet --pidfile "$PIDFILE" \
- --user "$USER" --name lua5.2 --oknodo --signal "$1";
+ --user "$USER" --name lua5.4 --oknodo --signal "$1";
then
return 0
else
@@ -111,7 +111,7 @@
;;
status)
log_daemon_msg "Status of Prosody XMPP Server" "prosody "
- status_of_proc -p"$PIDFILE" lua5.2
+ status_of_proc -p"$PIDFILE" lua5.4
;;
*)
log_action_msg "Usage: /etc/init.d/prosody
{start|stop|restart|reload|status}"
Bug#1060378: cups: Disables USB network printers
Package: cups Version: 2.4.2-3+deb12u5 Followup-For: Bug #1060378 X-Debbugs-Cc: mkes...@fsfe.org Dear Maintainer, This effectively disables USB network printers from being found and used. Will probably be a showstopper for many people. Best wishes Michael -- System Information: Debian Release: 12.5 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cups depends on: ii cups-client2.4.2-3+deb12u5 ii cups-common2.4.2-3+deb12u5 ii cups-core-drivers 2.4.2-3+deb12u5 ii cups-daemon2.4.2-3+deb12u5 ii cups-filters 1.28.17-3 ii cups-ppdc 2.4.2-3+deb12u5 ii cups-server-common 2.4.2-3+deb12u5 ii debconf [debconf-2.0] 1.5.82 ii ghostscript10.0.0~dfsg-11+deb12u3 ii libavahi-client3 0.8-10 ii libavahi-common3 0.8-10 ii libc6 2.36-9+deb12u4 ii libcups2 2.4.2-3+deb12u5 ii libgcc-s1 12.2.0-14 ii libstdc++6 12.2.0-14 ii libusb-1.0-0 2:1.0.26-1 ii poppler-utils 22.12.0-2+b1 ii procps 2:4.0.2-3 Versions of packages cups recommends: ii avahi-daemon 0.8-10 ii colord1.4.6-2.2 Versions of packages cups suggests: ii cups-bsd2.4.2-3+deb12u5 ii foomatic-db 20230202-1 ii printer-driver-cups-pdf [cups-pdf] 3.0.1-14 ii smbclient 2:4.17.12+dfsg-0+deb12u1 ii udev252.22-1~deb12u1 -- debconf information: cupsys/raw-print: true cupsys/backend: lpd, socket, usb, snmp, dnssd
Bug#1067920: FTBFS: error: no matching function for call to ‘max(saidx64_t&, long int)
Source: phylonium Version: 1.7-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=phylonium=armhf=1.7-2=1711651088=0 process.cxx: In lambda function: process.cxx:222:39: error: no matching function for call to ‘max(saidx64_t&, long int)’ 222 | this_length = std::max(inter.l, 0l); | ^ In file included from /usr/include/c++/13/vector:62, from process.h:8, from process.cxx:6: /usr/include/c++/13/bits/stl_algobase.h:257:5: note: candidate: ‘template constexpr const _Tp& std::max(const _Tp&, const _Tp&)’ 257 | max(const _Tp& __a, const _Tp& __b) | ^~~ -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1066649: libtritonus-java: diff for NMU version 20070428-14.2
Control: tags 1066649 + patch Control: tags 1066649 + pending Dear maintainer, I've prepared an NMU for libtritonus-java (versioned as 20070428-14.2) and uploaded it to unstable. Regards. -- WBR, wRAR diff -Nru libtritonus-java-20070428/debian/changelog libtritonus-java-20070428/debian/changelog --- libtritonus-java-20070428/debian/changelog 2020-01-27 04:28:23.0 +0500 +++ libtritonus-java-20070428/debian/changelog 2024-03-29 00:44:52.0 +0500 @@ -1,3 +1,10 @@ +libtritonus-java (20070428-14.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066649). + + -- Andrey Rakhmatullin Fri, 29 Mar 2024 00:44:52 +0500 + libtritonus-java (20070428-14.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru libtritonus-java-20070428/debian/patches/fix-implicit-function-declaration.patch libtritonus-java-20070428/debian/patches/fix-implicit-function-declaration.patch --- libtritonus-java-20070428/debian/patches/fix-implicit-function-declaration.patch 1970-01-01 05:00:00.0 +0500 +++ libtritonus-java-20070428/debian/patches/fix-implicit-function-declaration.patch 2024-03-29 00:44:52.0 +0500 @@ -0,0 +1,29 @@ +Description: Add missing header includes. +Author: Andrey Rakhmatullin +Bug-Debian: https://bugs.debian.org/1066649 +Last-Update: 2024-03-28 + +Index: libtritonus-java-20070428/src/lib/pvorbis/org_tritonus_lowlevel_pogg_Buffer.c +=== +--- libtritonus-java-20070428.orig/src/lib/pvorbis/org_tritonus_lowlevel_pogg_Buffer.c libtritonus-java-20070428/src/lib/pvorbis/org_tritonus_lowlevel_pogg_Buffer.c +@@ -24,6 +24,7 @@ + |<---this code is formatted to fit into 80 columns --->| + */ + ++#include + #include "common.h" + #include "org_tritonus_lowlevel_pogg_Buffer.h" + +Index: libtritonus-java-20070428/src/lib/pvorbis/org_tritonus_lowlevel_pogg_Packet.c +=== +--- libtritonus-java-20070428.orig/src/lib/pvorbis/org_tritonus_lowlevel_pogg_Packet.c libtritonus-java-20070428/src/lib/pvorbis/org_tritonus_lowlevel_pogg_Packet.c +@@ -24,6 +24,7 @@ + |<---this code is formatted to fit into 80 columns --->| + */ + ++#include + #include "common.h" + #include "org_tritonus_lowlevel_pogg_Packet.h" + diff -Nru libtritonus-java-20070428/debian/patches/series libtritonus-java-20070428/debian/patches/series --- libtritonus-java-20070428/debian/patches/series 2020-01-27 04:28:02.0 +0500 +++ libtritonus-java-20070428/debian/patches/series 2024-03-29 00:44:52.0 +0500 @@ -9,3 +9,4 @@ java10-compatibility.diff bump-java-to-1.6.patch fluidsynth2.patch +fix-implicit-function-declaration.patch signature.asc Description: PGP signature
Bug#1036884: more trackers
Some additional smaller trackers that apparently didn't have binNMUs: https://release.debian.org/transitions/html/auto-ogre-1.12.html https://release.debian.org/transitions/html/auto-ros-ros-comm.html https://release.debian.org/transitions/html/auto-octomap.html https://release.debian.org/transitions/html/auto-poppler.html https://release.debian.org/transitions/html/auto-freerdp2.html Not sure if it's possible to find more of those without checking all auto-* trackers. -- WBR, wRAR signature.asc Description: PGP signature
Bug#1067919: Update Build-Depends for the time64 library renames
Source: calindori Version: 24.02.0-1 Severity: serious Tags: ftbfs The package explicitly Build-Depends: libqt5*, these need to be changed to libqt5*t64 (where applicable) if these deps are needed at all. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1067918: FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 6 has type ‘time_t’ {aka ‘long long int’}
Source: mmsd-tng
Version: 2.6.0-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=mmsd-
tng=armhf=2.6.0-2=1711644612=0
In file included from ../src/mms.h:27,
from ../src/service.c:58:
../src/service.c: In function ‘time_to_str’:
../src/log.h:24:47: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 6 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
24 | g_log (G_LOG_DOMAIN, G_LOG_LEVEL_DEBUG, "%s:%s() " fmt, \
| ^~
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#1067917: nmu: openssh_1:9.7p1-2+b1
Package: release.debian.org Severity: normal X-Debbugs-Cc: open...@packages.debian.org Control: affects -1 + src:openssh User: release.debian@packages.debian.org Usertags: binnmu nmu openssh_1:9.7p1-2+b1 . armel armhf . unstable . -m "Rebuild for time_t" https://packages.debian.org/sid/ssh-askpass-gnome
Bug#1067916: FTBFS: tests failed
Source: capnproto Version: 1.0.1-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=capnproto=armhf=1.0.1-3%2Bb2=1711652087=0 [ TEST ] kj/mutex-test.c++:262: legacy test: Mutex/WhenWithTimeout kj/mutex-test.c++:321: failed: expected t >= 10 * kj::MILLISECONDS [20.039μs >= 10ms]; t = 20.039μs stack: 74ee05 74b4a9 f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f f76797d9 f767987d kj/mutex-test.c++:329: failed: expected t >= 20 * kj::MILLISECONDS [92.405μs >= 20ms]; t = 92.405μs stack: 74ee05 74b525 f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f f76797d9 f767987d kj/mutex-test.c++:373: failed: expected clock.now() - start >= 10 * kj::MILLISECONDS [12.208μs >= 10ms] stack: 74eacb 74b5b9 f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f f76797d9 f767987d [ FAIL ] kj/mutex-test.c++:262: legacy test: Mutex/WhenWithTimeout (47479 μs) [ TEST ] kj/mutex-test.c++:391: legacy test: Mutex/WhenWithTimeoutPreciseTiming kj/mutex-test.c++:412: failed: expected t >= 100 * kj::MILLISECONDS [11.64μs >= 100ms] stack: 74a51d f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f f76797d9 f767987d [ FAIL ] kj/mutex-test.c++:391: legacy test: Mutex/WhenWithTimeoutPreciseTiming (40 μs) [ TEST ] kj/mutex-test.c++:422: legacy test: Mutex/WhenWithTimeoutPreciseTimingAfterInterrupt kj/mutex-test.c++:446: failed: expected t >= 100 * kj::MILLISECONDS [12.647μs >= 100ms]; t / kj::MILLISECONDS = 0 stack: 74eca3 74a27f f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f f76797d9 f767987d [ FAIL ] kj/mutex-test.c++:422: legacy test: Mutex/WhenWithTimeoutPreciseTimingAfterInterrupt (10139 μs) -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1067914: Update Build-Depends for the time64 library renames
Source: collatinus Version: 12.2-1 Severity: serious The package explicitly Build-Depends: libqt5printsupport5, this needs to be changed to libqt5printsupport5t64 if it's needed at all. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1067915: Update Build-Depends for the time64 library renames
Source: veusz Version: 3.6.2-1 Severity: serious The package explicitly Build-Depends: libqt5*, these need to be changed to libqt5*t64 (where applicable) if these deps are needed at all. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1067902: elpa-debian-el: regression regarding apt-sources-mode and still warnings (comp)
Hi Jörg-Volker, Jörg-Volker Peetz writes: > Package: elpa-debian-el > Version: 37.11 > Severity: normal > > Dear Debian Emacsen team, > > thanks for taking care. > Unfortunately, there is a regression when detecting > apt-sources-mode. Previously, loading the file /etc/apt/sources.list > activated the apt-sources-mode. Now it doesn't. This seems to be a regression caused by https://salsa.debian.org/emacsen-team/debian-el/-/commit/67dbe593b650b7748e8cbe93fdb8f0cf883563ad. I'll test a fix soon. Meanwhile, you can temporarily add "(require 'debian-el)" or "(use-package debian-el)" in your init.el as a workaround > And there are still comp warnings when using debian-bug: > > Warning (comp): debian-bug.el:858:29: Warning: reference to free variable > ‘term-exec-hook’ > Warning (comp): debian-bug.el:931:16: Warning: ‘message’ called with 1 args > to fill 0 format field(s) > Warning (comp): debian-bug.el:861:10: Warning: the function ‘term-exec’ > might > not be defined at runtime. Will also take a look. BTW, please feel free to file one bug per issue which helps us tracking those issues. Thanks for your reports! > > Regards, > Jörg. > > -- System Information: > Debian Release: trixie/sid > APT prefers testing > APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.8.2 (SMP w/8 CPU threads) > Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set > Shell: /bin/sh linked to /usr/bin/dash > Init: sysvinit (via /sbin/init) > > Versions of packages elpa-debian-el depends on: > ii bzip2 1.0.8-5.1 > ii dh-elpa-helper 2.0.17 > ii emacsen-common 3.0.5 > ii reportbug 13.0.1 > ii xz-utils5.6.1-1 > > Versions of packages elpa-debian-el recommends: > ii emacs1:29.3+1-1 > ii emacs-lucid [emacs] 1:29.3+1-1 > pn wget > > elpa-debian-el suggests no packages. > > -- no debconf information > -- Xiyue Deng
Bug#1066203: recode: FTBFS: error.c:197:43: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration]
Ok, the problem was that CFLAGS now contains -Werror=implicit-function-declaration by default, set by dpkg-buildflags in unstable. The minimal fix is to drop such option, by adding this line to debian/rules: export DEB_CFLAGS_MAINT_STRIP = -Werror=implicit-function-declaration I'm Cc:ing Andrey Rakhmatullin, who was kind enough to look at this and try to diagnose it. Thanks.
Bug#1067913: FTBFS: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’}
Source: linssid
Version: 3.6-8
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=linssid=armhf=3.6-8%2Bb2=1711139760=0
MainForm.cpp: In member function ‘void MainForm::doLogData()’:
MainForm.cpp:1296:68: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka
‘const long long int*’}
1296 | std::strftime(nowStr, 100, "%Y/%m/%d.%H:%M:%S",
std::localtime(::now));
|
^~
||
|long
int*
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#1067912: Update Build-Depends for the time64 library renames
Source: nitrokey-app Version: 1.4.2-1 Severity: serious The package explicitly Build-Depends: libqt5concurrent5, this needs to be changed to libqt5concurrent5t64 if it's needed at all. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1067911: FTBFS: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror]
Source: zeroc-ice Version: 3.7.10-2.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=zeroc- ice=armhf=3.7.10-2.1=1711639887=0 arm-linux-gnueabihf-g++ -g -O2 -ffile-prefix-map=/<>=. -fstack- protector-strong -fstack-clash-protection -Wformat -Werror=format-security -MT modules/IcePy/build/arm-linux-gnueabihf/shared/pic/Grammar.o -MMD -MP -MF modules/IcePy/build/arm-linux-gnueabihf/shared/pic/Grammar.Td -Wall -Wextra -Wshadow -Wdeprecated -Werror -pthread -DNDEBUG -Imodules/IcePy -I../cpp/include -I../cpp/include/generated -I../cpp/src -I/usr/include/python3.11 -I/usr/include/python3.11 -Wsign-compare -g -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash- protection -Wformat -Werror=format-security -DNDEBUG -g -fwrapv -O2 -Wall -Wno- missing-field-initializers -Wno-psabi -fPIC -fvisibility=hidden -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -c ../cpp/src/Slice/Grammar.cpp -o modules/IcePy/build/arm- linux-gnueabihf/shared/pic/Grammar.o cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror] cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror] cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror] cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror] -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1067130: modernizr: NMU or update to latest upstream 3.12 or 3.13
Le jeudi 28 mars 2024, 18:36:54 UTC Fab Stz a écrit : > To build modernizr an additional source file is required (file.js) this file > is added to missing-sources (it comes from the npm package of the same name > from npm server or from upstreams repo). It is required by the build script > from upstream. > > The patch is only here to use that file. That way there is no need to create > a Debian package for it (packaging npm nodes is beyond my knowledge and I'm > not really interested in doing that). > > Concerning your other question, I don't understand it. The binary packages > only ships the js & min.js, not the build script. The missing sources is > required only by the build script iirc. Thanks, this should be documented in: - the comment at the begiging of missing-source/file - the header of patch see https://dep-team.pages.debian.net/deps/dep3/ > > > Le 28 mars 2024 19:23:08 GMT+01:00, "Bastien Roucariès" a > écrit : > >Le jeudi 28 mars 2024, 18:16:09 UTC Fab Stz a écrit : > >> Hello Bastien, > >> > >> Iirc not so many packages depend on it and none seems to use the files > >> that are not shipped anymore in the binary package (the individual > >> 'rules'). > >> > >> Concerning the build maybe you could look at d/rules on the merge request. > >> It uses upstream's build script that builds the complete js. > > > >I do not understand: > >- please document the patch using dep format > >- explain how the build script do not ship in /usr/share > >debian/missingsources > > > >bastien > >> > >> Regards > >> Fab > >> > >> Le 28 mars 2024 18:54:27 GMT+01:00, "Bastien Roucariès" > >> a écrit : > >> >Le jeudi 28 mars 2024, 17:21:48 UTC Fab Stz a écrit : > >> >> Dear Maintainers, > >> >> > >> >> I'm thinking of doing an NMU for the package by updating it to > >> >> 3.13.0-0.1. The > >> >> MR is now open since July 2023 and this bug referencing it has been > >> >> existing > >> >> for about 10 days (in case the MR wouldn't have been noticed). > >> >> > >> >> There is also bug > >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001203 > >> >> which request a newer version since 2021. > >> >> > >> >> BTW, I would require a sponsor to upload the NMU. > >> >> > >> >> Do you have advice or comment on this?* > >> > > >> >What is the state of reverse depends ? > >> > > >> >How does it build ? > >> > > >> >Bastien > >> >> > >> >> Regards > >> >> Fab > >> >> > >> >> On Tue, 19 Mar 2024 08:58:23 +0100 Fab Stz wrote: > >> >> > Source: modernizr > >> >> > Version: update > >> >> > Severity: wishlist > >> >> > Tags: patch > >> >> > > >> >> > Dear Maintainer, > >> >> > > >> >> > Please update to latest upstream version 3.12 or 3.13 > >> >> > > >> >> > For 3.12 I created a merge request on the VCS at > >> >> > > >> >> > https://salsa.debian.org/js-team/modernizr/-/merge_requests/2 > >> >> > > >> >> > There is also one for 2.* in > >> >> > > >> >> > https://salsa.debian.org/js-team/modernizr/-/merge_requests/1 > >> >> > > >> >> > You just have to choose which you prefer or both one after the other. > >> >> > > >> >> > > >> >> > > >> >> > -- System Information: > >> >> > Debian Release: 12.5 > >> >> > APT prefers stable-updates > >> >> > APT policy: (991, 'stable-updates'), (991, 'stable-security'), > >> >> > (991, > >> >> > 'stable'), (990, 'proposed-updates'), (390, 'oldstable-security'), > >> >> > (390, > >> >> > 'oldstable'), (389, 'oldstable-updates'), (380, 'oldoldstable'), > >> >> > (379, > >> >> > 'oldoldstable-updates'), (370, 'oldoldstable'), (95, 'testing'), (94, > >> >> > 'unstable'), (93, 'experimental') > >> >> > Architecture: amd64 (x86_64) > >> >> > Foreign Architectures: i386 > >> >> > > >> >> > Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) > >> >> > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, > >> >> > TAINT_UNSIGNED_MODULE > >> >> > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), > >> >> > LANGUAGE=fr:en_US > >> >> > Shell: /bin/sh linked to /usr/bin/dash > >> >> > Init: systemd (via /run/systemd/system) > >> >> > LSM: AppArmor: enabled > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> =<3776087.mvXUDI8C0e.ref@debian> > >> >> <3776087.mvXUDI8C0e@debian> > >> >> > >> >> > >> >> > >> > > >> > > > signature.asc Description: This is a digitally signed message part.
Bug#1067910: Update Build-Depends for the time64 library renames
Source: ifcplusplus Version: 0~git20190402.13744d5+dfsg-3 Severity: serious The package explicitly Build-Depends: libqt5widgets5, this needs to be changed to libqt5widgets5t64 if it's needed at all. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1067130: modernizr: NMU or update to latest upstream 3.12 or 3.13
To build modernizr an additional source file is required (file.js) this file is added to missing-sources (it comes from the npm package of the same name from npm server or from upstreams repo). It is required by the build script from upstream. The patch is only here to use that file. That way there is no need to create a Debian package for it (packaging npm nodes is beyond my knowledge and I'm not really interested in doing that). Concerning your other question, I don't understand it. The binary packages only ships the js & min.js, not the build script. The missing sources is required only by the build script iirc. Le 28 mars 2024 19:23:08 GMT+01:00, "Bastien Roucariès" a écrit : >Le jeudi 28 mars 2024, 18:16:09 UTC Fab Stz a écrit : >> Hello Bastien, >> >> Iirc not so many packages depend on it and none seems to use the files that >> are not shipped anymore in the binary package (the individual 'rules'). >> >> Concerning the build maybe you could look at d/rules on the merge request. >> It uses upstream's build script that builds the complete js. > >I do not understand: >- please document the patch using dep format >- explain how the build script do not ship in /usr/share debian/missingsources > >bastien >> >> Regards >> Fab >> >> Le 28 mars 2024 18:54:27 GMT+01:00, "Bastien Roucariès" a >> écrit : >> >Le jeudi 28 mars 2024, 17:21:48 UTC Fab Stz a écrit : >> >> Dear Maintainers, >> >> >> >> I'm thinking of doing an NMU for the package by updating it to >> >> 3.13.0-0.1. The >> >> MR is now open since July 2023 and this bug referencing it has been >> >> existing >> >> for about 10 days (in case the MR wouldn't have been noticed). >> >> >> >> There is also bug >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001203 >> >> which request a newer version since 2021. >> >> >> >> BTW, I would require a sponsor to upload the NMU. >> >> >> >> Do you have advice or comment on this?* >> > >> >What is the state of reverse depends ? >> > >> >How does it build ? >> > >> >Bastien >> >> >> >> Regards >> >> Fab >> >> >> >> On Tue, 19 Mar 2024 08:58:23 +0100 Fab Stz wrote: >> >> > Source: modernizr >> >> > Version: update >> >> > Severity: wishlist >> >> > Tags: patch >> >> > >> >> > Dear Maintainer, >> >> > >> >> > Please update to latest upstream version 3.12 or 3.13 >> >> > >> >> > For 3.12 I created a merge request on the VCS at >> >> > >> >> > https://salsa.debian.org/js-team/modernizr/-/merge_requests/2 >> >> > >> >> > There is also one for 2.* in >> >> > >> >> > https://salsa.debian.org/js-team/modernizr/-/merge_requests/1 >> >> > >> >> > You just have to choose which you prefer or both one after the other. >> >> > >> >> > >> >> > >> >> > -- System Information: >> >> > Debian Release: 12.5 >> >> > APT prefers stable-updates >> >> > APT policy: (991, 'stable-updates'), (991, 'stable-security'), (991, >> >> > 'stable'), (990, 'proposed-updates'), (390, 'oldstable-security'), >> >> > (390, >> >> > 'oldstable'), (389, 'oldstable-updates'), (380, 'oldoldstable'), (379, >> >> > 'oldoldstable-updates'), (370, 'oldoldstable'), (95, 'testing'), (94, >> >> > 'unstable'), (93, 'experimental') >> >> > Architecture: amd64 (x86_64) >> >> > Foreign Architectures: i386 >> >> > >> >> > Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) >> >> > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE >> >> > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), >> >> > LANGUAGE=fr:en_US >> >> > Shell: /bin/sh linked to /usr/bin/dash >> >> > Init: systemd (via /run/systemd/system) >> >> > LSM: AppArmor: enabled >> >> > >> >> > >> >> > >> >> > >> >> > >> >> =<3776087.mvXUDI8C0e.ref@debian> >> >> <3776087.mvXUDI8C0e@debian> >> >> >> >> >> >> >> > >> >
Bug#1067909: libc-devtools: please relax Depends on libgd3
Package: libc-devtools Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libgd3 pulls an excessive amount of dependencies, including fonts. It would thus be desirable to downgrade it to a mere Recommends. Martin-Éric - -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages libc-devtools depends on: ii libc6 2.37-15.1 pn libgd3 Versions of packages libc-devtools recommends: ii manpages 6.05.01-1 ii manpages-dev 6.05.01-1 libc-devtools suggests no packages. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmYFuH0ACgkQrh+Cd8S0 17ayNw/+KowbskIoaRqYApa3kOPNWPtLD/rvbEOISdjvJKBz9chs7cYImdtQdd7h 9Z+R6U9AGnxrOTUXxO2a1lfGtpgxVFMemiHIN361zV3kA7IdqX62e1kvAT2dympy Gselwg1Jr5PULghzDAdBcYlZ82S7roYnbh7lhd0vcS90xjCatL4Hk7+/bwCgISvB 2wgICAeXV5YrYxx4pX8FfeLUfGbsCRxzW0sKnG61a+RxGRykP5p+hiccSG2IACyL Wks1Jymf5jLO3Qk3hzYykN3iCikx/dM6wMscDXp36olD+kliD+0I6YDAFHXFIcrb FeL97pqFvNhoz8Q81IbML2BfZfMAEoAlSp5ROqqxyGuqo9BYzc9tDUkwaacPEJCY 9R2sAB1SHgwObOITueTRynfm1kIbemwi/ydiOBT7jjnYNTV3I52DdAdRaqqhSeUM hbCxk960xqF/v2IcMjc92wNepwI8dj4FGmQPgGwJ3JYuVa4y5IncFhf3N93KK00V bduJya6sT/2vR0PtsLnXnAQzh71SyEnqPGGvgQ8031JJ5zivqHZuLx0Huf/ZcjWY CMBmTI2WRByOwqGgA3kpSh5fc7gozb2to/XHTuS7vWFS03KNwZTe+oacHJaVEYTW rL04tKeCZD5t4e4rvrjKABFgheH/Q+TQPS0VfA2NrSYk76qfIeY= =mkEr -END PGP SIGNATURE-
Bug#1067850: src:kget: possible Salsa-CI reprotest misconfiguration.
On 2024-03-27, James Addison wrote: > I'd recommend removing the SALSA_CI_REPROTEST_ARGS line entirely -- which > in isolation could cause Salsa-CI reprotest to fail, due to a build-path > bug reported in #1003914 -- but also then applying the patch from that > bugreport to confirm and solve the problem. > > If that is undesirable, then as an alternative I could suggest configuring: > > SALSA_CI_REPROTEST_ARGS: '--variations=all,-build_path' I would recommend following the recently updated documentation: https://salsa.debian.org/salsa-ci-team/pipeline/#adding-extra-arguments-to-reprotest In short, switching to: SALSA_CI_REPROTEST_ARGS: '--vary=-build_path' I think this behaves more like people would expect, e.g. disabling build path variations and not anything else. live well, vagrant signature.asc Description: PGP signature
Bug#1067098: mpl-sphinx-theme: please make the build reproducible
On 2024-03-27, Andreas Tille wrote: > sorry about your work was lost. I confirm the new upstream > version in Git contains the patch. Unfortunately it needs > new dependencies. If it might help you I could upload your > NMU again. Not urgent, glad to see it is pending again! live well, vagrant signature.asc Description: PGP signature
Bug#1067130: modernizr: NMU or update to latest upstream 3.12 or 3.13
Le jeudi 28 mars 2024, 18:16:09 UTC Fab Stz a écrit : > Hello Bastien, > > Iirc not so many packages depend on it and none seems to use the files that > are not shipped anymore in the binary package (the individual 'rules'). > > Concerning the build maybe you could look at d/rules on the merge request. It > uses upstream's build script that builds the complete js. I do not understand: - please document the patch using dep format - explain how the build script do not ship in /usr/share debian/missingsources bastien > > Regards > Fab > > Le 28 mars 2024 18:54:27 GMT+01:00, "Bastien Roucariès" a > écrit : > >Le jeudi 28 mars 2024, 17:21:48 UTC Fab Stz a écrit : > >> Dear Maintainers, > >> > >> I'm thinking of doing an NMU for the package by updating it to 3.13.0-0.1. > >> The > >> MR is now open since July 2023 and this bug referencing it has been > >> existing > >> for about 10 days (in case the MR wouldn't have been noticed). > >> > >> There is also bug > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001203 > >> which request a newer version since 2021. > >> > >> BTW, I would require a sponsor to upload the NMU. > >> > >> Do you have advice or comment on this?* > > > >What is the state of reverse depends ? > > > >How does it build ? > > > >Bastien > >> > >> Regards > >> Fab > >> > >> On Tue, 19 Mar 2024 08:58:23 +0100 Fab Stz wrote: > >> > Source: modernizr > >> > Version: update > >> > Severity: wishlist > >> > Tags: patch > >> > > >> > Dear Maintainer, > >> > > >> > Please update to latest upstream version 3.12 or 3.13 > >> > > >> > For 3.12 I created a merge request on the VCS at > >> > > >> > https://salsa.debian.org/js-team/modernizr/-/merge_requests/2 > >> > > >> > There is also one for 2.* in > >> > > >> > https://salsa.debian.org/js-team/modernizr/-/merge_requests/1 > >> > > >> > You just have to choose which you prefer or both one after the other. > >> > > >> > > >> > > >> > -- System Information: > >> > Debian Release: 12.5 > >> > APT prefers stable-updates > >> > APT policy: (991, 'stable-updates'), (991, 'stable-security'), (991, > >> > 'stable'), (990, 'proposed-updates'), (390, 'oldstable-security'), (390, > >> > 'oldstable'), (389, 'oldstable-updates'), (380, 'oldoldstable'), (379, > >> > 'oldoldstable-updates'), (370, 'oldoldstable'), (95, 'testing'), (94, > >> > 'unstable'), (93, 'experimental') > >> > Architecture: amd64 (x86_64) > >> > Foreign Architectures: i386 > >> > > >> > Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) > >> > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > >> > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), > >> > LANGUAGE=fr:en_US > >> > Shell: /bin/sh linked to /usr/bin/dash > >> > Init: systemd (via /run/systemd/system) > >> > LSM: AppArmor: enabled > >> > > >> > > >> > > >> > > >> > > >> =<3776087.mvXUDI8C0e.ref@debian> > >> <3776087.mvXUDI8C0e@debian> > >> > >> > >> > > > signature.asc Description: This is a digitally signed message part.
Bug#1067130: modernizr: NMU or update to latest upstream 3.12 or 3.13
Hello Bastien, Iirc not so many packages depend on it and none seems to use the files that are not shipped anymore in the binary package (the individual 'rules'). Concerning the build maybe you could look at d/rules on the merge request. It uses upstream's build script that builds the complete js. Regards Fab Le 28 mars 2024 18:54:27 GMT+01:00, "Bastien Roucariès" a écrit : >Le jeudi 28 mars 2024, 17:21:48 UTC Fab Stz a écrit : >> Dear Maintainers, >> >> I'm thinking of doing an NMU for the package by updating it to 3.13.0-0.1. >> The >> MR is now open since July 2023 and this bug referencing it has been existing >> for about 10 days (in case the MR wouldn't have been noticed). >> >> There is also bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001203 >> which request a newer version since 2021. >> >> BTW, I would require a sponsor to upload the NMU. >> >> Do you have advice or comment on this?* > >What is the state of reverse depends ? > >How does it build ? > >Bastien >> >> Regards >> Fab >> >> On Tue, 19 Mar 2024 08:58:23 +0100 Fab Stz wrote: >> > Source: modernizr >> > Version: update >> > Severity: wishlist >> > Tags: patch >> > >> > Dear Maintainer, >> > >> > Please update to latest upstream version 3.12 or 3.13 >> > >> > For 3.12 I created a merge request on the VCS at >> > >> > https://salsa.debian.org/js-team/modernizr/-/merge_requests/2 >> > >> > There is also one for 2.* in >> > >> > https://salsa.debian.org/js-team/modernizr/-/merge_requests/1 >> > >> > You just have to choose which you prefer or both one after the other. >> > >> > >> > >> > -- System Information: >> > Debian Release: 12.5 >> > APT prefers stable-updates >> > APT policy: (991, 'stable-updates'), (991, 'stable-security'), (991, >> > 'stable'), (990, 'proposed-updates'), (390, 'oldstable-security'), (390, >> > 'oldstable'), (389, 'oldstable-updates'), (380, 'oldoldstable'), (379, >> > 'oldoldstable-updates'), (370, 'oldoldstable'), (95, 'testing'), (94, >> > 'unstable'), (93, 'experimental') >> > Architecture: amd64 (x86_64) >> > Foreign Architectures: i386 >> > >> > Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) >> > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE >> > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), >> > LANGUAGE=fr:en_US >> > Shell: /bin/sh linked to /usr/bin/dash >> > Init: systemd (via /run/systemd/system) >> > LSM: AppArmor: enabled >> > >> > >> > >> > >> > >> =<3776087.mvXUDI8C0e.ref@debian> >> <3776087.mvXUDI8C0e@debian> >> >> >> >
Bug#1067529: libonvif: Please package new upstream version
[Stephen Rhodes] > Hope you are having a nice day. I am researching my options for making a > Debian package for a python program, hope to have something soon. Very glad to hear you are on the case. Please ping me on IRC when you are ready to test. :) -- Happy hacking Petter Reinholdtsen
Bug#1067908: Enable I6300ESB_WDT
Package: linux-image-cloud-amd64 Version: 6.1.76-1 Severity: wishlist GCE will introduce a virtual watchdog timer device, implemented to appear as an Intel 6300ESB. The team implementing the device reports that the driver is not available on Debian. It looks like it's been in the kernel for ~19 years, so it should be a matter of setting CONFIG_I6300ESB_WDT=m (and any dependencies). If it's possible to get this into Debian 11 as well, that would be good. Cloud kernels only would be sufficient. arm64 as well.
Bug#1067907: flam3-utils: flam3-genome randomly segfaults on ppc64el
Package: flam3-utils Version: 3.1.1+ds2-2+b1 Severity: normal X-Debbugs-Cc: pe...@pblackman.plus.com User: debian-powe...@lists.debian.org Usertags: ppc64el Dear Maintainer, flam3-genome randomly segfaults on ppc64el, but runs OK on all other architectures. See https://ci.debian.net/packages/f/flam3/testing/ppc64el/ segfaults maybe one run in five. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001667
Bug#1067906: qtwebengine-opensource-src - FTBFS on armhf.
Package: qtwebengine-opensource-src Version: 5.15.15+dfsg-2 Severity: serious qtwebengine-opensource-src failed to build on armhf when binnmu'd for the time_t transition due to symbol changes. (qtwebengine does not support any of the other architectures affected by the time64 transition. grep MISSING qtwebengine-opensource-src.log | grep -v optional +#MISSING: 5.15.15+dfsg-2+b3# _ZN15QtWebEngineCore14ProfileAdapter21determineDownloadPathERK7QStringS3_RKl@Qt_5 5.14.1 +#MISSING: 5.15.15+dfsg-2+b3# _ZN7sandbox18localtime_overrideEPKl@Qt_5 5.12.2 +#MISSING: 5.15.15+dfsg-2+b3# _ZN7sandbox20localtime64_overrideEPKl@Qt_5 5.12.2 +#MISSING: 5.15.15+dfsg-2+b3# _ZN7sandbox20localtime_r_overrideEPKlP2tm@Qt_5 5.12.2 +#MISSING: 5.15.15+dfsg-2+b3# _ZN7sandbox22localtime64_r_overrideEPKlP2tm@Qt_5 5.12.2
Bug#1067130: modernizr: NMU or update to latest upstream 3.12 or 3.13
Le jeudi 28 mars 2024, 17:21:48 UTC Fab Stz a écrit : > Dear Maintainers, > > I'm thinking of doing an NMU for the package by updating it to 3.13.0-0.1. > The > MR is now open since July 2023 and this bug referencing it has been existing > for about 10 days (in case the MR wouldn't have been noticed). > > There is also bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001203 > which request a newer version since 2021. > > BTW, I would require a sponsor to upload the NMU. > > Do you have advice or comment on this?* What is the state of reverse depends ? How does it build ? Bastien > > Regards > Fab > > On Tue, 19 Mar 2024 08:58:23 +0100 Fab Stz wrote: > > Source: modernizr > > Version: update > > Severity: wishlist > > Tags: patch > > > > Dear Maintainer, > > > > Please update to latest upstream version 3.12 or 3.13 > > > > For 3.12 I created a merge request on the VCS at > > > > https://salsa.debian.org/js-team/modernizr/-/merge_requests/2 > > > > There is also one for 2.* in > > > > https://salsa.debian.org/js-team/modernizr/-/merge_requests/1 > > > > You just have to choose which you prefer or both one after the other. > > > > > > > > -- System Information: > > Debian Release: 12.5 > > APT prefers stable-updates > > APT policy: (991, 'stable-updates'), (991, 'stable-security'), (991, > > 'stable'), (990, 'proposed-updates'), (390, 'oldstable-security'), (390, > > 'oldstable'), (389, 'oldstable-updates'), (380, 'oldoldstable'), (379, > > 'oldoldstable-updates'), (370, 'oldoldstable'), (95, 'testing'), (94, > > 'unstable'), (93, 'experimental') > > Architecture: amd64 (x86_64) > > Foreign Architectures: i386 > > > > Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) > > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), > > LANGUAGE=fr:en_US > > Shell: /bin/sh linked to /usr/bin/dash > > Init: systemd (via /run/systemd/system) > > LSM: AppArmor: enabled > > > > > > > > > > > =<3776087.mvXUDI8C0e.ref@debian> > <3776087.mvXUDI8C0e@debian> > > > signature.asc Description: This is a digitally signed message part.
Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-1~deb12u1
On 27/03/2024 21.10, Adam D. Barratt wrote: Please go ahead, bearing in mind that the window for 12.6 closes over the coming weekend. The whole nvidia stack has now been uploaded, src:nvidia-graphics-drivers is sitting in NEW. Andreas
Bug#1067564: cpu 1.4.3-14~deb12u1 flagged for acceptance
package release.debian.org tags 1067564 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: cpu Version: 1.4.3-14~deb12u1 Explanation: provide exactly one definition of globalLdap in ldap plugin
Bug#1067888: libesmtp 1.1.0-3.1~deb12u1 flagged for acceptance
package release.debian.org tags 1067888 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: libesmtp Version: 1.1.0-3.1~deb12u1 Explanation: break and replace older library versions
Bug#1067149: hovercraft 2.7-6~deb12u1 flagged for acceptance
package release.debian.org tags 1067149 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: hovercraft Version: 2.7-6~deb12u1 Explanation: depend on python3-setuptools
Bug#1065060: php-proxy-manager 2.11.1+1.0.14-1+deb12u1 flagged for acceptance
package release.debian.org tags 1065060 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: php-proxy-manager Version: 2.11.1+1.0.14-1+deb12u1 Explanation: force system dependency loading
Bug#1065263: php-phpseclib 2.0.42-1+deb12u2 flagged for acceptance
package release.debian.org tags 1065263 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: php-phpseclib Version: 2.0.42-1+deb12u2 Explanation: guard isPrime() and randomPrime() for BigInteger [CVE-2024-27354]; limit OID length in ASN1 [CVE-2024-27355]; fix BigInteger getLength(); remove visibitility modifiers from static variables
Bug#1065261: php-phpseclib3 3.0.19-1+deb12u3 flagged for acceptance
package release.debian.org tags 1065261 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: php-phpseclib3 Version: 3.0.19-1+deb12u3 Explanation: force system dependency loading; guard isPrime() and randomPrime() for BigInteger [CVE-2024-27354]; limit OID length in ASN1 [CVE-2024-27355]; fix BigInteger getLength()
Bug#1065068: php-doctrine-deprecations 1.0.0-2+deb12u1 flagged for acceptance
package release.debian.org tags 1065068 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: php-doctrine-deprecations Version: 1.0.0-2+deb12u1 Explanation: force system dependency loading
Bug#1065067: php-doctrine-lexer 2.1.0-2+deb12u1 flagged for acceptance
package release.debian.org tags 1065067 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: php-doctrine-lexer Version: 2.1.0-2+deb12u1 Explanation: force system dependency loading
Bug#1065065: php-doctrine-annotations 2.0.1-1+deb12u1 flagged for acceptance
package release.debian.org tags 1065065 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: php-doctrine-annotations Version: 2.0.1-1+deb12u1 Explanation: force system dependency loading
Bug#1065062: php-zend-code 4.8.0-1+deb12u1 flagged for acceptance
package release.debian.org tags 1065062 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: php-zend-code Version: 4.8.0-1+deb12u1 Explanation: force system dependency loading
Bug#1065059: symfony 5.4.23+dfsg-1+deb12u2 flagged for acceptance
package release.debian.org tags 1065059 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: symfony Version: 5.4.23+dfsg-1+deb12u2 Explanation: force system dependency loading; DateTypTest: ensure submitted year is accepted choice
Bug#1051496: mailgraph: does not support the new syslog format
severity 1051496 normal tags 1051496 + moreinfo Hello Michael, thank you for spending your time helping to make Debian better with this bug report. We are using mailgraph one multiple server with Debian Bullseye, Bookworm and Trixie without any failure. Therefore I set the severity to normal. Please can you provide more details about your error? A depersonalized excerpt of the log files and the installed dependencies are important. CU Jörg Am Montag, dem 25.03.2024 um 16:32 -0700 schrieb mich...@oneilonline.com: > Debian 12 Bookworm > Package: mailgraph > Version: 1.14-21 > Severity: grave > Justification: renders package unusable > > I installed mailgraph from Debian Trixie testing hoping to get the fixes > mentioned in: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051496 > > However, it still fails to run correctly. > > mailgraph -v shows: > WARNING: line not in syslog format: > For every log entry. > > And graphs don’t create. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051496 > Says it was resolved, but this is not correct. > > I compared/contrasted the 1.14-20 vs 1.14-21 line by line and I only saw: > $text =~ /^(?:[\dA-F]+|[\dB-DF-HJ-NP-TV-Zb-df-hj-np-tv-z]+): > Changing to: > $text =~ /^[0-9A-Z]+: > In a number of places. > > Any insight would be appreciated. > > Thank you > > Michael -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#1065058: php-symfony-contracts 2.5.2-1+deb12u1 flagged for acceptance
package release.debian.org tags 1065058 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: php-symfony-contracts Version: 2.5.2-1+deb12u1 Explanation: force system dependency loading
Bug#1065057: php-composer-xdebug-handler 3.0.3-2+deb12u1 flagged for acceptance
package release.debian.org tags 1065057 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: php-composer-xdebug-handler Version: 3.0.3-2+deb12u1 Explanation: force system dependency loading
Bug#1065056: php-composer-class-map-generator 1.0.0-2+deb12u1 flagged for acceptance
package release.debian.org tags 1065056 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: php-composer-class-map-generator Version: 1.0.0-2+deb12u1 Explanation: force system dependency loading
Bug#1067093: Impacket Patches for PR 1714 and 1715
Arslan M. CRTO, GWAPT, OSCP Hi again, #1721 has been merged. Can the impacket package be updated to the latest state of the repository to allow the Kali Team and me to package NetExec? Thanks! On Friday, March 22nd, 2024 at 10:42, Arszilla wrote: > A small status update: > - https://github.com/fortra/impacket/pull/1714 has been merged, thus any > patch related to this is now redundant. > - https://github.com/fortra/impacket/pull/1715 has been redirected to > https://github.com/fortra/impacket/pull/1721 which is pending approval. > > As a result, once #1721 is merged, I'll be updating this ticket again to ask > you to update the impacket's package instead of applying patches. > > Kind regards.
Bug#1067844: c-evo-dh: Depends on dead-upstream mpg321 instead of mpg123
On 2024-03-28 Peter B wrote: > On 27/03/2024 14:57, Andreas Metzler wrote: >> mpg321 is dead upstream > I don't see that as a show stopper. >> Please consider moving to another player, e.g. mpg123. > I moved away from ffmpeg after c-evo-dh showed a puiparts fail > stemming from libnettle8. c-evo-dh does not use any crypto stuff, > that library was brought in by ffmpeg. > I picked mpg321 over mpg123 because it it has fewer dependencies. Hello Peter, > Also, mpg123 is broken > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067562 it works perfectly fine in trixie and both maintainers and upstream are actively working together to resolve the issue in sid. > mpg321 uses fixed point arithmetic, and is likely to be a better > choice on low spec architectures with no floating point (armel). > I would prefer to keep mpg321 as the sound option for c-evo-dh > Noting the user-tag mpg321-removal on your bug report, > I could instead maintain mpg321 myself if it were orphaned... I recently had a look at mpg321 because it had a FTBFS bug, I hotfixed this by NMU and looking at the package got the distinct impression of having stumbled over a package that we would better be off without in trixie. There are loads of old bugs including rather severe ones at first glance. The fact that the packaging is very dated is not the real problem (Updating to dh could probably be done in in an , since it os basically a single binary package.) There is just a lot of technical debt due to missing upstream, it does not need maintainership but a new upstream author. On my local system there simply is no sound output, I suspect it cannot work when pipewire or pulseaudio is used. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1064765: prometheus: FTBFS: dh_auto_test error
On 28.03.24 15:00, Santiago Vila wrote: Daniel Swarbrick wrote: * Add new 0022-Support-prometheus-common-0.47.0.patch (Closes: #1064765) Hello. I don't quite understand how the above fix is related to the bug itself (but maybe it's because I don't know prometheus internals). As described in the patch: This cherry-picks part of a commit relating to negotiation of the "Accept" header, which became more complex with prometheus/common 0.47.0. See upstream commit a28d786. This resolved the original FTBFS for which this bug was opened, as far as I could see, which was this test failure: > === RUN TestFederationWithNativeHistograms > federate_test.go:417: > Error Trace: /<>/.build/src/github.com/prometheus/prometheus/web/federate_test.go:417 >Error: Not equal: >expected: 4 >actual : 1 >Test: TestFederationWithNativeHistograms > --- FAIL: TestFederationWithNativeHistograms (0.01s) I was able to reliably reproduce that failure by rolling forward / back the prometheus/common dependency in go.mod on a local git clone. In either case, this is still happening for me in the current version: Lucas Nussbaum wrote: FAILED: 1:48: parse error: unexpected character inside braces: '0' This sounds like a _new_ bug. Note: I'm currently using virtual machines with 1 CPU and with 2 CPUs for archive rebuilds. On systems with 2 CPUs, the package FTBFS randomly. On systems with 1 CPU, the package FTBFS always. Therefore, to reproduce, please try GRUB_CMDLINE_LINUX="nr_cpus=1" in /etc/default/grub first. I'm struggling to see how a different number of CPU cores would elicit the aforementioned new bug. It doesn't seem to have the typical characteristics of a race condition. I'll have to try to find some time to setup a VM and try to reproduce it. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1067130: modernizr: NMU or update to latest upstream 3.12 or 3.13
Dear Maintainers, I'm thinking of doing an NMU for the package by updating it to 3.13.0-0.1. The MR is now open since July 2023 and this bug referencing it has been existing for about 10 days (in case the MR wouldn't have been noticed). There is also bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001203 which request a newer version since 2021. BTW, I would require a sponsor to upload the NMU. Do you have advice or comment on this? Regards Fab On Tue, 19 Mar 2024 08:58:23 +0100 Fab Stz wrote: > Source: modernizr > Version: update > Severity: wishlist > Tags: patch > > Dear Maintainer, > > Please update to latest upstream version 3.12 or 3.13 > > For 3.12 I created a merge request on the VCS at > > https://salsa.debian.org/js-team/modernizr/-/merge_requests/2 > > There is also one for 2.* in > > https://salsa.debian.org/js-team/modernizr/-/merge_requests/1 > > You just have to choose which you prefer or both one after the other. > > > > -- System Information: > Debian Release: 12.5 > APT prefers stable-updates > APT policy: (991, 'stable-updates'), (991, 'stable-security'), (991, > 'stable'), (990, 'proposed-updates'), (390, 'oldstable-security'), (390, > 'oldstable'), (389, 'oldstable-updates'), (380, 'oldoldstable'), (379, > 'oldoldstable-updates'), (370, 'oldoldstable'), (95, 'testing'), (94, > 'unstable'), (93, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), > LANGUAGE=fr:en_US > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > > > > =<3776087.mvXUDI8C0e.ref@debian> <3776087.mvXUDI8C0e@debian>
Bug#847983: apt: Sid Apt-Pinning ignoring other Release than Experimental
On Tue, Dec 13, 2016 at 08:43:35AM +, Adam D. Barratt wrote: > On 2016-12-12 20:25, Perl wrote: > >* What led up to the situation? > >I noticed, since long time ago, that I was not anymore able to use > >Apt-Pinning for installing packages from Stable and Testing Releases. > >* What exactly did you do (or not do) that was effective (or > > ineffective)? > > Everytime I try to use "APT-Pinning", I do not get what I want. > > Even if I try /testing or -t testing, or any Release other than > > Experimental, I only get error or Experimental list of packages. > > Finally, apt-cache policy only return Sid and Experimental > > packages. > >* What was the outcome of this action? > > If I try > > "apt-cache show -t testing linux-image-amd64" > > OR > > "apt-cache show linux-image-amd64/testing" > > I get this with apt-get: > > E: Release 'testing' for 'linux-image-amd64' was not found > > E: No packages found > > Well, the only testing sources.list entries listed in your report are: > > > #Testing > > deb-src http://ftp.fr.debian.org/debian/ testing main non-free contrib > > deb-src http://ftp2.fr.debian.org/debian/ testing main contrib non-free > > So I'm not sure where you're expecting apt to find information about > *binary* packages in testing from. I agree with this statement and I think we can close this bug because of it. Cheers, Wesley
Bug#1067054: Debian 12 - Copy files on USB 3
After further testing, the crash issue when copying multiple files (total volume 150 GB) or a disk image (250 GB) is present when an SSD is formatted in GPT format. This works without problem if the SSD is formatted in MBR/MS-DOS. Regards.
Bug#1067904: $frontend-$version-for-host: versioned dependency too strict
Source: gcc-14
Severity: wishlist
Tags: patch
User: helm...@debian.org
Usertags rebootstrap
Hi Matthias,
thanks for merging my -for-host work. I'm looking into making practical
use of it and a major issue is the following dependency:
$FRONTEND-$VERSION-for-host:$DEB_HOST_ARCH ->
$FRONTEND-$VERSION-$DEB_HOST_GNU_TYPE (= ${gcc:Version})
While this works nicely for native compilers, trying to use the
-for-host package with a cross toolchain is doomed to fail, because it
always has different version. The equal constraint is too strict to make
practical use of these -for-host packages. I think we should change (=
${gcc:Version}) to (>= ${gcc:SoftVersion}) as is done elsewhere. Do you
agree?
I'm attaching the obvious patch.
Helmut
commit 843e8ae7602a0ec16c67d7064396fa2acd1182cd
Author: Helmut Grohne
Date: Fri Mar 22 09:35:04 2024 +0100
use gcc:SoftVersion for -for-host dependencies
diff --git a/debian/control.m4 b/debian/control.m4
index 4b6c61b8..61a4d3a8 100644
--- a/debian/control.m4
+++ b/debian/control.m4
@@ -804,7 +804,7 @@ Package: gcc`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gcc`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, gcc`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
cpp`'PV`'-for-host (= ${gcc:Version}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU C compiler for the host architecture
@@ -929,7 +929,7 @@ Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
Section: ifdef(`TARGET',`devel',`interpreters')
-Depends: BASEDEP, cpp`'PV`'${target:suffix} (= ${gcc:Version}), ${misc:Depends}
+Depends: BASEDEP, cpp`'PV`'${target:suffix} (>= ${gcc:SoftVersion}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU C preprocessor for the host architecture
A macro processor that is used automatically by the GNU C compiler
@@ -1019,7 +1019,7 @@ Package: g++`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, g++`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, g++`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
gcc`'PV`'-for-host (= ${gcc:Version}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU C++ compiler for the host architecture
@@ -2522,7 +2522,7 @@ Package: gobjc++`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gobjc++`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, gobjc++`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
gobjc`'PV`'-for-host (= ${gcc:Version}), g++`'PV`'-for-host (= ${gcc:Version}),
${misc:Depends}
BUILT_USING`'dnl
@@ -2599,7 +2599,7 @@ Package: gobjc`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gobjc`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, gobjc`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
gobjc`'PV`'-for-host (= ${gcc:Version}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU Objective-C compiler for the host architecture
@@ -2844,7 +2844,7 @@ Package: gfortran`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gfortran`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, gfortran`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
gcc`'PV`'-for-host (= ${gcc:Version}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU Fortran compiler for the host architecture
@@ -3111,7 +3111,7 @@ Package: gccgo`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gccgo`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, gccgo`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
gcc`'PV`'-for-host (= ${gcc:Version}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU Go compiler for the host architecture
@@ -3821,7 +3821,7 @@ Package: gnat`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gnat`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, gnat`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
gcc`'PV`'-for-host (= ${gcc:Version}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU Ada compiler for the host architecture
@@ -3981,7 +3981,7 @@ Package: gdc`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gdc`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, gdc`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
gcc`'PV`'-for-host (= ${gcc:Version}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU D compiler (version 2) for the host architecture
@@ -4268,7 +4268,7 @@ Package: gm2`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gm2`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP,
Bug#1067903: RM: fuse3/experimental -- RoQA; time64 transition reverted
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: fu...@packages.debian.org Control: affects -1 + src:fuse3 Please remove fuse3 version 3.14.0-5.1~exp1 from experimental. It prepares a time64 transition that is not needed and will not propagate to unstable. The package causes /usr-merge issues and should not be installed. Therefore, the best course of action is removing it. Helmut
Bug#1061816: mmdebstrap-autopkgtest-build-qemu VM image cannot be updated with sbuild-qemu-update
Hi josch, On 2024-03-28 11:28, Johannes Schauer Marin Rodrigues wrote: > I think sbuild-qemu-boot and sbuild-qemu-update should do the same as > autopkgtest did here: > > https://salsa.debian.org/ci-team/autopkgtest/-/commit/7a4954ded0f24221ac34ca0aaf10f3f9b083afa2 Thanks for pointing this out! Applied (though stupidly, with two commits.) Though if I understand #1061816 correctly, then this should probably be a separate bug, right? (Wanted to check before I clone) Best, Christian
Bug#1067902: elpa-debian-el: regression regarding apt-sources-mode and still warnings (comp)
Package: elpa-debian-el Version: 37.11 Severity: normal Dear Debian Emacsen team, thanks for taking care. Unfortunately, there is a regression when detecting apt-sources-mode. Previously, loading the file /etc/apt/sources.list activated the apt-sources-mode. Now it doesn't. And there are still comp warnings when using debian-bug: Warning (comp): debian-bug.el:858:29: Warning: reference to free variable ‘term-exec-hook’ Warning (comp): debian-bug.el:931:16: Warning: ‘message’ called with 1 args to fill 0 format field(s) Warning (comp): debian-bug.el:861:10: Warning: the function ‘term-exec’ might not be defined at runtime. Regards, Jörg. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.8.2 (SMP w/8 CPU threads) Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages elpa-debian-el depends on: ii bzip2 1.0.8-5.1 ii dh-elpa-helper 2.0.17 ii emacsen-common 3.0.5 ii reportbug 13.0.1 ii xz-utils5.6.1-1 Versions of packages elpa-debian-el recommends: ii emacs1:29.3+1-1 ii emacs-lucid [emacs] 1:29.3+1-1 pn wget elpa-debian-el suggests no packages. -- no debconf information
Bug#1067901: jh_installjavadoc: should not write duplicative doc-base files.
Package: javahelper Version: 0.79 Severity: normal User: reproducible-bui...@lists.alioth.debian.org Usertags: fileordering Control: affects -1 libpixels-java Dear Maintainer, I'm an occasional volunteer contributor to the Reproducible Builds[1] project, and noticed that the 'libpixels-java' package, which build-depends on javahelper (src:javatools) and uses jh_installjavadoc, failed[2] an automated build test on the Reproducible Builds test infrastructure for Debian. In particular, the /usr/share/doc-base/libpixels-java.libpixels-java file varied between a control and experimental package build. The cause seems to relate to logic that writes[3] a '$package.doc-base.javadoc' file into the 'debian' directory during build. In the case of libpixels-java, that template file is written alongside an existing 'debian/doc-base' file[4] contained in the source package. Both of the files then contain an identical doc-id statement[5], and it's unpredictable which of them will be read[6] from the directory by dh_installdocs - it depends on the ordering returned by the filesystem. If it seems like a reasonable solution to you, perhaps jh_installjavadoc could be modified so that it does not write a templated doc-base file for a package when it detects an existing doc-base file that contains the same doc-id? Thank you, James [1] - https://reproducible-builds.org/ [2] - https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/libpixels-java.html [3] - https://sources.debian.org/src/javatools/0.79/jh_installjavadoc/?hl=86#L105-L118 [4] - https://sources.debian.org/src/libpixels-java/2.1.3%2Bsvn.42-3/debian/doc-base/ [5] - https://sources.debian.org/src/libpixels-java/2.1.3%2Bsvn.42-3/debian/doc-base/#L1 [6] - https://sources.debian.org/src/debhelper/13.14.1/dh_installdocs/#L406
Bug#1064404: snapd: please make the build reproducible.
> Wiadomość napisana przez James Addison w dniu > 28.03.2024, o godz. 15:51: > > On Thu, 28 Mar 2024 at 12:43, Zygmunt Krynicki wrote: >> >> Thank You for pursuing this! Please let me know when you have the patch and >> I will gladly apply it. >> >> Personally I think the simple solution is fine. No need to go overboard. > > Ok, agreed - I'll test and then provide a patch to use a fixed offset for the > timezone. > > Could you confirm your current preferred timezone to derive that value? (the > selection should be fairly arbitrary, but I'd prefer to ask) Perhaps just UTC? ZK
Bug#1067829: 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=]
Control: tags -1 + patch
Hi,
On 2024-03-27 11:02, Sebastian Ramacher wrote:
> export-cache.c: In function ‘junction_flush_exports_cache’:
> 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=]
> 110 | snprintf(flushtime, sizeof(flushtime), "%ld\n", now);
> | ~~^ ~~~
> | | |
> | | time_t {aka
> long long int}
> | long int
> | %lld
The attached patch by Vladimir Petko was sent upstream and fixes the
FTBFS on armhf/armel.
Emanuele
diff -Nru nfs-utils-2.6.4/debian/changelog nfs-utils-2.6.4/debian/changelog
--- nfs-utils-2.6.4/debian/changelog 2023-12-03 14:58:30.0 +0100
+++ nfs-utils-2.6.4/debian/changelog 2024-03-28 16:56:19.0 +0100
@@ -1,3 +1,10 @@
+nfs-utils (1:2.6.4-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Apply upstream patch to fix FTBFS on armhf/armel (Closes: #1067829)
+
+ -- Emanuele Rocca Thu, 28 Mar 2024 16:56:19 +0100
+
nfs-utils (1:2.6.4-3) unstable; urgency=medium
[ Salvatore Bonaccorso ]
diff -Nru nfs-utils-2.6.4/debian/patches/flushtime-long-long-int.patch nfs-utils-2.6.4/debian/patches/flushtime-long-long-int.patch
--- nfs-utils-2.6.4/debian/patches/flushtime-long-long-int.patch 1970-01-01 01:00:00.0 +0100
+++ nfs-utils-2.6.4/debian/patches/flushtime-long-long-int.patch 2024-03-28 16:56:19.0 +0100
@@ -0,0 +1,17 @@
+Author: Vladimir Petko
+Origin: https://bugzilla.kernel.org/show_bug.cgi?id=218540
+Bug-Debian: https://bugs.debian.org/1067829
+
+Index: nfs-utils-2.6.4/support/junction/export-cache.c
+===
+--- nfs-utils-2.6.4.orig/support/junction/export-cache.c
nfs-utils-2.6.4/support/junction/export-cache.c
+@@ -107,7 +107,7 @@ junction_flush_exports_cache(void)
+ xlog(D_GENERAL, "%s: time(3) failed", __func__);
+ return FEDFS_ERR_SVRFAULT;
+ }
+- snprintf(flushtime, sizeof(flushtime), "%ld\n", now);
++ snprintf(flushtime, sizeof(flushtime), "%lld\n", now);
+
+ for (i = 0; junction_proc_files[i] != NULL; i++) {
+ retval = junction_write_time(junction_proc_files[i], flushtime);
diff -Nru nfs-utils-2.6.4/debian/patches/series nfs-utils-2.6.4/debian/patches/series
--- nfs-utils-2.6.4/debian/patches/series 2023-12-03 14:58:30.0 +0100
+++ nfs-utils-2.6.4/debian/patches/series 2024-03-28 16:56:19.0 +0100
@@ -1,3 +1,4 @@
multiarch-kerberos-paths.patch
always-run-generator.patch
fsidd-call-anonymous-sockets-by-their-name-only-don-.patch
+flushtime-long-long-int.patch
Bug#1067771: cdk.h file location has changed, breaks application build
Hello Thomas! Thanks for chiming in on this issue. I had sent a follow-up at about the same time you did with a few details on the history as I could reconstruct it. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067771#18 In summary: I believe you changed the default location from to in 2012, adding a configure option at the same time. When this version was uploaded to Debian (much later), a debian-specific patch was added to retain the original location. Four years ago, the previous debian maintainer removed that patch - but was never uploaded to debian unstable. I took over maintenance a month ago and inadvertently uploaded to unstable a version where the header change from 2012 was exposed for the first time. I can see a valid argument for retaining the Debian practice. But when I discovered that the upstream change was 12 years old, I figured that there are likely other folks long used to the "new" header location and have adapted their code. So there is also a valid argument to adhering to the upstream location and harmonizing the landscape for code using libcdk. I actually did a search on github and discovered examples of all three cases: * code using only * code using only * code that probes both locations and uses the one found I'm wondering whether you have an opinion on the merits of one path versus the other. Do you have any information about how much currently-maintained software is still using ? At present, I'm leaning towards retaining the default location . Thanks, -Steve signature.asc Description: This is a digitally signed message part.
Bug#1067293: singular: FTBFS: cfModGcd.cc:1809:37: error: cannot convert ‘fq_nmod_ctx_struct*’ to ‘const fq_nmod_mat_struct*’
Hello Lucas, thanks for the report. The issue appeared to be fixed in version 4.3.2-p16. I am on my way to bring this new version to experimental. Best wishes, Jerome -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1067900: e2fsprogs: incorrect dependencies on 32-bit archs
Package: e2fsprogs Version: 1.47.0-2.4 Severity: important X-Debbugs-Cc: Helmut Grohne -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The following packages have unmet dependencies: e2fsprogs : PreDepends: libcom-err2 (>= 1.43.9) PreDepends: libss2 (>= 1.38) E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. The cause: Pre-Depends: libblkid1 (>= 2.36), libc6 (>= 2.34), libcom-err2 (>= 1.43.9), libext2fs2t64 (= 1.47.0-2.4), libss2 (>= 1.38), libuuid1 (>= 2.16) Basically, 32-bit builds incorrectly depend on libcom-err2 instead of libcom-err2t64. Martin-Éric - -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages e2fsprogs depends on: ii libblkid1 2.39.3-11 ii libc6 2.37-15.1 ii libcom-err2t64 [libcom-err2] 1.47.0-2.3+b1 ii libext2fs2t64 1.47.0-2.4 ii libss21.47.0-2.4 ii libuuid1 2.39.3-11 ii logsave 1.47.0-2.4 Versions of packages e2fsprogs recommends: ii e2fsprogs-l10n 1.47.0-2.4 Versions of packages e2fsprogs suggests: pn e2fsck-static pn fuse2fs pn gpart pn parted - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmYFkZUACgkQrh+Cd8S0 17bK/BAAjBS9k79q6TuzUgdlHN9D3aITCJntMIXcgGMK887+z9SZvVZGvXLbCO0b OsfItwEVcy3KpJXek731jHH2FGDfsOC+UQ4zTsDtujHHCB5qzJL2l8ZvzTUX0Vih kXQOsQ53BZil32dYOXf/fc8m9FPca9sJkHGLBuw1N2drD7Za320B3T9aLmE0bbg+ TZN+BBDA1q8Pket9a515L6hdam8Kyb0MQdru4QxbNlq5pcpiUEBNO6DCeBS+/42w FMNVqiXHs37dTErWmPJk6lA44MANdYPTcpKWZpHtE85AwlRFk11fxPROFyxQOSVp mtDVThnEwlNKTbXaNjxH8fOMY6MqR78VoRv/rETQ8xh3z1PMJZtwC0Rp9bQ2JDG/ WHrNgQgbUVbTqVD2kZEPTTwRavu43pnv1QFhlBiksHpwbBi7tbBqCtizPYcVX5Hf fQoBZgl2AcZgY8W4+Eto5wjP7p+R3kJr7VtBZ28d5rGdqYq4uSeV6rLJEK5LuUby /mu4UhWgtSvGv0aMsPujpXGhrLfn2xoBOld/G5hsciwZd7vzF4uGlV/w2JZzJ+QR +LcqdW1CJ4/6XetmSv2XL/W5olFhgpq9kZ1pdj8gbFNPBkjySH2T6s2Aj1wjankw EAWAK5Jaguuc3lEwguidioHSh6WPDbjINwE7ESIDH/WvoYV3Ovk= =yREi -END PGP SIGNATURE-
Bug#1067899: O: qt-avif-image-plugin -- Qt plug-in to read/write AVIF images
Package: wnpp Control: affects -1 + src:qt-avif-image-plugin Severity: normal I intend to orphan the qt-avif-image-plugin package. The avif format support is already provided by KDE's kimageformat-plugins, and a standalone qt-avif-image-plugin with conflict files may have little usage. The package description is: Qt plug-in to allow Qt and KDE based applications to read/write AVIF images. . Similar functionality is also provided in package kimageformat-plugins as part of KDE. General users should consider using KDE-provided plugin instead. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1067898: atril, dependencies unsatisfiable on 32-bit non-i386 architectures.
Package: atril Version: 1.26.2-2 Severity: serious The latest version of atril depends on both libatrildocument3 and libatrildocument3t64. As a result it is uninstallable on architectures that are undergoing the time64 transition (armel, armhf and some debian-ports archictures).
Bug#1067897: rust-coreutils - FTBFS with new rust-uutils-term-grid.
Package: rust-coreutils
Version: 0.0.24-2
Severity: serious
rust-coreutils FTBFS with the new version of rust-uutils-term-grid.
The Debian build-dependency allows the new version, but the Cargo
dependency does not.
After bumping the cargo dependency, the code fails to build with a
bunch of errors.
error[E0432]: unresolved import `term_grid::Cell`
--> src/uu/ls/src/ls.rs:37:17
|
37 | use term_grid::{Cell, Direction, Filling, Grid, GridOptions};
| no `Cell` in the root
|
= help: consider importing one of these items instead:
std::cell::Cell
core::cell::Cell
error[E0063]: missing field `width` in initializer of `GridOptions`
--> src/uu/ls/src/ls.rs:2598:34
|
2598 | let mut grid = Grid::new(GridOptions { filling, direction });
| ^^^ missing `width`
error[E0061]: this function takes 2 arguments but 1 argument was supplied
--> src/uu/ls/src/ls.rs:2598:24
|
2598 | let mut grid = Grid::new(GridOptions { filling, direction });
|^ -- an
argument of type `Vec<_>` is missing
error[E0599]: no method named `add` found for struct `Grid` in the current scope
--> src/uu/ls/src/ls.rs:2609:18
|
2609 | grid.add(formatted_name);
| ^^^ method not found in `Grid<_>`
error[E0599]: no method named `fit_into_width` found for struct `Grid` in the
current scope
--> src/uu/ls/src/ls.rs:2612:20
|
2612 | match grid.fit_into_width(width as usize) {
|^^ method not found in `Grid<_>`
error[E0599]: no method named `fit_into_columns` found for struct `Grid` in the
current scope
--> src/uu/ls/src/ls.rs:2618:40
|
2618 | write!(out, "{}", grid.fit_into_columns(1))?;
| method not found in
`Grid<_>`
Bug#1067715: closed by yokota (Re: Bug#1067715: calibre: doesn't install DeACSM plugin)
reopen 1067715 tags 1067715 + fixed-upstream thanks On Thu, 28 Mar 2024 15:15:05 + "Debian Bug Tracking System" wrote: > This is an automatic notification regarding your Bug report > which was filed against the calibre package: > > #1067715: calibre: doesn't install DeACSM plugin > > It has been closed by yokota . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact yokota > by > replying to this email. > «This bug is now closed because it was already fixed on upstream development code.» Yokota, Please, don't close bugs just because they are fixed upstream, the fixed-upstream exists exactly for this. The report shall remain open until the bug is fixed on all currently published Debian releases. I don't know yet whether the fix is already on an official Calibre release, or just on their development repository. What I have no doubt is the bug is still present on stable (bookworm), so until it gets fixed there this report shall remain open. Feel free to tag it for bookworkm, bullseye and buster appropriately if the fix is already into testing and unstable. Thanks a lot for your understanding and your effort at maintaining the package. Best regards, José Luis
