- Transcode: host on anduin for now
- iptables: ftp.netfilter.org has been discontinued
- mariadb: the mirror service only keeps the most current versions
available.
The reason is that our own box can output those kind of packets
rather frequently, and those packets immediately appear as
incoming. Since any non expected packet is logged, this clutters
the log. Dropping them in the "personal firewall" case is what is
wanted, but it has to be done before logging.
It's no longer built by default and is deprecated because it uses utmp,
wtmp, btmp, and lastlog; none of which are Y2038 safe, even on 64-bit
architectures.
Since this is commented out by default anyway, I don't think there's a
need for a freeze break.
1. Don't throw unspecified entries too early. Doing so caused various
rendering glitches. And we can now also check if an entry is
selected but it's parent not.
2. "menu"s in Kconfig can also have dependencies...
Some pre-existing .toml data files are found problematic after the
change, fix them and regenerate all rendered -kernel.xml files.
The issue is a new regression in 0.25.0, and it's causing test failures
in glib-networking and libsoup.
We know we are on Linux so we don't need the fancy #ifdef stuff, so we
can simplify the change into a sed.
Also create an ENTITY for qt5 or qt5-alternate and use that
to specify the qt5 dependenies.
The complete KF5/plasma packages should use the full qt5 build, but
the lxqt kf5/plasma components only need qt5-alternate.
Attention - you must have libxcrypt for this. If you are running an old
LFS release, install libxcrypt, then rebuild Shadow --with-yescrypt.
Technically if Shadow is built with PAM, then --with-{b,yes}crypt
switches are not necessary (but also do no harm). Just keep it there to
sync with LFS and prevent people building Shadow w/o PAM being locked
out of their system.
Well, my script did not handle package names with dashes correctly. So
some User Note links were mistakely removed. Recheck removed links
containing dashes and add them back if applicable.