Bug#929816: RFS: simhash/0.0.20161225-1 [ITA] -- generate similarity hashes to find nearly duplicate files
On Sat, Jun 01, 2019 at 01:27:53AM +0800, laokz wrote:
> I am looking for a sponsor for my first package "simhash".
>
> * Package name : simhash
> Version : 0.0.20161225-1
> Changes since the last upload:
>
> * New maintainer. Closes: #652727
> * Upgraded d/* according to Debian Policy 4.3.0.3.
> Priority -> optional, Standards-Version -> 4.3.0, debhelper >= 12,
> update Vcs-* fields, add simple testsuite and watch file,
> remove redundant d/{clean,dirs,lintian-overrides}.
> * Upstream cleaned up buffer signedness warned by gcc. (Git commit fa34436)
Hi!
It's nice to see you taking up this package -- however, this is an upload to
unstable during the freeze. It's generally a bad idea; it would be better
to either use experimental or to wait until Buster is released.
> After packaging, I checked lintian, debdiff .dsc|.deb results, tried
> install/remove/run, and https://tracker.debian.org/pkg/simhash. More
> explanations:
>
> * d/dirs removed: Its content is 'usr/bin' which belongs to FHS.
> * d/simhash.linlian-overrides removed: It contained "no-upstream-
> changelog", which is nonexisted in current lintian version.
> * d/{clean,rules,test/*}: Based on source 'test.sh', the testsuite can
> confirm the build procedure. d/clean is no needed also.
> * d/{watch,source/lintian-overrides}: New version adds a watch file. It is
> not very well but can do work.
It finds some old version for me:
uscan info: Newest version of simhash on remote site is 0.0.20110213, local version is 0.0.20161225
uscan info: => Only older package available from
https://github.com/BartMassey/simhash master
> Another request. I updated Vcs-* fields, but need you help to upload to
> salsa.debian.org/debian/.
(didn't do this yet)
Meow!
--
⢀⣴⠾⠻⢶⣦⠀ Latin: meow 4 characters, 4 columns, 4 bytes
⣾⠁⢠⠒⠀⣿⡁ Greek: μεου 4 characters, 4 columns, 8 bytes
⢿⡄⠘⠷⠚⠋ Runes: ᛗᛖᛟᚹ 4 characters, 4 columns, 12 bytes
⠈⠳⣄⠀⠀⠀⠀ Chinese: 喵 1 character, 2 columns, 3 bytes <-- best!
Reply to: