ghostscript_9.20~dfsg-3.2+deb9u5_amd64.changes ACCEPTED into proposed-updates->stable-new
Mapping stable-security to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 14 Sep 2018 22:53:46 +0200 Source: ghostscript Binary: ghostscript ghostscript-x ghostscript-doc libgs9 libgs9-common libgs-dev ghostscript-dbg Architecture: source amd64 all Version: 9.20~dfsg-3.2+deb9u5 Distribution: stretch-security Urgency: medium Maintainer: Debian Printing Team Changed-By: Moritz Mühlenhoff Description: ghostscript - interpreter for the PostScript language and for PDF ghostscript-dbg - interpreter for the PostScript language and for PDF - Debug symbo ghostscript-doc - interpreter for the PostScript language and for PDF - Documentati ghostscript-x - interpreter for the PostScript language and for PDF - X11 support libgs-dev - interpreter for the PostScript language and for PDF - Development libgs9 - interpreter for the PostScript language and for PDF - Library libgs9-common - interpreter for the PostScript language and for PDF - common file Changes: ghostscript (9.20~dfsg-3.2+deb9u5) stretch-security; urgency=medium . * Fixes for CVE-2018-16509 (fourth patch, rest were applied in deb9u4) CVE-2018-16802 and one additional issue with a CVE ID (yet) Checksums-Sha1: 4203fbffa0d63e2d873c68a6ad68342afdf40032 2898 ghostscript_9.20~dfsg-3.2+deb9u5.dsc 02e461e141c69c73d62d2a2c0b9f82101221f43e 139976 ghostscript_9.20~dfsg-3.2+deb9u5.debian.tar.xz b2e18d8c612fe105022b1df5b0d3b38dacb8d19e 11879984 ghostscript-dbg_9.20~dfsg-3.2+deb9u5_amd64.deb a4b002b61d8e21b928043b5a6bb155a0c9e9eb39 5631970 ghostscript-doc_9.20~dfsg-3.2+deb9u5_all.deb 72ca81ce3408bdd38e843c374298c8a15b45c9b8 91478 ghostscript-x_9.20~dfsg-3.2+deb9u5_amd64.deb fdad2761bab9e6d72779bf5ee61e28da3ec97473 13176 ghostscript_9.20~dfsg-3.2+deb9u5_amd64.buildinfo ff7ec35a44fd28356506f2e91899dd358ed00970 98198 ghostscript_9.20~dfsg-3.2+deb9u5_amd64.deb b5530651b2c1bb8964ca9c2240dc76732894aeef 73622 libgs-dev_9.20~dfsg-3.2+deb9u5_amd64.deb 875fc2ab311fdf6e648a422efcd7650b4a32cbf0 5164150 libgs9-common_9.20~dfsg-3.2+deb9u5_all.deb 33e11407665358c296a81b2d282498c2d7693a42 2071420 libgs9_9.20~dfsg-3.2+deb9u5_amd64.deb Checksums-Sha256: fbe3649deedd492093b9d127072c9e354e79685c468192cc567cd6472969dcd5 2898 ghostscript_9.20~dfsg-3.2+deb9u5.dsc 7de4511e18189e48ac0c9cc99f114cfdcaa481fd8bdbfaaac4174d69d5424022 139976 ghostscript_9.20~dfsg-3.2+deb9u5.debian.tar.xz cd2f97bdea546cf7169442778dd2682dc580ef1a3edb4b63ac811e3616bc9745 11879984 ghostscript-dbg_9.20~dfsg-3.2+deb9u5_amd64.deb ad6cffb2504a90fe45f070db7dfc909b55d2040c1161e930fa54b13938f5cfc9 5631970 ghostscript-doc_9.20~dfsg-3.2+deb9u5_all.deb 5f83cbceb55ba4d80f7180015e1bd2fca335030a6bfd04a260f325f5e10ac22c 91478 ghostscript-x_9.20~dfsg-3.2+deb9u5_amd64.deb 9ed161b3d04a35cbf54f71e374e7556ff42873eb705e2d32ff2b4a714ff8c40f 13176 ghostscript_9.20~dfsg-3.2+deb9u5_amd64.buildinfo 8ae5ca92b0d5e43b86267b96d65b00bd6caea9f6d92ec3bb4d32ded6a678edcd 98198 ghostscript_9.20~dfsg-3.2+deb9u5_amd64.deb fa6f41cdceeb7c25c5087fee5e9a5e60f119daa3d7307eac619533ce6b792060 73622 libgs-dev_9.20~dfsg-3.2+deb9u5_amd64.deb 0ccb0aa4ca2a254b7df52bb081ec787f4372ec88437995166b1140d1527e541a 5164150 libgs9-common_9.20~dfsg-3.2+deb9u5_all.deb a0477bd5e90b9b5a974f09bf76d02ff652d01652b4dd13a647373b565e6d634c 2071420 libgs9_9.20~dfsg-3.2+deb9u5_amd64.deb Files: aa4222e15cd6e8d7eeba27c2e2e8a48b 2898 text optional ghostscript_9.20~dfsg-3.2+deb9u5.dsc c20570dc82439068f3588e8861e8dd2b 139976 text optional ghostscript_9.20~dfsg-3.2+deb9u5.debian.tar.xz da03404af376964183a51fb24d8c29d8 11879984 debug extra ghostscript-dbg_9.20~dfsg-3.2+deb9u5_amd64.deb ce64e176454686b43a6578b81dbcddc6 5631970 doc optional ghostscript-doc_9.20~dfsg-3.2+deb9u5_all.deb 268638527b0d5e1bcc56ad4a2456bb4f 91478 text optional ghostscript-x_9.20~dfsg-3.2+deb9u5_amd64.deb 568f3d84aa220ad5100df7d27eefd06a 13176 text optional ghostscript_9.20~dfsg-3.2+deb9u5_amd64.buildinfo dbdd92273c2730c2d5add824f27505ae 98198 text optional ghostscript_9.20~dfsg-3.2+deb9u5_amd64.deb 92ec815764eaf0d5ea3aa3d8216c4fcb 73622 libdevel optional libgs-dev_9.20~dfsg-3.2+deb9u5_amd64.deb 438f5d8a98c1b49f6c79705948bd9bc3 5164150 libs optional libgs9-common_9.20~dfsg-3.2+deb9u5_all.deb d2ee146ada9bdd40a946ed209574b441 2071420 libs optional libgs9_9.20~dfsg-3.2+deb9u5_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAlub1E4ACgkQEMKTtsN8 TjZWvQ/+N86Q4xoEcxIX2Gup/FJiCnrGmTQoncjwiCGCtlSO6KJOMJi0PTh3yq4S c2y3l0KAZ58y5gP6pAE3Ht6eDZ9hQe+t+CbppPkTN7Ln8jBb4BDUaLpuY56JlvUA U95NU9+XbSiuMCJrq3kaPSWOyv0vedtapqUde6cA8sAGFBitNdhfvekP+uUR4sIM UDeVTzubp2ARv8rMHEqvUmvBASJa2C9Z9Ds26h2Tk4d6p6mwGtl6hfayDHJEYpwD aaebvj7b1lBH1zK2huonQkNKfjoMyvZJ9j33gPTTac+75J56mE7IVjcuDTMQGL3L hJ1PUgGJBtjgwpWUxwRJpCdo7tPKxO8C9tXTFPhQ+HQNO7gpmfjNUfJmnTFCmPxj wK/iDIOY1kJFhjq/o2EL/oxIXh0owpKh3WG7kirwNgbM4ncJ1PQo0yOyI5JpCpGO mbn6SzKvJwyYl1qNUPxJu+3ttFx3RjAQt45JZQaB1JmEK0edykIJpfYvNIow
Processed: Re: Bug#908937: ghostscript breaks ocrmypdf autopkgtest
Processing control commands: > reassign 908937 ocrmypdf Bug #908937 [src:ghostscript, src:ocrmypdf] ghostscript breaks ocrmypdf autopkgtest Bug reassigned from package 'src:ghostscript, src:ocrmypdf' to 'ocrmypdf'. No longer marked as found in versions ghostscript/9.25~dfsg-2 and ocrmypdf/6.2.3-1. Ignoring request to alter fixed versions of bug #908937 to the same values previously set -- 908937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908937: ghostscript breaks ocrmypdf autopkgtest
Control: reassign 908937 ocrmypdf Quoting Paul Gevers (2018-09-16 11:25:47) > ginggs already noted this: > > this patch fixes 1 of the 3 failing tests > https://github.com/jbarlow83/OCRmyPDF/commit/517b385fe5cb2195023100a807e6f18dc7e6faea#diff-b61a6d542f9036550ba9c401c80f00ef At http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=e997c68 linked from above the change is described as a deliberate change in Ghostscript, so reassigning this to ocrmypdf. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#908937: ghostscript breaks ocrmypdf autopkgtest
Dear Sean, On 16-09-18 20:30, Sean Whitton wrote: > Paul: does preventing regressions in testing take precedence? Normally, yes temporarily (we are not blocking yet), but ghostscript was uploaded with urgency high. That means that regressions are ignored and without an RC bug, ghostscript will migrate to testing tomorrow (if my counting is correct). > If so, > this bug should be reassigned to ghostscript and raised to RC severity. I don't follow what you mean by this sentence. > But ISTM that ocrmypdf is less important, so ghostscript should be > allowed to migrate and ocrmypdf should be kicked out. ocrmypdf can stay in testing as long as it doesn't have an RC bug itself. So just to make it clear: if this change making ocrmypdf totally unusable and you still want ghostscript to migrate to testing to fix multiple CVE's, than assigning this bug to ocrmypdf and raising it to RC level will start the autoremoval process. If you think it is worth searching for a solution in ghostscript to avoid it breaking ocrmypdf, than reassign this bug to ghostscript and raise the severity to RC level to avoid migration. Paul signature.asc Description: OpenPGP digital signature
Bug#908937: ghostscript breaks ocrmypdf autopkgtest
Hello, On Sun 16 Sep 2018 at 11:20AM +0200, Paul Gevers wrote: > With a recent upload of ghostscript [9.25] the autopkgtest of ocrmypdf > [6.2.3] fails in testing when that autopkgtest is run with the binary > packages of ghostscript from unstable. It passes when run with only > packages from testing. I copied some of the output at the bottom of > this report. James: how easily could we backport the GhostScript change to OCRmyPDF 6.x series? If not easily, and you still think that pikepdf's API will stabilise in time for Debian's upcoming stable release, maybe OCRmyPDF should just be kept out of testing for the timebeing. Paul: does preventing regressions in testing take precedence? If so, this bug should be reassigned to ghostscript and raised to RC severity. But ISTM that ocrmypdf is less important, so ghostscript should be allowed to migrate and ocrmypdf should be kicked out. -- Sean Whitton signature.asc Description: PGP signature
Bug#908871: marked as done (cups: completed jobs stay in queue)
Your message dated Sun, 16 Sep 2018 17:06:24 +0200 with message-id <2195442.mnpqfjg...@odyx.org> and subject line Re: Bug#908871: cups: completed jobs stay in queue has caused the Debian Bug report #908871, regarding cups: completed jobs stay in queue to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 908871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908871 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cups Version: 2.2.8-5 Severity: normal Dear Maintainer, Wondering why my printer didn't seem to want to print anymore, I noticed that completed print jobs stay in the queue, preventing any subsequent jobs from printing (unless I lprm the completed job). Tried with lpr, lp and printing from chromium. Same results. Since I don't print very often, I don't know exactly when this change occurred, but everything was working fine about a month ago AFAIK. Printer: HP LaserJet p2015n Series, hpcups 3.17.1 (via JetDirect). Happy to help debug this if you let me know what I can try. Thanks. - Felix -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cups depends on: ii cups-client2.2.8-5 ii cups-common2.2.8-5 ii cups-core-drivers 2.2.8-5 ii cups-daemon2.2.8-5 ii cups-filters 1.21.2-1 ii cups-ppdc 2.2.8-5 ii cups-server-common 2.2.8-5 ii debconf [debconf-2.0] 1.5.69 ii ghostscript9.22~dfsg-3 ii libavahi-client3 0.7-4 ii libavahi-common3 0.7-4 ii libc-bin 2.27-6 ii libc6 2.27-6 ii libcups2 2.2.8-5 ii libcupscgi12.2.8-5 ii libcupsimage2 2.2.8-5 ii libcupsmime1 2.2.8-5 ii libcupsppdc1 2.2.8-5 ii libgcc11:8.2.0-6 ii libstdc++6 8.2.0-6 ii libusb-1.0-0 2:1.0.22-2 ii poppler-utils 0.63.0-2 ii procps 2:3.3.15-2 Versions of packages cups recommends: ii avahi-daemon 0.7-4 ii colord 1.4.3-3 ii cups-filters [ghostscript-cups] 1.21.2-1 ii printer-driver-gutenprint5.2.13-2+b1 Versions of packages cups suggests: ii cups-bsd 2.2.8-5 pn cups-pdf ii foomatic-db-compressed-ppds [foomatic-db] 20180604-1 ii hplip 3.17.10+repack0-5 ii printer-driver-hpcups 3.17.10+repack0-5 ii smbclient 2:4.8.5+dfsg-1 ii udev 239-9 -- debconf information excluded --- End Message --- --- Begin Message --- Le dimanche, 16 septembre 2018, 15.30:34 h CEST Felix C. Stegerman a écrit : > * Brian Potkin [2018-09-16 13:50]: > > My quick tests show gstoraster is failing. There is a new ghostscript > > package now in unstable. Upgrade. How do you go on? > > That does indeed seem to fix the problem. Thanks! Closing then, thanks! -- OdyX--- End Message ---
Bug#908871: cups: completed jobs stay in queue
Thank you for your report, Felix. On Sat 15 Sep 2018 at 13:20:57 +0200, Felix C. Stegerman wrote: > Package: cups > Version: 2.2.8-5 > Severity: normal > > Dear Maintainer, > > Wondering why my printer didn't seem to want to print anymore, I > noticed that completed print jobs stay in the queue, preventing any > subsequent jobs from printing (unless I lprm the completed job). > > Tried with lpr, lp and printing from chromium. Same results. > > Since I don't print very often, I don't know exactly when this change > occurred, but everything was working fine about a month ago AFAIK. > > Printer: HP LaserJet p2015n Series, hpcups 3.17.1 (via JetDirect). > > Happy to help debug this if you let me know what I can try. My quick tests show gstoraster is failing. There is a new ghostscript package now in unstable. Upgrade. How do you go on? Regards, Brian.
Bug#908937: ghostscript breaks ocrmypdf autopkgtest
ginggs already noted this: this patch fixes 1 of the 3 failing tests https://github.com/jbarlow83/OCRmyPDF/commit/517b385fe5cb2195023100a807e6f18dc7e6faea#diff-b61a6d542f9036550ba9c401c80f00ef Paul signature.asc Description: OpenPGP digital signature
Processed: ghostscript breaks ocrmypdf autopkgtest
Processing control commands: > found -1 ghostscript/9.25~dfsg-2 Bug #908937 [src:ghostscript, src:ocrmypdf] ghostscript breaks ocrmypdf autopkgtest Marked as found in versions ghostscript/9.25~dfsg-2. > found -1 ocrmypdf/6.2.3-1 Bug #908937 [src:ghostscript, src:ocrmypdf] ghostscript breaks ocrmypdf autopkgtest Marked as found in versions ocrmypdf/6.2.3-1. -- 908937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908937: ghostscript breaks ocrmypdf autopkgtest
Source: ghostscript, ocrmypdf
Control: found -1 ghostscript/9.25~dfsg-2
Control: found -1 ocrmypdf/6.2.3-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainers,
With a recent upload of ghostscript the autopkgtest of ocrmypdf fails in
testing when that autopkgtest is run with the binary packages of
ghostscript from unstable. It passes when run with only packages from
testing. I copied some of the output at the bottom of this report.
As ghostscript is uploaded with urgency high, this regression is NOT
delaying of the migration of ghostscript to testing [1]. If this
regression requires blockage of ghostscript to testing, fast action is
required (raising the severity of this bug should be enough, albeit I
haven't tested RC blockage when bugs are assigned to multiple packages.
Due to the nature of this issue, I filed this bug report against both
packages. Can you please investigate the situation and reassign the bug
to the right package? As needed, please change the bug's severity.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=ghostscript
https://ci.debian.net/data/autopkgtest/testing/amd64/o/ocrmypdf/1000885/log.gz
=== FAILURES
===
___ test_compression_changed[congress.jpg-lossless]
spoof_tesseract_noop = {'ADTTMP':
'/tmp/autopkgtest-lxc.bj5c8t8i/downtmp/autopkgtest_tmp',
'ADT_ARTIFACTS':
'/tmp/autopkgtest-lxc.bj5c8t8i/do...j5c8t8i/downtmp/test-suite-artifacts',
'AUTOPKGTEST_TMP':
'/tmp/autopkgtest-lxc.bj5c8t8i/downtmp/autopkgtest_tmp', ...}
ocrmypdf_exec = ['/usr/bin/python3', '-m', 'ocrmypdf']
resources =
PosixPath('/tmp/autopkgtest-lxc.bj5c8t8i/downtmp/build.24A/src/tests/resources')
image = 'congress.jpg', compression = 'lossless'
outpdf =
'/tmp/pytest-of-debci/pytest-0/test_compression_changed_congr0/out.pdf'
@pytest.mark.parametrize('image,compression', [
('baiona.png', 'jpeg'),
('baiona_gray.png', 'lossless'),
('congress.jpg', 'lossless')
])
def test_compression_changed(spoof_tesseract_noop, ocrmypdf_exec,
resources, image, compression, outpdf):
from PIL import Image
input_file = str(resources / image)
output_file = str(outpdf)
im = Image.open(input_file)
# Runs: ocrmypdf - output.pdf < testfile
with open(input_file, 'rb') as input_stream:
p_args = ocrmypdf_exec + [
'--image-dpi', '150', '--output-type', 'pdfa',
'--pdfa-image-compression', compression,
'-', output_file]
p = Popen(
p_args, close_fds=True, stdout=PIPE, stderr=PIPE,
stdin=input_stream, env=spoof_tesseract_noop)
out, err = p.communicate()
assert p.returncode == ExitCode.ok, err
pdfinfo = PdfInfo(output_file)
pdfimage = pdfinfo[0].images[0]
if compression == "jpeg":
assert pdfimage.enc == Encoding.jpeg
else:
if ghostscript.jpeg_passthrough_available():
# Ghostscript 9.23 adds JPEG passthrough, which allows a
JPEG to be
# copied without transcoding - so report
if image.endswith('jpg'):
assert pdfimage.enc == Encoding.jpeg
else:
> assert pdfimage.enc not in (Encoding.jpeg,
Encoding.jpeg2000)
E AssertionError: assert not in
(, )
E+ where = .enc
tests/test_main.py:917: AssertionError
_ test_preserve_metadata[pdfa]
_
spoof_tesseract_noop = {'ADTTMP':
'/tmp/autopkgtest-lxc.bj5c8t8i/downtmp/autopkgtest_tmp',
'ADT_ARTIFACTS':
'/tmp/autopkgtest-lxc.bj5c8t8i/do...j5c8t8i/downtmp/test-suite-artifacts',
'AUTOPKGTEST_TMP':
'/tmp/autopkgtest-lxc.bj5c8t8i/downtmp/autopkgtest_tmp', ...}
output_type = 'pdfa'
resources =
PosixPath('/tmp/autopkgtest-lxc.bj5c8t8i/downtmp/build.24A/src/tests/resources')
outpdf =
'/tmp/pytest-of-debci/pytest-0/test_preserve_metadata_pdfa_0/out.pdf'
@pytest.mark.parametrize("output_type", [
'pdfa', 'pdf'
])
def test_preserve_metadata(spoof_tesseract_noop, output_type,
resources, outpdf):
pdf_before = pypdf.PdfFileReader(str(resources / 'graph.pdf'))
output = check_ocrmypdf(
resources / 'graph.pdf', outpdf,
'--output-type', output_type,
env=spoof_tesseract_noop)
pdf_after = pypdf.PdfFileReader(str(output))
for key in ('/Title', '/Author'):
> assert pdf_before.documentInfo[key] ==
pdf_after.documentInfo[key]
tests/test_metadata.py:52:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Bug#895320: re: ps2pdf crashes
On Sat, 15 Sep 2018 12:51:40 +0200 Jonas Smedegaard wrote: > Quoting Jonas Smedegaard (2018-09-14 22:33:14) > > A new release of ghostscript is now in experimental. > > > > Could you please help test if that succeeds? > > Didn't help. But neither do downgrading to 9.22~dfsg-2.1 in unstable > since 2018-04-20. Seems the cause of this is somewhere else than > ghostscript. > > texlive, perhaps? Ha, I haven’t seen this. Hmm, interesting. -- Cheers, Andrej
