Univention Bugzilla – Bug 35661
must_have_no_conflicts_apps tests for any conflicting package
Last modified: 2015-04-09 09:49:57 CEST
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']
Fixed in univention-management-console-module-appcenter 4.1.20-18.326.201503241422 Also added a ucs-test
Should be / can be backported to UCS 3.2. No apps in 4.0 do have this issue. This was 3.2 specific (Zarafa -> ownCloud 6)
OK: all packages have to be installed to be a conflicted app OK: Code-Review OK: test (reproduces the error) OK: YAML
<http://errata.univention.de/ucs/4.0/120.html>