Re: RHEL contacting EPEL maintainers when package goes into RHEL

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 20. 01. 21 15:27, Troy Dawson wrote:
This last week in the EPEL Steering Committee meeting, we talked about
what happens when an EPEL package gets pulled in and released in RHEL.
There were a couple of people who said that had happened to them and
they were totally un-aware that it was going to happen.

I contacted a couple people in Red Hat and found out that part of the
New Package procedure includes an EPEL check.  If the package is in
EPEL they are supposed to contact the EPEL maintainer.  They are also
supposed to have the NVR higher than the EPEL version.

This is a new procedure, implemented in June 2020.

If you are a EPEL package maintainer, and your package was pulled into
RHEL 7 or 8, and you were not contacted, please let me know.  Red Hat
wants this procedure to work, because when things go wrong, it affects
their customers.

Their current way of finding out who to contact is to do the following

   curl https://src.fedoraproject.org/_dg/bzoverrides/rpms/<package name>
example
  $ curl https://src.fedoraproject.org/_dg/bzoverrides/rpms/git-lfs
   {
     "epel_assignee": "carlwgeorge",
     "fedora_assignee": "qulogic"
   }

If anyone knows of a better way to find the EPEL maintainer, please
let me know and I'll pass it on.

Apparently, the EPEL maintainer receives an automated message like this:

This is an email notification that the new package: pybind11 is being
added to RHEL 8.4.0 and also exists in EPEL 8. You may want to remove
pybind11 from EPEL 8 or at least confirm that the pybind11
Version-Release will cleanly upgrade from and replace the EPEL package.

This also happens when the package is only added to a modular non-default stream. Is there a way the message could be adapted to:

 - discourage immediate retirement (RHEL 8.4 is not yet out, also CentOS Linux)
 - mention that removal is not always desired (especially with modular packages)

?

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux