Description of problem: FC6 is using beagle 0.2.13 while upstream has released 0.2.15.1 which includes fixes that prevents beagle from using to much cpu time. It would be nice to have this as an update for FC6.
I'm upgrading beagle in rawhide/f7, but it requires a later mono than what is in fc6, and I saw some bugreports for regressions on the list. I'm not sure just upgrading it for fc6 is a great idea.
ok, than what about pushing it (including new mono) to updates-testing and see how well it works. (I will test it and I am sure others will too). If its broken (regressions) we could wait until its fixed upstream before moving it to updates-final.
It sounds very much like you want to turn updates-testing into some sort of mini-rawhide. Development is done in rawhide, and doing massive upgrades of the whole mono stack and just to test things out smells very much like development. For instance, if we upgrade mono we could break any mono app in core, extras or a third party app, so there would need to be a lot of testing before that can be considered safe. I'm pretty sure we won't get that much testing in updates-testing.
ok your right, the mono update could break random mono apps so leave it in rawhide/f7 for now.
0.2.16 is out which is a bugfix release (should fix regressions mentioned above) and do not require a new mono anymore. >1.1.13.5 and we have 1.1.17.1 in fc6.
Yes, that sounds better. I'm building 0.2.16 in rawhide. Lets have it cook there for a while and see how it does.
whats the status of it? is it ready for updates-testing and later fc6-stable ?
ping ;)
any updates on this? please look at http://beagle-project.org/Troubleshooting_CPU "Beagle version 0.2.13 and older are buggy The first thing is to ensure that you're running at least Beagle 0.2.14 or newer. You can get this info usually by looking at the version of the package you have installed on your Linux system, or by running beagle-ping. Bugs in older versions existed that could cause directories to be continuously reindexed. If that directory was created on-demand with a number of files in it (such as untarring a tarball), this can cause 100% CPU utilization. " thats seems to be the problem that I have, any plans to get a newer beagle atleast in updates testing?
Is it feasible to package newer versions of beagle for FC6? There doesn't seem to be anything in the spec file that prevents this, apart from the F7 version being built against python 2.5.