You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Somehow the deb package generation in FPM does not seem to work with Ruby 3 anymore, see for instance: EESSI/filesystem-layer#64
Last month, someone already made a PR with a fix in the FPM repository, but this still hasn't been merged yet...
Since this github action automatically takes the latest Ruby container from Docker Hub, this functionality is also broken here now. I just did some manual tests and these confirmed that it still works fine with, for instance, ruby:2-alpine. Would it be possible to stick to that version for now (possibly on a separate branch), until the PR in the FPM project gets merged?
The text was updated successfully, but these errors were encountered:
Hi, thanks for letting me know 👍
Yes, we should go with the ruby:2-alpine image for now. Even if jordansissel/fpm#1740 gets merged, I would still want to wait until there is a tagged release.
Somehow the deb package generation in FPM does not seem to work with Ruby 3 anymore, see for instance:
EESSI/filesystem-layer#64
Last month, someone already made a PR with a fix in the FPM repository, but this still hasn't been merged yet...
Since this github action automatically takes the latest Ruby container from Docker Hub, this functionality is also broken here now. I just did some manual tests and these confirmed that it still works fine with, for instance,
ruby:2-alpine
. Would it be possible to stick to that version for now (possibly on a separate branch), until the PR in the FPM project gets merged?The text was updated successfully, but these errors were encountered: