Skip to content
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

Revert "redmine: mark as broken" #31211

Closed

Conversation

matthiasbeyer
Copy link
Contributor

This reverts commit f9c9c1d.

Motivation for this change

The Issue why this was marked as broken was already closed and I was able to build the package.

Things done
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions (debian with nix installed)
  • Fits CONTRIBUTING.md.

@matthiasbeyer
Copy link
Contributor Author

Sidenote: I'm not a user of redmine, I just noticed that the package was marked as broken for no reason (anymore).

@c0bw3b
Copy link
Contributor

c0bw3b commented Nov 4, 2017

Able to build is one thing but this package was marked as broken because of multiple security vulnerabilities in it.

According the the Redmine project itself the v2.5.2 we have here is affected by CVE-2015-8474 / CVE-2015-8346 / CVE-2015-8473 / CVE-2015-8537

That version is ~3y old anyway, so what it really needs is a serious refresh.

@matthiasbeyer
Copy link
Contributor Author

Well, yes. I'm not familiar with the Ruby packaging, so I'd rather close this...

@matthiasbeyer matthiasbeyer deleted the revert-redmine-broken branch November 4, 2017 08:46
@7c6f434c
Copy link
Member

7c6f434c commented Nov 4, 2017

Maybe replacing meta.broken with meta.knownVulnerabilities would be a better way now that the second attribute exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants