Compilation fails on ubuntu & debian, handlebars 5.1.1 has been yanked #1840

New Issue

Closed

opened 2025-11-07 07:22:06 -06:00 by GiteaMirror · 1 comment

GiteaMirror commented 2025-11-07 07:22:06 -06:00

Owner

Copy Link

Originally created by @dionysius on GitHub (Feb 2, 2024).

Subject of the issue

  failed to select a version for the requirement `handlebars = "^5.1.1"`
  candidate versions found which didn't match: 5.1.0, 5.0.0, 5.0.0-beta.5, ...

https://docs.rs/handlebars/latest/handlebars/index.html does say for 5.1.1: This release has been yanked, go to latest version. I build debian packages for ubuntu and debian stable. 1.30.2 was fine but ran into this today.

Troubleshooting data

https://github.com/dionysius/vaultwarden-deb/actions/runs/7756133150

  Installing vaultwarden v1.0.0 (/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3)
    Updating crates.io index
error: failed to compile `vaultwarden v1.0.0 (/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3)`, intermediate artifacts can be found at `/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3/target`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

Caused by:
  failed to select a version for the requirement `handlebars = "^5.1.1"`
  candidate versions found which didn't match: 5.1.0, 5.0.0, 5.0.0-beta.5, ...
  location searched: crates.io index
  required by package `vaultwarden v1.0.0 (/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3)`
  if you are looking for the prerelease package it needs to be specified explicitly
      handlebars = { version = "5.0.0-beta.5" }
  perhaps a crate was updated and forgotten to be re-vendored?

Originally created by @dionysius on GitHub (Feb 2, 2024). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue ``` failed to select a version for the requirement `handlebars = "^5.1.1"` candidate versions found which didn't match: 5.1.0, 5.0.0, 5.0.0-beta.5, ... ``` https://docs.rs/handlebars/latest/handlebars/index.html does say for 5.1.1: **This release has been yanked, go to latest version**. I build debian packages for ubuntu and debian stable. 1.30.2 was fine but ran into this today. ### Troubleshooting data https://github.com/dionysius/vaultwarden-deb/actions/runs/7756133150 ``` Installing vaultwarden v1.0.0 (/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3) Updating crates.io index error: failed to compile `vaultwarden v1.0.0 (/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3)`, intermediate artifacts can be found at `/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3/target`. To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path. Caused by: failed to select a version for the requirement `handlebars = "^5.1.1"` candidate versions found which didn't match: 5.1.0, 5.0.0, 5.0.0-beta.5, ... location searched: crates.io index required by package `vaultwarden v1.0.0 (/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3)` if you are looking for the prerelease package it needs to be specified explicitly handlebars = { version = "5.0.0-beta.5" } perhaps a crate was updated and forgotten to be re-vendored? ```

GiteaMirror added the bug label 2025-11-07 07:22:06 -06:00

GiteaMirror closed this issue 2025-11-07 07:22:07 -06:00

GiteaMirror commented 2025-11-07 07:22:08 -06:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Feb 2, 2024):

Thanks. That is unfortunate.
Working on a fix now.

@BlackDex commented on GitHub (Feb 2, 2024): Thanks. That is unfortunate. Working on a fix now.

GiteaMirror referenced this issue 2025-11-07 07:57:02 -06:00

[PR #1869] [MERGED] Fix WebAuthn issues and some small updates #2882

GiteaMirror referenced this issue 2026-03-07 21:02:37 -06:00

[PR #1869] [MERGED] Fix WebAuthn issues and some small updates #6659

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

cached-config-operations

test_dylint

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

better for forum

bug

documentation

duplicate

enhancement

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

SSO

Third party

troubleshooting

wontfix

No Label bug

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

GiteaMirror ninjasurge

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#1840