Bug 54342 – request for changing package dependencies for ucs-appliance-container

Bug 54342 - request for changing package dependencies for ucs-appliance-container


Summary:	request for changing package dependencies for ucs-appliance-container

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	General
Version:	UCS 5.0
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2022-01-16 09:39 CET by Gino Harlos
Modified:	2023-02-27 11:00 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
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):	bitesize, Cleanup, External feedback
Max CVSS v3 score:

Attachments
Patch suggestion (1.12 KB, patch) 2022-01-16 09:39 CET, Gino Harlos	Details \| Diff
dependencies cleanup (1.73 KB, patch) 2022-10-24 20:11 CEST, Gino Harlos	Details \| Diff
View All 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 Gino Harlos 2022-01-16 09:39:50 CET

Created attachment 10904 [details]
Patch suggestion

The headline should read as: Package univention-container-role-server-common and Package univention-role-server-common can move closer together again.
But I'm not 100% sure if packages univention-home-mounter and univention-maintenance are really needed.

Some facts about the required packages:
 - univention-firewall   : If an container has the right privileges they can use iptables without restrictions.
 - univention-nfs-server : NFS inside a container works well, if the container has the right permissions.
 - univention-portal     : was missing during any automated setup since first releas of UCS 5, but i don't know why.

And finaly the package univention-docker-container-mode is incompatible with "univention-container-mode" from ucs-appliance-container.

Comment 1 Gino Harlos 2022-10-24 20:09:32 CEST

Short update since commit ( https://github.com/univention/univention-corporate-server/commit/b04c19d673b3ba4dad5320e2bfaca8dad87d78f0 ), univention-docker-container-mode are not longer incompatible with "univention-container-mode" from ucs-appliance-container ( https://github.com/univention/ucs-appliance-container ).

podman exec -it dc.ucs.example dpkg -L univention-docker-container-mode
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/univention-docker-container-mode
/usr/share/doc/univention-docker-container-mode/changelog.Debian.gz
/usr/share/doc/univention-docker-container-mode/copyright

From ucs-appliance-container's point of view, almost all dependencies can be eliminated with pull-request ( https://github.com/univention/ucs-appliance-container/pull/7 ). Or better: Since UCS 5.0-2 and commit b04c19d673b3ba4dad5320e2bfaca8dad87d78f0 we can close this Bug :)

Maybe nice to cleanup the univention-container-role-server-common and univention-container-role-common, you will find container-role-common.cleanup.patch as patch suggestion.

Comment 2 Gino Harlos 2022-10-24 20:11:49 CEST

Created attachment 11000 [details]
dependencies cleanup