On Mon, 10 May 2010 14:54:20 -0400, Jarod wrote: > My mythtv-themes build keeps failing... Its a noarch package, but > requires mythtv-devel (which isn't noarch, and requires mythtv's build > deps too). Every time I've tried it, it lands on ppc64, and ppc64 > appears to have a broken lame package in the f12 updates repo -- lame > is there, but lame-libs is missing. In the long run, I'm going to > split up the mythtv-devel package so that its got a separate noarch > devel sub-package that'll minimally satisfy the themes build > dependencies and would make this problem irrelevant, but in the mean > time, we have a busted ppc64 repo. Can someone with the power to fix > it do so? Pretty please? :) (I wonder if pushing a new lame build > would be the easiest thing, but I'm not sure where/how things broke > down). The missing lame-libs package is because of: https://bugzilla.rpmfusion.org/show_bug.cgi?id=1166 Watching recent job.log files, it seems the ppc/ppc64 builder has been fixed. So, pushing a "lame" rebuild should result in a complete set of packages on ppc/ppc64, too.

P.S. It would be an exercise for somebody to compare i386 and powerpc repo metadata and try to find other powerpc builds, which are incomplete.

2010/5/11 Jarod Wilson <jarod(a)wilsonet.com&gt; > > On Mon, May 10, 2010 at 3:51 PM, Michael Schwendt <mschwendt(a)gmail.com&gt; > wrote: > > On Mon, 10 May 2010 14:54:20 -0400, Jarod wrote: > > > >> My mythtv-themes build keeps failing... Its a noarch package, but > >> requires mythtv-devel (which isn't noarch, and requires mythtv's build > >> deps too). Every time I've tried it, it lands on ppc64, and ppc64 > >> appears to have a broken lame package in the f12 updates repo -- lame > >> is there, but lame-libs is missing. In the long run, I'm going to > >> split up the mythtv-devel package so that its got a separate noarch > >> devel sub-package that'll minimally satisfy the themes build > >> dependencies and would make this problem irrelevant, but in the mean > >> time, we have a busted ppc64 repo. Can someone with the power to fix > >> it do so? Pretty please? :) (I wonder if pushing a new lame build > >> would be the easiest thing, but I'm not sure where/how things broke > >> down). > > > > The missing lame-libs package is because of: > > https://bugzilla.rpmfusion.org/show_bug.cgi?id=1166 > > > > Watching recent job.log files, it seems the ppc/ppc64 builder has been > > fixed. So, pushing a "lame" rebuild should result in a complete set > > of packages on ppc/ppc64, too. > > Looks like Dominik did exactly that on F11, but not F12. I'd go ahead > and push the same for F12, but I don't have permission to. Dominik, > can you do the bump-and-rebuild dance for F12 too? > > Don't need any bump or change in spec, just checkout lame, then go into the directory of lame, type 'make build'

On Monday, 10 May 2010 at 22:36, Jarod Wilson wrote: [...] > Looks like Dominik did exactly that on F11, but not F12. I'd go ahead > and push the same for F12, but I don't have permission to. Dominik, > can you do the bump-and-rebuild dance for F12 too? Yes, I'll try to do this tonight if I can find some time.