Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 1, 2023

This PR contains the following updates:

Package Type Update Change
aes dependencies minor 0.7.4 -> 0.8.0

Release Notes

RustCrypto/block-ciphers (aes)

v0.8.4

Compare Source

v0.8.3

Compare Source

v0.8.2

Compare Source

v0.8.1

Compare Source

v0.8.0

Compare Source

v0.7.5

Compare Source


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@iceiix
Copy link
Owner

iceiix commented Jan 1, 2023

Incompatible API change:

error[E0277]: the trait bound `Aes128: cfb8::cipher::BlockEncrypt` is not satisfied
    --> protocol/src/protocol/mod.rs:1057:20
     |
1057 |     cipher: Option<Aes128Cfb>,
     |                    ^^^^^^^^^ the trait `cfb8::cipher::BlockEncrypt` is not implemented for `Aes128`
     |
     = help: the trait `cfb8::cipher::BlockEncrypt` is implemented for `&Alg`
note: required by a bound in `Cfb8`
    --> .cargo/registry/src/github.com-1ecc6299db9ec823/cfb8-0.7.1/src/lib.rs:61:34
     |
61   | pub struct Cfb8<C: BlockCipher + BlockEncrypt> {
     |                                  ^^^^^^^^^^^^ required by this bound in `Cfb8`

@renovate renovate bot force-pushed the renovate/aes-0.x branch 2 times, most recently from 80c49b8 to da35793 Compare March 16, 2023 13:49
@renovate renovate bot changed the title Update Rust crate aes to 0.8.2 Update Rust crate aes to 0.8.3 Jun 18, 2023
@renovate renovate bot force-pushed the renovate/aes-0.x branch from da35793 to 9e7f8db Compare June 18, 2023 17:26
@renovate renovate bot force-pushed the renovate/aes-0.x branch from 9e7f8db to a934be8 Compare February 14, 2024 05:39
@renovate renovate bot changed the title Update Rust crate aes to 0.8.3 Update Rust crate aes to 0.8.4 Feb 14, 2024
@renovate renovate bot force-pushed the renovate/aes-0.x branch from a934be8 to 2376daa Compare May 5, 2024 08:57
@renovate renovate bot changed the title Update Rust crate aes to 0.8.4 Update Rust crate aes to 0.8.0 May 5, 2024
@renovate renovate bot force-pushed the renovate/aes-0.x branch from 2376daa to 4cd8a6e Compare August 12, 2025 00:08
@renovate renovate bot force-pushed the renovate/aes-0.x branch from 4cd8a6e to 9622070 Compare September 27, 2025 02:56
Copy link
Contributor Author

renovate bot commented Sep 27, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: protocol/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path protocol/Cargo.toml --package [email protected] --precise 0.8.4
warning: `/tmp/renovate/repos/github/iceiix/stevenarella/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant