| Summary: | Backport Candidate: Update owncloud-client to 2.2.4 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | José Jorge <lists.jjorge> |
| Component: | Backports | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | fri, lewyssmith, mageia, sysadmin-bugs |
| Version: | 5 | Keywords: | Backport, validated_backport |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA5-32-OK MGA5-64-OK | ||
| Source RPM: | owncloud-client | CVE: | |
| Status comment: | |||
|
Description
José Jorge
2016-10-13 18:01:40 CEST
RPMS : libocsync2-2.2.4-1.mga5 libowncloudsync2-2.2.4-1.mga5 owncloud-client-2.2.4-1.mga5 SRPM : owncloud-client-2.2.4-1.mga5 Keywords:
(none) =>
Backport I have been using this version for ten days without any bug, on both i586 and x86_64 for 5 Mageia computers. Whiteboard:
(none) =>
MGA5-32-OK MGA5-64-OK Sucessfully upgraded a friends mga5-64 owncloud client from 2.1.1 to this 2.2.4-1 For fresh installs, do you know if Bug 18982 is resolved? CC:
(none) =>
fri Is this backport OK to validate? You are the best judges. If so, please add 'validated_backport' to the Keywords. TIA CC:
(none) =>
lewyssmith Done Keywords:
(none) =>
validated_update
Nicolas Lécureuil
2016-11-07 23:24:18 CET
Keywords:
validated_update =>
validated_backport moved. Status:
ASSIGNED =>
RESOLVED |