Bug 1063 – ebuild scripts can't find "die"

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Christian Loitsch 2002-03-11 08:32:18 UTC]

When an ebuild-script fails it tries to start die, but can't find it.
Had this problem with 2 scripts (aspell and ?? I think it was mozilla)

[Comment 1 Daniel Robbins (RETIRED) 2002-03-11 15:56:14 UTC]

what version of Portage are you using?

[Comment 2 Christian Loitsch 2002-03-12 05:34:35 UTC]

*   sys-apps/portage
      Latest version Available:  1.8.8-r1
      Latest version Installed:  1.8.8-r1
      Description:  Portage ports system

will update to 1.8.9... and try again!

[Comment 3 Christian Loitsch 2002-03-12 07:29:48 UTC]

I just noticed that portage 1.8.9 is masked.  Should I nevertheless
try ist?
I just made a emerge sync and emerge --pretend update gives me:
[ebuild   U] sys-apps/baselayout-1.7.4-r2 to /
[ebuild N  ] app-shells/sash-3.4-r4 to /
[ebuild   U] sys-apps/grub-0.90-r7 to /
[ebuild   U] sys-libs/zlib-1.1.4 to /
[ebuild   U] net-misc/openssh-3.1_p1 to /

current baselayout:
*   sys-apps/baselayout
      Latest version Available:  1.7.4-r2
      Latest version Installed:  1.7.3-r1

[Comment 4 Daniel Robbins (RETIRED) 2002-03-12 09:53:15 UTC]

If you could, try to isolate the specific ebuilds that are giving you problems
with "die".

[Comment 5 Christian Loitsch 2002-03-12 13:44:44 UTC]

sorry can't reproduce it.
Tried the aspell script again.  Failed like a champion ;)
But die was found.
Also tried some home-made scripts, and they all fail perfectly.
As I am not able to do it again, I maybe messed the env-variables up
Have no idea how... but it works now.  (and even if not, it's not
a big deal)