Bug 31020 – pre post Update Hook in /usr/sbin/univention-ucc-software-update

Bug 31020 - pre post Update Hook in /usr/sbin/univention-ucc-software-update


Summary:	pre post Update Hook in /usr/sbin/univention-ucc-software-update

Status:	CLOSED WORKSFORME

Product:	Z_Univention Corporate Client (UCC)
Classification:	Unclassified
Component:	General
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal
Target Milestone:	UCC 2.0
Assigned To:	Moritz Muehlenhoff
QA Contact:	Erik Damrose

URL:
Keywords:	interim-3

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-04-10 17:38 CEST by Felix Botner
Modified:	2014-06-12 09:19 CEST (History)
CC List:	2 users (show)

See Also:
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:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Felix Botner

2013-04-10 17:38:09 CEST

We need a pre and post update hook in /usr/sbin/univention-ucc-software-update.

Comment 1 Felix Botner

2013-04-11 12:41:04 CEST

> - Da wir uns nicht darauf verlassen können, dass für das Update immer unser
> Tool verwendet wird, sollten wir ein neues Paket bauen, welches keine (!)
> Abhängigkeiten hat und von allen UCC Paketen als Pre-Depends aufgeführt
> wird. Das ist zwar nicht optimal, vor allem nicht aus Sicht des Debian
> Paketformat, aber das sollte uns die Möglichkeit geben, vor jedem Update
> bestimmte Skripte auszuführen.

Hier sollten wir für unterschiedliche Updates eigene Binary Pakete verwenden, 
also:
Pre-Depends: ucc-update-helper-1.0rev2

Comment 2 Erik Damrose

2013-04-17 17:13:55 CEST

Relevant for ucc1.1

Comment 3 Moritz Muehlenhoff

2013-12-18 11:20:26 CET

Maybe a similar mechanism to preup/postup can be implemented

Comment 4 Moritz Muehlenhoff

2014-05-15 15:53:00 CEST

We discussed the potential benefits and disadvantages and came to the conclusion that updates should rather be pushed through software updates alone. The handling of updates in UCC is different in comparison to UCS: In UCS the /etc/apt.sources.list.d gets automatically updated in case an update is available, while in UCC the entire system partition is replaced. We rather need the equivalent of preup.sh and postup.sh when updating images in the initramfs. A bug for that already exists and I've tagged it for evaluation in the next release (Bug 31384). 

For the standard software updates separate updates scripts are rather problematic in conparison to packages:
- they are not validated compared to DEB packages/Secure Apt unless separate signing logic is implemented
- they need a separate logic to track when and how often they should be executed (e.g. should they be executed with every apt-get dist-upgrade?)

Comment 5 Moritz Muehlenhoff

2014-05-19 07:18:37 CEST

As discussed per comment 4

Comment 6 Erik Damrose

2014-05-19 08:59:12 CEST

Verified

Comment 7 Moritz Muehlenhoff

2014-06-12 09:19:54 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".