On 02.07.2024 14:34, Sérgio Basto wrote:
On Thu, 2024-06-27 at 22:31 -0500, Carl George wrote:> This update changes from libclamav.so.9 to libclamav.so.11. It > will > require rebuilding c-icap-modules and librpminspect. If you > release > it in the current state you'll break installation of those > packages. > They should have been rebuilt in a side tag with clamav and > released > together. This is by definition an incompatible update, yet it > doesn't appear to have followed the EPEL Incompatible Upgrades > policy. > > https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/ > > Do not push this update to stable. Simply sending one email to say > "hey I did this and I'm gonna push to stable very soon" is not > sufficient. Follow the process outlined in the documentation. If > you > had followed the process in the first place, perhaps you would have > received karma on the update thanks to the multiple steps in the > process designed to raise awareness of this type of update. >OK Hopefully, I remembered to write in time . I wasn't expect that clamav has dependencies and no one in clamav group https://accounts.fedoraproject.org/group/clamav/ had remind me ... we need to move clamav to a build tag and build all dependents packages rpminspect and c-icap-modules the details are here https://src.fedoraproject.org/rpms/clamav/pull-request/26#comment-196845 and here https://bugzilla.redhat.com/show_bug.cgi?id=2237528 what else ? File an EPEL issue and add the meeting tag. This adds the issue to the agenda for discussion at the weekly EPEL meeting.
Hi Sergio - This is a reminder that per the incompatible upgrades policy, we are still waiting for an issue to be created and assigned the 'meeting' tag so that it can be voted on by the steering commitee. If there is anything I can do to help, please reach out. --neil
> On Thu, Jun 27, 2024 at 8:30 AM Sérgio Basto <sergio@xxxxxxxxxx> > wrote: > > > > > > Hi, > > > I though that I should let you know > > > > > > After 4 week in updates-testing > > > > > > this update will go to stable very soon and I got none, nienty, > > > zero > > > feedback, neither good or bad . > > > > > > Best regards, > > > -- > > > Sérgio M. B. > > > -- > > > _______________________________________________ > > > 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 > > > Do not reply to spam, report it: > > > https://pagure.io/fedora-infrastructure/new_issue > > > > -- > Carl George >-- Sérgio M. B. -- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Attachment:
signature.asc
Description: PGP signature
-- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
