This prevents pytest from collecting tests multiple times when
they are bundled in the wheel itself alongside the source tree.
Closes: #43946 [via git-merge-pr]
Also: do not compile bytecode in `do_install()` since it will be removed
in `post_install()`.
Co-authored-by: Gonzalo Tornaría <tornaria@cmat.edu.uy>
Co-authored-by: Andrew J. Hesford <ajh@sideband.org>
Closes: #44071.
The version packaged for Void Linux is extremely outdated.
Removing it will help moving from libbitcoin-secp256k1 to
bitcoin-core/secp256k1 for providing updated libsecp256k1.
The version packaged for Void Linux is extremely outdated.
Removing it will help moving from libbitcoin-secp256k1 to
bitcoin-core/secp256k1 for providing updated libsecp256k1.
The version packaged for Void Linux is extremely outdated.
Removing it will help moving from libbitcoin-secp256k1 to
bitcoin-core/secp256k1 for providing updated libsecp256k1.
The version packaged for Void Linux is extremely outdated.
Removing it will help moving from libbitcoin-secp256k1 to
bitcoin-core/secp256k1 for providing updated libsecp256k1.
The version packaged for Void Linux is extremely outdated.
Removing it will help moving from libbitcoin-secp256k1 to
bitcoin-core/secp256k1 for providing updated libsecp256k1.
The version packaged for Void Linux is extremely outdated.
Removing it will help moving from libbitcoin-secp256k1 to
bitcoin-core/secp256k1 for providing updated libsecp256k1.
The version packaged for Void Linux is extremely outdated.
Removing it will help moving from libbitcoin-secp256k1 to
bitcoin-core/secp256k1 for providing updated libsecp256k1.
The version packaged for Void Linux is extremely outdated.
Removing it will help moving from libbitcoin-secp256k1 to
bitcoin-core/secp256k1 for providing updated libsecp256k1.
The version packaged for Void Linux is extremely outdated.
Removing it will help moving from libbitcoin-secp256k1 to
bitcoin-core/secp256k1 for providing updated libsecp256k1.
The version packaged for Void Linux is extremely outdated.
Removing it will help moving from libbitcoin-secp256k1 to
bitcoin-core/secp256k1 for providing updated libsecp256k1.
Messages like "building [rust] for <platform>" could lead to mild panic as they
might be read as "building <large toolchain> on your laptop".
Simply adding "with" before the style/helpers should solve that.
It works for build_style, build_helper, both, and none.
=> ircdog-0.4.0_2: building with [go] for x86_64...
=> firefox-111.0.1_1: building with [rust] for x86_64...
=> riff-2.23.2_1: building with [cargo] [rust] for x86_64...
=> discord-0.0.26_1: building for x86_64...
Python packages built with pep517 system occasionally require
accessing distinfo files and/or entry points provided by the
package for tests to run. Since these assets are packed inside
the wheel generated in `do_build`, the target wheel is unpacked
in `do_check` first so that the said artifacts are accessible
during test runs.
The CI has `base-chroot` installed, but sometimes this script would try
to install `base-system,` causing conflicts. This commit fixes that
issue by using a brand-new rootdir.