FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 10-20-2008, 04:51 PM
Brian Wince
 
Default emerge world failing with No module name libxml2

All,


I am trying to use “emerge –uDN world” *to
upgrade from an older snapshot to 20081008 and I cannot seem to get past the
issues with module libxml2.


I have tried running python-updater –p and it
complains about blocked packages which are older packages that I have not yet
been able to get updated via the* emerge world.


Is it possible to do an emerge –uDN to the latest
snapshot on a system that was built a year or two ago or do I have to do it in
stages?


If so what is the correct procedure?


The following is a snipit of the failure and it does not
only happen with epiphany.


*


*


if [ -f "C/epiphany.xml" ]; then
d="../"; else d="/var/tmp/portage/www-client/ep


iphany-2.22.3/work/epiphany-2.22.3/help/"; fi;


******* (cd es/
&&


*********
`which xml2po` -e -p


***********
"${d}es/es.po"


***********
"${d}C/epiphany.xml" > epiphany.xml.tmp &&


***********
cp epiphany.xml.tmp epiphany.xml && rm -f epiphany.xml.tmp)


Traceback (most recent call last):


* File "/usr/bin/xml2po", line 35, in
<module>


*** import libxml2


ImportError: No module named libxml2


make[2]: *** [bg/epiphany.xml] Error 1


make[2]: *** Waiting for unfinished jobs....


Traceback (most recent call last):


Traceback (most recent call last):


* File "/usr/bin/xml2po", line 35, in
<module>


*** import libxml2


ImportError: No module named libxml2


Traceback (most recent call last):


* File "/usr/bin/xml2po", line 35, in
<module>


*** import libxml2


ImportError: No module named libxml2


make[2]: *** [el/epiphany.xml] Error 1


* File "/usr/bin/xml2po", line 35, in <module>


*** import libxml2


ImportError: No module named libxml2


make[2]: *** [ca/epiphany.xml] Error 1


make[2]: *** [de/epiphany.xml] Error 1


Traceback (most recent call last):


* File "/usr/bin/xml2po", line 35, in
<module>


*** import libxml2


ImportError: No module named libxml2


make[2]: *** [en_GB/epiphany.xml] Error 1


Traceback (most recent call last):


* File "/usr/bin/xml2po", line 35, in
<module>


*** import libxml2


ImportError: No module named libxml2


make[2]: *** [es/epiphany.xml] Error 1


make[2]: Leaving directory
`/var/tmp/portage/www-client/epiphany-2.22.3/work/epiphany-2.22.3/help'


make[1]: *** [all-recursive] Error 1


make[1]: Leaving directory
`/var/tmp/portage/www-client/epiphany-2.22.3/work/epiphany-2.22.3'


make: *** [all] Error 2


**


** ERROR: www-client/epiphany-2.22.3 failed.


** Call stack:


****************
ebuild.sh, line** 49:* Called src_compile


**************
environment, line 2604:* Called gnome2_src_compile


**************
environment, line 1968:* Called die


** The specific snippet of code:


******** emake || die
"compile failure"


*** The die message:


**** compile failure


**


** If you need support, post the topmost build error,
and the call stack if relevant.


** A complete build log is located at
'/var/tmp/portage/www-client/epiphany-2.22.3/temp/build.log'.


** The ebuild environment file is located at
'/var/tmp/portage/www-client/epiphany-2.22.3/temp/environment'.


**


*


*


*


*


*


*


Brian Wince


Lab Unix System Administrator


bwince@redback.com


408.750.8437


*


Lab
Services Website:


http://eng.redback.com/display/labsvc/Home
 
Old 10-20-2008, 05:05 PM
"Joao Emanuel"
 
Default emerge world failing with No module name libxml2

2008/10/20 Brian Wince <bwince@redback.com>:
> All,
>
> I am trying to use "emerge –uDN world" to upgrade from an older snapshot to
> 20081008 and I cannot seem to get past the issues with module libxml2.
>
> I have tried running python-updater –p and it complains about blocked
> packages which are older packages that I have not yet been able to get
> updated via the emerge world.
>
> Is it possible to do an emerge –uDN to the latest snapshot on a system that
> was built a year or two ago or do I have to do it in stages?
>
> If so what is the correct procedure?
>
> The following is a snipit of the failure and it does not only happen with
> epiphany.
>
>
>
>
>
> if [ -f "C/epiphany.xml" ]; then d="../"; else
> d="/var/tmp/portage/www-client/ep
>
> iphany-2.22.3/work/epiphany-2.22.3/help/"; fi;
>
> (cd es/ &&
>
> `which xml2po` -e -p
>
> "${d}es/es.po"
>
> "${d}C/epiphany.xml" > epiphany.xml.tmp &&
>
> cp epiphany.xml.tmp epiphany.xml && rm -f epiphany.xml.tmp)
>
> Traceback (most recent call last):
>
> File "/usr/bin/xml2po", line 35, in <module>
>
> import libxml2
>
> ImportError: No module named libxml2
>
> make[2]: *** [bg/epiphany.xml] Error 1
>
> make[2]: *** Waiting for unfinished jobs....
>
> Traceback (most recent call last):
>
> Traceback (most recent call last):
>
> File "/usr/bin/xml2po", line 35, in <module>
>
> import libxml2
>
> ImportError: No module named libxml2
>
> Traceback (most recent call last):
>
> File "/usr/bin/xml2po", line 35, in <module>
>
> import libxml2
>
> ImportError: No module named libxml2
>
> make[2]: *** [el/epiphany.xml] Error 1
>
> File "/usr/bin/xml2po", line 35, in <module>
>
> import libxml2
>
> ImportError: No module named libxml2
>
> make[2]: *** [ca/epiphany.xml] Error 1
>
> make[2]: *** [de/epiphany.xml] Error 1
>
> Traceback (most recent call last):
>
> File "/usr/bin/xml2po", line 35, in <module>
>
> import libxml2
>
> ImportError: No module named libxml2
>
> make[2]: *** [en_GB/epiphany.xml] Error 1
>
> Traceback (most recent call last):
>
> File "/usr/bin/xml2po", line 35, in <module>
>
> import libxml2
>
> ImportError: No module named libxml2
>
> make[2]: *** [es/epiphany.xml] Error 1
>
> make[2]: Leaving directory
> `/var/tmp/portage/www-client/epiphany-2.22.3/work/epiphany-2.22.3/help'
>
> make[1]: *** [all-recursive] Error 1
>
> make[1]: Leaving directory
> `/var/tmp/portage/www-client/epiphany-2.22.3/work/epiphany-2.22.3'
>
> make: *** [all] Error 2
>
> *
>
> * ERROR: www-client/epiphany-2.22.3 failed.
>
> * Call stack:
>
> * ebuild.sh, line 49: Called src_compile
>
> * environment, line 2604: Called gnome2_src_compile
>
> * environment, line 1968: Called die
>
> * The specific snippet of code:
>
> * emake || die "compile failure"
>
> * The die message:
>
> * compile failure
>
> *
>
> * If you need support, post the topmost build error, and the call stack if
> relevant.
>
> * A complete build log is located at
> '/var/tmp/portage/www-client/epiphany-2.22.3/temp/build.log'.
>
> * The ebuild environment file is located at
> '/var/tmp/portage/www-client/epiphany-2.22.3/temp/environment'.
>
> *
>
>
>
>
>
>
>
>
>
>
>
>
>
> Brian Wince
>
> Lab Unix System Administrator
>
> bwince@redback.com
>
> 408.750.8437
>
>
>
> Lab Services Website:
>
> http://eng.redback.com/display/labsvc/Home
>
>

Brian try to upgrade or merge again the libxml2 package.
After this, try again world update.

--

{}s

Joao Emanuel
 
Old 10-20-2008, 05:19 PM
Brian Wince
 
Default emerge world failing with No module name libxml2

>> Brian try to upgrade or merge again the libxml2 package.
>> After this, try again world update.
>>
>> --
>>
>> {}s
>>
>> Joao Emanuel

Thanks for the quick response.
I had already emerged libxml2 and still got this.

Brian

-----Original Message-----
From: Joao Emanuel [mailto:joaoemanuel1981@gmail.com]
Sent: Monday, October 20, 2008 10:06 AM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge world failing with No module name libxml2

2008/10/20 Brian Wince <bwince@redback.com>:
> All,
>
> I am trying to use "emerge -uDN world" to upgrade from an older snapshot to
> 20081008 and I cannot seem to get past the issues with module libxml2.
>
> I have tried running python-updater -p and it complains about blocked
> packages which are older packages that I have not yet been able to get
> updated via the emerge world.
>
> Is it possible to do an emerge -uDN to the latest snapshot on a system that
> was built a year or two ago or do I have to do it in stages?
>
> If so what is the correct procedure?
>
> The following is a snipit of the failure and it does not only happen with
> epiphany.
>
>
>
>
>
> if [ -f "C/epiphany.xml" ]; then d="../"; else
> d="/var/tmp/portage/www-client/ep
>
> iphany-2.22.3/work/epiphany-2.22.3/help/"; fi;
>
> (cd es/ &&
>
> `which xml2po` -e -p
>
> "${d}es/es.po"
>
> "${d}C/epiphany.xml" > epiphany.xml.tmp &&
>
> cp epiphany.xml.tmp epiphany.xml && rm -f epiphany.xml.tmp)
>
> Traceback (most recent call last):
>
> File "/usr/bin/xml2po", line 35, in <module>
>
> import libxml2
>
> ImportError: No module named libxml2
>
> make[2]: *** [bg/epiphany.xml] Error 1
>
> make[2]: *** Waiting for unfinished jobs....
>
> Traceback (most recent call last):
>
> Traceback (most recent call last):
>
> File "/usr/bin/xml2po", line 35, in <module>
>
> import libxml2
>
> ImportError: No module named libxml2
>
> Traceback (most recent call last):
>
> File "/usr/bin/xml2po", line 35, in <module>
>
> import libxml2
>
> ImportError: No module named libxml2
>
> make[2]: *** [el/epiphany.xml] Error 1
>
> File "/usr/bin/xml2po", line 35, in <module>
>
> import libxml2
>
> ImportError: No module named libxml2
>
> make[2]: *** [ca/epiphany.xml] Error 1
>
> make[2]: *** [de/epiphany.xml] Error 1
>
> Traceback (most recent call last):
>
> File "/usr/bin/xml2po", line 35, in <module>
>
> import libxml2
>
> ImportError: No module named libxml2
>
> make[2]: *** [en_GB/epiphany.xml] Error 1
>
> Traceback (most recent call last):
>
> File "/usr/bin/xml2po", line 35, in <module>
>
> import libxml2
>
> ImportError: No module named libxml2
>
> make[2]: *** [es/epiphany.xml] Error 1
>
> make[2]: Leaving directory
> `/var/tmp/portage/www-client/epiphany-2.22.3/work/epiphany-2.22.3/help'
>
> make[1]: *** [all-recursive] Error 1
>
> make[1]: Leaving directory
> `/var/tmp/portage/www-client/epiphany-2.22.3/work/epiphany-2.22.3'
>
> make: *** [all] Error 2
>
> *
>
> * ERROR: www-client/epiphany-2.22.3 failed.
>
> * Call stack:
>
> * ebuild.sh, line 49: Called src_compile
>
> * environment, line 2604: Called gnome2_src_compile
>
> * environment, line 1968: Called die
>
> * The specific snippet of code:
>
> * emake || die "compile failure"
>
> * The die message:
>
> * compile failure
>
> *
>
> * If you need support, post the topmost build error, and the call stack if
> relevant.
>
> * A complete build log is located at
> '/var/tmp/portage/www-client/epiphany-2.22.3/temp/build.log'.
>
> * The ebuild environment file is located at
> '/var/tmp/portage/www-client/epiphany-2.22.3/temp/environment'.
>
> *
>
>
>
>
>
>
>
>
>
>
>
>
>
> Brian Wince
>
> Lab Unix System Administrator
>
> bwince@redback.com
>
> 408.750.8437
>
>
>
> Lab Services Website:
>
> http://eng.redback.com/display/labsvc/Home
>
>

Brian try to upgrade or merge again the libxml2 package.
After this, try again world update.

--

{}s

Joao Emanuel
 
Old 10-20-2008, 05:39 PM
"Arttu V."
 
Default emerge world failing with No module name libxml2

On 10/20/08, Brian Wince <bwince@redback.com> wrote:
> I have tried running python-updater -p and it complains about blocked
> packages which are older packages that I have not yet been able to get
> updated via the emerge world.

Would python-updater -i be of any assistance? It looks at slots rather
than versions.

--
Arttu V.
 
Old 10-20-2008, 06:00 PM
Brian Wince
 
Default emerge world failing with No module name libxml2

That may work I will need to give it a shot later today and see if it helps.
So the -I ignores the versions of packages installed and just fixes packages broken by a python upgrade, independent of the version?
I guess I really do not understand what this means.
I understand that slots can be used to install different versions of an app but not sure how that relates to python-updater.

Brian

-----Original Message-----
From: Arttu V. [mailto:arttuv69@gmail.com]
Sent: Monday, October 20, 2008 10:39 AM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge world failing with No module name libxml2

On 10/20/08, Brian Wince <bwince@redback.com> wrote:
> I have tried running python-updater -p and it complains about blocked
> packages which are older packages that I have not yet been able to get
> updated via the emerge world.

Would python-updater -i be of any assistance? It looks at slots rather
than versions.

--
Arttu V.
 
Old 10-21-2008, 03:33 PM
"Arttu V."
 
Default emerge world failing with No module name libxml2

Sorry for the slow reply. I was expecting more people interested in
sharing their insights into updating old, ancient-grade dinosaur
systems.

On 10/20/08, Brian Wince <bwince@redback.com> wrote:
> So the -I ignores the versions of packages installed and just fixes packages
> broken by a python upgrade, independent of the version?

Yes, I'd think for example in terms of the difference between "emerge
foo" and "emerge =foo-1.2.3". AFAICT, python-updater does the latter
by default, but with the -i option it is given a permission to do the
former "within a slot".

Since most packages only have a single slot, the "within a slot"
becomes irrelevant for them.

> I understand that slots can be used to install different versions of an app
> but not sure how that relates to python-updater.

Sorry if I lead you too much into this slot territory. The slots are
more of a red herring here, or just a small, distracting detail. For
most packages slots "won't matter".

But there are the few, like qt, for which it is important to keep
within a slot. Therefore it is nice that helpful scripts, like
python-updater, try to provide automagic support for the slotting
related stuff where it is needed.

Still, python-updater -i is not guaranteed to fix your original
problem, it was just a suggestion. The problem might not even lay with
libxml2, but one of its dependencies, their dependencies, or
dependencies of python itself.

If you haven't already tried it, then revdep-rebuild from the
gentoolkit package is your other friend. You might need try running it
first and then retry with the python-updater.

--
Arttu V.
 

Thread Tools




All times are GMT. The time now is 07:10 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org