https://bugzilla.redhat.com/show_bug.cgi?id=2251952 --- Comment #11 from Carl George 🤠 <carl@xxxxxxxxxx> --- > Any update here ? > Petr, as I don't have access to the Jira tickets, I don't know if anything happened on the RHEL side of things ? > Carl, are the changes I made to the specfile correct ? No update yet on getting perl-lasso shipped in CRB. The good news is we don't have to block this review on that. We can complete lasso-epel, get perl-lasso shipped in EPEL, and then when/if the CRB request happens retire lasso-epel. > I have a local change added to the previous spec that defines version according to the elX macro, which would allow to keep all the epel branches for lasso-epel in sync. After having maintained a few *-epel packages, I would discourage you from going this route. For normal EPEL packages I agree that it is nice to keep dist-git branches in sync, but in this case it makes things more complicated than they need to be. From a maintenance perspective the best choice is to keep the lasso-epel spec file as close to the relevant sections of the RHEL lasso spec file as possible, and letting the git branches diverge appropriately. This will also help ensure a smooth transition from EPEL's perl-lasso to RHEL's perl-lasso in the future. I went ahead and requested the lasso-epel dist-git repo. Since it's excluded from the normal review process, I used the exception flag, which will require manual RelEng approval. Once created I'll add you as a maintainer, import the relevant CentOS RPMs to populate the epel8 and epel9 branches, and then we can make the minmal changes to cause the package to only ship the perl-lasso subpackages. https://pagure.io/releng/fedora-scm-requests/issue/58967 -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2251952 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202251952%23c11 -- _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
