bug#21829: guix import hackage failures

Federico Beffa skribis: > On Wed, Nov 25, 2015 at 10:45 PM, Ludovic Courtès wrote: >> Please add “Partly fixes .” or “Fixes >> .” in the commit logs as appropriate (see >> past commits for examples.) > > After committing I realized that I for

bug#21829: guix import hackage failures

On Wed, Nov 25, 2015 at 10:45 PM, Ludovic Courtès wrote: > Please add “Partly fixes .” or “Fixes > .” in the commit logs as appropriate (see > past commits for examples.) After committing I realized that I forgot about this. Sorry! Fede

bug#21829: guix import hackage failures

Federico Beffa skribis: > On Wed, Nov 25, 2015 at 10:45 PM, Ludovic Courtès wrote: >> Federico Beffa skribis: > > [...] > > + ;; indentation based block recognition. > + (begin (unread-char #\newline port) (read-char port) 0) Isn’t this equivalent to: 0 ? >>> >>> No.

bug#21829: guix import hackage failures

On Wed, Nov 25, 2015 at 10:45 PM, Ludovic Courtès wrote: > Federico Beffa skribis: [...] + ;; indentation based block recognition. + (begin (unread-char #\newline port) (read-char port) 0) >>> >>> Isn’t this equivalent to: 0 ? >> >> No. This is because at the start of a new

bug#21829: guix import hackage failures

Federico Beffa skribis: > On Sun, Nov 15, 2015 at 9:59 PM, Ludovic Courtès wrote: >> Federico Beffa skribis: >>> * guix/import/cabal.scm (lex-word): Add support for tests with no spaces. >>> (impl): Fix handling of operator "==". >> >> LGTM, but I think it’d be great to add a test that illust

bug#21829: guix import hackage failures

On Sun, Nov 15, 2015 at 9:59 PM, Ludovic Courtès wrote: > Federico Beffa skribis: >> * guix/import/cabal.scm (lex-word): Add support for tests with no spaces. >> (impl): Fix handling of operator "==". > > LGTM, but I think it’d be great to add a test that illustrates the case > that this fixes

bug#21829: guix import hackage failures

Federico Beffa skribis: > On Fri, Nov 13, 2015 at 10:19 PM, Ludovic Courtès wrote: >> Federico Beffa skribis: [...] >> In practice this discards LF even if it’s not following CR; that’s >> probably a good enough approximation, but an XXX comment would be >> welcome. > > This is intentional be

bug#21829: guix import hackage failures

On Fri, Nov 13, 2015 at 10:19 PM, Ludovic Courtès wrote: > Federico Beffa skribis: > >> --- >> (define (canonical-newline-port port) >> "Return an input port that wraps PORT such that all newlines consist >> of a single carriage retu

bug#21829: guix import hackage failures

Federico Beffa skribis: > --- > (define (canonical-newline-port port) > "Return an input port that wraps PORT such that all newlines consist > of a single carriage return." > (define (get-position) > (if (port-has-port-position

bug#21829: guix import hackage failures

On Thu, Nov 12, 2015 at 9:21 PM, Ludovic Courtès wrote: > If we go for the CRLF conversion port, we should avoid the pipe and > extra thread. Instead, I would suggest something like: > > (define (canonical-newline-port port) > "Return an input port that wraps PORT such that all newlines con

bug#21829: guix import hackage failures

Federico Beffa skribis: > On Thu, Nov 12, 2015 at 10:07 AM, Ludovic Courtès wrote: >> Federico Beffa skribis: >> I wonder if it wouldn’t be easier to change the lexer to recognize line >> feeds are white space or newlines, maybe along these lines: > > What you suggest is not enough. You have to

bug#21829: guix import hackage failures

On Thu, Nov 12, 2015 at 10:07 AM, Ludovic Courtès wrote: > Federico Beffa skribis: > I wonder if it wouldn’t be easier to change the lexer to recognize line > feeds are white space or newlines, maybe along these lines: What you suggest is not enough. You have to tweak a couple of other places as

bug#21829: guix import hackage failures

Federico Beffa skribis: > On Wed, Nov 11, 2015 at 12:18 PM, Ludovic Courtès wrote: >> Federico Beffa skribis: >> >>> * I do not get backtraces, but the following error: >> >> The backtrace thing was fixed in 5453de3d. >> >>> * The following packages fail because the file has DOS line endings: >

bug#21829: guix import hackage failures

On Wed, Nov 11, 2015 at 12:18 PM, Ludovic Courtès wrote: > Federico Beffa skribis: > >> * I do not get backtraces, but the following error: > > The backtrace thing was fixed in 5453de3d. > >> * The following packages fail because the file has DOS line endings: >> >> happy, base-compat, base-orp

bug#21829: guix import hackage failures

Federico Beffa skribis: > * I do not get backtraces, but the following error: The backtrace thing was fixed in 5453de3d. > * The following packages fail because the file has DOS line endings: > > happy, base-compat, base-orphans, fast-logger, generic-deriving, ObjectName, > SDL, setenv, spl

bug#21829: guix import hackage failures

Hi, I have checked the errors and have found the following: * I do not get backtraces, but the following error: -- $ ./pre-inst-env guix import hackage xmonad-contrib Starting download of /tmp/guix-file.yf7Cor >From http://hackage.haskell.org/package/xmonad-contrib/xm

bug#21829: guix import hackage failures

Paul van der Walt skribis: > 137: 4 [guix-import-hackage "xmonad-contrib"] > In ice-9/format.scm: > 1593: 3 [format # ...] > 766: 2 [format:format-work "~:[~*~;guix ~a: ~]~afailed to download cabal > file for package '~a'~%" ...] > 200: 1 [tilde-dispatch] > In unknown file: >?: 0 [scm-err

bug#21829: guix import hackage failures

Hello bug-guix, I have found that the command `guix import hackage foo` sometimes fails. I will try to provide a few examples. -8<-- $ guix import hackage xmonad-contrib Starting download of /tmp/guix-file.Bt94ZV >From http://ha