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