On 3/01/2009 9:54 AM, Fulko Hew wrote: why did you enable rawhide? this isnt a support channel. use the irc channel or fedoraforum -- Regards Greg http://www.fedoraforum.org/

On 3/01/2009 10:13 AM, Fulko Hew wrote: 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 -- Regards Greg http://www.fedoraforum.org/

On 3/01/2009 11:00 AM, Fulko Hew wrote: 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 -- Regards Greg http://www.fedoraforum.org/

On Fri, 2009-01-02 at 19:00 -0500, Fulko Hew wrote: It is a virtual Provides provided by the python package. 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). -- Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com&gt; PLEASE don't CC me; I'm already subscribed

Fulko Hew wrote: 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'. -- Glenn Simpson VE3DSP Hamilton, Ont

On Sat, Jan 03, 2009 at 10:12:44 -0800, Antonio Olivares <olivares14031(a)yahoo.com&gt; wrote: 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, Jan 03, 2009 at 10:34:41 -0800, Antonio Olivares <olivares14031(a)yahoo.com&gt; wrote: 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.

Fulko Hew wrote: 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 :-( -- Glenn Simpson VE3DSP Hamilton, Ont

On Fri, Jan 02, 2009 at 17:54:24 -0500, Fulko Hew <fulko.hew(a)gmail.com&gt; wrote: 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.

On Sat, Jan 03, 2009 at 12:18:03 -0500, glenn <gsimpson(a)mountaincable.net&gt; wrote: 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. 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 that is still the case. The issue here was the number of packages effected. What script are you referring to? 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. 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. 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. You could open bugs against packages that have broken dependencies if you think the maintainer hasn't noticed.

2009/1/2 Fulko Hew <fulko.hew(a)gmail.com&gt; 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. -- Regards, Derek