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

Swift Package Manager and tagging issue? #364

Closed
klaas opened this issue Jun 3, 2018 · 2 comments
Closed

Swift Package Manager and tagging issue? #364

klaas opened this issue Jun 3, 2018 · 2 comments
Labels

Comments

@klaas
Copy link

klaas commented Jun 3, 2018

What did you do?

Tried to use the latest version of GRDB with Swift Package Manager and this simple Package.swift file:

// swift-tools-version:4.0
import PackageDescription

let package = Package(
    name: "MyTarget",
    dependencies: [
        .package(url: "https://github.com/klaas/GRDB.swift.git", from: "2.10.0")
    ],
    targets: [
        .target( name: "MyTarget", dependencies: []),
    ]
)

What did you expect to happen?

No error message on swift build.

What happened instead?

Command line output of swift build:

Fetching https://github.com/groue/GRDB.swift.git
error: dependency graph is unresolvable; found these conflicting requirements:

Dependencies: 
    https://github.com/klaas/GRDB.swift.git @ 2.10.0..<3.0.0

Environment

Xcode version: Latest = Version 9.4 (9F1027a)
Swift version: Latest = Apple Swift version 4.1.2 (swiftlang-902.0.54 clang-902.0.39.2)
macOS version running Xcode: Latest 10.13.4 (17E202)

Demo Project

I created a fork and added a branch "taggingtest" with a tag "2.11.0" here: https://github.com/klaas/GRDB.swift

When I use this a a dependency everything works.

I found #72 where it is discussed whether it's possible to use the "v" as a prefix in the tags. Maybe this is the reason for my error?

I'm using GRDB for a long time now and the issues appeared just today.

@groue groue added the bug label Jun 4, 2018
@groue
Copy link
Owner

groue commented Jun 4, 2018

Hello @klaas!

Thanks for reporting this issue. Yes there was a tagging problem. I was wondering why the #313 SPM tests were failing... You showed me the light!

It should be fixed now. You may have to run the following commands on your local copies:

# Delete extra tags locally
git tag -d 3.0.0-beta2
git tag -d v3.0.0-beta2
# Delete extra tags on the `origin` remote
git push origin :refs/tags/3.0.0-beta2
git push origin :refs/tags/v3.0.0-beta2

@klaas
Copy link
Author

klaas commented Jun 4, 2018

Thanks for the very fast response as usual! and you're welcome :)

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

2 participants