Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 573332 - dev-python/jedi-0.9.0 - ebuild filesize does not match
Summary: dev-python/jedi-0.9.0 - ebuild filesize does not match
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Infrastructure
Classification: Unclassified
Component: Git (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Infrastructure
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-29 21:24 UTC by Nikolaj Šujskij
Modified: 2016-02-02 20:23 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolaj Šujskij 2016-01-29 21:24:18 UTC 
Cannot install dev-python/jedi-0.9.0

 # emerge -av1 --nodeps =dev-python/jedi-0.9.0

These are the packages that would be merged, in order:

[ebuild   R    ] dev-python/jedi-0.9.0::gentoo  USE="doc {-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5%* -python3_3" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB

Would you like to merge these packages? [Yes/No] 
>>> Verifying ebuild manifests

!!! Digest verification failed:
!!! /usr/portage/dev-python/jedi/jedi-0.9.0.ebuild
!!! Reason: Filesize does not match recorded size
!!! Got: 838
!!! Expected: 855
>>> Emerging (1 of 1) dev-python/jedi-0.9.0::gentoo
>>> Jobs: 0 of 1 complete, 1 running                Load avg: 3.13, 1.57, 0.85
!!! Digest verification failed:
!!! /usr/portage/dev-python/jedi/jedi-0.9.0.ebuild
!!! Reason: Filesize does not match recorded size
!!! Got: 838
!!! Expected: 855
>>> Failed to emerge dev-python/jedi-0.9.0

Reproducible: Always
Comment 1 Thomas Capricelli 2016-01-30 01:09:05 UTC 
i can confirm the problem here.

Checking ebuild actual size and manifest:
-rw-r--r-- 1 portage portage  838 Jan 29 05:59 jedi-0.9.0.ebuild

Manifest:EBUILD jedi-0.9.0.ebuild 855 SHA256 f1013f4c9608326ff49db3f8fd0ac1744df693184fbc1362d5994f167260a773 SHA512 a1990f217ccf8752ef49042fc67e5b408e396b68ebb4638cb84074336cf45505fd025c4ce68667cda811ba114d482c5868fe50436c6427d06a706e1d8e3d54e2 WHIRLPOOL beaad0b56d11b22aea4fb579828184cb15137e4545651c00a2ccf48fe11430e9846f5e3a0ed3bd20f9f0aa4cafeded57e34c1fb3ecbe18142cd0f7b65f5c565d

On the other hand, i know there are a bunch of problems with some rsync servers not deleting old files, that could create this kind of bug.
Comment 2 Mateusz Dereniowski 2016-02-02 12:29:03 UTC 
This bug was solved (for me) after today's sync.
Comment 3 Nikolaj Šujskij 2016-02-02 20:06:36 UTC 
Same here.

@Thomas, what about you?
Comment 4 Thomas Capricelli 2016-02-02 20:23:51 UTC 
Perfect from here. Thanks!