Univention Bugzilla – Bug 16053
Test case: is any package hold back
Last modified: 2023-03-25 06:51:27 CET
In einem automatisierten Test sollte erkannt werden, ob Pakete auf dem System zurückgehalten wurden. +++ This bug was initially created as a clone of Bug #14610 +++ Beim Update auf 2.2-1 über das online-repository kann univention-kolab2 nicht installiert werden da univention-kolab2-tools nicht in maintained sondern in unmaintained liegt, univention-kolab2 aber davon abhängt.
Please add a test case for UCS 4.0 which checks if an package is hold back.
A new test script is created with the name "103_packages_held_back" in 00_base/ It checks if there are any packages marked to be held back in the system, and fails if there were any. Tested on single server and multi-server environments.
FAIL: change the test to "safe" as it only reads data without modifying anything. > ## exposure: careful FAIL: the limitation on DC master should be removed > ## roles: [domaincontroller_master] FAIL: remove the unneeded line for packages: > ## packages: [] FAIL: please reference Bug #14610 > ## bugs: [14610] OK: dpkg --set-selections <<<"ucs-test-base hold" OK: ./103_packages_held_back -vvvf FYI: "aptitude hold $pkg" uses a separate database, which is different from what "apt-get" and "dpkg" use.
(In reply to Philipp Hahn from comment #3) > FAIL: change the test to "safe" as it only reads data without modifying > anything. > > ## exposure: careful > FAIL: the limitation on DC master should be removed > > ## roles: [domaincontroller_master] > FAIL: remove the unneeded line for packages: > > ## packages: [] > FAIL: please reference Bug #14610 > > ## bugs: [14610] Done.
OK: r54186 OK: ./103_packages_held_back