Backport updates to 5.0.12
Bug #1245593 reported by
Jonathan Riddell
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
owncloud (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned | ||
Quantal |
Won't Fix
|
Undecided
|
Unassigned | ||
Raring |
Won't Fix
|
Undecided
|
Unassigned | ||
Saucy |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The current version of owncloud in supported releases has known security bugs. We should update to 5.0.12 in all releases.
TEST CASE:
install 5.0.10 on saucy and set up an account and some data
upgrade to 5.0.12 from -proposed and check you can still use all the features of owncloud
Related branches
Changed in owncloud (Ubuntu Trusty): | |
status: | New → Fix Released |
tags: |
added: verification-done removed: verification-needed |
To post a comment you must log in.
I tried to backport it to raring, as usual there are many dependencies which don't exist in raring so need removed with the 3rdparty files included directly in the package. However when I did this it would not let me get past the first page and register an account, it just gave a blank page. Fixes welcome but I guess for now the backport can only be on saucy.