Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package pandoc for openSUSE:Factory checked 
in at 2021-06-01 10:39:13
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/pandoc (Old)
 and      /work/SRC/openSUSE:Factory/.pandoc.new.1898 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "pandoc"

Tue Jun  1 10:39:13 2021 rev:57 rq:896224 version:2.14

Changes:
--------
--- /work/SRC/openSUSE:Factory/pandoc/pandoc.changes    2021-03-28 
11:58:37.548344204 +0200
+++ /work/SRC/openSUSE:Factory/.pandoc.new.1898/pandoc.changes  2021-06-01 
10:40:50.937159053 +0200
@@ -1,0 +2,421 @@
+Sun May 30 17:37:12 UTC 2021 - [email protected]
+
+- Update pandoc to version 2.14.
+  ## pandoc 2.14 (2021-05-28)
+
+    * Change reader types, allowing better tracking of source positions
+      [API change].  Previously, when multiple file arguments were provided,
+      pandoc simply concatenated them and passed the contents to the readers,
+      which took a Text argument.  As a result, the readers had no way of 
knowing
+      which file was the source of any particular bit of text.  This meant that
+      we couldn't report accurate source positions on errors or include 
accurate
+      source positions as attributes in the AST.  More seriously, it meant that
+      we couldn't resolve resource paths relative to the files containing them
+      (see e.g. #5501, #6632, #6384, #3752).
+
+    * Add `rebase_relative_paths` extension (#3752).  When enabled, this
+      extension rewrites relative image and link paths by prepending
+      the (relative) directory of the containing file.  This
+      behavior is useful when your input sources are split
+      into multiple files, across several directories, with files
+      referring to images stored in the same directory.  The
+      extension can be enabled for all markdown and commonmark-based formats.
+
+    * Add Text.Pandoc.Sources (exported module), with a `Sources` type and a
+      `ToSources` class.  A `Sources` wraps a list of `(SourcePos, Text)` pairs
+      [API change]. A parsec `Stream` instance is provided for `Sources`.  The
+      module also exports versions of parsec's `satisfy` and other Char parsers
+      that track source positions accurately from a `Sources` stream (or any
+      instance of the new `UpdateSourcePos` class).
+
+    * Text.Pandoc.Parsing
+
+      + Export the modified Char parsers defined in Text.Pandoc.Sources
+        instead of the ones parsec provides.  Modified parsers to use a
+        `Sources` as stream [API change].
+      + Improve include file functions [API change].  Remove old
+        `insertIncludedFileF`.  Give `insertIncludedFile` a more general type,
+        allowing it to be used where `insertIncludedFileF` was.
+      + Add parameter to the `citeKey` parser from
+        Text.Pandoc.Parsing, which controls whether the `@{..}`
+        syntax is allowed [API change].
+
+    * Text.Pandoc.Error: Modified the constructor `PandocParsecError` to take a
+      `Sources` rather than a `Text` as first argument, so parse error 
locations
+      can be accurately reported.
+
+    * Fix source position reporting for YAML bibliographies (#7273).
+
+    * Issue error message when  reader or writer format is malformed
+      (#7231).  Previously we exited with an error status but (due to a bug)
+      no message.
+
+    * Smarter smart quotes (#7216, #2103).  Treat a leading `"` with no
+      closing `"` as a left curly quote.  This supports the practice, in
+      fiction, of continuing paragraphs quoting the same speaker without an
+      end quote.  It also helps with quotes that break over lines in line 
blocks.
+
+    * Markdown reader:
+
+      + Use MetaInlines not MetaBlocks for multimarkdown metadata fields.
+        This gives better results in converting to e.g.  pandoc markdown.
+      + Implement curly-brace syntax for Markdown citation keys (#6026).
+        The change provides a way to use citation keys that contain
+        special characters not usable with the standard citation key syntax.
+        Example: `@{foo_bar{x}'}` for the key `foo_bar{x}`.  It also allows
+        separating citation keys from immediately following text, e.g. 
`@{foo}A`.
+
+    * RST reader:
+
+      + Seek include files in the directory of the file
+        containing the include directive, as RST requires (#6632).
+      + Use `insertIncludedFile` from Text.Pandoc.Parsing
+        instead of reproducing much of its code.
+
+    * Org reader: Resolve org includes relative to the directory containing the
+      file containing the INCLUDE directive (#5501).
+
+    * ODT reader: Treat tabs as spaces (#7185, niszet).
+
+    * Docx reader:
+
+      + Add handling of vml image objects (#7257, mbrackeantidot).
+      + Support new table features (Emily Bourke, #6316):  column
+        spans, row spans, multiple header rows, table description
+        (parsed as a simple caption), captions, column widths.
+
+    * LaTeX reader:
+
+      + Improved siunitx support (#6658, #6620).
+      + Better support for `\xspace` (#7299).
+      + Improve parsing of `\def` macros.  We previously set "verbatim mode"
+        even for parsing the initial `\def`; this caused problems
+        for `\def` nested inside another `\def`.
+      + Implement `\newif`.
+
+    * ConTeXt writer: improve ordered lists (#5016, Denis Maier).
+      Change ordered list from itemize to enumerate.  Add new
+      itemgroup for ordered lists.  Remove manual insertion of
+      width attributes.  Use tabular figures in ordered list
+      enumerators.
+
+    * HTML reader:
+
+      + Don't fail on unmatched closing "script" tag (Albert Krenkel, #7282).
+      + Keep h1 tags as normal headers (#2293, Albert Krewinkel).
+        The tags `<title>` and `<h1 class="title">` often contain the same
+        information, so the latter was dropped from the document. However, as
+        this can lead to loss of information, the heading is now always
+        retained.  Use `--shift-heading-level-by=-1` to turn the `<h1>`
+        into the document title, or a filter to restore the previous behavior.
+      + Handle relative lengths (e.g. `2*`) in HTML column widths (#4063).
+        See <https://www.w3.org/TR/html4/types.html#h-6.6>.
+
+    * DocBook/JATS readers:
+
+      + Fix mathml regression caused by the switch in XML libraries (#7173).
+      + Fix "phrase" in DocBook: take classes from "role" not "class" (#7195).
+
+    * DocBook reader: ensure that first and last names are separated (#6541).
+
+    * Jira reader (Albert Krewinkel, #7218):
+
+      + Support "smart" links: `[alias|https://example.com|smart-card]` syntax.
+      + Allow spaces and most unicode characters in attachment links.
+      + No longer require a newline character after `{noformat}`.
+      + Only allow URI path segment characters in bare links.
+      + The `file:` schema is no longer allowed in bare links; these
+        rarely make sense.
+
+    * Plain writer: handle superscript unicode minus (#7276).
+
+    * LaTeX writer:
+
+      + Better handling of line breaks in simple tables (#7272).
+        Now we also handle the case where they're embedded in other elements,
+        e.g. spans.
+      + For beamer output, support `exampleblock` and `alertblock` (#7278).
+        A block will be rendered as an `exampleblock` if the heading
+        has class `example` and an `alertblock` if it has class `alert`.
+      + Separate successive quote chars with thin space (#6958,
+        Albert Krewinkel).  Successive quote characters are separated with
+        a thin space to improve readability and to prevent unwanted ligatures.
+        Detection of these quotes sometimes had failed if the second quote
+        was nested in a span element.
+      + Separate successive quote chars with thin space (#6958, Albert
+        Krewinkel).
+
+    * EPUB Writer: Fix belongs-to-collection XML id choice (#7267, nuew).
+      The epub writer previously used the same XML id for both the book
+      identifier and the epub collection. This causes an error on epubcheck.
+
+    * BibTeX/BibLaTeX writer: Handle `annote` field (#7266).
+
+    * ZimWiki writer: allow links and emphasis in headers (#6605,
+      Albert Krewinkel).
+
+    * ConTeXt writer:
+
+      + Support blank lines in line blocks (#6564, Albert Krewinkel,
+        thanks to @denismaier).
+      + Use span identifiers as reference anchors (#7246, Albert Krewinkel).
+
+    * HTML writer:
+
+      + Keep attributes from code nested below `pre` tag (#7221,
+        Albert Krewinkel).  If a code block is defined with `<pre><code
+        class="language-x">???</code></pre>`, where the `<pre>` element has no
+        attributes, then the attributes from the `<code>` element are used
+        instead. Any leading `language-` prefix is dropped in the code's
+        `class` attribute are dropped to improve syntax highlighting.
+      + Ensure headings only have valid attribs in HTML4 (#5944, Albert
+        Krewinkel).
+      + Parse `<header>` as a Div (Albert Krewinkel).
+
+    * Org writer:
+
+      + Inline latex envs need newlines (#7252, tecosaur).
+        As specified in https://orgmode.org/manual/LaTeX-fragments.html, an
+        inline \begin{}...\end{} LaTeX block must start on a new line.
+      + Use LaTeX style maths deliminators (#7196, tecosaur).
+
+    * JATS writer (Albert Krewinkel):
+
+      + Use either styled-content or named-content for spans (#7211).
+        If the element has a content-type attribute, or at least one class,
+        then that value is used as `content-type` and the span is put inside
+        a `<named-content>` element. Otherwise a `<styled-content>` element
+        is used instead.
+      + Reduce unnecessary use of `<p>` elements for wrapping (#7227).
+        The `<p>` element is used for wrapping in cases were the contents
+        would otherwise not be allowed in a certain context. Unnecessary
+        wrapping is avoided, especially around quotes (`<disp-quote>` 
elements).
+      + Convert spans to `<named-content>` elements (#7211).  Spans with
+        attributes are converted to `<named-content>` elements instead of
+        being wrapped with `<milestone-start/>` and `<milestone-end>`
+        elements. Milestone elements are not allowed in documents using the
+        articleauthoring tag set, so this change ensures the creation of valid
++++ 224 more lines (skipped)
++++ between /work/SRC/openSUSE:Factory/pandoc/pandoc.changes
++++ and /work/SRC/openSUSE:Factory/.pandoc.new.1898/pandoc.changes

Old:
----
  pandoc-2.13.tar.gz

New:
----
  pandoc-2.14.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ pandoc.spec ++++++
--- /var/tmp/diff_new_pack.TgRTDB/_old  2021-06-01 10:40:51.557160109 +0200
+++ /var/tmp/diff_new_pack.TgRTDB/_new  2021-06-01 10:40:51.561160115 +0200
@@ -19,7 +19,7 @@
 %global pkg_name pandoc
 %bcond_with tests
 Name:           %{pkg_name}
-Version:        2.13
+Version:        2.14
 Release:        0
 Summary:        Conversion between markup formats
 License:        GPL-2.0-or-later
@@ -35,6 +35,7 @@
 BuildRequires:  ghc-SHA-devel
 BuildRequires:  ghc-aeson-devel
 BuildRequires:  ghc-aeson-pretty-devel
+BuildRequires:  ghc-array-devel
 BuildRequires:  ghc-attoparsec-devel
 BuildRequires:  ghc-base64-bytestring-devel
 BuildRequires:  ghc-binary-devel
@@ -87,6 +88,7 @@
 BuildRequires:  ghc-text-conversions-devel
 BuildRequires:  ghc-text-devel
 BuildRequires:  ghc-time-devel
+BuildRequires:  ghc-unicode-collation-devel
 BuildRequires:  ghc-unicode-transforms-devel
 BuildRequires:  ghc-unix-devel
 BuildRequires:  ghc-unordered-containers-devel
@@ -144,7 +146,6 @@
 
 %prep
 %autosetup
-cabal-tweak-dep-ver 'attoparsec' '< 0.14' '< 0.15'
 
 %build
 %ghc_lib_build

++++++ pandoc-2.13.tar.gz -> pandoc-2.14.tar.gz ++++++
/work/SRC/openSUSE:Factory/pandoc/pandoc-2.13.tar.gz 
/work/SRC/openSUSE:Factory/.pandoc.new.1898/pandoc-2.14.tar.gz differ: char 17, 
line 1

Reply via email to