Re: ELN build order

[Stephen Gallagher <sgallagh@xxxxxxxxxx>]

On Mon, Jan 11, 2021 at 5:55 AM Vít Ondruch <vondruch@xxxxxxxxxx> wrote:

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.

This is on our todo list, but we have been balancing a lot of things at the same time and haven't been able to get to it yet. Believe me, we want this fixed ASAP because it causes us (the ELN maintainers) a lot of problems.

 

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'm not sure where or when in the process you are suggesting this would happen. ELN gates the compose, but not the builds.

 

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

Again, I'm not sure what you're asking for, here. 

 

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx