On Sunday 24 June 2012 03:06:14 Chris Geldenhuis did opine:

On 06/24/2012 02:47 AM, Gene Heskett wrote:

...

Greets;

This centos6.2 system seems to have python-2.6.6, but that is turning into a huge problem because I now have a backlog of about 40 packages that will not upgrade because they all need python 2.4.

That, and importing gpg keys doesn't seem to be helping in that regard.

But first, how to go about down grading python to 2.4?

Thanks.

Cheers, Gene

Hi Gene,

Down grading to Python 2.4 will break your CentOS 6.2 system. Rather install python 2.4 side by side with 2.6 and point the packages that need to use 2.4 to it by changing the first line in the scripts to #!/usr/bin/python2.4 instead of #!/usr/bin/python.

I have had to do this the other way around on CentOS nad Red Hat 4 systems where I needed newer features and it work well.

The instructions on how to do this are included in the tarball downloaded from the Python site.

ChrisG

This is not something that is available via yum?

In which case why do I have 30 or 40 packages that are being called security updates, released in the last week, that still need the older python? Something doesn't grok here. Like maybe I have the wrong repos enabled?

Maybe, a yum repolist says rpmfusion is for el5, maybe that is what I need to fix. How?

Thanks.

Cheers, Gene

On Sunday 24 June 2012 07:25:21 Veli-Pekka Kestilä did opine:

On 24.6.2012 10:12, Gene Heskett wrote:

...

On Sunday 24 June 2012 03:06:14 Chris Geldenhuis did opine:

...

On 06/24/2012 02:47 AM, Gene Heskett wrote:

...

Greets;

This centos6.2 system seems to have python-2.6.6, but that is turning into a huge problem because I now have a backlog of about 40 packages that will not upgrade because they all need python 2.4.

This is not something that is available via yum?

In which case why do I have 30 or 40 packages that are being called security updates, released in the last week, that still need the older python? Something doesn't grok here. Like maybe I have the wrong repos enabled?

Maybe, a yum repolist says rpmfusion is for el5, maybe that is what I need to fix. How?

Thanks.

Cheers, Gene

Remove your old rpmfusion repository package for el5, and follow the instruction in http://rpmfusion.org/Configuration/ to install the new one.

Attempting that get this in an error box: The name org.freedesktop.PackageKit was not provided by any .service files

But I believe it did download the file(s). However, doing the command line version also threw some errors: Revealing that the epel is set for 5.4. Hard to find the correct linkage instructs, they are quite a few entries down from the top google hits when searching.

Its an hour later, and I have installed and renamed the rpmnew's, even nuked a few packages it downloaded but couldn't install, and on a restart, yum is still showing me 21 packages to update, all from an el5 repo. There is not any file surviving in yum.repos.d that contains a reference to el5, so where is that cache being held so I can nuke it?

Thanks.

After that you should remove all el5 packages which were installer from rpmfusion for el5.

-vpk

The only file that had an el5 mark was adobe's flash plugin, which didn't work in konqerer anyway, so I changed the pref to firefox because it did work there. But I had yum nuke it anyway.

Thanks & Cheers, Gene

On Sunday 24 June 2012 12:43:23 Leonard den Ottolander did opine:

Hello Gene,

On Sun, 2012-06-24 at 08:40 -0400, Gene Heskett wrote:

...

yum is still showing me 21 packages to update, all from an el5 repo.\

You can figure out what repo that is by "rpm -qi"ing one of the packages that is causing you trouble. Remove all offending packages, then remove the repo rpm (rpm -e rpmforge-release or epel-release or even another one, that is for you to figure out).

After you got rid of the offending packages and repo-release you can now install the correct repo-release for the OS version you are using and add the packages you just removed.

Regards, Leonard.

There are no surviving el5 packages on the system, including in the .repo files of yum.repos.d

But if I fire up yumex, well over half the files presented say they are el5 coming from rpmfusion, but my rpmfusion .repo's are all set for el-6 as can be seen by this:

[root@coyote yum.repos.d]# grep el rpmfusion-*.repo rpmfusion-free- updates.repo:#baseurl=http://download1.rpmfusion.org/free/el/updates/6/$basearch/ rpmfusion-free- updates.repo:mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=free- el-updates-released-6&arch=$basearch rpmfusion-free-updates.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY- rpmfusion-free-el-6 rpmfusion-free- updates.repo:#baseurl=http://download1.rpmfusion.org/free/el/updates/6/$basearch/debug/ rpmfusion-free- updates.repo:mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=free- el-updates-released-debug-6&arch=$basearch rpmfusion-free-updates.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY- rpmfusion-free-el-6 rpmfusion-free- updates.repo:#baseurl=http://download1.rpmfusion.org/free/el/updates/6/SRPMS/ rpmfusion-free- updates.repo:mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=free- el-updates-released-source-6&arch=$basearch rpmfusion-free-updates.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY- rpmfusion-free-el-6 rpmfusion-free-updates- testing.repo:#baseurl=http://download1.rpmfusion.org/free/el/updates/testing/6/$basearch/ rpmfusion-free-updates- testing.repo:mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=free- el-updates-testing-6&arch=$basearch rpmfusion-free-updates-testing.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG- KEY-rpmfusion-free-el-6 rpmfusion-free-updates- testing.repo:#baseurl=http://download1.rpmfusion.org/free/el/updates/testing/6/$basearch/debug/ rpmfusion-free-updates- testing.repo:mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=free- el-updates-testing-debug-6&arch=$basearch rpmfusion-free-updates-testing.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG- KEY-rpmfusion-free-el-6 rpmfusion-free-updates- testing.repo:#baseurl=http://download1.rpmfusion.org/free/el/updates/testing/6/SRPMS/ rpmfusion-free-updates- testing.repo:mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=free- el-updates-testing-source-6&arch=$basearch rpmfusion-free-updates-testing.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG- KEY-rpmfusion-free-el-6 rpmfusion-nonfree- updates.repo:#baseurl=http://download1.rpmfusion.org/nonfree/el/updates/testing/6/$basearch/ rpmfusion-nonfree- updates.repo:mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree- el-updates-testing-6&arch=$basearch rpmfusion-nonfree-updates.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY- rpmfusion-nonfree-el-6 rpmfusion-nonfree- updates.repo:#baseurl=http://download1.rpmfusion.org/nonfree/el/updates/testing/6/$basearch/debug/ rpmfusion-nonfree- updates.repo:mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree- el-updates-testing-debug-6&arch=$basearch rpmfusion-nonfree-updates.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY- rpmfusion-nonfree-el-6 rpmfusion-nonfree- updates.repo:#baseurl=http://download1.rpmfusion.org/nonfree/el/updates/testing/6/SRPMS/ rpmfusion-nonfree- updates.repo:mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree- el-updates-testing-source-6&arch=$basearch rpmfusion-nonfree-updates.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY- rpmfusion-nonfree-el-6 rpmfusion- nonfree.updates.repo:#baseurl=http://download1.rpmfusion.org/nonfree/el/updates/6/$basearch/ rpmfusion- nonfree.updates.repo:mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree- el-updates-released-6&arch=$basearch rpmfusion-nonfree.updates.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY- rpmfusion-nonfree-el-6 rpmfusion- nonfree.updates.repo:#baseurl=http://download1.rpmfusion.org/nonfree/el/updates/6/$basearch/debug/ rpmfusion- nonfree.updates.repo:mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree- el-updates-released-debug-6&arch=$basearch rpmfusion-nonfree.updates.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY- rpmfusion-nonfree-el-6 rpmfusion- nonfree.updates.repo:#baseurl=http://download1.rpmfusion.org/nonfree/el/updates/6/SRPMS/ rpmfusion- nonfree.updates.repo:mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree- el-updates-released-source-6&arch=$basearch rpmfusion-nonfree.updates.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY- rpmfusion-nonfree-el-6

But I don't see anything but el-6 above. So something is well and truly knackered. The question is what?

Thanks & Cheers, Gene

On Sunday 24 June 2012 16:48:31 Leonard den Ottolander did opine:

Hello Gene,

On Sun, 2012-06-24 at 12:55 -0400, Gene Heskett wrote:

...

There are no surviving el5 packages on the system, including in the .repo files of yum.repos.d

But if I fire up yumex, well over half the files presented say they are el5 coming from rpmfusion,

Those two statements seem contradictory. Did you actually query those packages to establish their origin?

So you tell us you only have el6 repos enabled. Perhaps someone installed the offending packages manually or accidentally used the wrong repo before? Get rid of the offending ones and reinstall using the correct repo.

That 'someone' would likely be me, and no I didn't qi each package because there are no *.el-5* packages now installed. These are the packages it is showing me that I _could_ install, and nearly every blessed one of them has a dependency on python-2.4. Why yumex is even showing me el5 files is a puzzle I'm apparently not equipt to sort, it may as well be a basket of rattlesnakes. You could probably say I'm getting too old for this at 77, but I'm a retired broadcast CE, one who quit school at 14 and went out to fix these newfangled things called tv's in the later '40's, and have had a scope probe or four and a hot soldering iron handy ever since. Generally, electronics holds no puzzles for me, and I've had a C.E.T. since '72, and a 1st phone since '61.

I see what someone meant when they said centos was a stripped mostly server distro. Trying to nail kde and a working audio system to it reminds me of trying to nail jelly to a tree, everything you try to install winds up splattered on the floor.

So I've saved off my email corpus, and just burned a ubuntu-10.04-linuxcnc install cd, so by this time tomorrow I should have the same distro on all 4 machines here. Opencascade-libs, which supports all the cad design proggys like freecad, heekscad/cnc, openscam and a few others seem to be only built in .debs, so while I don't exactly love how ubuntu handles networking or its gui, once you get it configured, it Just Works(TM), including nfs shares, something I had a heck of a time making work on pclos. With the same config files installed here on centos6, nfs is dead, no hits, no runs & no errors logged.

Regards, Leonard.

Thanks for the reply Leonard, but I don't think centos and I will be able to be friends when yum is so easily confused. With synaptic, I might give it another week just in case I could sort this out. Synaptic for instance, when it encounters a dependency, looks it up and says 'you need these packages to resolve dependencies', shows you a list and asks if its ok to add them to the install list. Yum just reports the failure and does a segfault like exit, exactly as it was doing when I bailed out on fedora at about F-8, several years ago now.

Cheers Leonard, Gene

On Sunday 24 June 2012 20:43:15 Leonard den Ottolander did opine:

Hello Gene,

On Sun, 2012-06-24 at 17:21 -0400, Gene Heskett wrote:

...

These are the packages it is showing me that I _could_ install, and nearly every blessed one of them has a dependency on python-2.4. Why yumex is even showing me el5 files is a puzzle I'm apparently not equipt to sort,

I'm not familiar with yumex, just using plain yum and rpm. Perhaps using this non standard package manager is what is causing all your troubles. Could it be yumex uses hard coded (or configurable) paths and you installed a yumex for the wrong release? Where did you get that yumex from? And why not use plain yum? You are fitting all sorts of things onto a system that you are not familiar with, no wonder you meet a few bumps ;-) .

...

I see what someone meant when they said centos was a stripped mostly server distro.

It's a rebuild from Red Hat Enterprise Linux, which is based on Fedora. Since it's an enterprise distro it provides a limited range of packages and they are rather dated to safeguard functional, ABI and API compatibility for a period of 5 years.

You might want to give Fedora a try, it supports *way* more packages by default, but I have to warn you that it used to come with the warning that "it eats babies", in the sense that it's bleeding edge and might have some rough edges.

It also kills kittens.

...

Trying to nail kde and a working audio system to it reminds me of trying to nail jelly to a tree, everything you try to install winds up splattered on the floor.

I suppose that's just fallout from the issue you are having, things like this should work out of the box assuming your hardware is not too exotic or too new. But you have to be careful about which 3rd party repos you enable, which is probably true for any distro that supports those.

...

With the same config files installed here on centos6, nfs is dead, no hits, no runs & no errors logged.

CentOS/RHEL make you start services explicitly instead of enabling anything by default. Are both portmap and nfs running?

No clue at this time. IMO the 64 bit scene is just as broken as it was 3 years ago when I had a 64 bit version intended for AMD (Phenom quad core here) installed for about 2 hours.

...

Thanks for the reply Leonard, but I don't think centos and I will be able to be friends when yum is so easily confused.

yum != yumex . I'm quite sure one can screw up Ubuntu too, but if you're more comfortable with Ubuntu then by any means use it.

...

With synaptic, I might give it another week just in case I could sort this out. Synaptic for instance, when it encounters a dependency, looks it up and says 'you need these packages to resolve dependencies', shows you a list and asks if its ok to add them to the install list.

If your repos are set up correctly yum should behave in a similar way. This is why yum was added on top of rpm. The reason yum bails out is because it cannot find those dependencies in any of the repos as they have incorrect versions. What is the cause of that is not clear to me but something is insisting on looking at el5 repos and it's definitely *not* any of the packages that come with CentOS 6 by default.

If you are still interested in getting CentOS 6 running I suggest you do a clean install and only start adding 3rd party repos once you have the system up and running.

If I was to do a clean install, it would sure be 32 bit. But I don't have 32 bit media on site. Does the 32 bit version have the opencascade kit?

Cheers, Leonard.

Cheers Leonard, Gene

On 25/6/2012 3:48 πμ, Gene Heskett wrote:

IMO the 64 bit scene is just as broken as it was 3 years ago when I had a 64 bit version intended for AMD (Phenom quad core here) installed for about 2 hours.

We are using always 64-bit only installations of CentOS 5 and 6 (including all packages) for years without problems.

Nick

On 06/24/12 5:48 PM, Gene Heskett wrote:

IMO the 64 bit scene is just as broken as it was 3 years ago when I had a 64 bit version intended for AMD (Phenom quad core here) installed for about 2 hours.

WHAT is broken about 'the 64 bit scene' ?!? I have 64 bit Opteron systems happily running CentOS 3 in my lab, zero problems related to the bitness of them. These servers and installs are over 5 years old (HP DL585, with 4 x Opteron 850 and 8GB ram, new in 2005).

IMHO, its insane to be installing 32 bits on modern servers that have 12-48gb of ram, and dozens of terabytes of disk space in the 21st century. THATS broken.

On 6/24/2012 12:55 PM, Gene Heskett wrote:

On Sunday 24 June 2012 12:43:23 Leonard den Ottolander did opine:

...

Hello Gene,

On Sun, 2012-06-24 at 08:40 -0400, Gene Heskett wrote:

...

yum is still showing me 21 packages to update, all from an el5 repo.\

You can figure out what repo that is by "rpm -qi"ing one of the packages that is causing you trouble. Remove all offending packages, then remove the repo rpm (rpm -e rpmforge-release or epel-release or even another one, that is for you to figure out).

After you got rid of the offending packages and repo-release you can now install the correct repo-release for the OS version you are using and add the packages you just removed.

Regards, Leonard.

There are no surviving el5 packages on the system, including in the .repo files of yum.repos.d

But if I fire up yumex, well over half the files presented say they are el5 coming from rpmfusion, but my rpmfusion .repo's are all set for el-6 as can be seen by this:

[root@coyote yum.repos.d]# grep el rpmfusion-*.repo rpmfusion-free- updates.repo:#baseurl=http://download1.rpmfusion.org/free/el

But I don't see anything but el-6 above. So something is well and truly knackered. The question is what?

Thanks & Cheers, Gene

yum clean all might help you. Tony Schreiner

On Sun, Jun 24, 2012 at 11:55 AM, Gene Heskett gheskett@wdtv.com wrote:

...

...

There are no surviving el5 packages on the system, including in the .repo files of yum.repos.d

Did you use yum to remove the packages?

Hello Gene,

On Sun, 2012-06-24 at 12:55 -0400, Gene Heskett wrote:

There are no surviving el5 packages on the system, including in the .repo files of yum.repos.d

No _surviving_ el5 packages. So you *did* have el5 repos enabled earlier on? Perhaps yumex is caching that old configuration. Just a guess. As I said, I have no experience with yumex so I couldn't tell you off hand where to look, but /etc/yumex or /etc/yumex.d come to mind.

Regards, Leonard.