[gentoo-amd64] Warning Message After Emerge

[gentoo-amd64] Warning Message After Emerge

[Frank Peters]

Recently, after an emerge I will sometimes see this message in bold
red colors:

!!! CANNOT IMPORT HTTP.CLIENT: cannot import name HTTPSConnection

Everything functions normally and there are no problems with
anything else.  But why the message?  The source of the message
is the portage getbinpkg.py file, but I don't know the purpose
of this file.

Doing an Internet search reveals only one other report of this
behavior but no answers were given.

Has anyone else seen this?

Frank Peters

[gentoo-amd64] Re: Warning Message After Emerge

[Duncan]

Frank Peters posted on Sat, 17 Oct 2009 19:02:15 -0400 as excerpted:

> Recently, after an emerge I will sometimes see this message in bold red
> colors:
> 
> !!! CANNOT IMPORT HTTP.CLIENT: cannot import name HTTPSConnection
> 
> Everything functions normally and there are no problems with anything
> else.  But why the message?  The source of the message is the portage
> getbinpkg.py file, but I don't know the purpose of this file.

getbinpkg.py would do what its name implies, check for binary packages.  
Standard from-source emerging should work fine, as you noted it seems to, 
but if you run FEATURES=buildpkg as I do, or otherwise have binary 
packages available, it's likely you'll have trouble merging them when you 
try.

The problem is likely related to portage's interaction with python.  Do 
you have both python-3 and python 2.5 or 2.6 merged?  The newest versions 
of python packages and portage itself should work fine in that case, but 
the fixes necessary to make it work are fairly recent, so you may have to 
remerge various python packages (some may require the newest ~arch 
version) so they setup modules for both python 3 and python 2.x -- 
formerly they only setup modules in whatever python happened to be the 
system python at the time.

But if you don't bother with binary packages anyway, at least that 
message shouldn't be an issue for you, you should be able to simply 
ignore it.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Re: [gentoo-amd64] Re: Warning Message After Emerge

[Drake Donahue]

On Sat, 2009-10-17 at 23:59 +0000, Duncan wrote:
> Frank Peters posted on Sat, 17 Oct 2009 19:02:15 -0400 as excerpted:
> 
> > Recently, after an emerge I will sometimes see this message in bold red
> > colors:
> > 
> > !!! CANNOT IMPORT HTTP.CLIENT: cannot import name HTTPSConnection
> > 
> > Everything functions normally and there are no problems with anything
> > else.  But why the message?  The source of the message is the portage
> > getbinpkg.py file, but I don't know the purpose of this file.
> 
> getbinpkg.py would do what its name implies, check for binary packages.  
> Standard from-source emerging should work fine, as you noted it seems to, 
> but if you run FEATURES=buildpkg as I do, or otherwise have binary 
> packages available, it's likely you'll have trouble merging them when you 
> try.
> 
> The problem is likely related to portage's interaction with python.  Do 
> you have both python-3 and python 2.5 or 2.6 merged?  The newest versions 
> of python packages and portage itself should work fine in that case, but 
> the fixes necessary to make it work are fairly recent, so you may have to 
> remerge various python packages (some may require the newest ~arch 
> version) so they setup modules for both python 3 and python 2.x -- 
> formerly they only setup modules in whatever python happened to be the 
> system python at the time.
> 
> But if you don't bother with binary packages anyway, at least that 
> message shouldn't be an issue for you, you should be able to simply 
> ignore it.
> 
will running python-updater help this?

Re: [gentoo-amd64] Re: Warning Message After Emerge

[Frank Peters]

On Sat, 17 Oct 2009 23:59:44 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:

> Frank Peters posted on Sat, 17 Oct 2009 19:02:15 -0400 as excerpted:
> 
> > Recently, after an emerge I will sometimes see this message in bold red
> > colors:
> > 
> > !!! CANNOT IMPORT HTTP.CLIENT: cannot import name HTTPSConnection
> > 
> > Everything functions normally and there are no problems with anything
> > else.  But why the message?  The source of the message is the portage
> > getbinpkg.py file, but I don't know the purpose of this file.
> 
> getbinpkg.py would do what its name implies, check for binary packages.  
> Standard from-source emerging should work fine, as you noted it seems to, 
> but if you run FEATURES=buildpkg as I do, or otherwise have binary 
> packages available, it's likely you'll have trouble merging them when you 
> try.
>

That is correct.  Now that I've done some checking, the message occurs 
when I use the "-B" option to emerge.  But I also have seen it following
an emerge --sync.

> The problem is likely related to portage's interaction with python.  Do 
> you have both python-3 and python 2.5 or 2.6 merged?  

I have python-3.1.1 and python-2.6.3 installed.  It was not my intention
to install both; portage/emerge just did it automatically.  By the
time I noticed this dual installation my system was in place for some time
and running without problems, so I just left things that way.  Python-updater
(run without options) doesn't report any anomaly.

What python version should I be using as the system python, 2.6.3 or
3.1.1?  Should I delete the older version and run python-updater?

Frank Peters

Re: [gentoo-amd64] Re: Warning Message After Emerge

[Barry Schwartz]

Frank Peters <frank.peters@comcast.net> skribis:
> I have python-3.1.1 and python-2.6.3 installed.  It was not my intention
> to install both; portage/emerge just did it automatically.  By the
> time I noticed this dual installation my system was in place for some time
> and running without problems, so I just left things that way.  Python-updater
> (run without options) doesn't report any anomaly.
> 
> What python version should I be using as the system python, 2.6.3 or
> 3.1.1?  Should I delete the older version and run python-updater?

I haven't been following this conversation, but almost surely you do
not want python 3 as your system python. It is a brand new dialect and
almost nothing will work with it. :)

[gentoo-amd64] Re: Warning Message After Emerge

[Duncan]

Drake Donahue posted on Sat, 17 Oct 2009 23:08:13 -0400 as excerpted:

> will running python-updater help this?

It may.  But the problem is that if the packages it rebuilds are still 
using the single python slot method, they'll be rebuilt for whatever's 
currently eselect-python-ed.  Python3 is still ~arch, and it's likely 
that not all packages building python modules have a stable version that 
builds for multiple slots yet.  Thus, if someone's running a normally 
stable system but has the unstable python3 installed, just as with any 
mixing of stable and unstable, it's not fully tested or assumed to work, 
and they may well have problems unless they update every single python 
module containing package to the latest ~arch version, as well as 
eselect, so they can get the versions that will install for all slots, 
not just whatever happens to be the system python at the time.

Otherwise, what python-updater is likely to do is to update everything to 
whatever's eelect-python-ed, but in the process, remove the modules as 
they were installed for the other slots, and that's likely not what 
people want, particularly since a lot of stuff doesn't even work with 
python3 at all yet, so it's almost certain they'll want the modules 
installed for at least one python 2.x version, 2.5 or 2.6.

So what I'm saying is that if you /are/ running python3 on a normally 
stable system, you better keyword ~arch eselect and all the python module 
containing packages, or you /are/ likely to have /something/ broken.  And 
at this point, only that non-critical binpkg module was complaining, so 
it may well be best to leave well enough alone.

The other alternative of course, would be to mask python3 for the time 
being, if you don't have anything that specifically uses it.  Since it's 
~arch-only at present anyway, stable users who have it installed 
presumably NEED it for something, but if they don't, and for all ~arch 
users (like me) who would have it installed only because it's ~arch, not 
because they specifically need it, it may well be best to put >=dev-lang/
python-3.0.0 in your package.mask file, and not worry about it until 
something you have installed wants it as a dependency to upgrade.

That's actually what I'm doing at the moment.  I have nothing that needs 
python-3, so I package.masked it, and don't have it on my system.  When 
something that I run eventually needs it for an upgrade, I'll worry about 
it then, but meanwhile, I'm saving myself quite a bit of grief as various 
packages convert over and have various python-3 bugs, that will be fixed 
by the time I actually need it installed for something or other.  I do my 
share of testing, but python-3 is not an area I'm interested in worrying 
about, so I don't.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

[gentoo-amd64] Re: Warning Message After Emerge

[Duncan]

Barry Schwartz posted on Sat, 17 Oct 2009 23:19:14 -0500 as excerpted:

> Frank Peters <frank.peters@comcast.net> skribis:
>> I have python-3.1.1 and python-2.6.3 installed.  It was not my
>> intention to install both; portage/emerge just did it automatically. 
>> By the time I noticed this dual installation my system was in place for
>> some time and running without problems, so I just left things that way.
>>  Python-updater (run without options) doesn't report any anomaly.
>> 
>> What python version should I be using as the system python, 2.6.3 or
>> 3.1.1?  Should I delete the older version and run python-updater?
> 
> I haven't been following this conversation, but almost surely you do not
> want python 3 as your system python. It is a brand new dialect and
> almost nothing will work with it. :)

That's correct.  As I wrote in a different post, unless you have 
something specific that needs python-3, I'd actually recommend not 
installing it.  And almost without-a-doubt, you don't want it as your 
system python.  eselect python list, and make sure that's set for 
2.6.whatever.  If you're running a full ~arch system, that, and possibly 
rebuilding a specific package or two, should be all you need to do -- if 
it was working before, I'd not argue with it.  However, the chances of 
you actually needing 3.x for anything is going to be pretty low for 
another six months or so at least, and likely longer, if I don't miss my 
guess.  And you'll likely save yourself worrying about a few bugs as 
packages upgrade in the mean time.  So yes, I'd probably mask >=3.0.0, 
unmerge the python3 you have installed, and then run python updater, but 
it's up to you.  But I'd DEFINITELY ensure I had a 2.6 (or 2.5 for those 
still on it) set as the system python, and run the updater with that set, 
at a minimum.

FWIW, I do have 3.x masked and not on my system, here.  I test lots of 
stuff, but have no interest in worrying myself about python upgrade 
bugs.  Hopefully, by the time I do need it for something, many of the 
bugs from the 3.x upgrades have already been taken care of without me 
ever noticing them, since I was still locked on 2.6.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman