Bugzilla Bug 191022

# emerge -u numeric
Calculating world dependencies... done!
>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) dev-python/numeric-24.2-r6 to /
 * Numeric-24.2.tar.gz RMD160 ;-) ...                                     [ ok
]
 * Numeric-24.2.tar.gz SHA1 ;-) ...                                       [ ok
]
 * Numeric-24.2.tar.gz SHA256 ;-) ...                                     [ ok
]
 * Numeric-24.2.tar.gz size ;-) ...                                       [ ok
]
 * checking ebuild checksums ;-) ...                                      [ ok
]
 * checking auxfile checksums ;-) ...                                     [ ok
]
 * checking miscfile checksums ;-) ...                                    [ ok
]
 * checking Numeric-24.2.tar.gz ;-) ...                                   [ ok
]
>>> Unpacking source...
>>> Unpacking Numeric-24.2.tar.gz to /var/tmp/portage/dev-python/numeric-24.2-r6/work
 * Applying numeric-24.2-arrayobject.patch ...

 * Failed Patch: numeric-24.2-arrayobject.patch !
 *  ( /usr/portage/dev-python/numeric/files/numeric-24.2-arrayobject.patch )
 *
 * Include in your bugreport the contents of:
 *
 *  
/var/tmp/portage/dev-python/numeric-24.2-r6/temp/numeric-24.2-arrayobject.patch-11569.out

 *
 * ERROR: dev-python/numeric-24.2-r6 failed.
 * Call stack:
 *   ebuild.sh, line 1654:   Called dyn_unpack
 *   ebuild.sh, line 768:   Called qa_call 'src_unpack'
 *   ebuild.sh, line 44:   Called src_unpack
 *   numeric-24.2-r6.ebuild, line 49:   Called epatch
'/usr/portage/dev-python/numeric/files/numeric-24.2-arrayobject.patch'
 *   eutils.eclass, line 304:   Called die
 *
 * Failed Patch: numeric-24.2-arrayobject.patch!
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/tmp/portage/dev-python/numeric-24.2-r6/temp/build.log'.
 *

 * Messages for package dev-python/numeric-24.2-r6:

 * Failed Patch: numeric-24.2-arrayobject.patch !
 *  ( /usr/portage/dev-python/numeric/files/numeric-24.2-arrayobject.patch )
 *
 * Include in your bugreport the contents of:
 *
 *  
/var/tmp/portage/dev-python/numeric-24.2-r6/temp/numeric-24.2-arrayobject.patch-11569.out
 *
 * ERROR: dev-python/numeric-24.2-r6 failed.
 * Call stack:
 *   ebuild.sh, line 1654:   Called dyn_unpack
 *   ebuild.sh, line 768:   Called qa_call 'src_unpack'
 *   ebuild.sh, line 44:   Called src_unpack
 *   numeric-24.2-r6.ebuild, line 49:   Called epatch
'/usr/portage/dev-python/numeric/files/numeric-24.2-arrayobject.patch'
 *   eutils.eclass, line 304:   Called die
 *
 * Failed Patch: numeric-24.2-arrayobject.patch!
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/tmp/portage/dev-python/numeric-24.2-r6/temp/build.log'.
 *

Created an attachment (id=129808) [details]
arrayobject.patch output

Hi Paul,

Thanks for the note and this should be fixed now in portage cvs.
Please give it an hour or so to propagate to the mirrors then
re-sync and try again. Please re-open this bug should you still
have issues.

Best,
Markus

*** Bug 191024 has been marked as a duplicate of this bug. ***

Created an attachment (id=129823) [details]
numeric-24.2-python25.patch output

numeric-24.2-arrayobject.patch applies correctly now, but it fails a little
further on applying the numeric-24.2-python25.patch.

Reopened with updated summary.

(In reply to comment #4)
> numeric-24.2-arrayobject.patch applies correctly now, but it fails a little
> further on applying the numeric-24.2-python25.patch.

As Paul says, that patch fails.

emerge -pv numeric:
[ebuild     U ] dev-python/numeric-24.2-r6 [24.2-r4] USE="-debug -doc -lapack"
0 kB

It looks like the  "dev" (bicatali) touched his copy of the srcfile before
creating the patchfile!!!!

In patchfile: numeric-24.2-python25.patch
It says:
-/* $Id: numeric-24.2-python25.patch,v 1.2 2007/09/01 22:24:30 bicatali Exp $
*/
+/* $Id: numeric-24.2-python25.patch,v 1.2 2007/09/01 22:24:30 bicatali Exp $
*/

Instead of:
-/* $Id: arrayobject.c,v 1.107 2005/11/09 19:43:39 teoliphant Exp $ */
+/* $Id: numeric-24.2-python25.patch,v 1.2 2007/09/01 22:24:30 bicatali Exp $
*/

(In reply to comment #7)
> It looks like the  "dev" (bicatali) touched his copy of the srcfile before
> creating the patchfile!!!!

Nope, CVS fscked-up the $Id with its stupid headers mangling.

maybe slow mirrors, but i didn't see this error message in this bug yet,

>>> Verifying ebuild Manifests...

!!! Digest verification failed:
!!! /mnt/portage/main/dev-python/numeric/files/numeric-24.2-python25.patch
!!! Reason: Filesize does not match recorded size
!!! Got: 7690
!!! Expected: 7000

(In reply to comment #9)
> maybe slow mirrors, but i didn't see this error message in this bug yet,
> 
> >>> Verifying ebuild Manifests...
> 
> !!! Digest verification failed:
> !!! /mnt/portage/main/dev-python/numeric/files/numeric-24.2-python25.patch
> !!! Reason: Filesize does not match recorded size
> !!! Got: 7690
> !!! Expected: 7000
> 

Please re-sync and try again! You probably still have the "old" patch.

Unfortunately, I missed the python-2.5 patch yesterday since I am still
on python-2.4, but bicatali did fix it in the meantime.

Markus

(In reply to comment #10)
> (In reply to comment #9)
> > maybe slow mirrors, but i didn't see this error message in this bug yet,
> > !!! Digest verification failed:
> > !!! /mnt/portage/main/dev-python/numeric/files/numeric-24.2-python25.patch
> 
> Please re-sync and try again! You probably still have the "old" patch.
> 
> Markus

Yeah, everything patched and built fine now.

Works now.