On 16-04-2008 13:11:06 +0200, Bacchella Fabrice wrote:
> When I try to emerge portage, I'm getting the following messages :
> >>> Merging sys-apps/portage-2.2.00.9894 to /
> * ERROR: sys-apps/portage-2.2.00.9894 failed:
> * dev-lang/python-2.5.1-r5 does not actually support the ssl USE flag!
> *
> * Call stack:
> * ebuild.sh: 49: <call pkg_preinst>
> * environment:2296: <call built_with_use
> '>=dev-lang/python-2.5' 'ssl'>
> * environment: 399: die "$PKG does not
> actually support the $1 USE flag!"
> *
> * If you need support, post the topmost build error, and the call stack if
> relevant.
> * build log:
> '/data/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9894/temp/build.log'
> * ebuild environment:
> '/data/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9894/temp/environment'
> * S:
> '/data/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9894/work/prefix-portage-2.2.00.9894'
> !!! FAILED preinst: 1
>
> But I'm always getting this message, python being compiled with or without
> USE="-ssl"

Hmmmm, portage seems to be pretty confused. Just to check, do you have
EPREFIX set in your environment, and if you do, does it point to
something correct?


--
Fabian Groffen
Gentoo on a different level
--
gentoo-alt@lists.gentoo.org mailing list

No, the variable is not set. But the destination is good, /data/gentoo
is the good prefix. But i started the shell with the command :

su - root -c /data/gentoo/startprefix

I'm doing this after having finished the installation.


Le 16 avr. 08 à 13:44, Fabian Groffen a écrit :

On 16-04-2008 13:11:06 +0200, Bacchella Fabrice wrote:

When I try to emerge portage, I'm getting the following messages :

Merging sys-apps/portage-2.2.00.9894 to /

* ERROR: sys-apps/portage-2.2.00.9894 failed:
* dev-lang/python-2.5.1-r5 does not actually support the ssl USE
flag!

*
* Call stack:
* ebuild.sh: 49: <call pkg_preinst>
* environment:2296: <call built_with_use
'>=dev-lang/python-2.5' 'ssl'>
* environment: 399: die "$PKG
does not

actually support the $1 USE flag!"
*
* If you need support, post the topmost build error, and the call
stack if

relevant.
* build log:
'/data/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9894/temp/
build.log'

* ebuild environment:
'/data/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9894/temp/
environment'

* S:
'/data/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9894/work/
prefix-portage-2.2.00.9894'

!!! FAILED preinst: 1

But I'm always getting this message, python being compiled with or
without

USE="-ssl"


Hmmmm, portage seems to be pretty confused. Just to check, do you
have

EPREFIX set in your environment, and if you do, does it point to
something correct?


--
Fabian Groffen
Gentoo on a different level
--
gentoo-alt@lists.gentoo.org mailing list



--
gentoo-alt@lists.gentoo.org mailing list

On Wed, Apr 16, 2008 at 6:52 AM, Bacchella Fabrice
<fabrice.bacchella@exalead.com> wrote:
> No, the variable is not set. But the destination is good, /data/gentoo is
> the good prefix. But i started the shell with the command :
> su - root -c /data/gentoo/startprefix
>
> I'm doing this after having finished the installation.
<snip>

(Please don't top post, generally frowned upon on *nix lists)

Do you get a different result if you are not root? EPREFIX not being
set in your env seems like a problem to me...Can you track that down?
--
gentoo-alt@lists.gentoo.org mailing list

No change.

But I don't see the problem with EPREFIX ?

portage is complaigning about python and ssl, whatever the USE flag
was. I even tried to set it on command line or in make.conf. No change.

So I don't think problem is with EPREFIX.
I'm using a su - to be sure to have a clean environnement.


Le 16 avr. 08 à 20:58, Jeremy a écrit :

On Wed, Apr 16, 2008 at 6:52 AM, Bacchella Fabrice
<fabrice.bacchella@exalead.com> wrote:
No, the variable is not set. But the destination is good, /data/
gentoo is

the good prefix. But i started the shell with the command :
su - root -c /data/gentoo/startprefix

I'm doing this after having finished the installation.

<snip>

(Please don't top post, generally frowned upon on *nix lists)

Do you get a different result if you are not root? EPREFIX not being
set in your env seems like a problem to me...Can you track that down?
--
gentoo-alt@lists.gentoo.org mailing list



--
gentoo-alt@lists.gentoo.org mailing list

On 16-04-2008 21:23:03 +0200, Bacchella Fabrice wrote:
> No change.
>
> But I don't see the problem with EPREFIX ?
>
> portage is complaigning about python and ssl, whatever the USE flag was. I
> even tried to set it on command line or in make.conf. No change.
> So I don't think problem is with EPREFIX.
> I'm using a su - to be sure to have a clean environnement.

The problem is that Portage thinks that python has no ssl USE flag at
all. I asked for EPREFIX just to be sure you weren't pointing to some
random garbage Prefix. built_with_use is defined in
usr/portage/eclass/eutils.eclass

--
Fabian Groffen
Gentoo on a different level
--
gentoo-alt@lists.gentoo.org mailing list

On 16-04-2008 21:25:42 +0200, Fabian Groffen wrote:
> On 16-04-2008 21:23:03 +0200, Bacchella Fabrice wrote:
> > No change.
> >
> > But I don't see the problem with EPREFIX ?
> >
> > portage is complaigning about python and ssl, whatever the USE flag was. I
> > even tried to set it on command line or in make.conf. No change.
> > So I don't think problem is with EPREFIX.
> > I'm using a su - to be sure to have a clean environnement.
>
> The problem is that Portage thinks that python has no ssl USE flag at
> all. I asked for EPREFIX just to be sure you weren't pointing to some
> random garbage Prefix. built_with_use is defined in
> usr/portage/eclass/eutils.eclass

It looks like a bug in bash.

v=$( $(<"${file}") )
echo ${v[@]} -> gives "(bla bla bla)"
echo ${v[@]#[-+]} -> gives ""

(I don't expect the braces, and the empty result for the replacement
either)

--
Fabian Groffen
Gentoo on a different level
--
gentoo-alt@lists.gentoo.org mailing list

On 19-04-2008 13:18:19 +0200, Fabian Groffen wrote:
> It looks like a bug in bash.

Problem found. We don't bootstrap bash, because Bash 3.00 looked ok.
However, it contains a bug. You need to bootstrap bash before
bootstrapping portage, because /usr/bin/bash causes the problem. I've
now successfully emerged portage.

> v=$( $(<"${file}") )
> echo ${v[@]} -> gives "(bla bla bla)"
> echo ${v[@]#[-+]} -> gives ""
>
> (I don't expect the braces, and the empty result for the replacement
> either)


--
Fabian Groffen
Gentoo on a different level
--
gentoo-alt@lists.gentoo.org mailing list