Overview
Request 834769 superseded
- Migrate multi-spec build to multibuild.
- Update to version 2.36...
Depends on rq#834532.
This is a large rewrite of a spec file. One of the flavors is failing now. It needs to update build system itself, as the libmount1-mini provides library needed for the build system itself. To prevent build loops, it needs update of the build system of core packages (use util-linux-mini that does not require systemd).
- Created by sbrabec
- In state superseded
- Supersedes 833345
- Superseded by 845053
-
Open review for
factory-staging
Flavor "" and Flavor "standard" seem to be doing the same thing, i.e. we duplicate binaries there
First experiments in Staging are desasterous. Main issue:
rpm-build requires util-linux; util-linux is not provided by util-linux-mini and as such, mini becomes no possible flavor to be installed (which would be mandatory for ring0)
this in turn results in util-linux (based on the dep) and util-linux-mini (project vminstall) to be attempted as parallel installs - resulting in file conflicts.
Request History
sbrabec created request
- Migrate multi-spec build to multibuild.
- Update to version 2.36...
Depends on rq#834532.
This is a large rewrite of a spec file. One of the flavors is failing now. It needs to update build system itself, as the libmount1-mini provides library needed for the build system itself. To prevent build loops, it needs update of the build system of core packages (use util-linux-mini that does not require systemd).
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
licensedigger accepted review
ok
dimstar_suse set openSUSE:Factory:Staging:B as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:B"
dimstar_suse accepted review
Picked "openSUSE:Factory:Staging:B"
dimstar accepted review
dimstar_suse added factory-staging as a reviewer
Being evaluated by group "factory-staging"
dimstar_suse accepted review
Unstaged from project "openSUSE:Factory:Staging:B"
RBrownSUSE set openSUSE:Factory:Staging:A as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:A"
RBrownSUSE accepted review
Picked "openSUSE:Factory:Staging:A"
dimstar declined review
util-linux is too low level to work with a -min flavor.
As it's part already of the VMinstall statement, the -mini flavor figures in ALL OBS worker VMs; which blocks the inclusion of 'real' util-linux into the publishable products (like installation-images, containers,…)
dimstar declined request
util-linux is too low level to work with a -min flavor.
As it's part already of the VMinstall statement, the -mini flavor figures in ALL OBS worker VMs; which blocks the inclusion of 'real' util-linux into the publishable products (like installation-images, containers,…)
dimstar_suse reopened request
Reopened via staging workflow.
dimstar_suse added factory-staging as a reviewer
Being evaluated by group "factory-staging"
dimstar_suse accepted review
Unstaged from project "openSUSE:Factory:Staging:A"
dimstar_suse declined request
Declined via staging workflow.
superseded by 845053
58+- Include pam_securetty in login.pamd again (bsc#1033626)
That part will still lead to the issues documented in comment #4 on that bug.
REading through the bug, it's not so clear if that change is that much wanted nowadays
That mini flavor is likely not going to fly: we have util-linux-mini in VMInstall, meaning it must be present in ALL virtual machines being built up by OBS.
But then we have packages like installation-images, that MUST require the real util-linux (they do, via BuildRequires) as we don't want to ever end up with the -mini flavor on runtime systems - but there, the -mini (from vminstall) conflicts with the BuildRequires of the regular util-linux
Does this mean that at least we have to have a util-linux-mini.spec without multibuild?
No, the concept of a throwaway/bootstrap-only -mini variant is not suitable for util-linux.
The problem is that util-linux is part of the minimal VM setup for OBS workers (would be util-linux-mini with the -mini flavor) - but as soon as that is being used in a VM to build up, it is no longer possible to install BuildRequire util-linux (full variant, where needed) as this will always conflict with util-linux-mini (as used by worker VM buildup)
The original concept worked, as util-linux was used on final systems the same way as it was in the worker VM; and only 'extended' by utilities that are shipped in util-linux-systemd
I wonder why in past util-linux-systemd was required at all ... is this due to the requirement of libsystemd0 package? In other words to avoid dependency loop between util-linux and systemd?
with util-linux being used to build up literally every single worker VM, it's dependencies are best kept 'small' (ring0 / bootstrap)
systemd is ring1 - i.e. not required to get 'a distro build starting'
The few things that link libsystemd were thus shipped in util-linux-systemd (the name is probably not that fortunate - the fact that systemd linkage is the driver does not really belong in the package name)