On Fri, Mar 19, 2021 at 7:55 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote: > > On 19. 03. 21 15:25, Troy Dawson wrote: > > Problem: Users might want to test ELN for their own package/product > > that either is only in Fedora, or that has dependencies that are only > > in Fedora and not ELN. > > I am not sure I underrated this problem entirely. > > I thought ELN is used as an additional repo on rawhide [1]. Hence, you get > access to all the rawhide packages when you use ELN. Has that changed? > > [1] https://fedoraproject.org/wiki/Changes/ELN_Buildroot_and_Compose#How_To_Test It has not. And I might not totally understand the problem either. It was other people who brought it up. I am merely proposing a solution to what I understand they were telling me. The closest I have to this problem is having some EPEL packages that I want to make sure don't break on RHEL, and I'd rather know sooner rather than later. But, as for me, I plan on using epel-next for that. Troy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
