Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cargo vendor: failed to sync #25

Closed
fiersik opened this issue Sep 29, 2024 · 3 comments · Fixed by #40
Closed

cargo vendor: failed to sync #25

fiersik opened this issue Sep 29, 2024 · 3 comments · Fixed by #40
Assignees

Comments

@fiersik
Copy link
Contributor

fiersik commented Sep 29, 2024

How can I fix this error when using cargo vendor?

error: failed to sync

Caused by:
  found duplicate version of package `clipboard_wayland v0.2.2` vendored from two sources:

        source 1: registry `crates-io`
        source 2: https://github.com/pop-os/window_clipboard.git?tag=pop-dnd-6#8a816d8f

This is necessary to build without internet access during compilation, in my case, to build the package into the Sisyphus repository for ALT Linux

@MalpenZibo
Copy link
Owner

The problem is not easy to resolve see: rust-lang/cargo#10310

The project uses the iced.rs library and my fork of iced from pop_os that both use clipboard_wayland (one from crate and one from pop_os repo).

To resolve the issue I have to change the dependency from clipboard_wayland (pop_os repo version) to the crate one but to do that I had to change the codebase. Otherwise, I already planned an alternative solution #24.

Currently, I do not have a workaround.

@MalpenZibo
Copy link
Owner

MalpenZibo commented Oct 22, 2024

@fiersik Can you try with the latest commit on the main branch?
In case I will proceed with a new release

@MalpenZibo MalpenZibo self-assigned this Oct 22, 2024
@fiersik
Copy link
Contributor Author

fiersik commented Oct 23, 2024

I really managed to build an rpm package! I consider it fixed

@fiersik fiersik closed this as completed Oct 23, 2024
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 a pull request may close this issue.

2 participants