public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Wince <bwince@redback.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] emerge world failing with No module name libxml2
Date: Mon, 20 Oct 2008 09:51:56 -0700	[thread overview]
Message-ID: <B701736AA609BA4AB6555D5E7BC490FB8BBCE935DA@RBSJX.ad.redback.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3172 bytes --]

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


[-- Attachment #2: Type: text/html, Size: 8847 bytes --]

             reply	other threads:[~2008-10-20 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 16:51 Brian Wince [this message]
2008-10-20 17:05 ` [gentoo-user] emerge world failing with No module name libxml2 Joao Emanuel
2008-10-20 17:19   ` Brian Wince
2008-10-20 17:39 ` Arttu V.
2008-10-20 18:00   ` Brian Wince
2008-10-21 15:33     ` Arttu V.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B701736AA609BA4AB6555D5E7BC490FB8BBCE935DA@RBSJX.ad.redback.com \
    --to=bwince@redback.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox