Also introduce entities for pip3 wheel and pip3 install for future use
(#18466). Reuse the entities for gpgme and libpwquality, so the missed
--no-user in libpwquality is fixed as well.
- 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. Move kernel section before emergency boot disk section. The reason
is in the emergency boot disk section we already need to mount the
ESP, so we need VFAT and the related NLS configuration.
2. Add "codepage=437,iocharset=iso8859-1" mounting the ESP. I'm not
sure if grub-install will do things properly if a different NLS
setting is used. With some (broken IMO) kernel configuration a mount
command without explicit codepage and iocharset setting won't work at
all. And I don't like the idea to force the users to set
FAT_DEFAULT_CODEPAGE=437 or FAT_DEFAULT_IOCHARSET="iso8859-1" in
kernel configuration.
3. Use "mount --mkdir" instead of a separate "mkdir -pv" command
(again).
4. Wrap long commands at 80 characters.
5. The ESP entry in fstab is optional. Personally I prefer it in fstab
because I hate the Windoge behavior (hiding the ESP from the user).
6. Update kernel and LFS version in example grub.cfg file (again).
Add the fstab entry before mounting the partition, so we can omit device
node path and mount option. Also use --mkdir option so we don't need
mkdir -pv.
By the way bump the kernel version and LFS version in example grub.cfg.
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.
1. It does not make sense to tell the users "enable CONFIG_DRM_NOUVEAU"
here. It's the kernel driver needs the firmware, not the opposite.
So drop the kernel configuration section here.
2. Port the script to Python 3. I've checked the md5sums of the output
binaries and they are same with the original version.
3. Bump the NVIDIA driver blob version. If the blob is not downloaded
or extracted, the script will tell to download 340.32, so we use the
same version to avoid confusion.
4. Update nouveau wiki link.
This is stupid and it will cause meaningless diffs in version control
(like this commit does :( ).
Remove the kernel version from the generated XML files. Add
kernel.version file into git to track the kernel version.
I don't know these FS very well so I did not change things, except:
- "SCSI_LOW_LEVEL" should be "SCSI_LOWLEVEL" (without the "_" between
"LOW" and "LEVEL").
- RAID append mode is deprecated, so I removed it.
And I've fixed some issues in kernel-config.py as well.
clarify the rationale of the package and kernel support.
Note that we actually do not need this package if we only need to mount
FAT fs, not create or check or relabel it.
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.
I'm pretty sure it's at least not "required": there are some
configurations running qemu "headless".
And it seems qemu does not refers to any X components directly. It uses
X through SDL or GTK3, and they are already in the dependencies.
The instruction was a part of archived xf86-video-{amdgpu,radeon} kernel
configuration section.
Remove the kernel configurations from AMDGPU and Radeon because they
really should belong to the Mesa page or Xorg Server page.
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.
It's not really QEMU specific.
By the way, move the "additional cfg unneeded on most systems" into the
bottom of the page, and adjust it to refer modesetting driver instead of
radeon driver.
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.
