Comments
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This update was submitted a long time ago and is still not resolved.
If you are no longer interested in maintaining this package in EPEL, I advice you to find a co maintainer that is interested or you could also drop this update request.
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This update was submitted a long time ago and is still not resolved. From what I'm seeing shouldn't be any problem to merge this to stable since the 14 day wait have passed.
If you are no longer interested in maintaining this package in EPEL, find a comaintainer or drop this update request.
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This update was submitted a long time ago and is still not resolved. From what I'm seeing shouldn't be any problem to merge this to stable since the 14 day wait have passed.
If you are no longer interested in maintaining this package in EPEL, find a comaintainer or drop this update request.
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This update was submitted a long time ago and is still not resolved. From what I'm seeing shouldn't be any problem to merge this to stable since the 14 day wait have passed.
If you are no longer interested in maintaining this package in EPEL, find a comaintainer or drop this update request.
dherrera
commented & provided feedback
on python-XStatic-Patternfly-Bootstrap-Treeview-2.1.3.2-1.el7
3 months ago
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This update was submitted a long time ago and is still not resolved. From what I'm seeing shouldn't be any problem to merge this to stable since the 14 day wait have passed.
If you are no longer interested in maintaining this package in EPEL, find a comaintainer or drop this update request.
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This update was submitted a long time ago and is still not resolved. From what I'm seeing shouldn't be any problem to merge this to stable since the 14 day wait have passed.
If you are no longer interested in maintaining this package in EPEL, find a comaintainer or drop this update request.
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This update was submitted a long time ago and is still not resolved. From what I'm seeing shouldn't be any problem to merge this to stable since the 14 day wait have passed.
If you are no longer interested in maintaining this package in EPEL, find a comaintainer or drop this update request.
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This update was submitted a long time ago and is still not resolved. From what I'm seeing shouldn't be any problem to merge this to stable since the 14 day wait have passed.
If you are no longer interested in maintaining this package in EPEL, find a comaintainer or drop this update request.
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This update was submitted a long time ago and is still not resolved. From what I'm seeing shouldn't be any problem to merge this to stable since the 14 day wait have passed.
If you are no longer interested in maintaining this package in EPEL, find a comaintainer or drop this update request.
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This package is already available in EL7 distributions and shouldn't get an EPEL version [1].
[0] https://pagure.io/epel/issue/230
[1] https://docs.fedoraproject.org/en-US/epel/epel-policy/#package_maintenance_and_update_policy
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
Since this project retired from EPEL7, I would suggest to retire this update as well.
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
Since this project retired from EPEL7, I would suggest to retire this update as well.
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
Since this project retired from EPEL7, I would suggest to retire this update as well.
I'm contacting you because of a ticket submitted to the EPEL SIG regarding old updates still in testing [0]
This update was submitted a long time ago and is still not resolved. From what I'm seeing shouldn't be any problem to merge this to stable since the 14 day wait have passed.
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This minor version update for this project is marked as an enhancement and doesn't seem to comply with the current policy regarding package updates [1].
If you need this update to fix reported bugs, I would advice to backport the corresponding patches to do so, but if it is hard/not posible, I would advice you to follow the incompatible upgrade policy if you feel that this upgrade is necesary for this purpose [2]
[0] https://pagure.io/epel/issue/230
[1] https://docs.fedoraproject.org/en-US/epel/epel-policy/#guidelines_and_backgrounds_for_this_policy
[2] https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This update seems to already have been resolved by FEDORA-EPEL-2019-ed23295aaa and FEDORA-EPEL-2023-ed15641266
Please retire it
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
From what I'm seeing, the nut update still requires more karma to get approved [1], but If you really need to get this update, and feel that backporting the changes needed for the dependency to comply with requirements of the collectd package is hard/not possible, I would advice you to follow the incompatible upgrade policy [2]
[0] https://pagure.io/epel/issue/230
[1] https://docs.fedoraproject.org/en-US/epel/epel-policy/#guidelines_and_backgrounds_for_this_policy
[2] https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
These minor version updates for these projects are marked as an enhancements and don't seem to comply with the current policy regarding package updates [1].
If you need this update to fix reported bugs, I would advice to backport the corresponding patches to do so, but if it is hard/not posible, I would advice you to follow the incompatible upgrade policy if you feel that this upgrade is necesary for this purpose [2]
[0] https://pagure.io/epel/issue/230
[1] https://docs.fedoraproject.org/en-US/epel/epel-policy/#guidelines_and_backgrounds_for_this_policy
[2] https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
I'm contacting you because of a ticket submitted to the EPEL SIG regarding resolving old updates still in testing [0]
This update was submitted a long time ago and is still not resolved. From what I'm seeing shouldn't be any problem to merge this to stable since the 14 day wait have passed.
Works as expected and fixes the bug ;D