mirrors/arti.git/maint, branch arti-v1.2.7mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.72024-09-03T08:09:02ZFix typos2024-09-03T08:09:02ZDimitris Apostoloudimitris.apostolou@icloud.com2024-09-03T08:09:02Zurn:sha1:676f913463b7d84f34dd6101b99d03ef79cf57adMerge branch 'ahf/macos-cross-build' into 'main'2024-09-02T10:24:05ZAlexander Hansen Færøyahf@torproject.org2024-09-02T10:24:05Zurn:sha1:3cae65b1bab166e7bdcd0f1d69e297ed0034587f
Fix reproducible build CI job for macOS
Closes #1394 and #1507
See merge request tpo/core/arti!2377Explicitly specify the deployment target of macOS to 10.7.2024-09-01T21:09:36ZAlexander Færøyahf@0x90.dk2024-09-01T21:09:36Zurn:sha1:e111fc0ba22bd609e0d41d700555bb9bacd561c1
osxcross tries in various ways to detect which version of the compiler
we have, which version of the OS, which C++ standard library we use, and
many other things. With this variable set, osxcross seems able to detect
the environment provided by the SDK that we use.
The error messages from osxcross is as follows:
osxcross: error: cannot find libc++ headers
osxcross: error: while detecting target
This origins from its internal target detection code in target.cpp of
osxcross. This file contains a signficant amount of the detection for
paths of different versions of the macOS SDK's and macOS versions. All
of this is truly cursed.
In osxcross's main.cpp, the variable is read in:
if (char *p = getenv("MACOSX_DEPLOYMENT_TARGET")) {
target.OSNum = parseOSVersion(p);
unsetenv("MACOSX_DEPLOYMENT_TARGET");
}
and setting it thus forces the OS version to be parsed from the variable
instead of its (in our case failed) attempt at detecting the version
itself.
Fixes: tpo/core/arti#1394
check_toposort: Explain why we also check dev-dependencies2024-08-27T14:49:20ZJim Newsomejnewsome@torproject.org2024-08-22T14:37:45Zurn:sha1:5a3fafebac60c9ea18fc123e160f26221ad4a518Add comments explaining purpose of check_toposort2024-08-27T14:49:20ZJim Newsomejnewsome@torproject.org2024-08-22T14:30:28Zurn:sha1:48e45f095ec014616a67990c3e7d453bce99a173Merge branch 'ci' into 'main'2024-08-27T11:21:42ZIan Jacksoniwj@torproject.org2024-08-27T11:21:42Zurn:sha1:c030cb301698ebfb001f618ab7b40ee0834b980d
Run tests of every crate, with all features disabled
See merge request tpo/core/arti!2350Exclude debian/* from the forbid-absolute-shebangs checks2024-08-27T09:40:55ZNoisyCoilnoisycoil@tutanota.com2024-08-16T17:20:37Zurn:sha1:7ed29c071d27eb8272e386706978778e7bb807beAdd script for *testing* without any features enabled2024-08-19T17:00:48ZIan Jacksonijackson@chiark.greenend.org.uk2024-08-19T15:00:04Zurn:sha1:7a9bf49870533cc052b12680336f067f77d87b34
We can't do this for every crate.
I looked at what is now matrix-check to see if I wanted to use any of
the code. But it seems too entangled with its particular purpose, and
has a lot of embedded knowledge of our crates' features. I found it
sufficiently far from what I wanted that I decided on a fresh script.
Rename matrix-check from matrix_test2024-08-19T17:00:48ZIan Jacksonijackson@chiark.greenend.org.uk2024-08-19T14:58:15Zurn:sha1:92b95f404cbebda8c77b56b81b7323c723d17044
There's a TODO asking for `check` to be changed to `test`. And we're
about to invent a thing that does, sort of, the `test`.
maint: Remove exceptions for generational-arena2024-08-14T16:33:06ZNick Mathewsonnickm@torproject.org2024-08-14T16:33:06Zurn:sha1:1b7c77124f3c70895e390a5a926b2140b98a62eb
Now that it's gone, we no longer need to bless its MPL-2.0 usage
or excuse it from cargo-audit.