FS#79226 - [python-yaml] checksum mismatch
Attached to Project:
Arch Linux
Opened by Xeonacid (Xeonacid) - Friday, 28 July 2023, 08:29 GMT
Last edited by David Runge (dvzrv) - Friday, 28 July 2023, 22:13 GMT
Opened by Xeonacid (Xeonacid) - Friday, 28 July 2023, 08:29 GMT
Last edited by David Runge (dvzrv) - Friday, 28 July 2023, 22:13 GMT
|
Details
Description:
==> Building in chroot for [extra] (x86_64)... ==> Synchronizing chroot copy [/var/lib/archbuild/extra-x86_64/root] -> [xeonacid]...done ==> Making package: python-yaml 6.0.1-1 (Fri Jul 28 10:25:42 2023) ==> Retrieving sources... -> Downloading PyYAML-6.0.1.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 117k 0 117k 0 0 216k 0 --:--:-- --:--:-- --:--:-- 216k ==> Validating source files with sha512sums... PyYAML-6.0.1.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Could not download sources. A patch is in attachment. |
This task depends upon
Closed by David Runge (dvzrv)
Friday, 28 July 2023, 22:13 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with python-yaml 6.0.1-2
Friday, 28 July 2023, 22:13 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with python-yaml 6.0.1-2
Hmm, this is major weird. I have a tarball from 2023-07-26 that has the checksums as described in the PKGBUILD.
The only difference seems to be that my tarball has different ownership on the contained files (`runner:docker` instead of `root:root`).
I'll get in touch with upstream to clarify this.