Re: handling t64 backports in ppas
On Fri, Jun 7, 2024, at 4:38 PM, Jay Berkenbilt wrote: > On Fri, Jun 7, 2024, at 2:11 PM, Jeremy Bícha wrote: > > On Fri, Jun 7, 2024 at 2:03 PM Jay Berkenbilt wrote: > > > Sometime in the next few months, I plan on releasing qpdf 12, which > > > will include ABI-breaking changes. My hope would be update the debian > > > package to libqpdf30 and drop all the t64 stuff, but doing so will > > > complicate further backports. I could do any of these and am looking > > > for advice. > > > > The easiest solution for backports is to build and name your packages > > like normal but be sure to not build your package on affected > > architectures. If you are only backporting to Ubuntu, be sure your > > package does not build on armhf. That can either be set in the source > > package or in the PPA settings. > > Great, thanks. Looking at my PPA settings, it seems it is only > building for arm64, amd64, and i386. When I release qpdf 12, I'll make > sure to uncheck i386. armhf isn't even checked. By controlling it in > the PPA, I'll be able to do a straight backport. Actually, if I turn > it off right now, I can do a straight backport as the t64 package name > in jammy will be harmless. I will test upgrade path of jammy -> jammy > ppa without t64 -> jammy ppa with t64 -> noble ppa before uploading. A straight backport to jammy doesn't actually work because of the versioned dependency on dpkg-dev, but I know what to do now and will stop spamming the list. Thanks again. --Jay -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: handling t64 backports in ppas
On Fri, Jun 7, 2024, at 2:11 PM, Jeremy Bícha wrote: > On Fri, Jun 7, 2024 at 2:03 PM Jay Berkenbilt wrote: > > Sometime in the next few months, I plan on releasing qpdf 12, which > > will include ABI-breaking changes. My hope would be update the debian > > package to libqpdf30 and drop all the t64 stuff, but doing so will > > complicate further backports. I could do any of these and am looking > > for advice. > > The easiest solution for backports is to build and name your packages > like normal but be sure to not build your package on affected > architectures. If you are only backporting to Ubuntu, be sure your > package does not build on armhf. That can either be set in the source > package or in the PPA settings. Great, thanks. Looking at my PPA settings, it seems it is only building for arm64, amd64, and i386. When I release qpdf 12, I'll make sure to uncheck i386. armhf isn't even checked. By controlling it in the PPA, I'll be able to do a straight backport. Actually, if I turn it off right now, I can do a straight backport as the t64 package name in jammy will be harmless. I will test upgrade path of jammy -> jammy ppa without t64 -> jammy ppa with t64 -> noble ppa before uploading. > If you are also doing backports for Debian, there are a few other > affected architectures. Right, thanks. I have no intention of doing a debian backport. There's not enough demand, and qpdf is easy to build from source (depending only on zlib, jpeg, and openssl or gnutls, which are all ubiquitous). Anyway, your solution of simply disabling the 32-bit architectures is simple, and there is probably no demand for backported qpdf packages from my PPA on 32-bit architectures. Thanks for the quick response. --Jay -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
handling t64 backports in ppas
I am not subscribed to this list, so please CC me on response (or tell me to subscribe if needed). I am also known as q...@debian.org, upstream author and debian maintainer of qpdf. qpdf was affected by the 64-bit time_t transition. I maintain a ppa (ppa:qpdf/qpdf) where I backport the latest debian version of qpdf to all supported Ubuntu versions. I believe I know how to handle 64-bit time_t, but I want to check myself before uploading any backports. Today, I am releasing qpdf 11.9.1. The version in noble is 11.9.0-1.1build1, which is based on the 64-bit time_t NMU from debian. The shared library package is libqpdf29t64 on noble and libqpdf29 on earlier versions. 11.9.0-2 on debian incorporates the 64-bit time_t NMU and is identical to 11.9.0-1.1 except the version number. * For noble and newer, I can just use `backportpackage` from ubuntu-dev-tools as I have in the past. Since noble has 64-bit time_t, there should be no issue with this. * For jammy and focal, I will need to build a release-specific version of the package without the t64 changes. I already build a special version with focal that excludes the doc package (because sphinx is too old to build my docs on focal), so I have a working path to do this. The versions in the ppa for focal, jammy, and mantic (if I bother) will have libqpdf29 in them without any provided/breaks/replaces, and so those will upgrade smoothly to the version in the noble ppa. Sometime in the next few months, I plan on releasing qpdf 12, which will include ABI-breaking changes. My hope would be update the debian package to libqpdf30 and drop all the t64 stuff, but doing so will complicate further backports. I could do any of these and am looking for advice. 1. Call the new version libqpdf30t64 with the same provides/breaks/replaces as in the t64 version of the library, and backport the older version as libqpdf30, perpetuating the t64 stuff in the debian package. I'd have to wait until the the oldest version of Ubuntu I routinely backport to goes out of support, and then I could drop t64 after the next ABI change. That may be years from now. 2. Try to do something goofy with having the backported version be libqpdf30t32 or something, but that would be a one-off, and I would have to do keep the provides/breaks/replaces stuff around if I want to be able to just use backportpackage in the future. But surely this is going to happen -- people will start making PPAs to backport things from debian that were natively uploaded for the first time after 64-bit time_t, and the backporters will have to deal with this issue, right? And some of them won't think about it. So is there a plan for this? I haven't been able to find anything. 3. Something else I'm not thinking about? I can't remember if there's a way I can put something in the old package that hints about its replacement. In other words, if I could make libqpdf30 clean (no provides/replaces/breaks) and put something in the backported libqpdf30t32 that would achieve the same result, allowing it to be replaced by libqpdf30 after an upgrade. The other option would be to just not backport qpdf 12 to anything older than noble. If this is too complicated, I may just go that way. People can always build from source if they want it badly enough. If this has already been worked out, feel free to just point me to where to read. I've searched but haven't found anything. Thanks! --Jay Berkenbilt a.k.a -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Bug#1067196: qpdf: contrary to the documentation, fix-qdf aborts on removed objects
(Sorry for the duplicate -- I inadvertently failed to cc the bug report on my private reply.) On Sun, Apr 14, 2024, at 1:50 PM, Thorsten Glaser wrote: > Jay Berkenbilt dixit: > > >As it happens, I am upstream. > > Oh, nice ☻ in that case, thanks for qpdf. > > >--- > >It is not generally practical to remove objects from QDF files without > >messing up object numbering, but if you remove all indirect references > >to an object (without removing the object itself), this will leave the > >object unreferenced. Then you can run qpdf on the file (after running > >:command:`fix-qdf`), and qpdf will omit the now-orphaned object. > >--- > > That fixes the ambiguity but leaves the reader¹ wondering, on two > reading passes, what other references than indirect there are. > The reader who has not digested the PDF spec in and out, at least. > > If you s/ indirect//, would it still be correct? That would be > less possibly-ambiguous, I think. If it triggers this thought in you, it will trigger it in others. New wording: It is not generally practical to remove objects from QDF files without messing up object numbering, but if you remove all references to an object without removing the object itself (by removing all indirect objects that point to it), this will leave the object unreferenced. Then you can run qpdf on the file (after running :command:`fix-qdf`), and qpdf will omit the now-orphaned object. > bye, > //mirabilos > ① or at least me right now > -- > Beware of ritual lest you forget the meaning behind it. > yeah but it means if you really care about something, don't > ritualise it, or you will lose it. don't fetishise it, don't > obsess. or you'll forget why you love it in the first place. >
Bug#1067196: qpdf: contrary to the documentation, fix-qdf aborts on removed objects
Sorry for the top-post. As it happens, I am upstream. I have rewritten the pargraph as follows. I think this is clearer. What do you think? If you like it, I'll close this. My fix is here: https://github.com/qpdf/qpdf/pull/1187 --- It is not generally practical to remove objects from QDF files without messing up object numbering, but if you remove all indirect references to an object (without removing the object itself), this will leave the object unreferenced. Then you can run qpdf on the file (after running :command:`fix-qdf`), and qpdf will omit the now-orphaned object. --- On Sun, Apr 7, 2024, at 5:04 AM, Thorsten Glaser wrote: > Jay Berkenbilt dixit: > > >Can you tell me where in the docs it says what you're describing? > >Here's a direct quote from the current qpdf documentation: > > > >It is not generally practical to remove objects from QDF files without > >messing up object numbering, but if you remove all references to an > >object, you can run qpdf on the file (after running fix-qdf), and qpdf > >will omit the now-orphaned object. > > Yes, I meant that. At least two people assumed that “remove all > references” includes the object itself, but now that you point it > out, it likely doesn’t, but we are no native speakers, so I don’t > know which of the two interpretations is more likely to them or > if even both are possible. > > Maybe, if you have good connections to upstream, suggest to them > to add “(but not the object itself)” to behind “all references to > an object”, but the bug can then be closed. > > Thanks for looking into it, > //mirabilos > -- > Solange man keine schmutzigen Tricks macht, und ich meine *wirklich* > schmutzige Tricks, wie bei einer doppelt verketteten Liste beide > Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz > hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r >
Bug#1067196: qpdf: contrary to the documentation, fix-qdf aborts on removed objects
Can you tell me where in the docs it says what you're describing? Here's a direct quote from the current qpdf documentation: It is not generally practical to remove objects from QDF files without messing up object numbering, but if you remove all references to an object, you can run qpdf on the file (after running fix-qdf), and qpdf will omit the now-orphaned object. To me, it seems that the documentation matches the observed and intended behavior. Maybe there was an error in the older docs that have been subsequently fixed. On Tue, Mar 19, 2024, at 5:14 PM, Thorsten Glaser wrote: > Package: qpdf > Version: 10.1.0-1 > Severity: normal > Tags: upstream > X-Debbugs-Cc: t...@mirbsd.de, n...@naturalnet.de > > The qpdf documentation states that it is possible to remove an object > then run fix-qdf and it should renumber the remaining objects. > > In an exemplary PDF, I did this: > > - qpdf --qdf dings.pdf dings.qdf > - $EDITOR dings.qdf > - remove object '38 0' and the one reference to it > - fix-qdf dings.qdf >dings2.qdf > > It complained about the missing object: > > dings.qdf:20254: expected object 38 > > Line 20254 here is exactly the beginning of object '39 0' > after the end of object '37 0'. > > ──┤ Workaround ├ > > Just removing all the references and letting qpdf clean up the > now-unreferenced object seems to have worked here. > > But this does still not work as documented…
Bug#1037136: bumping qpdf 64-bit time_t for 11.9.0 in experimental
I need to upload qpdf 11.9.0-1 to unstable. Since this is newer than 11.8.0-1.1~exp1 in experimental with the 64-bit time_t NMU, it will cause that to disappear. In an effort to avoid that and keep things in sync with the time_t transition, I have ported the NMU forward to 11.9.0-1 and will upload 11.9.0-2~exp1 with the time_t changes to experimental right after I upload 11.9.0-1 to experimental. I am hoping that I am not messing anything up with this. Please feel free to adjust tags, do a separate NMU, or whatever is needed if I have gotten things out of sync. In any case, I want to get 11.9.0-1 uploaded right away since I'd like it to sync to Ubuntu before the 24.04 feature freeze. I'm sending this to the qpdf NMU debdiff bug and to the bug referenced in that issue. Thanks. --Jay Berkenbilt , qpdf maintainer
Bug#1037136: bumping qpdf 64-bit time_t for 11.9.0 in experimental
I need to upload qpdf 11.9.0-1 to unstable. Since this is newer than 11.8.0-1.1~exp1 in experimental with the 64-bit time_t NMU, it will cause that to disappear. In an effort to avoid that and keep things in sync with the time_t transition, I have ported the NMU forward to 11.9.0-1 and will upload 11.9.0-2~exp1 with the time_t changes to experimental right after I upload 11.9.0-1 to experimental. I am hoping that I am not messing anything up with this. Please feel free to adjust tags, do a separate NMU, or whatever is needed if I have gotten things out of sync. In any case, I want to get 11.9.0-1 uploaded right away since I'd like it to sync to Ubuntu before the 24.04 feature freeze. I'm sending this to the qpdf NMU debdiff bug and to the bug referenced in that issue. Thanks. --Jay Berkenbilt , qpdf maintainer
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
I have verified by running manual tests on a docker image of 23.04 and 23.10 after manually installing the packages as downloaded from https://bugs.launchpad.net/ubuntu/+source/qpdf by verifying that I could reproduce the bug, then install the updated libqpdf package, then verifying that the bug was fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Fix Committed Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
All, thanks for pushing this through. To be clear, I agree with all the points that it would have been better if we could have included the extra tests, but I'm glad you agree with my analysis about the cost vs. benefit. I will find some time to test in the next few days. I can do the manual test from the test plan and also do a local build with the additional test cases by just cherry-picking the commit into a temporary branch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Fix Committed Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who
[Desktop-packages] [Bug 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2
The tests include binary files. Unless something has changed, I can't create a quilt patch that modifies a binary file. The qpdf test suite is full of PDF files, and PDF files are binary files, even when they are hand-created, as many of mine are. This makes including tests in patches challenging. There are a few unit tests that we could include, but they will likely not backport cleanly, which adds additional risk, and I don't think including them in the patch will add any value since the tests are specifically crafted to prove that this bug is fixed, and we have already done that through current releases and the manual tests. The bug affects a very specific pattern in the data. This part of the code that was affected is not actively modified, and the bug involved changing an infrequently-traversed section of code. The tokenizer is very low level and stable, and I did an audit of the code again after this bug was found. qpdf has been an open source project since 2008 and has been in debian since the beginning. I am the author and debian maintainer. It is excessively unlikely that there will a "next" SRU that will come from other than the version control system, and unless I am hit by the proverbial bus, I will probably be the originator of it. While qpdf has a wide following, if I were not there to fix problems like this and push them through, it is not likely that problems like this would even be entered into an SRU process. It's been quite a long time since there's been any divergence between the debian and Ubuntu versions of the package. While I agree that more testing is better, I wonder if the benefit we will get is actually worth the effort. The new tests exercise specific case related to this fix. If there is still a bug of this type, adding the new tests will not help us find them. I don't think it would be worth the hassle to tweak the test system or jump through some hoops to allow the binary files involved in the tests to get into the patch -- that is more likely to cause a problem than to prevent one. The same is true of trying to backport the unit tests. qpdf processes millions of pages a day across a wide range of free and commercial systems. My employer processes over a million pages a day all by itself. In qpdf's 21 year history, 15 of which have been open source, this is only the second data-loss bug, and it has the potential to cause silent corruption of data in rare corner cases. I appreciate the diligence here, but I really think the level of testing that has already gone into this, the inclusion of new patches in the latest release, is adequate, and now that the bug is known, our priority should be getting a well- reviewed, well-tested patch in front of users to minimize the risk of data loss. Please let me know what else I need to do to get this through. I will cooperate, of course. My intention here is not to argue, but rather to try to assure you that the testing is already quite thorough, most likely exceeding the standard that would be applied to most packages by their authors. We are passing a point of diminishing return. Thanks for considering my argument. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: New Status in qpdf source package in Lunar: New Status in qpdf source package in Mantic: New Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the
[Desktop-packages] [Bug 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2
> This is great, but is this test suite run as part of the package build and publication process in Ubuntu? If not, how could we arrange to run the test suite against the Ubuntu build of the package that includes this patch to ensure that we aren't regressing unaffected users in providing this update? The test suite is run as part of the Ubuntu build. The patch doesn't include the new test cases, but it does include all the old ones, which should demonstrate that there is no regression. When 24.04 opens for business and the packages sync, the new tests will run as they are in 11.6.3. You can also see it in my PPA: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf. In any case, I believe the fact that test suite is run during the existing builds should be sufficient to ensure that there is no regression. qpdf also has meaningful autopkgtests. You can also check the debian build output. Debian stable proposed updates has 11.3.0 with the same patch. For manual testing: Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: New Status in qpdf source package in Lunar: New Status in qpdf source package in Mantic: New Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's
[Desktop-packages] [Bug 2039804] Re: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2
I've gone as far as I think I can, but I can do additional steps if needed. I have not tagged this or uploaded anything anywhere. Please let me know if I can/should take any additional steps to get this approved and processed as an SRU. ** Summary changed: - qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 + SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 Status in qpdf package in Ubuntu: New Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be reprocessed in the new state. qpdf has a rigorous test suite and an extremely good quality record. It processes millions of documents daily by many commercial entities. My current employer runs millions of pages a day through qpdf. [ Other Info ] See also Upstream bug report: https://github.com/qpdf/qpdf/issues/1050 Corresponding debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054158 Debian stable release approval: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/2039804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039804] [NEW] SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2
Public bug reported: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be reprocessed in the new state. qpdf has a rigorous test suite and an extremely good quality record. It processes millions of documents daily by many commercial entities. My current employer runs millions of pages a day through qpdf. [ Other Info ] See also Upstream bug report: https://github.com/qpdf/qpdf/issues/1050 Corresponding debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054158 Debian stable release approval: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New ** Patch added: "qpdf-11.3.0-1ubuntu1.debdiff" https://bugs.launchpad.net/bugs/2039804/+attachment/5711201/+files/qpdf-11.3.0-1ubuntu1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 Status in qpdf package in Ubuntu: New Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases,
[Desktop-packages] [Bug 2039804] Re: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2
** Patch added: "qpdf-11.5.0-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/2039804/+attachment/5711202/+files/qpdf-11.5.0-1ubuntu1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 Status in qpdf package in Ubuntu: New Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be reprocessed in the new state. qpdf has a rigorous test suite and an extremely good quality record. It processes millions of documents daily by many commercial entities. My current employer runs millions of pages a day through qpdf. [ Other Info ] See also Upstream bug report: https://github.com/qpdf/qpdf/issues/1050 Corresponding debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054158 Debian stable release approval: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/2039804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Bug#1054119: data loss patch for qpdf targeted at stable (11.3.0)
On Tue, Oct 17, 2023, at 12:15 PM, Adam D. Barratt wrote: > # bcc control@bugs.d.o > user release.debian@packages.debian.org > usertags 1054119 pu > tags 1054119 bookworm moreinfo > retitle 1054119 bookworm-pu: package qpdf/11.3.0-1 > thanks Thanks for fixing the tags. I'll reply to this instead of starting over. > On Tue, 2023-10-17 at 07:32 -0400, Jay Berkenbilt wrote: > > The attached patch to qpdf 11.3.0 fixes a bug that could potentially > > result in loss of data. I'd like permission from the release team to > > . . . > > > > Close, but a few rough edges. :-) > Ah, thanks for helping me get past my brain rot. When I used to maintain several packages, including tiff and icu, which had lots of security updates, I was much more familiar with this. It's funny how we can forget something so thoroughly that we can forget we knew it at one time. The doc reference was perfect and jogged my memory. > As noted in the dev-ref section, please use "reportbug > release.debian.org" for p-u requests, or set equivalent metadata. That > helps ensure that the request ends up in the correct section of our BTS > web view, where uncategorised bugs may get overlooked for some time. > I've fixed up the relevant bits for this request (see the start of my > reply). Thanks for fixing it up. Rather than starting over, I am replying with the information from reportbug. I'll let you remove the moreinfo tag assuming I have provided enough information. -- [ Reason ] Between qpdf 10.6.3 and 11.0.0, a contributor did substantial refactoring and performance optimizations on qpdf, ultimately achieving better than a 2x performance boost. In spite of careful testing and review, a bug to the lexical layer of qpdf snuck in. From the changelog: Fix data loss bug introduced in 11.0.0 and fixed in 11.6.3. The bug causes the qpdf tokenizer to discard the character after a one-digit or two-digit quoted octal string. Most writers don't create these, and they are rare outside of content streams. By default, qpdf doesn't parse content streams. The most common place for this to occur would be in a document's /ID string, but in the worst case, this bug could cause silent damage to some strings in a PDF file's metadata, such as bookmark names or form field values. The fix is in upstream version 11.6.3 which has been uploaded to unstable and has migrated to testing. Given that this bug can cause potential data loss, updating stable is warranted. The version in oldstable is not affected by this bug. [ Impact ] In rare cases, qpdf may silently corrupt data in the user's PDF file. [ Tests ] The commit that includes the fix: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 includes a number of new automated tests to specifically exercise this bug. (I have not included the additional automated tests in the patch.) Additionally, the user who reported the original upstream bug: https://github.com/qpdf/qpdf/issues/1050 has confirmed that the issue is fixed. I also verified with the user's file. [ Risks ] This is a very low-risk patch. The fix is small and targeted. qpdf has a rigorous test suite and a very good track record for stability. A bug of this sort is a very rare event. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] The character following the short octal quoted character was used to cause a state transition in the tokenizer but not reprocessed in the new state. The bug fixes this. Prior to refactoring, the code did not suffer from this logic error because a different mechanism was used to re-process a character used in a state transition. [ Other info ] Note: I am the upstream author of qpdf as well as the debian maintainer of the package. The user who submitted the pull request that contained this bug is a reliable and steady contributor to qpdf who has made great improvements to the code base. Heavy refactoring carries risks. qpdf processes millions of pages a day in commercial and open source applications. It is very important to get this fix out to avoid silent and hard-to-detect damage to PDF files. qpdf_11.30.0-1--11.30.0-1+deb12u1.debdiff Description: Binary data
Bug#1054119: data loss patch for qpdf targeted at stable (11.3.0)
On Tue, Oct 17, 2023, at 12:15 PM, Adam D. Barratt wrote: > # bcc control@bugs.d.o > user release.debian@packages.debian.org > usertags 1054119 pu > tags 1054119 bookworm moreinfo > retitle 1054119 bookworm-pu: package qpdf/11.3.0-1 > thanks Thanks for fixing the tags. I'll reply to this instead of starting over. > On Tue, 2023-10-17 at 07:32 -0400, Jay Berkenbilt wrote: > > The attached patch to qpdf 11.3.0 fixes a bug that could potentially > > result in loss of data. I'd like permission from the release team to > > . . . > > > > Close, but a few rough edges. :-) > Ah, thanks for helping me get past my brain rot. When I used to maintain several packages, including tiff and icu, which had lots of security updates, I was much more familiar with this. It's funny how we can forget something so thoroughly that we can forget we knew it at one time. The doc reference was perfect and jogged my memory. > As noted in the dev-ref section, please use "reportbug > release.debian.org" for p-u requests, or set equivalent metadata. That > helps ensure that the request ends up in the correct section of our BTS > web view, where uncategorised bugs may get overlooked for some time. > I've fixed up the relevant bits for this request (see the start of my > reply). Thanks for fixing it up. Rather than starting over, I am replying with the information from reportbug. I'll let you remove the moreinfo tag assuming I have provided enough information. -- [ Reason ] Between qpdf 10.6.3 and 11.0.0, a contributor did substantial refactoring and performance optimizations on qpdf, ultimately achieving better than a 2x performance boost. In spite of careful testing and review, a bug to the lexical layer of qpdf snuck in. From the changelog: Fix data loss bug introduced in 11.0.0 and fixed in 11.6.3. The bug causes the qpdf tokenizer to discard the character after a one-digit or two-digit quoted octal string. Most writers don't create these, and they are rare outside of content streams. By default, qpdf doesn't parse content streams. The most common place for this to occur would be in a document's /ID string, but in the worst case, this bug could cause silent damage to some strings in a PDF file's metadata, such as bookmark names or form field values. The fix is in upstream version 11.6.3 which has been uploaded to unstable and has migrated to testing. Given that this bug can cause potential data loss, updating stable is warranted. The version in oldstable is not affected by this bug. [ Impact ] In rare cases, qpdf may silently corrupt data in the user's PDF file. [ Tests ] The commit that includes the fix: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 includes a number of new automated tests to specifically exercise this bug. (I have not included the additional automated tests in the patch.) Additionally, the user who reported the original upstream bug: https://github.com/qpdf/qpdf/issues/1050 has confirmed that the issue is fixed. I also verified with the user's file. [ Risks ] This is a very low-risk patch. The fix is small and targeted. qpdf has a rigorous test suite and a very good track record for stability. A bug of this sort is a very rare event. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] The character following the short octal quoted character was used to cause a state transition in the tokenizer but not reprocessed in the new state. The bug fixes this. Prior to refactoring, the code did not suffer from this logic error because a different mechanism was used to re-process a character used in a state transition. [ Other info ] Note: I am the upstream author of qpdf as well as the debian maintainer of the package. The user who submitted the pull request that contained this bug is a reliable and steady contributor to qpdf who has made great improvements to the code base. Heavy refactoring carries risks. qpdf processes millions of pages a day in commercial and open source applications. It is very important to get this fix out to avoid silent and hard-to-detect damage to PDF files. qpdf_11.30.0-1--11.30.0-1+deb12u1.debdiff Description: Binary data
Bug#1054158: Data loss bug affecting qpdf 11.0.0 through 11.6.2 has upstream fix in 1ecc6bb2
Package: qpdf Version: 11.3.0-1 Severity: important Tags: upstream X-Debbugs-Cc: q...@debian.org Note: I am the upstream author and debian maintainer for qpdf. Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I am not attaching a patch to the bug report because I am the package maintainer and intend to immediately follow this with a fix targeted to bookworm. Please note: I am composing this bug from a system running Ubuntu 23.04 I have edited the package version in the bug pseudo-headers, but the system information below pertains to the system I am running reportbug from, which is not the system that is broken. -- System Information: Debian Release: bookworm/sid APT prefers lunar-updates APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 'lunar'), (100, 'lunar-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.2.0-34-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qpdf depends on: ii libc6 2.37-0ubuntu2.1 ii libgcc-s1 13.1.0-2ubuntu2~23.04 ii libqpdf29 11.6.3-1~bpo23.04.1~ppa1 ii libstdc++6 13.1.0-2ubuntu2~23.04 qpdf recommends no packages. qpdf suggests no packages. -- no debconf information
Bug#1054119: data loss patch for qpdf targeted at stable (11.3.0)
Package: release.debian.org
X-Debbugs-CC: q...@debian.org
The attached patch to qpdf 11.3.0 fixes a bug that could potentially
result in loss of data. I'd like permission from the release team to
upload this to stable. I've been a debian developer since 2005, but
it's been years since I've last prepared a release to the stable
distribution. As far as I can tell, the current procedure is to upload
with the target distribution as "stable" and upload to ftp-master.
This will direct the package the proposed-updates queue. Is this
correct?
The nature of the bug is that, if a quoted octal character with one or
two digits instead of three digits appears in the file, the following
character will be dropped from the string. This bug snuck in in a pull
request I accepted that performed significant performance optimization
on the tokenizer. Because it only affects strings in metadata when
qpdf is used in its default configuration, and because such quoted
characters of this type don't appear very often, it's somewhat of a
corner case, but I think the bug is critical to fix because there is a
chance that it could silently damage files in ways that would be hard
to detect.
Please let me know if I should proceed with an update to stable.
--Jay Berkenbilt (a.k.a. q...@debian.org)--- libqpdf/QPDFTokenizer.cc.orig 2023-10-17 07:19:31.829119946 -0400
+++ libqpdf/QPDFTokenizer.cc 2023-10-17 07:20:55.689510562 -0400
@@ -739,17 +739,22 @@
void
QPDFTokenizer::inCharCode(char ch)
{
+bool handled = false;
if (('0' <= ch) && (ch <= '7')) {
this->char_code = 8 * this->char_code + (int(ch) - int('0'));
if (++(this->digit_count) < 3) {
return;
}
-// We've accumulated \ddd. PDF Spec says to ignore
-// high-order overflow.
+handled = true;
}
+// We've accumulated \ddd or we have \d or \dd followed by other
+// than an octal digit. The PDF Spec says to ignore high-order
+// overflow.
this->val += char(this->char_code % 256);
this->state = st_in_string;
-return;
+if (!handled) {
+inString(ch);
+}
}
void
Bug#1054119: data loss patch for qpdf targeted at stable (11.3.0)
Package: release.debian.org
X-Debbugs-CC: q...@debian.org
The attached patch to qpdf 11.3.0 fixes a bug that could potentially
result in loss of data. I'd like permission from the release team to
upload this to stable. I've been a debian developer since 2005, but
it's been years since I've last prepared a release to the stable
distribution. As far as I can tell, the current procedure is to upload
with the target distribution as "stable" and upload to ftp-master.
This will direct the package the proposed-updates queue. Is this
correct?
The nature of the bug is that, if a quoted octal character with one or
two digits instead of three digits appears in the file, the following
character will be dropped from the string. This bug snuck in in a pull
request I accepted that performed significant performance optimization
on the tokenizer. Because it only affects strings in metadata when
qpdf is used in its default configuration, and because such quoted
characters of this type don't appear very often, it's somewhat of a
corner case, but I think the bug is critical to fix because there is a
chance that it could silently damage files in ways that would be hard
to detect.
Please let me know if I should proceed with an update to stable.
--Jay Berkenbilt (a.k.a. q...@debian.org)--- libqpdf/QPDFTokenizer.cc.orig 2023-10-17 07:19:31.829119946 -0400
+++ libqpdf/QPDFTokenizer.cc 2023-10-17 07:20:55.689510562 -0400
@@ -739,17 +739,22 @@
void
QPDFTokenizer::inCharCode(char ch)
{
+bool handled = false;
if (('0' <= ch) && (ch <= '7')) {
this->char_code = 8 * this->char_code + (int(ch) - int('0'));
if (++(this->digit_count) < 3) {
return;
}
-// We've accumulated \ddd. PDF Spec says to ignore
-// high-order overflow.
+handled = true;
}
+// We've accumulated \ddd or we have \d or \dd followed by other
+// than an octal digit. The PDF Spec says to ignore high-order
+// overflow.
this->val += char(this->char_code % 256);
this->state = st_in_string;
-return;
+if (!handled) {
+inString(ch);
+}
}
void
[Desktop-packages] [Bug 2008780] [NEW] please sync qpdf 11.3.0
Public bug reported: I'm not sure whether a feature freeze exception is required to sync 11.3.0 given that it was uploaded just before feature freeze. In any case, 11.3.0 has a couple of bug fixes, one very localized feature enhancement (whose implementation doesn't touch any existing code), and some dramatic performance enhancements. It would be great if that can be the version in Lunar. ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2008780 Title: please sync qpdf 11.3.0 Status in qpdf package in Ubuntu: New Bug description: I'm not sure whether a feature freeze exception is required to sync 11.3.0 given that it was uploaded just before feature freeze. In any case, 11.3.0 has a couple of bug fixes, one very localized feature enhancement (whose implementation doesn't touch any existing code), and some dramatic performance enhancements. It would be great if that can be the version in Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/2008780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1975740] [NEW] ec2-instance-connect fails with cert validation on ubuntu 22.04
Public bug reported: If needed, I can provide more exact steps to reproduce this, but hopefully this will be sufficient. Note that follow identical steps with Ubuntu 20.04 results in a working configuration. Launch an ec2 instance using the latest version of the Ubuntu AMI as returned by this query: aws ec2 describe-images --filters Name=architecture,Values=x86_64 Name=virtualization-type,Values=hvm Name=name,Values="ubuntu/images/*22.04-amd64-server-*" Name=block- device-mapping.volume-type,Values=gp2 --owners 099720109477 At this moment, that is ami-09db26f1ef0a9f406 in my region, us-east-1. Send public key: aws ec2-instance-connect send-ssh-public-key --availability-zone us- east-1a --instance-id i-abcdexample --instance-os-user ubuntu --ssh- public-key file:///home/user/.ssh/id_rsa.pub (Note: results are identical with .ssh/id_ed25519.pub) Attempt ssh ubuntu@ip-addr On the instance, /var/log/auth.log reports a failure. May 25 18:57:25 ip-10-98-1-66 sshd[1549]: AuthorizedKeysCommand /usr/share/ec2-instance-connect/eic_run_authorized_keys ubuntu SHA256:abcdefgexample failed, status 2 Running the failed command as root on the instance shows: C = US, O = "Starfield Technologies, Inc.", OU = Starfield Class 2 Certification Authority error 89 at 4 depth lookup: Basic Constraints of CA cert not marked critical C = US, O = "Starfield Technologies, Inc.", OU = Starfield Class 2 Certification Authority error 92 at 4 depth lookup: CA cert does not include key usage extension error /dev/shm/eic-7MlPua7W/cert.pem: verification failed I'm not sure where this certificate comes from, what's enforcing the key usage extension, etc. I haven't investigated further other than to verify that it's the same whether I use my RSA key or my ed25519 key (in fact, either way, my ssh client offers both keys, I see two log messages, and they both fail the same way) and to verify that it does work on Ubuntu 20.04. Also tried: apt update; apt dist-upgrade; reboot to ensure everything is up to date, verifying that ca-certificates is installed. If I use a keypair, I can log in just fine. To reproduce this for above, I launched the instance with a key pair, then moved .ssh/authorized_keys out of the way to see the failure. Please let me know if there's any other information I should supply or anything else you would like me to try. ** Affects: ec2-instance-connect (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975740 Title: ec2-instance-connect fails with cert validation on ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1975740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964707] [NEW] please sync qpdf 10.6.3
Public bug reported: qpdf 10.6.3 is in debian unstable with no blockers other than age. It is a bug-fix only release. The two code-facing changes are fix to allow correct handling of PDF 2.0 native UTF-8 strings and a fix to appearance stream generation when "0 Tf" appears in "/DA". ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964707 Title: please sync qpdf 10.6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1964707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1964707] [NEW] please sync qpdf 10.6.3
Public bug reported: qpdf 10.6.3 is in debian unstable with no blockers other than age. It is a bug-fix only release. The two code-facing changes are fix to allow correct handling of PDF 2.0 native UTF-8 strings and a fix to appearance stream generation when "0 Tf" appears in "/DA". ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1964707 Title: please sync qpdf 10.6.3 Status in qpdf package in Ubuntu: New Bug description: qpdf 10.6.3 is in debian unstable with no blockers other than age. It is a bug-fix only release. The two code-facing changes are fix to allow correct handling of PDF 2.0 native UTF-8 strings and a fix to appearance stream generation when "0 Tf" appears in "/DA". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1964707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960924] Re: qpdf 10.6.2 not syncing (freeze exception?)
Thanks for the clarification. What is the last date for uploading 10.6.3 before final freeze? There is one small bug fix on main for appearance stream generation that I might want to release, but I'll wait and see if anything else shows up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.2 not syncing (freeze exception?) Status in qpdf package in Ubuntu: New Bug description: I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as far as I can see, automatic sync freeze has not yet happened. There are some major changes in 10.6 that I would really like to get into Ubuntu because they include transitional code to help users migrate to qpdf 11. Is there something that needs to happen for this to sync? I don't want to miss the window. At this time, there are test failures in pikepdf because of a bug fix to qpdf in transcoding. We have determined that these test failures don't indicate a serious problem with either qpdf or pikepdf -- they are basically that pikepdf had some tests that were depending on incorrect qpdf functionality. For details, see https://github.com/pikepdf/pikepdf/issues/303 The pikepdf author is aware of the upcoming Ubuntu 22.04 freeze and is trying to get a fix in in time, but I'm hoping we can avoid getting into a situation where we miss the bus. There's a chance I might release 10.6.2 to fix one other minor transcoding issue, but I don't consider the issue to be important enough to justify a release. But if the pikepdf author wants a release to simplify his testing, I will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1960924] Re: qpdf 10.6.2 not syncing (freeze exception?)
Thanks for the clarification. What is the last date for uploading 10.6.3 before final freeze? There is one small bug fix on main for appearance stream generation that I might want to release, but I'll wait and see if anything else shows up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.2 not syncing (freeze exception?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960924] Re: qpdf 10.6.1 not syncing?
All regressions have been resolved now, and it seems to me like it's going to automatically migrate, but I'm not sure whether we missed the window to do so without a freeze exception. As far as I can see, the freeze date was February 19. I think the pikepdf upload that resolved the (false) regressions was February 20. If possible, consider this to be a freeze exception request (if needed). Hopefully the above is adequate justification. 10.6.2 is a relatively small change from 10.5.0 in terms of functionality, but it adds a number of new interfaces to the API and, most importantly, adds some documentation and preprocessor symbols designed to ease the transition to qpdf 11.0, which will switch shared pointer implementations that may require source changes in some rare cases. I released qpdf 10.6 two weeks before freeze to ensure it would make the cut, but then there were delays because of pikepdf test failures that weren't real problems, just reliance on previously incorrect functionality from qpdf. Over 10.5, 10.6 adds a number of fixes to character encoding issues (which is what caused the pikepdf test failures) and also makes it possible to use the C API to do a number of things that could previously only be done with the C++ API. Bottom line: this is a much better version to be in an LTS release than 10.5.0. ** Summary changed: - qpdf 10.6.1 not syncing? + qpdf 10.6.2 not syncing (freeze exception?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.2 not syncing (freeze exception?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1960924] Re: qpdf 10.6.1 not syncing?
All regressions have been resolved now, and it seems to me like it's going to automatically migrate, but I'm not sure whether we missed the window to do so without a freeze exception. As far as I can see, the freeze date was February 19. I think the pikepdf upload that resolved the (false) regressions was February 20. If possible, consider this to be a freeze exception request (if needed). Hopefully the above is adequate justification. 10.6.2 is a relatively small change from 10.5.0 in terms of functionality, but it adds a number of new interfaces to the API and, most importantly, adds some documentation and preprocessor symbols designed to ease the transition to qpdf 11.0, which will switch shared pointer implementations that may require source changes in some rare cases. I released qpdf 10.6 two weeks before freeze to ensure it would make the cut, but then there were delays because of pikepdf test failures that weren't real problems, just reliance on previously incorrect functionality from qpdf. Over 10.5, 10.6 adds a number of fixes to character encoding issues (which is what caused the pikepdf test failures) and also makes it possible to use the C API to do a number of things that could previously only be done with the C++ API. Bottom line: this is a much better version to be in an LTS release than 10.5.0. ** Summary changed: - qpdf 10.6.1 not syncing? + qpdf 10.6.2 not syncing (freeze exception?) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.2 not syncing (freeze exception?) Status in qpdf package in Ubuntu: New Bug description: I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as far as I can see, automatic sync freeze has not yet happened. There are some major changes in 10.6 that I would really like to get into Ubuntu because they include transitional code to help users migrate to qpdf 11. Is there something that needs to happen for this to sync? I don't want to miss the window. At this time, there are test failures in pikepdf because of a bug fix to qpdf in transcoding. We have determined that these test failures don't indicate a serious problem with either qpdf or pikepdf -- they are basically that pikepdf had some tests that were depending on incorrect qpdf functionality. For details, see https://github.com/pikepdf/pikepdf/issues/303 The pikepdf author is aware of the upcoming Ubuntu 22.04 freeze and is trying to get a fix in in time, but I'm hoping we can avoid getting into a situation where we miss the bus. There's a chance I might release 10.6.2 to fix one other minor transcoding issue, but I don't consider the issue to be important enough to justify a release. But if the pikepdf author wants a release to simplify his testing, I will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Bug#1006123: CI failures with pikepdf 5 and qpdf 10.6.2 (tomli)
Package: pikepdf Version: 5.0.0+dfsg-1 X-Debbugs-CC: q...@debian.org Still getting errors here: https://ci.debian.net/data/autopkgtest/testing/amd64/p/pikepdf/19355172/log.gz apparently because of tomli not being found. Is this a pikepdf packaging issue or something about how the test is being run? I'll admit to not being aware of how autopkgtest is set up. I've looked through the material but I have not taken the time to fully understand how it works.
Bug#1005766: alert to upstream bug report on pikepdf test failures
I have released qpdf 10.6.2, and a new pikepdf should be coming out imminently as well. This gets us back in sync -- the new pikepdf tests pass against 10.6.2.
[Desktop-packages] [Bug 1960924] Re: qpdf 10.6.1 not syncing?
It helps. Thanks. I just released 10.6.2, and pikepdf 5.0 is also being released hopefully today to get the two back in sync. Hopefully no further manual action will be required. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.1 not syncing? Status in qpdf package in Ubuntu: New Bug description: I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as far as I can see, automatic sync freeze has not yet happened. There are some major changes in 10.6 that I would really like to get into Ubuntu because they include transitional code to help users migrate to qpdf 11. Is there something that needs to happen for this to sync? I don't want to miss the window. At this time, there are test failures in pikepdf because of a bug fix to qpdf in transcoding. We have determined that these test failures don't indicate a serious problem with either qpdf or pikepdf -- they are basically that pikepdf had some tests that were depending on incorrect qpdf functionality. For details, see https://github.com/pikepdf/pikepdf/issues/303 The pikepdf author is aware of the upcoming Ubuntu 22.04 freeze and is trying to get a fix in in time, but I'm hoping we can avoid getting into a situation where we miss the bus. There's a chance I might release 10.6.2 to fix one other minor transcoding issue, but I don't consider the issue to be important enough to justify a release. But if the pikepdf author wants a release to simplify his testing, I will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1960924] Re: qpdf 10.6.1 not syncing?
It helps. Thanks. I just released 10.6.2, and pikepdf 5.0 is also being released hopefully today to get the two back in sync. Hopefully no further manual action will be required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.1 not syncing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1960924] Re: qpdf 10.6.1 not syncing?
There will definitely be a 10.6.2 in the next day or two. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.1 not syncing? Status in qpdf package in Ubuntu: New Bug description: I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as far as I can see, automatic sync freeze has not yet happened. There are some major changes in 10.6 that I would really like to get into Ubuntu because they include transitional code to help users migrate to qpdf 11. Is there something that needs to happen for this to sync? I don't want to miss the window. At this time, there are test failures in pikepdf because of a bug fix to qpdf in transcoding. We have determined that these test failures don't indicate a serious problem with either qpdf or pikepdf -- they are basically that pikepdf had some tests that were depending on incorrect qpdf functionality. For details, see https://github.com/pikepdf/pikepdf/issues/303 The pikepdf author is aware of the upcoming Ubuntu 22.04 freeze and is trying to get a fix in in time, but I'm hoping we can avoid getting into a situation where we miss the bus. There's a chance I might release 10.6.2 to fix one other minor transcoding issue, but I don't consider the issue to be important enough to justify a release. But if the pikepdf author wants a release to simplify his testing, I will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1960924] Re: qpdf 10.6.1 not syncing?
There will definitely be a 10.6.2 in the next day or two. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.1 not syncing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1960924] [NEW] qpdf 10.6.1 not syncing?
Public bug reported: I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as far as I can see, automatic sync freeze has not yet happened. There are some major changes in 10.6 that I would really like to get into Ubuntu because they include transitional code to help users migrate to qpdf 11. Is there something that needs to happen for this to sync? I don't want to miss the window. At this time, there are test failures in pikepdf because of a bug fix to qpdf in transcoding. We have determined that these test failures don't indicate a serious problem with either qpdf or pikepdf -- they are basically that pikepdf had some tests that were depending on incorrect qpdf functionality. For details, see https://github.com/pikepdf/pikepdf/issues/303 The pikepdf author is aware of the upcoming Ubuntu 22.04 freeze and is trying to get a fix in in time, but I'm hoping we can avoid getting into a situation where we miss the bus. There's a chance I might release 10.6.2 to fix one other minor transcoding issue, but I don't consider the issue to be important enough to justify a release. But if the pikepdf author wants a release to simplify his testing, I will do it. ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.1 not syncing? Status in qpdf package in Ubuntu: New Bug description: I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as far as I can see, automatic sync freeze has not yet happened. There are some major changes in 10.6 that I would really like to get into Ubuntu because they include transitional code to help users migrate to qpdf 11. Is there something that needs to happen for this to sync? I don't want to miss the window. At this time, there are test failures in pikepdf because of a bug fix to qpdf in transcoding. We have determined that these test failures don't indicate a serious problem with either qpdf or pikepdf -- they are basically that pikepdf had some tests that were depending on incorrect qpdf functionality. For details, see https://github.com/pikepdf/pikepdf/issues/303 The pikepdf author is aware of the upcoming Ubuntu 22.04 freeze and is trying to get a fix in in time, but I'm hoping we can avoid getting into a situation where we miss the bus. There's a chance I might release 10.6.2 to fix one other minor transcoding issue, but I don't consider the issue to be important enough to justify a release. But if the pikepdf author wants a release to simplify his testing, I will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1960924] [NEW] qpdf 10.6.1 not syncing?
Public bug reported: I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as far as I can see, automatic sync freeze has not yet happened. There are some major changes in 10.6 that I would really like to get into Ubuntu because they include transitional code to help users migrate to qpdf 11. Is there something that needs to happen for this to sync? I don't want to miss the window. At this time, there are test failures in pikepdf because of a bug fix to qpdf in transcoding. We have determined that these test failures don't indicate a serious problem with either qpdf or pikepdf -- they are basically that pikepdf had some tests that were depending on incorrect qpdf functionality. For details, see https://github.com/pikepdf/pikepdf/issues/303 The pikepdf author is aware of the upcoming Ubuntu 22.04 freeze and is trying to get a fix in in time, but I'm hoping we can avoid getting into a situation where we miss the bus. There's a chance I might release 10.6.2 to fix one other minor transcoding issue, but I don't consider the issue to be important enough to justify a release. But if the pikepdf author wants a release to simplify his testing, I will do it. ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.1 not syncing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Bug#1005766: alert to upstream bug report on pikepdf test failures
Package: pikepdf Version: 4.2.0+dfsg-1 X-Debbugs-CC: q...@debian.org The current version of pikepdf has some failed tests that are preventing qpdf 10.6.1 from transitioning. I just wanted to make you aware of this upstream bug report: https://github.com/pikepdf/pikepdf/issues/303 Short version: qpdf 10.6 fixed a character encoding bug for a few obscure characters. This changed qpdf's response to some calls that were being made in pikepdf's tests. A fix to pikepdf is forthcoming that will adjust the error handling behavior based on a runtime check, but in the meantime, the failures are not actually a regression but are instead tests that are failing because they were relying on incorrect qpdf behavior. I'm hoping a new pikepdf version will come out with this fix soon so just uploading a new pikepdf will unblock the qpdf transition. Since debian maintenance of pikepdf has generally been very responsive, I won't plan on creating another issue about it unless you would like to say something when pikepdf is updated. Thanks!
Bug#1004159: Add a qpdf-doc package
On Fri, Jan 21, 2022, at 5:13 PM, 積丹尼 Dan Jacobson wrote: > Package: qpdf > Version: 10.5.0-1 > Severity: wishlist > > Add a qpdf-doc package, so the documentation can be viewed offline, > without needing to obtain an Internet connection, once one realizes the > full documentation is missing. This is something I would like to do and would have done except generating qpdf document requires newer versions of sphinx and sphinx_rtd_theme than are present in debian at the moment as well as in Ubuntu versions that I support through my ppa, so building the documentation from source and following the policy regarding shared javascript doesn't work within the debian packaging ecosystem at this time. This is most likely a problem that will solve itself if I wait long enough. Alternatively, I may be able to go back to packaging a pre-built PDF version of the documentation. In the meantime, I would refer you to the /usr/share/doc/qpdf/README-doc.txt which includes instructions on how to download offline documentation. I suppose another option would be to follow the lead of the DVD Codec people and provide a script that would download the offline documentation. I'm open to other suggestions. --Jay P.S. I feel honored to have randomly gotten a bug whose number ends with 4 consecutive pi digits that fall so early in pi.
Bug#996792: pikepdf: blocking qpdf from transitioning
Package: pikepdf Version: 1.17.3+dfsg-5 X-Debbugs-CC: q...@debian.org See https://qa.debian.org/excuses.php?package=qpdf autopkgtest for pikepdf is blocking qpdf 10.3.2 from transitioning to testing. The version of pikepdf in debian is very old. Pikepdf is at version 3.1.0. The version packaged for debian is 1.17.3. I think pikepdf should be removed from debian or upgraded. It's not really fair for such an old version of pikepdf to be blocking the transition of qpdf anymore. Please let me know if there's anything I can do to help the situation. --Jay Berkenbilt (a.k.a. q...@debian.org)
[Bug 1918729] Re: please sync qpdf 10.3.1-1 from debian experimental
Makes sense. Hopefully ubuntu is looking either at only the supported architectures or only the ones that it uses itself. In the former case, looks like everything's built but mips64el which appears to be building now, so hopefully it's not much longer. If I'm lucky, 10.2.0 and 10.3.0 won't make it into anyone's releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918729 Title: please sync qpdf 10.3.1-1 from debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1918729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1918729] Re: please sync qpdf 10.3.1-1 from debian experimental
Makes sense. Hopefully ubuntu is looking either at only the supported architectures or only the ones that it uses itself. In the former case, looks like everything's built but mips64el which appears to be building now, so hopefully it's not much longer. If I'm lucky, 10.2.0 and 10.3.0 won't make it into anyone's releases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1918729 Title: please sync qpdf 10.3.1-1 from debian experimental Status in qpdf package in Ubuntu: In Progress Bug description: 10.3.1 includes a very small but important fix to a bug that would cause qpdf 10.3.0 to reject certain valid files when splitting pages. I also added a check for exceptions that will make future bugs of this type (if any) just generate warnings instead of blocking the whole operations in hopes of not needing to do any emergency releases any time soon even if this wasn't the "last bug." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1918729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1918729] Re: please sync qpdf 10.3.1-1 from debian experimental
Thanks. I don't know if there's a way for me to know when your utility can find it. I wait until I get the email from debian that the package has been accepted before posting this, but apparently that's not quite enough. Eventually debian will release, Ubuntu will release, and automatic syncs will resume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918729 Title: please sync qpdf 10.3.1-1 from debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1918729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1918729] Re: please sync qpdf 10.3.1-1 from debian experimental
Thanks. I don't know if there's a way for me to know when your utility can find it. I wait until I get the email from debian that the package has been accepted before posting this, but apparently that's not quite enough. Eventually debian will release, Ubuntu will release, and automatic syncs will resume. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1918729 Title: please sync qpdf 10.3.1-1 from debian experimental Status in qpdf package in Ubuntu: In Progress Bug description: 10.3.1 includes a very small but important fix to a bug that would cause qpdf 10.3.0 to reject certain valid files when splitting pages. I also added a check for exceptions that will make future bugs of this type (if any) just generate warnings instead of blocking the whole operations in hopes of not needing to do any emergency releases any time soon even if this wasn't the "last bug." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1918729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1918729] [NEW] please sync qpdf 10.3.1-1 from debian experimental
Public bug reported: 10.3.1 includes a very small but important fix to a bug that would cause qpdf 10.3.0 to reject certain valid files when splitting pages. I also added a check for exceptions that will make future bugs of this type (if any) just generate warnings instead of blocking the whole operations in hopes of not needing to do any emergency releases any time soon even if this wasn't the "last bug." ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918729 Title: please sync qpdf 10.3.1-1 from debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1918729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1918729] [NEW] please sync qpdf 10.3.1-1 from debian experimental
Public bug reported: 10.3.1 includes a very small but important fix to a bug that would cause qpdf 10.3.0 to reject certain valid files when splitting pages. I also added a check for exceptions that will make future bugs of this type (if any) just generate warnings instead of blocking the whole operations in hopes of not needing to do any emergency releases any time soon even if this wasn't the "last bug." ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1918729 Title: please sync qpdf 10.3.1-1 from debian experimental Status in qpdf package in Ubuntu: New Bug description: 10.3.1 includes a very small but important fix to a bug that would cause qpdf 10.3.0 to reject certain valid files when splitting pages. I also added a check for exceptions that will make future bugs of this type (if any) just generate warnings instead of blocking the whole operations in hopes of not needing to do any emergency releases any time soon even if this wasn't the "last bug." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1918729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917906] Re: please sync qpdf 10.3.0-1 from debian experimental
This is a bug-fix release. It contains only two changes: correction of a very old bug (from 2.3.0 released in 2011) involving references to replaced objects and a more significant series of fixes to the form field enhancements in 10.2.0, which turned out to be incorrect and were creating PDF files that were missing fields in the document-level form dictionary. It is called 10.3.0 because I had to add new methods to the public API, and qpdf uses semantic versioning. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1917906 Title: please sync qpdf 10.3.0-1 from debian experimental Status in qpdf package in Ubuntu: Incomplete Bug description: Sorry to do this again so soon, but I released qpdf 10.3.0 and uploaded to debian experimental. I have gotten the email from debian indicating that the package has been accepted, and it is visible on qa.debian.org, so hopefully it's "there" for purposes of doing the sync. If not, give it a few hours. :-) Thanks for helping to keep qpdf updated in Ubuntu! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1917906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1917906] Re: please sync qpdf 10.3.0-1 from debian experimental
This is a bug-fix release. It contains only two changes: correction of a very old bug (from 2.3.0 released in 2011) involving references to replaced objects and a more significant series of fixes to the form field enhancements in 10.2.0, which turned out to be incorrect and were creating PDF files that were missing fields in the document-level form dictionary. It is called 10.3.0 because I had to add new methods to the public API, and qpdf uses semantic versioning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917906 Title: please sync qpdf 10.3.0-1 from debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1917906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917906] [NEW] please sync qpdf 10.3.0-1 from debian experimental
Public bug reported: Sorry to do this again so soon, but I released qpdf 10.3.0 and uploaded to debian experimental. I have gotten the email from debian indicating that the package has been accepted, and it is visible on qa.debian.org, so hopefully it's "there" for purposes of doing the sync. If not, give it a few hours. :-) Thanks for helping to keep qpdf updated in Ubuntu! ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917906 Title: please sync qpdf 10.3.0-1 from debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1917906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1917906] [NEW] please sync qpdf 10.3.0-1 from debian experimental
Public bug reported: Sorry to do this again so soon, but I released qpdf 10.3.0 and uploaded to debian experimental. I have gotten the email from debian indicating that the package has been accepted, and it is visible on qa.debian.org, so hopefully it's "there" for purposes of doing the sync. If not, give it a few hours. :-) Thanks for helping to keep qpdf updated in Ubuntu! ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1917906 Title: please sync qpdf 10.3.0-1 from debian experimental Status in qpdf package in Ubuntu: New Bug description: Sorry to do this again so soon, but I released qpdf 10.3.0 and uploaded to debian experimental. I have gotten the email from debian indicating that the package has been accepted, and it is visible on qa.debian.org, so hopefully it's "there" for purposes of doing the sync. If not, give it a few hours. :-) Thanks for helping to keep qpdf updated in Ubuntu! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1917906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1916658] Re: please sync qpdf 10.2.0-1 from debian experimental
Great, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916658 Title: please sync qpdf 10.2.0-1 from debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1916658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1916658] Re: please sync qpdf 10.2.0-1 from debian experimental
Great, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1916658 Title: please sync qpdf 10.2.0-1 from debian experimental Status in qpdf package in Ubuntu: Fix Committed Bug description: Since debian is in freeze, I uploaded qpdf-10.2.0-1 to experimental. I know unstable syncs automatically to Ubuntu, but I'm not sure I have to request a sync from experimental or if this is the way to do it. In any case, it would be great if we can pull qpdf-10.2.0-1 from experimental into the current release. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1916658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1916658] Re: please sync qpdf 10.2.0-1 from debian experimental
I just uploaded it. I can ask again in a couple of days. I'll put a reminder for tomorrow to check status. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916658 Title: please sync qpdf 10.2.0-1 from debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1916658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1916658] Re: please sync qpdf 10.2.0-1 from debian experimental
I just uploaded it. I can ask again in a couple of days. I'll put a reminder for tomorrow to check status. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1916658 Title: please sync qpdf 10.2.0-1 from debian experimental Status in qpdf package in Ubuntu: New Bug description: Since debian is in freeze, I uploaded qpdf-10.2.0-1 to experimental. I know unstable syncs automatically to Ubuntu, but I'm not sure I have to request a sync from experimental or if this is the way to do it. In any case, it would be great if we can pull qpdf-10.2.0-1 from experimental into the current release. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1916658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1916658] [NEW] please sync qpdf 10.2.0-1 from debian experimental
Public bug reported: Since debian is in freeze, I uploaded qpdf-10.2.0-1 to experimental. I know unstable syncs automatically to Ubuntu, but I'm not sure I have to request a sync from experimental or if this is the way to do it. In any case, it would be great if we can pull qpdf-10.2.0-1 from experimental into the current release. Thanks! ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916658 Title: please sync qpdf 10.2.0-1 from debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1916658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1916658] [NEW] please sync qpdf 10.2.0-1 from debian experimental
Public bug reported: Since debian is in freeze, I uploaded qpdf-10.2.0-1 to experimental. I know unstable syncs automatically to Ubuntu, but I'm not sure I have to request a sync from experimental or if this is the way to do it. In any case, it would be great if we can pull qpdf-10.2.0-1 from experimental into the current release. Thanks! ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1916658 Title: please sync qpdf 10.2.0-1 from debian experimental Status in qpdf package in Ubuntu: New Bug description: Since debian is in freeze, I uploaded qpdf-10.2.0-1 to experimental. I know unstable syncs automatically to Ubuntu, but I'm not sure I have to request a sync from experimental or if this is the way to do it. In any case, it would be great if we can pull qpdf-10.2.0-1 from experimental into the current release. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1916658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Bug#981465: pikepdf is still blocking qpdf
Here's an additional patch. This time I tested it against the actual debian source package. Just drop this into debian/patches and append to debian/patches/series, and you should be good to go. Thanks. As an added bonus, I also verified that this is clean with what will soon be qpdf 10.2. commit 7ca375cb6ff82011d716da1614ef5721a97f91b0 Author: James R. Barlow Date: Wed Jan 6 03:39:50 2021 -0800 Fix test_tokenfilter_is_abstract Index: pikepdf-1.17.3+dfsg/tests/test_filters.py === --- pikepdf-1.17.3+dfsg.orig/tests/test_filters.py +++ pikepdf-1.17.3+dfsg/tests/test_filters.py @@ -88,4 +88,3 @@ def test_tokenfilter_is_abstract(pal): page = pikepdf.Page(pal.pages[0]) with pytest.raises((RuntimeError, pikepdf.PdfError)): page.get_filtered_contents(pikepdf.TokenFilter()) -assert 'Tried to call pure virtual' in pal.get_warnings()[0]
Bug#981465: pikepdf is still blocking qpdf
Package: pikepdf Version: 1.17.3+dfsg-3 X-Debbugs-CC: q...@debian.org Please see https://ci.debian.net/data/autopkgtest/testing/amd64/p/pikepdf/10125896/log.gz If needed, I can try to prepare a patch, but I think my previous patch already included the fix for this issue. Please let me know if you need me to do something to get this unstuck. Thanks.
Bug#980426: old pikepdf is blocking qpdf transition
On Tue, Jan 19, 2021, at 4:06 PM, Sean Whitton wrote: > control: tag -1 + patch pending > > Hello, > > On Tue 19 Jan 2021 at 09:39AM -05, Jay Berkenbilt wrote: > > > Here's a patch that applies cleanly against upstream v1.17.3 after > > which the resulting pikepdf builds and passes its test with qpdf > > 10.1. Please let me know if this is sufficient. I put some comments at > > the top of the patch citing original commits in case you want to do > > the DEP-3 thing. > > Well, several of those we are already carrying in d/patches :) Yeah, if it had taken me more than a few minutes to gather this up, I would have started with the debian package. I probably should have done that. :-) > Uploading shortly. Thanks for investigating! That's great. Thanks for responding so quickly. --Jay
Bug#980426: old pikepdf is blocking qpdf transition
tags 980426 +patch
thanks
Here's a patch that applies cleanly against upstream v1.17.3 after which the
resulting pikepdf builds and passes its test with qpdf 10.1. Please let me know
if this is sufficient. I put some comments at the top of the patch citing
original commits in case you want to do the DEP-3 thing.
--JayPatch created as follows:
cp /dev/null /tmp/a.patch
git show 7ac9b058104219b26747f3fc9761ac6b3c037402 >> /tmp/a.patch
git show 5394b7855eb87f637316432b2b597294adcb974e >> /tmp/a.patch
git show fe4b568ac88ba551458578613b013ac17edf5c4e -- tests/test_filters.py >> /tmp/a.patch
git show 7ca375cb6ff82011d716da1614ef5721a97f91b0 >> /tmp/a.patch
commit 7ac9b058104219b26747f3fc9761ac6b3c037402
Author: James R. Barlow
Date: Mon Jan 4 20:21:51 2021 -0800
Fix externalize_inline_images for qpdf 10.1.0
diff --git a/src/qpdf/page.cpp b/src/qpdf/page.cpp
index 64b641d..6f70d20 100644
--- a/src/qpdf/page.cpp
+++ b/src/qpdf/page.cpp
@@ -106,7 +106,10 @@ void init_page(py::module_& m)
.def("_get_mediabox", ::getMediaBox)
.def("_get_cropbox", ::getCropBox)
.def("_get_trimbox", ::getTrimBox)
-.def("externalize_inline_images", ::externalizeInlineImages,
+.def("externalize_inline_images",
+[](QPDFPageObjectHelper , size_t min_size = 0) {
+return poh.externalizeInlineImages(min_size);
+},
py::arg("min_size") = 0,
R"~~~(
Convert inlines image to normal (external) images.
commit 5394b7855eb87f637316432b2b597294adcb974e
Author: James R. Barlow
Date: Tue Aug 18 00:36:46 2020 -0700
Fix potential undefined behavior in memoryview
Apply patch based on pybind11 PR2223 to change how Python
memory views on C++ buffers are declared - avoids a possible use-
after-free in Python's code.
This change is not in a released pybind11 version yet so we are
pulling it forward.
diff --git a/src/qpdf/pipeline.cpp b/src/qpdf/pipeline.cpp
index 1856987..8a4fe79 100644
--- a/src/qpdf/pipeline.cpp
+++ b/src/qpdf/pipeline.cpp
@@ -22,6 +22,7 @@
#include "pikepdf.h"
#include "pipeline.h"
+#include "utils.h"
void Pl_PythonOutput::write(unsigned char *buf, size_t len)
@@ -29,8 +30,7 @@ void Pl_PythonOutput::write(unsigned char *buf, size_t len)
py::gil_scoped_acquire gil;
ssize_t so_far = 0;
while (len > 0) {
-py::buffer_info buffer(buf, len);
-py::memoryview view_buffer(buffer);
+py::memoryview view_buffer = memoryview_from_memory(buf, len);
py::object result = this->stream.attr("write")(view_buffer);
try {
so_far = result.cast();
diff --git a/src/qpdf/qpdf_inputsource.h b/src/qpdf/qpdf_inputsource.h
index 4a96f6b..8ec6a55 100644
--- a/src/qpdf/qpdf_inputsource.h
+++ b/src/qpdf/qpdf_inputsource.h
@@ -82,8 +82,7 @@ public:
{
py::gil_scoped_acquire gil;
-py::buffer_info buffer_info(buffer, length);
-py::memoryview view_buffer_info(buffer_info);
+py::memoryview view_buffer_info = memoryview_from_memory(buffer, length);
this->last_offset = this->tell();
py::object result = this->stream.attr("readinto")(view_buffer_info);
diff --git a/src/qpdf/utils.cpp b/src/qpdf/utils.cpp
index bf189f6..36769ca 100644
--- a/src/qpdf/utils.cpp
+++ b/src/qpdf/utils.cpp
@@ -46,3 +46,20 @@
}
#endif
+
+// Copied from pybind11 master branch (pre-2.6), can remove when we require
+// pybind11 v2.6 and replace with py::memoryview::from_memory
+py::memoryview memoryview_from_memory(void *mem, ssize_t size, bool readonly)
+{
+PyObject* ptr = PyMemoryView_FromMemory(
+reinterpret_cast(mem), size,
+(readonly) ? PyBUF_READ : PyBUF_WRITE);
+if (!ptr)
+py::pybind11_fail("Could not allocate memoryview object!");
+return py::reinterpret_steal(ptr);
+}
+
+py::memoryview memoryview_from_memory(const void *mem, ssize_t size)
+{
+return memoryview_from_memory(const_cast(mem), size, true);
+}
diff --git a/src/qpdf/utils.h b/src/qpdf/utils.h
index 9f6a411..f26c5bd 100644
--- a/src/qpdf/utils.h
+++ b/src/qpdf/utils.h
@@ -17,3 +17,6 @@ inline bool str_startswith(T haystack, S needle)
{
return std::string(haystack).rfind(needle, 0) == 0;
}
+
+py::memoryview memoryview_from_memory(void *mem, ssize_t size, bool readonly = false);
+py::memoryview memoryview_from_memory(const void *mem, ssize_t size);
commit fe4b568ac88ba551458578613b013ac17edf5c4e
Author: James R. Barlow
Date: Wed Jan 6 00:22:16 2021 -0800
libqpdf 10.1.0 raises different exception
The different errors are acceptable to us; actually they are more
correct than the original behavior.
diff --git a/tests/test_filters.py b/tests/test_filters.py
index 90c0ca5..36d2a4c 100644
--- a/tests/test_filters.py
+++ b/tests/test_filters.py
@@ -74,19 +74,18 @@ class FilterInvalid(pikepdf.TokenFilter):
def test_invalid_handle_token(pal):
page =
Bug#980426: old pikepdf is blocking qpdf transition
(pardon the duplicate -- I accidentally did reply to sender instead of reply all) On Mon, Jan 18, 2021, at 7:55 PM, Sean Whitton wrote: > Dear Jay, > > On Mon 18 Jan 2021 at 05:35PM -05, Jay Berkenbilt wrote: > > > Package: pikepdf > > Version: 1.17.3+dfsg-2 > > X-Debbugs-CC: q...@debian.org > > > > This is a request to please upload the latest pikepdf to sid. Right now, > > qpdf 10.1.0 is not able to transition to testing because autopkgtest is > > failing because of a regression in pikepdf. The problem is actually in > > pikepdf, and the pikepdf author resolved the issue within 24 hours of my > > release of qpdf 10.1.0. > > > > Reference: https://qa.debian.org/excuses.php?package=qpdf > > > > Please let me know if any additional information is required. (I am the > > debian maintainer and upstream author of qpdf.) > > > > Also please let me know if you would like me to do an NMU. I can, but I'd > > prefer not to have to do it. Thanks. > > There are two blockers: > > 1) we're in the transitions freeze, so updating pikepdf would need >permission from the release team Oops, I forgot that was already going on. > 2) pikepdf has undergone a license change, and someone on the Debian >side needs to look over upstream's work in contacting all >copyright holders and having them okay it, and d/copyright needs >updating. > > Additionally, new releases of pikepdf typically involve a lot of work > updating d/copyright for new test resources. > > So, perhaps we could just backport the fix? Sure, I think that would work. I will ask upstream about it and/or try to come up with a patch. I know there were two small fixes, both simple. I'll let you know as soon as I can. --Jay
Bug#980426: old pikepdf is blocking qpdf transition
Package: pikepdf Version: 1.17.3+dfsg-2 X-Debbugs-CC: q...@debian.org This is a request to please upload the latest pikepdf to sid. Right now, qpdf 10.1.0 is not able to transition to testing because autopkgtest is failing because of a regression in pikepdf. The problem is actually in pikepdf, and the pikepdf author resolved the issue within 24 hours of my release of qpdf 10.1.0. Reference: https://qa.debian.org/excuses.php?package=qpdf Please let me know if any additional information is required. (I am the debian maintainer and upstream author of qpdf.) Also please let me know if you would like me to do an NMU. I can, but I'd prefer not to have to do it. Thanks.
Bug#979947: qpdf: can't read password from stdin
The @ syntax doesn't work in the middle of an argument. You can put --password=something in a file and use @file in place of the whole argument, or you can use @- and type --password=something I'll admit that it's a bit confusingly worded. I will clarify the documentation about this and see if it's worth handling reading the password from a file as a special case (e.g. --password-file=- or --password-file=file), but no guarantees. On Tue, Jan 12, 2021, at 5:50 AM, Jakub Wilk wrote: > Package: qpdf > Version: 10.1.0-1 > > The QPDF Manual reads: > > >--password=password > > > >Specifies a password for accessing encrypted files. Note that you > >can use @filename or @- as described above to put the password in a > >file or pass it via standard input so you can avoid specifying it on > >the command line. > > So I tried: > >$ qpdf --decrypt --password=@- foo.pdf bar.pdf > > But qpdf didn't read anything from stdin. > > I also tried: > >$ qpdf --decrypt --password @- foo.pdf bar.pdf > > This time qpdf read stuff from stdin, but then it died with: > >qpdf: --password must be given as --password=password > > > -- System Information: > Architecture: i386 > > Versions of packages qpdf depends on: > ii libc6 2.31-9 > ii libgcc-s1 10.2.1-6 > ii libqpdf28 10.1.0-1 > ii libstdc++6 10.2.1-6 > > -- > Jakub Wilk >
Bug#956400: Processed: retitle 956400 to qpdf: FTBFS on multiple 32-bit architectures, needs libatomic
Oops, I fixed this, but I made a cut and paste error and "Closed" the wrong bug number in the changelog. I wlll clean it up tomorrow by removing the fixed version from the wrong bug and adding it to the right one. On Fri, Apr 10, 2020, at 1:39 PM, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > retitle 956400 qpdf: FTBFS on multiple 32-bit architectures, needs libatomic > Bug #956400 [src:qpdf] pdf: FTBFS on multiple 32-bit architectures, needs > libatomic > Changed Bug title to 'qpdf: FTBFS on multiple 32-bit architectures, needs > libatomic' from 'pdf: FTBFS on multiple 32-bit architectures, needs > libatomic'. > > thanks > Stopping processing here. > > Please contact me if you need assistance. > -- > 956400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956400 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#956400: Processed: retitle 956400 to qpdf: FTBFS on multiple 32-bit architectures, needs libatomic
Oops, I fixed this, but I made a cut and paste error and "Closed" the wrong bug number in the changelog. I wlll clean it up tomorrow by removing the fixed version from the wrong bug and adding it to the right one. On Fri, Apr 10, 2020, at 1:39 PM, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > retitle 956400 qpdf: FTBFS on multiple 32-bit architectures, needs libatomic > Bug #956400 [src:qpdf] pdf: FTBFS on multiple 32-bit architectures, needs > libatomic > Changed Bug title to 'qpdf: FTBFS on multiple 32-bit architectures, needs > libatomic' from 'pdf: FTBFS on multiple 32-bit architectures, needs > libatomic'. > > thanks > Stopping processing here. > > Please contact me if you need assistance. > -- > 956400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956400 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Re: Should qpdf depend on gnutls?
Yeah, that's what what I decided to do. Thanks. On Thu, Apr 9, 2020, at 2:08 PM, Florian Weimer wrote: > * Jay Berkenbilt: > > > I'm about to release qpdf 10. Someone contributed an openssl crypto > > provider. Do you think I should build with the qpdf packages for > > debian with 1) only gnutls, 2) only openssl, or 3) both gnutls and > > openssl? Option 3 allows users to select at runtime but makes qpdf > > dependent on both packages. I notice that systemd also depends on > > openssl. My impulse is to go with option 1 (gnutls only) because I > > really don't see any advantage in the OS package letting users > > choose at runtime which crypto to use, but including both cryptos > > probably doesn't ultimately affect what gets installed on anyone's > > system since openssl is basically always going to be there. > > This seems to be more of a query for debian-devel, to be honest. > > Two packages do not seem particularly useful to me. Since apt depends > on libgnutls30, I don't see how an OpenSSL backend for qpdf could > minimize installation size. This suggests to me that you should stick > with GNUTLS for Debian. >
Re: Should qpdf depend on gnutls?
I'm about to release qpdf 10. Someone contributed an openssl crypto provider. Do you think I should build with the qpdf packages for debian with 1) only gnutls, 2) only openssl, or 3) both gnutls and openssl? Option 3 allows users to select at runtime but makes qpdf dependent on both packages. I notice that systemd also depends on openssl. My impulse is to go with option 1 (gnutls only) because I really don't see any advantage in the OS package letting users choose at runtime which crypto to use, but including both cryptos probably doesn't ultimately affect what gets installed on anyone's system since openssl is basically always going to be there. Opinions welcome. Thanks! On Sun, Nov 10, 2019, at 9:10 PM, Jay Berkenbilt wrote: > Okay, thanks for all the response, public and private. There seems to be > broad consensus to use the gnutls crypto and disable the native one, so > that's what I'll do. Appreciate the advice! > > --Jay > > On Sun, Nov 10, 2019 at 2:05 PM Moritz Mühlenhoff wrote: >> On Sat, Nov 09, 2019 at 07:10:44PM -0500, Jay Berkenbilt wrote: >> > I am the upstream author and the debian maintainer of qpdf. >> > >> > At the request of RedHat, I have made an enhancement to qpdf that >> > allows an external library to be used for crypto functions rather than >> > using qpdf's native crypto implementations. The qpdf library includes >> > code to compute hashes with md5 and sha2 (256, 384, and 512) as well >> > as encryption functions for rc4 and aes256 with and without CBC. >> > Disabling insecure crypto is not a practical option because of the way >> > these things are used in the PDF spec, but it is possible create PDFs >> > that don't use insecure crypto by just using 256-bit encryption. >> > >> > I can build qpdf 9.1 for Debian in one of three ways: 1) use only the >> > native crypto as in all previous releases, thus avoiding a dependency >> > on gnutls; 2) build only the gnutls crypto provider thus causing a >> > dependency on gnutls but eliminating the native crypto entirely; or 3) >> > building both crypto providers, in which case gnutls will be used by >> > default, but developers and end users will have the ability to select >> > the native crypto provider at runtime if desired. >> > >> > Do you have an opinion about which way I should go? I believe RHEL and >> > Fedora are going to use the second option of building with only gnutls >> > and dropping native crypto, but I have also enjoyed the fact that qpdf >> > has so few build dependencies. It is possible that a future version of >> > qpdf may support digital signature, in which case I will definitely >> > have to add either openssl or gnutls as a dependency. >> >> I'd recommend to go with 2); there's a lot of value in using a common / >> scrutinised crypto library over a custom implementation and for all >> practical purposes gnutls would not be an additional dep as systemd >> already pulls it in on virtually every Linux system these days. >> >> Cheers, >> Moritz >>
Accepted qpdf 9.1.1-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 26 Jan 2020 21:08:43 -0500 Source: qpdf Architecture: source Version: 9.1.1-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Changes: qpdf (9.1.1-1) unstable; urgency=medium . * New upstream release. * Update standards to 4.5.0. No changes required. Checksums-Sha1: 0a606af11f487728e15c39e0013d051da4ff8c31 2078 qpdf_9.1.1-1.dsc 8176a6ee6257cd66817bf1aacbab27854f3b1def 18312457 qpdf_9.1.1.orig.tar.gz ed6ce133627bbc83e100daf936c39683858e0b52 833 qpdf_9.1.1.orig.tar.gz.asc 1e6267abd5d8a42aeffbeb982d441a6eec2894b6 13456 qpdf_9.1.1-1.debian.tar.xz 41bdc5c6dc6b0100d7d771a07a957de19b9663bc 7181 qpdf_9.1.1-1_amd64.buildinfo Checksums-Sha256: 956c8a473edd9602d20532814d05fa2cecc73f73b6de277465e9c3f47d2e41d0 2078 qpdf_9.1.1-1.dsc a2c6fc410ec45df0ca0996b039e00bb6f39cfc76d42d784b7ad7bc9e163f4236 18312457 qpdf_9.1.1.orig.tar.gz 287cabeb3f0555f29d626e8e3d64c51a64a1eb645afcea93a183e0bf1e2aa55f 833 qpdf_9.1.1.orig.tar.gz.asc 39e01e0278d09d6570b326ffd790d288f4696e76e10cfaae2918ecb22d144797 13456 qpdf_9.1.1-1.debian.tar.xz d079b4375d5324bde4f68345551d4c6485bd8ba7c1aaef03c7299705368b97e5 7181 qpdf_9.1.1-1_amd64.buildinfo Files: 956aa876a69459fb0b83c3fdd5d60cb4 2078 libs optional qpdf_9.1.1-1.dsc 8a2ddc3bdf0671234a5651251a7e9da6 18312457 libs optional qpdf_9.1.1.orig.tar.gz 83fbf4ccc546c073164458ccda7a3408 833 libs optional qpdf_9.1.1.orig.tar.gz.asc 1f9f1a1a72b474c14a3a3f88e4274d30 13456 libs optional qpdf_9.1.1-1.debian.tar.xz 7dcb3b8291757d06b7cef109757fe128 7181 libs optional qpdf_9.1.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAl4uSB0PHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+SE8QAIQxZ15g2Qf1ORV05LjqD0bmXpHFfCd8KYT2 GyditqnhtufUWeE7CveSFf0cdarc44S/2ohz4PFqfMltiguj1yg1rvxPQA3w2M7g odxARWrJafjUJVYYa3eeHEWWSJaLH288xl7und3xFFf3tSOT/BTpZupPUNAK9kYQ nDBpvq4vpcVaaw6aQdRCDWFt0DZaluqI6wLYAmGaiIt2bYrbf4CpGtBKEHuYCpxe M6Zay0aVVPfPshOv1MOxipz9ie+EajyuV0fpjgTepFXzRqv17bKWPPRLRLNMbkLP m9YNvvbyXbDJTbjCHHeZ8f/3X0muSnCXpNMuJAJZ/C5h+MBGEAt0ShiYF5gNCKzX B8HxC1eKvlVKB5tRTGLHt56ukfJ0E3aJiQkPDwJrqJyvkPgxcfatqRujz1VlvvhQ tZgz8rQgqBQekendMdoojc1GVrPhe6t5pBm9GDm/hzqENL7pqvkOsAJhT+pGsqef DRluUikAwuEIPZLbGHOBaSys9MGAyVfgt5Sii91zw0kBKdaDhlOcunsSlf0t+stY Ga0FAR4GjVvwHCJkG7fGvFeDvjaC8Gyq1R82TzWvufTWyQyz/tm9YUuBdrWzEsuY PDTQ7zM3awpu2Op7RWNSVW242pD7Nr2LpDH8BCPLILSRZu9swtA0vhD2yfYPPplI 9kDMuMIU =Q4pY -END PGP SIGNATURE-
Accepted qpdf 9.1.0-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 17 Nov 2019 08:24:01 -0500 Source: qpdf Architecture: source Version: 9.1.0-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Changes: qpdf (9.1.0-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 6d55e75335deab8a5f655c6221fb6d49fd4e3c4b 2078 qpdf_9.1.0-1.dsc 14312ba0f30c86ae8cd71b4e82e2ec907734c9f1 18285597 qpdf_9.1.0.orig.tar.gz 9128d48ffc4a6ef60e12d1e9e280448c1c145e01 833 qpdf_9.1.0.orig.tar.gz.asc 23f67626d09afcd3731ddff0691ce685785694cc 13564 qpdf_9.1.0-1.debian.tar.xz f5c447e13872f72f0da5427eedd2706226da2445 7026 qpdf_9.1.0-1_amd64.buildinfo Checksums-Sha256: 72b45be96fbb1b82c33ee38e641a4d228307c6c23456d1819012face36e43ea8 2078 qpdf_9.1.0-1.dsc 3a7907f2e750336b9c97e67b6e806aca91ab537402ec080656d63940ed79 18285597 qpdf_9.1.0.orig.tar.gz fd5c47312162d2ad37fe25bd839cf088742eec1ba9ea0159601fc3c446178c91 833 qpdf_9.1.0.orig.tar.gz.asc 36be15881733d5a9f3f7c4a33e2ae2d0648c5a0bd2f4de79842f85f3462d86d9 13564 qpdf_9.1.0-1.debian.tar.xz 4ef4bb4823a945d370ca10b18532caa817ea92c52a5b20f095c6b75ab2e04313 7026 qpdf_9.1.0-1_amd64.buildinfo Files: 4cd392fa79c8a5f9631c6f50e24673c6 2078 libs optional qpdf_9.1.0-1.dsc 090d03ab179c281233f8240ade179d54 18285597 libs optional qpdf_9.1.0.orig.tar.gz 2b7263a7ffa47d829f544c3acde6367b 833 libs optional qpdf_9.1.0.orig.tar.gz.asc 5738fe0b9e7050c68d9a72b8613d5873 13564 libs optional qpdf_9.1.0-1.debian.tar.xz 576045761129be2969bb1210378c4690 7026 libs optional qpdf_9.1.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAl3RS1MPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+Qk0P/3gby3RUHmLf7S8w1K4ErZWUqXJOpjGfhqhC EpI9PLO65VZPTzoUsPN6GwABWMkI/Psm7lMGNoaRxP56YMDpO2BTskmOIJiGzM9W mPFm2ZH3DqAIFyfJ5XA9On05YIUSgleYATWMmv6YHrkkcQ9XBrNVUx/cbZBNSLov y27z2TW5Fo2TJzmMuPsMMBtBp6o/S2M490PFTEw1ANH+LuN89kN33O833yNNPVQX uhwYBGJXHMfnXh5JQ9e+WH0mU8cJjqA56lFMf2cc6mzvyZROfg1vXGuKURAmDk6O BJIGcvt8goYcG3qC8dOIvfJSlxHL79XYLlFzHAYd8v4Pvdq+7xOYGfCTi+iVYxg8 hQxsJQKYM02UAZa0bjxk3D+Fte8l8wR0NGL0E5+9634geUTlReHKF7wN35S/6agD l3G9QwUXMLIBuBgs5BzA5xkEQgVl8tDpYaB/AIUb4VF6xuxSd8OV+D83FcFjN2QV aJepQNZQZpDIjY8wYgEfIgoMM1NpT5oHZspKcozM+fAZDWAmFAybAZdIzF5og3Xl +kroiYL9Tho4sGdLKykaU3oJ7gqLW+CIrrWKkQNCjzOoB9ZPAu1P4DjXxHdDTgLU g5F4CKr82E59h1rB6mGSnIMsJy6LxkLbrKZybs5QtJ/E08xutvt6iINr1c6S9lzb 4Im5tEKQ =Le95 -END PGP SIGNATURE-
Accepted qpdf 9.1~rc1-1 (source) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Nov 2019 21:38:01 -0500 Source: qpdf Architecture: source Version: 9.1~rc1-1 Distribution: experimental Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Changes: qpdf (9.1~rc1-1) experimental; urgency=medium . * New upstream release. * Includes build dependency on gnutls to use gnutls crypto provider instead of qpdf's native crypto. Checksums-Sha1: c1b491a478f1f9fdbf39f8515b78200bda8c8bef 2098 qpdf_9.1~rc1-1.dsc 0fd1a4aeeca77ed4cd0bcb80bf3f42af4eb9b71e 18286346 qpdf_9.1~rc1.orig.tar.gz 126b131e8c510c52cf09aa03132b01bc48b33ac7 833 qpdf_9.1~rc1.orig.tar.gz.asc b35944a96815228087fd8d12d9d2abaf6f188b4b 13540 qpdf_9.1~rc1-1.debian.tar.xz 650e3883f62a513480a85719d164c3c7bb4957d2 7059 qpdf_9.1~rc1-1_amd64.buildinfo Checksums-Sha256: 7943e9c21d89bcf8f66435e3d98d7bc4c1fc77e5ce3b9448ffcb8dfe9b903429 2098 qpdf_9.1~rc1-1.dsc 91146eac53bd37832442f2fd2f9e8ed1966cc06889a3136403e30bf93c08fc57 18286346 qpdf_9.1~rc1.orig.tar.gz f5b2df7f3e392b9a793ef2f3a986233b88219d9cdde534ec775e14aa831b2be7 833 qpdf_9.1~rc1.orig.tar.gz.asc 94031258d85ddc76ce4ab3f4c220b34a278755139ca39ac57b1e1813b839c864 13540 qpdf_9.1~rc1-1.debian.tar.xz 32adf3492eec683dd00abb54a683fbfdd29ec185f7f26d6a93ec5faa5f67 7059 qpdf_9.1~rc1-1_amd64.buildinfo Files: 5fd562a8b96586db86aa5bfbbb7c90b3 2098 libs optional qpdf_9.1~rc1-1.dsc d6e8c5d7019b62bfe3e9fc7bb2162139 18286346 libs optional qpdf_9.1~rc1.orig.tar.gz b25b4d741fd08698a33b25e09c85d54f 833 libs optional qpdf_9.1~rc1.orig.tar.gz.asc c6142aba003bf3bea8f96c89ce47139e 13540 libs optional qpdf_9.1~rc1-1.debian.tar.xz 0887b117793bedfa11d568725589a721 7059 libs optional qpdf_9.1~rc1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAl3I1AQPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+UV8P/2nMmxJrNDRj0gqGhbQlVzA65MSAFFikHLOu aMkRODHC5Q24eTY+SK/MGnbRsCw5DUNE4/wxovUS07J9EK8nh8GNqA2OOlXUH0am Sj+nfw9BBKyNpXFsOK8htx7rNG8lqhZbmNtg7y9hlRYII1ku1XnSDA+n9rhcpcKO MmS9rKeeSU75nMapcuzaxZFKu8vsBbvlE19G1XKCDpu+LFbHGlDLPmPRJiCsqDvB rnvl4aElH/WBD/FDAgFKnuDoE9XjgxnJqRZZ1Gj2WzTa0Hrf1Ak3ihW0qBOlfV6s dUhfxKtn5waO0iwAPRipYoiL9+MjPNpVUq3ulDer3qE8GESmCsVSHTjYT4s/tdTB dQ7ykLr2om9L4WJG274PZeR0lIPWpIQh4gzIiPpCnLA9T+VtynbAn20zwutWai58 lbYiKz56ca9hvFxf49PygqTw1Nr5trrHTWVjYNPuqYMIEHjUW+NPY88qI09MCln5 XlnWJk95RX/iTH3K68RQTfInZPdw+h3/IK9yvLotmWjQ9aFBAyJi1HLNAdtujX7t 97V+Hc4QbEdXNElhZN+Jv49pa6KdDetf3D9Vpfq5BquxlecIgaTimfPTlJy7kwTt zEDW4iJo49b8klomng/vxQzl7R7md0H31K34oBSjTixgLkWj3pFvzpO7j3o7Sx3n yHHKUQr/ =VNEv -END PGP SIGNATURE-
Accepted qpdf 9.1~rc1-1 (source) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Nov 2019 21:38:01 -0500 Source: qpdf Architecture: source Version: 9.1~rc1-1 Distribution: experimental Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Changes: qpdf (9.1~rc1-1) experimental; urgency=medium . * New upstream release. * Includes build dependency on gnutls to use gnutls crypto provider instead of qpdf's native crypto. Checksums-Sha1: c1b491a478f1f9fdbf39f8515b78200bda8c8bef 2098 qpdf_9.1~rc1-1.dsc 0fd1a4aeeca77ed4cd0bcb80bf3f42af4eb9b71e 18286346 qpdf_9.1~rc1.orig.tar.gz 126b131e8c510c52cf09aa03132b01bc48b33ac7 833 qpdf_9.1~rc1.orig.tar.gz.asc b35944a96815228087fd8d12d9d2abaf6f188b4b 13540 qpdf_9.1~rc1-1.debian.tar.xz 650e3883f62a513480a85719d164c3c7bb4957d2 7059 qpdf_9.1~rc1-1_amd64.buildinfo Checksums-Sha256: 7943e9c21d89bcf8f66435e3d98d7bc4c1fc77e5ce3b9448ffcb8dfe9b903429 2098 qpdf_9.1~rc1-1.dsc 91146eac53bd37832442f2fd2f9e8ed1966cc06889a3136403e30bf93c08fc57 18286346 qpdf_9.1~rc1.orig.tar.gz f5b2df7f3e392b9a793ef2f3a986233b88219d9cdde534ec775e14aa831b2be7 833 qpdf_9.1~rc1.orig.tar.gz.asc 94031258d85ddc76ce4ab3f4c220b34a278755139ca39ac57b1e1813b839c864 13540 qpdf_9.1~rc1-1.debian.tar.xz 32adf3492eec683dd00abb54a683fbfdd29ec185f7f26d6a93ec5faa5f67 7059 qpdf_9.1~rc1-1_amd64.buildinfo Files: 5fd562a8b96586db86aa5bfbbb7c90b3 2098 libs optional qpdf_9.1~rc1-1.dsc d6e8c5d7019b62bfe3e9fc7bb2162139 18286346 libs optional qpdf_9.1~rc1.orig.tar.gz b25b4d741fd08698a33b25e09c85d54f 833 libs optional qpdf_9.1~rc1.orig.tar.gz.asc c6142aba003bf3bea8f96c89ce47139e 13540 libs optional qpdf_9.1~rc1-1.debian.tar.xz 0887b117793bedfa11d568725589a721 7059 libs optional qpdf_9.1~rc1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAl3I1AQPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+UV8P/2nMmxJrNDRj0gqGhbQlVzA65MSAFFikHLOu aMkRODHC5Q24eTY+SK/MGnbRsCw5DUNE4/wxovUS07J9EK8nh8GNqA2OOlXUH0am Sj+nfw9BBKyNpXFsOK8htx7rNG8lqhZbmNtg7y9hlRYII1ku1XnSDA+n9rhcpcKO MmS9rKeeSU75nMapcuzaxZFKu8vsBbvlE19G1XKCDpu+LFbHGlDLPmPRJiCsqDvB rnvl4aElH/WBD/FDAgFKnuDoE9XjgxnJqRZZ1Gj2WzTa0Hrf1Ak3ihW0qBOlfV6s dUhfxKtn5waO0iwAPRipYoiL9+MjPNpVUq3ulDer3qE8GESmCsVSHTjYT4s/tdTB dQ7ykLr2om9L4WJG274PZeR0lIPWpIQh4gzIiPpCnLA9T+VtynbAn20zwutWai58 lbYiKz56ca9hvFxf49PygqTw1Nr5trrHTWVjYNPuqYMIEHjUW+NPY88qI09MCln5 XlnWJk95RX/iTH3K68RQTfInZPdw+h3/IK9yvLotmWjQ9aFBAyJi1HLNAdtujX7t 97V+Hc4QbEdXNElhZN+Jv49pa6KdDetf3D9Vpfq5BquxlecIgaTimfPTlJy7kwTt zEDW4iJo49b8klomng/vxQzl7R7md0H31K34oBSjTixgLkWj3pFvzpO7j3o7Sx3n yHHKUQr/ =VNEv -END PGP SIGNATURE-
Re: Should qpdf depend on gnutls?
Okay, thanks for all the response, public and private. There seems to be broad consensus to use the gnutls crypto and disable the native one, so that's what I'll do. Appreciate the advice! --Jay On Sun, Nov 10, 2019 at 2:05 PM Moritz Mühlenhoff wrote: > On Sat, Nov 09, 2019 at 07:10:44PM -0500, Jay Berkenbilt wrote: > > I am the upstream author and the debian maintainer of qpdf. > > > > At the request of RedHat, I have made an enhancement to qpdf that > > allows an external library to be used for crypto functions rather than > > using qpdf's native crypto implementations. The qpdf library includes > > code to compute hashes with md5 and sha2 (256, 384, and 512) as well > > as encryption functions for rc4 and aes256 with and without CBC. > > Disabling insecure crypto is not a practical option because of the way > > these things are used in the PDF spec, but it is possible create PDFs > > that don't use insecure crypto by just using 256-bit encryption. > > > > I can build qpdf 9.1 for Debian in one of three ways: 1) use only the > > native crypto as in all previous releases, thus avoiding a dependency > > on gnutls; 2) build only the gnutls crypto provider thus causing a > > dependency on gnutls but eliminating the native crypto entirely; or 3) > > building both crypto providers, in which case gnutls will be used by > > default, but developers and end users will have the ability to select > > the native crypto provider at runtime if desired. > > > > Do you have an opinion about which way I should go? I believe RHEL and > > Fedora are going to use the second option of building with only gnutls > > and dropping native crypto, but I have also enjoyed the fact that qpdf > > has so few build dependencies. It is possible that a future version of > > qpdf may support digital signature, in which case I will definitely > > have to add either openssl or gnutls as a dependency. > > I'd recommend to go with 2); there's a lot of value in using a common / > scrutinised crypto library over a custom implementation and for all > practical purposes gnutls would not be an additional dep as systemd > already pulls it in on virtually every Linux system these days. > > Cheers, > Moritz > >
Should qpdf depend on gnutls?
I am the upstream author and the debian maintainer of qpdf. At the request of RedHat, I have made an enhancement to qpdf that allows an external library to be used for crypto functions rather than using qpdf's native crypto implementations. The qpdf library includes code to compute hashes with md5 and sha2 (256, 384, and 512) as well as encryption functions for rc4 and aes256 with and without CBC. Disabling insecure crypto is not a practical option because of the way these things are used in the PDF spec, but it is possible create PDFs that don't use insecure crypto by just using 256-bit encryption. I can build qpdf 9.1 for Debian in one of three ways: 1) use only the native crypto as in all previous releases, thus avoiding a dependency on gnutls; 2) build only the gnutls crypto provider thus causing a dependency on gnutls but eliminating the native crypto entirely; or 3) building both crypto providers, in which case gnutls will be used by default, but developers and end users will have the ability to select the native crypto provider at runtime if desired. Do you have an opinion about which way I should go? I believe RHEL and Fedora are going to use the second option of building with only gnutls and dropping native crypto, but I have also enjoyed the fact that qpdf has so few build dependencies. It is possible that a future version of qpdf may support digital signature, in which case I will definitely have to add either openssl or gnutls as a dependency. --Jay
Accepted qpdf 9.0.2-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 13 Oct 2019 20:42:32 -0400 Source: qpdf Binary: libqpdf-dev libqpdf26 libqpdf26-dbgsym qpdf qpdf-dbgsym Architecture: source amd64 Version: 9.0.2-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf26 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Changes: qpdf (9.0.2-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 50d12c5c91ecd33dcd1fa2bbc2eaeaef05b90938 2061 qpdf_9.0.2-1.dsc ba3a9ce177186288ed2cc77ad070f37467770edf 18168977 qpdf_9.0.2.orig.tar.gz 056778295109221c9c1e6db6e6f167b07a715d07 833 qpdf_9.0.2.orig.tar.gz.asc 84d5fec3c10b57923b58c89a4f884000cad91910 13436 qpdf_9.0.2-1.debian.tar.xz 15321544830179b77e30bbc009a1a326a644d822 645344 libqpdf-dev_9.0.2-1_amd64.deb 2acc8d54950d21c3bf5327955a7309aa37580079 7850980 libqpdf26-dbgsym_9.0.2-1_amd64.deb 8690491631dfabc6b23db66281bc3d6d691e4496 471864 libqpdf26_9.0.2-1_amd64.deb ce67272f0f4de59c123054f26039dfcc5d05cd0b 1493820 qpdf-dbgsym_9.0.2-1_amd64.deb c26a4e9231a0c3e3aebeefda16b3723158852d9d 6567 qpdf_9.0.2-1_amd64.buildinfo 582ac5653b9afeef711e93a82b05c119f7af9444 447432 qpdf_9.0.2-1_amd64.deb Checksums-Sha256: 86b65cf74bae484b3761cee38d4280b0e21eac88b73c1cac6723f1281c4c0120 2061 qpdf_9.0.2-1.dsc d02451d906068947f45e5216032f0f29ae53313c70c4deedcf3c3e173584d22c 18168977 qpdf_9.0.2.orig.tar.gz 28ab558d1cf03eb323b85d2dca9db8ffb6806394e64e6196775d1805709b 833 qpdf_9.0.2.orig.tar.gz.asc c9e6c4ca8c8a5334d0021234f8caf644b8cab18af02bbf2f9767cef257b54d46 13436 qpdf_9.0.2-1.debian.tar.xz a840880cd67ec7c0e644e15f2d34e686db23e23a38d02edc7746d5bbf9db101a 645344 libqpdf-dev_9.0.2-1_amd64.deb c167d7ce2b045755bc3cdbfabce9962e4062dd87d34bc6bc033c0594dec8ee70 7850980 libqpdf26-dbgsym_9.0.2-1_amd64.deb 4c201a1b8fd91f0f4ca3907b55bd753e085665f3bb20a8bd2a5c8eadc160f708 471864 libqpdf26_9.0.2-1_amd64.deb d445baaa518aadf2d653bd1e197610d15867692fed18745d15aa98d67a264aa3 1493820 qpdf-dbgsym_9.0.2-1_amd64.deb 4c9cf5085c8410bfeb56bcc671d6d8315bca94d20c6f33e355e69ce2bbdea70b 6567 qpdf_9.0.2-1_amd64.buildinfo 713395c45c14451c8281dfc92563145548d3494209aa5c56daabe83c67e06030 447432 qpdf_9.0.2-1_amd64.deb Files: fb8282e9d5a97562c9a792bd42c7b704 2061 libs optional qpdf_9.0.2-1.dsc ad9431ddd92c0767d9f040ada2ac5065 18168977 libs optional qpdf_9.0.2.orig.tar.gz b55c7445bb6d3348887ec84d401a4c5b 833 libs optional qpdf_9.0.2.orig.tar.gz.asc 99da51531989f876ec1b6786a03a0724 13436 libs optional qpdf_9.0.2-1.debian.tar.xz a4ab19901d0d0e81056ff9219fa50b55 645344 libdevel optional libqpdf-dev_9.0.2-1_amd64.deb 490c98c49a535d4235658a8f495b13e3 7850980 debug optional libqpdf26-dbgsym_9.0.2-1_amd64.deb 098f626213ea4d8e59ec7ffdfee92166 471864 libs optional libqpdf26_9.0.2-1_amd64.deb c1badad019c554fbe88cdcc6cf4b7935 1493820 debug optional qpdf-dbgsym_9.0.2-1_amd64.deb 0c199bc780255c8b429ca2a9e8240734 6567 libs optional qpdf_9.0.2-1_amd64.buildinfo f5f36e51259ba0d65b01f0a9f61ff692 447432 text optional qpdf_9.0.2-1_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAl2jylkPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+5H4QAIjEzNmGX1AZWi8rilO7LMFOpMfjDpbfmfA2 vFQ0FrCsaK1uXvRaq6VXBIlyDRXofPHCHkbpCQuaiQ//BYPWBYOyNbh6KicfKz3j 25fRp2JEQgez3Y0r0Enqz0npKeN4vxRzOg1WGBOjwdrlO6jqdpVp4HfKiPC45AcS sKyPGHyYn6eXRg5BKQIMKZPK1gGSoyfxUpaFTTvicwIHxXtJXAMRux+8Ulho+tHj 8ZfTCPW65y/f5CLWojvH+2ziLRJ0wK966eWS9EjWKtSypWh0YHIy109sKKrV1yw5 yNDWS/9eemhXhxZ1nuGuzH1sHgq5tboABHdYauHLv1p1Eqyiuh6bn+32xuSAzwqV Tn2i9H/51rHf8GBSJRoSexAVIw1r0ahpukYeUTDfU0ZhCie6yv+LTLXoeS9EwXeR kb+l+Ds107q+RVtHzxBs4eXR51DUO/2xJe/Zx5BJT7n+/J4RFsd1ETyM2e6+c5d5 7lAEwzT9gTXGREJPtegw8IM3yH2VhIinHRn+dMHp6fxIwJhUMWfJYA0TShMNIDEy f+IU8bzDdcdm48fPljRcrvlw43SzOecx2W7QZno7zrQXXe6jFJYwsdY9E7Bh1bDz AIYZT3/I5Tp3ax7PSc6qGJ5Tz4to3A4VeFjFhRDB88ecpOLu8Gz1sXZJxDbUnfkT q6okEZcp =wp7r -END PGP SIGNATURE-
Accepted qpdf 9.0.1-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 20 Sep 2019 09:35:45 -0400 Source: qpdf Binary: libqpdf-dev libqpdf26 libqpdf26-dbgsym qpdf qpdf-dbgsym Architecture: source amd64 Version: 9.0.1-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf26 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Closes: 933397 Changes: qpdf (9.0.1-1) unstable; urgency=medium . * New upstream release. * Upstream release includes detection of duplicated dictionary keys. (Closes: #933397) Checksums-Sha1: dbc40c6435ef749714f7a02ad4bdc8bfd913436a 2061 qpdf_9.0.1-1.dsc 5a3f8f86a71cd1fde2fcba08837b61d995f6aa39 18172693 qpdf_9.0.1.orig.tar.gz 7886669d3d32552e823a456fe3f1103731be6a9c 833 qpdf_9.0.1.orig.tar.gz.asc 9b8a3c3b8a78ec30692c874267071707914baf47 13420 qpdf_9.0.1-1.debian.tar.xz 28a941a5a276b238d0d74f5a7fd5d1487ff0235f 646032 libqpdf-dev_9.0.1-1_amd64.deb ba5c3849c18a506f21f9d3d144e4b8aa7cf9383b 7848988 libqpdf26-dbgsym_9.0.1-1_amd64.deb 9858d762c5e2e5f4bd602b73157e5f2029596048 472380 libqpdf26_9.0.1-1_amd64.deb 4e966fd909c4d480fceb046378c555d6b3fb5860 1483784 qpdf-dbgsym_9.0.1-1_amd64.deb bb39f9e036f79261bf12c549ec303559d9bfb31b 6614 qpdf_9.0.1-1_amd64.buildinfo 25d9ff7bb042f6ffd0bd02fb30421b58ac02925f 447032 qpdf_9.0.1-1_amd64.deb Checksums-Sha256: e0eb455b1a9d01a08168843e09b58956ec692ca025cb70cc93c844ede2b80210 2061 qpdf_9.0.1-1.dsc 2511f3daa131afe9766caec17bfd4f9cca7d849093ebe845530210a1055a0f52 18172693 qpdf_9.0.1.orig.tar.gz 3346db666fd2d0ba962fb22aa83e93dcd1208e53fbb9ba5d18d2e44ca52c08f4 833 qpdf_9.0.1.orig.tar.gz.asc 8dc8a15ecc76ee7da00f6d1aa3dd6169acfc2e9b27f94359b0f7b752e137506d 13420 qpdf_9.0.1-1.debian.tar.xz 08de41382800d591ea41b059158b3e6b91ba796cc583216d4e6a87cbbec459e0 646032 libqpdf-dev_9.0.1-1_amd64.deb 4046968ef011611b2e56d5ac1ad5c647d82c1773cb4d29203119fc18e18b686f 7848988 libqpdf26-dbgsym_9.0.1-1_amd64.deb 80b55b86ca023793ad3be828ca8975c4e83bcb7bffd2040e739cee74f1ec726f 472380 libqpdf26_9.0.1-1_amd64.deb 6cc01211782e65fbdcf8b82d1ef4f1401d27fc7ac82b60b494f6f9d16ab75c96 1483784 qpdf-dbgsym_9.0.1-1_amd64.deb 14191a0d62d122da2fb925f1867844366103bf9f05c4f451294670f81273d0fd 6614 qpdf_9.0.1-1_amd64.buildinfo 0b88e72a82408d614c6bb93b51ae2251af8531a96aa63bc7e7f3fbe98069f0a5 447032 qpdf_9.0.1-1_amd64.deb Files: 2e4dbc37b61afcf23669aa839ef5a7bd 2061 libs optional qpdf_9.0.1-1.dsc d064a3dfee9fc53c306f10f48328ed2e 18172693 libs optional qpdf_9.0.1.orig.tar.gz 71d2a1d063dddbe5700acbcb1f2c0303 833 libs optional qpdf_9.0.1.orig.tar.gz.asc 3e3c0956e37762879a5a6086b7c5e984 13420 libs optional qpdf_9.0.1-1.debian.tar.xz 3313eff1371af4d3e1dea24b5bf17bb8 646032 libdevel optional libqpdf-dev_9.0.1-1_amd64.deb 121da85b62cc3a3841d01732c0db1826 7848988 debug optional libqpdf26-dbgsym_9.0.1-1_amd64.deb b12aeba934c95651d83a88eb37a2989c 472380 libs optional libqpdf26_9.0.1-1_amd64.deb c2d9393c209558fb469ac7817cb384a2 1483784 debug optional qpdf-dbgsym_9.0.1-1_amd64.deb 59931b18ae740c44635573acfd0c595d 6614 libs optional qpdf_9.0.1-1_amd64.buildinfo 970046874dbd82943bd8b1d9c9985f1a 447032 text optional qpdf_9.0.1-1_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAl2E1rEPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+MNYP/35gqD+ZJH4gCzWqLk1mEimtGnz55OwtVPr3 KxUQEb+TCD0EFgi39jmOaY23b6egPUlqAsiuXbsIhWgQmfZM6AAW398uinpPw1vo JFJI6td93SvEmnYbOQfWNM2GmVRiECjCfYyeEsxeqSd+XNGRy+gypRk/T0RZd42M w1wOX1PgGHbhq7J0MRxcU0UNwqsZ40JQRCNdUCRlNkE7ffr1fuDAI/u0fnTJzFJL Gzsa0jO/rO6Xt9NMLlArRER9oIYo/4HQqgoAenpjUrXFqYF/Yqecx7c3GTt+Wl8l w9Lcs+LHDggmzoQErLR+tXrk1vSLa1M/2M1O/LNN9fVfMRXr1LF0PV4WUi8jvFZW 7C7OWaT7s5/V4VweQBLBooCTpPdTewbeKkcxb6vB6OWtY3D/tzjOPkJMvBNvb497 okU2lNKQE8J+P42iYW2RhbxVsuAtcB1eMvyyj08n7OYf2VBmXTJjqEaWhwucr38L JzBjySwBeiZuRtma/OfryogCbPxebCpxfJxdZzzmnRZAIeYndR1x2aJ3RFryl60b +eoAKJTPumS3Nz7AVCdE1wzHdW94CMAXFQxlpxNO6k/RMBeQJvs4j0Ao1McdcSql 0yvi7LsOsNT8lICUNvX4rhgHvCJFbVOP+kL26VKb8Lab8PVFzyLbbmx+Xvofiu7U VFCEKNnP =1/Tx -END PGP SIGNATURE-
Accepted qpdf 9.0.0-2 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 17 Sep 2019 19:18:59 -0400 Source: qpdf Binary: libqpdf-dev libqpdf26 libqpdf26-dbgsym qpdf qpdf-dbgsym Architecture: source amd64 Version: 9.0.0-2 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf26 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Changes: qpdf (9.0.0-2) unstable; urgency=medium . * Patch for integer conversion warnings on big-endian systems and to fix a test failure (from a bad test, not a coding error) for systems where char is unsigned. Checksums-Sha1: e450768d39de99cfbedab2fd6a034ded01bb5f34 2061 qpdf_9.0.0-2.dsc 1b5ff1d90c2f56559d77fdd0055403bb8a8d15a4 14664 qpdf_9.0.0-2.debian.tar.xz 2182a63078ee487832494a09adc131bf13eb1ffb 644540 libqpdf-dev_9.0.0-2_amd64.deb 26084e275399cc7f019dbdea18edb3b4597e6b42 7850924 libqpdf26-dbgsym_9.0.0-2_amd64.deb 4534f7f30c4b7c90169387a7b36a92b54668c680 471344 libqpdf26_9.0.0-2_amd64.deb 86e4dcae195eb1387a4041c110aae8eedf0380d0 1483768 qpdf-dbgsym_9.0.0-2_amd64.deb b44925ea612f3f3a57ad44d24ed9a1b505921417 6614 qpdf_9.0.0-2_amd64.buildinfo 4c062f93eb8e7f9ff120f1439f778bbc005d6fcf 446400 qpdf_9.0.0-2_amd64.deb Checksums-Sha256: f2096a465e28219c71c4ee8410475fdd0a6c7b917216405a762bcd26ff104a7a 2061 qpdf_9.0.0-2.dsc 1b52c32d8329ee0ca04676c082fb1167721364727446d8450b500ca661263175 14664 qpdf_9.0.0-2.debian.tar.xz a46ef7f8d784cf28ed90f242de4d11c31f81bd6e58502e022efa45e2dce9f671 644540 libqpdf-dev_9.0.0-2_amd64.deb e7cbf92f1886a28fe382686be096cb5f74fc28b557c403e9f60b18e235b36fbf 7850924 libqpdf26-dbgsym_9.0.0-2_amd64.deb 008e0e3821958fcc95b5846d3a3925b4b5b3706f04a2194b6b53d174ba95f159 471344 libqpdf26_9.0.0-2_amd64.deb 3b5f98c9344df8440ab79636a564961902eacd44131e1075bcb8b5b732c947cf 1483768 qpdf-dbgsym_9.0.0-2_amd64.deb 052bdd902942f34d2d9fe288a2cbc45e7dba02e6576877f2ce861fc2c72fb8bc 6614 qpdf_9.0.0-2_amd64.buildinfo 199e5c948437b6bfc0dddaffd340f3ce30f8a8caf95e3fe08e68bb60aeffbb50 446400 qpdf_9.0.0-2_amd64.deb Files: 903cbae00e49ea1ae3e27502bd3dee85 2061 libs optional qpdf_9.0.0-2.dsc 837afe8dd9373206fd71aeb8b22793b8 14664 libs optional qpdf_9.0.0-2.debian.tar.xz d37d33fb0540242041fd7446a1b3a456 644540 libdevel optional libqpdf-dev_9.0.0-2_amd64.deb f02c207171c760edcefda107a23e1064 7850924 debug optional libqpdf26-dbgsym_9.0.0-2_amd64.deb da31cc73da66758a5e58396721122e8c 471344 libs optional libqpdf26_9.0.0-2_amd64.deb 9da1322c0cd2bdbfda3e19f7576d015e 1483768 debug optional qpdf-dbgsym_9.0.0-2_amd64.deb 2a48066ebd89601c433c5d390d6dbe5a 6614 libs optional qpdf_9.0.0-2_amd64.buildinfo 023a189665f71f76f930d1a72ab38c50 446400 text optional qpdf_9.0.0-2_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAl2BayAPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+av4QAK41DtWQmm3syEF0XKr+GvUwVRtPF1ITmxvY H1WzIu7oNswtUn2MMfjry304NxSOTRLCj5l5Pe41FDJuHuEDWrOcU3ut981RKl0y 6GM8acPPMjCulQqVs5gOLk+Nm5/FTjKxip88ih1vTInJwwLCK6b9/RmI/ROygAho Slktx3jU9QfKkGRcsYpMTZ8h4Z13fPPNnBpT2fBeKfmZrbqhUW8cE4mIF83/qLm7 RQ9hxRi6oNANZQ84iaId0RoqsQw7t8iQJT7yDh9828c/d0xZ/B7iI8E5rKECt7oz 0FqgAupplT/Iv85pypy08NFdJRmz+1lXUr43gAmRsef8raJ2Q6fvAYC9PK3EH47z 5RFRdZ8J3zVxjytX2LrCDIiTGWJ3y5L3AVa/5FTCylY0fclZ4xUeEMLPGRREOwFs jm4ixXoz3hbs66l3ycvESvUsfHyAuuHdHHmdIFpUKdsgTePVfsQQDkKnOu5lUA1A q07zXaMXXDOcJA+WRtKLjkxiKN5kHwH23BPlmP/2JBDFJSFP2uOk/TUnYKN9HwMP ijhMsM1rsaxwwDZ8FTeK09HqmSIUHqKFV8Z/7ZTgZb5Pt5+VhcRJDhaQUOiAdIao eFf3io0yrJqYI1TnhfOnI/mYPLL6CW9ArEnKj0GRGeEZnVhdPTyTP73clUGwjo1w c6X1sF50 =3rNH -END PGP SIGNATURE-
Accepted qpdf 9.0.0-1 (source amd64) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 31 Aug 2019 21:45:41 -0400 Source: qpdf Binary: libqpdf-dev libqpdf26 libqpdf26-dbgsym qpdf qpdf-dbgsym Architecture: source amd64 Version: 9.0.0-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf26 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Closes: 933401 Changes: qpdf (9.0.0-1) unstable; urgency=medium . * Use https on download address in copyright file. (Closes: #933401) * Update standards to 4.4.0. No changes required. * New upstream release. Checksums-Sha1: 05d19af5165ee99f779e0726d03510692c258935 2061 qpdf_9.0.0-1.dsc 9e43d623dd761e257a665f6c8d4fa52105a83373 18172400 qpdf_9.0.0.orig.tar.gz e83a8a71cfd1049bbd51bedba093c296a3d8e914 833 qpdf_9.0.0.orig.tar.gz.asc 4e9d5281277c292d6c1c567e85fada3c362dae75 13304 qpdf_9.0.0-1.debian.tar.xz a0497c918350f39379fa144f745936ef1bd5fa31 643964 libqpdf-dev_9.0.0-1_amd64.deb f09416f8dfcc9cc31ccc348398d18982246e6236 7850536 libqpdf26-dbgsym_9.0.0-1_amd64.deb 0caaab932f915d625ac461f582f54f2f96a73f5c 471236 libqpdf26_9.0.0-1_amd64.deb 10006e7ff6fea6c185cbb51a891236af17755e0e 1483608 qpdf-dbgsym_9.0.0-1_amd64.deb 847d453edd3a5299b1aaea9f4ecce0cb4c394f34 6602 qpdf_9.0.0-1_amd64.buildinfo 3fb57ebf957707d787f0a29ab26f95617a0e1e02 445904 qpdf_9.0.0-1_amd64.deb Checksums-Sha256: 968e0db3162e820f3bc589ec4a1f4e732a25ccc10f7bfd1ab2d5523a0083b38e 2061 qpdf_9.0.0-1.dsc 9d2a70c181ff7e5d92a0fc10c4973a2a8164d4fb71ce3584bc5f1740bd65379c 18172400 qpdf_9.0.0.orig.tar.gz 9c1f673e25ddd62ea5dfecccf8aaea24cce20bf5721508b808bc804e65eaef7d 833 qpdf_9.0.0.orig.tar.gz.asc b578c6d0c75e06c1a68627678f30374bf980a82ae529f80f908f0c004d576642 13304 qpdf_9.0.0-1.debian.tar.xz 27a2e662d7a1f4971ecc6ff71ae966913a6008d7316291ea2463d95b80c7a0a4 643964 libqpdf-dev_9.0.0-1_amd64.deb b33ab67665c596cd1958c00497769bb607f9e8ad86a036fe2d7a9f0a5955f6f8 7850536 libqpdf26-dbgsym_9.0.0-1_amd64.deb 1837d6bcb314f66f785f3451936991ee011d30ad7b2a9dd38147732a56dc7dde 471236 libqpdf26_9.0.0-1_amd64.deb 067ac548b3f664074dfa126b55b23f89c8bbad6aa72b192cc08cb16e9aef357c 1483608 qpdf-dbgsym_9.0.0-1_amd64.deb bd3c7fdf639e3fca62a3f75566f330527ccab601330c92fd0b8403e6b873a5d8 6602 qpdf_9.0.0-1_amd64.buildinfo b5289bf53380ce416455d74bcd2962051f101f086946806a31a9e32a06eb20ae 445904 qpdf_9.0.0-1_amd64.deb Files: 9940b0a93d9ad602a159a2c68ec5511d 2061 libs optional qpdf_9.0.0-1.dsc d7e165edd07df8bc4c1c4e6b8538b455 18172400 libs optional qpdf_9.0.0.orig.tar.gz 728337323b286bf926efd486869ee525 833 libs optional qpdf_9.0.0.orig.tar.gz.asc a6e0e5a5edeb8d277498dd0ee9128f44 13304 libs optional qpdf_9.0.0-1.debian.tar.xz 0a04b3fedc75dbeb474e8125fc64c90f 643964 libdevel optional libqpdf-dev_9.0.0-1_amd64.deb 55d18df8534af0aa505a76a3a7f07d2b 7850536 debug optional libqpdf26-dbgsym_9.0.0-1_amd64.deb 7a1ca294e47f6cff88d7813bf8fbaa6f 471236 libs optional libqpdf26_9.0.0-1_amd64.deb 97819d2a85dc53135655c786aacbd2e0 1483608 debug optional qpdf-dbgsym_9.0.0-1_amd64.deb b39557437f4bf61283d55bfa568ecf3f 6602 libs optional qpdf_9.0.0-1_amd64.buildinfo f0b7b642ed720e045ae2a08a755baa03 445904 text optional qpdf_9.0.0-1_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAl1rJmgPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+CUsP/AnmrUwPISa/lTs/bbh+55KFDWG54Y0dmNlY 0v5tmXzxSWyJ5PeX9CInr/AgdbAPhtzLleecMFinJwsRK3dEfndmLBvv9yJedoSU 022JsqneDGY+uC2vTaQVrixXswOzaS+2DmPkfoBPcVrIR6Ys1BfEH96NHiwOgMEJ ib0zdMEFy4MCqet3YfnOc20nuhiKqJr6Dmcdwwg8z7z+tqU0dnen9vVd5oPZT2oz VYOBxaXgw2cSxIQ2U4CWgDv1+cyAdSfH9YFiXEUg4Ozoo7K6WMGuKqk8afaX8mDK pJA0uPBmkPDNw5KmUOcthfOk8uiokOKMUZynCZet/jd2YEb98gfleBQ/lWlOZ5qx yg1mHcUbHqn9akTwR+84tfauF6eGCCBi9BadXsSWeBMZREdcaRD/KlIFbLaeXnfD tzNtW2DPwcwnNhQ3aAzJuBhFIZtBqBO/LmNF0GS6GUcYm3f3VsOU3ejOJ26AdsXq 6+k0kLeZ7AQghvJgFq8W+uY5dCCtztbo4sTO6DLYTr4QtcelpJxuDXIahlEj2J4l wf+s2vOO9sUsa2n1NbTRsSPrFgtUErI1EG4fh1QdOgMBSdi7j04XNeqf9+idqFl4 t9zOMG1KzHUlv0OGBBdG/GT6IjI8HyRT1HvD0O2AQ+4fPoa/nXyqr74+bZqyct6D WGK3evmT =2skT -END PGP SIGNATURE-
Bug#933401: qpdf: copyright file: should use https
I've fixed it in my local repository, so the bug will close the next time I upload. Thanks. On Tue, Jul 30, 2019 at 7:27 AM Vincent Lefevre wrote: > Package: qpdf > Version: 8.4.2-1 > Severity: normal > > In the /usr/share/doc/qpdf/copyright file: > > It was downloaded from http://github.com/qpdf/qpdf/releases > > For security, https should be used and documented. > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, > 'testing'), (500, 'stable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX > (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages qpdf depends on: > ii libc62.28-10 > ii libgcc1 1:9.1.0-10 > ii libjpeg62-turbo 1:1.5.2-2+b1 > ii libqpdf218.4.2-1 > ii libstdc++6 9.1.0-10 > ii zlib1g 1:1.2.11.dfsg-1 > > qpdf recommends no packages. > > qpdf suggests no packages. > > -- no debconf information > >
Bug#929252: unblock: qpdf/8.4.2-1
On Mon, May 27, 2019 at 4:14 PM Paul Gevers wrote: > Control: tags -1 moreinfo > > On Sun, 19 May 2019 20:43:29 -0400 Jay Berkenbilt wrote: > > The changes between qpdf 8.4.0 and 8.4.2 are bug fixes, but I am > > asking for consideration because this update includes fixes to a > > serious performance bug (CLI), a CLI non-compatibility bug, and a > > library fix that could cause data loss in rare cases. These bugs are > > all in the part of the code concerned with splitting and merging > > documents, which is one of the main things people use the qpdf CLI > > for. While these changes are not critical, it would be disappointing > > if the version of qpdf in the next debian stable has these > > already-fixed bugs. > > How would a targeted fix look like? I don't think we'll unblock the new > upstream version. > I could extract the changes between 8.4.0 and 8.4.2 and apply them as a patch to 8.4.0, but I don't think I'll do it. It will be confusing if the debian stable version is called 8.4.0 but actually includes most of the fixes from 8.4.2. If it's too late to accept this unblock request, that's fine; we'll just leave things as they are. I plan on releasing a version 9 this summer, and I can just do a backport. If the unblock request is rejected, please feel free to close the request. Thanks! --Jay
Bug#929252: unblock: qpdf/8.4.2-1
On Mon, May 27, 2019 at 4:14 PM Paul Gevers wrote: > Control: tags -1 moreinfo > > On Sun, 19 May 2019 20:43:29 -0400 Jay Berkenbilt wrote: > > The changes between qpdf 8.4.0 and 8.4.2 are bug fixes, but I am > > asking for consideration because this update includes fixes to a > > serious performance bug (CLI), a CLI non-compatibility bug, and a > > library fix that could cause data loss in rare cases. These bugs are > > all in the part of the code concerned with splitting and merging > > documents, which is one of the main things people use the qpdf CLI > > for. While these changes are not critical, it would be disappointing > > if the version of qpdf in the next debian stable has these > > already-fixed bugs. > > How would a targeted fix look like? I don't think we'll unblock the new > upstream version. > I could extract the changes between 8.4.0 and 8.4.2 and apply them as a patch to 8.4.0, but I don't think I'll do it. It will be confusing if the debian stable version is called 8.4.0 but actually includes most of the fixes from 8.4.2. If it's too late to accept this unblock request, that's fine; we'll just leave things as they are. I plan on releasing a version 9 this summer, and I can just do a backport. If the unblock request is rejected, please feel free to close the request. Thanks! --Jay
Accepted qpdf 8.4.2-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 18 May 2019 09:55:37 -0400 Source: qpdf Binary: libqpdf-dev libqpdf21 libqpdf21-dbgsym qpdf qpdf-dbgsym Architecture: source amd64 Version: 8.4.2-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf21 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Changes: qpdf (8.4.2-1) unstable; urgency=medium . * Update standards to 4.3.0. No changes required. * New upstream release. Checksums-Sha1: 91781106b061dee2aefe721755575073f3d83b8b 2061 qpdf_8.4.2-1.dsc cff70e5436953fb8b84066cf12a42ce9861ba822 16988263 qpdf_8.4.2.orig.tar.gz 20bcbf505fcfc04bfe076ce43bae46e07c1b8967 833 qpdf_8.4.2.orig.tar.gz.asc 96844ef6a71bcc621f3b22a477be925519729cfb 13272 qpdf_8.4.2-1.debian.tar.xz d7e4e01779341a7609b605e773ff16b00b6e9e05 577084 libqpdf-dev_8.4.2-1_amd64.deb e903a59a72e0e74a7a0280ff247e37bf4b454b6b 6839908 libqpdf21-dbgsym_8.4.2-1_amd64.deb dadecc2770bbd1ad5b79e1309d62e5bbe0a6d015 434760 libqpdf21_8.4.2-1_amd64.deb 92c8a7f175fb97b0421ec029926329b01fbc4bb5 1256112 qpdf-dbgsym_8.4.2-1_amd64.deb 570d87d24fe37706c489b23dff5ae0d6a342cb5f 6361 qpdf_8.4.2-1_amd64.buildinfo 52ef9511b778fd1a5b20629400f848e8766d29e8 419664 qpdf_8.4.2-1_amd64.deb Checksums-Sha256: 732ba4c43060ad44c0a7230980fea1d6796db64a278a0e199a130e46d82d1fd1 2061 qpdf_8.4.2-1.dsc 69a30a65ef9398e6dbf151f1f6a31321cbc0f49b6cc0689ce10ea958bfd13ec3 16988263 qpdf_8.4.2.orig.tar.gz 9af5a7e5050075c76b44289d97bae982fbd90e4dfc1e75bf88ffc28d3016d55d 833 qpdf_8.4.2.orig.tar.gz.asc 8ddd308e16d0a19e997170a05edfceeba456ccb64973ff09958afff243872675 13272 qpdf_8.4.2-1.debian.tar.xz bba35b76b86ae2d7d7e9d403e5fe6c7097fc2a874365a0ebd5eb49aabf276592 577084 libqpdf-dev_8.4.2-1_amd64.deb 75426edb12b9ca401fa8b06a07c82e8533c12c649ccc5d16ede50a3e1e0ccb03 6839908 libqpdf21-dbgsym_8.4.2-1_amd64.deb e8be09cdcbc4c2755b45e8fb6dc8682b25499f31ed979cfab46fe0912e257172 434760 libqpdf21_8.4.2-1_amd64.deb 075654a4ae7eac0edfa409073a6254c567b46708a43ca2cc0c4c64be2fb887a2 1256112 qpdf-dbgsym_8.4.2-1_amd64.deb d3e45c188ac9ca75a3f01f3666d1006dfc358a39ab7a8369180c6682dfd938aa 6361 qpdf_8.4.2-1_amd64.buildinfo 3c7e916f8e82a5adc5e39f33739ff4e61ea3ac891d28d88a7c1d7becc66c0561 419664 qpdf_8.4.2-1_amd64.deb Files: 6d80e96969026b9bb6895bba8abc6a22 2061 libs optional qpdf_8.4.2-1.dsc 41160fbd4450d4988f0705d394069ad4 16988263 libs optional qpdf_8.4.2.orig.tar.gz 3254aac98f16e4dc6022ccdd754534b7 833 libs optional qpdf_8.4.2.orig.tar.gz.asc c57b0673c4bbe3890c5c3b158dad754d 13272 libs optional qpdf_8.4.2-1.debian.tar.xz 671558d72302e5e7caab24b9ad154cb0 577084 libdevel optional libqpdf-dev_8.4.2-1_amd64.deb 6648d768b0c6c14cf151c22d7b3343e9 6839908 debug optional libqpdf21-dbgsym_8.4.2-1_amd64.deb 698388be504200a8bafdf7696b63afc7 434760 libs optional libqpdf21_8.4.2-1_amd64.deb 60ae819b80c56fd2a78d8de98c01dc26 1256112 debug optional qpdf-dbgsym_8.4.2-1_amd64.deb 9e7bd571b51af3197cf6fab1ba87622a 6361 libs optional qpdf_8.4.2-1_amd64.buildinfo f4a98ab5de3fc54ccc47343e9d9b4af6 419664 text optional qpdf_8.4.2-1_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAlzgEGcPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+ukQQAIXDN5urnjAyLsIQzePa2jY5TSwyimpJxoSk f45stfN7JBPj1/O3Sq3ybm9ndu7J0BwdF/pvYuIPRSFa8tvSxhTJGrl3I08sbbNF DIVVgIso9hkdLIRDQDlO4/FU/gHlWuTjcFRQgFe4EHHJo7rR6OX3wOnsDbUJB9cv j7eF/Z0BbFQneayoMb864skixslIOHw9Vdd02cZ7BlEEGQvbxbmz6HJD1evuPKTi FQL+G2ujhO8BFq0B4Tl8yaN2gjMmFIEOAO+5U0tMrVTrKij96zxDXMReYm0I/7pa dMgckNcqTn8xIk2qFUueFXRsD2lNSny4Q4j34dqD3nN4+9IAIfg061A/wTgngCxu kw8meLSmfge9xpvq+/JdsQWJv9dIxglGsW4ITEFTpMmjSnFssgf/TJM1HiTpsn8h 9jywcSRT1y4AthTvQVMzbdpXIe9Y+kHt5Wq0wE5VvU0aae6SnB73NMNify+lzA3D 1iWtkmSepxdyUwHE02z4KQAvB7ZdNbb97OtbyC4PGpZc1/+cIV8I4QIZQm0hKd/O vZ3HMr9RO5I+icbSpFwc4TdEtXniD3RcXpLew/Ce7gGz0BXMAyTTSEQCRJe76Avw mrJ1ElBfPM6BRSAyadlxOMkdWpudkaLIZ6AdA6qXioyvCMqUtTGbaEC8iJn/sxAK 8GhzgooJ =K2uy -END PGP SIGNATURE-
Accepted qpdf 8.4.1-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Apr 2019 22:13:00 -0400 Source: qpdf Binary: libqpdf-dev libqpdf21 libqpdf21-dbgsym qpdf qpdf-dbgsym Architecture: source amd64 Version: 8.4.1-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf21 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Changes: qpdf (8.4.1-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: c4963d0ad8a48cb69aedad1c8b1b83cea159505f 2061 qpdf_8.4.1-1.dsc bb7e6ee3b9b515b873366fc85d14bcdf00853bb8 16990752 qpdf_8.4.1.orig.tar.gz e3dda59a6fb1ea9ec664e47609439c8ff02ce90a 833 qpdf_8.4.1.orig.tar.gz.asc fb6f24a0674bb9158f694ec7a0cc3bc41065b4e1 13244 qpdf_8.4.1-1.debian.tar.xz 873d981e6a76ffe438129c5967a54f9b0e3faec3 576196 libqpdf-dev_8.4.1-1_amd64.deb 1770bd6c2d2e2c0ee6c41ff1bed1280463736fc4 6839924 libqpdf21-dbgsym_8.4.1-1_amd64.deb 4db89c41a5f0992a858bd9be7ef48556ba32fed6 434260 libqpdf21_8.4.1-1_amd64.deb ecb29ed4ae01ecff29e3c52a06f6a96eb1c68d5e 1256004 qpdf-dbgsym_8.4.1-1_amd64.deb fc1e7ae39f919c10ec153084db0d70176da73850 6361 qpdf_8.4.1-1_amd64.buildinfo 16c6ac1d8fa15a6af5987986fb58e210345e7cab 419516 qpdf_8.4.1-1_amd64.deb Checksums-Sha256: 12c3018cd1c1075e37578ff1bbf9e16ad2647778925783e88d7f59614b628672 2061 qpdf_8.4.1-1.dsc 07fd02b8b32f760ea86c1999f5a67086126437ea854b4064f02c55dbd0f04ebb 16990752 qpdf_8.4.1.orig.tar.gz 78b122a26cdd683e19a0f737966319cb2977909fce3c5c7929fd9fd95f0568c3 833 qpdf_8.4.1.orig.tar.gz.asc 6ef6a2357f3ca25a5086b6625eb1f0882cdbada2d80385c95f0570cfbb8f3b9e 13244 qpdf_8.4.1-1.debian.tar.xz 5e70a2cee83494b0c07961a31a1045c0ac8d32dae6f3817560e647de2359317e 576196 libqpdf-dev_8.4.1-1_amd64.deb 1f8923d45b85322fd5227dee7f8d15ce52097f839d6762783d108f9b9a86f51e 6839924 libqpdf21-dbgsym_8.4.1-1_amd64.deb 0eee95c7e2af027c426a562b266abb8b8837a70f97c2ac46cd2ed7a9b88866ab 434260 libqpdf21_8.4.1-1_amd64.deb 2a65a0f716deea40ef9c00506a1bca2a1f626b41773f3e3978fb76ecfe98e03c 1256004 qpdf-dbgsym_8.4.1-1_amd64.deb 825b629291aa796deddc7da821269a78624e9a828a4c52dde7639a4bf372cba0 6361 qpdf_8.4.1-1_amd64.buildinfo 415ecc37087a6a549f2db37568af418a9102a56c8b01274f77435e607e55f22a 419516 qpdf_8.4.1-1_amd64.deb Files: aa2d61a72d001e2b443f0bdead9cadb4 2061 libs optional qpdf_8.4.1-1.dsc aeec36aaa33d9ded8fd466ae67b9c4bd 16990752 libs optional qpdf_8.4.1.orig.tar.gz ab3d662c20dc45468003777e05e7a1ee 833 libs optional qpdf_8.4.1.orig.tar.gz.asc d94e7c74af40686bdebff54bec8bea6b 13244 libs optional qpdf_8.4.1-1.debian.tar.xz e21f176b5927f10d432412623e8b72c6 576196 libdevel optional libqpdf-dev_8.4.1-1_amd64.deb 6cb40fa486e52f1531defd45b181af5c 6839924 debug optional libqpdf21-dbgsym_8.4.1-1_amd64.deb ac24073070d79c655860125b993d61c3 434260 libs optional libqpdf21_8.4.1-1_amd64.deb 11324af2d11ef248a0d856232c20c9ed 1256004 debug optional qpdf-dbgsym_8.4.1-1_amd64.deb 7d33e5681ad3dd21a2fc3c6a25bf17c9 6361 libs optional qpdf_8.4.1-1_amd64.buildinfo 6cdfebc908329a67d72c27989b328e49 419516 text optional qpdf_8.4.1-1_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAlzFFEAPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+T5oQALaf1wlM9tpLznI+6Cq7IlKwotuK0u2xLk9q CSd2jghiEivJlxhGNo+Fp1FrxedKQAOx4LNlDevtsOAGp447ezX0DCP585ciSD64 kyXwPTf/NNXbyzE4inOEI553OfD0jAVUJel6jyMaBtszUo22EB21xW78hDHg1TpP AM49IwcC061n3shiEbHOT39Lo6IpSU6zbES8DjoE9Bdr7SLNf1G5gx071LrFtFlZ ThXO2jlEFrjNs8HkE/5YDs/7xrdg19fvVuFhqBXKxzJQDk9DDShiGsQ+NsoILW1H vXQ6UsVJpZ+4UbeTc38Hl4K1kkoshDEWmmDXZ0qHVYFsGqfweRog/9rarNALyBOT WKgM6UGq7t3so4a6xpQ6MTAZ00FCGgfBqvxI8LrXRDNPAQnJL/DM4CxHmyT9OrUb zMXE2H1AC3PLQKeUDQPVZepWONTVPVPXndkAhyQZZJDZi6EBjlE/oCTozqblgZjl XnVExy4iP3n8w9Rpw7JjNkvE1iFXn7doXW/yKfuSeCqgpVS6WiBMoyvTlQulRb0M 0dy60o4OMWiW/4p2yER81S1Pg0Ap2sadYs0pcN2EjOfqLndeg/RxyWYegaA/d1iu V1uFkFcAuD0RXdDP2A7/MYJvXA7Gi7+VLRirkEH7r9VnEX0MvHwqW+8ocmReerRF j5p59cjg =P2xr -END PGP SIGNATURE-
Accepted qpdf 8.4.0-2 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 08 Feb 2019 17:43:33 -0500 Source: qpdf Binary: libqpdf-dev libqpdf21 libqpdf21-dbgsym qpdf qpdf-dbgsym Architecture: source amd64 Version: 8.4.0-2 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf21 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Closes: 921722 Changes: qpdf (8.4.0-2) unstable; urgency=medium . * Stop having library packages recommend binary packages. I'm not sure this was ever done or why it took so long to notice. (Closes: #921722) Checksums-Sha1: 454cf22c820a714af201c83c38be60a24d67b5fb 2061 qpdf_8.4.0-2.dsc 70156f613f73052075c88d6b3e74369bef78c588 13224 qpdf_8.4.0-2.debian.tar.xz 2dfc8c901bf823849a9e20de0b07107db5d45c1a 575616 libqpdf-dev_8.4.0-2_amd64.deb 33ac62a25f71c7fef7fb0e02feea1d879f87553a 6855416 libqpdf21-dbgsym_8.4.0-2_amd64.deb 39f4c4083b9b217d83b6e4867c3bfa58e8b6f657 434772 libqpdf21_8.4.0-2_amd64.deb 04f97bfca979e9d6595cd37d4ee651f64f5e8bd0 1257236 qpdf-dbgsym_8.4.0-2_amd64.deb 2acee2be9e050d71364737df8c8b4f7c7edde679 6380 qpdf_8.4.0-2_amd64.buildinfo 894c753b4a26fda1dd6cd506affb4a214f09afd8 413488 qpdf_8.4.0-2_amd64.deb Checksums-Sha256: b044fd546fbbab26b14267532fb8d68abcee17fc56c1c2fe2aaa18a6b7657cdd 2061 qpdf_8.4.0-2.dsc 393bf192b26d796db8f2a6f78bb6f31cd3bd6ca70e19cb856e6fb002ffb53d80 13224 qpdf_8.4.0-2.debian.tar.xz 697ddeaf0109ca3e3c363d38effe084eb22c85653c84b126cd92bc6b7664bcaf 575616 libqpdf-dev_8.4.0-2_amd64.deb c3a8c18e3229b18fdb5551f0484e1207c7e71fd074cd0622f6f4c1707a4510a2 6855416 libqpdf21-dbgsym_8.4.0-2_amd64.deb 4326110031c03c832da22bda1dc97c8eda891cf5285993f3ae4a3ab15ea17172 434772 libqpdf21_8.4.0-2_amd64.deb 395ed613cf0e38848a3f8ffc81b12c8190e5cb0a2bdbe1d7590682e729f87404 1257236 qpdf-dbgsym_8.4.0-2_amd64.deb 6d2c1d16a57cf7e5e622a0e4c68a898e399a9e611012b0ee8a5368ceeef507b0 6380 qpdf_8.4.0-2_amd64.buildinfo 35cbb1057a61f26e92a5fb61ff1dc69932ae228cdbf92432647952cb028e9e76 413488 qpdf_8.4.0-2_amd64.deb Files: 5884344930da21886a87bfcf8d0a525e 2061 libs optional qpdf_8.4.0-2.dsc d537cf3383069393c66dcd13d68f0e70 13224 libs optional qpdf_8.4.0-2.debian.tar.xz 214dd95d280a584a01f588b528b650b9 575616 libdevel optional libqpdf-dev_8.4.0-2_amd64.deb 14d1ed8fc12c25dc827e686deee3bc63 6855416 debug optional libqpdf21-dbgsym_8.4.0-2_amd64.deb 049dfc6da7a65855d493a3844d618351 434772 libs optional libqpdf21_8.4.0-2_amd64.deb 3119d04bc325a21263ee24f26ad257fd 1257236 debug optional qpdf-dbgsym_8.4.0-2_amd64.deb 2125435ad41cbb8a2e0482cf3646dcdb 6380 libs optional qpdf_8.4.0-2_amd64.buildinfo 210b66176b7b71e777d0fffcec1bf034 413488 text optional qpdf_8.4.0-2_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAlxeB7kPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+8y8P+wac5dJcAgJiGz2fyzxDttRyD09/ThAxGmAG WyBo04DxhZvwSxLetgAaiwrrFBjUB7j0hAbLU2LfiTOrg9nHccYbQ/rqUClzL1pY iGmABooxPOSz2JlCOZJtEgE94bEdUKRZCtmKDCa60szYJB0Zmdtzt5KnlyX519Gx VqVYKZFVlwG3x9H0wCrB7PGMMGAaKKSnf4RIZnVPF3WsJifU/VY5Nw8PMYq7AvHL NQEFH6kWfgAelHCUFzUPNbvkMF2TA1QGLcgD6nZjZVH7wu1dhzePqBwTlxA5PrlE cIkJppyl/Yn9E217DrTeUqEAO/OL4i6OWxEbZnF2wov1zi/ALFck2+Lks4Sjvwxz R90NtOga1h2ThtbS9BQBxeUZnB6A3TFGlZQhIxnXfs8mGABI/MYiohLcgLsBj0hD Jl1HzHpRvbxwoWXi7Jxjo4BM4CsYMeXo7FBRe205j/PJ67JDGXlOCBgAZIKgvqxO kIH4dI7CtAu0hbnc4iuQEAzmAeV6QMv3GZ05kfsVl3OUz4qctm1UdS/iSKUYDXzk 7hj2a0/0mgAiA5tGVvtp8/SiBI16PC7L8luR5sU8nGb0l14fEcK+Ruc+mihZnkzU EamQC2Menr/jqpHOSC6l7MryywjTwLER6DdPXXyC+2j+C5s2q0uPuKyC24D8+OpA 400twCSJ =RWg8 -END PGP SIGNATURE-
Bug#921722: Please stop making libraries recommending qpdf
Definitely a bug. I have no idea why I did that. Probably a cut and paste error when I first create the package years ago. I will fix and upload a new version. Thanks for the report. On Fri, Feb 8, 2019 at 7:39 AM Laurent Bigonville wrote: > Source: qpdf > Version: 8.4.0-1 > Severity: normal > > Hi, > > Are there any reasons why the libqpdf Recommends qpdf? Does the library > use an executable contained in that package? > > Kind regards, > > Laurent Bigonville > > -- System Information: > Debian Release: buster/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, > 'experimental-debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_WARN > Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), > LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy > > -- no debconf information > >
Accepted qpdf 8.4.0-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 02 Feb 2019 09:42:59 -0500 Source: qpdf Binary: libqpdf-dev libqpdf21 libqpdf21-dbgsym qpdf qpdf-dbgsym Architecture: source amd64 Version: 8.4.0-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf21 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Changes: qpdf (8.4.0-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: accfbc7b4a48e567e007ef8e77c307127c5588f4 2061 qpdf_8.4.0-1.dsc b16325a88a09ed4b0684e569f060c406f8b208ef 16981811 qpdf_8.4.0.orig.tar.gz f98bcf5c5eb4d774eb8076da50b5983c9b238326 833 qpdf_8.4.0.orig.tar.gz.asc 479471153ff5a355ca9c353cb70d90b5dcf2174e 13168 qpdf_8.4.0-1.debian.tar.xz 4425c0bde705e4729cf4406439e507e640075065 575304 libqpdf-dev_8.4.0-1_amd64.deb 2edb0bb705ebad977de9717f335d54f4ce3a4ed5 6855348 libqpdf21-dbgsym_8.4.0-1_amd64.deb 2e242116361311d4deb1c4b66901f38d7a854a80 434132 libqpdf21_8.4.0-1_amd64.deb 129d961c9e0bb4b9f95f9de56c0b8c4738754040 1257364 qpdf-dbgsym_8.4.0-1_amd64.deb 87e5e68bfb1c9a3d7c812e7e951a071c9205c3e9 6380 qpdf_8.4.0-1_amd64.buildinfo e3d94ee2c41d883df14e9819cd2ebfa226291301 413364 qpdf_8.4.0-1_amd64.deb Checksums-Sha256: e337add91c72c3f0679ec31d232d5c45ebc063bd6b69a857d4dcb367be8604cc 2061 qpdf_8.4.0-1.dsc 39018f3bff700c68e41f6d44ea9f7842e2a5af200a80b2cdec7fa32a4abac4a0 16981811 qpdf_8.4.0.orig.tar.gz ede2199865bea24fb3cdd20894032cefbd4a53b50e40d54d00732a2ce166eb09 833 qpdf_8.4.0.orig.tar.gz.asc fd33cf98cd17deac4473583ac44024894cdb2c8e3bd42ae2ff56f821c143bde8 13168 qpdf_8.4.0-1.debian.tar.xz 15c5b66e984c633377ade3d4d5b27850aa0a8e32bdbaa310d22ad60d4291ff9f 575304 libqpdf-dev_8.4.0-1_amd64.deb 328437f553773475c2d8a64e11aef81b5a485f4767e9acc8edc4158334a4c431 6855348 libqpdf21-dbgsym_8.4.0-1_amd64.deb 9084bcc3ad23fbeccbae4d792bc5225be4b6e805dd781f3a803b38e30a2818d6 434132 libqpdf21_8.4.0-1_amd64.deb 0a0df88dd7421c8b2658e96ded67a1b756a59aa9e52f31a2b0f968893236477a 1257364 qpdf-dbgsym_8.4.0-1_amd64.deb 1e4dd5570678b95e44ebefa0dc7650a68bbaf73a3cc25eea6a3c19aeadbde363 6380 qpdf_8.4.0-1_amd64.buildinfo d195ced87872df43d4ed5c535efb6f2e2adac45d83b89fb284a22a60c2689133 413364 qpdf_8.4.0-1_amd64.deb Files: b8294af3cb09aad0800a306197fdbb8a 2061 libs optional qpdf_8.4.0-1.dsc 60a66cf8cbdb3bb0d3bcf5b2f53ec06b 16981811 libs optional qpdf_8.4.0.orig.tar.gz 55b3274697a158c118ab115522df3fee 833 libs optional qpdf_8.4.0.orig.tar.gz.asc 64e499b3731a347117c71efba926512b 13168 libs optional qpdf_8.4.0-1.debian.tar.xz 8e19ca9f8c4ce230c5beaa6a111aa66b 575304 libdevel optional libqpdf-dev_8.4.0-1_amd64.deb 80d94dc11e33b0ece59d6e0af01dc113 6855348 debug optional libqpdf21-dbgsym_8.4.0-1_amd64.deb 12d431a2be5822ef64966770a8961d80 434132 libs optional libqpdf21_8.4.0-1_amd64.deb ae6dd180dbf49619ac423bd2aaef5733 1257364 debug optional qpdf-dbgsym_8.4.0-1_amd64.deb b30ab71c6075d762908d78160c3d1ce2 6380 libs optional qpdf_8.4.0-1_amd64.buildinfo 4322cef4a0cf580c89d1e7572a40b8e5 413364 text optional qpdf_8.4.0-1_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAlxVrXYPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+8SAP/3X9ohZujbJasFLQRxscCeloPrWYQzB8OtkS 7p8CjkGH/15MN50PWjyGrL8KJXeujMQ6deeKY3kcPaCsXdaWVag7X7LODZAbTyrP imV5FsbwEtjbQN1twdxIZ1JABbIHDXsudOprRDhw4ldO1LOz7+Yqh+al7B4lhlxh JUabUXRr0hHK7xNBg9E0lQriZwIf53W7t2I275uhS4QYzQTjM4EPYtlKrb6epO9/ kRnmSj8seKoaucGF7y+ssKplT8GX6k15cDPPH2oqf/7/apTuwgz1Ar1P/caoNRKh KOY+WNuJHn0nvBLVWDXcs+J9GUxZJIOko0S8vhiCtKtZVWg/22qRNU3xrNqbWb6u +ENCXS6zRw8LekudSw8YmcVoXDEWIy3rfnTLQ9o55GxeMcjhBJr6KPLeuRWDmq2a VoVzTRpZLU4stvdWXCYJsqvZguDzYtM88UGlMUJukfDAgycgjshCrG6Rv3nBBYcm 1kFoel081r28euMWFcR1SJEU2th7tN7cm/z9BDtFDY3XkBu2w3Z34jalyaUdB2xW 3p1e3ECxAvKrwUglyl3gLkPjy9YhdGokP2VGs29XJwfJkl6hWVEQ3jprNJKOPfr3 4opNTBg/qkbSAG1uKh2KylPXsH5/XjGiE4ibQWCqcDTk4K/r/hdLfVUs/KVPys/K gpBkYMLs =sjeB -END PGP SIGNATURE-
[Desktop-packages] [Bug 1564249] Re: Cannot print a PDF with AcroForms using fit-to-page
I think this bug can be closed now, right? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1564249 Title: Cannot print a PDF with AcroForms using fit-to-page Status in cups-filters package in Ubuntu: Fix Released Status in qpdf package in Ubuntu: Triaged Bug description: Using KUbuntu 14.04. I am trying to print the attached PDF with filled forms (AcroForms) with the following command: lpr -o fit-to-page PDFForm3.pdf But my Samsung ML-1210 prints the document with empty forms. If I omit -o fit-to-page then all the forms keep the filled data. -- # lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 # apt-cache policy cups cups: Installed: 1.7.2-0ubuntu1.7 Candidate: 1.7.2-0ubuntu1.7 Version table: *** 1.7.2-0ubuntu1.7 0 500 http://ftp.byfly.by/ubuntu/ trusty-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 Packages 100 /var/lib/dpkg/status 1.7.2-0ubuntu1 0 500 http://ftp.byfly.by/ubuntu/ trusty/main i386 Packages CUPS in Xenial (from here: http://cdimage.ubuntu.com/daily- live/current/xenial-desktop-i386.iso) has the same issue. Xenial: # lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 # apt-cache policy cups cups: Installed: 2.1.3-3 Candidate: 2.1.3-4 Version table: 2.1.3-4 500 500 http://by.archive.ubuntu.com/ubuntu xenial/main i386 Packages *** 2.1.3-3 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1564249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1564249] Re: Cannot print a PDF with AcroForms using fit-to-page
I think this bug can be closed now, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564249 Title: Cannot print a PDF with AcroForms using fit-to-page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1564249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Accepted qpdf 8.3.0-2 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 17 Jan 2019 10:52:00 -0500 Source: qpdf Binary: libqpdf21 libqpdf-dev qpdf Architecture: source amd64 Version: 8.3.0-2 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf21 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Changes: qpdf (8.3.0-2) unstable; urgency=medium . * Fix potential data loss. The change is already in master. Details in https://github.com/qpdf/qpdf/issues/276 Checksums-Sha1: cc18ce216c30a47cea166777c6b6b4d321dd3834 2058 qpdf_8.3.0-2.dsc 9c3e2723aec692c45516977c24e54ac485467fa1 13544 qpdf_8.3.0-2.debian.tar.xz 176d350294a9c6e08764113ee6887f9851f4ad26 547416 libqpdf-dev_8.3.0-2_amd64.deb 8ef2f5132a997733cce238d5758432a9ef85c031 6543872 libqpdf21-dbgsym_8.3.0-2_amd64.deb 8b3759b1e1bd8b9640f051291c15aa1b005cc22b 414984 libqpdf21_8.3.0-2_amd64.deb 9a774bc5d86dfe4d8734f63fd042b50a4e8f037c 1085844 qpdf-dbgsym_8.3.0-2_amd64.deb e6ab2559f4598a445909fe67217848bd5729f3d2 6386 qpdf_8.3.0-2_amd64.buildinfo 50d76b83b4b804dab1621bc165869f49379c9f9a 370072 qpdf_8.3.0-2_amd64.deb Checksums-Sha256: 68e6ca17ce8cd3c296bf0f2265cfcbe337536f34c0a9bc4db2afda188d41e7e8 2058 qpdf_8.3.0-2.dsc 95ccf0319e09161f5f50f3b2c0fcd35dea1a24e9b43d54f5654ada8e2a5e35f2 13544 qpdf_8.3.0-2.debian.tar.xz 7161b22dc6297ebcb9b01d95b8cb5d133c9978242d81ad0202855b24fd8c500b 547416 libqpdf-dev_8.3.0-2_amd64.deb fefb888c15769362b5806bbe96bf0e29450978be0a1f7b0d933559648f554b7b 6543872 libqpdf21-dbgsym_8.3.0-2_amd64.deb 065b89bab9cbe9c9eb9eae9ffb57817fd9c3047675f82bfabaa9c8f6333a 414984 libqpdf21_8.3.0-2_amd64.deb 2303e8da7aa930a8fa91468d6655c80e144ad56e831e17c7ce60459398586655 1085844 qpdf-dbgsym_8.3.0-2_amd64.deb b19ce186106556049673af0fde1e7ae651b428fbb93ebe6ef920728e8c44f8a6 6386 qpdf_8.3.0-2_amd64.buildinfo 7779b749f50b8d98d05ab1d23ceb063650fa24b5e3528553ce8a1f10635004b6 370072 qpdf_8.3.0-2_amd64.deb Files: 9df3d936fab1fa4e8b4c9f1faf0fb751 2058 libs optional qpdf_8.3.0-2.dsc 99f00afc4ead6e81e8144436fcd0d0bf 13544 libs optional qpdf_8.3.0-2.debian.tar.xz b4ff97d3605472e918a635066b1de0a1 547416 libdevel optional libqpdf-dev_8.3.0-2_amd64.deb fd24ace034c6810e05efa9fc496245e7 6543872 debug optional libqpdf21-dbgsym_8.3.0-2_amd64.deb 632f8ebb4ba6c1659f679cda6a3d90a9 414984 libs optional libqpdf21_8.3.0-2_amd64.deb fa1bc91579d164fe5cc0996d28b4ea1c 1085844 debug optional qpdf-dbgsym_8.3.0-2_amd64.deb 417e3fd41410e506b9fed3c5f22e1374 6386 libs optional qpdf_8.3.0-2_amd64.buildinfo 60694f1fbca012f913a96d071f374dd2 370072 text optional qpdf_8.3.0-2_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAlxArZkPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+J9QQAI+L32Ba32H40Y0Twg+FCkkqZ5ixjCIzTYYW WYvnfmlB5fWqcObYkI1cO/6eVyYDxshUPwnmgTJZ7RVos/uMC5FtzZrHxP1Vpgf+ qgwXMdh/YW9/5crEmKsmRlc9AEb41M1X07i7dRHYK9hnweO4p8y6tIMHvGdbUwA1 ebHAHIUOPyquhlDxIWmfEMNcGjVa8K88yifNI5Hy7gQ5WvxBo9Q3/8bV2vNos3hs lWyAq10MkYR+WzZpt12zmo9KvT4OOiXUQDQo1dWxrovxSnH378dwumjVYdO+OtBR PY26KVqA/KW08EeYpgtqpB3s/POPDlOpZhq/SEISI8MlJCyKLBOo6uEdzdVcabIP 9DCCnyFwFqfPGDrpMPhmEuAOSC+EcLjYGP0BAsPZFKJB7b1XTevprxADdJU+xj+J 41/BhA3vrLHvXxqzxmMmatSLD3Wpc3xSjXqRJLqg2n0h0ZBbQsJ5P7ZL3OFDWlfB ahKQq4urrz7zLmWP5wKW8MVgmRxp8ULoHbx3Mdrs2hu9SSP2u+tI8a5ffjouPUtp hgCp/XAfpTW3l3h5OIyYahiz2tMIM/SO024MEL98nRb4cRHTFCIv7YTI/dO/PCm2 /pFN3pn/ukYbD720e1o9PS66LR6cYjAV5XMtOrbUOAGuW5cP+93SAFgjl+MFY3B6 jKPyU76z =aZSB -END PGP SIGNATURE-
Accepted qpdf 8.3.0-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Jan 2019 18:47:47 -0500 Source: qpdf Binary: libqpdf21 libqpdf-dev qpdf Architecture: source amd64 Version: 8.3.0-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf21 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Changes: qpdf (8.3.0-1) unstable; urgency=medium . * New upstream release. * Install bash and zsh completion files. Checksums-Sha1: 2a85b95755e523e850b2d956e832895de354809c 2058 qpdf_8.3.0-1.dsc 34860254880bcde07d188cf57ccd01d0092ff963 8915504 qpdf_8.3.0.orig.tar.gz 37e09f9cb1deaaf3e35f60f60c2613562ea3c08b 833 qpdf_8.3.0.orig.tar.gz.asc 56e88b4f080cada39fd2dc7cdc2b43a3638a6a95 13088 qpdf_8.3.0-1.debian.tar.xz be16aac34daf6b07fef10a9304451a08a47c7c11 547484 libqpdf-dev_8.3.0-1_amd64.deb 8b009f53fe2bca98caa9c1c1a544600a0d1818a5 6543780 libqpdf21-dbgsym_8.3.0-1_amd64.deb 578c838958d36398f74ca1d530e5dfba1d4fbe44 415200 libqpdf21_8.3.0-1_amd64.deb e01502e4b05abc01f31bb7f187fb997d1d829f39 1086040 qpdf-dbgsym_8.3.0-1_amd64.deb e74ef3593d2c78c411b492ef4960e27e5fefd56c 6382 qpdf_8.3.0-1_amd64.buildinfo 4673bb38a4c06d6dc94748ddbafb333028b7192e 370136 qpdf_8.3.0-1_amd64.deb Checksums-Sha256: 09fc23d819a30110b5a05ae2c50f4d27348812e49138028f36b5ad38f1effbff 2058 qpdf_8.3.0-1.dsc 46c2a10690b86ba680db1c828e9ce44bb8e2993f69aa96d5a52fd1d98dc391f7 8915504 qpdf_8.3.0.orig.tar.gz aee90d397dc8bd6dff2d667f5085c5e13122d67bd24b6e0f7afffc2b010f3004 833 qpdf_8.3.0.orig.tar.gz.asc a5010cac09bd33250e8a6ac6c5d5d4bafa7a9a30c077a926303282b71219b9fb 13088 qpdf_8.3.0-1.debian.tar.xz 7e69e658ce6fee15e3fe1ee4c01b3f49ed1f02a48f07405384f6f93c061483f0 547484 libqpdf-dev_8.3.0-1_amd64.deb 78daccd271b7a33e3257787597ea47123ecb7fcb7741419c0cb9c1c8fab674f0 6543780 libqpdf21-dbgsym_8.3.0-1_amd64.deb 7396be5d4ec1689ed77376f046cd6dfb3b2c739bbdd52837606f2f40acbff9f3 415200 libqpdf21_8.3.0-1_amd64.deb 618d7ff6a15ce6f5595551c7575ee80873de767a239aca9acf32c45c4aa24349 1086040 qpdf-dbgsym_8.3.0-1_amd64.deb 57a44335a923b7c690a9ac9d3eed3590e2b5bd5be221efe25770a0e9b3efc6ed 6382 qpdf_8.3.0-1_amd64.buildinfo e0abf0a0cb6abbcc45f840d3a230d401d4807e4d982ea310576cb46862b7f359 370136 qpdf_8.3.0-1_amd64.deb Files: 2422fba42efa1fc31afe2fdbdd6cb992 2058 libs optional qpdf_8.3.0-1.dsc 4df89ee9b32c48839b8e76f51115451c 8915504 libs optional qpdf_8.3.0.orig.tar.gz 1aa6df3cdf2eccee9157fce2fb2eaa66 833 libs optional qpdf_8.3.0.orig.tar.gz.asc bc67370d70f5a9967dda03e336a22cb9 13088 libs optional qpdf_8.3.0-1.debian.tar.xz 36e5d192b8480d3a0034cc629ce66c30 547484 libdevel optional libqpdf-dev_8.3.0-1_amd64.deb cbbb049d174da2a1b571cb70cb5113e9 6543780 debug optional libqpdf21-dbgsym_8.3.0-1_amd64.deb f39af6b1f764c6456d4313d24148bb64 415200 libs optional libqpdf21_8.3.0-1_amd64.deb c62d01ab710acd02ad57bb4e5b96443b 1086040 debug optional qpdf-dbgsym_8.3.0-1_amd64.deb fdaaff067e703dc2d5174410b5ae31df 6382 libs optional qpdf_8.3.0-1_amd64.buildinfo 2b29c429fc67ce09da185b658afcf883 370136 text optional qpdf_8.3.0-1_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAlw0ATQPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+13MP/iRm5HLsYqIgTbKcgu3bhHiko0VpGpW7w6Mj Pdk1rjwBUGn0MtBDsRYuWNAHKIDV8qKPAuquxr5SBlWfvsk7bNwuGyOfyFw2+ut4 Gzz49evZLiT06H2vPjeFckVtWA3xluNqOq0+Z/U4IuPGrCEqhHdWHRdPLqXqONf0 c3GaeCnnsEdTrpLneCOXG4KdGPtzDVmd6EWqWX9MVO8ocH+q3C+I7TqFVt2Ob5Xq Y/q6fx6gAIXKDDSkdTTYt3ENpiUaFxHKsUpPlU4glvQqWh52YhmS+xIxxlmCEvGD LBIpUgo2N4p4zfnfJg5VYZvxx9J23wNgzNeQKnWdsgFvhPJdKjnUrQUftOkvm8pS 4IDmsVF7CcNEM4XCRG5EaPfYjgx5Xj5id9XOu0Tdt7eqbDflTVjrQoeCCzRRB+QJ kFlEWMKZEcWyWmjkIjtGXTeVa8wbERCh3CIVAOhapiRGHzq+dmKEle5HOif25Ybm 89cwwA+KCM2TWnzDMv1NMRdGYaK3shWPCqcUIM5iS+eSq58BZF5IR+UPhH1xJj14 FNSvYp1IfSHL/MtUnC82sesBP5Ner9EakMk91m86HLnvscwPXJ8le4mwKVwt3sbL fdgYi2oG80/4ryhdwKec+nrAG8UvP4Q0jy2vorwFZVEcf7xtZTaxX8Ja4ZTBTI6J Wfm9/ZSR =knc+ -END PGP SIGNATURE-
Bug#238585: [Pkg-sysvinit-devel] Bug#238585: changing submitter
No, I think this has long since been overcome by events. Please feel free to close. We live in a world of systemd today. Thanks for following up. On Sat, Dec 29, 2018 at 1:33 PM Dmitry Bogatov wrote: > > control: tags -1 +moreinfo > > Dear submitter, are you still going to implement your suggestion? > > [2008-06-11 18:35] Petter Reinholdtsen > > > > part text/plain 448 > > [Jay Berkenbilt] > > > A quick perusal of the code suggests that it should be a pretty > > > localized change. > > > > I would recommend looking at how SuSe and Fedore does this, to see if > > they got some nice ideas. In SuSe, I know that parallel booting is > > disabled when interactive boot is activated, and I suspect this is a > > good idea for Debian too. > > > > And yes, a patch relative to the latest svn version is prefered. :) > > > > Happy hacking, > > -- > > Petter Reinholdtsen > >
Accepted qpdf 8.2.1-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 18 Aug 2018 11:21:48 -0400 Source: qpdf Binary: libqpdf21 libqpdf-dev qpdf Architecture: source amd64 Version: 8.2.1-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf21 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Changes: qpdf (8.2.1-1) unstable; urgency=medium . * New upstream release. * Change interpreter path for fix-qdf to not use /usr/bin/env * Update standards version to 4.2.0 Checksums-Sha1: b966ec79d81bd02d12e44366c9c816522ffef16a 2058 qpdf_8.2.1-1.dsc 54d9597eaa739d9da5c9e2afab439f1704eb6560 8256216 qpdf_8.2.1.orig.tar.gz 1beb269d0a984d5934e31b85590d872bdfe9da53 833 qpdf_8.2.1.orig.tar.gz.asc eb1e5b0bea61d509d47f3a4bad1a9c05a78eaa4e 12924 qpdf_8.2.1-1.debian.tar.xz 77c33bdfdebbf9764627873bb185f446eef2fe5c 468700 libqpdf-dev_8.2.1-1_amd64.deb 5ac2e32ae08432b7799f597c2f0fe4a5757b012b 5266112 libqpdf21-dbgsym_8.2.1-1_amd64.deb dfd5b69c944657a51783aab91688d6762677 357144 libqpdf21_8.2.1-1_amd64.deb f60ebeff1efbb6d9f950ccc1f257fe182af90886 547824 qpdf-dbgsym_8.2.1-1_amd64.deb 99885af9988bc4b8f83587857ba646b392fce771 6697 qpdf_8.2.1-1_amd64.buildinfo d494d87ccbeb23385e6117c71ed470bd2e75db0d 292972 qpdf_8.2.1-1_amd64.deb Checksums-Sha256: 4b2f300bcbf41f8f8be5399e880b16d0f83d7cb821d68cbfe35e66f2e5f52568 2058 qpdf_8.2.1-1.dsc f445d3ebda833fe675b7551378f41fa1971cc6f7a792194d3a71a404abc9 8256216 qpdf_8.2.1.orig.tar.gz d466fd36687391124b2242ba202e82f9abb71f365d67ae4785adb0a9eea859ac 833 qpdf_8.2.1.orig.tar.gz.asc 067493e8e46a98bcb75402740967f4b5625b0abd629f5352c25296ee04bdbb34 12924 qpdf_8.2.1-1.debian.tar.xz e5b73ecb6671fd716d75f92d06c5ffbbae45c58d2bbb908b1da471cac4492cb1 468700 libqpdf-dev_8.2.1-1_amd64.deb 53b3effc4f8d670b0ead54caac583db2b31da45ac3247190702feb17f9e7100c 5266112 libqpdf21-dbgsym_8.2.1-1_amd64.deb b812c6be049958b6bcdf16b0764fa48d08215e46ea5d1293a5e894f2227dc5e1 357144 libqpdf21_8.2.1-1_amd64.deb 07d8c3f1982e3992ab1f846feeda9667a7972fb0d382502d6ee83ad18df293d0 547824 qpdf-dbgsym_8.2.1-1_amd64.deb 6e61fea6fee257d55c6253a13883c12c95dd723c57f1264ac377e5b84e82ac93 6697 qpdf_8.2.1-1_amd64.buildinfo c3fb5376343bc02cf4d45f9301729049a2bcb5533437a5140eee76c15aa32d18 292972 qpdf_8.2.1-1_amd64.deb Files: d0065b2a0505ae8a8e2be2b8753dd95e 2058 libs optional qpdf_8.2.1-1.dsc a11c1f99753934be7d60c0ab43821bbc 8256216 libs optional qpdf_8.2.1.orig.tar.gz 01c9be8c277f1377a705689642753a85 833 libs optional qpdf_8.2.1.orig.tar.gz.asc e1293fb4848e8ec8c76289a6ae3879b6 12924 libs optional qpdf_8.2.1-1.debian.tar.xz db865d76ee66f32c709d37fe38b8597b 468700 libdevel optional libqpdf-dev_8.2.1-1_amd64.deb fceb4f6946e1d1b5148c11a0bb24a8cd 5266112 debug optional libqpdf21-dbgsym_8.2.1-1_amd64.deb 274bbee3146dd8c99b44dd056b1e322d 357144 libs optional libqpdf21_8.2.1-1_amd64.deb e904af978579324bf54bacaf568cee40 547824 debug optional qpdf-dbgsym_8.2.1-1_amd64.deb c25131fe81ebb63a97bf38fe112d 6697 libs optional qpdf_8.2.1-1_amd64.buildinfo a1831ba867f6cc64f086ffe3dbb61e6a 292972 text optional qpdf_8.2.1-1_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAlt4OwUPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+9+EP/iNJS1iXDUS5zFvqXpA/+lbdOcScJZQ+iS1+ 1dBUXxliB+bi8ruBR9y0nHQnSVYng6PsL1cX4aCSjYzpMNUzG2c6S8ouzhFD2uMG w4D4yfZaJZNi3iyHq7Plop9+8d9AO3SBzUZpctJ55rDUHnGwusp1ozgsB9VyRQRx bVjxkm8Rk1dYiIwfSn0idxgryydEOmAvdrH4vi8qq9Mx87Cw59ZtMnYdSbTEC+AH NRXicPO83iZXE3EG73inVUxSGGND1sSa5RUXPLBPC1LPW4cBBJkrr3D6qP5BVGWz tRqsmUYYLMGG0i04XelOoh9iYOZ/ghRvFM+Ub/4cgyOQeEm/17Z40BqtRT9v+RtN tmRTTnY0TPaK9yZP8zIfZh1LAPgpzK0FBxRprc4RR/NlUALw6TXWz9U2CkjJQXlA 71XUkE5M2ntlj357aR/cJ2IXQ7TGd3jzVgnPEXv2ACFcor5CZRnNGkaYCOy3VOg4 GGnczDQIra5r9yaFFc9IuVm4DfX1XsLNOKXoCsswuf4kE6tjQ8yeABK8Kk4O973L Y1vfeUT5KuIAqDwMah2kyDZfxUn8iJ9gD11gDwcWFloGwueJ1sTm5QDLWSqHHl2K QHc0YlP1IbqWYbXRUpW79MgFHcvZPxfBErF+m3l9rzN0uhaiH0Hk/r0AQ9PPY2xn VvwXGU2o =1WK9 -END PGP SIGNATURE-
Accepted qpdf 8.2.0-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 17 Aug 2018 21:32:53 -0400 Source: qpdf Binary: libqpdf21 libqpdf-dev qpdf Architecture: source amd64 Version: 8.2.0-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf21 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Closes: 902642 Changes: qpdf (8.2.0-1) unstable; urgency=medium . * New upstream release. * Includes documentation fixes reported as debian bug. (Closes: #902642) Checksums-Sha1: e820378291c01e15db37035d62a93ad71e0e1360 2058 qpdf_8.2.0-1.dsc 8dff630fff190f4dd5828f984ad134feb5eaa545 8250327 qpdf_8.2.0.orig.tar.gz f00cf3817f9d858c500e5723a2ebf888dc50d81f 833 qpdf_8.2.0.orig.tar.gz.asc a765a1d5dc7f5ffa76d8f9115389e03c8fdf4e9c 12752 qpdf_8.2.0-1.debian.tar.xz 3ad54c3727439244b9c9bd9be8be1a3d045c5743 468396 libqpdf-dev_8.2.0-1_amd64.deb 2d3aae84a309ca8cd9e64a8f38531c7e95fcd078 5266092 libqpdf21-dbgsym_8.2.0-1_amd64.deb d3eda9073a2d9064d8fb6694bcb9522b44589865 356600 libqpdf21_8.2.0-1_amd64.deb 226f0901e1b9dde4d6427b4253314232da95f6cb 530612 qpdf-dbgsym_8.2.0-1_amd64.deb 2337205fe07a1ab2c260116062ddca231b4002c6 6697 qpdf_8.2.0-1_amd64.buildinfo 1a5830d15e4b3bba1cced4906a4ae1d98a68304e 289656 qpdf_8.2.0-1_amd64.deb Checksums-Sha256: 2f5474dd8262ef9b78f18269ef06e3eba63e48fe434a9634c554dbdd24dcd2f2 2058 qpdf_8.2.0-1.dsc debf7fd07b5336d8e772f6f6d090b124353f99d8b74030dd0feefe7a11e35cbd 8250327 qpdf_8.2.0.orig.tar.gz e9e41bcd4e28ea46c260d3b7a7760115d6a9046b95aecf6c7d0ce073ad43cd9b 833 qpdf_8.2.0.orig.tar.gz.asc 43757e8046ed4955e2bdf8b179bb247ce79051bc95e697fb232860e2cddb6741 12752 qpdf_8.2.0-1.debian.tar.xz f4f29678b08da7b6446cffb7ab89ebe25af5fc0a47a2299bb3f70aa06670845d 468396 libqpdf-dev_8.2.0-1_amd64.deb 124d348fcdce41756057ee2b62d22d85e496d1ca667b1bee1ec30ec2aca7d645 5266092 libqpdf21-dbgsym_8.2.0-1_amd64.deb 011093d62daea967eb8217e7cf792b3ee9e8792316f2df8840fd9fd6cf114fa9 356600 libqpdf21_8.2.0-1_amd64.deb 7293e6094dc7ebf6c930c8cb7d4f5b91015e69e1062f18f22c65382f246b8a85 530612 qpdf-dbgsym_8.2.0-1_amd64.deb 2a8974edc1b95c74afdd50bde388980f9a776eee4b4d326567066ea4520eedb8 6697 qpdf_8.2.0-1_amd64.buildinfo 48062315c7ce469dd32b93cf2254c511bf69a9689ca804fe54754332230a5b00 289656 qpdf_8.2.0-1_amd64.deb Files: aa732531fda353346ae5b51c0085a28e 2058 libs optional qpdf_8.2.0-1.dsc 5e8c98a7123800d9081d9a9a09acacdd 8250327 libs optional qpdf_8.2.0.orig.tar.gz a09f699f3a058acda6857ebfc5ec8a30 833 libs optional qpdf_8.2.0.orig.tar.gz.asc dcbc1de2defb870aa23544364a6f82f5 12752 libs optional qpdf_8.2.0-1.debian.tar.xz 548406025e9d7d26f246ee408245f9a2 468396 libdevel optional libqpdf-dev_8.2.0-1_amd64.deb ce83b782b7b7e459e623721713b9d328 5266092 debug optional libqpdf21-dbgsym_8.2.0-1_amd64.deb 296b15b80da3e6402c788d0986e3ed36 356600 libs optional libqpdf21_8.2.0-1_amd64.deb 80ebde5d4f569ff0d6c99b36d3f3111f 530612 debug optional qpdf-dbgsym_8.2.0-1_amd64.deb 1aa87e2a5608563798c6e80ba2ac498a 6697 libs optional qpdf_8.2.0-1_amd64.buildinfo 1918701ca57008cb5a148fe8af2a86f2 289656 text optional qpdf_8.2.0-1_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAlt3eXEPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+GDwQAIZAgMQS9WXht8U+dEl1jVpnR8fHqRd8QeoQ 9Vym0G2Qp17R7tB1dlbtpwLJCbXbfb48LNxNgGx70W+tj5IXKpV3QVNN5cKp63nL jwroLLn3smRQ6iLrDl/H0ye4DkwPl/IEQoI2JE10gXSI9SWkiGmGKEkMWD8QGwuy xancLFCZ+L6tL6MtUKMhPs4N8pyumHjNEiGEiYLqCc1OYStv7sinf2zbn1RBm7fN 5izKNo++7TNfpH2qYW+3oSqdS4XQpHxob0JnkuTtb1Z2pOMoNbxJ2r79RNWsxEdK 9kc84cl+RkoLSiqlrFx4X22BN3+2qll6dXBw3vN8rPHPlrrtO0Bs0uQ/kVacZDEy 8ftT3K5Min0q2YDjHFIN67ptIdUxBW2lhqC3BDG2gzmTjioB8xFNsGDzq0Po6niB f/ikXDFCeMN4quxpEGlZv85YHgTJBa/BgmfPOABpFP6/BHRQCcgvKvWMLmXuaUg4 HZH0rmsEdZNWAbHa/2waOliRALpL/qH6+ETn1jMGeAeD86J4mbL/uhdTHol+72qb uj/iP/9LF4FuSyzVllCBuXZkevxhAkFMzkId0r9X/16DsF+jbL8r32hLldzWDrCN GpXG93jDL53saEAlRJ+/F5BjSEyOoWkg+NG7jb0TIJyJ6m5btfMKYMmudJsTGO8G HzsCVsqb =ppnI -END PGP SIGNATURE-
Bug#902642: qpdf.1: Minor fixes to the manual
This will be fixed with upstream release 8.2.0. Thanks for taking the time to report this and for proiving a patch. On Thu, Jun 28, 2018 at 8:15 PM Bjarni Ingi Gislason wrote: > Package: qpdf > Version: 8.1.0-1 > Severity: minor > Tags: patch > > Input file is qpdf.1 > > Add a period in front of the first two comment lines, otherwise troff > creates the first page to be empty. > > Test nr. 13: > > Change -- in x--y to \(em (em-dash), or, if an > option, to \-\- > > 18:\fBqpdf --help\fR. A complete manual can be found in > > # > > Test nr. 21: > > Use a macro to change to the italic font, instead of \fI [1], if > possible. > The macros have the italic corrections, but "\c" removes them. > > Or > > add the italic corrections. > [1] man-pages(7) [package "manpages"] > > 8:[ \fIoptions \fR] \fIinfilename [ outfilename ]\fR > > # > > The patch: > > --- qpdf.1 2018-06-23 13:17:28.0 + > +++ qpdf.1.new 2018-06-28 19:28:31.0 + > @@ -1,11 +1,11 @@ > -\" This file is not processed by autoconf, but rather by build.mk in > -\" the manual directory. > +.\" This file is not processed by autoconf, but rather by build.mk in > +.\" the manual directory. > .TH QPDF "1" "April 2008" "qpdf version 8.1.0" "User Commands" > .SH NAME > qpdf \- PDF transformation software > .SH SYNOPSIS > .B qpdf > -[ \fIoptions \fR] \fIinfilename [ outfilename ]\fR > +.RI "[ " options " ] " infilename " [ " outfilename " ]" > .SH DESCRIPTION > The qpdf program is used to convert one PDF file to another equivalent > PDF file. It is capable of performing a variety of transformations > @@ -15,5 +15,5 @@ options for inspecting or checking PDF f > useful primarily to PDF developers. > .PP > For a summary of qpdf's options, please run > -\fBqpdf --help\fR. A complete manual can be found in > +\fBqpdf \-\-help\fR. A complete manual can be found in > /usr/share/doc/qpdf/qpdf-manual.html or > /usr/share/doc/qpdf/qpdf-manual.pdf. > > > -- System Information: > Debian Release: buster/sid > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, > 'testing'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.9.110-1 (SMP w/2 CPU cores) > Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), > LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1) > Shell: /bin/sh linked to /bin/dash > Init: sysvinit (via /sbin/init) > > Versions of packages qpdf depends on: > ii libc62.27-3 > ii libgcc1 1:8.1.0-8 > ii libjpeg62-turbo 1:1.5.2-2+b1 > ii libqpdf218.1.0-1 > ii libstdc++6 8.1.0-8 > ii zlib1g 1:1.2.11.dfsg-1 > > qpdf recommends no packages. > > qpdf suggests no packages. > > -- no debconf information > > -- > Bjarni I. Gislason > >
Bug#903625: ITP: pikepdf -- python library for reading and writing PDFs, powered by qpdf
Thanks for making me aware of this. I didn't know about pikepdf. That's really exciting -- I've always wanted to be able to use qpdf from Python. I will contact pikepdf's author. On Thu, Jul 12, 2018 at 3:18 AM Sean Whitton wrote: > Package: wnpp > Severity: wishlist > Owner: Sean Whitton > > * Package name: pikepdf > Version : 0.2.2 > Upstream Author : James R. Barlow > * URL : https://github.com/pikepdf/pikepdf > * License : MPL-2.0 > Programming Lang: Python & C++ > Description : python library for reading and writing PDFs, powered > by qpdf > > This is a new dependency of the latest upstream release of OCRmyPDF. > > I intend to maintain it under the Debian Python Modules Team umbrella. > > After discussion with upstream, I plan to upload to experimental, > because the library's API is not yet stable. Upstream expects it to > have stabilised in time to upload to unstable in time for the buster > freeze. > > -- > Sean Whitton >
Bug#903625: ITP: pikepdf -- python library for reading and writing PDFs, powered by qpdf
Thanks for making me aware of this. I didn't know about pikepdf. That's really exciting -- I've always wanted to be able to use qpdf from Python. I will contact pikepdf's author. On Thu, Jul 12, 2018 at 3:18 AM Sean Whitton wrote: > Package: wnpp > Severity: wishlist > Owner: Sean Whitton > > * Package name: pikepdf > Version : 0.2.2 > Upstream Author : James R. Barlow > * URL : https://github.com/pikepdf/pikepdf > * License : MPL-2.0 > Programming Lang: Python & C++ > Description : python library for reading and writing PDFs, powered > by qpdf > > This is a new dependency of the latest upstream release of OCRmyPDF. > > I intend to maintain it under the Debian Python Modules Team umbrella. > > After discussion with upstream, I plan to upload to experimental, > because the library's API is not yet stable. Upstream expects it to > have stabilised in time to upload to unstable in time for the buster > freeze. > > -- > Sean Whitton >
Accepted qpdf 8.1.0-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Jun 2018 09:17:28 -0400 Source: qpdf Binary: libqpdf21 libqpdf-dev qpdf Architecture: source amd64 Version: 8.1.0-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt Changed-By: Jay Berkenbilt Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf21 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Changes: qpdf (8.1.0-1) unstable; urgency=medium . * New upstream release. * Includes fix for CVE-2018-9918 Checksums-Sha1: fc2c460738474ce0d7f29dfebcc624e07abc3aa0 2058 qpdf_8.1.0-1.dsc f819707c346b21d90194cf9cec95e370f2807f20 8243624 qpdf_8.1.0.orig.tar.gz 891c9c5d84bff7b40025f74d160e7bfaa416e8f2 833 qpdf_8.1.0.orig.tar.gz.asc 52b1aa72b8843746340e64cb741bb4939b363eb0 12728 qpdf_8.1.0-1.debian.tar.xz 4b1f13cf579f7ccecd49114dc39eaca517937580 443412 libqpdf-dev_8.1.0-1_amd64.deb 1092b824984152c5fde6b5baf57c6699036eed06 3649876 libqpdf21-dbgsym_8.1.0-1_amd64.deb 73e959f2d7bcf47272ea410f8296fd50a2af6469 343540 libqpdf21_8.1.0-1_amd64.deb 0516a6b91a7d787b22e1743bd9c3ab15a8619b43 384548 qpdf-dbgsym_8.1.0-1_amd64.deb a06feafcefa4f482eb41ba3b45803eeb2bfe9102 6564 qpdf_8.1.0-1_amd64.buildinfo 2e21302b876020a40b1dd85d8cd45978256ae66a 285472 qpdf_8.1.0-1_amd64.deb Checksums-Sha256: a5cb820adb5650c35f60180d6105bd5d6254fe48f972247ea24bfbb6a8159ef9 2058 qpdf_8.1.0-1.dsc 7d1f4827a3801a4b7d63f66fa50bbe237e74911801f3d31ee9f22f73e36370d4 8243624 qpdf_8.1.0.orig.tar.gz 96b73eeaa11a6f4c913c64727bd8c0b72883690e03f0f1878439d7386077cecf 833 qpdf_8.1.0.orig.tar.gz.asc f1f46575451e5b1b39f6feb754a4930fb8713fa9df431db14e2e9fdff38d88d7 12728 qpdf_8.1.0-1.debian.tar.xz dca95d0f40af28e313930ce145bd239c23820b696e05cc9f8191c2fc055788de 443412 libqpdf-dev_8.1.0-1_amd64.deb 0b74c450e6a0ef7783a2cf77d084f9a58e0a9618fc575f36214f7fa515ea0c95 3649876 libqpdf21-dbgsym_8.1.0-1_amd64.deb 6107d61a517323710f0ff4c5ef4bb49a44cbaba602bdc27e00109c46ec0cd399 343540 libqpdf21_8.1.0-1_amd64.deb 0e25db1d32a257a6632e92b09a6a055c9b8ff2b8dacc7917bbd6b9155cc63650 384548 qpdf-dbgsym_8.1.0-1_amd64.deb 0d90e5bc6d3a151b62c24612bc1dbf00ada57f12d58c2de408dcc372cad7fd62 6564 qpdf_8.1.0-1_amd64.buildinfo 6f9b831fe91feb961ed527c32ac7e11c260a0eb5f2a60c3e54a8e8aedefc2daf 285472 qpdf_8.1.0-1_amd64.deb Files: 48daebdce259d6bbb131e8bbe9f29bba 2058 libs optional qpdf_8.1.0-1.dsc f943837c39bc6310c51a954ec6d7cc03 8243624 libs optional qpdf_8.1.0.orig.tar.gz e13cb67a17cd057803d52701d3fd52e4 833 libs optional qpdf_8.1.0.orig.tar.gz.asc f01506b61eff3b523494fa647fb0ab5f 12728 libs optional qpdf_8.1.0-1.debian.tar.xz a5c2337ed0db82f31ea1d281dd058572 443412 libdevel optional libqpdf-dev_8.1.0-1_amd64.deb 0a7bfdc0b4ee305608d7e7b2881eae5b 3649876 debug optional libqpdf21-dbgsym_8.1.0-1_amd64.deb c7ecf126dc7d049846e1d11c89b7c089 343540 libs optional libqpdf21_8.1.0-1_amd64.deb ca80705691a2d35c5e777e8ff8113022 384548 debug optional qpdf-dbgsym_8.1.0-1_amd64.deb 32616601e46089d8c847ea5156c1b5fb 6564 libs optional qpdf_8.1.0-1_amd64.buildinfo 598ff9e30a9c4b1d30649651aeb2a686 285472 text optional qpdf_8.1.0-1_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEwslrEAEf4Anm0d+CinXRCZgBLH4FAlsuStMPHHFqYkBkZWJp YW4ub3JnAAoJEIp10QmYASx+otEP/Aplo+QFKvLDEVDaWiEXzfWJJHTo1b07MB4K nCSq8VvHYW4w4qxJ9a8DEnPntIExgbrAWEiWqUEgobtUOT23Lh1taC8hktDi8vKm KGpn/zmLFpfUUhlVJ8/NSQ3JH+yq3/5ATBmP29Hx5TuIJUdxlzZwPtsxvK/aW3ea vcT10KeDDrs8mLQKAu5HxWvNNSin0wFvyh0DSJYvUN2uwFVPfsHSOWx4Sa9ahS27 MrhVbSK9xjPni2RdYkC6TRRV8wt0ecm6MobChiO3SnJMZyz0C+8lpE9RzhJNuBwy ewH0AnRmY1PkaoF0iY0e4hued4BG3D9Z2EFBJsXnpWxD6vWjI+fkIDiHUfwHso8M tm0+enVek71wlyMaRWX/4kSsfCJ9Hmf92O9RgxaynXUokfC7zq+KyITDSgegKgP3 oGNEuEo7Fx+wdSjdrqzuRAiRk3HvAEqWBBaA2+eSIyItSrUTYjVWxNeQ8x2Ioj4V Vo/wJiaOoNho9xrsP3Qw9+i0yh/mRz+HFaZmT9HTqs7WfnbTbYxeBr/gAvmvBOCX uucMy1zLKVTju3w3ZqoxAK3V2DmQqZCUqr7Bsxin+dZRVb8bdYQNi2FZo+PXAoeN jGLLgYEtT5fspSJJcRNRnPypa6G/fcTJUldMv08yqevmUWesxdcmKXwHwkFH1Q2y vUsSwxcp =r9Pq -END PGP SIGNATURE-
Accepted qpdf 8.0.2-3 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Apr 2018 16:24:12 -0400 Source: qpdf Binary: libqpdf21 libqpdf-dev qpdf Architecture: source amd64 Version: 8.0.2-3 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt <q...@debian.org> Changed-By: Jay Berkenbilt <q...@debian.org> Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf21 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Closes: 895443 Changes: qpdf (8.0.2-3) unstable; urgency=medium . * Add patch for CVE-2018-9918 from upstream commit b4d6cf6836ce025ba1811b7bbec52680c7204223. (Closes: #895443) Checksums-Sha1: d5286d5cd1a4301ec943cb49d9c5797349b8cd8c 2029 qpdf_8.0.2-3.dsc 84b8c4dcadc7c8abfbbc76c05e16daf9b3fb7e4a 13548 qpdf_8.0.2-3.debian.tar.xz 6ac9108ae2fe3d53290e2ac7c0dcd7d9395dcb10 406516 libqpdf-dev_8.0.2-3_amd64.deb ff1a192a340d03fede5f60d6a7a262eec7cab7a3 3165596 libqpdf21-dbgsym_8.0.2-3_amd64.deb 1a708bba1a1ef1ef1768da43dee1f2a095cb9381 320252 libqpdf21_8.0.2-3_amd64.deb d39913268169a86415c9dd792d6c341e9f86bf23 362412 qpdf-dbgsym_8.0.2-3_amd64.deb ae2db556c6c7e3cb0dffc2e9855881bcea5a4124 6455 qpdf_8.0.2-3_amd64.buildinfo 604409edda61e75e1c9e33c73fc1b7074fd1190d 265768 qpdf_8.0.2-3_amd64.deb Checksums-Sha256: 54a81c4dcdc4bff191cd7d54bfb71d6ee916e7ccbc2dfda113154e9a4756e3f9 2029 qpdf_8.0.2-3.dsc fdda73c312306f06d189806f8f7508787bf9397cc5225c2c95b1db25097d4fb5 13548 qpdf_8.0.2-3.debian.tar.xz 9d0edd3a6f91a6f67660bb3b7bc3addacf568724b9036bd4ee480492414bb031 406516 libqpdf-dev_8.0.2-3_amd64.deb 9363619b58a2b8e9288d8b6dbf4835e2cd45819cb57945cbb6774ec99ca8d301 3165596 libqpdf21-dbgsym_8.0.2-3_amd64.deb e6f57beef40624f3acabb0615a6e6297ca9d696ab22c0cbfce5433f57fc41470 320252 libqpdf21_8.0.2-3_amd64.deb 8165acf21222d066d6f0829ea00fc979806467ee37d22a3fc41f40d1123e724a 362412 qpdf-dbgsym_8.0.2-3_amd64.deb 4ca0fd5cd9e56600af2a3f13458ed9d1fedbb012925afb3def638413c9f5ec42 6455 qpdf_8.0.2-3_amd64.buildinfo 981a5b3e7faef4e975379b60e603f7e37232b418fedd85755f493c68f6d86f92 265768 qpdf_8.0.2-3_amd64.deb Files: 4c0742c174d8108a1f440ec48c1f9213 2029 libs optional qpdf_8.0.2-3.dsc 43467d8429368a1b3b4fa9d103a79374 13548 libs optional qpdf_8.0.2-3.debian.tar.xz 7144379aac0e692690db7f417b643d5f 406516 libdevel optional libqpdf-dev_8.0.2-3_amd64.deb e2c174729ffab22950b67180e82506f0 3165596 debug optional libqpdf21-dbgsym_8.0.2-3_amd64.deb 351d6a2f66db2f3d3bdf55e130401b44 320252 libs optional libqpdf21_8.0.2-3_amd64.deb 47ea52e1f3c98e86bdb2ab1e622facdd 362412 debug optional qpdf-dbgsym_8.0.2-3_amd64.deb 3cd6ef09c484684770f2317583c79a58 6455 libs optional qpdf_8.0.2-3_amd64.buildinfo daacf9e5d283ec274889476b80cedce9 265768 text optional qpdf_8.0.2-3_amd64.deb -BEGIN PGP SIGNATURE- iQIsBAEBCAAWBQJa09KTDxxxamJAZGViaWFuLm9yZwAKCRCKddEJmAEsfijZD/oC 0n6PxKjurRsYncLiHXo6J7S/uoq0AUGREOOycyWUwl44kS2w1AVRZfrps/l0+8Ki 5Tpy4KC2OT456WWavH8OnYt7I0mlN2a6GDPovB86Jrk8VZWEdPJvsl1/FS+QcrCF iMqLXpyk1p3ktW5B6nhy7Np5kL74fCVCpvLbFVcwe/l5jrsuPhRZtD7JlzWcDnar a4WFjRTNDI7xzpaA7pJupbYsSiiDhngD3HJEegux+CyIYKfMh3WWJFqXFuY4bJbT 53s6zCsqYL4slOYKYZVUMtsDZ4YjhTuS5+mgED2xF4RV8YkNnJAU+44IYpSj3bIn NyJ1BoNiBkyM4CvrfPdRCwGtIBhS9nGfuxDc7Pst486sQAya+Aqj4rUZynWke5RG YOX3m7L3XGn5spJVkokciL0ckntUWptZQwlF35+6Mf0dA2sqf9jntElkZaym+G54 heac725P8EIw+MNxFDHwgVqX8DTfa+DhnT0CXtG/T28UgLZ3NrMwh0GsPzqwJo4r TeKPra6gwmLOUDdF7Q0IGKHpIEbScSNxKOz1YNAiZgXbuFVjBsn3xegKkJsDtk8g n5mA9sobX83DqVH+a2zj9lGULtV1/yR5DfUIW02yTnYzMXlkgYw6VnUkgo26bZaB 8jVooY5s15nb66oI7X/7IgH1Zz45hQ9Mu7U5NWeKxQ== =bSD7 -END PGP SIGNATURE-
Accepted qpdf 8.0.2-2 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Mar 2018 08:29:34 -0400 Source: qpdf Binary: libqpdf21 libqpdf-dev qpdf Architecture: source amd64 Version: 8.0.2-2 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt <q...@debian.org> Changed-By: Jay Berkenbilt <q...@debian.org> Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf21 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Closes: 893581 Changes: qpdf (8.0.2-2) unstable; urgency=medium . * Update debhelper dependency to 10.3 for dh_missing. (Closes: #893581) Checksums-Sha1: 137c830fce53afad918d0097d26a7f098940ef99 2029 qpdf_8.0.2-2.dsc 4b9b14c7f2289889d00539a71bf5e7de2cf7a900 12640 qpdf_8.0.2-2.debian.tar.xz ed2faa4f8cd9f98c0f62a164011dc004143b34f4 406580 libqpdf-dev_8.0.2-2_amd64.deb 6663814cf8850138d837f67a26c969de13877d8b 3164896 libqpdf21-dbgsym_8.0.2-2_amd64.deb 71ff13381a2be1027410087b388f0e3190a3c5b9 319708 libqpdf21_8.0.2-2_amd64.deb 6507faf65d06482ccbdea49a19f3f91745725054 362308 qpdf-dbgsym_8.0.2-2_amd64.deb c20415d34aa50790ec6937cc283cd7cedac024ab 6455 qpdf_8.0.2-2_amd64.buildinfo dc8ed52c7f1d7b62c030ce84f42bf6377fc0771a 265752 qpdf_8.0.2-2_amd64.deb Checksums-Sha256: 662ccecc4e6e9f83a173baac0fb34ee3bc6c0935cca4646ca9174318f95b9946 2029 qpdf_8.0.2-2.dsc 2feb99f263d1f8a23ef80546cde5194d8abc3ed795e0fbca9e0e7ed8de93e280 12640 qpdf_8.0.2-2.debian.tar.xz 25263ddde0d66cfef2418198f333415d435960c31e1ddc778fe40d85e27d 406580 libqpdf-dev_8.0.2-2_amd64.deb c1a6ded5b829b0f26b598c44284b8d07d9f476fee26f5a2eec1f8819f11ec238 3164896 libqpdf21-dbgsym_8.0.2-2_amd64.deb bed045162f01c73784c6d272fbf899cdfecfbf71161bd744c926ff2d07f7a2bc 319708 libqpdf21_8.0.2-2_amd64.deb 0fbf098c7bbb7fc4186f0a44a9568a9c0fc9cd12c94310899f8319775d012275 362308 qpdf-dbgsym_8.0.2-2_amd64.deb c3b48e382d253b7dffcac0955676c75cbdf8c07e681cacdc2ac4a942764c7e7c 6455 qpdf_8.0.2-2_amd64.buildinfo 69abc7885a3142ae25e7cac16853e3db547b1d23888408c2859f9cb53fcbfdd4 265752 qpdf_8.0.2-2_amd64.deb Files: a1e051a3b3d1f59bca67bc61b21a51e1 2029 libs optional qpdf_8.0.2-2.dsc a35c1cea4bec005e2eaf8761c9745026 12640 libs optional qpdf_8.0.2-2.debian.tar.xz a01866293a7dd7905d1368b1cf2aec9c 406580 libdevel optional libqpdf-dev_8.0.2-2_amd64.deb 1dca14a86b3772ebad1efa25b8ab86d0 3164896 debug optional libqpdf21-dbgsym_8.0.2-2_amd64.deb 36c3825c3e0787a2d3db2c4dca29c44f 319708 libs optional libqpdf21_8.0.2-2_amd64.deb 99864b47887184858cfb45e093eeda74 362308 debug optional qpdf-dbgsym_8.0.2-2_amd64.deb 6ec9a193192a2dccd6ca13470df89c93 6455 libs optional qpdf_8.0.2-2_amd64.buildinfo 2c7b2276516cd7aa8299423d3a1b0119 265752 text optional qpdf_8.0.2-2_amd64.deb -BEGIN PGP SIGNATURE- iQIsBAEBCAAWBQJat5gMDxxxamJAZGViaWFuLm9yZwAKCRCKddEJmAEsfjl+EACK G6I77ULtgBOMa67zXkG3+sHN5QfW4yV0RNbWSMs0d+n3DWI76JA9VeSOaVfN9Jtb eWA1Zj6OvxrjXQ4IO5I1yIuOMqv/zvskSQ7CZL+MmQAqwrfObHdd7R9svcRnYEt0 5xealYgXZZrsno/jot+hhCN5XVIZ6bF5T0NAgfPTziW9kawsWo6Dugv/wOIxhH0b pk9zgEYa6srtVe2l5oI0TAnn3SnahfRoI1RSc/jb+jultsSj+GGqc1E7vLWDrckg U3gEn8m2pBPFVz4mFjYBiHuC0F+5FjEawPW8JFg7U8Wmb4CaYRreGoagq9Rwkyjl HavYFHL8r20W8tHP3Nv0LP8X4StrVTCXD3GEXGJSYO6oJhSB5tvRW/FebZambAsY kPSqaE+ANlrCqxDY6VcyIqDOxw9ET2vV9cI7sd3n3E+L37tJ48bbboGmOQaz2UFI AkPxq7tZRS0banGLOIeppbtjxkn2Lk+/wsE6JwMpXFjiGax9Itns09xWELuMbTd5 GTEqrcR0xcb3i9e/OGzFZv9oBT6g0tm9WTg86Ia7EAc5WoSw8qkjwDYA278hUMTu /yGkwKA/qHGFppif7gEwgMo6Imx3ZLFkqMUPtnRhwVNZxZ0kVhOJ01y9TkOTtJMx en9eu+req7m78CNnhO8fjhUc+lwhCDNV5JI77baDlw== =sFwj -END PGP SIGNATURE-
[Bug 1753621] Re: FeatureFreeze exception
qpdf 8.0.2 is released, on github and sourceforge, and uploaded to debian unstable. It should be visible momentarily. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753621 Title: FeatureFreeze exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1753621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1753621] Re: FeatureFreeze exception
qpdf 8.0.2 is released, on github and sourceforge, and uploaded to debian unstable. It should be visible momentarily. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1753621 Title: FeatureFreeze exception Status in qpdf package in Ubuntu: Triaged Bug description: I am requesting an exception to the FeatureFreeze for Ubuntu 18.04 LTS. I would like qpdf 8.0.1 to be synced from debian. I am the upstream author of qpdf and the debian maintainer. I released 8.0.0 with the explicit goal of beating the 18.04 feature freeze. It was released and uploaded to debian on February 25. Then I realized 8.0.1 a few days later (March 4) with a few very small additional enhancements. I came to learn that 8.0.0 was not synced before the deadline, so I am requesting a freeze exception. You can find 8.0.0 in debian testing and 8.0.1 in unstable. I was planning on releasing 8.0.2 with another one-line change. The changes from 8.0.0 to 8.0.2 are not fixes to bugs in 8.0.0. Both releases include small additional enhancements. For now, I am request sync of 8.0.1, which is the latest version in debian. The qpdf package has a very strong record of stability. The principle changes in 8.0.0 were source-compatible but non-binary-compatible changes to support more advanced handling of PDF files at the lexical layer. These changes are required to support some Google summer of code work toward handling PDF forms in files being printed. qpdf is used as the backend for cups-filters. Additionally, qpdf 8.0.0 includes fixes that allow a wide range of incorrect PDF files that break in 7.1.1 to be processed as it handles more cases as recoverable rather than fatal errors. 8.0.1 adds the additional enhancement of allowing PDF files with checksum errors in their compressed data to be processed. The risk to allowing qpdf 8 into 18.04 is minimal as qpdf has a very thorough regression test suite, and all the changes are backward compatible at the source level. The advantages of having qpdf 8 in 18.04 include handling of a wider range of incorrect files for printing and opening the door to a backport of the form handling capabilities in cups-filters should that be desired. If possible, I would like to request an exception for 8.0.2, which I have not yet released. 8.0.2 includes only one small additional enhancement: better recovery of files that have loops in the cross reference table. Most readers can't handle such files well anyway, but evince can, and this would enable successful printing of such files from evince. It's a one line change + test suite updates. I have not released 8.0.2 but could do so at any time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1753621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Accepted qpdf 8.0.2-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 06 Mar 2018 11:54:54 -0500 Source: qpdf Binary: libqpdf21 libqpdf-dev qpdf Architecture: source amd64 Version: 8.0.2-1 Distribution: unstable Urgency: medium Maintainer: Jay Berkenbilt <q...@debian.org> Changed-By: Jay Berkenbilt <q...@debian.org> Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf21 - runtime library for PDF transformation/inspection software qpdf - tools for transforming and inspecting PDF files Changes: qpdf (8.0.2-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: b7ed7231cccb70ce602fdc793a48017945a2d53a 2027 qpdf_8.0.2-1.dsc ffafee34e424fe9da32f0d1874c3eaeb65f529c1 7952979 qpdf_8.0.2.orig.tar.gz 4dd1329f8a8b7d3cb788fa7169789ebaf1d58adb 801 qpdf_8.0.2.orig.tar.gz.asc 85f0ffe6c5f913196b85bf37da08a1f4245fe4ff 12600 qpdf_8.0.2-1.debian.tar.xz 87cec2240791399b3531418e5276638e2f6ccbac 406760 libqpdf-dev_8.0.2-1_amd64.deb 4eaa90506c179eddd2545d38733bb3a5004bbab7 3165204 libqpdf21-dbgsym_8.0.2-1_amd64.deb 9c76d8f10a056d3744935bf19d70d29c5fd460c0 319884 libqpdf21_8.0.2-1_amd64.deb ae558a2e6c91cad7229877bcc1e23a535df19ab9 362368 qpdf-dbgsym_8.0.2-1_amd64.deb bda4f3799188ae9406363a215ea549f6a8b442b1 6451 qpdf_8.0.2-1_amd64.buildinfo 112b9b4748ccf3b1b99d4bd93fb572a9cb5f332f 265668 qpdf_8.0.2-1_amd64.deb Checksums-Sha256: 504737625b776153c2b1c647eed1260a3fe44482ba102b606fafa57a21d5131e 2027 qpdf_8.0.2-1.dsc b09e1730b515956903866619b466da359cc051ae8c9d8690d8e7a2aca493c8c1 7952979 qpdf_8.0.2.orig.tar.gz 57a4287c2b05fe8b0ba17999da9de8d08bfebf14392582969955b6afdd69b8b6 801 qpdf_8.0.2.orig.tar.gz.asc 395f0cf78f5a18c008eda8d052b31ac7978bc9a274e2c7ba669fbd3a4beaf4cd 12600 qpdf_8.0.2-1.debian.tar.xz 7f9a366f0bf20f49fcf61e08b5aca5253cea718b6b6fd46c6582d135f092de5c 406760 libqpdf-dev_8.0.2-1_amd64.deb 184b641a19024b0b2d25b4cc02572de052617861dc2af36d1276ff48cc1ef0c9 3165204 libqpdf21-dbgsym_8.0.2-1_amd64.deb 4166a86bfbf43d2c70b5d077907ed3590f41b80641ca35593d27e686ba865706 319884 libqpdf21_8.0.2-1_amd64.deb cb7032c7250d8e8a1e8e0e9fae5ccca4282143ae690c5eabbc660d7b4c860a02 362368 qpdf-dbgsym_8.0.2-1_amd64.deb e3ef8cff749408c95da35fbcd9fa42d6e7b02d8a2babe6219255e5db1b76f61b 6451 qpdf_8.0.2-1_amd64.buildinfo 2b69802077bc894a9b2cce3c80e9981a7e5b975547c63f7b624a79f94ae919ce 265668 qpdf_8.0.2-1_amd64.deb Files: aadebf3bdab366b92ce768e473a016e4 2027 libs optional qpdf_8.0.2-1.dsc 74a9c61be4e899f92c1d8598cec06108 7952979 libs optional qpdf_8.0.2.orig.tar.gz ebf44fabdd4bb93e8f2b09e40da453b9 801 libs optional qpdf_8.0.2.orig.tar.gz.asc b41b8e34c5e55d717f9fea69f4d400fb 12600 libs optional qpdf_8.0.2-1.debian.tar.xz f5dda63e910a9cd6e8b2781f39543c42 406760 libdevel optional libqpdf-dev_8.0.2-1_amd64.deb 17e837c8c537eca930bd1fd8da1bdb64 3165204 debug optional libqpdf21-dbgsym_8.0.2-1_amd64.deb 6cadeb22525011dc5ddf2376d3c5547d 319884 libs optional libqpdf21_8.0.2-1_amd64.deb b5471e583bea6f51eddec2152e2489ef 362368 debug optional qpdf-dbgsym_8.0.2-1_amd64.deb bcc4499b2aefd71bf1b105af96d57c8f 6451 libs optional qpdf_8.0.2-1_amd64.buildinfo 9980664bf0547bf28645e194fc991e7d 265668 text optional qpdf_8.0.2-1_amd64.deb -BEGIN PGP SIGNATURE- iQIsBAEBCAAWBQJansjzDxxxamJAZGViaWFuLm9yZwAKCRCKddEJmAEsfhUVD/0e Ttl6I55W+YHpRXjiDZ/pw3mNjTpmB81/VJsdqst77OX9LTUOB2+Xl9vxkL114qvL bi62fmYqpSQV/GRRl3O5/ptMgxjufgK9NOLBep0Ti+w/HdlKs54ThsHpdsBVx462 sVGv067BA2sNzObkxQajudUQWRd1OJj25sV1JrX9goSew4tCXcTZrCGoyKxzuVw6 jZOVVAJ3P6uBTvZDCjh0TyfHbEqKmyDbTZyuV76QFjjCiFRdh+D4gfqczWSWNMs5 WMXC7tf6PvZ2wwex8MGp/JzqpD15SXVBG0Miy0gfNMMbgQ3gjfzoEkO1VCKPvJsP bLATcHke74anohlnpqocFD4xTfteno9Wpz/bjVnfQV/RGjkOMgfSh0QX8PdafsiV 9pgyRoQgh61qH/nP38QpctY44WLv/tN1NuH7YnJvNmN2qo7lzCZN+lTXWIRb8mdf Viwd3xu9J9F2T+7qsmHrem6P7pA3o1fyLr39LXlsrJ7tAaC6LvvNMPO1XJwOCRw4 TTFeLHhbNI88yJK/B7mVlhRK/Z3pHg6qQojf6th/Gl2gyXJRXseyNn9KaDzzB4oe upp4Omy7POdS1NbCggsbc1v7L6gDPG/82QqPyopnNombEu4TSLGFGAzqhOXF80dh nUmiz/r02G7Fit/MHT+vkVPiQ/ItjwIjNEc56SJRbw== =Lpn9 -END PGP SIGNATURE-
