I decided to enable rawhide on my test F10 system, and do a yum update.
I get a lot of dependency failures like:
setroubleshoot-2.0.12-3.fc10.noarch from installed has depsolving problems --> Missing Dependency: python(abi) = 2.5 is needed by package setroubleshoot-2.0.12-3.fc10.noarch (installed)
Any suggestions?
TIA Fulko
On 3/01/2009 9:54 AM, Fulko Hew wrote:
I decided to enable rawhide on my test F10 system, and do a yum update.
I get a lot of dependency failures like:
setroubleshoot-2.0.12-3.fc10.noarch from installed has depsolving problems --> Missing Dependency: python(abi) = 2.5 is needed by package setroubleshoot-2.0.12-3.fc10.noarch (installed)
Any suggestions?
TIA Fulko
why did you enable rawhide? this isnt a support channel. use the irc channel or fedoraforum
On Fri, Jan 2, 2009 at 6:11 PM, Greg spowd@bigpond.com wrote:
On 3/01/2009 9:54 AM, Fulko Hew wrote:
I decided to enable rawhide on my test F10 system, and do a yum update.
I get a lot of dependency failures like:
setroubleshoot-2.0.12-3.fc10.noarch from installed has depsolving problems --> Missing Dependency: python(abi) = 2.5 is needed by package setroubleshoot-2.0.12-3.fc10.noarch (installed)
Any suggestions?
TIA Fulko
why did you enable rawhide? this isnt a support channel. use the irc channel or fedoraforum
Sorry. I thought fedora-test was for testing rawhide? ;-(
On 3/01/2009 10:13 AM, Fulko Hew wrote:
On Fri, Jan 2, 2009 at 6:11 PM, Gregspowd@bigpond.com wrote:
On 3/01/2009 9:54 AM, Fulko Hew wrote:
I decided to enable rawhide on my test F10 system, and do a yum update.
I get a lot of dependency failures like:
setroubleshoot-2.0.12-3.fc10.noarch from installed has depsolving problems --> Missing Dependency: python(abi) = 2.5 is needed by package setroubleshoot-2.0.12-3.fc10.noarch (installed)
Any suggestions?
TIA Fulko
why did you enable rawhide? this isnt a support channel. use the irc channel or fedoraforum
Sorry. I thought fedora-test was for testing rawhide? ;-(
it is but your not giving much details of what you are actually testing?. by the looks of it you have fc10 rpms
from what i understand you were using fedora10 an installed Fedora11 from enabling rawhide. correct method for testing Fedora11 is downloading the boot.iso an installing fc11 that way an testing it alongside fc10. you say your getting a lot of deps but what exactly did you install from rawhide repo? if you can figure that one out im sure you'll fix it
On Fri, Jan 2, 2009 at 6:40 PM, Greg spowd@bigpond.com wrote:
On 3/01/2009 10:13 AM, Fulko Hew wrote:
On Fri, Jan 2, 2009 at 6:11 PM, Gregspowd@bigpond.com wrote:
On 3/01/2009 9:54 AM, Fulko Hew wrote:
I decided to enable rawhide on my test F10 system, and do a yum update.
I get a lot of dependency failures like:
setroubleshoot-2.0.12-3.fc10.noarch from installed has depsolving problems --> Missing Dependency: python(abi) = 2.5 is needed by package setroubleshoot-2.0.12-3.fc10.noarch (installed)
Any suggestions?
TIA Fulko
why did you enable rawhide? this isnt a support channel. use the irc channel or fedoraforum
Sorry. I thought fedora-test was for testing rawhide? ;-(
it is but your not giving much details of what you are actually testing?. by the looks of it you have fc10 rpms
I thought I'd be testing F11 (as updated from F10 via rawhide.
from what i understand you were using fedora10 an installed Fedora11 from enabling rawhide. correct method for testing Fedora11 is downloading the boot.iso an installing fc11
Oh! I was led to believe from
https://fedoraproject.org/wiki/Releases/Rawhide#To_update_to_rawhide_via_yum
that I could move to Rawhide from F10
that way an testing it alongside fc10. you say your getting a lot of deps but what exactly did you install from rawhide repo?
Technically, I didn't install anything from rawhide, I simply enabled the rawhide repo as per the URL above, and did 'yum update'.
if you can figure that one out im sure you'll fix it
The trouble is that it is complaining about "Missing Dependency: python(abi) = 2.5" for a vast number of packages. Yum updated the system to python 2.5.2 but that doesn't help me to understand what package??? "python(abi)" is? At first I thought it was an unusually named package, then I thought It was a version of python, but downgrading python didn't help either.
It seems as thought the rawhide packages need python 2.5 and I now have python 2.5.2 installed???
So I'm at a loss to understand exactly what's missing/wrong.
(My ultimate goal was to find out if KDE 4.2 was packaged for testing yet, and if so, did it now contain fixes for the missing functionality, that KDE 3.5 has, that I need/want in 4.x.)
On 3/01/2009 11:00 AM, Fulko Hew wrote:
Technically, I didn't install anything from rawhide, I simply enabled the rawhide repo as per the URL above, and did 'yum update'.
if you wanna test KDE4.2 for Fedora10 Rex Dieter has made a LiveCD to test in Fedora10 http://rdieter.livejournal.com/11344.html http://kde-redhat.sourceforge.net/ . do you know for sure that you havent gotten any fedora11 rpms mixed with fedora10? first i'd be typing
rpm -qa|grep fc11
On 1/2/09, Fulko Hew fulko.hew@gmail.com wrote:
On Fri, Jan 2, 2009 at 6:40 PM, Greg spowd@bigpond.com wrote:
On 3/01/2009 10:13 AM, Fulko Hew wrote:
On Fri, Jan 2, 2009 at 6:11 PM, Gregspowd@bigpond.com wrote:
On 3/01/2009 9:54 AM, Fulko Hew wrote:
I decided to enable rawhide on my test F10 system, and do a yum update.
I get a lot of dependency failures like:
setroubleshoot-2.0.12-3.fc10.noarch from installed has depsolving problems --> Missing Dependency: python(abi) = 2.5 is needed by package setroubleshoot-2.0.12-3.fc10.noarch (installed)
Any suggestions?
TIA Fulko
why did you enable rawhide? this isnt a support channel. use the irc channel or fedoraforum
Sorry. I thought fedora-test was for testing rawhide? ;-(
it is but your not giving much details of what you are actually testing?. by the looks of it you have fc10 rpms
I thought I'd be testing F11 (as updated from F10 via rawhide.
from what i understand you were using fedora10 an installed Fedora11 from enabling rawhide. correct method for testing Fedora11 is downloading the boot.iso an installing fc11
Oh! I was led to believe from
https://fedoraproject.org/wiki/Releases/Rawhide#To_update_to_rawhide_via_yum
that I could move to Rawhide from F10
that way an testing it alongside fc10. you say your getting a lot of deps but what exactly did you install from rawhide repo?
Technically, I didn't install anything from rawhide, I simply enabled the rawhide repo as per the URL above, and did 'yum update'.
if you can figure that one out im sure you'll fix it
The trouble is that it is complaining about "Missing Dependency: python(abi) = 2.5" for a vast number of packages. Yum updated the system to python 2.5.2 but that doesn't help me to understand what package??? "python(abi)" is? At first I thought it was an unusually named package, then I thought It was a version of python, but downgrading python didn't help either.
It seems as thought the rawhide packages need python 2.5 and I now have python 2.5.2 installed???
So I'm at a loss to understand exactly what's missing/wrong.
(My ultimate goal was to find out if KDE 4.2 was packaged for testing yet, and if so, did it now contain fixes for the missing functionality, that KDE 3.5 has, that I need/want in 4.x.)
Did you have F10 updates-testing enabled? Either way, the EVR in rawhide might be lower. You can remove/re-install the packages, try --skip-broken, and combinations therein.
jerry
On Fri, 2009-01-02 at 19:00 -0500, Fulko Hew wrote:
The trouble is that it is complaining about "Missing Dependency: python(abi) = 2.5" for a vast number of packages. Yum updated the system to python 2.5.2 but that doesn't help me to understand what package??? "python(abi)" is? At first I thought it was an unusually named package, then I thought It was a version of python, but downgrading python didn't help either.
It is a virtual Provides provided by the python package.
It seems as thought the rawhide packages need python 2.5 and I now have python 2.5.2 installed???
No, they need 2.6. The python package is getting updated, but other packages that depend on python are not, therefore leading them to depend on an older python(abi).
Fulko Hew wrote:
(My ultimate goal was to find out if KDE 4.2 was packaged for testing yet, and if so, did it now contain fixes for the missing functionality, that KDE 3.5 has, that I need/want in 4.x.)
I'd suggest using the packages in the kde-redhat testing repository instead. Rawhide is not intended for daily use, it's for development and testing only. There can be broken dependencies like the one you're seeing in Rawhide. (Actually, in this case, the broken dependency is due to the package in the F10 updates having a higher Epoch-Version-Release (EVR) than the one in Rawhide, but there are also some dependencies which are just broken, for example packages which failed to rebuild for Python 2.6 for some reason.)
Kevin Kofler
Fulko Hew wrote:
On Fri, Jan 2, 2009 at 6:40 PM, Greg spowd@bigpond.com wrote:
On 3/01/2009 10:13 AM, Fulko Hew wrote:
On Fri, Jan 2, 2009 at 6:11 PM, Gregspowd@bigpond.com wrote:
On 3/01/2009 9:54 AM, Fulko Hew wrote:
I decided to enable rawhide on my test F10 system, and do a yum update.
I get a lot of dependency failures like:
setroubleshoot-2.0.12-3.fc10.noarch from installed has depsolving problems --> Missing Dependency: python(abi) = 2.5 is needed by package setroubleshoot-2.0.12-3.fc10.noarch (installed)
Any suggestions?
TIA Fulko
why did you enable rawhide? this isnt a support channel. use the irc channel or fedoraforum
Sorry. I thought fedora-test was for testing rawhide? ;-(
it is but your not giving much details of what you are actually testing?. by the looks of it you have fc10 rpms
I thought I'd be testing F11 (as updated from F10 via rawhide.
from what i understand you were using fedora10 an installed Fedora11 from enabling rawhide. correct method for testing Fedora11 is downloading the boot.iso an installing fc11
Oh! I was led to believe from
https://fedoraproject.org/wiki/Releases/Rawhide#To_update_to_rawhide_via_yum
that I could move to Rawhide from F10
that way an testing it alongside fc10. you say your getting a lot of deps but what exactly did you install from rawhide repo?
Technically, I didn't install anything from rawhide, I simply enabled the rawhide repo as per the URL above, and did 'yum update'.
if you can figure that one out im sure you'll fix it
The trouble is that it is complaining about "Missing Dependency: python(abi) = 2.5" for a vast number of packages. Yum updated the system to python 2.5.2 but that doesn't help me to understand what package??? "python(abi)" is? At first I thought it was an unusually named package, then I thought It was a version of python, but downgrading python didn't help either.
It seems as thought the rawhide packages need python 2.5 and I now have python 2.5.2 installed???
So I'm at a loss to understand exactly what's missing/wrong.
(My ultimate goal was to find out if KDE 4.2 was packaged for testing yet, and if so, did it now contain fixes for the missing functionality, that KDE 3.5 has, that I need/want in 4.x.)
Just to add to your confusion :-(
I did your route. I installed F10 distro. I then changed the repo to rawhide, then attempted to use yum update. Initially I got a lot of conflicts between F10 and F11, but I simply used 'yum erase xxxxx' because I was at an early stage, and then tried 'yum update' again. This I time succeeded, except for items like 'python abi=2.5'.
That is basically where I am these days, after a lot of running yum updates on any given day. It would take me time, much more than you would have to spare, to do the following: yum list updates >yum.list then with a window open on 'yum.list', I would use yum -y update x* where would be the first one or more letters of a subset of files I wished to update. That is a painful method and uses regular expressions to make a quick selection list.
Ideally, I should have a script try each file, individually. But that would take hours and as it is, sometimes I spend to 2 or 3 hrs to work through the list of updates and seldom get below 300 pkgs waiting for dependencies.
In your case, you might wish to use koji. I might remove the blocking issues so you can get a look at the area you are interested. Unlike me, you are not a concerned the F11 development is 'pure rawhide'.
--- On Sat, 1/3/09, glenn gsimpson@mountaincable.net wrote:
Ideally, I should have a script try each file, individually. But that would take hours and as it is, sometimes I spend to 2 or 3 hrs to work through the list of updates and seldom get below 300 pkgs waiting for dependencies.
In your case, you might wish to use koji. I might remove the blocking issues so you can get a look at the area you are interested. Unlike me, you are not a concerned the F11 development is 'pure rawhide'.
-- Glenn Simpson VE3DSP Hamilton, Ont
--
It might be better to remove all packages with python and their dependencies and then reinstall them. This way everything gets updated and moved on. Otherwise he would have to update everytime selectively and skip those packages time and time again till they would get resolved :)
At the beginning I ran into the same problem, but thanks to several members on the list, I quickly fixed the issue(s) by removing the packages one at a time till yum update pulled in all the new packages and their deps.
Regards,
Antonio
On Sat, Jan 03, 2009 at 10:12:44 -0800, Antonio Olivares olivares14031@yahoo.com wrote:
It might be better to remove all packages with python and their dependencies and then reinstall them. This way everything gets updated and moved on. Otherwise he would have to update everytime selectively and skip those packages time and time again till they would get resolved :)
Did you actually try that? I wouldn't recommend that as a lot of stuff depends on python (including yum). If someone is having trouble handling a yum update, they probably aren't going to have much luck doing an update using what's left of the system after removing python and all of it's dependencies.
--- On Sat, 1/3/09, Bruno Wolff III bruno@wolff.to wrote:
From: Bruno Wolff III bruno@wolff.to Subject: Re: missing dependency python(abi) = 2.5 for package: ... To: "Antonio Olivares" olivares14031@yahoo.com Cc: "glenn" gsimpson@mountaincable.net, fedora-test-list@redhat.com Date: Saturday, January 3, 2009, 10:18 AM On Sat, Jan 03, 2009 at 10:12:44 -0800, Antonio Olivares olivares14031@yahoo.com wrote:
It might be better to remove all packages with python
and their dependencies and then reinstall them. This way everything gets updated and moved on. Otherwise he would have to update everytime selectively and skip those packages time and time again till they would get resolved :)
Did you actually try that? I wouldn't recommend that as a lot of stuff depends on python (including yum). If someone is having trouble handling a yum update, they probably aren't going to have much luck doing an update using what's left of the system after removing python and all of it's dependencies.
I looked at the packages with the conflicts and I removed them either with rpm -e or with yum erase package_name.rpm. Then I ran yum update successfully. At that time, only about 3 or 4 packages were removed so that I can yum update. At this time, this might be different but it worked for me. I have 3 machines running rawhide, only 1 fails to load X it freezes and does nothing. It works on level 3 though. YMMV with removing the packages with the conflicts.
Regards,
Antonio
On Sat, Jan 03, 2009 at 10:34:41 -0800, Antonio Olivares olivares14031@yahoo.com wrote:
I looked at the packages with the conflicts and I removed them either with rpm -e or with yum erase package_name.rpm. Then I ran yum update successfully. At that time, only about 3 or 4 packages were removed so that I can yum update. At this time, this might be different but it worked for me. I have 3 machines running rawhide, only 1 fails to load X it freezes and does nothing. It works on level 3 though. YMMV with removing the packages with the conflicts.
That's a non-sequitor. I was referring your advice to try removing python before doing an upgrade. The above advice is reasonable and is close to what I did.
On Sat, 2009-01-03 at 10:40 +1100, Greg wrote:
from what i understand you were using fedora10 an installed Fedora11 from enabling rawhide. correct method for testing Fedora11 is downloading the boot.iso an installing fc11 that way an testing it alongside fc10.
Actually, both of them are valid. The thing is that some maintainers (perhaps rightfully) believe that stable releases are more important than Rawhide and so package EVRs in stable can be higher than in Rawhide, leading to update issues.
Fulko Hew wrote:
On Fri, Jan 2, 2009 at 6:11 PM, Greg spowd@bigpond.com wrote:
On 3/01/2009 9:54 AM, Fulko Hew wrote:
I decided to enable rawhide on my test F10 system, and do a yum update.
I get a lot of dependency failures like:
setroubleshoot-2.0.12-3.fc10.noarch from installed has depsolving problems --> Missing Dependency: python(abi) = 2.5 is needed by package setroubleshoot-2.0.12-3.fc10.noarch (installed)
Any suggestions?
TIA Fulko
why did you enable rawhide? this isnt a support channel. use the irc channel or fedoraforum
Sorry. I thought fedora-test was for testing rawhide? ;-(
As you know, Rawhide is the development of the next release.
I think that Greg made some wrong assumptions. He assumed you wanted to work on F10. He didn't think abt how you start to experience F11 development because he may not be into F11 development himself. == At the last time, I had over 300 pkgs waiting for solving dependency issues. I am not in production evironment as you know, so I am waiting for Fedora mgmt to focus on some of these issues.
For the last few weeks, John has been involved in virtual activity. He is been trying quite a number of distro for operation under virtual box. He feels there has been great progress on that front. I may get around to that activity later this month. I played with virtual abt a year ago but lost interest be it didn't at that time have the features I was hoping for.
John tells me the virtual box has made great strides. I think he is using Sun's virtual box, and is having success with quite a number of guests. He had a couple of questions abt F9, and I told him that I would repeat his steps, but on a dedicated host, and use the latest updates for F9. I reported that worked without a hitch.
I think John is compounding his issues. John is basically a 'hardware man'. He gets the opportunity with work with new hardware, which then often winds up as upgrades to his customers. As you know, Linux is developed by volunteer and it is usually safer to be on hardware that has been out for a little while, and has other volunteers working the Linux bugs out. John is an AMD man, and I know the latest motherboard he is working with has a recently released video card. When he hits some issues, I think it is due to hardware that may still be a challenge for Linux. == Different topic.
Recently, I decided that I needed to increase the storage on Mary's machine. It had an 80 GB drive. As drives are cheap now, I thought I would just add a 320 or 500 GB drive. Either is less than $100 these days.
Well I went to Tiger Dirct and they were sold out of 500 GB Seagate drives on that day, but they did have 320 GB Western Digital SATA, so I purchased that ($64 + tax).
I plugged it in and while the BIOS knew it was there XP didn't :-(
I eventually went to my support expert John. I had to learn how to do things on an XP system. It turns out I had to use the option to assign the drive a letter ('E' in my case), and create a partition (I assigned the whole 320 GB to a single partition). Then I had it create an NTFS file system. That took a couple of hours.
All went to prove how far I am out of date with MS systems. But John and I work back and forth. He calls me abt Linux and it turns out I had to call him abt MS :-(
On (02/01/09 17:54), Fulko Hew wrote:
I decided to enable rawhide on my test F10 system, and do a yum update.
I get a lot of dependency failures like:
setroubleshoot-2.0.12-3.fc10.noarch from installed has depsolving problems --> Missing Dependency: python(abi) = 2.5 is needed by package setroubleshoot-2.0.12-3.fc10.noarch (installed)
Any suggestions?
TIA Fulko
It's an EVR bug. The version in rawhide is 2.0.12-2 and in updates is 2.0.12-3. Check if it's reported. I think this is testing and that this is bug. So this list is appropriate.
On Fri, Jan 02, 2009 at 17:54:24 -0500, Fulko Hew fulko.hew@gmail.com wrote:
I decided to enable rawhide on my test F10 system, and do a yum update.
I get a lot of dependency failures like:
setroubleshoot-2.0.12-3.fc10.noarch from installed has depsolving problems --> Missing Dependency: python(abi) = 2.5 is needed by package setroubleshoot-2.0.12-3.fc10.noarch (installed)
Any suggestions?
I did a yum upgrade to F11 a couple of days ago and there are issues with some packages not being updatable in a way that prevents skip broken from being able to fix things. (This is probably a bigger problem than normal due to all of the python dependencies.)
I was able to get it to work by removing a few things temporarily. If you don't do this kind of thing a lot you might not want to go down this route. Also at this stage there can be a lot of bumps and going back isn't practical.
You might be better off doing installs to unused partitions that you can just scrap if you don't like things.
Fulko Hew wrote:
I decided to enable rawhide on my test F10 system, and do a yum update.
I get a lot of dependency failures like:
setroubleshoot-2.0.12-3.fc10.noarch from installed has depsolving problems --> Missing Dependency: python(abi) = 2.5 is needed by package setroubleshoot-2.0.12-3.fc10.noarch (installed)
Any suggestions?
TIA Fulko
Agreed, F11 development is not ready for anything yet.
I have been trying to run F11 development updates, but with little success. I vary from 300 to abt 350 pkgs that are waiting for dependencies. The python abi=2.5 is a prime example.
I think development in Fedora has changed in personality. IMO it used to be you reported problems (ex: with dependencies) and in a few days, updates would come along to address the issue. Now everything is driven by some God awful complex script (so many things are being supportted). That has changed the output to often a 100 or more pkgs in a day. The pkgs are all over the map so I doubt it is possible to support with manual methods.
The problem, I think is, they are focused on script issues. Things like the python abi=2.5 has been a known problem for over a month now.
I also think things are not managed very well. The active development is using koji as a site. Those verbally complaining abt something not working as expected, have often been pointed to koji and advise that the problem had been fixed there, but hasn't made it to distro.
I thing a lot of people are using koji to support what they have from Rawhide. I have doggedly stayed away from that option because I figure for quality, it is important to not contaminate my Rawhide items. But that is not true for the 'propellor heads'. And when they get a work around like that, they stop the noise abt unsolved dependencies.
It seems to me that people like me should be screeming every few days that items like python have not been fixed in *weeks*, but I think people have left it up to Fedora mgmt to recognize the issue.
So much for 'volunteer' management.
On Sat, Jan 03, 2009 at 12:18:03 -0500, glenn gsimpson@mountaincable.net wrote:
Agreed, F11 development is not ready for anything yet.
That's a bit strong. I wouldn't recommend trying to do normal work on it, but trying it to test particular things is doable.
I have been trying to run F11 development updates, but with little success. I vary from 300 to abt 350 pkgs that are waiting for dependencies. The python abi=2.5 is a prime example.
That is a bit of a special case. A lot of things depend on the perl abi so there are a lot of packages that need to be updated. It is more typical for only a few packages to be blocked in this manner when there are problems. There aren't that many blocking packages left and if you do some work you can work around the problem to get the update to succeed.
I think development in Fedora has changed in personality. IMO it used to be you reported problems (ex: with dependencies) and in a few days, updates would come along to address the issue. Now everything is driven
I think that is still the case. The issue here was the number of packages effected.
by some God awful complex script (so many things are being supportted).
What script are you referring to?
That has changed the output to often a 100 or more pkgs in a day. The pkgs are all over the map so I doubt it is possible to support with manual methods.
Lots of packages being changed is a good sign. That means development is getting done and things are getting pushed out quickly so that there is less latency in feedback for changes.
The problem, I think is, they are focused on script issues. Things like the python abi=2.5 has been a known problem for over a month now.
And things are mostly fixed. If you want to do an update, you need to manually downgrade a few packages and uninstall a few more. I have lots of packages installed (5849 on f10) and was able to get the upgrade to work without doing a huge amount of work. More typical installes may need to only deal with a handful of packages instead of a couple dozen.
I also think things are not managed very well. The active development is using koji as a site. Those verbally complaining abt something not working as expected, have often been pointed to koji and advise that the problem had been fixed there, but hasn't made it to distro.
Stuff in koji for rawhide usually appears in the next rawhide push (which happens daily). It doesn't get faster than that. For stable branches it may not get pushed to testing because the developer doesn't think it is safe for general testing and update/testing pushes often don't happen every day. However, having koji available is much better than having a developer having their own private branch somewhere as it allows you to do some testing when needed, on stuff that isn't safe to hand out to everyone.
It seems to me that people like me should be screeming every few days that items like python have not been fixed in *weeks*, but I think people have left it up to Fedora mgmt to recognize the issue.
You could open bugs against packages that have broken dependencies if you think the maintainer hasn't noticed.
On Sat, 03 Jan 2009 12:18:03 -0500, glenn wrote:
Agreed, F11 development is not ready for anything yet.
I have been trying to run F11 development updates, but with little success. I vary from 300 to abt 350 pkgs that are waiting for dependencies. The python abi=2.5 is a prime example.
Cannot be true. Compare with the daily "Rawhide Report" which is posted to this list and fedora-devel-list. At the bottom it shows the full list of broken dependencies in Rawhide.
What makes the problem worse, however, is that packages in up-to-date F10 are seen as "newer than" packages in Rawhide. This happens if updates are released only for F10, i.e. the corresponding update in Rawhide is missing (or fails to build), and the version-release of the F10 updates is higher than the most recent build of the pkg in Rawhide. If this results in additional broken dependencies [which are not covered in the Rawhide report], such as with Python 2.5 to 2.6, it becomes more difficult to upgrade from F10 to Rawhide.
Upgrade issues are a separate issue, though. It needs a policy before somebody could continue with running the upgrade path checker script.
I think development in Fedora has changed in personality. IMO it used to be you reported problems (ex: with dependencies) and in a few days, updates would come along to address the issue.
With the daily Rawhide Report, the package maintainers receive private email for broken dependencies. Daily and till they fix the packages.
Now everything is driven by some God awful complex script (so many things are being supportted).
Could you expand on this? What "awful complex script" do you refer to?
That has changed the output to often a 100 or more pkgs in a day. The pkgs are all over the map so I doubt it is possible to support with manual methods.
It is 100 or more updates in Rawhide a day, because the total number of packages in Rawhide has increased a lot. And many packagers update their packages regularly. Every successful build for Rawhide done in koji is published automatically a day later. You don't need to visit koji web to download anything there.
The problem, I think is, they are focused on script issues. Things like the python abi=2.5 has been a known problem for over a month now.
Still there may be issues that are either being worked on or which need additional work before a package would build and work for Python 2.6.
I also think things are not managed very well. The active development is using koji as a site. Those verbally complaining abt something not working as expected, have often been pointed to koji and advise that the problem had been fixed there, but hasn't made it to distro.
Are you sure?
It doesn't apply to Rawhide, but only to releases of Fedora. In these cases, something has been fixed in Rawhide (and *will* be available in Rawhide a day later), but updates for Fedora N need to be prepared separately and be pushed through the Fedora Updates System. Probably you mean, that builds in koji (= the Fedora Build System) may be downloaded already _before_ they will be published in Rawhide or as updates for Fedora N.
2009/1/2 Fulko Hew fulko.hew@gmail.com
I decided to enable rawhide on my test F10 system, and do a yum update.
I get a lot of dependency failures like:
setroubleshoot-2.0.12-3.fc10.noarch from installed has depsolving problems --> Missing Dependency: python(abi) = 2.5 is needed by package setroubleshoot-2.0.12-3.fc10.noarch (installed)
Any suggestions?
TIA Fulko
I had this before, and assuming that the machine in question will remain as a rawhide testing machine, the solution I used was to disable all the repos other than rawhide. After that, all the Python ABI errors disappeared.
-
Antonio Olivares -
Bruno Wolff III -
Derek Cramer -
Fulko Hew -
glenn -
Greg -
Ignacio Vazquez-Abrams -
Jerry Amundson -
Kevin Kofler -
Michael Schwendt -
Nikolay Vladimirov