Bug 34851

Summary:	univention-ucc-software-update without policy
Product:	Z_Univention Corporate Client (UCC)	Reporter:	Moritz Muehlenhoff <jmm>
Component:	Documentation	Assignee:	Moritz Muehlenhoff <jmm>
Status:	CLOSED FIXED	QA Contact:	Erik Damrose <damrose>
Severity:	enhancement
Priority:	P5	CC:	gohmann, jmm, meybohm
Version:	unspecified	Keywords:	interim-4
Target Milestone:	UCC 2.0
Hardware:	Other
OS:	Linux
What kind of report is it?:	---	What type of bug is this?:	---
Who will be affected by this bug?:	---	How will those affected feel about the bug?:	---
User Pain:		Enterprise Customer affected?:
School Customer affected?:		ISV affected?:
Waiting Support:		Flags outvoted (downgraded) after PO Review:
Ticket number:		Bug group (optional):
Max CVSS v3 score:

Description Moritz Muehlenhoff

2014-05-15 16:03:17 CEST

+++ This bug was initially created as a clone of Bug #32296 +++

Ticket#: 2013082121001597 ] Update UCC

At the moment there is no easy way to deploy an update (like done with univention-ucc-software-update) on a client without defining a UCC software update policy.

A switch should be added to univention-ucc-software-update (--force?) so that the user may update a UCC client without having to define and link a policy.

Comment 1 Moritz Muehlenhoff

2014-05-23 12:21:22 CEST

Documented in revision 50594

Comment 2 Erik Damrose

2014-06-02 14:07:13 CEST

Documentation verified

Comment 3 Moritz Muehlenhoff

2014-06-12 09:19:33 CEST

UCC 2.0 has been released:
 http://docs.univention.de/release-notes-ucc-2.0.html

If this error occurs again, please use "Clone This Bug".