View previous topic :: View next topic |
Author |
Message |
smokyrun n00b

Joined: 26 Dec 2023 Posts: 69 Location: Reunion Island
|
Posted: Sat May 17, 2025 10:19 am Post subject: Digest verification failed [SOLVED] |
|
|
Hello All,
I try to update my nordvpn package but I get this error message :
Code: | [ebuild U ~] net-vpn/nordvpn-3.20.2::nordvpn [3.20.1::nordvpn] 0 KiB
Total: 1 package (1 upgrade), Size of downloads: 0 KiB
Would you like to merge these packages? [Yes/No] yes
>>> Verifying ebuild manifests
!!! Digest verification failed:
!!! /var/db/repos/nordvpn/net-vpn/nordvpn/nordvpn-3.20.2.ebuild
!!! Reason: Failed on BLAKE2B verification
!!! Got: f36cb8970ea0578969a9d35397c7549c4cbd812253cfb37e5c7883956cef9eaf9e1620dc5d02ba98ebccc8f4c75f8e0ab6e8eeb9baadfd18e219ed6c049bf736
!!! Expected: 8b039edd54aa9c993ccb2dd893445dd964e2c92361ee33bf67cbfce45514e7701e0402fb05af99a48ee9499b816a83ef8c924f692fe218800f05ca8db87dc526
|
The sync of the nordvpn repository is OK:
Code: |
emaint sync --repo nordvpn
>>> Syncing repository 'nordvpn' into '/var/db/repos/nordvpn'...
/usr/bin/git fetch origin --depth 1
remote: Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
/usr/bin/git reset --hard refs/remotes/origin/master
HEAD is now at 5292572 2025-05-11 07:39:39 UTC
=== Sync completed for nordvpn
* Copying old database to /var/cache/eix/previous.eix
* Running eix-update
Reading Portage settings...
Building database (/var/cache/eix/portage.eix)...
[0] "gentoo" /var/db/repos/gentoo (cache: metadata-md5-or-flat)
Reading category 173|173 (100) Finished
[1] "nordvpn" /var/db/repos/nordvpn (cache: parse|ebuild*3.0.24#metadata-md5#metadata-flat#assign)
Reading category 173|173 (100) Finished
Applying masks...
Calculating hash tables...
Writing database file /var/cache/eix/portage.eix...
Database contains 19092 packages in 173 categories
Action: sync for repo: nordvpn, returned code = 0
|
I removed the ebuild in /var/db/repos/nordvpn/net-vpn/nordvpn and resynced again the repository but the error persist.
I understand that the BLAKE2B checksum of the ebuild is different that expecting.
How can I fix this issue ?
Thank you in advance for your help.
Kind regards,
Smokyrun
Last edited by smokyrun on Sat May 17, 2025 1:31 pm; edited 2 times in total |
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55256 Location: 56N 3W
|
Posted: Sat May 17, 2025 11:57 am Post subject: |
|
|
smokyrun,
Mirror updates are not atomic, if you hit the mirror at the same time as its updating this happens.
It's a feature of non atomic updates. Sync again.
It may be that the maintainer didn't update the digest. That's a bug.
If that happened, the sync above will not fix it.
You can force the digest to match, which removes a safety/security feature of portage.
If effect you are saying you know better than portage and everything is really ok.
To do that run Code: | ebuild /full/path/to/ebuild/file digest |
Better to report the bug and wait for a fix. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
smokyrun n00b

Joined: 26 Dec 2023 Posts: 69 Location: Reunion Island
|
Posted: Sat May 17, 2025 1:26 pm Post subject: |
|
|
Hello NeddySeagoon,
Thank you so much for your help and your explanations, I understand better now.
Very interessting this command Code: | ebuild /var/db/repos/nordvpn/net-vpn/nordvpn/nordvpn-3.20.2.ebuild digest |
I succeeded to upgrade my nordvpn package.
Now everything is ok on my system.
Have a nice day.
Kind regards,
smokyrun |
|
Back to top |
|
 |
Hu Administrator

Joined: 06 Mar 2007 Posts: 23449
|
Posted: Sat May 17, 2025 2:08 pm Post subject: |
|
|
Prior to overriding the digest check, how did you determine that the incorrect digest is a spurious error? Did you report this to the NordVPN overlay maintainer, or find evidence that someone else already reported it? If not, your next sync will likely reset you to the mismatched digest. |
|
Back to top |
|
 |
smokyrun n00b

Joined: 26 Dec 2023 Posts: 69 Location: Reunion Island
|
Posted: Mon May 19, 2025 4:01 pm Post subject: |
|
|
Hello Hu,
Thank you for your reply, I've just send an email to NordVPN overlay maintainer, as I overrided the digest check how can I be sure now that my NordVPN respository contents the good checksum for next synchronisations ?
Kind regards,
smokyrun |
|
Back to top |
|
 |
Hu Administrator

Joined: 06 Mar 2007 Posts: 23449
|
Posted: Mon May 19, 2025 4:13 pm Post subject: |
|
|
Synchronizing will, by definition, reset your files to what the overlay provides. If what the overlay maintainer provides is wrong, then yes, synchronizing will get you a bad checksum. |
|
Back to top |
|
 |
smokyrun n00b

Joined: 26 Dec 2023 Posts: 69 Location: Reunion Island
|
Posted: Mon May 19, 2025 4:41 pm Post subject: |
|
|
The maintainer have just confirmed to me that the overlay is wrong because he omitted to tell the merge of the source branch to the main branch of the Gitlab environnment.
Kind regards,
smokyrun |
|
Back to top |
|
 |
|