Hi. Over the past couple of weeks I've been mock-rebuilding rawhide packages against current x264 and faad2-2.7, both of which bring ABI and API changes. Here's the list of affected packages with current status of my rebuilds: - = untested, + = rebuilt fine, * = rebuilt after fixes, X = failed, unfixed for faad2: X avidemux + cmus + ffmpeg * gpac X gstreamer-plugins-bad * libquicktime + mpd + mplayer - mythtv + streamripper X vlc + xine-lib-extras-freeworld + xmms2-freeworld for x264: X avidemux + ffmpeg X gstreamer-plugins-bad * libquicktime + mencoder (mplayer) X vlc Reports for gpac and libquicktime have been posted to bugzilla. I'll keep poking at avidemux, gstreamer and vlc.

On Sunday, 22 March 2009 at 16:35, Dominik 'Rathann' Mierzejewski wrote: > On Saturday, 21 March 2009 at 20:12, Dominik 'Rathann' Mierzejewski wrote: > > Hi. > > > > Over the past couple of weeks I've been mock-rebuilding rawhide packages > > against current x264 and faad2-2.7, both of which bring ABI and API changes. > > > > Here's the list of affected packages with current status of my rebuilds: > > > > - = untested, + = rebuilt fine, * = rebuilt after fixes, X = failed, unfixed > > > > for faad2: > > X avidemux > > + cmus > > + ffmpeg > > * gpac > > X gstreamer-plugins-bad > > * libquicktime > > + mpd > > + mplayer > > - mythtv > > + streamripper > > X vlc > > + xine-lib-extras-freeworld > > + xmms2-freeworld > > > > for x264: > > X avidemux > > + ffmpeg > > X gstreamer-plugins-bad > > * libquicktime > > + mencoder (mplayer) > > X vlc > > > > Reports for gpac and libquicktime have been posted to bugzilla. > > I'll keep poking at avidemux, gstreamer and vlc. > > Status update: > gstreamer-plugins-bad and vlc are now building fine (fixes posted in bugzilla). > avidemux compiles fine but fails on translation files (bugs filed/updated). And current mythtv from rawhide seems to build fine against faad2-2.7. I wonder though why it is dlopen()ing the library instead of simply linking to it?

On 3/25/09 5:19 PM, Dominik 'Rathann' Mierzejewski wrote: >Avidemux (2.4.4) builds fine now in my local mock. I'll fix it in CVS. > >Regards, >R. > Thanks, I'll submit a build later tonight.

2009/3/26 Dominik 'Rathann' Mierzejewski<dominik(a)greysector.net>: > On Wednesday, 25 March 2009 at 23:49, Stewart Adam wrote: >> On 3/25/09 5:19 PM, Dominik 'Rathann' Mierzejewski wrote: >>> Avidemux (2.4.4) builds fine now in my local mock. I'll fix it in CVS. >> Thanks, I'll submit a build later tonight. > You'll have to wait until the new qt package hits rawhide repos (and our > mirrors). The build I submitted failed: > http://buildsys.rpmfusion.org/build-status/job.psp?uid=3125 That means we will need to wait until rawhide got unfrozen.

Thorsten Leemhuis wrote: > On 26.03.2009 10:05, Nicolas Chauvet wrote: >> 2009/3/26 Dominik 'Rathann' Mierzejewski<dominik(a)greysector.net>: >>> On Wednesday, 25 March 2009 at 23:49, Stewart Adam wrote: >>>> On 3/25/09 5:19 PM, Dominik 'Rathann' Mierzejewski wrote: >>>>> Avidemux (2.4.4) builds fine now in my local mock. I'll fix it in CVS. >>>> Thanks, I'll submit a build later tonight. >>> You'll have to wait until the new qt package hits rawhide repos (and our >>> mirrors). The build I submitted failed: >>> http://buildsys.rpmfusion.org/build-status/job.psp?uid=3125 >> That means we will need to wait until rawhide got unfrozen. > We can put selected packages from koji into a private buildsys repo that > is available to all builders. I guess that might make sense here to not > delay things further, as long as the packages build against the new qt > run on the qt that is part of the beta/rawhide currently (but I assume > that's the case?). Should be ok now. If you want to grab a qt build, I'd suggest: http://koji.fedoraproject.org/koji/buildinfo?buildID=95387

On Thursday, 26 March 2009 at 14:07, Thorsten Leemhuis wrote: > On 26.03.2009 12:42, Rex Dieter wrote: >> Thorsten Leemhuis wrote: >>> On 26.03.2009 10:05, Nicolas Chauvet wrote: >>>> 2009/3/26 Dominik 'Rathann' Mierzejewski<dominik(a)greysector.net>: >>>>> On Wednesday, 25 March 2009 at 23:49, Stewart Adam wrote: >>>>>> On 3/25/09 5:19 PM, Dominik 'Rathann' Mierzejewski wrote: >>>>>>> Avidemux (2.4.4) builds fine now in my local mock. I'll fix it in CVS. >>>>>> Thanks, I'll submit a build later tonight. >>>>> You'll have to wait until the new qt package hits rawhide repos (and our >>>>> mirrors). The build I submitted failed: >>>>> http://buildsys.rpmfusion.org/build-status/job.psp?uid=3125 >>>> That means we will need to wait until rawhide got unfrozen. >>> We can put selected packages from koji into a private buildsys repo that >>> is available to all builders. I guess that might make sense here to not >>> delay things further, as long as the packages build against the new qt >>> run on the qt that is part of the beta/rawhide currently (but I assume >>> that's the case?). >> Should be ok now. If you want to grab a qt build, I'd suggest: >> http://koji.fedoraproject.org/koji/buildinfo?buildID=95387 > Done, should be avilable in the buildroots for rawhide now. Thanks. In the meantime, I successfully built faad2, x264 and ffmpeg. It'd be nice to have a list of broken deps posted daily for a couple of days starting today to keep track of the progress.

[...] Regarding the mass rebuild: I'll queue all packages that haven't been build in rawhide since 2009023 for a rebuild over the next few days if nobody yells or does it before I get to it.

On 03/27/2009 11:20 AM, Thorsten Leemhuis wrote: > On 27.03.2009 07:06, Thorsten Leemhuis wrote: >> [...] >> Regarding the mass rebuild: I'll queue all packages that haven't been >> build in rawhide since 2009023 for a rebuild over the next few days if >> nobody yells or does it before I get to it. > We have quite a few packages that have something like > > ExclusiveArch: i386 ... > > in the spec file. Those need a s/i386/i586/ to get properly build on > rawhide now. It would be nice if the packages maintainer could do this > adjustments on their own and queue a build afterwards, as the mass > rebuild likely will result in lot of work for me already ;-) > > BTW, the better fix might be to change > > ExclusiveArch: i386 ... > > into something like > > ExcludeArch: x86_64 ppc ppc64 ia64 sparc64 sparc How about "ExclusiveArch: %{ix86}"

or will that cause us to get build multiple times (i386, i586, i686, etc.) ?

I'm not a fan of using the "ExcludeArch: world" method when we really *are* ExclusiveArch: i?86

> On 27.03.2009 07:06, Thorsten Leemhuis wrote: >> >> [...] >> Regarding the mass rebuild: I'll queue all packages that haven't been >> build in rawhide since 2009023 for a rebuild over the next few days if >> nobody yells or does it before I get to it. > I was wondering if the mass rebuild will be done over tagged versions of packages in cvs or not? The latest version of xmms-wma is currently untagged in rawhide, because it doesn't function properly and we are working on it. Rathann? Any chance of having a look at it before F-11 is released?