Your message dated Wed, 24 Sep 2025 09:24:59 -0300 with message-id <[email protected]> and subject line Re: jdupes segfaults on too many files has caused the Debian Bug report #1061398, regarding jdupes segfaults on too many files to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1061398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061398 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: jdupes Version: 1.19.1-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Run "jdupes -dN -r ." on a file system with millions of files * What exactly did you do (or not do) that was effective (or ineffective)? See above * What was the outcome of this action? Segfault, program exited * What outcome did you expect instead? Working copy not segfaulting. Old version of jdupes found, as this bug was fixed in jdupes 1.20.x. Note, sources have moved to https://codeberg.org/jbruchon/jdupes -- System Information: Debian Release: 11.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-0.deb11.13-amd64 (SMP w/12 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) Versions of packages jdupes depends on: ii libc6 2.31-13+deb11u7 jdupes recommends no packages. jdupes suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Considering this bug was fixed and it is present in old-old-stable only, I am closing this bug. Regards, Eriberto
--- End Message ---
