This reverts commits 3fb4a15096
and 0e8350ca14.
Either building with meson or other upstream changes was causing
issues with booting, and I didn't have time to debug this properly.
This is needed because an additional property was added and the
tests fail otherwise. I think adding of the property is OK, it's
fully backwards compatible.
Also use %if 0 syntax to make it easy to copy&paste the commands.
Error: Transaction check error:
file /usr/share/polkit-1/rules.d from install of systemd-233-1.fc27.x86_64 conflicts with file from package polkit-0.113-7.fc26.x86_64
What is included:
- .wants directories
- for our own targets listed in systemd.special(7)
This is not supposed to cover all possible .wants and .requires and .d
dirs for all units, or even targets, or even just our targets, but only
the reasonably common ones that we provide.
It still fails in koji, and I'd have to download each package from
koji by hand to find out what is the issue (or wait until tomorrow for
a compose). Let's just nuke the whole thing, all deps should be installed.
Build failed with the following:
Traceback (most recent call last):
File "./hwdb/parse_hwdb.py", line 195, in <module>
groups = parse(fname)
File "./hwdb/parse_hwdb.py", line 136, in parse
parsed = grammar.parseFile(fname)
File "/usr/lib/python3.6/site-packages/pyparsing.py", line 2142, in parseFile
file_contents = f.read()
File "/usr/lib64/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 15765: ordinal not in range(128)
In mock, LC_CTYPE is unset, so python3 defaults to ascii, uselessly.
I think "ID_VENDOR_FROM_DATABASE=VENGIT Korlátolt Felelősségű Társaság"
is the issue here.
The header on the patch is fake. git am does not deal well with just
diff output, mumbling the following:
Applying: seccomp: rework seccomp code, to improve compat with some archs
Applying:
fatal: empty ident name (for <>) not allowed
We should really move away from mucking around with text patches.
We don't expect those calls to fail (they should work fine both
with systemd running and without). But if they fail, most likely
some unit is missing or misspelt, which we want to catch.
koschei builds are failing on systemd.rpm:
DEBUG util.py:421: error: unpacking of archive failed on file
/etc/dbus-1/system.d/org.freedesktop.hostname1.conf;581cb002: cpio: open
DEBUG util.py:421: error: systemd-232-2.fc26.x86_64: install failed
Only fall back to "dns" if nss-resolve is not installed (for the
architecture of the calling program). Once it is, we never want to
fall back to "dns" as that breaks enforcing DNSSEC verification and
also pointlessly retries NXDOMAIN failures.
C.f. https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=5e00954
