Bug#1110138: ltrace: wtb bitfield-enum decoding

2025-07-31 Thread наб
Control: tags -1 + patch memcpy(0x7ffeae63e888, ".", 1) = 0x7ffeae63e888 inotify_add_watch(3, ".", IN_MOVED_TO|IN_CREATE|IN_DELETE_SELF|IN_MOVE_SELF|IN_ONLYDIR|IN_EXCL_UNLINK) = 1 reallocarray(nil, 2, 8)

Bug#1110138: ltrace: wtb bitfield-enum decoding

2025-07-30 Thread наб
Package: ltrace Version: 0.7.91~git20230705.8eabf68-3 Severity: wishlist Dear Maintainer, In a config like #include int inotify_init(); int inotify_init1(octal); int inotify_add_watch(int, string, hex(int)); int inotify_rm_watch(int, int); the hex(int) fie

Bug#1108037: linux-perf: perf report --demangle only works on some(?) symbols

2025-07-09 Thread наб
Control: tag -1 - moreinfo On Wed, Jul 09, 2025 at 06:15:10PM +0200, Ben Hutchings wrote: > What does the actual declaration of this function look like, and what > toolchain are you using to compile it? I get this out of src:botan3 3.7.1+dfsg-2 src/lib/modes/cbc/cbc.cpp when building with clang t

Bug#1108665: override: cron:admin/optional

2025-07-02 Thread наб
On Wed, Jul 02, 2025 at 11:24:59PM +0200, Alexandre Detiste wrote: > Le mer. 2 juil. 2025 à 17:35, Chris Hofstaedtler a écrit : > > > Without any particular hat: I would expect someone wanting to drop cron > > > to come up with some analysis of what remains to be done and what is > > > going to br

Bug#1108632: libqt6widgets6: the triangle sort order icons in a filter/sort view are backwards

2025-07-01 Thread наб
Package: libqt6widgets6 Version: 6.4.2+dfsg-10 Version: 6.8.2+dfsg-8 Severity: normal Dear Maintainer, In the default theme, QSortFilterProxyModel's arrows are backwards, please consult attached screenshots of sample project (https://www.walletfox.com/course/qsortfilterproxymodelexample.php). I

Bug#1108393: Also look up birthdays in ~/.config/

2025-06-28 Thread наб
Control: tags -1 + pending Fixed in git @ https://salsa.debian.org/salvage-team/birthday/-/commit/cce369fe86c73f11c94b4334699f70fabbdaa603 staged for post-trixie. signature.asc Description: PGP signature

Bug#1108129: ITP: wg-netns -- Create network namespace with wireguard tunnel

2025-06-21 Thread наб
On Sat, Jun 21, 2025 at 05:20:03AM +0200, Mazen Neifer wrote: > On Sat, 2025-06-21 at 01:44 +0200, наб wrote: > > * Package name    : wg-netns > > > > I would need a sponsor. > I can sponsor that if you want. Thanks; barring any objections I'll finish this up post

Bug#1108129: ITP: wg-netns -- Create network namespace with wireguard tunnel

2025-06-20 Thread наб
Package: wnpp Severity: wishlist Owner: наб X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: wg-netns Version : 2.3.5 * URL : https://github.com/dadevel/wg-netns * License : MIT Programming Lang: Python Description : Create network namespace

Bug#1108037: linux-perf: perf report --demangle only works on some(?) symbols

2025-06-19 Thread наб
Please see https://lfs.nabijaczleweli.xyz/0027-b.d.o-1108037/perf.tar.zst instead of attachment. signature.asc Description: PGP signature

Bug#1108037: linux-perf: perf report --demangle only works on some(?) symbols

2025-06-19 Thread наб
Package: linux-perf Version: 6.1.140-1 Version: 6.12.30-1 Version: 6.12.32-1 Severity: normal Dear Maintainer, I'm attaching a tarball that, when extracted in the home directory, should demonstrate the issue. Running perf report -g --demangle shows Samples: 278K of event 'cycles:u', Event coun

Bug#1108033: Should dradio be removed from unstable?

2025-06-19 Thread наб
Source: dradio Severity: serious Justification: grab attention of maintainer X-Debbugs-Cc: Package Salvaging Team User: helm...@debian.org Usertags: sidremove Dear Maintainer, I suggest removing dradio from Debian for the following reasons: * It accumulated one RC-bug: + #1057554 dradio: FTB

Bug#1108008: cryfs: embeds src:cryptopp

2025-06-18 Thread наб
Source: cryfs Version: 0.11.4-3 Severity: normal Dear Maintainer, cryfs embeds the entirety of src:cryptopp, in violation of policy 4.13. Best, -- System Information: Debian Release: 12.11 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stab

Bug#1014382: dradio currently not usable

2025-06-18 Thread наб
Control: tags -1 + patch $ valgrind dradio ==4191498== Memcheck, a memory error detector ==4191498== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==4191498== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info ==4191498== Command: dradio ==4191498== ==4191498== In

Bug#1107929: python3-protobuf: DeprecationWarning: datetime.datetime.utcfromtimestamp() is deprecated and scheduled for removal in a future version.

2025-06-17 Thread наб
Package: python3-protobuf Version: 3.21.12-3 Severity: normal Dear Maintainer, When running electrum, I got /usr/lib/python3/dist-packages/google/protobuf/internal/well_known_types.py:91: DeprecationWarning: datetime.datetime.utcfromtimestamp() is deprecated and scheduled for removal in a fu

Bug#1107814: darkstat: With -i parameter only, starts listening on 0.0.0.0 and [::]

2025-06-15 Thread наб
Control: severity -1 wishlist Control: tags -1 + wontfix On Sun, Jun 15, 2025 at 01:20:15AM +, Witold Baryluk wrote: > Package: darkstat > Version: 3.0.721-2 > > When started with no extra arguments other than required -i INTERFACE, > it default to listening on 0.0.0.0 and [::] port 667. > >

Bug#1107745: iproute2: parser refuses to parse ip link set $DEVICE macaddr del $MACADDR, manual says that's right

2025-06-13 Thread наб
Package: iproute2 Version: 6.1.0-3 Version: 6.13.0-1 Severity: normal Dear Maintainer, ip-link(8) says ip link { set | change } { DEVICE | group GROUP } [ { up | down } ] ... [ addrgenmode { eui64 | none | stable_secret | random } ]

Bug#1107279: dh-cargo: silently ignores --sourcedirectory

2025-06-04 Thread наб
Package: dh-cargo Version: 30 Severity: normal Dear Maintainer, I have dh $@ --buildsystem cargo with dh_auto_clean --sourcedirectory=b3sum dh_auto_configure --sourcedirectory=b3sum dh_auto_build --sourcedirectory=b3sum dh_auto_test --sourcedirectory=b3sum dh_auto_install

Bug#1107091: [Pkg-rust-maintainers] Bug#1107091: rust-blake3: please also build libblake3-dev

2025-06-03 Thread наб
On Mon, Jun 02, 2025 at 08:25:06PM +0200, Fabian Grünbichler wrote: > On Sun, Jun 1, 2025, at 4:29 PM, наб wrote: > > Upstream distributes libblake3 in c/, > > this should be easily buildable with dh_auto_build --sourcedir c &c. > > > > Please distribute this. A

Bug#1107164: /usr/bin/x86_64-linux-gnux32-ld.bfd: /bin/ld: cryptic "error: could not close arguments file" when /tmp ENOSPC

2025-06-02 Thread наб
Package: binutils-x86-64-linux-gnux32 Version: 2.43.90.20250127-1 Severity: minor File: /usr/bin/x86_64-linux-gnux32-ld.bfd Dear Maintainer, I'd recently been hit with the following error $ make ... /bin/ld: error: could not close arguments file collect2: error: ld returned 1 exit status

Bug#1107092: [Pkg-rust-maintainers] Bug#1107092: rust-b3sum: why not build this out of src:rust-blake3?

2025-06-02 Thread наб
Control: tag -1 unreproducible Control: close -1 On Mon, Jun 02, 2025 at 08:19:45PM +0200, Fabian Grünbichler wrote: > On Sun, Jun 1, 2025, at 4:34 PM, наб wrote: > > src:rust-blake3 consists of the whole upstream BLAKE3 distribution, > > incl. b3sum; > it does not - that&

Bug#1055526: efibootmgr: output broken and shows hex dump after update (can be fixed with -u, which is documented as unrelated)

2025-06-02 Thread наб
Control: tags -1 + patch On Sun, Jun 01, 2025 at 04:17:41PM +0200, Fab Stz wrote: > You might also be interested in this commit > > https://github.com/rhboot/efibootmgr/commit/ > e8ce9fecebd15adb4c60a0678d4c417afe06dde4 You're right. That yielded a simple patch https://github.com/rhboot/efiboo

Bug#1107093: Embeds BLAKE3 C implementation, should use libblake3-dev when it becomes available

2025-06-01 Thread наб
Source: wasmedge Version: 0.14.1+dfsg-3.1 Severity: wishlist Control: block 1107091 by -1 Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 Control: reassign -2 src:librecast 0.9.1-1 Control: reassign -3 src:cryptokit 1.20.1-1 Control: reassign -4 src:litecoin 0.21.4-1 Control: reassign -5 src:mesa 25.0.5-

Bug#1055526: efibootmgr: output broken and shows hex dump after update (can be fixed with -u, which is documented as unrelated)

2025-06-01 Thread наб
Funnily enough, efibootmgr 18-1: $ efibootmgr BootCurrent: 0001 Timeout: 2 seconds BootOrder: 0001,0004,0002,0003,0007, Boot* Enter Setup FvVol(8063c21a-8e58-4576-95ce-089e87975d23)/FvFile(462caa21-7614-4503-836e-8ab6f4662331) Boot0001* Debian GNU/Linux trixie/sid with Linux 6.6.9-amd64

Bug#1107104: qemu-system-x86: qemu-system-i386 -smp 6 (-smp >2) breaks the NetBSD bootloader now ‒ regression from 1:7.2+dfsg-7+deb12u7 to 1:9.1.1+ds-2~bpo12+1 and later

2025-06-01 Thread наб
On Sun, Jun 01, 2025 at 06:20:17PM +0200, наб wrote: > On Sun, Jun 01, 2025 at 07:07:18PM +0300, Michael Tokarev wrote: > > On 01.06.2025 18:47, наб wrote: > > >curl -SOL > > > ftp://ftp.netbsd.org/pub/NetBSD/images/10.1/NetBSD-10.1-i386.iso > > >qemu-

Bug#1107104: qemu-system-x86: qemu-system-i386 -smp 6 (-smp >2) breaks the NetBSD bootloader now ‒ regression from 1:7.2+dfsg-7+deb12u7 to 1:9.1.1+ds-2~bpo12+1 and later

2025-06-01 Thread наб
On Sun, Jun 01, 2025 at 07:07:18PM +0300, Michael Tokarev wrote: > On 01.06.2025 18:47, наб wrote: > >curl -SOL > > ftp://ftp.netbsd.org/pub/NetBSD/images/10.1/NetBSD-10.1-i386.iso > >qemu-system-i386 -enable-kvm -smp 6 -m 4G -cdrom NetBSD-10.1-i386.iso > > n

Bug#1107104: qemu-system-x86: qemu-system-i386 -smp 6 (-smp >2) breaks the NetBSD bootloader now ‒ regression from 1:7.2+dfsg-7+deb12u7 to 1:9.1.1+ds-2~bpo12+1 and later

2025-06-01 Thread наб
Package: qemu-system-x86 Version: 1:9.1.1+ds-2~bpo12+1 Version: 1:9.2.0+ds-3~bpo12+2 Version: 1:9.2.2+ds-1~bpo12+1 Version: 1:10.0.0+ds-2~bpo12+2 Severity: normal Dear Maintainer, curl -SOL ftp://ftp.netbsd.org/pub/NetBSD/images/10.1/NetBSD-10.1-i386.iso qemu-system-i386 -enable-kvm -smp 6 -m

Bug#1107092: rust-b3sum: why not build this out of src:rust-blake3?

2025-06-01 Thread наб
Source: rust-b3sum Severity: minor Control: affects -1 src:rust-blake3 Dear Maintainer, src:rust-blake3 consists of the whole upstream BLAKE3 distribution, incl. b3sum; there doesn't appear to be a reason to duplicate just part of it to src:rust-b3sum? -- System Information: Debian Release: 12.

Bug#1107091: rust-blake3: please also build libblake3-dev

2025-06-01 Thread наб
Source: rust-blake3 Severity: wishlist Dear Maintainer, Upstream distributes libblake3 in c/, this should be easily buildable with dh_auto_build --sourcedir c &c. Please distribute this. A quick DCS query http://codesearch.debian.net/search?q=%5Cbblake3_hasher_init%5Cb&literal=0&perpkg=1 says

Bug#1106778: coreutils: dd: status=progress dumps progress updates after every I/O for every second it was SIGSTOPped

2025-05-29 Thread наб
Package: coreutils Version: 9.7-2 Version: 9.1-1 Severity: minor Dear Maintainer, If you ^Z dd status=progress, then resume it, it will issue a slew of updates to the status line; script shows this roughly corresponds to 1 update per suspended second, and the status is dumped after /every/ I/O un

Bug#1106762: ltrace: -p $pid SIGCONTs $pid

2025-05-29 Thread наб
Control: retitle -1 ltrace: -p $pid SIGCONTs $pid and makes SIGTSTPping $pid ineffective Actually, if you attach ltrace -p then you can ^Z and it instantly resumes. You can then fg, ^Z and this repeats. ll.zst Description: application/zstd signature.asc Description: PGP signature

Bug#1106763: ltrace: would like -b/--detach-on= like strace

2025-05-29 Thread наб
Package: ltrace Version: 0.7.91~git20230705.8eabf68-3 Severity: wishlist Dear Maintainer, I just ran into a use-case where having ltrace -b, like strace -b, would've been very useful. Please implement this. Best, -- System Information: Debian Release: 12.11 APT prefers stable-updates APT po

Bug#1106762: ltrace: -p $pid SIGCONTs $pid

2025-05-29 Thread наб
Package: ltrace Version: 0.7.91~git20230705.8eabf68-3 Severity: normal Dear Maintainer, $ /dev/null 1756444160 bytes (1.8 GB, 1.6 GiB) copied, 4 s, 439 MB/s^Z [3]+ Stopped /bin/dd status=progress < /dev/zero > /dev/null $ jobs -p %3 3049318 $ ltrace -p 3049318 -o /dev/null 21471

Bug#1106726: ITS: mhddfs

2025-05-28 Thread наб
Source: mhddfs Severity: important X-Debbugs-Cc: Package Salvaging Team Dear Maintainer, I'm interested in salvaging your package mhddfs, in accordance with the Package Salvaging procedure outlined in the Developers Reference[1]. Your package meets the criteria for this process, and I would love

Bug#661136: dhcp_probe output to output file is garbled

2025-05-24 Thread наб
Control: tags -1 + moreinfo On Fri, Feb 24, 2012 at 11:57:35AM +, Shalom Bhooshi wrote: > When the -o option is used to the dhcp_probe command, all the output > to the file seems to be garbled. > > # dhcp_probe -f eth0 -o /dev/stdout > note: starting, version 1.3.0 > warn: received unexpe

Bug#944622: Moreinfo: Bug#944622: sloccount: Fails in a non-ASCII directory

2025-05-24 Thread наб
Control: tags -1 + moreinfo Can't repro this. $ cp -r ~/code/archivemount-ng/ göming $ sloccount . Have a non-directory at the top, so creating directory top_dir Adding /home/nabijaczleweli/uwu/sloccount/./COPYING to top_dir Adding /home/nabijaczleweli/uwu/sloccount/./ChangeLog to top_dir Adding

Bug#716179: sloccount: php_count, ml_count, c_count: echo /ENOENT | $count -f - &c. segfault

2025-05-24 Thread наб
Control: retitle -1 sloccount: php_count, ml_count, c_count: $count /ENOENT & echo /ENOENT | $count -f - &c. segfault Control: merge -1 716181 $ echo /ENOENT | ./ml_count -f - Segmentation fault (core dumped) $ echo /ENOENT | ./c_count -f - Segmentation fault (core dumped) $ echo /ENOENT | ./php_

Bug#1106450: sloccount: explodes when given --datadir when $PWD has spaces

2025-05-24 Thread наб
Package: sloccount Version: 2.26-5.2 Version: 2.26+ds-1 Severity: normal Dear Maintainer, Try sloccount --datadir . . when $PWD has a space in it: + cd . + pwd + datadir=/home/nabijaczleweli/code/archive mount + cd /home/nabijaczleweli/code/archive mount /bin/sloccount: 85: cd: can't cd

Bug#1106403: unblock: archivemount/1b-1

2025-05-24 Thread наб
/debian/changelog 2024-12-21 16:00:13.0 +0100 +++ archivemount-1b/debian/changelog 2025-05-14 16:06:03.0 +0200 @@ -1,3 +1,10 @@ +archivemount (1b-1) unstable; urgency=medium + + * New upstream version 1b (+ changelog & NEWS) + Closes: #1105758 + + -- наб Wed, 14 May 2025 1

Bug#1106346: php-net-publicsuffix: Should php-net-publicsuffix be removed from unstable?

2025-05-23 Thread наб
Control: tags -1 - wontfix Nevermind https://bugs.debian.org/1090260#29 signature.asc Description: PGP signature

Bug#1090260: Reassign: Bug#1090260: php-net-publicsuffix: FTBFS: PHP Fatal error: Uncaught ValueError: idn_to_ascii(): Argument #1 ($domain) must not be empty

2025-05-23 Thread наб
On Fri, May 23, 2025 at 07:41:20PM +0200, Ondřej Surý wrote: > Sorry, but no - the usage of idn_to_ascii() is invalid in > php-net-publicsuffix and you need to fix it there. > > The missing check got fixed in > https://github.com/php/php-src/commit/33f1cf202ef1 and it's OK to make small > chang

Bug#1106346: php-net-publicsuffix: Should php-net-publicsuffix be removed from unstable?

2025-05-23 Thread наб
Control: tags -1 + wontfix On Fri, May 23, 2025 at 08:33:47AM +0200, Andreas Tille wrote: > Source: php-net-publicsuffix > Version: 0.2-1.1 > Severity: serious > Justification: grab attention of maintainer > > Dear maintainer, > > I suggest removing php-net-publicsuffix from Debian for the foll

Bug#1090260: Reassign: Bug#1090260: php-net-publicsuffix: FTBFS: PHP Fatal error: Uncaught ValueError: idn_to_ascii(): Argument #1 ($domain) must not be empty

2025-05-23 Thread наб
Control: retitle -1 php8.4-intl: idn_to_ascii("") throws ValueError ‒ regression from bookworm Control: reassign -1 php8.4-intl 8.4.6-2 Control: affects -1 php-net-publicsuffix On Mon, Dec 16, 2024 at 05:51:30PM +, Santiago Vila wrote: > Package: src:php-net-publicsuffix > Version: 0.2-1.1 >

Bug#1106029: installation-reports: trixie RC1 fails to add a boot entry or create a bootx64.efi on EFI (=> installs unbootable system)

2025-05-19 Thread наб
Control: reassign -1 qemu-system-x86 1:9.2.0+ds-3~bpo12+2 Control: retitle -1 qemu-system-x86: fails to save boot entries when installing to blank disk(?) => trixie d-i installs unbootable system efibootmgring in the chroot but before the reboot shows Boot0009=File(shimx64.efi); QEMU /can/ save

Bug#1106000: systemd-cron: purging "anacron" after systemd-cron will publish message with level 'error' on journal, once

2025-05-18 Thread наб
rol: Update standards version to 4.7.2 - -- Lance Lin Wed, 23 Apr 2025 20:47:24 +0700 + [ наб ] + * d/cron.d: move [ -x test into if so it doesn't fail the job if it fails (Closes: #1106000) + + -- наб Sun, 18 May 2025 21:31:24 +0200 anacron (2.3-42) unstable; urgency=medium diff

Bug#1105758: archivemount: hides files with non-ASCII names from archives

2025-05-14 Thread наб
Package: archivemount Version: 1a-1+b1 Severity: important Tags: upstream fixed-upstream Control: forwarded -1 https://todo.sr.ht/~nabijaczleweli/archivemount-ng/2 $ base64 pack.rar UmFyIRoHAM+QcwAADQDIfnQgkCwADwEAAHwBAAAChMuQh7Eim1odMwcAIHNpZ250 YWcA8DbPlAwVDMzP1UETeuFGtsOW0BNW3ZaJdl4

Bug#914542: dict-jargon: Merging with src:jargon and src:jargon-text

2025-05-08 Thread наб
On Sat, Nov 24, 2018 at 03:48:49PM +, Dmitry Bogatov wrote: > There is three source packages in Debian, that contain Jargon File > * `dict-jargon' (v4.4.7) > * `jargon-text' (v4.4.7) -- orphaned > * `jargon' (v4.0.0) -- out-of-date, as written in description dict-jargon's maintainer is MIA a

Bug#1104914: tgt-admin: -d is supposed to be --delete but is an "Option d is ambiguous (delete, dump)" error instead

2025-05-08 Thread наб
Package: tgt Version: 1:1.0.85-1.3 Severity: normal Dear Maintainer, Quoth tgt-admin(1): OPTIONS -d, --delete Delete all or selected targets. The target will be deleted only if it's not used (no initiator is connected to it). And yet # tgt-admin -d Option d is ambig

Bug#1104609: /usr/share/groff/1.23.0/tmac/doc.tmac: Nm in broken in -Tps with multiple documents

2025-05-02 Thread наб
By applying "/Sh Name/i.ds doc-topic-name" to the input to explicitly clear what should've been, I've managed to work around this. But, it should just work instead. I see . ds doc-topic-name \" empty in .de doc-end-macro and then .\" NS Dd user macro (not parsed, not callable) .\" NS set

Bug#1104609: /usr/share/groff/1.23.0/tmac/doc.tmac: Nm in broken in -Tps with multiple documents

2025-05-02 Thread наб
Package: groff-base Version: 1.23.0-7 Severity: important File: /usr/share/groff/1.23.0/tmac/doc.tmac Dear Maintainer, Observe the Nms in https://ra.ws.co.ls/~nabijaczleweli/tzpfms/blob/f2bb78cd74ba4237cc1036ef9825d448963b51a4/tzpfms.pdf (as built with groff -K utf8 -tpe -mdoc -Tps -dpaper=a4

Bug#1103255: /usr/bin/rails: No $EDITOR to open file in. Assign one like this: EDITOR="mate --wait" bin/rails credentials:edit

2025-04-15 Thread наб
On Tue, Apr 15, 2025 at 03:20:02PM -0300, Antonio Terceiro wrote: > However, not following a "should" directive in policy is not really a > serious bug. Whoops, misread the "must" for using-$EDITOR-in-general as also applying to defaulting-to-/bin/editor. my b. signature.asc Description: PGP sign

Bug#1103255: /usr/bin/rails: No $EDITOR to open file in. Assign one like this: EDITOR="mate --wait" bin/rails credentials:edit

2025-04-15 Thread наб
Package: ruby-railties Version: 2:6.1.7.10+dfsg-1~deb12u1 Severity: serious Justification: Policy 11.4 File: /usr/bin/rails Dear Maintainer, I just got $ rails credentials:edit No $EDITOR to open file in. Assign one like this: EDITOR="mate --wait" bin/rails credentials:edit For edit

Bug#1053738: [debian-mysql] Bug#1053738: Bug#1053738: mariadb: what's up with the binary sizes?

2025-04-12 Thread наб
On Sat, Apr 12, 2025 at 08:00:00AM +0300, Otto Kekäläinen wrote: > I never saw a patch or MR about this, I discarded it when it didn't work I think. > but I am happy to have one, even > if it is only 90% done and failing, if you still want to help optimize > the binary sizes. Here's a quick recons

Bug#1101361: ltrace crashes when attaching to a process that links a deleted library

2025-04-05 Thread наб
On Wed, Mar 26, 2025 at 10:59:58PM +0900, Adam Rice wrote: > Package: ltrace > Version: 0.7.3+git20240814-0.3 > Severity: normal > Tags: upstream > X-Debbugs-Cc: ri...@google.com > > Sample output: > """ > ===> Building in /tmp/tmp.oldWtch6po ... > ===> Running ltrace -p 4025257 ... > Can't open /

Bug#1101435: /usr/bin/pyftsubset: ModuleNotFoundError: No module named 'zopfli' with --flavor=woff

2025-03-31 Thread наб
On Mon, Mar 31, 2025 at 02:33:43PM -0400, Boyuan Yang wrote: > Package python3-zopfli is needed, however it only presents in Debian > 13/Testing/Sid now. > > I am not sure what would be the best way forward. A stable-backports is > possible, yet > it won't fundamentally solve the issue in the St

Bug#1101446: RFS: rarpd/0.981107-9.1 [NMU] -- Reverse Address Resolution Protocol daemon

2025-03-27 Thread наб
net/debian/pool/main/r/rarpd/rarpd_0.981107-9.1.dsc Changes since the last upload: rarpd (0.981107-9.1) unstable; urgency=medium . * Non-maintainer upload. * d/rarpd.service: add (Closes: #1039343) Regards, -- наб signature.asc Description: PGP signature

Bug#1101435: /usr/bin/pyftsubset: ModuleNotFoundError: No module named 'zopfli' with --flavor=woff

2025-03-27 Thread наб
Package: fonttools Version: 4.38.0-1 Severity: normal File: /usr/bin/pyftsubset Dear Maintainer, $ pyftsubset RobotoSlab-Regular+tabdig.ttf --flavor="woff" --output-file="RobotoSlab-Regular+tabdigS.woff" --unicodes="0123456789" --with-zopfli --verbose 2>&1 Text: '' Unicodes: [

Bug#1100866: RFS: ddate/0.2.2-1.1 [NMU] [RC] -- convert Gregorian dates to Discordian dates

2025-03-19 Thread наб
es-Requires-Root: no (routine-update) * watch file standard 4 (routine-update) * Update d/gbp.conf for new version * E: ddate: alien-tag no-upstream-changelog Regards, -- наб signature.asc Description: PGP signature

Bug#1100778: RFS: fdclone/3.01j-1.1 [NMU] [RC] -- console-base lightweight file manager

2025-03-18 Thread наб
able; urgency=medium . * Non-maintainer upload. . [ Debian Janitor ] * Use secure URI in Homepage field. * Bump debhelper from old 12 to 13. * Update standards version to 4.6.1, no changes needed. * Avoid explicitly specifying -Wl,--as-needed linker flag. . [ наб ] * Fix GCC-14 FTB

Bug#1099665: Reassign: Bug#1099665: gnome-shell-extensions-apps-menu: gnome has removed this package

2025-03-15 Thread наб
Control: reassign -1 gnome-shell-extension-apps-menu 48~rc-1 How did you manage to report this with the wrong package name? signature.asc Description: PGP signature

Bug#1099831: Should atitvout be removed from unstable?

2025-03-08 Thread наб
Source: atitvout Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing atitvout from Debian for the following reasons: * It accumulated one RC-bug: + #1063644: missing required debian/rules targets build-

Bug#1060057: returning to pending CUPS-PDF issue

2025-03-08 Thread наб
On Sat, Mar 08, 2025 at 07:10:40PM +0200, Martin-Éric Racine wrote: > la 8.3.2025 klo 18.03 наб (nabijaczlew...@nabijaczleweli.xyz) kirjoitti: > > I just explicitly updated cups-pdf cups ghostscript on sid and > > lp -dPDF all.ps > > still produced an empty file (attached).

Bug#1060057: returning to pending CUPS-PDF issue

2025-03-08 Thread наб
I just explicitly updated cups-pdf cups ghostscript on sid and lp -dPDF all.ps still produced an empty file (attached). CUPS config attached, log below. $ dpkg -l | grep -e cups -e pdf -e ghost ii cups 2.4.10-2+b1amd64 Common UNIX Printing System(tm) - PPD/drive

Bug#879118: Maintaining buffer on Salsa in Debian team?

2025-03-07 Thread наб
On Fri, Mar 07, 2025 at 02:34:32PM +0100, Martin Buck wrote: > On Wed, Mar 05, 2025 at 10:44:45AM +0100, Andreas Tille wrote: > > Inside the Tiny Tasks Matrix channel наб asked: > >"isn't mbuffer the same as buffer but better?" > > So I'm all fo

Bug#1099307: librep: binary-all FTBFS

2025-03-01 Thread наб
Control: tags -1 + pending https://salsa.debian.org/debian/librep/-/commit/bf6b39cff1d5cbf1fc6d0c7c53a335e44580d7ed and this is tagged debian/0.92.7-2 but is not in the 0.92.7-2 dsc 💀 so Andreas uploaded a .changes from the wrong revision, reads like? signature.asc Description: PGP signature

Bug#953879: Please review potential NMU of libnl3

2025-02-26 Thread наб
Control: tags -1 + wontfix Control: close -1 Hi! [CC += #953879] On Wed, Feb 26, 2025 at 02:21:17AM +0100, Cyril Brulebois wrote: > I don't think that's a practical problem, but that would be a change > compared to the libnl-genl-3-200-udeb package found in unstable, which > ships the library un

Bug#1098736: ibus 1.5.32~beta2-2 breaks + on US intl layout

2025-02-24 Thread наб
Control: forcemerge -1 1098792 In discussion under forwarded, we can see that > But if user does not have the compose file, IBus won't touch it. > I thought this case and it's now timeout. And naturally the release notes https://github.com/ibus/ibus/releases/tag/1.5.32-beta2 say > Your compose

Bug#1098747: bugs.debian.org: "Please confirm subscription" mail from nnn-subhelp@b.d.o's header dump is a one-line python-encoded b'...' string instead of an actual header dump (broken between 2024-0

2025-02-23 Thread наб
Package: bugs.debian.org I noticed this on a subscription confirmation from today; looking back through my archive, this started happening some time after Date: Wed, 10 Jan 2024 15:27:11 + (UTC) but before Date: Fri, 5 Jul 2024 14:00:11 + (UTC) (unfortunately that's the best granulari

Bug#1098481: FTBFS: static_asserts in matchpathcon.c impossible to satify on x32

2025-02-22 Thread наб
Control: forwarded -1 https://github.com/SELinuxProject/selinux/issues/463 Control: tags -1 + patch The reported forwarded this; I wrote a patch @ https://github.com/SELinuxProject/selinux/pull/464 which I'm including below. This makes selinux trunk compile on my x32 system (x32 does not need m

Bug#716481: libdisasm 0.23-7 uploaded to DELAYED/10

2025-02-21 Thread наб
Control: tags -1 + pending Accd'g to the #1094816 ITS, libdisasm 0.23-7 was just uploaded to DELAYED/10 signature.asc Description: PGP signature

Bug#1095576: RFS: cvsweb/3:3.0.6-9 [ITA] -- CGI interface to your CVS repository

2025-02-19 Thread наб
[sorry for the delay, you didn't CC me, had to get this off the bug page] On Tue, Feb 11, 2025 at 05:37:58AM +0900, Jing Luo wrote: > On 2025-02-10 01:14, наб wrote: > > Overall looks pretty good, but note: > > * You have doubled changelog entries. > > * Accd'g

Bug#580822: aggregate 1.6-8 uploaded to DELAYED/10.

2025-02-18 Thread наб
Control: tags -1 + pending Accd'g to the #1094428 ITS, aggregate 1.6-8 was just uploaded to DELAYED/10. signature.asc Description: PGP signature

Bug#1093192: #1093192 "ITS: vtgrab": no uploaders specified?

2025-02-16 Thread наб
On Sun, Feb 16, 2025 at 05:29:26PM +0100, Chris Hofstaedtler wrote: > On Sun, Feb 16, 2025 at 05:18:39PM +0100, наб wrote: > > Quoting the relevant: > > > It is recommended to choose between one of the two following schemes: > > > 2. Put the mailing list addr

Bug#1093192: #1093192 "ITS: vtgrab": no uploaders specified?

2025-02-16 Thread наб
On Sun, Feb 16, 2025 at 08:56:22AM +0100, Joost van Baal-Ilić wrote: > When dealing with #1093192 "ITS: vtgrab", you've set > "Maintainer: Package Salvaging Team " > in https://salsa.debian.org/salvage-team/vtgrab/-/blob/debian/debian/control . > However, you forgot to set the "Uploaders: "-field:

Bug#1082108: ttyrec 1.1.7.1-1 uploaded to DELAYED/10

2025-02-15 Thread наб
Control: tags -1 + pending Accd'g to the #1094191 ITS, ttyrec 1.1.7.1-1 was just uploaded to DELAYED/10. signature.asc Description: PGP signature

Bug#1095855: libzfslinux-dev: pkg-config --cflags libzfs (or libzfs_core) always fails now with "Package libtirpc was not found in the pkg-config search path." (same for zlib)

2025-02-12 Thread наб
one day i will not forger 💀 a patch From a5908434a5f0ab6d7956962b49c5706552d26738 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=BD=D0=B0=D0=B1?= Date: Thu, 13 Feb 2025 01:00:23 +0100 Subject: [PATCH] d/control: libzfslinux-dev Depends: libtirpc-dev, zlib1g-dev (Closes: #1095855) X-Mutt-PGP: OS --

Bug#1095855: libzfslinux-dev: pkg-config --cflags libzfs (or libzfs_core) always fails now with "Package libtirpc was not found in the pkg-config search path." (same for zlib)

2025-02-12 Thread наб
've narrowed this down to a pkg-config --cflags libzfs libzfs_core invocation. Installing libtirpc-dev and zlib1g-dev fixed this and let fzifdso build. Attaching patch that fixes this by adding them to Depends:, also in the form of an MR at https://salsa.debian.org/zfsonlinux-team/zfs/

Bug#1066410: [Help] Seems to be autoconf issue in ncftp

2025-02-12 Thread наб
https://salsa.debian.org/debian/ncftp/-/merge_requests/1 signature.asc Description: PGP signature

Bug#1095677: lowmem installer UI frames start getting corrupted (UTF-8 as cp437(?)) after first stage of install (@ scanning install media stage)

2025-02-10 Thread наб
Package: debian-cd Severity: normal Hi! Reported by a friend, I'm reproing in QEMU (> 4G; truncate -s 4G 4G; qemu-system-x86_64 -enable-kvm -smp 2 -m 500m -cdrom debian-testing-amd64-netinst.iso 4G -bios /usr/share/ovmf/OVMF.fd and non-lowmem with -m 2g) but platform probably irrelevant; happen

Bug#1095576: RFS: cvsweb/3:3.0.6-9 [ITA] -- CGI interface to your CVS repository

2025-02-09 Thread наб
s since the last upload: > > cvsweb (3:3.0.6-9) unstable; urgency=medium > . >[ наб ] >* Vcs-Git: https://salsa.debian.org/debian/cvsweb.git > . >[ Jing Luo ] >* d/control: upgrade standards version to 4.7.0 >* d/control: upgrade debhelper-compat

Bug#1094933: ITS: proot

2025-02-08 Thread наб
Control: affects -1 + src:care Further analysis shows that src:care is built from the same upstream source as src:proot and has been similarly neglected. If this ITS pops, src:proot will instead build proot and care, and this will be cloned to RM ROM src:care (which will at that point be providin

Bug#1075630: vtgrab 0.1.8-4 uploaded to DELAYED/10

2025-02-06 Thread наб
Control: tags -1 + pending Per the #1093192 ITS, vtgrab 0.1.8-4 was just uploaded to DELAYED/10. signature.asc Description: PGP signature

Bug#1095123: Should asmix be removed from unstable?

2025-02-03 Thread наб
Source: asmix Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing asmix from Debian for the following reasons: * It accumulated one RC-bug: + #1066206: asmix: FTBFS: asmix.c:193:61: error: implicit decl

Bug#1063806: closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#1063806: fixed in clutter-imcontext 0.1.4-4)

2025-02-01 Thread наб
On Sat, Feb 01, 2025 at 10:49:42AM +0100, Helmut Grohne wrote: > On Fri, Jan 31, 2025 at 07:09:01AM +, Debian Bug Tracking System wrote: > > #1063806: clutter-imcontext FTCBFS: fails running gtk-doc scanner > This bug is reproducible on 0.1.4-4 and my patch evidently has not been > applied. The

Bug#1094917: dump: new NEWS say /usr/share/dump/NEWS.gz instead of /usr/share/doc/dump/NEWS.gz

2025-02-01 Thread наб
Package: dump Version: 0.4b49-1 Severity: minor Dear Maintainer, dump (0.4b49-1) unstable; urgency=high release 0.4b49 is not fully backwards compatible with older releases: older releases cannot restore backups that have been created with 0.4b49. the codebase has been refreshed and fix

Bug#1094880: coreutils: numfmt: --format refuses -

2025-01-31 Thread наб
Package: coreutils Version: 9.4-3 Version: 9.1-1 Severity: normal Dear Maintainer, $ numfmt --format "AB%0'-fCD" '123' | cat -A numfmt: invalid format ‘AB%0'-fCD’, directive must be %[0]['][-][N][.][N]f The directive is exactly that. Expecting $ out/cmd/numfmt --format "AB%0'-fCD"

Bug#1094868: coreutils: numfmt: --format doesn't understand 0

2025-01-31 Thread наб
Package: coreutils Version: 9.1-1 Version: 9.4-3 Severity: normal Dear Maintainer, $ numfmt --format 'ab%0fcd' '123 123' --field - --suffix ef ab 123efcd ab 123efcd The manual says %0f should work. Well it says the '0' bit of that works, anyway, and it hasn't here. Best, -- Syste

Bug#1094816: ITS: libdisasm

2025-01-31 Thread наб
Source: libdisasm Severity: important X-Debbugs-Cc: Package Salvaging Team Dear Maintainer, I'm interested in salvaging your package libdisasm, in accordance with the Package Salvaging procedure outlined in the Developers Reference[1]. Your package meets the criteria for this process, and I woul

Bug#1094797: crypt++el: invalid maintainer address

2025-01-31 Thread наб
Source: crypt++el Severity: serious Justification: Policy 3.3 : host mitropoulos.debian.org[194.177.211.212] said: 550 Unrouteable address (in reply to RCPT TO command) https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer -- System Information: Debian Release: 12.9 APT pref

Bug#446133: Should crypt++el be removed from unstable?

2025-01-31 Thread наб
user helm...@debian.org usertags 446133 + sidremove severity 446133 important retitle 446133 Should crypt++el be removed from unstable? thanks Given the aforementioned and also the following factors: * last upstream version 2008 * last maintainer/uploader upload 2017 * upstream dead * upst

Bug#1094753: coreutils: numfmt: drops and force-rounds away all precision with --to!=none

2025-01-30 Thread наб
Package: coreutils Version: 9.4-3 Version: 9.1-1 Severity: normal Dear Maintainer, $ numfmt ' 1.110.1100.1 1000.1' --field - --to si --format '%.1f' 2.011.0101.0 1.1K $ numfmt ' 1.110.1100.1 1000.1' --field - --to iec --format '%.1f' 2.011.0101.0

Bug#1094752: coreutils: numfmt: loses autodetected precision (and also, therefore, introduces error) with --to!=none

2025-01-30 Thread наб
Package: coreutils Version: 9.4-3 Version: 9.1-1 Severity: normal Dear Maintainer, Per #1094384 we know that numfmt will, by default, reproduce the input XXX.YYY format. Except it doesn't actually, with --to!=none: it truncates to no precision (XXX): $ numfmt ' 1.110.1100.1 1000.1'

Bug#1094738: coreutils: numfmt: doesn't properly detect the width of the first field

2025-01-30 Thread наб
Package: coreutils Version: 9.4-3 Version: 9.1-1 Severity: normal Dear Maintainer, $ echo '123000 123123 -123123123' | numfmt --suffix Q --field - --to si 123KQ 124KQ -124MQ $ echo ' 123000 123123 -123123123' | numfmt --suffix Q --field - --to si 123KQ 124KQ

Bug#1094723: RFS: fdclone/3.01j-1.1 [NMU] [RC] -- console-base lightweight file manager

2025-01-30 Thread наб
able; urgency=medium . * Non-maintainer upload. . [ Debian Janitor ] * Use secure URI in Homepage field. * Bump debhelper from old 12 to 13. * Update standards version to 4.6.1, no changes needed. * Avoid explicitly specifying -Wl,--as-needed linker flag. . [ наб ] * Fix sig

Bug#1074949: Patch: Bug#1074949: fdclone: ftbfs with GCC-14

2025-01-29 Thread наб
Control: tags -1 + patch The patch is below, also forwarded to https://salsa.debian.org/elias/fdclone/-/merge_requests/2 and uploaded to mentors for an NMU. From: =?utf-8?b?0L3QsNCx?= Date: Thu, 30 Jan 2025 08:06:23 +0100 Subject: Fix signal2() FTBFS (Closes: #1074949) --- pathname.h | 18

Bug#1094670: ltrace: long doubles don't work (not supported at all, sliced into doubles)

2025-01-29 Thread наб
Package: ltrace Version: 0.7.91~git20230705.8eabf68-2 Severity: normal Control: forwarded -1 https://gitlab.com/cespedes/ltrace/-/issues/22 Dear Maintainer, Given #include #include int main(int n, char **) { printf("%d %f\n", n, log(n)); printf("%d %Lf\n", n, logl(n)); } ltrace

Bug#1094581: coreutils: numfmt: --invalid!=abort --suffix strips suffix

2025-01-28 Thread наб
Package: coreutils Version: 9.4-3 Version: 9.1-1 Severity: normal Dear Maintainer, $ numfmt --invalid=fail --suffix QWE 12q3QWE 123 numfmt: invalid suffix in input: ‘12q3’ 12q3 123QWE Same for warn/ignore. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (5

Bug#881437: aggregate can't handle all CIDR input correctly

2025-01-27 Thread наб
Actually nevermind, it explicitly supports a short format: /* a -- 32 bits */ /* a.b -- 8.24 bits */ /* a.b.c -- 8.8.16 bits */ /* a.b.c.d -- 8.8.8.8 bits */ so $ echo 10.0.65280/24 | ./aggregate -q 10.0.255.0/24 and calls it /* * Internet format: * a.b.c.d

Bug#1094428: ITS: aggregator

2025-01-27 Thread наб
Source: aggregate Severity: important X-Debbugs-Cc: Package Salvaging Team Dear Maintainer, I'm interested in salvaging your package aggregate, in accordance with the Package Salvaging procedure outlined in the Developers Reference[1]. Your package meets the criteria for this process, and I woul

Bug#881437: aggregate can't handle all CIDR input correctly

2025-01-27 Thread наб
Control: severity -1 wishlist On Sat, Nov 11, 2017 at 07:45:05PM +0100, Lonesome Walker wrote: > Consider this as a bug, since 176.31.188/22 is a valid CIDR. I don't actually see any short output here, it's all in 0.0.0.0/0 format. Reseveritying to wishlist since aggregate(1) doesn't claim to par

Bug#1094388: coreutils: numfmt: parses floats with no LC_NUMERIC=POSIX fallback

2025-01-27 Thread наб
Package: coreutils Version: 9.1-1 Version: 9.4-3 Severity: normal Dear Maintainer, $ LC_NUMERIC=pl_PL.UTF-8 seq 100,100 0.1 100.200 100,1 100,2 $ LC_NUMERIC=pl_PL.UTF-8 numfmt 100,100 0.1 100.200 100,100 numfmt: invalid suffix in input: ‘0.1’ $ LC_NUMERIC=ps_AF.UTF-8 seq 100$(printf '\u066B')100

  1   2   3   4   5   6   7   8   9   >