When skysentials-1.0.1-python26.patch was committed to the tree, cvs changed the file; a line # $Id: skysentials.py 141 2007-11-22 17:42:53Z pkolmann $ became # $Id: skysentials-1.0.1-python26.patch,v 1.2 2009/09/20 17:46:27 darkside Exp $ Thus, the patch fails, and emerge fails. Manually reverting the line in the local portage tree and re-digesting the file solves the problem. See bug 280372 for the background / history. grenadine ~ # ebuild /usr/portage/net-im/skysentials/skysentials-1.0.1-r1.ebuild unpack * skysentials-1.0.1.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking skysentials-1.0.1.tar.gz ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking skysentials-1.0.1.tar.gz to /var/tmp/portage/net-im/skysentials-1.0.1-r1/work * Applying skysentials-1.0.1-python26.patch ... * Failed Patch: skysentials-1.0.1-python26.patch ! * ( /usr/portage/net-im/skysentials/files/skysentials-1.0.1-python26.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/net-im/skysentials-1.0.1-r1/temp/skysentials-1.0.1-python26.patch-11979.out
Sorry for dragging on this one. Quite embarrassing. Fixed now I do believe.
