Hi Nicolas, $subject says it all, not sure what the orphan process for rpmfusion is, hence this direct mail. Regards, Hans

Hi, On 13-11-16 09:53, Andrea Musuruane wrote: > > Hi Hans, > you have to retire it (not to orphan it). > > This procedure is up to date AFAIK: > http://rpmfusion.org/Contributors#Retiring_a_package > > Bye, > > Andrea Thank you, I've added dead.package files to git and created: https://bugzilla.rpmfusion.org/show_bug.cgi?id=4335

Hi, On 13-11-16 11:33, Nicolas Chauvet wrote: > > 2016-11-13 10:54 GMT+01:00 Hans de Goede <j.w.r.degoede(a)gmail.com&gt;: >> >> Hi, >> >> On 13-11-16 09:53, Andrea Musuruane wrote: >>> >>> >>> Hi Hans, >>> you have to retire it (not to orphan it). >>> >>> This procedure is up to date AFAIK: >>> http://rpmfusion.org/Contributors#Retiring_a_package >>> >>> Bye, >>> >>> Andrea >> >> >> >> Thank you, I've added dead.package files to git and created: >> >> https://bugzilla.rpmfusion.org/show_bug.cgi?id=4335 > > I think you should be able to use pkgdb to retire the package. > Now I still wonder if we still need mpg123 in 25 GA repo. I think so, > so it won't break users that might install with kickstart and only GA > repos for both projects. I went here (and logged in): https://admin.rpmfusion.org/pkgdb/package/free/mpg123/ I can orphan it there, but I don't think I can retire it there.