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

Always warning in Xcode with version 1.0.2 #290

Open
diuming opened this issue May 18, 2024 · 6 comments
Open

Always warning in Xcode with version 1.0.2 #290

diuming opened this issue May 18, 2024 · 6 comments

Comments

@diuming
Copy link

diuming commented May 18, 2024

skipping cache due to an error: https://github.com/apple/swift-numerics.git: The repository could not be found. Make sure a valid repository exists at the specified location and try again.

@paulsUsername
Copy link

How do I fix this?

@artemelianov
Copy link

@paulsUsername
Try adding https://github.com/apple/swift-numerics without the .git extension

@tonyarnold
Copy link

tonyarnold commented Oct 3, 2024

Yeah, I see this a lot in my projects, too. The problem is that it's not a warning, it's an error, so I can't update the packages for my own project while something within them relies on this project.

4ee9e68d57b958a8

@Iikeli
Copy link

Iikeli commented Nov 13, 2024

@tonyarnold not an ideal "solution", but I had the same issue, caused by using swift-algorithms. My solution was to comment out all the code using the package, commenting out the dependency from my Package.swift, updating all my packages, and finally undoing all the commenting out.

Luckily for me that was just ~50 lines of code that was fairly nicely isolated.

@tonyarnold
Copy link

Thanks for the suggestion, @Iikeli. Unfortunately in my project, Swift Numerics is an indirect dependency of something else, and that something else is used in too many places to comment them out.

I wonder if this is actually a SwiftPM issue, rather than something that this repository has done wrong?

@JHeisecke
Copy link

I have seen many posts about this issue on other packages.
All changes discussed here will be in your file ~/.gitconfig

Fix 1
Change forceSignAnnotated to false. Source
As Taras pointed out we're configuring Git so that it does not require GPG signatures for annotated tags on a global level for the user.
git config --global tag.forcesignannotated false

Fix 2
Apparently if you're using SourceTree, remove these lines. Source

[safe]
    bareRepository = explicit

or change it to:

[safe]
    bareRepository = *

Fallback
In my case, I still couldn't get it work, I realized I couldn't even push changes to my repo because I didn't have set the gpg.format

[gpg]
	program = gpg
	format = openpgp

If this wasn't your issue, just try to commit and push changes through the Terminal and fix the errors you see on it, with all previous changes done, it should be working by now.

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

No branches or pull requests

6 participants