Bug 445018 – dev-libs/libnl-3.2.16 - mv "${WORKDIR}"/${PN}-doc-3.2.15 "${WORKDIR}"/${PN}-doc-${PV} - mv: cannot stat '/var/tmp/portage/dev-libs/libnl-3.2.16/work/libnl-doc-3.2.15': No such file or directory

• Status: RESOLVED DUPLICATE of bug 445026
• Product: Gentoo Linux

[Description Kevin 2012-11-28 00:20:17 UTC]

Created attachment 330786 [details]
build log and emerge --info output

emerge libnl-3.2.14 fails due to a file not found error. emerge --sync has been recently performed. 

Failure happens in the libnl-1.1-vlan-header.patch with 'no such file or directory' (filename is libnl-doc-3.2.15)

Manual inspection shows no such file in the package, redownload of source showed no difference.

[Comment 1 Alexander 2012-11-28 11:27:44 UTC]

Same for me

[Comment 2 Tom Wijsman (TomWij) (RETIRED) 2012-11-28 14:19:05 UTC]

> emerge libnl-3.2.14 fails

You have attached the build log for 3.2.16.

> Failure happens in the libnl-1.1-vlan-header.patch with 'no such file or directory' (filename is libnl-doc-3.2.15)

That patch does not contain "libnl-doc-3.2.15" so it is irrelevant, can one of you please attach the full build log?

Full build log is located at /var/tmp/portage/dev-libs/libnl-3.2.16/temp/build.log

[Comment 3 Alexander 2012-11-28 14:59:21 UTC]

 * Package:    dev-libs/libnl-3.2.16
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        amd64 elibc_glibc kernel_linux multilib userland_GNU
 * FEATURES:   sandbox
>>> Unpacking source...
>>> Unpacking libnl-3.2.16.tar.gz to /var/tmp/portage/dev-libs/libnl-3.2.16/work
>>> Source unpacked in /var/tmp/portage/dev-libs/libnl-3.2.16/work
>>> Preparing source in /var/tmp/portage/dev-libs/libnl-3.2.16/work/libnl-3.2.16 ...
 * Running elibtoolize in: libnl-3.2.16/
 *   Applying portage/1.2.0 patch ...
 *   Applying sed/1.5.6 patch ...
 *   Applying as-needed/2.4.2 patch ...
 * Applying libnl-1.1-vlan-header.patch ...                                                                                                            [ ok ]
mv: не удалось выполнить stat для «/var/tmp/portage/dev-libs/libnl-3.2.16/work/libnl-doc-3.2.15»: Нет такого файла или каталога
 * ERROR: dev-libs/libnl-3.2.16 failed (prepare phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  93:  Called src_prepare
 *   environment, line 2411:  Called die
 * The specific snippet of code:
 *       mv "${WORKDIR}"/${PN}-doc-3.2.15 "${WORKDIR}"/${PN}-doc-${PV} || die
 * 
 * If you need support, post the output of `emerge --info '=dev-libs/libnl-3.2.16'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/libnl-3.2.16'`.
 * The complete build log is located at '/var/tmp/portage/dev-libs/libnl-3.2.16/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/libnl-3.2.16/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/libnl-3.2.16/work/libnl-3.2.16'
 * S: '/var/tmp/portage/dev-libs/libnl-3.2.16/work/libnl-3.2.16'

[Comment 4 Tom Wijsman (TomWij) (RETIRED) 2012-11-28 15:30:01 UTC]

Ah, now I see, that is the full build log.

The important piece is this:

> * The specific snippet of code:
> *       mv "${WORKDIR}"/${PN}-doc-3.2.15 "${WORKDIR}"/${PN}-doc-${PV} || die

It's not the patch, but an instruction from the ebuild that goes wrong, I didn't see this in the .14 ebuild, that makes sense as it appears to have been introduced in the .16 ebuild:

>src_prepare() {
>        elibtoolize
>        epatch "${FILESDIR}"/${PN}-1.1-vlan-header.patch
>        if use doc ; then
>                mv "${WORKDIR}"/${PN}-doc-3.2.15 "${WORKDIR}"/${PN}-doc-${PV} \
>                        || die
>        fi
>}

Perhaps this has been copied from a .15 ebuild and hasn't been adjusted since?

[Comment 5 Kevin 2012-11-28 15:32:38 UTC]

yes sorry i meant 3.2.16 the 14 was a typo, the build log is the correct one.

[Comment 6 Kevin 2012-11-28 15:40:18 UTC]

If i remove the move statement from the build file for 3.2.16 the build completes successfully as expected. 

Either the file was removed and not reflected in the ebuild, or it didn't get packaged with source but isn't build critical, since it has a different version im inclined to think it was just removed

[Comment 7 Jeroen Roovers (RETIRED) 2012-11-28 15:42:39 UTC]

*** This bug has been marked as a duplicate of bug 445026 ***