* Joachim Breitner <nomeata@debian.org> [2015-04-20 12:47:39+0200] > Am Montag, den 20.04.2015, 10:14 +0300 schrieb Dmitry Bogatov: > > > > About package-plan. I am actually have problems with it. > > > > [...] > > > > 1. complains loudly and a lot about: > > > > > > > > E: read, still have 733 to read but none left > > > > grep-aptavail: apt-cache dumpavail:2: expected a colon. > > > > > > Weird, never seen that. Looks like a problem with apt. Did you run > > > apt-get update? Do you have apt-src lines in your sources.list? > > > > Yes, you was right. I missed src repositories, but even with them > > I receive > > > > grep-dctrl: -:1: expected a colon. > > Weird, never seen that. Can you try the commands > $ apt-cache -t experimental dumpavail | grep-dctrl -F GHC-Package . -s GHC-Package -n > and > $ apt-cache -t experimental dumpavail | grep-dctrl -F Package -s Version -n -X happy > and see if that shows the problem? If so, you can debug it from there. Both have same output: grep-dctrl: -:2: expected a colon. E: read, still have 733 to read but none left > > Okay, than what branch should I use? I tried ghc-7.8, it > > outputs less errors, but still seems I do it wrong: > > > > Cabal install failed: > > cabal: Could not resolve dependencies: > > next goal: cabal-debian (user goal) > > 31 error(s) in total. > > [...] > Looks like you have libghc-cabal-dev installed. Try running it without > any lib-foo-dev packages installed – since you run it in docker anyways, > that should be possible. > > Ah, but I see a problem: cabal-install now depends on libghc-cabal-dev. > Hmpf. It worked for me as I had cabal-install 0.20 installed > > I’ll see if I can find Daniel’s (not Sven’s) mail about telling cabal to > use an empty package database.... > > Indeed, that works quite nicely! Looks like it is no longer needed to > run it in a clean environment. It still requires the "right" version of > ghc, though. Can you pull (branch ghc-7.8) and see if it works for you > now? No, it does not. Both in by main env (ghc-haddock installed) and docker (only ghc and cabal-install) it complains about haddock. Here is snippet from clean environment. Cabal install failed: cabal: Could not resolve dependencies: next goal: haddock (user goal) rejecting: haddock-2.16.0, 2.15.0.2, 2.15.0.1, 2.15.0, 2.14.3, 2.14.2, 2.14.1, 2.13.2.1, 2.13.2, 2.13.1, 2.13.0, 2.12.0, 2.11.1, 2.11.0, 2.10.0, 2.9.4, 2.9.3, 2.9.2, 2.9.1, 2.9.0, 2.8.1, 2.8.0, 2.7.2, 2.7.1, 2.7.0, 2.6.1, 2.6.0, 2.5.0, 2.4.2, 2.4.1, 2.4.0, 2.2.2, 2.2.1, 2.2.0, 2.1.0, 2.0.0.0, 0.9, 0.8 (global constraint requires (==2.14.3.1)) Dependency tree exhaustively searched. 31 error(s) in total. root@a25e2856d37c:~/package-plan# aptitude search haddock p ghc-haddock - Documentation tool for annotated Haskell source code Just in case, commit 4e42b58d6c203d5b620dedac0dbf65c36f30b6c2 > > Also, just a thought. Would not it be great to make a native debian > > package out of all out tools and scripts? It is annoying to discover > > by-hand that I need another perl library. > > Good idea! Feel free to create such a package for the test-packages.pl > script. Although we need a better name for it then. Possibly > haskell-package-plan. Okay. I will start at it when I finally make test-packages.pl work for me. -- Best regards, Dmitry Bogatov <KAction@gnu.org>, Free Software supporter, esperantisto and netiquette guardian. GPG: 54B7F00D
Attachment:
pgpqsNY1KobPV.pgp
Description: PGP signature