Bug 38220 - must_have_no_conflicts_apps tests for any conflicting package
must_have_no_conflicts_apps tests for any conflicting package
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: App Center
UCS 3.2
Other Linux
: P5 normal (vote)
: UCS 3.2-x
Assigned To: App Center maintainers
:
Depends on: 35661
Blocks:
  Show dependency treegraph
 
Reported: 2015-04-09 09:49 CEST by Dirk Wiesenthal
Modified: 2017-04-07 11:39 CEST (History)
5 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

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Wiesenthal univentionstaff 2015-04-09 09:49:57 CEST
Backport to UCS 3.2. Otherwise this bug does not make much sense. Zarafa -> ownCloud is bugged in UCS 3.2. In UCS 4.0 not anymore.

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

must_have_no_conflicts_apps tests if any package in defaultpackages of a conflicting app is installed

 if any(package_manager.is_installed(package) for package in app.get('defaultpackages')):
    ...

This is somehow wrong in situations where different apps share some default packages (like owncloud5 and owncloud6 do) leading to false positive conflict detection like described in http://forum.univention.de/viewtopic.php?t=3417:
Zarafa Update is blocked because of installed owncloud5 but zarafa app only has a conflict with owncloud6.


One may change toe test from any() to all() to avoid this but this may break other conflicts that depend on any() like:

samba-memberserver conflicts with samba4 => ['univention-samba4', 'univention-s4-connector']
samba3 conflicts with samba4 => ['univention-samba4', 'univention-s4-connector']