From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: New package: flashfocus-2.0.3
Date: Sun, 15 Sep 2019 12:53:44 +0200 [thread overview]
Message-ID: <20190915105344.gcCOxTkH5Vr-2OM5punNH32jK-ZFvVpR6sP3Dg44Mk0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14426@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]
New comment by travankor on void-packages repository
https://github.com/void-linux/void-packages/pull/14426#issuecomment-531555278
Comment:
```
Looking for .cabal or package.yaml files to use to init the project.
Using cabal packages:
- ./
Selected resolver: lts-12.26
Initialising configuration using resolver: lts-12.26
Total number of user packages considered: 1
Overwriting existing configuration file: stack.yaml
All done.
WARNING: Ignoring Cabal's bounds on containers (>=0.4.2.1 && <0.6); using containers-0.6.0.1.
Reason: trusting snapshot over cabal file dependency information.
Error: While constructing the build plan, the following exceptions were encountered:
In the dependencies for language-python-0.5.6:
containers-0.6.0.1 from stack configuration does not match ==0.5.* (latest matching version
is 0.5.11.0)
needed since language-python is a build target.
Some different approaches to resolving this:
* Set 'allow-newer: true'
in /builddir/language-python-0.5.6/.stack/config.yaml to ignore all version constraints and build anyway.
* Recommended action: try adding the following to your extra-deps
in /builddir/language-python-0.5.6/stack.yaml:
- containers-0.5.11.0@sha256:28ad7337057442f75bc689315ab4ec7bdf5e6b2c39668f306672cecd82c02798,16685
```
https://www.stackage.org/package/containers/snapshots
```
0.6.0.1 LTS Haskell 13.1 (ghc-8.6.3)
0.6.0.1 Stackage Nightly 2018-12-31 (ghc-8.6.3)
0.5.11.0 LTS Haskell 12.26 (ghc-8.4.4)
```
next prev parent reply other threads:[~2019-09-15 10:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 22:21 [PR PATCH] " voidlinux-github
2019-09-12 22:31 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-12 22:31 ` voidlinux-github
2019-09-14 9:27 ` voidlinux-github
2019-09-14 9:27 ` voidlinux-github
2019-09-14 9:59 ` voidlinux-github
2019-09-14 12:14 ` voidlinux-github
2019-09-15 6:03 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-15 6:03 ` voidlinux-github
2019-09-15 9:33 ` voidlinux-github
2019-09-15 9:33 ` voidlinux-github
2019-09-15 10:02 ` voidlinux-github
2019-09-15 10:03 ` voidlinux-github
2019-09-15 10:05 ` voidlinux-github
2019-09-15 10:53 ` voidlinux-github [this message]
2019-09-15 10:53 ` [PR PATCH] [Closed]: " voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190915105344.gcCOxTkH5Vr-2OM5punNH32jK-ZFvVpR6sP3Dg44Mk0@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).