From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: python-2.7 update: re-emerge of cracklib failed, how can I fix it?
Date: Sun, 27 Mar 2011 11:10:09 +0100 [thread overview]
Message-ID: <201103271110.19731.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4D8EEA3B.4010904@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 806 bytes --]
On Sunday 27 March 2011 08:41:47 Jarry wrote:
> On 27. 3. 2011 8:50, Remy Blank wrote:
> > Try re-emerging setuptools.
>
> On 27. 3. 2011 8:51, Adam Carter wrote:
> > emerge --oneshot dev-python/setuptools would be a good start. (FWIW
> > google "cracklib No module named setuptools"...)
>
> Thanks, this work! So it seems to me, the right procedure is:
> 1. emerge --update...
> 2. eselect python set python2.7
> 3. python-updater ${options}
> 4. emerge --depclean
> 5. revdep-rebuild
>
> My mistake was I forgot to run "2."...
>
> Jarry
... and run 4. and 5. above in the wrong order?
In the e-warning words of --depclean itself:
"* Depclean may break link level dependencies. Thus, it is
* recommended to use a tool such as `revdep-rebuild` ... "
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-27 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 6:38 [gentoo-user] python-2.7 update: re-emerge of cracklib failed, how can I fix it? Jarry
2011-03-27 6:50 ` [gentoo-user] " Remy Blank
2011-03-27 7:41 ` Jarry
2011-03-27 10:10 ` Mick [this message]
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=201103271110.19731.michaelkintzios@gmail.com \
--to=michaelkintzios@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