Re: Portage & Python3 - WAS: Re: [gentoo-user] updating old box: segfaults with python
On Thu, 09 Jan 2014 06:59:16 -0500, Tanstaafl wrote: > Is there any plan to eventually move portage to python3? It isn't like > python3 hasn't been out for a while now... ;) USE="python3" emerge -1 portage I've been sing that for a long time, but this is Gentoo, it is up to the individual to decide which version they use. -- Neil Bothwick Always remember you're unique, just like everyone else. signature.asc Description: PGP signature
Re: [gentoo-user] updating old box: segfaults with python
Am 09.01.2014 12:29, schrieb Neil Bothwick: > On Thu, 09 Jan 2014 11:16:01 +0100, Stefan G. Weichinger wrote: > >> I only have python 2.7 / 3.2 / 3.3 now installed. > > Bear n mind that portage will stick with python2, whatever your > eselect settings, unless you emerged it with the python3 USE flag. Yes. What I did now: went back to gcc-4.4.4-r2 (built in 2010) and rebuilt both dev-lang/python:2.7 and dev-lang/python:3.2 So I should have python built against the current unpacked glibc-2.16, right? Now I could retry to upgrade to glibc-2.17 ... and see if I hit that missing eutils.eclass again.
Portage & Python3 - WAS: Re: [gentoo-user] updating old box: segfaults with python
On 2014-01-09 6:29 AM, Neil Bothwick wrote: Bear n mind that portage will stick with python2, whatever your eselect settings, unless you emerged it with the python3 USE flag. I have wondered... Is there any plan to eventually move portage to python3? It isn't like python3 hasn't been out for a while now... ;)
Re: [gentoo-user] updating old box: segfaults with python
On Thu, 09 Jan 2014 11:16:01 +0100, Stefan G. Weichinger wrote: > I only have python 2.7 / 3.2 / 3.3 now installed. Bear n mind that portage will stick with python2, whatever your eselect settings, unless you emerged it with the python3 USE flag. -- Neil Bothwick WINDOWS: Will Install Needless Data On Whole System signature.asc Description: PGP signature
Re: [gentoo-user] updating old box: segfaults with python
Am 09.01.2014 11:16, schrieb Stefan G. Weichinger: > glibc-2.17 *builds* OK (emerge -B) but does not install ... when I > read correctly it does not find the class eutils.class (which is there > ...). Additional: I would not mind staying with 2.16 ... as I run with it right now, it is only portage "thinking" to have 2.17 installed ... but downgrading is hard-masked.
Re: [gentoo-user] updating old box: segfaults with python
Am 09.01.2014 08:07, schrieb Mick: > If dev-lang/python:2.7 does not allow you to emerge glibc then use > eselect to switch --python2 to an older python available in that > box and try emerging glibc with that. You may have to repeat this > until successful (hopefully) with dev-lang/python:2.7. > I don't know if you would need to update glibc in smaller steps (I > can't recall how many versions were there in between) but this can > be a painful process. It already is ... I face problems with postfix now ... needing another kernel leading to the udev-upgrade needing other kernel-option(s) ... you know. I only have python 2.7 / 3.2 / 3.3 now installed. glibc-2.17 *builds* OK (emerge -B) but does not install ... when I read correctly it does not find the class eutils.class (which is there ...). The memory seems OK to me ...
Re: [gentoo-user] updating old box: segfaults with python
On Wednesday 08 Jan 2014 14:37:00 Stefan G. Weichinger wrote: > Am 08.01.2014 14:36, schrieb Mick: > >> I don't know if I am stating the obvious but just in case: Have > >> a look here and set up your --python2 to reflect what you have > >> installed. You may need to go at it in steps between versions. > > > > Oops! Pulled the trigger too fast - sorry: > > > > http://www.gentoo.org/proj/en/Python/python-r1/user-guide.xml > > Yep. > > I tried to install glibc-2.17 again and it failed again. > Re-applied the 2.16-tarball ... > > python-3.3.2-r2 emerged fine, I assume I should also re-emerge > dev-lang/python:2.7 ? If dev-lang/python:2.7 does not allow you to emerge glibc then use eselect to switch --python2 to an older python available in that box and try emerging glibc with that. You may have to repeat this until successful (hopefully) with dev-lang/python:2.7. I don't know if you would need to update glibc in smaller steps (I can't recall how many versions were there in between) but this can be a painful process. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] updating old box: segfaults with python
Am 08.01.2014 17:41, schrieb Stefan G. Weichinger:
> trying "emerge -B glibc" for now ... step by step.
emerge -B : success
emerge -K: same failure
The unpacking of glibc seems to somehow break python while emerge still
runs ... at least that is my impression.
Manually unpacking the 2.17-tarball does not fix python ...
So I am back with the manual glibc-2.16 ... and have the correctly built
glibc-2.17.tbz2 as well.
So how to fix that?
Use another python? Right now I have:
# eselect python list
Available Python interpreters:
[1] python2.4
[2] python2.5
[3] python2.6
[4] python2.7 *
[5] python3.1
[6] python3.2
[7] python3.3
In make.conf:
PYTHON_TARGETS="python2_6 python2_7 python3_2"
PYTHON_SINGLE_TARGET="python2_7"
I assume I could get rid of some releases ... but currently I am
hesitating ;-)
2.7.5-r3 and 3.2.5-r3 rebuilt fine here today.
used python-3.2 now ... next failure to install the tbz2
What do I get?
->
>>> Installing (1 of 1) sys-libs/glibc-2.17
* Defaulting /etc/host.conf:multi to on
* ERROR: sys-libs/glibc-2.17::gentoo failed (prerm phase):
* eutils.eclass could not be found by inherit()
*
* Call stack:
* ebuild.sh, line 545: Called source
'/var/db/pkg/sys-libs/glibc-2.17/glibc-2.17.ebuild'
* glibc-2.17.ebuild, line 5: Called inherit 'eutils' 'versionator'
'toolchain-funcs' 'flag-o-matic' 'gnuconfig' 'multilib' 'systemd'
'unpacker' 'multiprocessing'
* ebuild.sh, line 257: Called die
* The specific snippet of code:
* [[ -z ${location} ]] && die "${1}.eclass could not be found by
inherit()"
*
* If you need support, post the output of `emerge --info
'=sys-libs/glibc-2.17::gentoo'`,
* the complete build log and the output of `emerge -pqv
'=sys-libs/glibc-2.17::gentoo'`.
* The complete build log is located at
'/var/tmp/portage/._unmerge_/sys-libs/glibc-2.17/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/._unmerge_/sys-libs/glibc-2.17/temp/die.env'.
* Working directory: '/usr/lib/portage/pym'
* S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.17/work/glibc-2.17'
/usr/lib/portage/bin/isolated-functions.sh: Zeile 109: 17558
Speicherzugriffsfehler "$PORTAGE_BIN_PATH"/ebuild-ipc exit 1
* The ebuild phase 'prerm' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* QA Notice: ECLASS 'eutils' inherited illegally in sys-libs/glibc-2.17
* ERROR: sys-libs/glibc-2.17::gentoo failed:
* eutils.eclass could not be found by inherit()
*
* Call stack:
* misc-functions.sh, line 17: Called source
'/usr/lib/portage/bin/ebuild.sh'
* ebuild.sh, line 545: Called source
'/var/db/pkg/sys-libs/glibc-2.17/glibc-2.17.ebuild'
* glibc-2.17.ebuild, line 5: Called inherit 'eutils' 'versionator'
'toolchain-funcs' 'flag-o-matic' 'gnuconfig' 'multilib' 'systemd'
'unpacker' 'multiprocessing'
* ebuild.sh, line 257: Called die
* The specific snippet of code:
* [[ -z ${location} ]] && die "${1}.eclass could not be found by
inherit()"
*
... and way more.
I tried to remove /var/db/pkg/sys-libs/glibc-2.17/environment.bz2 ...
didn't help.
Looking forward to some clever suggestions ;-)
Stefan
Re: [gentoo-user] updating old box: segfaults with python
Am 08.01.2014 17:20, schrieb Neil Bothwick:
> On Wed, 08 Jan 2014 12:54:09 +0100, Stefan G. Weichinger wrote:
>
>> # python-updater /usr/sbin/python-updater: Zeile 146: 28887
>> Speicherzugriffsfehler /usr/bin/portageq has_version / "${1}"
>> /usr/sbin/python-updater: Zeile 146: 2
>> Speicherzugriffsfehler /usr/bin/portageq has_version / "${1}" *
>> Python 2 and Python 3 not installed
>
> Is eselect python pointing to valid python 2 and 3 versions? Can
> you run python2 and python3 in a terminal?
Yes, since untaring glibc-2.16.
glibc-2.17 does not emerge --- it fails and leaves me with the
segfaults ... only fix so far is unpacking that 2.16-tarball
http://tinderbox.dev.gentoo.org/default-linux/x86/sys-libs/ only has
2.16 ... portage on the given system "thinks" 2.17 is installed so I
can't (re-)emerge 2.16 because downgrading is not supported.
I don't want to keep it this way as it isn't really consistent ... so
I should find out why glibc-2.17 does not install, right?
trying "emerge -B glibc" for now ... step by step.
Re: [gentoo-user] updating old box: segfaults with python
On Wed, 08 Jan 2014 12:54:09 +0100, Stefan G. Weichinger wrote:
> # python-updater
> /usr/sbin/python-updater: Zeile 146: 28887 Speicherzugriffsfehler
> /usr/bin/portageq has_version / "${1}"
> /usr/sbin/python-updater: Zeile 146: 2 Speicherzugriffsfehler
> /usr/bin/portageq has_version / "${1}"
> * Python 2 and Python 3 not installed
Is eselect python pointing to valid python 2 and 3 versions? Can you run
python2 and python3 in a terminal?
--
Neil Bothwick
When told the reason for Daylight Saving time the old Indian said...
"Only a white man would believe that you could cut a foot off the top of a
blanket And sew it to the bottom of a blanket and have a longer blanket."
signature.asc
Description: PGP signature
Re: [gentoo-user] updating old box: segfaults with python
Am 08.01.2014 14:36, schrieb Mick: >> I don't know if I am stating the obvious but just in case: Have >> a look here and set up your --python2 to reflect what you have >> installed. You may need to go at it in steps between versions. > > Oops! Pulled the trigger too fast - sorry: > > http://www.gentoo.org/proj/en/Python/python-r1/user-guide.xml Yep. I tried to install glibc-2.17 again and it failed again. Re-applied the 2.16-tarball ... python-3.3.2-r2 emerged fine, I assume I should also re-emerge dev-lang/python:2.7 ?
Re: [gentoo-user] updating old box: segfaults with python
On Wednesday 08 Jan 2014 13:33:20 Mick wrote: > On Wednesday 08 Jan 2014 12:10:41 Stefan G. Weichinger wrote: > > Am 08.01.2014 13:06, schrieb Mick: > > > On Wednesday 08 Jan 2014 11:58:01 Stefan G. Weichinger wrote: > > >> Thanks for the pointer. > > >> > > >> Unpacked /usr/portage/distfiles/portage-2.2.7.tar.bz2 right now > > >> etc > > >> > > >> Still getting segfaults with the replaced emerge-command :-( > > > > > > This does not look good. > > > > > > Can you get someone to reboot the machine with a sysrescue or > > > Gentoo LiveCD for you to connect to it remotely and then chroot > > > into the borked installation to essentially reinstall the required > > > packages with a functional portage and toolchain from the LiveCD? > > > > maybe ... *but* I think I got something done: > > > > pulled in python-2.7.5-r3.tbz2 from http://tinderbox.dev.gentoo.org > > ... and untarred it ... didn't help. > > > > Then glibc-2.16.0.tbz2 ... and now python-updater and eix and emerge > > ... don't segfault anymore. > > > > I will now re-emerge glibc and python etc ... right? > > > > Thanks! > > I don't know if I am stating the obvious but just in case: Have a look > here and set up your --python2 to reflect what you have installed. You > may need to go at it in steps between versions. Oops! Pulled the trigger too fast - sorry: http://www.gentoo.org/proj/en/Python/python-r1/user-guide.xml -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] updating old box: segfaults with python
On Wednesday 08 Jan 2014 12:10:41 Stefan G. Weichinger wrote: > Am 08.01.2014 13:06, schrieb Mick: > > On Wednesday 08 Jan 2014 11:58:01 Stefan G. Weichinger wrote: > >> Thanks for the pointer. > >> > >> Unpacked /usr/portage/distfiles/portage-2.2.7.tar.bz2 right now > >> etc > >> > >> Still getting segfaults with the replaced emerge-command :-( > > > > This does not look good. > > > > Can you get someone to reboot the machine with a sysrescue or > > Gentoo LiveCD for you to connect to it remotely and then chroot > > into the borked installation to essentially reinstall the required > > packages with a functional portage and toolchain from the LiveCD? > > maybe ... *but* I think I got something done: > > pulled in python-2.7.5-r3.tbz2 from http://tinderbox.dev.gentoo.org > ... and untarred it ... didn't help. > > Then glibc-2.16.0.tbz2 ... and now python-updater and eix and emerge > ... don't segfault anymore. > > I will now re-emerge glibc and python etc ... right? > > Thanks! I don't know if I am stating the obvious but just in case: Have a look here and set up your --python2 to reflect what you have installed. You may need to go at it in steps between versions. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] updating old box: segfaults with python
Am 08.01.2014 13:06, schrieb Mick: > On Wednesday 08 Jan 2014 11:58:01 Stefan G. Weichinger wrote: > >> Thanks for the pointer. >> >> Unpacked /usr/portage/distfiles/portage-2.2.7.tar.bz2 right now >> etc >> >> Still getting segfaults with the replaced emerge-command :-( > > This does not look good. > > Can you get someone to reboot the machine with a sysrescue or > Gentoo LiveCD for you to connect to it remotely and then chroot > into the borked installation to essentially reinstall the required > packages with a functional portage and toolchain from the LiveCD? maybe ... *but* I think I got something done: pulled in python-2.7.5-r3.tbz2 from http://tinderbox.dev.gentoo.org ... and untarred it ... didn't help. Then glibc-2.16.0.tbz2 ... and now python-updater and eix and emerge ... don't segfault anymore. I will now re-emerge glibc and python etc ... right? Thanks!
Re: [gentoo-user] updating old box: segfaults with python
On Wednesday 08 Jan 2014 12:06:47 Mick wrote: > On Wednesday 08 Jan 2014 11:58:01 Stefan G. Weichinger wrote: > > Thanks for the pointer. > > > > Unpacked /usr/portage/distfiles/portage-2.2.7.tar.bz2 right now etc > > > > Still getting segfaults with the replaced emerge-command :-( > > This does not look good. > > Can you get someone to reboot the machine with a sysrescue or Gentoo LiveCD > for you to connect to it remotely and then chroot into the borked > installation to essentially reinstall the required packages with a > functional portage and toolchain from the LiveCD? Another idea, in case you have a fs corruption: if awk/gawk segfaults can you use a binary package from your local machine to see if the segfault goes away? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] updating old box: segfaults with python
On Wednesday 08 Jan 2014 11:58:01 Stefan G. Weichinger wrote: > Thanks for the pointer. > > Unpacked /usr/portage/distfiles/portage-2.2.7.tar.bz2 right now etc > > Still getting segfaults with the replaced emerge-command :-( This does not look good. Can you get someone to reboot the machine with a sysrescue or Gentoo LiveCD for you to connect to it remotely and then chroot into the borked installation to essentially reinstall the required packages with a functional portage and toolchain from the LiveCD? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] updating old box: segfaults with python
Am 08.01.2014 12:53, schrieb Mick: > In case things are really badly borked: > > http://www.gentoo.org/proj/en/portage/doc/manually-fixing-portage.xml > > Then you can use emerge --buildpkg to create a binary package > locally, and scp it to the remote machine where you can use > --usepkg or --usepkgonly. Thanks for the pointer. Unpacked /usr/portage/distfiles/portage-2.2.7.tar.bz2 right now etc Still getting segfaults with the replaced emerge-command :-(
Re: [gentoo-user] updating old box: segfaults with python
Am 08.01.2014 12:45, schrieb Mick:
> The segfaults look scary and could point to hardware fault. I'd
> run a backup of any useful data to start with.
sure, backups ran late night ... and non-python-stuff seems to work ok
so far
> Then run 'python-updater' to rebuild any packages that had their
> links broken.
That does not run. Already tried it.
# python-updater
/usr/sbin/python-updater: Zeile 146: 28887 Speicherzugriffsfehler
/usr/bin/portageq has_version / "${1}"
/usr/sbin/python-updater: Zeile 146: 2 Speicherzugriffsfehler
/usr/bin/portageq has_version / "${1}"
* Python 2 and Python 3 not installed
Re: [gentoo-user] updating old box: segfaults with python
On Wednesday 08 Jan 2014 11:39:03 Stefan G. Weichinger wrote: > Am 08.01.2014 12:28, schrieb Stefan G. Weichinger: > > What can I do? quickpkg some python-version and copy over? > > (sidenote: 32bit box ...) > > I assume it should be glibc repaired, right? > Activated some 32bit-chroot here and building glibc-2.17-package now. > > How to apply that without emerge? googling ... In case things are really badly borked: http://www.gentoo.org/proj/en/portage/doc/manually-fixing-portage.xml Then you can use emerge --buildpkg to create a binary package locally, and scp it to the remote machine where you can use --usepkg or --usepkgonly. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] updating old box: segfaults with python
On Wednesday 08 Jan 2014 11:28:36 Stefan G. Weichinger wrote:
> Greetings,
>
> yesterday I started to upgrade an older gentoo server at a customer. It
> has only been updated now and then as they tend to save money and rarely
> contact me ...
>
> I recommended to at least apply the stuff mentioned in the GLSAs ... and
> applied some updates today (remote, via ssh).
>
> Today glibc failed to merge:
> >>> Installing (2 of 3) sys-libs/glibc-2.17
>
> * Defaulting /etc/host.conf:multi to on
> /usr/lib/portage/bin/phase-functions.sh: Zeile 87: 26924
> Speicherzugriffsfehler "${PORTAGE_PYTHON:-/usr/bin/python}"
> "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}"
> * ERROR: sys-libs/glibc-2.11.3::gentoo failed (prerm phase):
> * filter-bash-environment.py failed
> *
> * Call stack:
> *ebuild.sh, line 480: Called __preprocess_ebuild_env
> * phase-functions.sh, line 156: Called __filter_readonly_variables
> '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
> * phase-functions.sh, line 137: Called die
> * The specific snippet of code:
> *"${PORTAGE_PYTHON:-/usr/bin/python}"
> "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" ||
> die "filter-bash-environment.py failed"
> *
> * If you need support, post the output of `emerge --info
> '=sys-libs/glibc-2.11.3::gentoo'`,
> * the complete build log and the output of `emerge -pqv
> '=sys-libs/glibc-2.11.3::gentoo'`.
> * The complete build log is located at
> '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.11.3/temp/build.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.11.3/temp/environment'.
> * Working directory: '/usr/lib/portage/pym'
> * S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.11.3/work/glibc-2.11.3'
> /usr/lib/portage/bin/isolated-functions.sh: Zeile 109: 27001
> Speicherzugriffsfehler "$PORTAGE_BIN_PATH"/ebuild-ipc exit 1
>
> But it seems that this is the consequence of problems with python.
> There are various versions installed:
>
> # eselect python list
> Available Python interpreters:
> [1] python2.4
> [2] python2.5
> [3] python2.6
> [4] python2.7 *
> [5] python3.1
> [6] python3.3
>
>
> But I get segfaults (german: Speicherzugriffsfehler) for all of them:
>
> mail ~ # python2.7
> Speicherzugriffsfehler
> mail ~ # python3.1
> Speicherzugriffsfehler
> mail ~ # python3.3
> Speicherzugriffsfehler
>
> dmesg shows lines:
>
> awk[28527]: segfault at 579e ip 579e sp bfc3006c error 4 in
> gawk[8048000+4c000]
> awk[28531]: segfault at 579e ip 579e sp bff3c8ec error 4 in
> gawk[8048000+4c000]
> find[28706]: segfault at 579e ip 579e sp bff21c3c error 4 in
> find[8048000+21000]
> find[28707]: segfault at 579e ip 579e sp bff42c9c error 4 in
> find[8048000+21000]
> find[28708]: segfault at 579e ip 579e sp bfe1a4ac error 4 in
> find[8048000+21000]
> find[28714]: segfault at 579e ip 579e sp bf82cb5c error 4 in
> find[8048000+21000]
> find[28715]: segfault at 579e ip 579e sp bfa0ef3c error 4 in
> find[8048000+21000]
> find[28716]: segfault at 579e ip 579e sp bfa4c4cc error 4 in
> find[8048000+21000]
> find[28720]: segfault at 579e ip 579e sp bfa1c83c error 4 in
> find[8048000+21000]
> find[28721]: segfault at 579e ip 579e sp bfcf9fbc error 4 in
> find[8048000+21000]
> eix[28731]: segfault at 579e ip 579e sp bfc028ec error 4 in
> eix[8048000+114000]
> python2.7[28732]: segfault at 579e ip 579e sp bfa1c9fc error 4 in
> python2.7[8048000+1000]
> python2.7[28733]: segfault at 579e ip 579e sp bf8a2c0c error 4 in
> python2.7[8048000+1000]
> python2.7[28746]: segfault at 579e ip 579e sp bfeb392c error 4 in
> python2.7[8048000+1000]
> python2.7[28747]: segfault at 579e ip 579e sp bfbfcd4c error 4 in
> python2.7[8048000+1000]
> python2.7[28749]: segfault at 579e ip 579e sp bfa1b71c error 4 in
> python2.7[8048000+1000]
> python2.7[28757]: segfault at 579e ip 579e sp bfeb8b0c error 4 in
> python2.7[8048000+1000]
> python2.7[28762]: segfault at 579e ip 579e sp bfeb479c error 4 in
> python2.7[8048000+1000]
>
>
>
> This leads to not being able to emerge something :-(
>
> What can I do? quickpkg some python-version and copy over?
> (sidenote: 32bit box ...)
>
> I would like to avoid to have to drive there so it would be great to be
> able to fix that from here, via ssh.
>
>
> Thanks for any help, Stefan
The segfaults look scary and could point to hardware fault. I'd run a backup
of any useful data to start with.
Then run 'python-updater' to rebuild any packages that had their links broken.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] updating old box: segfaults with python
Am 08.01.2014 12:28, schrieb Stefan G. Weichinger: > What can I do? quickpkg some python-version and copy over? > (sidenote: 32bit box ...) I assume it should be glibc repaired, right? Activated some 32bit-chroot here and building glibc-2.17-package now. How to apply that without emerge? googling ...
[gentoo-user] updating old box: segfaults with python
Greetings,
yesterday I started to upgrade an older gentoo server at a customer. It
has only been updated now and then as they tend to save money and rarely
contact me ...
I recommended to at least apply the stuff mentioned in the GLSAs ... and
applied some updates today (remote, via ssh).
Today glibc failed to merge:
>>> Installing (2 of 3) sys-libs/glibc-2.17
* Defaulting /etc/host.conf:multi to on
/usr/lib/portage/bin/phase-functions.sh: Zeile 87: 26924
Speicherzugriffsfehler "${PORTAGE_PYTHON:-/usr/bin/python}"
"${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}"
* ERROR: sys-libs/glibc-2.11.3::gentoo failed (prerm phase):
* filter-bash-environment.py failed
*
* Call stack:
*ebuild.sh, line 480: Called __preprocess_ebuild_env
* phase-functions.sh, line 156: Called __filter_readonly_variables
'--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
* phase-functions.sh, line 137: Called die
* The specific snippet of code:
* "${PORTAGE_PYTHON:-/usr/bin/python}"
"${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" ||
die "filter-bash-environment.py failed"
*
* If you need support, post the output of `emerge --info
'=sys-libs/glibc-2.11.3::gentoo'`,
* the complete build log and the output of `emerge -pqv
'=sys-libs/glibc-2.11.3::gentoo'`.
* The complete build log is located at
'/var/tmp/portage/._unmerge_/sys-libs/glibc-2.11.3/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/._unmerge_/sys-libs/glibc-2.11.3/temp/environment'.
* Working directory: '/usr/lib/portage/pym'
* S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.11.3/work/glibc-2.11.3'
/usr/lib/portage/bin/isolated-functions.sh: Zeile 109: 27001
Speicherzugriffsfehler "$PORTAGE_BIN_PATH"/ebuild-ipc exit 1
But it seems that this is the consequence of problems with python.
There are various versions installed:
# eselect python list
Available Python interpreters:
[1] python2.4
[2] python2.5
[3] python2.6
[4] python2.7 *
[5] python3.1
[6] python3.3
But I get segfaults (german: Speicherzugriffsfehler) for all of them:
mail ~ # python2.7
Speicherzugriffsfehler
mail ~ # python3.1
Speicherzugriffsfehler
mail ~ # python3.3
Speicherzugriffsfehler
dmesg shows lines:
awk[28527]: segfault at 579e ip 579e sp bfc3006c error 4 in
gawk[8048000+4c000]
awk[28531]: segfault at 579e ip 579e sp bff3c8ec error 4 in
gawk[8048000+4c000]
find[28706]: segfault at 579e ip 579e sp bff21c3c error 4 in
find[8048000+21000]
find[28707]: segfault at 579e ip 579e sp bff42c9c error 4 in
find[8048000+21000]
find[28708]: segfault at 579e ip 579e sp bfe1a4ac error 4 in
find[8048000+21000]
find[28714]: segfault at 579e ip 579e sp bf82cb5c error 4 in
find[8048000+21000]
find[28715]: segfault at 579e ip 579e sp bfa0ef3c error 4 in
find[8048000+21000]
find[28716]: segfault at 579e ip 579e sp bfa4c4cc error 4 in
find[8048000+21000]
find[28720]: segfault at 579e ip 579e sp bfa1c83c error 4 in
find[8048000+21000]
find[28721]: segfault at 579e ip 579e sp bfcf9fbc error 4 in
find[8048000+21000]
eix[28731]: segfault at 579e ip 579e sp bfc028ec error 4 in
eix[8048000+114000]
python2.7[28732]: segfault at 579e ip 579e sp bfa1c9fc error 4 in
python2.7[8048000+1000]
python2.7[28733]: segfault at 579e ip 579e sp bf8a2c0c error 4 in
python2.7[8048000+1000]
python2.7[28746]: segfault at 579e ip 579e sp bfeb392c error 4 in
python2.7[8048000+1000]
python2.7[28747]: segfault at 579e ip 579e sp bfbfcd4c error 4 in
python2.7[8048000+1000]
python2.7[28749]: segfault at 579e ip 579e sp bfa1b71c error 4 in
python2.7[8048000+1000]
python2.7[28757]: segfault at 579e ip 579e sp bfeb8b0c error 4 in
python2.7[8048000+1000]
python2.7[28762]: segfault at 579e ip 579e sp bfeb479c error 4 in
python2.7[8048000+1000]
This leads to not being able to emerge something :-(
What can I do? quickpkg some python-version and copy over?
(sidenote: 32bit box ...)
I would like to avoid to have to drive there so it would be great to be
able to fix that from here, via ssh.
Thanks for any help, Stefan
