-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
Unable to build when using GzipSwift #65
Comments
As a workaround, you can ping the version to anything below 6.1.0. |
Thanks @alessandrodn . Will you guys be making a new release soon? Just wondering if I should work around this or just wait for you guys to publish. |
will there be a release for this fix soon? thanks |
Could you please publish a new release with this fix? It's currently preventing me from building my project, which has dependencies that depend on GzipSwift. I can't pin a prior version without forking those dependencies. |
@DePasqualeOrg @BenTincher as @alessandrodn suggested, you can force SPM to use an earlier version. I'm doing the following to achieve this:
|
- later versions have compile issues: 1024jp/GzipSwift#65 fixes: #85
@DePasqualeOrg ah gotcha, yeah that is a problem. it sounds like you already tried this, but note that it's okay for the dependency to have different versions specified in your Package.swift vs your dependencies' Package.swift files, as long as they don't conflict. I had this problem with a different dependency ( In this case, Firebase had this version specifier:
I wanted to lock to a specific commit, so I had my package.swift specify the version as follows:
I think this ended up working fine since the Anyway, just sharing for posterity. Ultimately, GzipSwift does need to either unpublish 6.1.0 or release a fixed version. |
The problem is mostly Xcode, which didn't seem to want to download the version of the package I specified. I had to remove it and add it back again from my own fork of the dependency. Stuff like this wastes hours of people's time, while publishing a patch version takes just a minute. I know people are busy and open source work is mostly unpaid, but please don't leave broken packages out there like this, especially after the fix already exists. |
- later versions have compile issues: 1024jp/GzipSwift#65 fixes: #85
agreed, xcode and swift package manager are both pretty terrible. one thing in particular that's pretty gnarly: if you (or your dependencies) are pulling a dependency in via
Note that the
|
Is there any reason why |
Version 6.1.0 of the package can't be installed because of a typo in the file
[email protected]
.Doing a simple package update during the build invalidates the whole project with Xcode presenting the error
The PR #64 fixes the issue.
The text was updated successfully, but these errors were encountered: