Hi,
On 05/01/2013 02:28 PM, Sérgio Basto wrote:
On Qua, 2013-05-01 at 09:14 +0200, Hans de Goede wrote:
Hi,
On 04/29/2013 03:36 PM, Nicolas Chauvet wrote:
2013/4/29 Hans de Goede <j.w.r.dego...@gmail.com
<mailto:j.w.r.dego...@gmail.com>>
Hi,
On 04/27/2013 04:07 AM, Sérgio Basto wrote:
...
sidplay-2.0.9-13.fc17.x86_64
While working on sidplay, I found out there is a new upstream for it
called sidplayfp,
which fixes the issues making sidplay nonfree. So I've packaged
libsidplayfp and
sidplay for Fedora. Also the sid plugin for audacious has been changed to
build with
libsidplayfp and this has now landed in Fedora-updates for F-19+, so the
following
packages can now be retired from rpmfusion:
sidplay
sidplay-libs
audacious-plugins-nonfree
I'll go and create dead.package files for them in their F-19+ branches.
What is
the proper procedure for blocking these from inclusion in rpmfusion F-19+
repos ?
I will manually remove them from the repository.
taking care of that before the next push.
BTW, what about an audacity update (in both fedora and RPM Fusion ?)
It looks unmaintained.
I've pinged the Fedora maintainer and he admits he was away for a while, but he
is back now.
I've offered him help on getting the Fedora packages upgraded to 2.0.3, once
that is done
I'll also take care of the rpmfusion packages.
We already have a ticket to fix audacity :
https://bugzilla.rpmfusion.org/show_bug.cgi?id=2707
Ok, I've committed all the necessary changes for a new 2.0.3 based audacity
package to the
devel branch in CVS. Building this needs to wait for tomorrows rawhide push as
it needs a new
enough portaudio.
This problem extends to F-19, do we have updates-testing in the F-19 buildroot?
If not we
will need to wait 3 days, so that I can push the new portaudio to the stable
F-19 updates
repo, and hope we don't run into some freeze.
Regards,
Hans
