search

oddlama / gentoo-install

A gentoo installer with a TUI interface that supports systemd and OpenRC, EFI and BIOS, as well as variable disk layouts using ext4, zfs, btrfs, luks and mdraid.
MIT License
531 stars 72 forks source link

Error: Checksum mismatch #17

Closed manlike3li closed 2 years ago

manlike3li commented 3 years ago

Was doing on Linux Mint xfce:

gpg: Signature made Sun Oct 31 17:41:05 2021 UTC
gpg:                using RSA key 534E4209AB49EEE1C19D96162C44695DB9F6043D
gpg: Good signature from "Gentoo Linux Release Engineering (Automated Weekly Release Key) <releng@gentoo.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 13EB BDBE DE7A 1277 5DFD  B1BA BB57 2E0E 2D18 2910
     Subkey fingerprint: 534E 4209 AB49 EEE1 C19D  9616 2C44 695D B9F6 043D
[+] Verifying tarball integrity

--( Verifying /dev/fd/63 )------------------------------------------------------
stage3-amd64-openrc-20211031T170530Z.tar.xz         ERR
stage3-amd64-openrc-20211031T170530Z.tar.xz         OK 
--------------------------------------------------------------------------------
Errors Occurred: Errors:1   Miss:0   Success:1   Total:2  
error: Checksum mismatch!
oddlama commented 3 years ago

I just tried this on a fresh virtual machine and can't reproduce the error with the same stage3 file. As this is a checksum failure, it is probably just an issue with the upstream checksum file that has already been resolved. Can you check if this error occurs again if you retry the installation?

manlike3li commented 3 years ago

Same thing happened

oddlama commented 3 years ago

Did you start from scratch, or reuse an already cloned version of gentoo-install?

manlike3li commented 3 years ago

I just went to GitHub, downloaded the zip, unzipped the file, went to the configure part and then sudo ./install and then when it downloaded the stage 3 there was a checksum error.

oddlama commented 3 years ago

That's very strange indeed. It might be related to differences in tools in linux mint, so maybe something didn't have the expected parsing output. Could you maybe post the contents of /tmp/gentoo-install/stage3-<something>.DIGESTS.asc after the error occurs?

Can you also clarify whether you are using a Linux Mint live system or a different base system setup?

manlike3li commented 3 years ago

Output: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

BLAKE2 (b2sum) HASH

ccbc68ba3fd9e7cd862e3b0557cb0c6496a4914057e403b30a946c7ca8a0b4f42dbcf54dce54800ea0a7bc7008180a96644568efbcc6783ccf07fd0325cd467f /var/tmp/catalyst/builds/default/stage3-amd64-openrc-20211101T222649Z.tar.xz

SHA512 HASH

0f28dedb3534def343c0ea7ee53603097fcf079e52d3130f4aa38ede7989dff9fdb01c592f69a146d2ce054d7dd00ec1504c25d57f6dc82a1316f71672951f35 stage3-amd64-openrc-20211101T222649Z.tar.xz

BLAKE2 (b2sum) HASH

481b2add0c887e8f9d8e3bb8346990adedfd13cc1b4157ccdd25f7289f7e352a1440d59567c01c4258e77e92d476955d256d7bd1892de44debdc44bc6d70b335 /var/tmp/catalyst/builds/default/stage3-amd64-openrc-20211101T222649Z.tar.xz.CONTENTS.gz

SHA512 HASH

0c319d8df8af25dd13eb011870e04ba43f8e9d16f49a46a38ec6b26ef0b9e100c458215532d9773a849416bf2ce58c33e28727ed3b9a3915d4fb1a7001b9724c stage3-amd64-openrc-20211101T222649Z.tar.xz.CONTENTS.gz -----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEU05CCatJ7uHBnZYWLERpXbn2BD0FAmGAcbIACgkQLERpXbn2 BD1gPwf/QCZNQqtlMEfIXvFoA58m1sNM1s+37gvw3YitBl3IEm4xYLaeTyHR2h57 Dk7JVOZPkP/uaqt/Of3hihBKkn+bb5P+cw4t/yYzy7RG5tn3ILbl0IZrVDqNsAND W+x2S4HHjrl1ox7qi0RIU9ZyNXLkucSeNSTwFg/4a5xShupKAlA2Iyg3Vn0iJK2u R9gZanc8HflZjf/k+LudEQQ111XdG/wKNxqmp1XQNioHrQ3BnleFlTfHBG4MOgob HlsOrJ4eGTT2j4HNqjBQAbrVWm+Ns4u5H8tAuiubKzvoxntOCwVkamS8tQSES832 ybfUHi1wkeMK6SEgGdxe0UK0BA3LXg== =jgX5 -----END PGP SIGNATURE-----

(is using a live usb)

oddlama commented 2 years ago

I just re-checked this configuration in a fresh virtual machine, and with the newest version of gentoo-install everything is working as expected and both verifications pass. Closing this as it seems to be resolved. If you still experience issues, please let me know and I will re-open the issue.