« Return to Thread: 15 packages have bad SHA1 checksums

Re: 15 packages have bad SHA1 checksums

by John Marino-9 :: Rate this Message:

| View in Thread

On 5/18/2012 08:51, John Marino wrote:

> The following 15 packages need to have distinfo files fixed:
>
> camlimages-4.0.1nb8/checksum.log:29:checksum:
>      mismatch for camlimages-4.0.1/v4.0.1.tar.gz
> cgal-3.9nb4/checksum.log:3:checksum:
>      mismatch for CGAL-3.9.tar.gz
> dnscheck-1.2.6/checksum.log:29:checksum:
>      mismatch for dotse-dnscheck-1.2.6-0-g86a5c69.tar.gz
> fityk-0.9.7nb5/checksum.log:29:checksum:
>      mismatch for fityk-0.9.7.tar.bz2
> gitolite-2.2/checksum.log:3:checksum:
>      mismatch for sitaramc-gitolite-v2.2-0-g15b17d7.tar.gz
> jabberd-2.2.16/checksum.log:3:checksum:
>      mismatch for jabberd-2.2.16.tar.gz
> libcarddav-0.6.2.2.2nb2/checksum.log:3:checksum:
>      mismatch for libcarddav_0.6.2-2debian2.tar.gz
> libdesktop-agnostic-0.3.92nb2/checksum.log:3:checksum:
>      mismatch for libdesktop-agnostic-0.3.92.tar.gz
> librecad-1.0.0nb3/checksum.log:3:checksum:
>      mismatch for LibreCAD-LibreCAD-v1.0.0-0-g22839a7.zip
> percona-toolkit-2.0.4/checksum.log:30:checksum:
>      mismatch for percona-toolkit-2.0.4.tar.gz
> pyXX-html2text-3.02/checksum.log:3:checksum:
>      mismatch for aaronsw-html2text-3.02-0-gd9bf7d6.tar.gz
> ricty-ttf-3.2.0/checksum.log:3:checksum:
>      mismatch for yascentur-Ricty-3.2.0-0-gb9d8b9c.tar.gz.tar.gz
> tahoe-lafs-1.9.1nb1/checksum.log:3:checksum:
>      mismatch for allmydata-tahoe-1.9.1.tar.bz2
> tor-0.2.2.35/checksum.log:3:checksum:
>      mismatch for tor-0.2.2.35.tar.gz
> youtube-dl-20120108bnb1/checksum.log:3:checksum:
>      mismatch for youtube-dl-20120108b/youtube-dl
>
> John


All 15 of these have the curl dependency in common.  They all failed
within the pbulk script inside a chroot.  When I deleted all the source
files and used "bmake checksum" to pull them again, they all passed.

1) So there is no problem with the distfile of 15 packages
2) Is Curl really required for these?  Why not just use the regular
fetch mechanism?
3) Why would the curl fetch fail within the pbulk run?  Everything else
seems to be working well (11,300+ passes on last run).

John




 « Return to Thread: 15 packages have bad SHA1 checksums