Paludis: failed SHA512 on all packages

Message

are · Post by **are** » Sat Feb 23, 2013 1:05 am

Dear All,

since the last upgrade paludis/cave fails verification of all files, e.g.

Checking 'google-chrome-beta_25.0.1364.97-r183676_amd64.deb'... failed SHA512
Checking 'google-chrome-libudev-0.13.1-amd64.tar.xz'... failed SHA512

I deleted the content of /var/paludis/dist and resynched several times already, nothing helped. Furthermore PORTAGE works at the same time well with the same packages/manifests.

Please do you have any idea?

Best regards!

are · Post by **are** » Tue Feb 26, 2013 4:19 am

Update on that: I solved it partially by re-installing paludis using portage:

Code: Select all

emerge paludis

After re-installing paludis/cave and sha512-verification worked again -- until I did a new

Code: Select all

cave resolve installed-packages -x

which broke sha512-verification again!

Hypnos · Post by **Hypnos** » Tue Feb 26, 2013 5:39 am

FWIW, I cannot reproduce your problem -- the checksums are found valid on my machine with paludis-1.0.0 .

You might want to ask the Paludis developers.

are · Post by **are** » Sat Apr 06, 2013 9:35 am

The problem still exists, even after installing paludis-1.2.0.

If I build paludis with "emerge -1 paludis", it it will work and after I can build all other packages with"cave resolve ...".
If I build paludis with "cave resolve paludis -x1", it will work BUT AFTER I can not build anything with "cave resolve ..." as check-sums are found invalid.

Hypnos · Post by **Hypnos** » Sat Apr 06, 2013 10:42 am

Hmmm ... I am also using paludis-1.2.0, which was installed using paludis-1.0.0 -- no problems.

Of course, your choice of package manager should have no effect on the function of the package that was installed with it. All Portage and Paludis do are calculate package dependencies, then execute some scripts with some additional sanity checks. Your bug is very strange.

If you are serious about solving the problem you should inquire to the Paludis developers.