First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 164320
Alias:
Product:
Component:
Status: RESOLVED
Resolution: DUPLICATE of bug 131293
Assigned To: Portage team <dev-portage@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Esen Kuşluoğlu <esenkweb@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 164320 depends on: Show dependency tree
Bug 164320 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-01-28 21:49 0000
When I try to emerge portage I get digest verification error.



Reproducible: Always

Steps to Reproduce:
1. emerge portage
2.
3.

Actual Results:  
>>> Emerging (1 of 1) sys-apps/portage-2.1.1-r2 to /
 * portage-2.1.1.tar.bz2 MD5 ;-) ...                                      [ ok
]
 * portage-2.1.1.tar.bz2 RMD160 ;-) ...                                   [ ok
]
 * portage-2.1.1.tar.bz2 SHA1 ;-) ...                                     [ ok
]
 * portage-2.1.1.tar.bz2 SHA256 ;-) ...                                   [ ok
]
 * portage-2.1.1.tar.bz2 size ;-) ...                                     [ ok
]
 * portage-2.1.1-r2.patch.bz2 MD5 ;-) ...                                 [ ok
]
 * portage-2.1.1-r2.patch.bz2 RMD160 ;-) ...                              [ ok
]
 * portage-2.1.1-r2.patch.bz2 SHA1 ;-) ...                                [ ok
]
 * portage-2.1.1-r2.patch.bz2 SHA256 ;-) ...                              [ ok
]
 * portage-2.1.1-r2.patch.bz2 size ;-) ...                                [ ok
]
 * checking ebuild checksums ;-) ...                                      [ !!
]

!!! Digest verification failed:
!!! /usr/portage/sys-apps/portage/portage-2.1-r2.ebuild
!!! Reason: Failed on SHA256 verification
!!! Got: 7a1911a8afa416e2feff1658a010b671b9b176dc0c8107080d5fd133558d1d15
!!! Expected: 74bcfc61436bb7312baec85aa3e3a1927258677f02bde909ead47bd0e56232ed

------- Comment #1 From Zac Medico 2007-01-28 22:39:25 0000 -------
Try upgrading pycrypto with FEATURES=-strict.

*** This bug has been marked as a duplicate of bug 131293 ***

First Last Prev Next    No search results available      Search page      Enter new bug