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

No available version for github "LinusU/Marionette" satisfies the requirement: #1

Open
omgbbqhaxx opened this issue Dec 29, 2018 · 2 comments

Comments

@omgbbqhaxx
Copy link

Im creating Cartfile
add this : github "LinusU/Marionette" ~> 1.0.0
and write:
carthage update --platform iOS
But gives me an error :

No available version for github "LinusU/Marionette" satisfies the requirement:

@LinusU
Copy link
Owner

LinusU commented Jan 8, 2019

Marionette is currently in alpha, I didn't change the readme since it's a bit of a pain to update readme whenever I make new releases, should probably do that though...

In the meantime, you can use the currently latest version, 1.0.0-alpha.10, like so:

github "LinusU/Marionette" "1.0.0-alpha.10"

You can see all releases here: https://github.com/LinusU/Marionette/releases

@chromakey-io
Copy link

chromakey-io commented Apr 15, 2019

FYI. The same works with Swift.package.... just add the full alpha-xx.

You should probably modify your example on the readme, since swift package will fail in a similar way complaining about being unable to find anything between 1.00->2.0.0

I'm hoping this is better than alpha quality. The two others, are FAR ... FAR from calling themselves alpha. I just spent the day trying to follow the instructions to build Erik with Carthage (His swift.package file is there merely as a joke I think, it along with the dependencies' broken packaging meant I had to venture into the Cartfile world of doom. I'm more of a strictly swift CLI guy, and Xcode is a monster I have yet to conquer)... and failed spectacularly with the libraries not linking no matter how I whispered sweat nothings to them.

Then there's WKZombie, which looks great on the surface. It has a minor issue with the packaging system, he didn't seem to understand how to link the XML libs properly. That was an easy fix, but the fact his async code doesn't function was a pretty big deal breaker. All this stuff needs to be synchronous, and thus when the garbage sitting on top of the callbacks fails, it's just a total disaster.

Sorry for the off-topic rambling bs. I've just spent the day getting more and more frustrated and losing more and more time.

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

3 participants