updating katepart from 4.8 to 4.8.1 fails with the following msg: mv: cannot stat `kate-4.8.1/': No such file or directory this blocks the entire kde 4.8.1 upgrade Reproducible: Always
Created attachment 304663 [details] build.log
Created attachment 304697 [details] creffett build.log emerges successfully for me, though it throws a few warnings about missing files at the start of the emerge: tar: kate-4.8.1/cmake: Not found in archive tar: kate-4.8.1/ConfigureChecks.cmake: Not found in archive tar: kate-4.8.1/doc/part: Not found in archive attached successful build.log
(In reply to comment #2) > Created attachment 304697 [details] > creffett build.log > > emerges successfully for me, though it throws a few warnings about missing > files at the start of the emerge: > tar: kate-4.8.1/cmake: Not found in archive > tar: kate-4.8.1/ConfigureChecks.cmake: Not found in archive > tar: kate-4.8.1/doc/part: Not found in archive > attached successful build.log for you it works, for me something is seriously wrong, kde-base/kfmclient fails with similar issue, tried to remove the tar files, dl from another location, removing the tmp folder, all fails. see: >>> Emerging (1 of 173) kde-base/kfmclient-4.8.1 * kde-baseapps-4.8.1.tar.xz RMD160 SHA1 SHA256 size ;-) ... [ ok ] >>> Unpacking source... * Unpacking parts of kde-baseapps-4.8.1.tar.bz2 to /var/tmp/portage/kde-base/kfmclient-4.8.1/work ... tar extract command failed at least partially - continuing anyway mv: cannot stat `kde-baseapps-4.8.1/': No such file or directory * ERROR: kde-base/kfmclient-4.8.1 failed (unpack phase): * Died while moving "kde-baseapps-4.8.1/" to "kfmclient-4.8.1" * * Call stack: * ebuild.sh, line 85: Called src_unpack * environment, line 3936: Called kde4-meta_src_unpack * environment, line 3206: Called kde4-meta_src_extract * environment, line 3146: Called die * The specific snippet of code: * mv ${topdir} ${P} || die "Died while moving \"${topdir}\" to \"${P}\""; * * If you need support, post the output of 'emerge --info =kde-base/kfmclient-4.8.1', * the complete build log and the output of 'emerge -pqv =kde-base/kfmclient-4.8.1'. * This ebuild used the following eclasses from overlays: * /var/lib/layman/kde/eclass/kde4-meta.eclass * /var/lib/layman/kde/eclass/kde4-base.eclass * /var/lib/layman/kde/eclass/kde4-functions.eclass * The complete build log is located at '/var/log/portage/kde-base:kfmclient-4.8.1:20120309-062518.log'. * The ebuild environment file is located at '/var/tmp/portage/kde-base/kfmclient-4.8.1/temp/environment'. * S: '/var/tmp/portage/kde-base/kfmclient-4.8.1/work/kfmclient-4.8.1'
seems to have found the issue, from the log: Unpacking parts of kate-4.8.1.tar.bz2 to /var/tmp/portage/kde-base/katepart-4.8.1/work ... but: dagg@NCC-5001-D ~ $ ll /usr/portage/distfiles/kate-4.8.1.tar* -rw-r--r-- 1 root root 2031068 Mar 9 08:22 /usr/portage/distfiles/kate-4.8.1.tar.xz why does the ebuild searches for tar.bz2 when it downloads tar.xz? is it an eclass issue?
as I'm using kde overlay for kdevelop, I needed to sync with the overlay.
