FS#36426 - [scribus] checksum mismatch

Attached to Project: Community Packages
Opened by Eric Belanger (Snowman) - Monday, 05 August 2013, 23:33 GMT
Last edited by Gaetan Bisson (vesath) - Monday, 19 August 2013, 05:32 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

$ makepkg --allsource
==> Making package: scribus 1.4.3-1 (Mon Aug 5 19:21:13 EDT 2013)
==> Retrieving sources...
-> Downloading scribus-1.4.3.tar.xz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0
100 67.2M 100 67.2M 0 0 350k 0 0:03:16 0:03:16 --:--:-- 439k
==> Validating source files with sha1sums...
scribus-1.4.3.tar.xz ... FAILED
==> ERROR: One or more files did not pass the validity check!
This task depends upon

Closed by  Gaetan Bisson (vesath)
Monday, 19 August 2013, 05:32 GMT
Reason for closing:  Fixed
Additional comments about closing:  scribus-1.4.3-2 in [community]
Comment by Gaetan Bisson (vesath) - Tuesday, 06 August 2013, 12:39 GMT
Thanks for noticing. The only explanation I can think of is that upstream "re-released" the same tarball. I would download the new tarball and compare it to the old one but Internet is very flaky and tops at 20 kB/s here so there is not much I can do for another two weeks at least.
Feel free to update the sha1sums, bump the pkgrel, and push a rebuild to the repos if you care enough about this.
Comment by Gaetan Bisson (vesath) - Monday, 19 August 2013, 04:54 GMT
Apparently they re-released the tarball because they messed up the embedded path the first time; it was scribus-1.4.3/scribus-1.4.3/ . Great.

Loading...