| 1 |
Am 08.01.2014 17:20, schrieb Neil Bothwick: |
| 2 |
> On Wed, 08 Jan 2014 12:54:09 +0100, Stefan G. Weichinger wrote: |
| 3 |
> |
| 4 |
>> # python-updater /usr/sbin/python-updater: Zeile 146: 28887 |
| 5 |
>> Speicherzugriffsfehler /usr/bin/portageq has_version / "${1}" |
| 6 |
>> /usr/sbin/python-updater: Zeile 146: 28888 |
| 7 |
>> Speicherzugriffsfehler /usr/bin/portageq has_version / "${1}" * |
| 8 |
>> Python 2 and Python 3 not installed |
| 9 |
> |
| 10 |
> Is eselect python pointing to valid python 2 and 3 versions? Can |
| 11 |
> you run python2 and python3 in a terminal? |
| 12 |
|
| 13 |
Yes, since untaring glibc-2.16. |
| 14 |
|
| 15 |
glibc-2.17 does not emerge --- it fails and leaves me with the |
| 16 |
segfaults ... only fix so far is unpacking that 2.16-tarball |
| 17 |
|
| 18 |
http://tinderbox.dev.gentoo.org/default-linux/x86/sys-libs/ only has |
| 19 |
2.16 ... portage on the given system "thinks" 2.17 is installed so I |
| 20 |
can't (re-)emerge 2.16 because downgrading is not supported. |
| 21 |
|
| 22 |
I don't want to keep it this way as it isn't really consistent ... so |
| 23 |
I should find out why glibc-2.17 does not install, right? |
| 24 |
|
| 25 |
trying "emerge -B glibc" for now ... step by step. |
Archives