| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
With the removal of the hard `rustls` dependency and preferring
`futures-rustls`, then `paste` crate gets downgraded to a too-low of a version
so we should update it for our code to be able to compile correctly.
|
| |
|
|
| |
Fixes #1519
|
| |
|
|
|
| |
This is the version that introduces `root_hint_subjects()`,
which we want our ServerCertVerifier to override.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes the `minimal-versions` failure:
```
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?
[email protected]
```
(we don't actually need to un-downgrade `futures-lite` anymore)
But we *do* need to un-downgrade `event-listener`
(`async-global-executor` needs `event_listener::EventListener` to be `UnwindSafe`,
and in `event-listener 3.0.0`, they are not)
|
| | |
|
| |
|
|
|
|
| |
This has been obsolete for a very long time.
We have already published a version with a "won't be updated" warning.
|
| |
|
|
|
|
| |
This is necessary for async-global-executor, which uses
`futures_lite::future::or`, which futures-lite does not have before
1.4.0 or thereabouts.
|
| | |
|
| |
|
|
| |
This let me run it with my privsep setup.
|
| |
|
|
| |
We don't use "log" but some dependency of one of our examples does.
|
| |
|
|
|
|
|
| |
We don't actually use filetime directly, but notify wants it, and
notify accepts a version that doesn't actually appear to work.
This fixes minimal_versions CI.
|
| |
|
|
|
|
|
|
|
|
| |
This commit changes the shebang in all shell scripts from absolute
paths (such as `/bin/bash` or `/usr/bin/python3`) to the `/usr/bin/env`
binary with the accompanying interpreter as it's argument.
The reason for this are as follows:
- NixOS cannot work with absolute paths
- BSD systems install their packages in /usr/local/bin
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- arti#448 and arti!607 highlight an issue with upgrading `rsa`: namely,
the `x25519-dalek` version previously used has a hard dependency on
`zeroize` 1.3, which creates a dependency conflict.
- However, `x25519-dalek` version `2.0.0-pre.1` relaxes this dependency.
Reviewing the changelogs, it doesn't look like that version is
substantially different from the current one at all, so it should be
safe to use despite the "prerelease" tag.
- The new `x25519-dalek` version also bumps `rand_core`, which means we
don't have to use the RNG compat wrapper in `tor-llcrypto` as much.
closes arti#448
|
| | |
|
| |\
| |
| |
| |
| | |
Add a comment explaining what downgrade_dependencies is for.
See merge request tpo/core/arti!480
|
| | | |
|
| | |
| |
| |
| |
| | |
nix:0.4.2 is no longer a dependency
synstructure:0.12.0 is no longer required to build
|
| |/
|
|
| |
This is no longer necessary. :)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commitid is the current head of my MR branch
https://github.com/colin-kiegel/rust-derive-builder/pull/253
https://github.com/ijackson/rust-derive-builder/tree/field-builder
Using the commitid prevents surprises if that branch is updated.
We will require this newer version of derive_builder. The version
will need to be bumped again later, assuming the upstream MR is merged
and upstream do a release containing the needed changes.
We will need the new version of not only `derive_builder_core` (the
main macro implementation) but also`derive_builder` for a new error
type.
|
| |
|
|
|
|
|
|
|
| |
The new version of derive_builder requires a newer darling.
Ooops. Upstream MR here:
https://github.com/colin-kiegel/rust-derive-builder/pull/242
For now, upgrade darling. When there's a new upstream derive_builder,
we can use it and drop this.
|
| | |
|
| |
|
|
|
|
|
|
| |
The *earlier* versions of these crates pull in *dependencies* that
violate our MSRV policy by requiring a *later* version of Rust.
Empirically, env_logger 0.5.4 would be enough, but practice here seems
to be to just say "cargo update".
|
| | |
|
| | |
|
| | |
|
|
|
Previously this code was in .gitlab-ci.yml, but for the purposes of
testing my fix for #275, it turned out to be much better to have it
in a script of its own.
Also, we now need to update our "quote" second-order dependency,
since otherwise our minimal first-order dependencies won't build
correctly.
|