I just wondered how the RPM packages from Fedora used in RPMFusion
buildroots are verfied on the RPMFusion builders. Fedora uses direct
access to the RPM packages via a secure channel afaik, but since
RPMFusion does not use Fedora infrastructure, this seems not to be
possible. Also I did not found the typical RPM message about importing
the GPG key that is usually displayed on my local mock builds in the
RPMFusion build roots. Therefore I fear that the RPMs are not verified
at all, but please don't let this be true.
Packages built and released for RPM Fusion (Fedora - free) 12: 1
Changes in RPM Fusion (Fedora - free) 12:
* Fri Jan 29 2010 Hans de Goede <j.w.r.degoede(a)hhs.nl> 2.2-3
- Fix another hang in the madplug plugin (rf1061)
* Mon Jan 25 2010 Hans de Goede <j.w.r.degoede(a)hhs.nl> 2.2-2
- Don't hang when trying to identify unknown files as mp3 files (rf1031)
* Sat Dec 19 2009 Hans de Goede <j.w.r.degoede(a)hhs.nl> 2.2-1
- Update to 2.2
Somebody please push the
test update for F-12 free into "stable".
Fedora bodhi has just decided to ignore my "no karma automatism"
setting for the Audacious 2.2 test update set and posted:
The following update has reached a karma of 3 and is being
automatically marked as stable.
(!) audacious-freeworld must be published before audacious, as only
then there will be broken dependencies temporarily. If the audacious
upgrade is pushed before audacious-freeworld, plugins will be missing (!)