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

Jump to bottom

couchdb: security update to 2.2.0 #1314

Closed
l2dy opened this issue Aug 9, 2018 · 3 comments
Closed

couchdb: security update to 2.2.0 #1314

l2dy opened this issue Aug 9, 2018 · 3 comments
Labels
security Topic/issue involves a security issue/fixed stalled Topic/issue has stalled upgrade Topic/issue involves a package upgrade

Comments

@l2dy
Copy link
Member

l2dy commented Aug 9, 2018

CVE-2018-11769
@l2dy l2dy added upgrade Topic/issue involves a package upgrade security Topic/issue involves a security issue/fixed labels Aug 9, 2018
@MingcongBai
Copy link
Member

Upgrading to 2.2.0 even if it's a patch release...

All users should upgrade to CouchDB 2.2.0.

Upgrades from previous 2.x versions in the same series should be seamless.

@MingcongBai
Copy link
Member

This package, even able to be built with a patched rebar.config.script to "fix" Erlang version detection, will crash with Erlang 21 - which is the current version available from the stable repository.

Fixing this package will require introduction of a "compat" 20.x erlang package, making it only able to be fixed in the explosive branch. Or alternatively, we can wait for the next release, marking to-explosive and stalled.

@MingcongBai MingcongBai added stalled Topic/issue has stalled to-explosive and removed to-stable labels Aug 17, 2018
@l2dy
Copy link
Member Author

l2dy commented Dec 18, 2018

To be superseded.

@l2dy l2dy closed this as completed Dec 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
security Topic/issue involves a security issue/fixed stalled Topic/issue has stalled upgrade Topic/issue involves a package upgrade
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MingcongBai @l2dy