<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2013/4/29 Hans de Goede <span dir="ltr"><<a href="mailto:j.w.r.degoede@gmail.com" target="_blank">j.w.r.degoede@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi,<div><div class="h5"><br>
<br>
On 04/27/2013 04:07 AM, Sérgio Basto wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
...<br>
sidplay-2.0.9-13.fc17.x86_64<br>
</blockquote>
<br></div></div>
While working on sidplay, I found out there is a new upstream for it called sidplayfp,<br>
which fixes the issues making sidplay nonfree. So I've packaged libsidplayfp and<br>
sidplay for Fedora. Also the sid plugin for audacious has been changed to build with<br>
libsidplayfp and this has now landed in Fedora-updates for F-19+, so the following<br>
packages can now be retired from rpmfusion:<br>
<br>
sidplay<br>
sidplay-libs<br>
audacious-plugins-nonfree<br>
<br>
I'll go and create dead.package files for them in their F-19+ branches. What is<br>
the proper procedure for blocking these from inclusion in rpmfusion F-19+ repos ?<br></blockquote><br></div>I will manually remove them from the repository.<br></div><div class="gmail_extra">taking care of that before the next push.<br>
<br></div><div class="gmail_extra"></div><div class="gmail_extra">BTW, what about an audacity update (in both fedora and RPM Fusion ?)<br>It looks unmaintained.<br><br>Thx<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">
Nicolas (kwizart)<br></div></div>