Bug 38728 – Unexpected behavior and display order of information with ConflictedSystemPackges when installing an app

Bug 38728 - Unexpected behavior and display order of information with ConflictedSystemPackges when installing an app


Summary:	Unexpected behavior and display order of information with ConflictedSystemPac...

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	App Center
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	App Center maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-06-19 10:02 CEST by Erik Damrose
Modified:	2020-07-03 20:52 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.057
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 Erik Damrose

2015-06-19 10:02:31 CEST

If i install an app and a conflicted system package as definied in its .ini is detected, the following happens:
Tested with zarafa, conflict with tomcat6
- univention-install tomcat6
- Try to install zarafa via app center
-- Consistency check does run, shows which packages will be installed
-- Click install to really install zarafa: Warning about tomcat6 is shown [1]
-- Click cancel
- univention-remove tomcat6
- Click install again
-- A warning is shown about a conflict with tomcat6 [2]
-- Click Cancel
-- Click install again: Installation is possible

[1] This should be shown directly after executing the consistency check
[2] Some cache is probably not updated, leading to this not expected error

Comment 1 Dirk Wiesenthal

2017-04-05 14:54:33 CEST

Should not have improved in the meantime

Comment 2 Ingo Steuwer

2020-07-03 20:52:24 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.