On Fri, 2021-05-14 at 12:16 +0200, Eric Schirra wrote:
With "you" I mean suse or the one who is responsible for the macros / the build service / the parsing of the spec file. That was probably a translation mistake. In my opinion the spec file is correct, but the evaluation of the macros in an if loop has an error.
Please stop intermingling openSUSE / SUSE. openSUSE, the distribution you are using, is a community distribution. SUSE as a company is helping to maintain part of the packages / toolchains, based on their needs for their enterprise products. But we cannot ask from a company, that uses our distro as a base, to contribyte to packages they have no customer base for. So, 'you' as in 'SUSE' makes no sense. If they would have a customer willing to pay for the feature you ask, they would dedicate resources for it.
And why only me? The main question was not from me. So minimum two persons want cyrus. And I think a lot of others just don't even know.
Rally up people to fix the package - can be you, or other people interested in the package. But don't 'ask' any random person to fix something they do not use or care for.
But the answers show me again and more and more recently, the ignorance or this dismissal and discussion of problems. What's going on at suse? Sad sad.
To look at the problem in the spec file in server:mail %if %{defined systemd_requires} %global with_systemd 1 %endif %bcond_with systemd … %if %{with systemd} BuildRequires: systemd Requires(pre): %fillup_prereq %systemd_requires This is wrong and probably misunderstood by the packager in first place: %if %{defined systemd_requires} => this is unusable in the light of the scheduler: no package is yet installed, hence nothing defines systemd_requires (would come from the package systemd-rpm-macros), thus the %global definition won't happen in the scheduler. %bcond_with means: by default, build without, except if specified otherwise (e.g. osc build --with=systemd; obviously not done by OBS) It's never specified otherwise - hence: build without systemd (in 2021, where basically every supported distro uses systemd, I'd rather change this to bcond_withou, make the default WITH systemd, and make the others exceptions) To make things fun, though: %if %{defined systemd_requires} is true in the context of the actual build: the setup worker VM has systemd-macros installed (and systemd-mini, as other packages pull it in), and thus installs the correct files, and the dep generator in the end also has it defined. Hope this helps to get somebody started to actually do the fixing now. cheers, Dominique