thought I d report as found out while doing an emerge world -e. It is reproducable on another gentoo box and in gentoo forum another user reported same behaviour. No urgency for me though but I thought I d report anyway in case its a bug. Reproducible: Always Steps to Reproduce: 1.emerge koffice-i18n Actual Results: >>> Emerging (1 of 1) app-i18n/koffice-i18n-1.6.1 to / * koffice-l10n-de-1.6.1.tar.bz2 RMD160 ;-) ... [ ok ] * koffice-l10n-de-1.6.1.tar.bz2 SHA1 ;-) ... [ ok ] * koffice-l10n-de-1.6.1.tar.bz2 SHA256 ;-) ... [ ok ] * koffice-l10n-de-1.6.1.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking koffice-l10n-de-1.6.1.tar.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking koffice-l10n-de-1.6.1.tar.bz2 to /var/tmp/portage/app-i18n/koffice-i18n-1.6.1/work * Applying koffice-18n-1.6.1-es-fix.diff ... * Failed Patch: koffice-18n-1.6.1-es-fix.diff ! * ( /usr/portage/app-i18n/koffice-i18n/files/koffice-18n-1.6.1-es-fix.diff ) * * Include in your bugreport the contents of: * * /var/tmp/portage/app-i18n/koffice-i18n-1.6.1/temp/koffice-18n-1.6.1-es-fix.diff-14965.out !!! ERROR: app-i18n/koffice-i18n-1.6.1 failed. Call stack: ebuild.sh, line 1614: Called dyn_unpack ebuild.sh, line 751: Called qa_call 'src_unpack' environment, line 4732: Called src_unpack koffice-i18n-1.6.1.ebuild, line 42: Called epatch '/usr/portage/app-i18n/koffice-i18n/files/koffice-18n-1.6.1-es-fix.diff' eutils.eclass, line 341: Called die !!! Failed Patch: koffice-18n-1.6.1-es-fix.diff! !!! 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/app-i18n/koffice-i18n-1.6.1/temp/build.log'.
Created attachment 114550 [details] koffice-18n-1.6.1-es-fix.diff-14965.out
Your problem seems to have been caused by the patch submitted in bug #161197 - please follow the discussion there *** This bug has been marked as a duplicate of bug 161197 ***
I do not understand that, nor did I find a solution in the mentioned bugreport. Need advice how to solve this. Thank you. (Btw. did not add patch myself, just emerged stable version) and thats how I get this error, If I can be of any help on this please tell me how to..
Yep, screwed this one completely - wrong test shell I suppose. :/
Maybe its just me not understanding but why is this one beeing closed with a comment I dont get any sense of ? Resynced and retried. Problem is still there and the mentioned duplicate bug is closed although there are reports there that the problem seems to persist.
re-resynced (last sync mentioned was yesterday) and now it emerges fine. Thanks !
