lower pvp-bounds: extraneous version range for a dependency on an internal library #3290
Comments
I just hit the same error uploading stack-1.5.0 with |
I'm not sure if this is related, but |
There's probably much better solutions, but something like filtering out the package from adding bounds master...mfine:mfine/filter-internal-dependencies |
This is a workaround for the problem described in: commercialhaskell/stack#3290
This is a workaround for the problem described in: commercialhaskell/stack#3290
Lookin at #3413's "user story": it seems the bug was hard to debug because That's in addition to fixing this specific |
When the |
I also can't upload to Hackage with any option for
I have benchmarks in package which depend on library itself. |
@chshersh Ah, thanks for the more minimal repro. I think I've resolved this, but can't test the hackage upload. I've pushed a fix to master, can you please test after running |
@mgsloan Thanks for your work! Sorry for long answer... I tested after I'm testing on this Stack version $ stack --version
Version 1.5.1, Git revision 600c1f01435a10d127938709556c1682ecfd694e (4861 commits) x86_64 hpack-0.17.1 Observed error $ stack sdist --pvp-bounds upper
$ stack upload --pvp-bounds upper .
Getting file list for /home/fenx/programming/haskell/serokell/universum/
Building sdist tarball for /home/fenx/programming/haskell/serokell/universum/
Checking package 'universum' for common mistakes
Uploading universum-0.7.1.1.tar.gz... unhandled status code: 400
Error: Invalid package
The package has an extraneous version range for a dependency on an internal library: universum <0.8. This version range includes the current package but isn't needed as the current package's library will always be used.
Upload failed on universum-0.7.1.1.tar.gz |
@chshersh Hmm, did May be helpful to do |
@mgsloan Sorry, false alarm! Yes, I did |
Awesome! |
@mgsloan using
|
General summary/comments
Publishing with
pvp-bounds: lower
has stopped working with no change in tooling. Hackage is now returning an "extraneous version range" on an internal library error and failing the upload with 400 "Invalid package" - previously this hadn't been the case.I see this check in cabal - potentially this is from updated software on hackage?
Steps to reproduce
Publish a package to hackage containing an executable with an unbounded dependency on the package's library with a stack.yaml containing
pvp-bounds: lower
.Expected
The publish has in the past passed without issues. In hackage I see that the unbounded dependency on the package's library has a lower bound in wolf-0.3.23.cabal, like:
Actual
Now the publish fails with:
I am able to get the publish to pass by manually removing the bounds on the internal library in wolf-0.3.24.cabal, like:
Stack version
Also tried with 1.5.0:
Method of installation
The text was updated successfully, but these errors were encountered: