This fixes compilation errors like:
```
In file included from /nix/store/1p6r4w8943g0cklmsdmsm4pdvvldw8ja-lix-2.95.2-dev/include/lix/libutil/error-trace.hh:11,
from /nix/store/1p6r4w8943g0cklmsdmsm4pdvvldw8ja-lix-2.95.2-dev/include/lix/libutil/error.hh:18,
from /nix/store/1p6r4w8943g0cklmsdmsm4pdvvldw8ja-lix-2.95.2-dev/include/lix/libutil/async.hh:4,
from /nix/store/1p6r4w8943g0cklmsdmsm4pdvvldw8ja-lix-2.95.2-dev/include/lix/libutil/async-io.hh:4,
from /nix/store/1p6r4w8943g0cklmsdmsm4pdvvldw8ja-lix-2.95.2-dev/include/lix/libutil/archive.hh:4,
from /nix/store/1p6r4w8943g0cklmsdmsm4pdvvldw8ja-lix-2.95.2-dev/include/lix/libutil/hash.hh:6,
from /nix/store/1p6r4w8943g0cklmsdmsm4pdvvldw8ja-lix-2.95.2-dev/include/lix/libstore/realisation.hh:6,
from /nix/store/1p6r4w8943g0cklmsdmsm4pdvvldw8ja-lix-2.95.2-dev/include/lix/libstore/build-result.hh:4,
from ../src/plugin.cc:3:
/nix/store/1p6r4w8943g0cklmsdmsm4pdvvldw8ja-lix-2.95.2-dev/include/lix/libutil/fmt.hh:6:10: fatal error: boost/format.hpp: No such file or directory
6 | #include <boost/format.hpp>
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
```
curl 8.21.0 contains
2a2104f3cf
which breaks lix for some reason. Revert this single change just for lix
as a workaround
Signed-off-by: Sefa Eyeoglu <contact@scrumplex.net>
Oops, sorry. I dropped the patch in bb29bae6 as a mistake.
Change-Id: If3d7b6b0364e8b203a9c1156930d59b84b169705
Signed-off-by: Raito Bezarius <masterancpp@gmail.com>
Address an exploitable intger overflow leading to privilege escalation.
Read Lix release notes for more details.
Change-Id: I0d4ade161025189798b3ded82d33cd2de92d0ee8
Signed-off-by: Raito Bezarius <masterancpp@gmail.com>
Address an exploitable integer overflow leading to privilege escalation.
Read Lix release notes for more details.
Change-Id: I9fac168cdd775ab6e998200f5bb1e585aa5eced4
Signed-off-by: Raito Bezarius <masterancpp@gmail.com>
Lix 2.93 is removed because it has been deprecated. Lix 2.93.3 has a
known series of issues and 2.94 is superior along all dimensions to the
current knowledge.
Change-Id: Ie95b6ac3a25e67702c5618aecf39f86f2e1293ad
Signed-off-by: Raito Bezarius <masterancpp@gmail.com>
Set the build-test-env and build-test-shell Meson flags to ensure that
the BUILD_TEST_ENV and BUILD_TEST_SHELL environment variables are set,
as test_env_to_env depends on both of these variables [1].
[1]: 22b33b9d08
Lix 2.93/2.94 still reference [output.linkcheck] in book.toml,
but mdbook-linkcheck2 installs as binary 'mdbook-linkcheck2'
which mdbook cannot discover via [output.linkcheck]. Substituting
mdbook-linkcheck2 would not work due to this binary name mismatch.
Dropping it entirely for now seems safe, lix upstream commented it out
in 54df89f601b3. And the build still passes.
Due to an issue [1] in the Python splices uncovered by the setuptools-rust
cross compilation fix [2], some dependencies will otherwise fail to build.
Unfortunately this actually means losing the tests when the build platform
can execute host binaries (such as in `pkgsStatic`), but there's not a lot
one can do about this without fixing the Python splicing.
[1] https://github.com/NixOS/nixpkgs/issues/476822
[2] https://github.com/NixOS/nixpkgs/pull/467817
In ce375feadf, by accident the conditional
libsodium was introduced in addition to the previously existing unconditional
one, instead of replacing it. Correct this mistake now.
Apply patches to lix_2_93, lix_2_94, and git versions to support
building documentation with mdbook 0.5.
The patch is from upstream Lix commit 54df89f6, which maintains
compatibility with both mdbook 0.4.x and 0.5.x.
https://git.lix.systems/lix-project/lix/issues/1051