Hello community,

here is the log from the commit of package qpdf for openSUSE:Factory checked in 
at 2019-01-25 22:41:52
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/qpdf (Old)
 and      /work/SRC/openSUSE:Factory/.qpdf.new.28833 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "qpdf"

Fri Jan 25 22:41:52 2019 rev:38 rq:667891 version:8.3.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/qpdf/qpdf.changes        2018-08-28 
09:21:12.824223329 +0200
+++ /work/SRC/openSUSE:Factory/.qpdf.new.28833/qpdf.changes     2019-01-25 
22:41:55.403334786 +0100
@@ -1,0 +2,8 @@
+Mon Jan 21 12:43:47 UTC 2019 - Ismail Dönmez <[email protected]>
+
+- Update to version 8.3.0
+  See included ChangeLog for the complete changelog
+- Add qpdf-data-loss-fix.patch to fix
+  https://github.com/qpdf/qpdf/issues/276
+
+-------------------------------------------------------------------

Old:
----
  qpdf-8.2.1.tar.gz
  qpdf-8.2.1.tar.gz.asc

New:
----
  qpdf-8.3.0.tar.gz
  qpdf-8.3.0.tar.gz.asc
  qpdf-data-loss-fix.patch

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

Other differences:
------------------
++++++ qpdf.spec ++++++
--- /var/tmp/diff_new_pack.B3zy1x/_old  2019-01-25 22:41:56.103333924 +0100
+++ /var/tmp/diff_new_pack.B3zy1x/_new  2019-01-25 22:41:56.103333924 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package qpdf
 #
-# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany.
+# Copyright (c) 2019 SUSE LINUX GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -12,13 +12,13 @@
 # license that conforms to the Open Source Definition (Version 1.9)
 # published by the Open Source Initiative.
 
-# Please submit bugfixes or comments via http://bugs.opensuse.org/
+# Please submit bugfixes or comments via https://bugs.opensuse.org/
 #
 
 
 %define so_version 21
 Name:           qpdf
-Version:        8.2.1
+Version:        8.3.0
 Release:        0
 Summary:        Command-line tools and library for transforming PDF files
 License:        Apache-2.0
@@ -27,6 +27,7 @@
 Source:         
https://github.com/qpdf/qpdf/releases/download/release-qpdf-%{version}/qpdf-%{version}.tar.gz
 Source1:        
https://github.com/qpdf/qpdf/releases/download/release-qpdf-%{version}/qpdf-%{version}.tar.gz.asc
 Source2:        qpdf.keyring
+Patch1:         qpdf-data-loss-fix.patch
 BuildRequires:  gcc-c++
 BuildRequires:  libjpeg8-devel
 BuildRequires:  pkgconfig
@@ -73,6 +74,7 @@
 
 %prep
 %setup -q
+%autosetup -p1
 
 %build
 export CXXFLAGS="%{optflags} -fvisibility-inlines-hidden"

++++++ qpdf-8.2.1.tar.gz -> qpdf-8.3.0.tar.gz ++++++
/work/SRC/openSUSE:Factory/qpdf/qpdf-8.2.1.tar.gz 
/work/SRC/openSUSE:Factory/.qpdf.new.28833/qpdf-8.3.0.tar.gz differ: char 5, 
line 1

++++++ qpdf-data-loss-fix.patch ++++++
>From 4bc434000c42a7191e705c8a38216ca6743ad9ff Mon Sep 17 00:00:00 2001
From: Jay Berkenbilt <[email protected]>
Date: Thu, 17 Jan 2019 08:50:19 -0500
Subject: [PATCH] Copy subdictionaries when removing resources (fixes #276)

When removing unreferenced resources, the code was copying the overall
resource dictionaries but not the subdictionaries being modified. This
was a "typo" in the code -- the comment clearly stated the need to do
this, but the code replaced the dictionary with itself rather than
with a shallow copy of itself.
---
 libqpdf/QPDFPageObjectHelper.cc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/libqpdf/QPDFPageObjectHelper.cc b/libqpdf/QPDFPageObjectHelper.cc
index 611f33ea..ba647372 100644
--- a/libqpdf/QPDFPageObjectHelper.cc
+++ b/libqpdf/QPDFPageObjectHelper.cc
@@ -156,6 +156,7 @@ QPDFPageObjectHelper::removeUnreferencedResources()
         {
             continue;
         }
+        dict = dict.shallowCopy();
         resources.replaceKey(*d_iter, dict);
         std::set<std::string> keys = dict.getKeys();
         for (std::set<std::string>::iterator k_iter = keys.begin();


Reply via email to