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

The version 0.11 is not recognized with SPM. #75

Closed
mitsuse opened this issue Sep 22, 2016 · 7 comments
Closed

The version 0.11 is not recognized with SPM. #75

mitsuse opened this issue Sep 22, 2016 · 7 comments
Labels

Comments

@mitsuse
Copy link

mitsuse commented Sep 22, 2016

The version string of patch seems to be required in the current implementation of SPM. I executed swift package update with this manifest file and got the output as follow:

Cloning https://github.com/Carthage/Commandant.git
error: The dependency graph could not be satisfied. The package (https://github.com/Carthage/Commandant.git) with version tag in range (0.11.0..<0.11.9223372036854775807) is not found. Found tags ([0.1.1, 0.6.1, 0.7.0-beta.1, 0.7.0, 0.8.1, 0.8.2, 0.8.3, 0.9.0, 0.10.0, 0.10.1])

They are related source codes to this issue:

@ikesyo
Copy link
Member

ikesyo commented Sep 22, 2016

Looks like 0.11 is not listed in the found tags messeage:

Found tags ([0.1.1, 0.6.1, 0.7.0-beta.1, 0.7.0, 0.8.1, 0.8.2, 0.8.3, 0.9.0, 0.10.0, 0.10.1])

You might have to run swift package fetch or swift package update.

@mitsuse
Copy link
Author

mitsuse commented Sep 22, 2016

Thanks for a quick reply. I tried also swift package fetch but got a same message as before.

@ikesyo
Copy link
Member

ikesyo commented Sep 22, 2016

That's really annoying...... 😫

@ikesyo
Copy link
Member

ikesyo commented Sep 22, 2016

Okay, we should consistently use x.y.z style tag to meet Semantic Versioning spec: http://semver.org/#spec-item-2

A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes. X is the major version, Y is the minor version, and Z is the patch version. Each element MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0.

@mdiep I'm going to cut 0.11.1 release to just fix the versioning issue.

@ikesyo ikesyo closed this as completed in 4e056dd Sep 22, 2016
@mitsuse
Copy link
Author

mitsuse commented Sep 22, 2016

Thanks!

@ikesyo
Copy link
Member

ikesyo commented Sep 22, 2016

@mitsuse Thank you! This should be fixed with 0.11.1.

@mdiep
Copy link
Member

mdiep commented Sep 22, 2016

Thanks @ikesyo!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants