lukaslueg

FWIW, I think applying patches is beyond Cargo's rational. Besides the intricacies of successfully applying patches (see the wilderness of `git apply`), at the end of the day Cargo itself...

AFAICS there is currently no reliable way to do this; it's is a long-standing issue with rustc, tracked among others in https://github.com/rust-lang/rust/issues/44036. Also see https://github.com/rust-lang/cargo/issues/7828

This is (as I now realize) undocumented, but expected behavior: https://github.com/lukaslueg/built/blob/c7b082bf092c51a6cae7b9ee5da5eff896551936/src/lib.rs#L421-L429 `libgit2`, which is used to retrieve git-information is unable to query repositories that are based on shallow clones. This...

Probably because the other repo has a shorter commit history and its root is within the commit-depth that GitLab's CI will check out. You may be able to tell GitLab's...

Then I don't know.

Thanks for the PR! I think there is a problem here because the current code maps any kind of error and replaces the message with one that specifically refers to...

As far as I can see this is expected behavior, as `verdigris` is a library. Only top-level crates (read: executables) get a lockfile of their own. That is, when `verdigris`...

Excuse my ignorance: Is `target-cpu` the more specific form of [`target_arch`](https://docs.rs/built/0.3.2/built/struct.Options.html#method.set_cfg), which gives you one of [these](https://docs.rs/platforms/0.2.1/platforms/target/enum.Arch.html) ?

My natural inclination is to avoid having to parse RUSTFLAGS for obvious reasons, at least if this is the only solution. Maybe open an issue with Cargo, so `target-cpu` and...

This depends on https://github.com/rust-lang/rust/issues/44036