Your message dated Wed, 27 Jun 2018 17:37:52 +0300 with message-id <[email protected]> and subject line Re: pandoc: FTBFS on armel/armhf: Identifier `InvalidYaml' used as a constructor-like thing has caused the Debian Bug report #899208, regarding pandoc: FTBFS on armel/armhf: Identifier `InvalidYaml' used as a constructor-like thing to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 899208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899208 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: pandoc Version: 2.2-1 Severity: serious pandoc fails to build on armel and armhf: [117 of 131] Compiling Text.Pandoc.Readers.Markdown ( src/Text/Pandoc/Readers/Markdown.hs, dist-ghc/build/Text/Pandoc/Readers/Markdown.o ) src/Text/Pandoc/Readers/Markdown.hs:275:20: error: * Identifier `InvalidYaml' used as a constructor-like thing * In the pattern: InvalidYaml (Just YamlParseException {yamlProblem = problem, yamlContext = _ctxt, yamlProblemMark = YamlMark {yamlLine = yline, yamlColumn = ycol}}) In a case alternative: InvalidYaml (Just YamlParseException {yamlProblem = problem, yamlContext = _ctxt, yamlProblemMark = YamlMark {yamlLine = yline, yamlColumn = ycol}}) -> logMessage $ CouldNotParseYamlMetadata problem (setSourceLine (setSourceColumn pos (sourceColumn pos + ycol)) (sourceLine pos + 1 + yline)) In a stmt of a 'do' block: case err' of InvalidYaml (Just YamlParseException {yamlProblem = problem, yamlContext = _ctxt, yamlProblemMark = YamlMark {yamlLine = yline, yamlColumn = ycol}}) -> logMessage $ CouldNotParseYamlMetadata problem (setSourceLine (setSourceColumn pos (sourceColumn pos + ycol)) (sourceLine pos + 1 + yline)) _ -> logMessage $ CouldNotParseYamlMetadata (show err') pos | 275 | InvalidYaml (Just YamlParseException{ | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^... Full logs at https://buildd.debian.org/status/package.php?p=pandoc&suite=sid Emilio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---Version: 2.2.1-1 Latest version builds on armel/armhf. Thanks, -- Ilias
--- End Message ---
