Can the ELN be fixed to stop doing rebuild like this? Of course the issue is not in rubygem-thin but the issue is that once the Ruby side tag was merged, ELN did not bothered with build order and now there is rubygem-eventmachine which was built against Ruby 2.7 where is should have been build against Ruby 3.0. I can't rebuild it, because that would require release bump in Fedora (I don't want to do that, because Fedora maintainers should not be bothered with ELN, right?).

I think that ELN should try to follow the Rawhide build order. If it can't do that, then it should wait for manual intervention.

I think that ELN should have done gating or scratch build and check if the dependencies are the same as in Rawhide or something.

I think that ELN should check the build result for dependency issue and stop blindly submitting builds.



Vít




-------- Přeposlaná zpráva --------
Předmět: bpeck/jenkins-continuous-infra.apps.ci.centos.org's rubygem-thin-1.7.2-16.eln108 failed to build
Datum:  Mon, 11 Jan 2021 08:49:37 +0000 (GMT)
Od:     notificati...@fedoraproject.org
Komu:   vondr...@redhat.com



Notification time stamped 2021-01-11 08:49:35 UTC

bpeck/jenkins-continuous-infra.apps.ci.centos.org's rubygem-thin-1.7.2-16.eln108 failed to build
http://koji.fedoraproject.org/koji/buildinfo?buildID=1666628

--
You received this message due to your preference settings at https://apps.fedoraproject.org/notifications/vondruch.id.fedoraproject.org/email/50912

Attachment: OpenPGP_0x0CE09EE79917B87C.asc
Description: application/pgp-keys

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org

Reply via email to