cc @aycanirican @unprolix @greydot
(no current issue tracker)
Building library for hdaemonize-0.5.6..
[1 of 1] Compiling System.Posix.Daemonize
/var/stackage/work/unpack-dir/unpacked/hdaemonize-0.5.6-a68167e6476ad268d01284686b1700451791a16aa31722433071fa5124b60686/Syst
em/Posix/Daemonize.hs:292:16: error: [GHC-83865]
• Couldn't match expected type: OpenFileFlags -> IO Fd
with actual type: IO Fd
• The function ‘openFd’ is applied to four value arguments,
but its type ‘FilePath -> OpenMode -> OpenFileFlags -> IO Fd’
has only three
In a stmt of a 'do' block:
null <- openFd "/dev/null" ReadWrite Nothing defaultFileFlags
In the expression:
do null <- openFd "/dev/null" ReadWrite Nothing defaultFileFlags
let sendTo fd' fd = closeFd fd >> dupTo fd' fd
mapM_ (sendTo null) [stdInput, stdOutput, ....]
|
292 | do null <- openFd "/dev/null" ReadWrite Nothing defaultFileFlags
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
/var/stackage/work/unpack-dir/unpacked/hdaemonize-0.5.6-a68167e6476ad268d01284686b1700451791a16aa31722433071fa5124b60686/Syst
em/Posix/Daemonize.hs:292:45: error: [GHC-83865]
• Couldn't match expected type ‘OpenFileFlags’
with actual type ‘Maybe a0’
• In the third argument of ‘openFd’, namely ‘Nothing’
In a stmt of a 'do' block:
null <- openFd "/dev/null" ReadWrite Nothing defaultFileFlags
In the expression:
do null <- openFd "/dev/null" ReadWrite Nothing defaultFileFlags
let sendTo fd' fd = closeFd fd >> dupTo fd' fd
mapM_ (sendTo null) [stdInput, stdOutput, ....]
|
292 | do null <- openFd "/dev/null" ReadWrite Nothing defaultFileFlags
| ^^^^^^^
Building library for frisby-0.2.4..
[1 of 2] Compiling Text.Parsers.Frisby
/var/stackage/work/unpack-dir/unpacked/frisby-0.2.4-43e9bed6cccab0e91ce17767f8eec02073d220bd78b58b9207cbaef096ccd36f/Text/Par
sers/Frisby.hs:253:11: error: [GHC-88464]
Variable not in scope: ap :: PM s (a -> b) -> PM s a -> PM s b
Suggested fix:
Perhaps use one of these:
data constructor ‘Ap’ (imported from Data.Monoid),
‘IntSet.map’ (imported from Data.IntSet),
‘map’ (imported from Prelude)
|
253 | (<*>) = ap
| ^^
/var/stackage/work/unpack-dir/unpacked/frisby-0.2.4-43e9bed6cccab0e91ce17767f8eec02073d220bd78b58b9207cbaef096ccd36f/Text/Par
sers/Frisby.hs:516:21: error: [GHC-88464]
Variable not in scope:
liftM :: (PE a2 -> PE a1) -> NM (PE a2) -> NM (PE a1)
Suggested fix:
Perhaps use one of these:
‘lift’ (imported from Control.Monad.State),
‘liftA’ (imported from Control.Applicative)
|
516 | f (PMap fn x) = liftM (PMap fn) (f x)
| ^^^^^
In the dependencies for tasty-hunit-0.10.0.3:
tasty dependency cycle detected: tasty, syb, doctest, prettyprinter-ansi-terminal,
optparse-applicative, tasty, tasty-bench, primitive, random, QuickCheck, BNFC
needed since tasty-hunit is a build target.
In the dependencies for syb-0.7.2.3:
tasty dependency cycle detected: tasty, syb, doctest, prettyprinter-ansi-terminal,
optparse-applicative, tasty, tasty-bench, primitive, random, QuickCheck, BNFC
needed since syb is a build target.
In the dependencies for tasty-hunit-0.10.0.3:
tasty dependency cycle detected: tasty, syb, doctest, prettyprinter-ansi-terminal,
optparse-applicative, tasty, tasty-bench, primitive, random, QuickCheck, BNFC
needed since tasty-hunit is a build target.
In the dependencies for syb-0.7.2.3:
tasty dependency cycle detected: tasty, syb, doctest, prettyprinter-ansi-terminal,
optparse-applicative, tasty, tasty-bench, primitive, random, QuickCheck, BNFC
needed since syb is a build target.
In the dependencies for tasty-bench-0.3.4: [14/144965]
tasty dependency cycle detected: tasty, tasty-bench, primitive, random, QuickCheck,
prettyprinter, optparse-applicative, tasty, STMonadTrans, Agda
needed since tasty-bench is a build target.
In the dependencies for tasty-hunit-0.10.0.3:
tasty dependency cycle detected: tasty, tasty-bench, primitive, random, QuickCheck,
prettyprinter, optparse-applicative, tasty, STMonadTrans, Agda
needed since tasty-hunit is a build target.
In the dependencies for tasty-quickcheck-0.10.2:
optparse-applicative dependency cycle detected: optparse-applicative, tasty-quickcheck,
pgp-wordlist, prettyprinter, optparse-applicative, tasty,
STMonadTrans, Agda
tasty dependency cycle detected: tasty, tasty-bench, primitive, random, QuickCheck,
prettyprinter, optparse-applicative, tasty, STMonadTrans, Agda
needed since tasty-quickcheck is a build target.
In the dependencies for pgp-wordlist-0.1.0.3:
tasty dependency cycle detected: tasty, tasty-bench, primitive, random, QuickCheck,
prettyprinter, optparse-applicative, tasty, STMonadTrans, Agda
needed since pgp-wordlist is a build target.
In the dependencies for prettyprinter-1.7.1:
tasty dependency cycle detected: tasty, tasty-bench, primitive, random, QuickCheck,
prettyprinter, optparse-applicative, tasty, STMonadTrans, Agda
needed since prettyprinter is a build target.
In the dependencies for syb-0.7.2.3:
tasty dependency cycle detected: tasty, tasty-bench, primitive, random, QuickCheck,
prettyprinter, optparse-applicative, tasty, STMonadTrans, Agda
needed since syb is a build target.
In the dependencies for text-short-0.1.5:
tasty dependency cycle detected: tasty, tasty-bench, primitive, random, QuickCheck,
prettyprinter, optparse-applicative, tasty, STMonadTrans, Agda
needed since text-short is a build target.
In the dependencies for time-compat-1.9.6.1:
tasty dependency cycle detected: tasty, tasty-bench, primitive, random, QuickCheck,
prettyprinter, optparse-applicative, tasty, STMonadTrans, Agda
needed since time-compat is a build target.
In the dependencies for vector-0.13.0.0:
tasty dependency cycle detected: tasty, tasty-bench, primitive, random, QuickCheck,
prettyprinter, optparse-applicative, tasty, STMonadTrans, Agda
needed since vector is a build target.
not sure it is enough though
ghc-heap-view, Win32 for mintty, cassava, and transformers-compat
More could probably be dropped but these stood out
cabal-install doesn't allow resolv-0.2 yet
Invalid flag specification:
* Package ansi-terminal does not define the following flags (specified in the project-level
configuration (e.g. stack.yaml)): win32-2-13-1.
Flags defined by package ansi-terminal are: example.
