Otto Urpelainen kirjoitti 29.9.2021 klo 20.39:
Vít Ondruch kirjoitti 29.9.2021 klo 13.56:
Dne 27. 09. 21 v 19:38 Otto Urpelainen napsal(a):
I have determined the reason for those changes is that the files
inside jekyll 4.2.1 gem have CRLF line endings.
This seems strange. Was there really some change like this in
upstream? Then it should be possible to understand the reason for such
change from Git log, but I can't find such change in Git neither I can
see CRLF in e.g.
https://raw.githubusercontent.com/jekyll/jekyll/master/lib/jekyll.rb.
Therefore I suspect that this might be release engineering issue.
Somebody released the gem from Windows where it previously was
released from Linux. This is something upstream should address.
The reason why I did not contact upstream yet was that I was not able to
find any specification or best practices saying that gems should be
released in one form or another. I guess I can write to upstream and
notify them that this change has caused trouble, maybe it was just an
accident and they want to revert to avoid any further trouble:
https://github.com/jekyll/jekyll/issues/8826
Upstream confirmed that this was a mistake. A new release should be
available in a few days, I will wait for this.
I wonder if this should be considered as a single incident that is
unlikely to repeat, or as something that can happen to any Ruby package
at any time, and should be protected against somehow? Maybe in different
conditions the build would have succeeded, but the unusual line endings
would cause other problems at user installations.
Otto
_______________________________________________
ruby-sig mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
