[EPEL-devel] Re: missing rhel devel packages - another proposal
On 23. 06. 21 0:31, Kevin Fenzi wrote: Outside of that on the technical side... if these are from stream they might not always work for base epel would they? I think that if we don't download the latest version from Stream, but the build with the corresponding epoch:version-release to the RHEL package instead, it should work. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: missing rhel devel packages - another proposal
On Tue, Jun 22, 2021 at 02:53:05PM -0700, Troy Dawson wrote: > Someone brought this proposal to me, I'd like to get others feedback. > > Proposal: > EPEL would make its own "devel" repo, with the missing RHEL packages, > grabbing the packages from the publicly available centos stream koji > builds.[1] For example, the missing lmdb-devel would be downloaded from > here.[2] > We would have a list of missing packages, along with their corresponding > source rpm name. Whenever that source rpm get's updated in RHEL, we would > grab the updated missing packages, and regenerate the "devel" repo. > This should work for epel8, epel8-next, epel9, epel9-next > > I realize that this will require some up front work, but I'd like to get > people's ideas about the proposal. The main concern I have is keeping it in sync... I think we would want some automation here to notify when such a package updates in rhel, otherwise while we might update it at first, it will get forgotten after a while. Outside of that on the technical side... if these are from stream they might not always work for base epel would they? kevin signature.asc Description: PGP signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] missing rhel devel packages - another proposal
Someone brought this proposal to me, I'd like to get others feedback. Proposal: EPEL would make its own "devel" repo, with the missing RHEL packages, grabbing the packages from the publicly available centos stream koji builds.[1] For example, the missing lmdb-devel would be downloaded from here.[2] We would have a list of missing packages, along with their corresponding source rpm name. Whenever that source rpm get's updated in RHEL, we would grab the updated missing packages, and regenerate the "devel" repo. This should work for epel8, epel8-next, epel9, epel9-next I realize that this will require some up front work, but I'd like to get people's ideas about the proposal. Troy [1] - https://koji.mbox.centos.org/koji/ [2] - https://koji.mbox.centos.org/pkgs/packages/lmdb/0.9.24/1.el8/x86_64/lmdb-devel-0.9.24-1.el8.x86_64.rpm ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee
Dear all, You are kindly invited to the meeting: EPEL Steering Committee on 2021-06-23 from 16:00:00 to 17:00:00 US/Eastern At fedora-meet...@irc.libera.net The meeting will be about: This is the weekly EPEL Steering Committee Meeting. A general agenda is the following: #meetingname EPEL #topic Intros #topic Old Business #topic EPEL-7 #topic EPEL-8 #topic EPEL-9 #topic Openfloor #endmeeting Source: https://calendar.fedoraproject.org//meeting/9854/ ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee
Dear all, You are kindly invited to the meeting: EPEL Steering Committee on 2021-06-23 from 16:00:00 to 17:00:00 US/Eastern At fedora-meet...@irc.libera.net The meeting will be about: This is the weekly EPEL Steering Committee Meeting. A general agenda is the following: #meetingname EPEL #topic Intros #topic Old Business #topic EPEL-7 #topic EPEL-8 #topic EPEL-9 #topic Openfloor #endmeeting Source: https://apps.fedoraproject.org/calendar/meeting/9854/ ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
