| 1 |
On Fri, Sep 26, 2008 at 2:47 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> On Thu, 25 Sep 2008 17:59:35 -0400, Kirk Lowery wrote: |
| 3 |
> |
| 4 |
>> During upgrading today, I inadvertently allowed 2.3 to be deleted. I |
| 5 |
>> looked in portage, but it is apparently gone. |
| 6 |
> |
| 7 |
> Nothing is ever truly gone from portage |
| 8 |
> |
| 9 |
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-lang/python/?hideattic=0 |
| 10 |
> |
| 11 |
> goes back as far as python-1/5/2 |
| 12 |
|
| 13 |
Thanks for the answers. I thought I'd report my experience here for |
| 14 |
the knowledgebase: |
| 15 |
|
| 16 |
I went back and downloaded not only the latest 2.3.6 ebuild into my |
| 17 |
local overlay, and all the attendant files (including important |
| 18 |
patches) in the "files" directory. In order to be able to emerge the |
| 19 |
ebuild file, I had to recreate the digest and manifest files. Don't |
| 20 |
know why the checksums were off, but they were. The solution was |
| 21 |
simple: |
| 22 |
|
| 23 |
# ebuild python-2.3.6-r6.ebuild digest |
| 24 |
|
| 25 |
took care of it. When I tried to restart my legacy software I got a |
| 26 |
python error: "ImportError: No module named thread". Sure enough, the |
| 27 |
equery use feature told me "-threads". So I overrode that in |
| 28 |
package.use. Nope, no change. Looking at the compile log, I saw this: |
| 29 |
|
| 30 |
./configure --prefix=/usr --host=x86_64-pc-linux-gnu |
| 31 |
--mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share |
| 32 |
--sysconfdir=/etc --localstatedir=/var/lib --with-fpectl |
| 33 |
--enable-shared --enable-ipv6 --infodir=${prefix}/share/info |
| 34 |
--mandir=${prefix}/share/man --with-libc= --enable-unicode=ucs4 |
| 35 |
--with-threads --without-threads --with-threads --libdir=/usr/lib64 |
| 36 |
--build=x86_64-pc-linux-gnu |
| 37 |
|
| 38 |
Configure has both --with- and --without-threads!!?? |
| 39 |
|
| 40 |
Nothing I did seemed to make a difference. So I traced where in the |
| 41 |
ebuild this might be coming from: |
| 42 |
|
| 43 |
use threads \ |
| 44 |
&& myconf="${myconf} --with-threads" \ |
| 45 |
&& myconf="${myconf} --without-threads" |
| 46 |
|
| 47 |
I still don't know why (and would appreciate any knowledgeable person |
| 48 |
commenting here), but I simply commented out the third line above, |
| 49 |
re-emerged, and viola! my legacy software is up and running. |
| 50 |
|
| 51 |
Kirk |
Archives