On 10 January 2018 at 01:53, Ding Yi Chen <dchen@xxxxxxxxxx> wrote: > I received a bug[1] asking to remove EPEL7 branch, as the package > LibRaw, is already in RHEL. > > How should I do that? > > Regards, > We do not remove branches as much as retire the package. https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life GIT[edit] Run fedpkg retire DESCRIPTION in all non-stable Fedora branches and EPEL branches, if applicable. The retiring needs to start with the oldest branch (e.g. retire on f25 before you retire on master) Remarks[edit] The DESCRIPTION parameter should explain why the package was retired, good messages are: Obsoleted by bar Renamed to bar The command will remove all files from the branch, add a file name dead.package containing the description and push the changes. Starting with fedpkg 1.13 it will also retire the package in package DB. git rm all files in the other branches only if there are special factors at work, like licensing issues, or package being removed completely from Fedora. If you retired master before other older branches you want to retire, just continue with the older branches. It will still work, but will block the package in more Koji tags, because tag inheritance will not be used automatically then. Ignore any errors related to Package DB. The package state is not tracked in Package DB anymore and a future fedpkg update will remove Package DB support from fedpkg. EPEL[edit] Note that you can use this process for EPEL as well with one difference: You can remove the package from any EPEL branch whether or not it has been released. For example, if your package has been added to base RHEL in RHEL-6.4 then perform the steps above but use the el6 branch instead of master. so basically... fedpkg switch-branch epel-7 fedpkg pull fedpkg retire > > 1. https://bugzilla.redhat.com/show_bug.cgi?id=1526701 > -- > Ding-Yi CHEN > > Software Engineer, Globalization Group > Red Hat Asia-Pacific Pty Ltd > dchen@xxxxxxxxxx > Twitter: @redhatway | Instagram: @redhatinc | Snapchat: @redhatsnaps > _______________________________________________ > epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
