-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
nextcloud 16.0.10 release missing #19976
Closed
Labels
Comments
flokli
added
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
bug
labels
Mar 15, 2020
10 tasks
I guess that is already fixed by #19362 for 16.0.9 and a typo with the advisory. 16.0.10 is not released yet. You can find the release schedule at the wiki here on GitHub. |
Oh,m yeah sorry it's supposed to be 16.0.9 |
flokli
added a commit
to flokli/nextcloud-security-advisories
that referenced
this issue
Mar 16, 2020
Turns out, this was a typo, and this is already fixed in 16.0.9 by nextcloud/server#19362. See nextcloud/server#19976 for context. Closes: nextcloud/server#19976
flokli
added a commit
to flokli/nextcloud-security-advisories
that referenced
this issue
Mar 16, 2020
Turns out, this was a typo, and this is already fixed in 16.0.9 by nextcloud/server#19362. See nextcloud/server#19976 for context. Closes: nextcloud/server#19976 Signed-off-by: Florian Klink <[email protected]>
Fixed in nextcloud/security-advisories#21, PTAL. |
flokli
added a commit
to flokli/nixpkgs
that referenced
this issue
Mar 16, 2020
includes fix for nC-SA-2020-015. See nextcloud/server#19976, the SA currently has a typo - adressed in nextcloud/security-advisories#21.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
How to use GitHub
Steps to reproduce
Expected behaviour
It should be hosted there.
Actual behaviour
It's currently not available.
Server configuration
This is for packaging Nextcloud for the current (phasing out) stable distro release, so we'd like to keep the 16.x track
The text was updated successfully, but these errors were encountered: