Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 201821 - dev-python/pycrypto-2.0.1-r6 failed patch
Summary: dev-python/pycrypto-2.0.1-r6 failed patch
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-10 01:43 UTC by BS
Modified: 2007-12-10 07:47 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 BS 2007-12-10 01:43:14 UTC 
PATCH COMMAND:   patch -p0 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-python/pycrypto/files/pycrypto-2.0.1-uint32.patch

=======================================
patching file src/RIPEMD.c
=======================================

ACTUALLY APPLYING pycrypto-2.0.1-uint32.patch ...

=======================================
libsandbox:  Can't resolve open: (null)
ERROR: dev-python/pycrypto-2.0.1-r6 failed.
 * Call stack:
 *                  ebuild.sh, line 1701:  Called dyn_compile
 *                  ebuild.sh, line 1039:  Called qa_call 'src_compile'
 *                  ebuild.sh, line   44:  Called src_compile
 *   pycrypto-2.0.1-r6.ebuild, line   39:  Called distutils_src_compile
 *           distutils.eclass, line   48:  Called die



Reproducible: Always

Actual Results:  
emerge  dev-python/pycrypto

Expected Results:  
same error again
Comment 1 BS 2007-12-10 01:45:40 UTC 
Portage 2.1.3.19 (default-linux/amd64/2007.0, gcc-4.1.1, glibc-2.6.1-r0, 2.6.23-gentoo-r3 x86_64)
=================================================================
System uname: 2.6.23-gentoo-r3 x86_64 Intel(R) Celeron(R) CPU 2.53GHz
Timestamp of tree: Sun, 09 Dec 2007 16:46:01 +0000
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2007-12-10 03:55:27 UTC 
Which mirror did you rsync with? /var/log/emerge.log should tell you the IP address.
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2007-12-10 07:47:06 UTC 
See above and reopen w/ emerge --info, you are using a broken mirror.