public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jarry <mr.jarry@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] python-2.7 update: re-emerge of cracklib failed, how can I fix it?
Date: Sun, 27 Mar 2011 08:38:54 +0200	[thread overview]
Message-ID: <4D8EDB7E.6090801@gmail.com> (raw)

Hi,
apparently I screwed something during python update, and now
I can not fix my system. This is what I did:

emerge --sync
emerge --ask --update --deep --newuse world

At the end, I have seen:
You should run 'python-updater ${options}' to rebuild Python modules.

So I did, then "emerge --depclean", and that was my mistake:
python2.6 has been unmerged before I switched to python2.7.
Im just surprised python2.6 has been unmerged, when it was
still active and selected python version.

Then by revdep-rebuild I got a lot of error-messages and
at that time I realised something got wrong.

Then I switched to python2.7 (eselect python set python2.7),
and tried revdep-rebuild again. Two packages needed to be
emerged again: libxstl and cracklib. The first got emerged
without a problem, but for cracklib emerge failed with
this messages:

--------------------------------------------------------
   File "setup.py", line 22, in <module>
     from setuptools import setup, Extension, find_packages
ImportError: No module named setuptools
  * ERROR: sys-libs/cracklib-2.8.16 failed (compile phase):
  *   Building failed with CPython 2.7 in distutils_building() function
  *
  * Call stack:
  *     ebuild.sh, line   56:  Called src_compile
  *   environment, line 5094:  Called do_python
  *   environment, line 1389:  Called distutils_src_compile
  *   environment, line 1238:  Called python_execute_function 
'distutils_building'
  *   environment, line 3662:  Called die
  * The specific snippet of code:
  *                       die "${failure_message}";
  *
* If you need support, post the output of 'emerge --info 
=sys-libs/cracklib-2.8.16',
  * the complete build log and the output of 'emerge -pqv 
=sys-libs/cracklib-2.8.16'.
  * The complete build log is located at 
'/var/tmp/portage/sys-libs/cracklib-2.8.16/temp/build.log'.
  * The ebuild environment file is located at 
'/var/tmp/portage/sys-libs/cracklib-2.8.16/temp/environment'.
  * S: '/var/tmp/portage/sys-libs/cracklib-2.8.16/work/cracklib-2.8.16'

 >>> Failed to emerge sys-libs/cracklib-2.8.16, Log file:

 >>>  '/var/tmp/portage/sys-libs/cracklib-2.8.16/temp/build.log'
--------------------------------------------------------

My question is: how can I fix this mess?

Jarry

-- 
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.



             reply	other threads:[~2011-03-27  6:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27  6:38 Jarry [this message]
2011-03-27  6:50 ` [gentoo-user] Re: python-2.7 update: re-emerge of cracklib failed, how can I fix it? Remy Blank
2011-03-27  7:41   ` Jarry
2011-03-27 10:10     ` Mick
2011-03-27 10:25       ` Adam Carter
2011-03-27 20:13     ` JM
2011-03-28 11:34       ` Mr. Jarry
2011-03-28 12:35         ` Neil Bothwick
2011-03-27  6:51 ` [gentoo-user] " Adam Carter

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=4D8EDB7E.6090801@gmail.com \
    --to=mr.jarry@gmail.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