#6080: epel7 branch for jsr-305

[Fedora Release Engineering]

#6080: epel7 branch for jsr-305
--------------------------+------------------------
 Reporter:  richardfearn  |       Owner:  rel-eng@…
     Type:  task          |      Status:  new
Milestone:                |   Component:  epel
 Keywords:                |  Blocked By:
 Blocking:                |
--------------------------+------------------------
 Hi,

You recently created an epel7 branch for the jsr-305 package. (Thanks!)

While trying to build FindBugs for EPEL 7 using mock, I noticed that
 jsr-305 was actually being pulled in from the 'base' repo. However that
 repo is a CentOS repo, not a RHEL repo.

Having the epel7 branch might turn out to be very useful, since I might
 need a newer version of jsr-305 for FindBugs. But assuming that there is a
 jsr-305 package in RHEL, is it OK that there is now also a jsr-305 in EPEL
 7?

(I seem to remember something on the wiki saying that EPEL branches would
 not be created for packages that are already in RHEL, but I might be
 mistaken.)

[Fedora Release Engineering]

#6080: epel7 branch for jsr-305
---------------------------+-----------------------
  Reporter:  richardfearn  |      Owner:  rel-eng@…
      Type:  task          |     Status:  closed
 Milestone:                |  Component:  epel
Resolution:  invalid       |   Keywords:
Blocked By:                |   Blocking:
---------------------------+-----------------------
Changes (by till):

* status:  new => closed
 * resolution:   => invalid

Comment:

It is against policy to replace a RHEL/CentOS package in EPEL. If you need
 a newer version, a parallel installable package with the newer version
 needs to be created.

There is no automatic check currently, therefore branches for RHEL/CentOS
 packages might be created by accident.