-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Ruby from 2.6.6 to 2.7.x #488
Comments
Synology ships with this? |
Doesn't look like an upgraded Ruby 2.6.9 package has been released yet. https://launchpad.net/%7Ebrightbox/+archive/ubuntu/ruby-ng/+index?batch=75&memo=75&start=75 However according to Ruby, the maintenance for 2.6 is ending next month, so probably better to move to Ruby 2.7.2+ since thats the latest version that redmine 4.2 supports. |
Someone must have created a package for it. Its been in their package manager for years now. |
Pushed release 4.2.3-1 @sameersbn Build needs to be kicked off |
done! |
Hi there, |
Well thats annoying, I checked https://www.redmine.org/projects/redmine/wiki/RedmineInstall which only mentions avoiding 2.7.0/2.7.1 Found your issue. https://www.redmine.org/issues/36584 Seems like we should revert this change until 4.2.4 is released... |
Posted 4.2.3-2 that reverts back to Ruby 2.6.6. Hopefully redmine 4.2.4 will fix the issue with Ruby 2.7 |
I hope also ;) |
Should leave this open since its not actually resolved yet |
Redmine 4.2.4 has been released. Will update docker image |
Well, i guess not quite yet, they posted the changelog but haven't uploaded the 4.2.4 tarball. |
Now, it is released |
So not sure whats happening over there but who ever did the release attached it to the Downloads wiki page instead of uploading it to the normal releases url. https://www.redmine.org/releases/. So our standard download link doesn't work. Posted an issue to redmine.org, perhaps they are having some server issues and this is a temporary situation. |
Now, it should be online... |
Yup, sorry was busy last week. Looking at it now
…On Tue, Mar 8, 2022 at 10:33 AM CSCSxx ***@***.***> wrote:
Now, it should be online...
—
Reply to this email directly, view it on GitHub
<#488 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABK2RGKHASPAWEMVPGM2RIDU65XLXANCNFSM5N42RIAQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
--
Jonathan Cormier
Software Engineer
Voice: 315.425.4045 x222
http://www.CriticalLink.com <http://www.criticallink.com/>
6712 Brooklawn Parkway, Syracuse, NY 13211
<https://www.linkedin.com/company/critical-link-llc>
<https://twitter.com/Critical_Link>
|
Just pushed 4.2.4 and 4.1.6. However, looks like only "lastest" build got triggered. |
Tags 4.2, 4.2.4, and 4.1.6-r2 have been pushed |
Unfortunately, I can't do the upgrade myself within my Dockerfile because I'm using it on a Synology NAS and can't really access the core from the outside.
But I also think in general that it makes sense to close the known security gaps in this way
The text was updated successfully, but these errors were encountered: