emerge -G still failing

[Psumoni]

Any attempt to emerge -G something fails like this:

localhost ~ # emerge -pG mozilla-firefox

These are the packages that would be merged, in order:

Fetching binary packages info...
cache miss: 'x' --- cache hit: 'o'
xTraceback (most recent call last):
File "/usr/bin/emerge", line 4049, in ?
emerge_main()
File "/usr/bin/emerge", line 4044, in emerge_main
myopts, myaction, myfiles, spinner)
File "/usr/bin/emerge", line 3452, in action_build
myopts, myparams, spinner)
File "/usr/bin/emerge", line 675, in __init__
trees["/"]["bintree"].populate(
File "/usr/lib/portage/pym/portage.py", line 5428, in populate
self.remotepkgs = getbinpkg.dir_get_metadat a(
File "/usr/lib/portage/pym/getbinpkg.py", line 524, in dir_get_metadata
myid = file_get_metadata(baseurl +"/"+x, conn, chunk_size)
File "/usr/lib/portage/pym/getbinpkg.py", line 327, in file_get_metadata
data,rc,msg = make_http_request(conn, address, params, headers)
File "/usr/lib/portage/pym/getbinpkg.py", line 207, in make_http_request
response = conn.getresponse()
File "/usr/lib/python2.4/httplib.py", line 866, in getresponse
response.begin()
File "/usr/lib/python2.4/httplib.py", line 336, in begin
version, status, reason = self._read_status()
File "/usr/lib/python2.4/httplib.py", line 300, in _read_status
raise BadStatusLine(line)
httplib.BadStatusLine

Here's my make.conf:

# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /etc/make.conf.example for a more detailed example.
CFLAGS="-O2 -pipe -mtune=970 -mcpu=970 -mabi=altivec"
CXXFLAGS="-O2 -pipe -mtune=970 -mcpu=970 -mabi=altivec"
# This should not be changed unless you know exactly what you are doing. You
# should probably be using a different stage, instead.
CHOST="powerpc-unknown-linux-gnu"
PORTDIR_OVERLAY="/root/livecd/overlays/portage"
PORTAGE_BINHOST="http://ftp-chi.osuosl.org/pub/gentoo-ps3/grp32/All/"

Regular emerge works fine, but I'd really rather not build all my own binaries with this system.

I tried waiting two days after a emerge --sync before this run today.

[asong26]

Originally Posted by Psumoni

Any attempt to emerge -G something fails like this:



Here's my make.conf:



Regular emerge works fine, but I'd really rather not build all my own binaries with this system.

I tried waiting two days after a emerge --sync before this run today.

I think you need to update your portage application. For this, you should use regular emerge -av portage. Once that's done, you'll have everything running. In order to get the right version of portage with the proper bug fixes for -G flag use and the dependencies, you'll need to unmask to the latest version. Here's how you do that.

login as root / su

type

nano -w /etc/portage/package.keywords

If you already have this file, just add the line:
sys-apps/portage ~ppc64

exit nano by taping ctrl-X followed by y, then enter.

type in

emerge -pv portage

Current latest version should show as sys-apps/portage-2.1.2-r1

then just type in

emerge -v portage

Once the portage is downloaded, emerge -G functions should work fine. I hope this works out for you.
-= Double Post =-
NOTICE:

The above post is assuming that you're using the latest 64bit userland tarball install.

[Psumoni]

Hmmm... not sure if it's working right now, it now displays:

Calculating dependencies -Fetching binary package info...
Cache miss 'x' -- cache hit: 'o':
xxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxx

It's been throwing new x's up for a few minutes now.
-= Double Post =-
After a bunch of X's it started doing the download.

Thanks for the help!

[blade47167]

I don't know what will happen with what he just told you to do but hes wrong about whats going on. If you would attempt to search a bit you would see the solution. Either way...

It's because you recently synced your emerge. Refrain from using the emerge --sync command to once every 2 weeks or so. The reason its failing is because there are no current group packages to support your version. Hence -G failing to find its files. Please wait a week or so and try the emerge -G again. If you however sync again it will cause your wait to extend even longer.

[Crymson]

Yep, I agree. Blade47167's post to my comment earlier made sense. So I spent 2 days compiling Gnome.

Now that's it done though, I have Gnome, Mplayer, Audacious, and NFS setup on the PS3, and everything is working great. I love being able to stream stuff from the other systems on my network and play them.

Now if we could just get some wifi drivers... (I know, they're working on it.)

[asong26]

Your make.conf file looks correct for 32-bit userland tarball....

However, if you're using the latest 64-bit userland tarball, be sure to modify your make.conf file

from

PORTAGE_BINHOST="http://ftp-chi.osuosl.org/pub/gentoo-ps3/grp32/All/"

to

PORTAGE_BINHOST="http://ftp-chi.osuosl.org/pub/gentoo-ps3/grp64/All/"

-= Double Post =-

Originally Posted by blade47167

I don't know what will happen with what he just told you to do but hes wrong about whats going on. If you would attempt to search a bit you would see the solution. Either way...

It's because you recently synced your emerge. Refrain from using the emerge --sync command to once every 2 weeks or so. The reason its failing is because there are no current group packages to support your version. Hence -G failing to find its files. Please wait a week or so and try the emerge -G again. If you however sync again it will cause your wait to extend even longer.

Are you referring to me when you say

hes wrong

?

Updating the portage app is part of the instruction: look here:

http://overlays.gentoo.org/proj/cell...allGentooOnPS3

Here's a quote from the install instructions:

Installing GRP packages ¶

Note: Due to a number of bugs in the current stable version of portage, you must use at least portage-2.1.2-rc4-8 to install GRP over the network. If you do not have this version of portage, you should add 'sys-apps/portage ~ppc' or 'sys-apps/portage ~ppc64' to your /etc/portage/package.keywords file and then 'emerge -u portage'. In the release of 2.1.2-r1, there will also be at least one fix in the dependency resolution of binary packages.

Our GRP packages are currently hosted on three sites:

* http://ftp.osuosl.org/pub/gentoo-ps3/
* http://ftp-atl.osuosl.org/pub/gentoo-ps3/
* http://ftp-chi.osuosl.org/pub/gentoo-ps3/