I posted an issue that may warrant a patch some days ago with no response. Is there a more appropriate list to post on?
Regards,
Stan
3 thoughts on - What List To Use For Patch Requests
that patch woudl have to come from redhat in a rhel7 update to make it into CentOS mainstream.
CentOS is a rebuild of RHEL Source code … we don’t release bugfixes of things released by RHEL unless we (CentOS team) somehow introduced the broken code with branding updates. Remember, CentOS is supposed to be bug for bug compatible with the upstream products and if we want things fixed they need to come down from upstream.
Also, the evolution in CentOS-7 is 3.8.5-22.el7_0.1 … not evolution
3.10.x. That means that the patch from Fedora 20 will likely not apply as is.
If you are sure that it is the same issue then we can open a Red Hat bug and hopefully they will roll in the patch.
Thanks, Johnny Hughes
For informational purposes, it seems they are on this for c7 now:
When they release it, not sure. The version listed in the bug is 7.1, so it should come then at the latest. The status is ON_QA, so they are testing it now.
3 thoughts on - What List To Use For Patch Requests
that patch woudl have to come from redhat in a rhel7 update to make it into CentOS mainstream.
CentOS is a rebuild of RHEL Source code … we don’t release bugfixes of things released by RHEL unless we (CentOS team) somehow introduced the broken code with branding updates. Remember, CentOS is supposed to be bug for bug compatible with the upstream products and if we want things fixed they need to come down from upstream.
Also, the evolution in CentOS-7 is 3.8.5-22.el7_0.1 … not evolution
3.10.x. That means that the patch from Fedora 20 will likely not apply as is.
If you are sure that it is the same issue then we can open a Red Hat bug and hopefully they will roll in the patch.
Thanks, Johnny Hughes
For informational purposes, it seems they are on this for c7 now:
https://bugzilla.redhat.com/show_bug.cgi?id=1153723
When they release it, not sure. The version listed in the bug is 7.1, so it should come then at the latest. The status is ON_QA, so they are testing it now.
Thanks, Johnny Hughes