Hi.
I've just stumbled on an abnormality for which I've yet no explanation.
Posting for possible general interest.
Yesterday ebuild unpack started to emit errors:
find: unrecognized: -mindepth
BusyBox v1.13.2 (2009-09-02 17:33:46 IDT) multi-call binary
Usage: find [PATH...] [EXPRESSION]
On Wednesday 25 November 2009 11:35:53 Amit Dor-Shifer wrote:
Hi.
I've just stumbled on an abnormality for which I've yet no explanation.
Posting for possible general interest.
Yesterday ebuild unpack started to emit errors:
find: unrecognized: -mindepth
BusyBox v1.13.2 (2009-09-02
amit0 ~ # fgrep make-symlinks /var/log/portage/elog/summary.log
/var/log/emerge.log;echo $?
1
amit0 ~ # euse -a make-symlinks
amit0 ~ #
amit0 ~ # grep -i -A 8 busybox-1.13.2 /var/log/portage/elog/summary.log
Messages generated by process 17234 on 2009-09-02 17:35:08 IDT for
package
This all happened because you didn't read this:
pkg_preinst() {
if use make-symlinks [[ ! ${VERY_BRAVE_OR_VERY_DUMB} == yes ]]
[[ ${ROOT} == / ]] ; then
ewarn setting USE=make-symlinks and emerging to / is very
dangerous.
ewarn it WILL overwrite lots
On Wednesday 25 November 2009 14:33:29 Amit Dor-Shifer wrote:
amit0 ~ # fgrep make-symlinks /var/log/portage/elog/summary.log
/var/log/emerge.log;echo $?
1
[snip]
Do you perhaps have a minimal elog config? I get that message every time here
FWIW, exing the excess exe-s from /bin/ helped
Alan McKinnon wrote:
On Wednesday 25 November 2009 14:33:29 Amit Dor-Shifer wrote:
amit0 ~ # fgrep make-symlinks /var/log/portage/elog/summary.log
/var/log/emerge.log;echo $?
1
[snip]
Do you perhaps have a minimal elog config? I get that message every time here
amit0 ~ #
6 matches
Mail list logo
