Bug 40504 – block update, if (essential) univention packages are going to be removed

Bug 40504 - block update, if (essential) univention packages are going to be removed


Summary:	block update, if (essential) univention packages are going to be removed

Status:	RESOLVED DUPLICATE of bug 43613

Product:	UCS
Classification:	Unclassified
Component:	Update - univention-updater
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.1-x
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-01-27 09:07 CET by Felix Botner
Modified:	2018-04-14 13:51 CEST (History)
CC List:	2 users (show)

See Also:	41215
What kind of report is it?:	Bug Report
What type of bug is this?:	7: Crash: Bug causes crash or data loss
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	4: A User would return the product
User Pain:	0.160
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

2016-01-27 09:07:26 CET

We have seen in some cases, that during major updates apt-get has removed some essential univention packages.

We should check that in the updater (apt-get dist-upgrade) and preup.sh (pre update).

Better to block the update than having broken system.

Are there any debian specific ways to do something like this?

Comment 1 Felix Botner

2016-05-12 11:16:34 CEST

also, 

if apt-get -s dist-upgrade fails, we should abort the upgrade

Comment 2 Florian Best

2017-02-16 13:06:57 CET


*** This bug has been marked as a duplicate of bug 39092 ***

Comment 3 Florian Best

2017-02-22 15:29:23 CET

comment #1 was not fixed in Bug #39092, therefore this is a duplicate of Bug #43613.

*** This bug has been marked as a duplicate of bug 43613 ***