<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 11, 2016 at 7:43 PM, Sérgio Basto <span dir="ltr"><<a href="mailto:sergio@serjux.com" target="_blank">sergio@serjux.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">On Dom, 2016-07-10 at 16:36 +0200, Andrea Musuruane wrote:<br>
> If you are interested, I have a review request for devedeng:<br>
> <a href="https://bugzilla.rpmfusion.org/show_bug.cgi?id=4013" rel="noreferrer" target="_blank">https://bugzilla.rpmfusion.org/show_bug.cgi?id=4013</a><br>
><br>
> devede is no longer maintained upstream.<br>
<br>
</span>yes , I found it 2 or 3 days ago , now that seems we will have<br>
RPMfusion rawhide ! , we can put devedeng there . <br>
But shouldn't devedeng replace devede ? , i.e., or rename package or<br>
even just update devede package with new code (devedeng), or do you<br>
want the 2 packages, devede and devedeng, at same time ? <br></blockquote><div><br></div><div>Upstream has two different source code repositories: one for devede and one for devedeng. Therefore I choose to made a new package for devedeng (which is quite different from the package for devede).<br><br></div><div>Moreover I followed Fedora Guidelines regarding replacing an existing package:<br><a href="https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages">https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages</a><br><br></div><div>When devedeng is in the RPM fusion repository, we will be able to retire devede.<br></div><div><br></div><div>Bye,<br><br></div><div>Andrea<br><br></div></div></div></div>