Why not port encrypt to FreeBSD?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Yesterday
Yesterday
Support for PHP 8.4 is still there.
dereckson committed rOPSe5ec87dfe258: Allow systemd-hostnamed to create socket when called from Varlink (authored by dereckson).
Allow systemd-hostnamed to create socket when called from Varlink
Deployed on Dwellers, works like a charm.
dereckson updated the diff for D3658: Allow systemd-hostnamed to create socket when called from Varlink.
Allow to remove the socket too
dereckson planned changes to D3658: Allow systemd-hostnamed to create socket when called from Varlink.
Uninstalled certbot.
Pruned old Python 3 dependencies.
Updated EPEL repo to epel-release-10-6
Updated packages
Reinstalled certbot, now running under Python 3.12 too.
Just for information, working on T2113, I've first updated the packages non related to that conflict, so I had fresh packages for both systemd and selinux config.
https://snapcraft.io/starship - last update: 27 April 2023 - latest/edge
dereckson retitled D3658: Allow systemd-hostnamed to create socket when called from Varlink from Allow systemd-hostnamed to create socket when started by snap starinstalled with snap to Allow systemd-hostnamed to create socket when called from Varlink.
dereckson requested review of D3658: Allow systemd-hostnamed to create socket when called from Varlink.
dereckson added a comment to T2113: systemd-hostnamed service can't be launched - SELinux blocks it - starship.
Was looking to offer a fix upstream, like read hostname from /proc/sys/kernel/hostname on Linux, but then I've realised this is an interaction issue with snap, starship, systemd and SELinux.
Nasqueron DevCentral · If it had been much bigger the moon would have had a core of ice. · Powered by Phabricator