On 27.05.2009 20:01, Thorsten Leemhuis wrote: > I'm doing some preparation for F11 branching (maybe Xavier and I might > even finish it today). So if something is not working please be a bit > patient and retry a bit later; If problems remain for longer please let > me know -- preferred via IRC in this case, as that might reduce > communication to "there is a problem foo" "we know, please be patient, > we are working on it" ;-) Made some progress over the past two hours: [...] /me leaves the keyboard now, way to late for me already

On 05/30/2009 09:45 AM, Thorsten Leemhuis wrote: > CVS is branched for F-11 now (thanks Xavier for you help with the > preparations). Note that devel/ still targets F11 till rawhide actually > moves on to F12 (e.g. until F11 is released) -- this is different from > Fedora! > > IOW: > > - everything you build from foo/F-11/ will go to F11-updates-testing and > later get moved to F11-updates > > - everything you build from devel/ over the next few days will get into > the release repos for F11 > > But I'd guess nobody should build anything in the devel branch anymore > over the next few days apart from critical bugfixes to make sure we > don't introduce any new bugs in those repos. Okay, so per our discussion on irc about putting mythtv 0.21 into the initial release repo... It sounds like I want to build the latest 0.21 in devel/ so that ships w/the release, and then build 0.22-svn in F-11/, and have it go to updates-testing... Correct?

Haven't looked yet to see that mythtv has been removed from the f11 repos,

we have a massive gathering at the house starting... 5 minutes ago... But I'll try to give it a look later this evening, and get builds all squared away.

wrote:

Quoting "Thorsten Leemhuis" <fedora(a)leemhuis.info&gt;: > On 30.05.2009 16:25, Jarod Wilson wrote: >> Okay, so per our discussion on irc about putting mythtv 0.21 into >> the >> initial release repo... It sounds like I want to build the latest >> 0.21 >> in devel/ so that ships w/the release, and then build 0.22-svn in >> F-11/, >> and have it go to updates-testing... Correct? > > Correct. Ugh, and I just yum upgraded my mythtv box to F11. When is the 0.22- svn version supposed to go stable?

On 27.05.2009 22:12, Thorsten Leemhuis wrote: > On 27.05.2009 20:01, Thorsten Leemhuis wrote: [...] But I'd guess nobody should build anything in the devel branch anymore over the next few days apart from critical bugfixes to make sure we don't introduce any new bugs in those repos. Hence I plan to review any package updates a bit closer before pushing them. If something odd comes up I'll ask packagers or this list for advice.

On Sat, Jun 6, 2009 at 3:08 AM, Thorsten Leemhuis wrote: > On 30.05.2009 15:45, Thorsten Leemhuis wrote: >> On 27.05.2009 22:12, Thorsten Leemhuis wrote: >>> On 27.05.2009 20:01, Thorsten Leemhuis wrote: >> [...] >> But I'd guess nobody should build anything in the devel branch anymore >> over the next few days apart from critical bugfixes to make sure we >> don't introduce any new bugs in those repos. Hence I plan to review any >> package updates a bit closer before pushing them. If something odd comes >> up I'll ask packagers or this list for advice. > > kwizart build a new totally new nvidia driver (180 -> 185) for devel/F11 > release repos: > > http://buildsys.rpmfusion.org/build-status/job.psp?uid=4139 > http://buildsys.rpmfusion.org/build-status/job.psp?uid=4138 > > It might be quite an important component, but problems with it can > (seldomly) damage hardware and if something is wrong with that package > it can bite users for the next 13 months. Thus I'm quite unwilling to > push this to the F11 release repos at this point with F11 only three > days away. A few days updates-testing for F11 IMHO is the way better > place IMHO. > > Thus I didn't push it yet. Does someone agree/disagree with that > (kwizart obviously will disagree, asking more for other opinions here)? > If enough people disagree then I can still push it, but if something is > wrong then it might get hard to fix (which would cost quite a bit of my > time, which I don't have right now) because rawhide might move on > today/tomorrow and thus would need another round of mock adjustments on > all builders. > > CU > knurd > My user perspective: I've been using the 185 driver for a couple days now without any problems. It won't be a problem for me if me include 185 in the F-11 release repo. My packager perspective: I agree with you on this. The 185 package didn't get enough testing time. But can we ship the 180 driver in the F-11 release repo at least?