Your message dated Mon, 08 Sep 2025 18:15:13 +0000 with message-id <[email protected]> and subject line Bug#1111754: Removed package(s) from unstable has caused the Debian Bug report #314548, regarding perforate: suggestions for speeding up the program 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.) -- 314548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314548 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: perforate Version: 1.1-2 Severity: wishlist For a large directory tree, finddup takes a long time to run. Apparently, it reads every file in the tree. I suggest several ways to reduce the amount of data read from the disk: - The initial scan of the directory tree should record only file size, ownership, and permissions. If there is only one file of a given length, then it has no duplicates and need not be read. - Optionally, ignore small files (where linking would not save much space anyway) - Per bug #263782, if files of a given size all differ in ownership and/or permissions, they need not be read. (Actually I would like the option of ignoring ownership and permissions. In a read-only backup it might be okay to link files with differing ownership and permissions.) - If there are exactly two files of a given size, ownership, and permissions, then use "diff -q" to compare them (so the two files are read only up to the first difference). - If there are more than two files of a given size, then use md5sum to identify probable duplicate files. To guard against false matches, I would advocate checking with "diff -q". In that case, I suggest calculating the md5sum only of the leading part of the file (say, the first 4096 bytes). If differences are found in the leading parts of the files then of course the remainders of the files need not be read. Other users might not insist on the "diff -q" check, in which case the md5sum should of course be calculated on the entire file. Unfortunately, I'm not enough of a perl programmer to provide a patch. - Jim Van Zandt -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.29 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages perforate depends on: ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1.2-6+rm Dear submitter, as the package perforate has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1111754 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Paul Tagliamonte (the ftpmaster behind the curtain)
--- End Message ---
