Bug 932

There is an update queued in Fedora proper for F-12:

http://admin.fedoraproject.org/updates/picard-0.12.1-1.fc12

Unfortunately since rawhide/F-12 is a deep freeze, this update wasn't able to make it into the F-12 GA release, but it will be available as a 0-day update.  

This is a problem of synchronising between Fedora and RPM Fusion, especially since RPM Fusion does not (yet) use bodhi, so there is no way in RPM Fusion to "queue" a built update and then "push" it manually to stable when ready.

For the moment, I suggest using:

yum update --exclude=picard

or using the --skip-broken option

I'd like to get this fixed on the repo level, to make sure our repos are free of unresolvable deps, to make sure RPM Fusion works fine in Anaconda (installs, livecd-creator, ...)

So we have to options: 

- remove, the new version, build a older version for our rawhide and put that in the repo; later build the 0.12 version as update and push it in sync
- remove the new version and only ship the new version as update -- but then people won't be able to create spins with picard and to select it in anaconda  during install

I'd prefer to got for the first option. Ohhn and:

> This is a problem of synchronising between Fedora and RPM Fusion, especially
> since RPM Fusion does not (yet) use bodhi,

bodhi isn't the problem (or the solution to it), different dates for freezing and final repo generation (and the lack or proper communication about it) are (but the different dates are afaics something some crucial RPM Fusion contributors want)

(In reply to comment #2)
> I'd like to get this fixed on the repo level, to make sure our repos are free
> of unresolvable deps, to make sure RPM Fusion works fine in Anaconda (installs, livecd-creator, ...)

> So we have to options: 
> - remove, the new version, build a older version for our rawhide and put that
> in the repo; later build the 0.12 version as update and push it in sync
> - remove the new version and only ship the new version as update -- but then
> people won't be able to create spins with picard and to select it in anaconda 
> during install

> I'd prefer to got for the first option. Ohhn and:

picard 0.12.1 in Fedora has already gone in as an update, and I don't want/plan to withdraw it it would be too difficult at this point.  I would ship picard-freeworld as an update for rpmfusion so that both are available as updates for F-12.  

If it's possible to build the old 0.11 version of picard-freeworld that goes into the F-12 GA for rpmfusion, then that's fine with me.  Then I guess that would be option 1.  It would have to be pushed as 0-day update for rpmfusion-free-updates as I've currently set the Fedora picard to go straight to stable.

> > This is a problem of synchronising between Fedora and RPM Fusion, especially
> > since RPM Fusion does not (yet) use bodhi,

> bodhi isn't the problem (or the solution to it), different dates for freezing
> and final repo generation (and the lack or proper communication about it) are
> (but the different dates are afaics something some crucial RPM Fusion
> contributors want)

True, although having something like bodhi would allow builds to be made/tested without going straight to a repo.

picard-freeworld-0.12.1-1.fc12.x86_64 removed; can you downgrade picard-freeworld in cvs to a version that matches rawhide and kick of a build please? tia

> True, although having something like bodhi would allow builds to be made/tested
> without going straight to a repo.

Well, a freeze like we had for the public rawhide/F12 would be the fair comparison. Anyway, if you want to test something bevore you push it drop me a mail, I can easily exclude packages from a push.

(In reply to comment #4)
> picard-freeworld-0.12.1-1.fc12.x86_64 removed; can you downgrade
> picard-freeworld in cvs to a version that matches rawhide and kick of a build
> please? tia

Done:

http://buildsys.rpmfusion.org/build-status/job.psp?uid=5553

> > True, although having something like bodhi would allow builds to be made/tested
> > without going straight to a repo.
> 
> Well, a freeze like we had for the public rawhide/F12 would be the fair
> comparison. Anyway, if you want to test something bevore you push it drop me a
> mail, I can easily exclude packages from a push.

Ok, noted, thanks. 

So, now what should I do to ensure the picard-freeworld 0.12.1 build in rpmfusion is ready to go when the 0-day F-12 update for picard goes out?

(In reply to comment #5)
> (In reply to comment #4)
> > picard-freeworld-0.12.1-1.fc12.x86_64 removed; can you downgrade
> > picard-freeworld in cvs to a version that matches rawhide and kick of a 
> > build please? tia
> Done:
> http://buildsys.rpmfusion.org/build-status/job.psp?uid=5553

thx, push in progress.

(In reply to comment #6)
> So, now what should I do to ensure the picard-freeworld 0.12.1 build in
> rpmfusion is ready to go when the 0-day F-12 update for picard goes out?

Just build the new version again please and I take care of the rest. Would be nice if you could tell me when you notice that the new picard hits Fedora's updates repos (but I'll try to watch out for it myself)

(In reply to comment #7)

> Just build the new version again please and I take care of the rest. Would be
> nice if you could tell me when you notice that the new picard hits Fedora's
> updates repos (but I'll try to watch out for it myself)

OK, I've done a new build of 0.12.1 for F-12 again:

http://buildsys.rpmfusion.org/build-status/job.psp?uid=5555 

I'll look out for when the Fedora picard hits updates.

I also just kicked off a build of picard-freeworld for F-11:

http://buildsys.rpmfusion.org/build-status/job.psp?uid=5558

to match the version of picard currently in Fedora updates-testing:

https://admin.fedoraproject.org/updates/F11/FEDORA-2009-11261

Is it possible to pin this build to rpmfusion-free-updates-testing until I (manually) push the Fedora build to stable once it gets some testing, then it can be pushed to rpmfusion-free-updates.

Thanks.

done

(In reply to comment #9)

> Is it possible to pin this build to rpmfusion-free-updates-testing until I
> (manually) push the Fedora build to stable once it gets some testing, then it
> can be pushed to rpmfusion-free-updates.

OK, I just submitted the F-11 version of picard to "updates":

https://admin.fedoraproject.org/updates/F11/FEDORA-2009-11261

Can you unpin the corresponding picard-freeworld and let it go to rpmfusion-free-updates?  Of course, I don't know when the next push will happen but perhaps you could time the next rpmfusion push to include picard-freeworld somehow.  Thanks!

Ping?  Could you please push the picard-freeworld 0.12 in rpmfusion-free-updates-testing for F-11 to rpmfusion-free-updates?  The corresponding picard 0.12 in Fedora is now in updates, so this causes broken deps.  Thanks