[EPEL-devel] Re: missing rhel devel packages - another proposal
On Tue, Jun 22, 2021 at 2:53 PM 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. > > 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 > > Thanks to everyone for the discussion both on email and during our committee meeting. In the end this was deemed infeasible. The biggest problem dealt with updates that get released in RHEL, but the release in Stream has a different NVR. It could be that rhel ships foo-1-5.el8 but stream goes from foo-1-4.el8 to -6.el8. It could be that rhel ships bar-1.0-5, but stream is already at bar-1.1-1, and doesn't have any update because 1.1 already fixed the problem. Most of the other problems (automation, figuring out when and where to grab package, getting koji to play nice, etc..) could be coded and worked around. But if the package isn't built for CentOS Stream, there is no work around for that. Our current solution is to create -epel packages that only have the missing sub-packages. There are some drawbacks, but it works.[1][2] Troy [1] - https://src.fedoraproject.org/rpms/lmdb-epel [2] - https://src.fedoraproject.org/rpms/mobile-broadband-provider-info-epel ___ 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 4:49 PM Miro Hrončok wrote: > 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. > That's what I was thinking of if we did/tried this. We wouldn't grab the latest version. We would find out the RHEL NVR (Name-Version-Release), and grab that specific missing package. And yes, it would have to be automated. I don't know if it would be possible, but I think it would be good to be done right after the daily RHEL sync is done. Troy ___ 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 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
