Yellow Dog Linux

Hey Paul. I went ahead and made that change to the repos. (i.e) (change enabled=1 to enabled=0)
. I noticed that it loaded much quicker this time! I was just curious if I'll be missing out on a lot of good available software by changing this? I'm sure the repos I've got setup will be more than enough for my 10GIG YDL load.

NuxIT wrote:Hey Paul. I went ahead and made that change to the repos. (i.e) (change enabled=1 to enabled=0)
. I noticed that it loaded much quicker this time! I was just curious if I'll be missing out on a lot of good available software by changing this? I'm sure the repos I've got setup will be more than enough for my 10GIG YDL load.

Here's the deal.

Originally, there was nothing in YellowDog Extras. That's why we added Fedora Extras.

Then - with 6.2 - they put EPEL in there:
http://fedoraproject.org/wiki/EPEL

These packages apparently conflict with Fedora Extras. The slowdown you see is protectbase trying to reconcile the two differing repos.

billb can explain the differences between the two repos better than I can - but I think everything that's in EPEL is in Fedora Extras.

Cheers,
Paul

I cant get PS3Bodega Software Repository to work. this is what I get:

Code: Select all

[emre8041@localhost ~]$ rpm -ivh http://pleasantfiction.ipower.com/ps3linux/ps3bodega62/ppc/ps3bodega-release-6.2-2.noarch.rpm
Retrieving http://pleasantfiction.ipower.com/ps3linux/ps3bodega62/ppc/ps3bodega-release-6.2-2.noarch.rpm
error: can't create transaction lock on /var/lib/rpm/__db.000
[emre8041@localhost ~]$


???

It looks like you skipped Step 1:


1. Open a terminal window and use the su command to become the root user:

Code: Select all

su

<enter your root password>

nope I didnt

Code: Select all

[emre8041@localhost ~]$ su emre8041
Password:
[emre8041@localhost ~]$ rpm -ivh http://pleasantfiction.ipower.com/ps3linux/ps3bodega62/ppc/ps3bodega-release-6.2-2.noarch.rpm
Retrieving http://pleasantfiction.ipower.com/ps3linux/ps3bodega62/ppc/ps3bodega-release-6.2-2.noarch.rpm
error: can't create transaction lock on /var/lib/rpm/__db.000
[emre8041@localhost ~]$


Yep, you did...

Enter su by itself as shown, not with your username added. You want to be logged in as root and su by itself will do that for you.

billb wrote:Yep, you did...

Enter su by itself as shown, not with your username added. You want to be logged in as root and su by itself will do that for you.

D`OH lol ok
yeah its installed now.thanks

I did everything and now I cant use add/remove software it gives this error:
"Another application is running which is accessing software information"

EMR01 wrote:I did everything and now I cant use add/remove software it gives this error:
"Another application is running which is accessing software information"

By default the yum "updatesd" daemon is running, and sometimes it will be doing things when you try to use yum yourself. The easiest thing to do is turn it off using

system-config-services

Look for an entry called yum-updatesd.

I did a post some time back on what to do.

viewtopic.php?f=19&t=6625&p=33168&hilit=updatesd#p33168

Ron Rogers Jr. (CronoCloud)

Software Updater suddenly said there were a few dozen updates available (even though they've been on the PS3Bodega repo for a few months), including an updated kernel. I went ahead and installed, but after rebooting, got the following repeating warning during boot:

udevb[1200]: add_to_rules: unknown key 'ATTRS{idProduct}'
udevb[1200]: add_to_rules: unknown key 'ATTRS{idVendor}'

...and it fills up the screen. It didn't appear to affect operation of YDL 6.2, but it was kind of annoying. I finally narrowed it down to libmtp-0.2.6.1-1.ydl62.bdg.ppc.rpm, installed as a dependency to rhythmbox-0.11.7-5.ydl62.bdg.ppc.rpm. Uninstalling those got rid of the error. Has anyone else seen this or is there maybe something else on my system causing that library to error?

xnonsuchx wrote:Software Updater suddenly said there were a few dozen updates available (even though they've been on the PS3Bodega repo for a few months), including an updated kernel. I went ahead and installed, but after rebooting, got the following repeating warning during boot:

udevb[1200]: add_to_rules: unknown key 'ATTRS{idProduct}'
udevb[1200]: add_to_rules: unknown key 'ATTRS{idVendor}'

...and it fills up the screen. It didn't appear to affect operation of YDL 6.2, but it was kind of annoying. I finally narrowed it down to libmtp-0.2.6.1-1.ydl62.bdg.ppc.rpm, installed as a dependency to rhythmbox-0.11.7-5.ydl62.bdg.ppc.rpm. Uninstalling those got rid of the error. Has anyone else seen this or is there maybe something else on my system causing that library to error?

Those were packages that were in the testing repo (disabled by default) that were recently moved to the main repo. Thanks for the report -- I'll look into it on my system as well.

billb wrote:
Those were packages that were in the testing repo (disabled by default) that were recently moved to the main repo. Thanks for the report -- I'll look into it on my system as well.

xnonsuchx wrote:Software Updater suddenly said there were a few dozen updates available (even though they've been on the PS3Bodega repo for a few months), including an updated kernel. I went ahead and installed, but after rebooting, got the following repeating warning during boot:

udevb[1200]: add_to_rules: unknown key 'ATTRS{idProduct}'
udevb[1200]: add_to_rules: unknown key 'ATTRS{idVendor}'

...and it fills up the screen. It didn't appear to affect operation of YDL 6.2, but it was kind of annoying. I finally narrowed it down to libmtp-0.2.6.1-1.ydl62.bdg.ppc.rpm, installed as a dependency to rhythmbox-0.11.7-5.ydl62.bdg.ppc.rpm. Uninstalling those got rid of the error. Has anyone else seen this or is there maybe something else on my system causing that library to error?

Those were packages that were in the testing repo (disabled by default) that were recently moved to the main repo. Thanks for the report -- I'll look into it on my system as well.

Same result on my system, and uninstalling the libmtp (and rhythmbox) updates got rid of the error for me as well. I'll pull those updates from the main repo and try new updates in the testing repo.

Trying something interesting.

I just did a clean install of 6.2 - finally - and I'm working on the repo setup.

So - I thought I'd try something different.

I'm using the standard YDL "3", plus livna & dribble - but I'm leaving out Fedora Extras. I figured that since YellowDog Extras includes EPEL, maybe it would work without Fedora Extras.

So far - so good. I'm not sure I'm officially recommending this, but it is interesting.

Cheers,
Paul

ppietro wrote:I'm using the standard YDL "3", plus livna & dribble - but I'm leaving out Fedora Extras. I figured that since YellowDog Extras includes EPEL, maybe it would work without Fedora Extras.

Well - it mostly works. But - it seems that basically YDL 6.2 is at a higher revision than livna. So - certain things were failing - like mplayer - because the YDL repos had newer versions than livna expected.

So - it seems that ps3bodega is probably the best to roll with for 6.2.

Me? I'm back to 6.1 now. There was nothing in 6.2 that I particularly needed at the present time.

Cheers,
Paul

BTW, it appears that Fixstars recently changed its YDL 6.2 mirrorlist to only point to the mirror at OSU, which appears to have March 2010 and June 2010 file in the Updates repo that include files that don't work with YDL 6.2 on PS3. Namely, the util-linux-2.13-0.52.1.ppc.rpm update includes an updated /sbin/hwclock binary, causing YDL 6.2 on PS3 to not be able to sync its clock to the system clock and will always think it's double however many hours you are behind GMT behind the current time (e.g. if it's noon Pacific US DS time (7p GMT), it will think it's 5a the same day instead), and will show sync errors during boot/shutdown.

If you backup the /sbin/hwclock file after initial install and restore it after doing a yum update, it should work fine, but I wonder how many other newer updates may not be compatible.

UPDATE: After looking further, it looks like Fixstar's main repo now just resolves to the OSU site. After checking several other working repos, only the OSU site has the March-June '10 newer files in the updates repo, so I'm not sure if something weird (and untested) is going on or if the other mirrors just haven't added those updates yet. It's still disconcerting to me, so for the time-being, I've changed my YDL repo files and created my own mlist mirror list files (w/o the OSU one included).