Matthias Guede wrote:
Make sure your working directory is in the path:
PATH=${PATH}:./ ./python /usr/bin/emerge python
!!Big security hole!! ./ is purposely left out of the path so people
can't sneak fake programs in there.
~eric
--
gentoo-user@lists.gentoo.org mailing list
On Friday 22 February 2008, Eric Martin wrote:
Matthias Guede wrote:
Make sure your working directory is in the path:
PATH=${PATH}:./ ./python /usr/bin/emerge python
!!Big security hole!! ./ is purposely left out of the path so people
can't sneak fake programs in there.
~eric
Very
On Thursday 21 February 2008, Joseph wrote:
On 02/20/08 11:02, Alan McKinnon wrote:
Or just untar the one on a recent install disk and re-install
python. If all else fails I could send you a copy of
python-2.5.1-r5 which is about 8M large
Hi Alan,
I had python 2.4.4 installed on my AMD64
On Thu, Feb 21, 2008 at 3:13 AM, Joseph [EMAIL PROTECTED] wrote:
(...)
* checking Python-2.4.4.tar.bz2 ;-) ...[ ok ]
* checking python-gentoo-patches-2.4.4-r4.tar.bz2 ;-) ...[ ok ]
/usr/bin/env: python: No such file or directory
/usr/bin/env: python: No such file or directory
2008/2/21, Joseph [EMAIL PROTECTED]:
When trying to emerge ./python /usr/bin/emerge python
I got an error:
./python /usr/bin/emerge python
Calculating dependencies... done!
Verifying ebuild Manifests...
Emerging (1 of 1) dev-lang/python-2.4.4-r6 to /
* Python-2.4.4.tar.bz2
On Thursday 21 February 2008, Joseph wrote:
Thanks for the input folks.
running 'which python' did not find any python so I had to add python
to the path: PATH=/usr/local/bin/:$PATH
That directory should be in your PATH anyway. Add it and /usr/local/sbin
as well in your .bashrc
Strange that
On 02/21/08 13:05, Henry Gebhardt wrote:
On Thu, Feb 21, 2008 at 3:13 AM, Joseph [EMAIL PROTECTED] wrote:
(...)
* checking Python-2.4.4.tar.bz2 ;-) ...[ ok ]
* checking python-gentoo-patches-2.4.4-r4.tar.bz2 ;-) ...[ ok ]
/usr/bin/env: python: No such file or directory
/usr/bin/env:
Hello
On Wed, Feb 20, 2008 at 09:35:54AM +0100, Stéphane ANCELOT wrote:
I made a silly mistake :
emerge --unmerge python*
now emerge does not work anymore since it needs python !!!
Any idea ?
If you install python manually, emerge should start working. Then you
can emerge it and get back
On Wednesday 20 February 2008, Stéphane ANCELOT wrote:
Hi,
I made a silly mistake :
emerge --unmerge python*
now emerge does not work anymore since it needs python !!!
Any idea ?
Best Regards
Steph
Oops.
An easy way is to get a quickpkg tarball of python from another machine
and unpack
On (20/02/08 11:02) Alan McKinnon wrote:
On Wednesday 20 February 2008, Stéphane ANCELOT wrote:
Hi,
I made a silly mistake :
emerge --unmerge python*
now emerge does not work anymore since it needs python !!!
Any idea ?
Best Regards
Steph
Oops.
An easy way is to get a
On 02/20/08 11:02, Alan McKinnon wrote:
On Wednesday 20 February 2008, Stéphane ANCELOT wrote:
Hi,
I made a silly mistake :
emerge --unmerge python*
now emerge does not work anymore since it needs python !!!
Any idea ?
Best Regards
Steph
Oops.
An easy way is to get a quickpkg tarball of
On 02/20/08 18:06, Joseph wrote:
I just made the same mistake, was running revdev-rebuild and an error
showed up regarding python block another package, without much thinking I
unmerged python :-/
How can I install it manually?
Can I just copy python directory from from x86 machine to AMD64,
On 02/20/08 18:51, Joseph wrote:
Here is the solution just in case somebody need it.
http://www.jonm.co.uk/Linux.html
Though the command:
./python emerge python
should be (full path):
./python /usr/bin/emerge python
--
#Joseph
When trying to emerge ./python /usr/bin/emerge python
I got an
13 matches
Mail list logo
