[gentoo-user] python-2.7 update: re-emerge of cracklib failed, how can I fix it?

[gentoo-user] python-2.7 update: re-emerge of cracklib failed, how can I fix it?

[Jarry]

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.

[gentoo-user] Re: python-2.7 update: re-emerge of cracklib failed, how can I fix it?

[Remy Blank]

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

Jarry wrote:
>    File "setup.py", line 22, in <module>
>      from setuptools import setup, Extension, find_packages
> ImportError: No module named setuptools

Try re-emerging setuptools.

-- Remy


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] python-2.7 update: re-emerge of cracklib failed, how can I fix it?

[Adam Carter]

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

> --------------------------------------------------------
>  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?
>
> emerge --oneshot dev-python/setuptools would be a good start. (FWIW google
"cracklib No module named setuptools"...)

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

Re: [gentoo-user] Re: python-2.7 update: re-emerge of cracklib failed, how can I fix it?

[Jarry]

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

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

Re: [gentoo-user] Re: python-2.7 update: re-emerge of cracklib failed, how can I fix it?

[Mick]

[-- 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 --]

Re: [gentoo-user] Re: python-2.7 update: re-emerge of cracklib failed, how can I fix it?

[Adam Carter]

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

> ... 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` ... "
>

Agreed, revdep last. I always run depclean with pretend first. If depclean
wants to remove key packages like python, i will often just remove all the
others it has identified manually rather than running it again without
pretend. I also use buildsyspkg.

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

Re: [gentoo-user] Re: python-2.7 update: re-emerge of cracklib failed, how can I fix it?

[JM]

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

Hi - you don't give the name of the python version to eselect python set,
you give it the number of the option (usually 1 or 2) next to the version
you want, which you saw when running 'eselect python list'

On 27 March 2011 08:41, Jarry <mr.jarry@gmail.com> 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
>
> --
> _______________________________________________________________
> This mailbox accepts e-mails only from selected mailing-lists!
> Everything else is considered to be spam and therefore deleted.
>
>

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

Re: [gentoo-user] Re: python-2.7 update: re-emerge of cracklib failed, how can I fix it?

[Mr. Jarry]

Apparently, both methods work. But I agree your way is easier...

BTW, when we are at the subject, is it possible to switch to python 3.x,
and get rid of python 2.x completely? I noticed there are still both versions
of python installed: 2.7.1 and 3.1.3...

Jarrry

On Sun, Mar 27, 2011 at 10:13 PM, JM <jmurray315@googlemail.com> wrote:
> Hi - you don't give the name of the python version to eselect python set,
> you give it the number of the option (usually 1 or 2) next to the version
> you want, which you saw when running 'eselect python list'
>
>> 1. emerge --update...
>> 2. eselect python set python2.7
>> 3. python-updater ${options}
>> 4. emerge --depclean
>> 5. revdep-rebuild

Re: [gentoo-user] Re: python-2.7 update: re-emerge of cracklib failed, how can I fix it?

[Neil Bothwick]

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

On Mon, 28 Mar 2011 13:34:29 +0200, Mr. Jarry wrote:

> BTW, when we are at the subject, is it possible to switch to python 3.x,
> and get rid of python 2.x completely? I noticed there are still both
> versions of python installed: 2.7.1 and 3.1.3...

Possible, yes. Advisable, no. Many (most?) Python 2 scripts will not work
with Python 3, so you really need both interpreters installed.


-- 
Neil Bothwick

Idaho - It's not the end of the world, but you can see it from there.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]