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)
what version of Portage are you using?
* 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!
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
If you could, try to isolate the specific ebuilds that are giving you problems with "die".
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)