rpi-firmware-network (subpackage of linux-firmware) now provides the
necessary wifi blobs, so rpi-firmware no longer includes them and now
depends on rpi-firmware-network.
Closes: #26939 [via git-merge-pr]
Signed-off-by: Piraty <piraty1@inbox.ru>
Now that linux-firmware-network provides the necessary wifi blobs for
the Raspberry Pi, we can remove them from rpi-firmware and provided them
in a new rpi-firmware-network subpackage.
The linux-firmware-network subpackage is modified so that only the brcm
not related to the Raspberry Pi is included.
Remove pam_tally from system-login. The pam_tally module is deprecated
as of PAM 1.4.0 and was removed on PAM 1.5.0.
Remove pam_lastlog optional, since it's no longer built on musl and
conflicts with the logs recorded by login(1).
Remove pam_ck_connector, since it's no longer provided.
Fix license name.
The file was created in chroot_prepare(), but the configuration
directory was being cleaned in chroot_sync_repodata(). This commit moves
the configuration to after the directories are created.
Fixes#25534
Replacing the outdated and broken python{,3}-iso-8601 with the new
python{,3}-iso8601, the preferred provider for cryptography, allows
previously failing tests to pass.
The homepage listed on the PyPI site returns NXDOMAIN, the PyPI release
is two years old, and it fails to parse valid ISO-8601 date strings (as
seen when trying to run tests in python-cryptography).
Technially, libressl-devel doesn't depend on libressl.
However, base-chroot depends on ca-certificates which depends on
libressl. On middle up upgrading libressl, xbps-src runs into some
trouble. Let's just make libressl-devel depends on libressl instead.
the configure script was erasing the enviroment's compiler/cflags
setting, which resulted in broken builds with ccache enabled - this
is because with ccache we have a bunch of symlinks installed, one
of which is clang, and the configure script's autodetection first
checks for clang and then for gcc
however, there is no actual clang installed, and their check is
wrong, as it uses 'type' rather than 'command' and the former
will also succeed for broken symlinks (as it only checks the
existence of the path, regardless of if it's broken or not)
that said, even with ccache off, this would still build wrong,
since it would be ignoring the compiler flags on native builds,
and additionally the cross-compiling environment on cross builds
