Hi all,
I'm trying to upgrade a new and fully updated FC6 laptop to rawhide for testing, however when I try and run 'yum upgrade' or 'yum update' I get the following:
--> Running transaction check --> Processing Dependency: python-elementtree for package: yum --> Processing Dependency: python(abi) = 2.4 for package: yum --> Processing Dependency: firstboot-tui = 1.4.28 for package: firstboot --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Package firstboot-tui.noarch 0:1.4.28-2.fc7 set to be updated --> Running transaction check --> Processing Dependency: python-elementtree for package: yum --> Processing Dependency: python(abi) = 2.4 for package: yum --> Finished Dependency Resolution Error: Missing Dependency: python(abi) = 2.4 is needed by package yum
Where does this come into it?
tor, 18 01 2007 kl. 21:27 +1100, skrev Steven Haigh:
Hi all,
I'm trying to upgrade a new and fully updated FC6 laptop to rawhide for testing, however when I try and run 'yum upgrade' or 'yum update' I get the following:
--> Running transaction check --> Processing Dependency: python-elementtree for package: yum --> Processing Dependency: python(abi) = 2.4 for package: yum --> Processing Dependency: firstboot-tui = 1.4.28 for package: firstboot --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Package firstboot-tui.noarch 0:1.4.28-2.fc7 set to be updated --> Running transaction check --> Processing Dependency: python-elementtree for package: yum --> Processing Dependency: python(abi) = 2.4 for package: yum --> Finished Dependency Resolution Error: Missing Dependency: python(abi) = 2.4 is needed by package yum
Where does this come into it?
I have a feeling that is because the yum in FC6 (at least updates-testing) is newer than the one in Rawhide.
- David Nielsen
On Thursday 18 January 2007 11:33, David Nielsen wrote:
Error: Missing Dependency: python(abi) = 2.4 is needed by package yum
Where does this come into it?
I have a feeling that is because the yum in FC6 (at least updates-testing) is newer than the one in Rawhide.
Yep. Waiting for upstream yum 3.1, which is rolling in a bunch of patches to the 3.0(.3) version.
On 19/01/2007, at 3:38 AM, Jesse Keating wrote:
On Thursday 18 January 2007 11:33, David Nielsen wrote:
Error: Missing Dependency: python(abi) = 2.4 is needed by package yum
Where does this come into it?
I have a feeling that is because the yum in FC6 (at least updates-testing) is newer than the one in Rawhide.
Yep. Waiting for upstream yum 3.1, which is rolling in a bunch of patches to the 3.0(.3) version.
Is there a way I can make the update happen anyhow without downgrading yum?
I did see something a while back about the --skip-broken (i think) option, however I can't seem to see this option available.
Steven Haigh wrote:
On 19/01/2007, at 3:38 AM, Jesse Keating wrote:
On Thursday 18 January 2007 11:33, David Nielsen wrote:
Error: Missing Dependency: python(abi) = 2.4 is needed by package yum
Where does this come into it?
I have a feeling that is because the yum in FC6 (at least updates-testing) is newer than the one in Rawhide.
Yep. Waiting for upstream yum 3.1, which is rolling in a bunch of patches to the 3.0(.3) version.
Is there a way I can make the update happen anyhow without downgrading yum?
I did see something a while back about the --skip-broken (i think) option, however I can't seem to see this option available.
That is part of the yum-skip-broken plugin in Fedora Extras.
Rahul
On 19/01/2007, at 10:07 AM, Rahul Sundaram wrote:
Steven Haigh wrote:
On 19/01/2007, at 3:38 AM, Jesse Keating wrote:
On Thursday 18 January 2007 11:33, David Nielsen wrote:
Error: Missing Dependency: python(abi) = 2.4 is needed by package yum
Where does this come into it?
I have a feeling that is because the yum in FC6 (at least updates-testing) is newer than the one in Rawhide.
Yep. Waiting for upstream yum 3.1, which is rolling in a bunch of patches to the 3.0(.3) version.
Is there a way I can make the update happen anyhow without downgrading yum? I did see something a while back about the --skip-broken (i think) option, however I can't seem to see this option available.
That is part of the yum-skip-broken plugin in Fedora Extras.
Looks like this still won't work as glib (or glibc?) also depends on dependencies that fall within the updated yum packages. This means without reverting yum back to the rawhide version, it's currently not possible to do an upgrade from FC6 to the current rawhide.
A newer version of yum in rawhide would probably fix this.
On Saturday 20 January 2007 10:59, Steven Haigh wrote:
Looks like this still won't work as glib (or glibc?) also depends on dependencies that fall within the updated yum packages. This means without reverting yum back to the rawhide version, it's currently not possible to do an upgrade from FC6 to the current rawhide.
A newer version of yum in rawhide would probably fix this.
We're waiting for the the new upstream version of yum.
On 21/01/2007, at 3:18 AM, Jesse Keating wrote:
On Saturday 20 January 2007 10:59, Steven Haigh wrote:
Looks like this still won't work as glib (or glibc?) also depends on dependencies that fall within the updated yum packages. This means without reverting yum back to the rawhide version, it's currently not possible to do an upgrade from FC6 to the current rawhide.
A newer version of yum in rawhide would probably fix this.
We're waiting for the the new upstream version of yum.
Would it cause any issues downgrading to the rawhide yum? For what reason is the rawhide yum older than the released yum version in the stable/updates area?
On Saturday 20 January 2007 11:35, Steven Haigh wrote:
Would it cause any issues downgrading to the rawhide yum? For what reason is the rawhide yum older than the released yum version in the stable/updates area?
We had a specific bug we wanted to fix in FC6. Rawhide has some other patches to make it work with python2.5, and juggling in the rest of the 3.0 patches I guess was not ideal. 3.1 is supposed to be coming very soon from upstream and yum will get updated then. Most definitely it will either get a new upstream release, or the forward port before Test1.
-
David Nielsen -
Jesse Keating -
Rahul Sundaram -
Steven Haigh