std: sync to dep versions of backtrace

[klensy]

Minor versions from backtrace desynced with std (they still differs in patch numbers, but still better):
https://github.com/rust-lang/backtrace-rs/blob/4d7906bb24ae91ee6587127020d360f5298f9e7e/Cargo.toml#L44-L48

There is hidden bug here, let's see if CI can find it.

cc @workingjubilee

r? @jhpratt

rustbot has assigned @jhpratt.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

These commits modify the library/Cargo.lock file. Unintentional changes to library/Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging.

cc @davidtwco, @wesleywiser

The job mingw-check-tidy failed! Check out the build log: (web) (plain)
Click to see the possible cause of the failure (guessed by this bot)

No, not this bug.

what bug are you hunting?

bootstrap and CI happily accept warnings from cargo: check mingw-check job log to find:

2025-01-03T13:09:09.0664097Z �[1m�[33mwarning�[0m�[1m:�[0m profile package spec `adler` in profile `release` did not match any packages
2025-01-03T13:09:09.0664972Z 
2025-01-03T13:09:09.0665149Z 	Did you mean `adler2`?

which refers to:

rust/library/Cargo.toml

Line 35 in 319f529

adler.debug = 0

where i didn't replaced adler with adler2.

ahh.

Wow,

2025-01-04T10:20:08.1162350Z �[1m�[33mwarning�[0m�[1m:�[0m rustc_llvm@0.0.0: Inherited flag "-fembed-bitcode=all" is not supported by the currently used CC

2025-01-04T11:42:20.2875925Z �[0m�[1m�[33mwarning�[0m�[0m�[1m: unexpected `cfg` condition name: `test`�[0m
2025-01-04T11:42:20.2876899Z �[0m  �[0m�[0m�[1m�[38;5;12m--> �[0m�[0mcompiler/rustc_macros/src/symbols.rs:35:7�[0m

from #135095 dist-x86_64-linux

CI really don't care about warnings.

...lol.

anyway, this seems fine to me.

@bors r+

📌 Commit 4d3a028 has been approved by workingjubilee

It is now in the queue for this repository.

The warning about adler is not so “secret” any more; I see it on the command-line every time bootstrap builds library.

It's annoying that this is allowed in CI, but we should also fix the thing that it's warning about.

EDIT: Warning will be fixed by #135110.

Oh, i actually forgot to push fix myself here, haha.