| Summary: | sys-apps/systemd-245_rc1-r1 has an automagic dependency on app-crypt/p11-kit | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Marien Zwart <marien.zwart> |
| Component: | Current packages | Assignee: | Gentoo systemd Team <systemd> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log from systemd-245_rc1-r1
emerge --info systemd::gentoo |
||
Created attachment 613458 [details]
emerge --info systemd::gentoo
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=abbe427ac62df0fa9ae86d86aa859c50152f72c8 commit abbe427ac62df0fa9ae86d86aa859c50152f72c8 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2020-02-23 17:25:20 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2020-02-23 17:25:20 +0000 sys-apps/systemd: add pkcs11 and pwquality USE flags Closes: https://bugs.gentoo.org/709378 Package-Manager: Portage-2.3.89_p9, Repoman-2.3.20_p79 Signed-off-by: Mike Gilbert <floppym@gentoo.org> sys-apps/systemd/metadata.xml | 2 ++ ...ystemd-245_rc1-r1.ebuild => systemd-245_rc1-r2.ebuild} | 15 ++++++++++++--- sys-apps/systemd/systemd-9999.ebuild | 6 +++++- 3 files changed, 19 insertions(+), 4 deletions(-) |
Created attachment 613456 [details] build.log from systemd-245_rc1-r1 sys-apps/systemd-245_rc1-r1 gained an automagic dependency on p11-kit that sys-apps/systemd-244 did not have. It looks like this is used to implement the PKCS#11 smartcard support mentioned in the NEWS file. This dependency should probably be explicit, and should possibly be optional (I added "-Dp11kit=$(meson_use pkcs11)" to the ebuild, and that seems to do the right thing). Comparing meson_options.txt between 244 and 245, libpwquality might need similar treatment. (I noticed because the dependency gets added (via libsystemd-shared) to /lib/systemd/systemd, along with a dependency on openssl's libcrypto, and I wondered why my initramfs size had gone up (both libraries are relatively large by initramfs standards). The size increase isn't really a big deal, but it seems wise to keep the dependencies of the PID1 process somewhat under control to make it less likely some bug or mistake renders the system unbootable.) build.log (from unmodified ebuild) attached.