| View previous topic :: View next topic |
| Author |
Message |
dspahn
Guru
Joined: 22 Jun 2006
Posts: 392
|
 Posted: Thu Nov 12, 2015 3:02 pm Post subject: [Solved] llvm 3.5 digest verificaiton failure |
 |
|
Is there a fix for this?
| Code: | localhost RaspberryPi2B # emerge -av llvm
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] sys-devel/llvm-3.5.0:0/3.5::gentoo USE="libffi ncurses static-analyzer xml -clang -debug -doc -gold -libedit -multitarget -ocaml -python {-test}" PYTHON_TARGETS="python2_7 (-pypy)" VIDEO_CARDS="(-radeon)" 11496 KiB
Total: 1 package (1 new), Size of downloads: 11496 KiB
Would you like to merge these packages? [Yes/No] yes
>>> Verifying ebuild manifests
!!! Digest verification failed:
!!! /usr/portage/sys-devel/llvm/ChangeLog
!!! Reason: Filesize does not match recorded size
!!! Got: 9711
!!! Expected: 9414
|
trying to install on RPi2B Arm7A. Any ideas?
edit: Thanks to anyone who read this. I deleted the changelog file and the distfiles for the package then ran emerge -av sys-devel/llvm and it got past the point of failure. It's working now so I've marked this as solved.
Thanks again! |
|
| Back to top |
|
 |
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Thu Nov 12, 2015 3:19 pm Post subject: |
|
|
There's two ways: secure and insecure.
secure: resync your tree and see if error disappears.
insecure: force your tree to accept this file.
| Code: | cd /usr/portage/sys-devel/llvm
ebuild "any_ebuild_that_is_in_the_directory" manifest
|
"any_ebuild_that_is_in_the_directory" : is any ebuild file you will see in that directory, something you can get easy with "ls *.ebuild" and should logically start with llvm
If it's only a problem with a Changelog, of course the "insecure" way is not totally insecure, as Changelog is a text file you would certainly never use. |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1464
Location: Berlin, Germany
|
| Posted: Thu Nov 12, 2015 4:42 pm Post subject: |
|
|
I have been re-syncing all afternoon, and keep getting digest verification failures:
| Code: | >>> Verifying ebuild manifests
!!! Digest verification failed:
!!! /usr/portage/app-text/iso-codes/ChangeLog
!!! Reason: Filesize does not match recorded size
!!! Got: 4195
!!! Expected: 4014
!!! Digest verification failed:
!!! /usr/portage/dev-util/gtk-update-icon-cache/ChangeLog
!!! Reason: Filesize does not match recorded size
!!! Got: 5071
!!! Expected: 4874
!!! Digest verification failed:
!!! /usr/portage/dev-libs/libxml2/ChangeLog
!!! Reason: Filesize does not match recorded size
!!! Got: 5221
!!! Expected: 5038
!!! Digest verification failed:
!!! /usr/portage/dev-util/gdbus-codegen/ChangeLog
!!! Reason: Filesize does not match recorded size
!!! Got: 3722
!!! Expected: 3535
!!! Digest verification failed:
!!! /usr/portage/dev-libs/libcroco/ChangeLog
!!! Reason: Filesize does not match recorded size
!!! Got: 3037
!!! Expected: 2856
!!! Digest verification failed:
!!! /usr/portage/dev-python/pygobject/ChangeLog
!!! Reason: Filesize does not match recorded size
!!! Got: 4347
!!! Expected: 4164
!!! Digest verification failed:
!!! /usr/portage/dev-python/cryptography/ChangeLog
!!! Reason: Filesize does not match recorded size
!!! Got: 8694
!!! Expected: 7914
!!! Digest verification failed:
!!! /usr/portage/net-misc/modemmanager/ChangeLog
!!! Reason: Filesize does not match recorded size
!!! Got: 3913
!!! Expected: 3727
|
Is this maybe some issue with switching to Git? Something else wrong with the portage tree? I've synced to several different rsync servers; I'm not seeing the issue go away.
Cheers,
EE |
|
| Back to top |
|
|
dspahn
Guru
Joined: 22 Jun 2006
Posts: 392
|
| Posted: Fri Nov 13, 2015 8:14 pm Post subject: Me Too... |
|
|
I had the one file cause a problem, as in the original post. It was just a changelog, so I deleted it- Worst case scenario I have to delete and rebuild the /usr/portage tree from a tarball...
Everything started merging again, until I had to quit the process (I had a package that wouldn't merge, so I shut the computer down when it died).
Later on, I had the computer at home, and without running emerge --sync, I simply ran | Code: | | emerge -av kde-meta |
I had 20+ more of the same failures- all of them on the ChangeLog file for their respective package.
A few notes:
All except for the last 2 of ExecutorElassus' packages were on my list of problematic packages... obviously there were quite a few more, but my emerge was 488 packages.
@EE: I did some reading on this- according to official Getoo sources, resyncing the tree in response to this problem is likely to make the problem worse, not better. |
|
| Back to top |
|
|
|
Gentoo on Alternative Architectures
