This is a large, but still intermediate commit for KDE6 (kf6 and plasma6).
These are the key changes:
Update kf6 dependencies.
Remove kuserfeedback (it is now a part of kf6).
Move libdbusmenu-qt to General Libraries. It is still needed for LXQt, but
will be remmoved when LXQt moves to Qt6 and LF6/Plasma6.
Made some changes to bluez to use &root;.
Commented out kmix, libkcddb, and k3b. These are still kf5 apps and would
require adding back most of kf5 to the book. It's easier to just wait for
these to be updated to qt6/kf6.
Removed references to the full qt5 package in LXQt packages. It mkes no sense
now that Qt6 is in the book to also build the full (deprecated) Qt5 package.
It may makes sense to just remove the full Qt5 package from th ebook now.
Renamed an internal referece from plasma5-build to just plasma-build in polkit
and mesa.
Upstream commit b16b19885c5383cd0499503617b98ceb188c898e seems
to fix obexd operation on non-systemd systems. Therefore we
shouldn't need the patch anymore.
It's almost a plain "conversion". Exceptions:
- In elogind, [CGROUPS] is dropped because it's in LFS now.
- In libusb, move the kernel configuration to match the layout of other
packages.
1. I'm pretty sure MD5, SHA1, and KEY_DH_OPERATIONS are not needed
because I've tried testing bluez w/o them.
2. Some options mentioned by the package's README should be added.
3. The menu hierarchy of Cryptographic API section has been changed in
recent kernel releases so we need to adapt.
4. Let's not encourage people to use CONFIG_EXPERT.
In the systemd unit file of bluez-5.64, there is:
ProtectSystem=full
ReadWritePaths=/var/lib/bluetooth
The combination of these two options make systemd to bind mount /
recursively and read-only to /run/systemd/unit-root in a new mount
namespace, then bind mount /var/lib/bluetooth to
/run/systemd/unit-root/var/lib/bluetooth, then run bluez in the chroot
at /run/systemd/unit-root in the separate namespace.
This helps to reduce the potential damage if a bluez security
vulnerability is exposed. But, if /var/lib/bluetooth does not exist,
systemd will fail to bind mount it and complain:
bluetooth.service: bluetooth.service: Failed to set up mount
namespacing: /run/systemd/unit-root/var/lib/bluetooth: No such
file or directory
As a simple workaround, just create this directory at installation. A
more elegant solution will be shipped in bluez-5.65:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=0905a06
Q: Why -m700?
A: https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=edc69d2
I know it is somewhat useless, but I don't like them for
two reasons: first they cannot be seen, and I do not like things I
cannot see. Second, git highlights them, and this is disturbing...
Update to qpdf-10.2.0
Update to libgxps-0.3.2
Update to babl-0.1.86
Update to libqmi-1.28.2
Update to poppler-21.03.0
Update to URI-5.09 (Perl Module)
Update to gtksourceview4-4.8.1
Update to OpenSSH-8.5p1 (and ssh-askpass-8.5p1)
libwacom: Correct version number
libwacom: Add libwacom-show-stylus
bluez: Drop the patch
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@24333 af4574ff-66df-0310-9fd7-8a98e5e911e0
In the process, some attributes in single quotes have been changed to double
quotes, and a few attribute lists have been written on one line instead of
several lines.
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@24236 af4574ff-66df-0310-9fd7-8a98e5e911e0
Update to WebKitGTK+-2.30.5
Update to asciidoc-9.1.0
Update to xterm-366 (Security Update)
Fix a crash in bluez when using A2DP-based bluetooth devices
Belatedly mark Jinja2 as a security update
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@24213 af4574ff-66df-0310-9fd7-8a98e5e911e0
