Re: pkg_rolling-replace -u ... gives message opt/pkg/bin/pkg_tarup[159]: local: not found [No such file or directory]

[Richard PALO <richard.palo%baou.fr@localhost>]

Le 08/01/13 09:36, Richard PALO a écrit :
> Not sure if this is a bug or not, as I am just trying out using
> pkg_rolling-replace -u instead of pkg_chk -u...
>
> I notice in the logs the same pkg_tarup message as below:
>
> ===> Replacing for pango-1.32.5
> WARNING: experimental target - DATA LOSS MAY OCCUR.
> => Becoming ``root'' to make su-replace (pfexec)
> /opt/pkg/bin/pkg_tarup[159]: local: not found [No such file or directory]
> Creating binary package: pango-1.32.5
> Creating package /tmp/pkgsrc/devel/pango/work/pango-1.32.5
> ...
>
> Is this a possible problem with pkg_tarup, or rather an invocation
> problem of pkg_tarup inside pkg_rolling-replace?
>
> Has anybody else noticed this, in particular that have ${PREFIX}
> elsewhere than the default?
Le 08/01/13 09:36, Richard PALO a écrit :> Not sure if this is a bug or 
not, as I am just trying out using
> pkg_rolling-replace -u instead of pkg_chk -u...
>
> I notice in the logs the same pkg_tarup message as below:
>
> ===> Replacing for pango-1.32.5
> WARNING: experimental target - DATA LOSS MAY OCCUR.
> => Becoming ``root'' to make su-replace (pfexec)
> /opt/pkg/bin/pkg_tarup[159]: local: not found [No such file or directory]
> Creating binary package: pango-1.32.5
> Creating package /tmp/pkgsrc/devel/pango/work/pango-1.32.5
> ...
>
> Is this a possible problem with pkg_tarup, or rather an invocation
> problem of pkg_tarup inside pkg_rolling-replace?
>
> Has anybody else noticed this, in particular that have ${PREFIX}
> elsewhere than the default?
>
>
>

Is it possible that the problems are here
in pkgsrc/mk/pkgformat/pkg/replace.mk:
> # Generates a binary package for the (older) installed package using 
pkg_tarup.
> #
> replace-tarup: .PHONY
>         ${RUN} [ -x ${_PKG_TARUP_CMD:Q} ] \
>         || ${FAIL_MSG} ${_PKG_TARUP_CMD:Q}" was not found.";            \
>         ${_REPLACE_OLDNAME_CMD};                                        \
>         ${PKGSRC_SETENV} PKG_DBDIR=${_PKG_DBDIR} PKG_SUFX=${PKG_SUFX}   \
>                 PKGREPOSITORY=${WRKDIR}                                 \
>                 ${_PKG_TARUP_CMD} $${oldname} ||                        \
>         ${FAIL_MSG} "Could not pkg_tarup $${oldname}".

in package.mk:
> ######################################################################
> ### tarup (PUBLIC)
> ######################################################################
> ### tarup is a public target to generate a binary package from an
> ### installed package instance.
> ###
> _PKG_TARUP_CMD= ${LOCALBASE}/bin/pkg_tarup

though these seem okay
> richard@devzone:~/src/pkgsrc/devel/pango$ bmake show-var 
VARNAME=_PKG_TARUP_CMD
> /opt/pkg/bin/pkg_tarup
> richard@devzone:~/src/pkgsrc/devel/pango$ file /opt/pkg/bin/pkg_tarup
> /opt/pkg/bin/pkg_tarup: executable /usr/xpg4/bin/sh script

on the other hand, what *is* strange about the file command is that it 
chooses /usr/xpg4/bin/sh instead of:
> richard@devzone:~/src/pkgsrc/devel/pango$ bmake show-var 
VARNAME=TOOLS_PLATFORM.sh
> /bin/bash

perhaps that is fixed at runtime (?)...