| View previous topic :: View next topic |
| Author |
Message |
depontius
Advocate
Joined: 05 May 2004
Posts: 2156
|
 Posted: Tue Jan 11, 2011 5:15 pm Post subject: Installation oddity - python version |
 |
|
I was installing a new system last weekend and ran into what turned out to be a python oddity. Four packages refused to install:
1 - sys-apps/gnome-disk-utility - needed by gnucash
2 - xfce-base/exo - needed by xfce4-meta
3 - gnome-base/gdm - needed by gdm
4 - net-analyzer/snmp - needed by hplip
Eventually reading through the various error logs I found a frequent thread - something about syntax errors in /usr/bin/xml2po. From the error listings and a direct look at xml2po, it was python. Since all of my other Gentoo systems were working and up-to-date, it couldn't be simply a coding error. So I tried "eselect python list" and discovered that my "system python" was set to python-3.1. I set it back to python-2.6, where it belonged, rebuilt app-text/gnome-doc-utils, which provides /usr/bin/xml2po, and all was well and I could finish my install.
The real question here is how the heck system python got set to python-3.1 and left that way. I can see it getting temporarily getting set that way during some installation process or another, but I wouldn't expect it to be left there. Next question is what other landmines this has left in my system - I'm guessing that there are other packages built with python-3.1 that either haven't failed me yet, or are language-neutral and won't bother me. Is simply running "python-updater" now that I've set the correct python version sufficient?
_________________
.sigs waste space and bandwidth |
|
| Back to top |
|
 |
phajdan.jr
Developer
Joined: 23 Mar 2006
Posts: 1740
Location: Poland
|
| Posted: Tue Jan 11, 2011 6:27 pm Post subject: Re: Installation oddity - python version |
|
|
| depontius wrote: | | The real question here is how the heck system python got set to python-3.1 and left that way. |
It's possible it's a bug. It'd be interesting to see whether this could be reproduced...
_________________
http://phajdan-jr.blogspot.com/ |
|
| Back to top |
|
|
depontius
Advocate
Joined: 05 May 2004
Posts: 2156
|
| Posted: Tue Jan 11, 2011 6:38 pm Post subject: |
|
|
I've still got "/var/log/emerge.log" which will contain the packages and sequence of installation. Is there some way to examine an installed package and tell which version of python was used to build it? I'm presuming that the differences will only show on packages implemented in python. I've also got the complete record in "/var/log/portage" if someone can suggest specifics to look for.
_________________
.sigs waste space and bandwidth |
|
| Back to top |
|
|
phajdan.jr
Developer
Joined: 23 Mar 2006
Posts: 1740
Location: Poland
|
| Posted: Tue Jan 11, 2011 6:41 pm Post subject: |
|
|
| depontius wrote: | | I've still got "/var/log/emerge.log" which will contain the packages and sequence of installation. Is there some way to examine an installed package and tell which version of python was used to build it? I'm presuming that the differences will only show on packages implemented in python. I've also got the complete record in "/var/log/portage" if someone can suggest specifics to look for. |
Maybe something in /var/db/pkg, I'm not sure. I've sent an e-mail to gentoo-dev, this is not the only thread suggesting that system version of python mysteriously "flipped".
_________________
http://phajdan-jr.blogspot.com/ |
|
| Back to top |
|
|
Section_8
Guru
Joined: 22 May 2004
Posts: 461
Location: Arlington, TX, US
|
| Posted: Tue Jan 11, 2011 7:17 pm Post subject: |
|
|
| I was experimenting with a 32bit chroot a couple of weeks ago and I think I hit the same problem. I couldn't emerge elogv in the chroot (complained about a print statement), and it looked like the real problem was that my default python was 3.*. In my case, I don't think I had a python 2.* installed at all - IIRC, eselect python list just showed python 3. I was surprised at that, but assumed it was a WAD. Anyway, I ended blowing away the chroot for other reasons so can't go back and investigate. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 29963
Location: 56N 3W
|
| Posted: Tue Jan 11, 2011 7:37 pm Post subject: |
|
|
There was a bug in some stage3 tarballs tat had python-3.1 set as the default.
This is now fixed.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
depontius
Advocate
Joined: 05 May 2004
Posts: 2156
|
| Posted: Tue Jan 11, 2011 7:52 pm Post subject: |
|
|
I began the install last Friday - Jan 7, and was a bit surprised to see that the amd64 stage3 tarball I grabbed was dated in late December. I know people do take time off for the holidays, but somewhere I got the impression that stage tarballs were automated.
Anyway, the other thing that surprised me was that so little was broken by having python-3.1 set as the default. I would have expected much more to fail.
_________________
.sigs waste space and bandwidth |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 29963
Location: 56N 3W
|
| Posted: Wed Jan 12, 2011 6:36 pm Post subject: |
|
|
depontius,
More and more things work with python-3.1. I have hear of some devs using it for a month or two as their default python.
I'm not brave enough to switch yet.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
duderonomy
Guru
Joined: 20 Mar 2004
Posts: 325
Location: SF Bay Area
|
| Posted: Sat Feb 25, 2012 5:03 am Post subject: |
|
|
| NeddySeagoon wrote: | | This is now fixed. |
Hi!
I am not so sure...
It is still happening.
I just encountered it with stage3-amd64-20120223.tar.bz2
About 644 packages built with v3, unbeknownst to me!.
sys-apps/x86info failed with print syntax.
Cheers,
 |
|
| Back to top |
|
|
t0dbld
n00b
Joined: 23 Jun 2011
Posts: 34
|
| Posted: Sat May 05, 2012 6:22 pm Post subject: |
|
|
| Code: | /usr/bin/xml2po: EPYTHON variable has unrecognized value 'python2'
/usr/bin/xml2po: EPYTHON variable has unrecognized value 'python2'
/usr/bin/xml2po: EPYTHON variable has unrecognized value 'python2'
/usr/bin/xml2po: EPYTHON variable has unrecognized value 'python2'
make[2]: *** [el/gdm.xml] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [id/gdm.xml] Error 1
make[2]: *** [de/gdm.xml] Error 1
/usr/bin/xml2po: EPYTHON variable has unrecognized value 'python2'
make[2]: *** [ko/gdm.xml] Error 1
/usr/bin/xml2po: EPYTHON variable has unrecognized value 'python2'
make[2]: *** [fr/gdm.xml] Error 1
make[2]: *** [it/gdm.xml] Error 1
/usr/bin/xml2po: EPYTHON variable has unrecognized value 'python2'
/usr/bin/xml2po: EPYTHON variable has unrecognized value 'python2'
make[2]: *** [es/gdm.xml] Error 1
make[2]: *** [en_GB/gdm.xml] Error 1
/usr/bin/xml2po: EPYTHON variable has unrecognized value 'python2'
make[2]: *** [oc/gdm.xml] Error 1
make[2]: Leaving directory `/var/tmp/portage/gnome-base/gdm-3.2.1.1-r2/work/gdm-3.2.1.1/docs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/gnome-base/gdm-3.2.1.1-r2/work/gdm-3.2.1.1'
make: *** [all] Error 2
* ERROR: gnome-base/gdm-3.2.1.1-r2 failed (compile phase):
* emake failed
|
recompiled with proper python still happening here |
|
| Back to top |
|
|
cwr
Veteran
Joined: 17 Dec 2005
Posts: 1462
|
| Posted: Sun May 06, 2012 2:21 pm Post subject: |
|
|
AFAIK the current stage3's (certainly the x86) have only a 3.x python.
I thought that meant that packages had all moved to 3.x, but apparently
not - the cure is to download 2.x and switch to that before the full install.
Will |
|
| Back to top |
|
|
t0dbld
n00b
Joined: 23 Jun 2011
Posts: 34
|
| Posted: Mon May 07, 2012 12:31 am Post subject: |
|
|
| cwr wrote: | AFAIK the current stage3's (certainly the x86) have only a 3.x python.
I thought that meant that packages had all moved to 3.x, but apparently
not - the cure is to download 2.x and switch to that before the full install.
Will |
Actually i Got this from an upgrade from a working system , both 2.7 and 3.1 are installed, I have selected 2.7 and recompiled everything still nothing , I gave it a day or two to try and figure out what caused the bug and for work around or fixes but at this point I have to move on and just rebuild  |
|
| Back to top |
|
|
t0dbld
n00b
Joined: 23 Jun 2011
Posts: 34
|
| Posted: Mon May 07, 2012 3:43 am Post subject: |
|
|
| t0dbld wrote: | | cwr wrote: | AFAIK the current stage3's (certainly the x86) have only a 3.x python.
I thought that meant that packages had all moved to 3.x, but apparently
not - the cure is to download 2.x and switch to that before the full install.
Will |
Actually i Got this from an upgrade from a working system , both 2.7 and 3.1 are installed, I have selected 2.7 and recompiled everything still nothing , I gave it a day or two to try and figure out what caused the bug and for work around or fixes but at this point I have to move on and just rebuild |
Mods please delete all of my posts, I am in fact an idiot |
|
| Back to top |
|
|
|
Installing Gentoo
