Backpack infdefinite error explain#11669
Merged
mergify[bot] merged 6 commits intoMay 25, 2026
Merged
Conversation
jappeace
force-pushed
the
backpack-infdefinite-error-explain
branch
2 times, most recently
from
9d64a70 to
6926b83
Compare
geekosaur
reviewed
Mar 27, 2026
geekosaur
approved these changes
Mar 27, 2026
jappeace
force-pushed
the
backpack-infdefinite-error-explain
branch
from
4864b7b to
1adc564
Compare
zlonast
reviewed
Apr 24, 2026
zlonast
approved these changes
May 20, 2026
Collaborator
zlonast
left a comment
zlonast
left a comment
There was a problem hiding this comment.
I think we still need to fix the backup's behavior until it's fully mature. Please continue fixing it so we can write more examples of how to use it :)
Collaborator
Author
|
@zlonast for now I stopped investigating backpack, but I'll probably get back to this in the future because I think it's such a cool system, I'm swamped with client work right now 😆 |
mergify
Bot
added
ready and waiting
Contributor
Merge Queue Status
This pull request spent 1 hour 16 minutes 12 seconds in the queue, including 1 hour 5 minutes 31 seconds running CI. Waiting for any of
All conditions
ReasonThe merge conditions cannot be satisfied due to failing checks Failing checks: HintYou may have to fix your CI before adding the pull request to the queue again. |
86 tasks
Collaborator
|
Hi @jappeace, can you squash the commits and rebase? |
Collaborator
|
Squashing can be done automatically on merge, you just need to use another label: squash+merge instead of merge me. Rebased can be done either via the bot (a bit flaky) or with GitHub UI (pretty reliable). In sum, you shouldn't need PR author''s help with these actions @zlonast |
zlonast
added
squash+merge me
```
Error:
The following packages are broken because other packages they depend on are missing. These broken packages must be rebuilt before they can be used.
planned package consumer-0.1.0.0 is broken due to missing package
framework-0.1.0.0+95RTb42ZWxa9J13cUStM0q
````
To
```
Error:
The following packages are broken because other packages they depend on are missing. These broken packages must be rebuilt before they can be used.
planned package consumer-0.1.0.0
is broken due to missing package
framework-0.1.0.0 (has unfilled signature: App)
The package is installed as indefinite.
To use it, rebuild it in the same cabal project as the consumer so cabal can fill the signatures.
```
Hopefully it gives more guidence on what's going on to the user. I encountered this when trying to use backpack in a nix setup (for example jappeace-sloth/prrrrrrrrr#2) It keeps on wanting to build everything locally and I couldn't understand why. I still don't fully understand why it can't have partially filled modules upstream. It claims it's because of nix but I don't understand it.
Add missing expected output file for cabal variant of Backpack Fail5 test The setupAndCabalTest function runs the test twice: once with setup and once with cabal. The setup variant uses setup-external-fail.out, but the cabal variant needs setup-external-fail.cabal.out which was missing, causing the test to expect empty output and fail.
This reverts commit 7160910.
zlonast
force-pushed
the
backpack-infdefinite-error-explain
branch
from
eebc462 to
f2a7ebb
Compare
Contributor
Merge Queue Status
This pull request spent 1 hour 55 minutes 1 second in the queue, including 1 hour 43 minutes 11 seconds running CI. Required conditions to merge
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes the error message from:
To
Hopefully it gives more guidence on what's going on to the user. I encountered this when trying to use backpack in a nix setup (for example jappeace-sloth/prrrrrrrrr#2) It keeps on wanting to build everything locally and I couldn't understand why.
I still don't fully understand why it can't have partially filled modules upstream. It claims it's because of nix but I don't understand it.It's not nix, I'm in a deep cabal hole, but it looks like I'm finding a way out of it (slowly). This is the final backpack PR for now, I'll investigate it more another time. Frankly I want (good) mobile support more then I want to work with backpack.
significance: significantin the changelog file.