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

Update deps causing failed build + outdated telegram-bot-api #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

artimath
Copy link

In the process of solving fizruk/telegram-bot-simple#188, I fixed a few things to get it to build again and figured I'd PR.

The original extra-deps in stack.yaml:

extra-deps:
  - git: https://github.com/fizruk/telegram-bot-simple.git
    commit: v0.2

led to:

> stack build

Error: [S-112]
       Cannot complete repo information for a non SHA1 commit due to non-reproducibility:
       Git repo at https://github.com/fizruk/telegram-bot-simple.git, commit v0.2.

After some googling, saw this commercialhaskell/stack#4882, which hinted that the issue was with not having a full hash for the commit.

I updated to:

extra-deps:
  - git: https://github.com/fizruk/telegram-bot-simple.git
    commit: 'f7acd0a9feb7fd9beb0ec621a2fe271f6721d51c'
    subdirs:
      - telegram-bot-simple

Which worked, but then led to this:

In the dependencies for telegram-bot-simple-0.14.1:
         * telegram-bot-api must match >=7.3.1, but telegram-bot-api-6.7.1 is in the Stack configuration
           (latest matching version is 7.4).
       The above is/are needed due to demo-bot-0.1.0 -> telegram-bot-simple-0.14.1

Also GHC 8.4.3 didn't even have a build for Mac 14.5.

Added new resolver:

resolver: nightly-2024-08-25

Everything works, also addresses the version bump needed to fix fizruk/telegram-bot-simple#188

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

Successfully merging this pull request may close these issues.

ExceptionInLinkedThread: Missing field in record construction sendMessageMessageEffectId
1 participant