[Fedora][Engine] Hystrix going to be orphaned in Fedora
FESCo approved an updated policy for packages which fail to build from source during mass rebuilds (FTBFS). The updated policy is still at https://fedoraproject.org/ wiki/Fails_to_build_from_source. Highlights: - packages which FTBFS are subject to orphaning if there is no maintainer acknowledgement within 8 weeks - packages which FTBFS in two consecutive mass rebuilds will be retired soon after the second mass rebuild Focusing on Hystrix, it has been reported failing on 2018-03-14, more than 10 weeks ago and it's failing to build since Fedora 26, totalling 3 consecutive mass rebuild failures. This put Hystrix in a candidate position for being orphaned. The Hystrix package is used by oVirt Engine. The POM requires version 1.4.14 (released this on 6 Aug 2015) . Fedora 24 and CentOS Virt SIG has 1.4.21 (released this on 17 Nov 2015). Latest upstream version is 1.5.13. Since in oVirt 4.3 we're aiming to support Fedora 28 we need to decide on what to do with Hystrix: - drop it as dependency? - update to latest? - try to fix build failure and keep current version? Roman, current maintainer (in cc) is unresponsive, not replying to my needinfo since 2017-08-17 Any volunteer for taking over? -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://red.ht/sig> <https://redhat.com/summit>
On Tue, May 29, 2018 at 10:06 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
FESCo approved an updated policy for packages which fail to build from source during mass rebuilds (FTBFS).
The updated policy is still at https://fedoraproject.org/w iki/Fails_to_build_from_source.
Highlights:
- packages which FTBFS are subject to orphaning if there is no maintainer acknowledgement within 8 weeks
- packages which FTBFS in two consecutive mass rebuilds will be retired soon after the second mass rebuild
Focusing on Hystrix, it has been reported failing on 2018-03-14, more than 10 weeks ago and it's failing to build since Fedora 26, totalling 3 consecutive mass rebuild failures. This put Hystrix in a candidate position for being orphaned.
The Hystrix package is used by oVirt Engine. The POM requires version 1.4.14 (released this on 6 Aug 2015) . Fedora 24 and CentOS Virt SIG has 1.4.21 (released this on 17 Nov 2015). Latest upstream version is 1.5.13.
Since in oVirt 4.3 we're aiming to support Fedora 28 we need to decide on what to do with Hystrix: - drop it as dependency? - update to latest? - try to fix build failure and keep current version?
Roman, current maintainer (in cc) is unresponsive, not replying to my needinfo since 2017-08-17
I simply missed it. At least a concrete ping would have been nice. Best Regards, Roman
Any volunteer for taking over?
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@redhat.com <https://red.ht/sig> <https://redhat.com/summit>
On Tue, May 29, 2018 at 10:43 AM, Roman Mohr <rmohr@redhat.com> wrote:
On Tue, May 29, 2018 at 10:06 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
FESCo approved an updated policy for packages which fail to build from source during mass rebuilds (FTBFS).
The updated policy is still at https://fedoraproject.org/w iki/Fails_to_build_from_source.
Highlights:
- packages which FTBFS are subject to orphaning if there is no maintainer acknowledgement within 8 weeks
- packages which FTBFS in two consecutive mass rebuilds will be retired soon after the second mass rebuild
Focusing on Hystrix, it has been reported failing on 2018-03-14, more than 10 weeks ago and it's failing to build since Fedora 26, totalling 3 consecutive mass rebuild failures. This put Hystrix in a candidate position for being orphaned.
The Hystrix package is used by oVirt Engine. The POM requires version 1.4.14 (released this on 6 Aug 2015) . Fedora 24 and CentOS Virt SIG has 1.4.21 (released this on 17 Nov 2015). Latest upstream version is 1.5.13.
Since in oVirt 4.3 we're aiming to support Fedora 28 we need to decide on what to do with Hystrix: - drop it as dependency? - update to latest? - try to fix build failure and keep current version?
Roman, current maintainer (in cc) is unresponsive, not replying to my needinfo since 2017-08-17
I simply missed it. At least a concrete ping would have been nice.
Ok, my failure. I got a ping.
Best Regards,
Roman
Any volunteer for taking over?
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@redhat.com <https://red.ht/sig> <https://redhat.com/summit>
2018-05-29 10:57 GMT+02:00 Roman Mohr <rmohr@redhat.com>:
On Tue, May 29, 2018 at 10:43 AM, Roman Mohr <rmohr@redhat.com> wrote:
On Tue, May 29, 2018 at 10:06 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
FESCo approved an updated policy for packages which fail to build from source during mass rebuilds (FTBFS).
The updated policy is still at https://fedoraproject.org/w iki/Fails_to_build_from_source.
Highlights:
- packages which FTBFS are subject to orphaning if there is no maintainer acknowledgement within 8 weeks
- packages which FTBFS in two consecutive mass rebuilds will be retired soon after the second mass rebuild
Focusing on Hystrix, it has been reported failing on 2018-03-14, more than 10 weeks ago and it's failing to build since Fedora 26, totalling 3 consecutive mass rebuild failures. This put Hystrix in a candidate position for being orphaned.
The Hystrix package is used by oVirt Engine. The POM requires version 1.4.14 (released this on 6 Aug 2015) . Fedora 24 and CentOS Virt SIG has 1.4.21 (released this on 17 Nov 2015). Latest upstream version is 1.5.13.
Since in oVirt 4.3 we're aiming to support Fedora 28 we need to decide on what to do with Hystrix: - drop it as dependency? - update to latest? - try to fix build failure and keep current version?
Roman, current maintainer (in cc) is unresponsive, not replying to my needinfo since 2017-08-17
I simply missed it. At least a concrete ping would have been nice.
Ok, my failure. I got a ping.
NP, I'm happy you're not MIA :-) What's your view on this topic?
Best Regards,
Roman
Any volunteer for taking over?
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@redhat.com <https://red.ht/sig> <https://redhat.com/summit>
-- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://red.ht/sig> <https://redhat.com/summit>
On Tue, May 29, 2018 at 11:00 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
2018-05-29 10:57 GMT+02:00 Roman Mohr <rmohr@redhat.com>:
On Tue, May 29, 2018 at 10:43 AM, Roman Mohr <rmohr@redhat.com> wrote:
On Tue, May 29, 2018 at 10:06 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
FESCo approved an updated policy for packages which fail to build from source during mass rebuilds (FTBFS).
The updated policy is still at https://fedoraproject.org/w iki/Fails_to_build_from_source.
Highlights:
- packages which FTBFS are subject to orphaning if there is no maintainer acknowledgement within 8 weeks
- packages which FTBFS in two consecutive mass rebuilds will be retired soon after the second mass rebuild
Focusing on Hystrix, it has been reported failing on 2018-03-14, more than 10 weeks ago and it's failing to build since Fedora 26, totalling 3 consecutive mass rebuild failures. This put Hystrix in a candidate position for being orphaned.
The Hystrix package is used by oVirt Engine. The POM requires version 1.4.14 (released this on 6 Aug 2015) . Fedora 24 and CentOS Virt SIG has 1.4.21 (released this on 17 Nov 2015). Latest upstream version is 1.5.13.
Since in oVirt 4.3 we're aiming to support Fedora 28 we need to decide on what to do with Hystrix: - drop it as dependency? - update to latest? - try to fix build failure and keep current version?
Roman, current maintainer (in cc) is unresponsive, not replying to my needinfo since 2017-08-17
I simply missed it. At least a concrete ping would have been nice.
Ok, my failure. I got a ping.
NP, I'm happy you're not MIA :-) What's your view on this topic?
I am updating it right now to 1.5.13. I have no strong opinions. If oVirt will not use it anymore there is probably not much reason to keep it then. I don't think that it has wide adoption. Best Regards, Roman
Best Regards,
Roman
Any volunteer for taking over?
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@redhat.com <https://red.ht/sig> <https://redhat.com/summit>
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@redhat.com <https://red.ht/sig> <https://redhat.com/summit>
On Tue, May 29, 2018 at 11:11 AM, Roman Mohr <rmohr@redhat.com> wrote:
On Tue, May 29, 2018 at 11:00 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
2018-05-29 10:57 GMT+02:00 Roman Mohr <rmohr@redhat.com>:
On Tue, May 29, 2018 at 10:43 AM, Roman Mohr <rmohr@redhat.com> wrote:
On Tue, May 29, 2018 at 10:06 AM, Sandro Bonazzola <sbonazzo@redhat.com
wrote:
FESCo approved an updated policy for packages which fail to build from source during mass rebuilds (FTBFS).
The updated policy is still at https://fedoraproject.org/w iki/Fails_to_build_from_source.
Highlights:
- packages which FTBFS are subject to orphaning if there is no maintainer acknowledgement within 8 weeks
- packages which FTBFS in two consecutive mass rebuilds will be retired soon after the second mass rebuild
Focusing on Hystrix, it has been reported failing on 2018-03-14, more than 10 weeks ago and it's failing to build since Fedora 26, totalling 3 consecutive mass rebuild failures. This put Hystrix in a candidate position for being orphaned.
The Hystrix package is used by oVirt Engine. The POM requires version 1.4.14 (released this on 6 Aug 2015) . Fedora 24 and CentOS Virt SIG has 1.4.21 (released this on 17 Nov 2015). Latest upstream version is 1.5.13.
Since in oVirt 4.3 we're aiming to support Fedora 28 we need to decide on what to do with Hystrix: - drop it as dependency? - update to latest? - try to fix build failure and keep current version?
Roman, current maintainer (in cc) is unresponsive, not replying to my needinfo since 2017-08-17
I simply missed it. At least a concrete ping would have been nice.
Ok, my failure. I got a ping.
NP, I'm happy you're not MIA :-) What's your view on this topic?
I am updating it right now to 1.5.13. I have no strong opinions. If oVirt will not use it anymore there is probably not much reason to keep it then. I don't think that it has wide adoption.
An update here: Hystrix 1.5.12 is in rawhide working again since last week. The update for fc28 can be found in [1]. Best Regards, Roman [1] https://bodhi.fedoraproject.org/updates/FEDORA-2018-a1647d6783
Best Regards,
Roman
Best Regards,
Roman
Any volunteer for taking over?
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@redhat.com <https://red.ht/sig> <https://redhat.com/summit>
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@redhat.com <https://red.ht/sig> <https://redhat.com/summit>
2018-05-29 10:43 GMT+02:00 Roman Mohr <rmohr@redhat.com>:
On Tue, May 29, 2018 at 10:06 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
FESCo approved an updated policy for packages which fail to build from source during mass rebuilds (FTBFS).
The updated policy is still at https://fedoraproject.org/w iki/Fails_to_build_from_source.
Highlights:
- packages which FTBFS are subject to orphaning if there is no maintainer acknowledgement within 8 weeks
- packages which FTBFS in two consecutive mass rebuilds will be retired soon after the second mass rebuild
Focusing on Hystrix, it has been reported failing on 2018-03-14, more than 10 weeks ago and it's failing to build since Fedora 26, totalling 3 consecutive mass rebuild failures. This put Hystrix in a candidate position for being orphaned.
The Hystrix package is used by oVirt Engine. The POM requires version 1.4.14 (released this on 6 Aug 2015) . Fedora 24 and CentOS Virt SIG has 1.4.21 (released this on 17 Nov 2015). Latest upstream version is 1.5.13.
Since in oVirt 4.3 we're aiming to support Fedora 28 we need to decide on what to do with Hystrix: - drop it as dependency? - update to latest? - try to fix build failure and keep current version?
Roman, current maintainer (in cc) is unresponsive, not replying to my needinfo since 2017-08-17
I simply missed it. At least a concrete ping would have been nice.
Please re-check your mailbox.
Best Regards,
Roman
Any volunteer for taking over?
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@redhat.com <https://red.ht/sig> <https://redhat.com/summit>
-- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://red.ht/sig> <https://redhat.com/summit>
participants (2)
-
Roman Mohr -
Sandro Bonazzola