>>> Unpacking source... * Unpacking parts of kdebase-4.4.2.tar.bz2 to /var/tmp/portage/kde-base/kdialog-4.4.2/work ... tar -xpf /var/tmp/portage/kde-base/kdialog-4.4.2/distdir/kdebase-4.4.2.tar.bz2 --bzip2 --transform=s|apps/|| kdebase-4.4.2/apps/cmake/ kdebase-4.4.2/apps/CMakeLists.txt kdebase-4.4.2/apps/ConfigureChecks.cmake kdebase-4.4.2/apps/config.h.cmake kdebase-4.4.2/apps/AUTHORS kdebase-4.4.2/apps/COPYING kdebase-4.4.2/apps/INSTALL kdebase-4.4.2/apps/README kdebase-4.4.2/apps/NEWS kdebase-4.4.2/apps/ChangeLog kdebase-4.4.2/apps/kdialog kdebase-4.4.2/apps/config-apps.h.cmake kdebase-4.4.2/apps/ConfigureChecks.cmake mv: rename kdebase-4.4.2/ to kdialog-4.4.2: No such file or directory * ERROR: kde-base/kdialog-4.4.2 failed: * Died while moving "kdebase-4.4.2/" to "kdialog-4.4.2" * * Call stack: * ebuild.sh, line 48: Called src_unpack * environment, line 4205: Called kde4-meta_src_unpack * environment, line 3395: Called kde4-meta_src_extract * environment, line 3336: Called die * The specific snippet of code: * mv ${topdir} ${P} || die "Died while moving \"${topdir}\" to \"${P}\""; * # tar -xpf /var/tmp/portage/kde-base/kdialog-4.4.2/distdir/kdebase-4.4.2.tar.bz2 --bzip2 --transform=s|apps/|| kdebase-4.4.2/apps/cmake/ kdebase-4.4.2/apps/CMakeLists.txt kdebase-4.4.2/apps/ConfigureChecks.cmake kdebase-4.4.2/apps/config.h.cmake kdebase-4.4.2/apps/AUTHORS kdebase-4.4.2/apps/COPYING kdebase-4.4.2/apps/INSTALL kdebase-4.4.2/apps/README kdebase-4.4.2/apps/NEWS kdebase-4.4.2/apps/ChangeLog kdebase-4.4.2/apps/kdialog kdebase-4.4.2/apps/config-apps.h.cmake kdebase-4.4.2/apps/ConfigureChecks.cmake -bash: apps/: No such file or directory tar: Option --transform=s is not supported Usage: List: tar -tf <archive-filename> Extract: tar -xf <archive-filename> Create: tar -cf <archive-filename> [filenames...] Help: tar --help -bash: kdebase-4.4.2/apps/cmake/: No such file or directory better transform the files using sed on directly the paths imho
Indeed. This is in kde4-meta.eclass, so the problem is a bit more general: 222 case ${KMNAME} in 223 kdebase-apps) 224 # kdebase/apps -> kdebase-apps 225 tarball="kdebase-${PV}.tar.${postfix}" 226 # Go one level deeper for kdebase-apps in tarballs 227 moduleprefix=apps/ 228 KMTARPARAMS+=" --transform=s|apps/||" 229 ;;
Unfortunately modular unpacking mechanism is quite complex and sed-ing paths doesn't seem straighforward at all. I'd avoid messing there. Of course patches welcome.
Alternatively, can gnu tar be installed on bsd, and if yes, can we add it to the dependencies and use it there?!
This bug makes kde ebuilds unuseable on BSD. Which basically means they should not have the respective keywords. Given there has been no feedback here, no duplicates, and no further complaints, I can only assume that nobody is even trying to run that combination. So, I'd recommend dropping bsd keywords from the next kde release on. Any thoughts?
several things: - this bug made ebuilds with KMNAME=kdebase-apps unusable, not all - from what I can see in the eclass, this code wont be hitten with 4.6.1, so you fixed it yourself ? - iirc you can use gnu tar on bsd but its called gtar - i dont understand why KMNAME cannot be set to kdebase/apps from the beginning (discard this remark if its going to be like the 2nd point from now on) - considering i dont have a bsd box anymore, you can remove the keyword if you want. I was in the middle of keywording most of it but i hit this bug and it hasnt been fixed/responded with a proposal before I had to move and leave the box somewhere in the corner of a garage. - if you drop the keywords and i ever go back to do bsd stuff, i'll most likely refrain from keywording anything kde related because i dont like doing twice the same (boring) work - you can use some kde stuff outside of a kde desktop, so the keywords arent totally useless as they are.
(In reply to comment #5) > - this bug made ebuilds with KMNAME=kdebase-apps unusable, not all Correct > - from what I can see in the eclass, this code wont be hitten with 4.6.1, so > you fixed it yourself ? No, upstream decided to change how it was laying out its tarballs as of 4.6.1 > - i dont understand why KMNAME cannot be set to kdebase/apps from the beginning KMNAME is used to determine what the name of the tarball itself is (in this case, kdebase-apps-${PV}.tar.bz2) as well what directory to search.
(In reply to comment #6) > (In reply to comment #5) > > - this bug made ebuilds with KMNAME=kdebase-apps unusable, not all > > Correct > > > - from what I can see in the eclass, this code wont be hitten with 4.6.1, so > > you fixed it yourself ? > > No, upstream decided to change how it was laying out its tarballs as of 4.6.1 > if it will remain as such, I think you can close the bug as its fixed :)
> > if it will remain as such, I think you can close the bug as its fixed :) ok thanks for the help! plz reopen if the problem reappears...
*** Bug 363471 has been marked as a duplicate of this bug. ***
