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

Yay doesn't handle moved repository for AUR/devel, needing user to clean cache manually #1483

Open
Porkepix opened this issue Mar 31, 2021 · 0 comments
Labels
Status: Confirmed Bug has been verified Type: Bug
Milestone

Comments

@Porkepix
Copy link

Porkepix commented Mar 31, 2021

Affected Version

yay v10.2.0 - libalpm v12.0.2

Describe the bug

For an AUR -git package, if the repository move, yay result in an error as it tries to update a local repository with wrong remotes:

==> ERROR: /home/clement/.cache/yay/libadwaita-git/libadwaita is not a clone of https://gitlab.gnome.org/GNOME/libadwaita

As visible here and here upstream moved, therefore remotes were now wrong. If editing local cache's repository would be considered as too dangerous, the command could at least offer to clean local repo in such a situation.

@Jguer Jguer added Status: Confirmed Bug has been verified and removed Status: Triage labels Apr 5, 2021
@Jguer Jguer added this to the yay v11.1 milestone Sep 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Confirmed Bug has been verified Type: Bug
Projects
None yet
Development

No branches or pull requests

2 participants