[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#662080: marked as done (RFP: hadori -- Hardlinks identical files)

Your message dated Tue, 02 May 2017 08:00:10 +0000
with message-id <E1d5SjC-0003Ka-L5@fasolo.debian.org>
and subject line Bug#662080: fixed in hadori 1.0-1
has caused the Debian Bug report #662080,
regarding RFP: hadori -- Hardlinks identical 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 owner@bugs.debian.org
immediately.)


-- 
662080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662080
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org

   Package name: hadori
        Version: 0.2
Upstream Author: Timo Weingärtner <timo@tiwe.de>
            URL: https://github.com/tiwe-de/hadori
        License: GPL3+
    Description: Hardlinks identical files
 This might look like yet another hardlinking tool, but it is the only one
 which only memorizes one filename per inode. That results in less merory
 consumption and faster execution compared to its alternatives. Therefore
 (and because all the other names are already taken) it's called
 "HArdlinking DOne RIght".
 .
 Advantages over other hardlinking tools:
  * predictability: arguments are scanned in order, each first version is kept
  * much lower CPU and memory consumption
  * hashing option: speedup on many equal-sized, mostly identical files

The initial comparison was with hardlink, which got OOM killed with a hundred 
backups of my home directory. Last night I compared it to duff and rdfind 
which would have happily linked files with different st_mtime and st_mode.

I need a sponsor. I'll upload it to mentors.d.n as soon as I get the bug 
number.


Greetings
Timo

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
--- Begin Message --- 
Source: hadori
Source-Version: 1.0-1

We believe that the bug you reported is fixed in the latest version of
hadori, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 662080@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Weingärtner <timo@tiwe.de> (supplier of updated hadori package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 30 Apr 2017 14:15:34 +0200
Source: hadori
Binary: hadori
Architecture: source amd64
Version: 1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Timo Weingärtner <timo@tiwe.de>
Changed-By: Timo Weingärtner <timo@tiwe.de>
Description:
 hadori     - Hardlinks identical files
Closes: 662080
Changes:
 hadori (1.0-1) unstable; urgency=medium
 .
   * Add Homepage: and Vcs-* to debian/control
   * Add debian/watch
   * Add Vcs branch spec to comply with Poicy 3.9.4
   * New upstream release 1.0.
   * move references away from github
   * bump dh compat, policy and copyright years
   * enable more buildflags
   * Upload to debian. Closes: #662080.
Checksums-Sha1:
 12c20cc0002ed15d3456f04b1f091b6d82bf0e5d 1813 hadori_1.0-1.dsc
 f960abaab0ccdfffb2e1d21a3f205cf9d3a93f5c 17366 hadori_1.0.orig.tar.gz
 ccfa653877eedf334eaf17522cc2dd66e2aeed25 2076 hadori_1.0-1.debian.tar.xz
 a06cafb41c56c64f3bb2e9f5d5dd47f590610e53 319718 hadori-dbgsym_1.0-1_amd64.deb
 8dde9865439849419ed8f476d2c106a6a32a2711 6223 hadori_1.0-1_amd64.buildinfo
 b0c48186683e5ad516b56277abb876188abd5241 33016 hadori_1.0-1_amd64.deb
Checksums-Sha256:
 119a1815b93ec3f1e4321571ffff93935e3e9bbf256539ca01130f5b4de4e9da 1813 hadori_1.0-1.dsc
 8ca277b0c516fd2171776aefededcab16cbf041550a98b453d34c45b15fdcb14 17366 hadori_1.0.orig.tar.gz
 5afb84a7bf19d65c088f2d5c375e775bbe1c63421a9a17456963a6a521b368c5 2076 hadori_1.0-1.debian.tar.xz
 fc2dda388146d1d9e2de383ba928e4c54dd433752ab62501535e711bc11b56fc 319718 hadori-dbgsym_1.0-1_amd64.deb
 4901e38e98ec37149fde1bed9ab1eb7b83ed87103510edd2929e53be8d46d8f8 6223 hadori_1.0-1_amd64.buildinfo
 a2df91b72b1ad723f05f2b1435a9b6ad25822f84247a1f165bd8a3373430afc6 33016 hadori_1.0-1_amd64.deb
Files:
 8d5ac03dfadc8433db8ded98592b468b 1813 utils extra hadori_1.0-1.dsc
 a2c9334ca800dc23816eefc82a268bb3 17366 utils extra hadori_1.0.orig.tar.gz
 4a17d5053b29ba0f218753e144c87bf4 2076 utils extra hadori_1.0-1.debian.tar.xz
 5ed41ce4aae5220103079510d17cf27b 319718 debug extra hadori-dbgsym_1.0-1_amd64.deb
 1d912eb6590bd6e636cafbae2cc91bd2 6223 utils extra hadori_1.0-1_amd64.buildinfo
 290a2e7085a3ef0bc15981feca7d5e54 33016 utils extra hadori_1.0-1_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE87+TxUS8xnavTxo5VO6rSJSm4+0FAlkF1m4ACgkQVO6rSJSm
4+2ccRAAn/oYQO8l1Dh3i48fnfhjehRRpvNo9y8/f2GrHIV6b7Ua4tMIN1UV6mxF
rOWRfzentYmqLUKjhYG5THOTBrb/0EJi2IqqVwRUhtc5GEl346GGRJ1Tz2PkqGCV
0112aDXmNQ1eFVB3h2Gn8n4xUM4wQdy1xS8s3uSSeTRnLlrRFEnGITk1HYfyUORb
dPECHjSBZKojM45V0Lc0gtAQPoGs2VHYNqDzsjWkMOXwUl1aq0RV/oz9CIwUEX7S
pq00ptdg8rZUFcZTo37MO8KaS79csqpjuea4gR55MyevZqwfNki6cOVWX/q2wA1W
hQm07LYWTN/i5q0IbQFSJsvXv8nPOPD4LyGIlWjxOgf/XK/GynyCs1vUr+XoFNi9
I6MSRMgR3eQGV7WAlT2MMyly3waZHYnnyVVEG4trIy89Xl1i7iUeITf5++UwJDcM
5y5OWDyklSN4WRZ75x33lhn88Hrh9VvzzoVPRCATpIk5Fc6pyZbNBMOFVmwU+ZGi
ZVjY0YiQcyWioWERNvomQi1p82CQl4VCUJ3tZ7+eoQZW/m10gIFOmuNifuNAmbo9
Zl+FuNrYlnNd5ljEzrH6a0tAqItGOnVHtS0Deu5rtwja2FSiqcLUZyisdhKUwehH
edYOc0Kk1YD0Ad6cQCf8C11aSU+dXhihsOf0JdOjcqcGvJd+BSQ=
=CKMg
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: