Processed: reopening
Processing commands for cont...@bugs.debian.org:
> found 1071595 2.4.7-1.2+b1
Bug #1071595 {Done: Thorsten Alteholz } [cups] cups:
contortions needed to use duplex printing on HP Laserjet M402dn
Did not alter found versions and reopened.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1071595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: ipp-usb: diff for NMU version 0.9.23-1.1
Processing control commands: > tags 1057793 + pending Bug #1057793 [src:ipp-usb] ipp-usb: delegate placement of systemd/udev files to pkg-config data Added tag(s) pending. -- 1057793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: raise remaining usrmerge normal bugs to important
054191 1055514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055514 1061238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061238 1061245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061245 1061248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061248 1061259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061259 1061332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061332 1061337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061337 1061342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061342 1061352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061352 1061353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061353 1061489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061489 1061491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061491 1061527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061527 1061702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061702 1061849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061849 1061851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061851 1061855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061855 1061865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061865 1063455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063455 1063458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063458 1063552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063552 1063571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063571 1063572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063572 1063620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063620 1063622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063622 1063692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063692 1063693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063693 1063694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063694 1063696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063696 1063699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063699 1063876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063876 1063878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063878 1064045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064045 1064046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064046 1064125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064125 1064126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064126 1064237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064237 1064238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064238 1064299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064299 1064315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064315 1064316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064316 1064396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064396 1064400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064400 1064408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064408 1064430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064430 1064449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064449 1064459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064459 1064887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064887 1064888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064888 1071119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bump severity for usr-merge bugs
ps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058846 1058856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058856 1058857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058857 1058859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058859 1059190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059190 1059283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059283 1059365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059365 1059371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059371 1059372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059372 1059378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059378 1059379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059379 1059414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059414 1059432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059432 1059516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059516 1059757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059757 1060080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060080 1060195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060195 1060200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060200 1060229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060229 1060315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060315 1060333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060333 1060335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060335 1060344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060344 1060352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060352 1060356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060356 1060358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060358 1060799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060799 1061359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061359 1065306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065306 1065307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1068209 in 8.9, tagging 1069984, tagging 1039809, found 1063190 in 5.2.1.13040+dfsg-1~exp1 ...
ttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062115 1062125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062125 1062246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062246 1062322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062322 1062711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062711 1062855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062855 1062859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062859 1062939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062939 1062981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062981 1062982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062982 1063013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063013 1063072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063072 1063074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063074 1063095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063095 1063103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063103 1063106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063106 1063141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063141 1063181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063181 1063186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063186 1063190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063190 1063193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063193 1063267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063267 1063314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063314 1063315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063315 1064095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064095 1064248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064248 1064251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064251 1064264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064264 1064332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064332 1065787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065787 1066097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066097 1066103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066103 1068209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068209 1069984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069984 1070254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060769: marked as done (foo2zjs: mitigate empty directory loss for usrmerge (DEP17 P6))
Your message dated Sat, 27 Apr 2024 09:20:28 + with message-id and subject line Bug#1060769: fixed in foo2zjs 20200505dfsg0-3 has caused the Debian Bug report #1060769, regarding foo2zjs: mitigate empty directory loss for usrmerge (DEP17 P6) 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.) -- 1060769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: foo2zjs Version: 20200505dfsg0-2 Severity: normal Tags: patch User: helm...@debian.org Usertags: dep17p6 For the currently ongoing UsrMerge effort [1], paths installed into /lib should move to /usr/lib. printer-driver-foo2zjs installs the empty directory /lib/firmware/hp. On a naive move to /usr, this directory would be lost on upgrades (the "DEP17 P6" problem). Please find a patch attached to install the relevant paths into /usr, and a mitigation for the lost directory. I've chosen the postinst way, as your package already had a postinst dealing with this path. Note: this should not be backported to bookworm. If you intend to backport, please revert the entire patch for the backport. If your package will change for the t64 transition or otherwise rename/split/move its binaries (packages) during trixie, please then upload to experimental and get in touch with the UsrMerge driver, please see the wiki [1]. Chris [1] https://wiki.debian.org/UsrMerge diff -Nru foo2zjs-20200505dfsg0/debian/changelog foo2zjs-20200505dfsg0/debian/changelog --- foo2zjs-20200505dfsg0/debian/changelog 2021-09-02 14:45:45.0 +0200 +++ foo2zjs-20200505dfsg0/debian/changelog 2024-01-13 23:36:22.0 +0100 @@ -1,3 +1,12 @@ +foo2zjs (20200505dfsg0-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Install into UsrMerged-layout (udev files, firmware directory). +Restore /usr/lib/firmware/hp as an empty directory in postinst if it +is lost on upgrades. (DEP17 P6) (Closes: #-1) + + -- Chris Hofstaedtler Sat, 13 Jan 2024 23:36:22 +0100 + foo2zjs (20200505dfsg0-2) unstable; urgency=medium * Remove myself from Uploaders diff -Nru foo2zjs-20200505dfsg0/debian/NEWS foo2zjs-20200505dfsg0/debian/NEWS --- foo2zjs-20200505dfsg0/debian/NEWS 2021-09-02 14:45:45.0 +0200 +++ foo2zjs-20200505dfsg0/debian/NEWS 2024-01-13 23:36:22.0 +0100 @@ -1,7 +1,7 @@ foo2zjs (20090908dfsg-2) unstable; urgency=low Starting with this version all HP firmwares are looked for into - /lib/firmware/hp/ instead of upstream /usr/share/foo2zjs/firmware/ + /usr/lib/firmware/hp/ instead of upstream /usr/share/foo2zjs/firmware/ (thus solving bug #517957). The upstream /usr/bin/getweb and /lib/udev/hplj1000 scripts have diff -Nru foo2zjs-20200505dfsg0/debian/patches/0012-Use-the-same-firmware-folder-for-all-HP-LJ-printers.patch foo2zjs-20200505dfsg0/debian/patches/0012-Use-the-same-firmware-folder-for-all-HP-LJ-printers.patch --- foo2zjs-20200505dfsg0/debian/patches/0012-Use-the-same-firmware-folder-for-all-HP-LJ-printers.patch 2021-09-02 14:45:45.0 +0200 +++ foo2zjs-20200505dfsg0/debian/patches/0012-Use-the-same-firmware-folder-for-all-HP-LJ-printers.patch 2024-01-13 23:36:22.0 +0100 @@ -2,6 +2,8 @@ Date: Tue, 4 Oct 2016 11:43:55 +0200 Subject: Use the same firmware folder for all HP LJ printers +[zeha@d.o 2024-01-13: changed to /usr/ for UsrMerge layout] + --- hplj1000 | 6 -- hplj10xx.conf | 10 +- @@ -58,7 +60,7 @@ match "vendor" "0x03f0"; match "product" "0x3d17"; -action "cat /usr/share/foo2xqx/firmware/sihpP1005.dl > /dev/$device-name"; -+action "cat /lib/firmware/hp/sihpP1005.dl > /dev/$device-name"; ++action "cat /usr/lib/firmware/hp/sihpP1005.dl > /dev/$device-name"; }; # Firmware download HP LaserJet P1006 printer @@ -66,7 +68,7 @@ match "vendor" "0x03f0"; match "product" "0x3e17"; -action "cat /usr/share/foo2xqx/firmware/sihpP1006.dl > /dev/$device-name"; -+action "cat /lib/firmware/hp/sihpP1006.dl > /dev/$device-name"; ++action "cat /usr/lib/firmware/hp/sihpP1006.dl > /dev/$device-name"; }; # Firmware download HP LaserJet P1007 printer @@ -74,7 +76,7 @@ match "vendor" "0x03f0"; match "product" "0x4817"; -action "cat /usr/share/foo2xqx/firmware/sihpP1005.dl > /dev/$device-name"; -+action "cat /lib/firmware/hp
Bug#1063451: marked as done (foo2zjs: move all files to /usr DEP17 + empty directory loss)
Your message dated Sat, 27 Apr 2024 09:20:28 + with message-id and subject line Bug#1060769: fixed in foo2zjs 20200505dfsg0-3 has caused the Debian Bug report #1060769, regarding foo2zjs: move all files to /usr DEP17 + empty directory loss 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.) -- 1060769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: foo2zjs Version: 20200505dfsg0-2 Tags: patch User: helm...@debian.org Usertags: dep17m2 dep17p6 Hi, we are in the process of finalizing the /usr-merge by moving all aliased files from / to /usr via DEP17. printer-driver-foo2zjs contains an empty directory /lib/firmware/hp in an aliased location. If this is moved to /usr, it will be lost in a package upgrade. This loss is flagged by dumat and is the reason I'm writing this mail. Since no other package in Debian writes any files to /lib/firmware/hp or /usr/lib/firmware/hp, this loss can only happen during the package upgrade. Therefore, recreating the lost directory in printer-driver-foo2zjs.postinst is a reasonable mitigation. I've implemented the /usr-move and this mitigation in the attached patch. After applying it, the /usr-move is done from a foo2zjs perspective. Note that this patch must not be backported to bookworm-backports. I hope this is not a problem as foo2zjs has not been backported in earlier releases. In case it needs to be backports, this patch needs to be reverted. If this leaves any questions, don't hesitate to ask. Helmut DEP17: http://subdivi.de/~helmut/dep17.html diff --minimal -Nru foo2zjs-20200505dfsg0/debian/NEWS foo2zjs-20200505dfsg0/debian/NEWS --- foo2zjs-20200505dfsg0/debian/NEWS 2021-09-02 14:45:45.0 +0200 +++ foo2zjs-20200505dfsg0/debian/NEWS 2024-02-08 13:55:52.0 +0100 @@ -1,7 +1,7 @@ foo2zjs (20090908dfsg-2) unstable; urgency=low Starting with this version all HP firmwares are looked for into - /lib/firmware/hp/ instead of upstream /usr/share/foo2zjs/firmware/ + /usr/lib/firmware/hp/ instead of upstream /usr/share/foo2zjs/firmware/ (thus solving bug #517957). The upstream /usr/bin/getweb and /lib/udev/hplj1000 scripts have diff --minimal -Nru foo2zjs-20200505dfsg0/debian/changelog foo2zjs-20200505dfsg0/debian/changelog --- foo2zjs-20200505dfsg0/debian/changelog 2021-09-02 14:45:45.0 +0200 +++ foo2zjs-20200505dfsg0/debian/changelog 2024-02-08 14:01:50.0 +0100 @@ -1,3 +1,10 @@ +foo2zjs (20200505dfsg0-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * DEP17: Move all aliased files to /usr. (Closes: #-1) + + -- Helmut Grohne Thu, 08 Feb 2024 14:01:50 +0100 + foo2zjs (20200505dfsg0-2) unstable; urgency=medium * Remove myself from Uploaders diff --minimal -Nru foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs-common.install foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs-common.install --- foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs-common.install 2021-09-02 14:45:45.0 +0200 +++ foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs-common.install 2024-02-08 13:54:31.0 +0100 @@ -1,7 +1,7 @@ PPD/* usr/share/ppd/foo2zjs/ debian/printer-driver-foo2zjs-common.ppd-updater /usr/share/cups/ppd-updaters/ getweb usr/sbin -hplj1000 lib/udev +hplj1000 usr/lib/udev hplj1020.desktop usr/share/applications/ hplj1020_icon.png usr/share/pixmaps usr/bin/foo2ddst-wrapper diff --minimal -Nru foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.dirs foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.dirs --- foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.dirs2021-09-02 14:45:45.0 +0200 +++ foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.dirs2024-02-08 13:58:25.0 +0100 @@ -1 +1 @@ -/lib/firmware/hp/ +/usr/lib/firmware/hp/ diff --minimal -Nru foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.links foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.links --- foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.links 2021-09-02 14:45:45.0 +0200 +++ foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.links 2024-02-08 13:55:25.0 +0100 @@ -1,10 +1,10 @@ -lib/udev/hplj1000 lib/udev/hplj1005 -lib/udev/hplj1000 lib/udev/hplj1018 -lib/udev/hplj1000 lib/udev/hplj1020 -lib/udev/hplj1000 lib/udev/hpljP1005 -lib/udev/hplj1000 lib/udev/hpljP1006 -lib/udev/hplj1000 lib/udev/hpljP1007 -lib/udev/hplj1000 lib/udev/hpljP1008 -lib/udev/hplj1000 lib/udev/hpljP1505 -lib/udev/hplj1000 lib/udev/hpljP1505n +usr/lib/udev/hplj1000 usr/lib/udev/hplj1005 +usr
Bug#1064089: marked as done (gutenprint: NMU diff for 64-bit time_t transition)
Your message dated Sat, 27 Apr 2024 00:19:32 + with message-id and subject line Bug#1064089: fixed in gutenprint 5.3.4.20220624T01008808d602-2 has caused the Debian Bug report #1064089, regarding gutenprint: NMU diff for 64-bit time_t transition 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.) -- 1064089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gutenprint Version: 5.3.4.20220624T01008808d602-1 Severity: important Tags: patch User: debian-...@lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified gutenprint as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for gutenprint. Please find the patch for this NMU attached. Unfortunately, due to unrelated bugs (bug #1064088), your package fails to build in unstable and therefore we will not be uploading an NMU for this. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: gutenprint Source-Version: 5.3.4.20220624T01008808d602-2 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of gutenprint, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated gutenprint package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Apr 2024 23:10:00 +0200 Source: gutenprint Architecture: source Version: 5.3.4.20220624T01008808d602-2 Distribution: unstable Urgency: medium Maintainer: Debian Printing Group Changed-By: Thorsten Alteholz Closes: 1064088 1064089 Changes: gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium . * do not build this package on 32bit architectures anymore Closes: #1064088 Closes: #1064089 There was no patch attached to #1064089, so I can not reproduce the problems mentioned in #1064088. I am fed up with this poorly done transition, so I won't spend more time with this. Sorry 32bit people. Checksums-Sha1: 263f3b632560f12513538b513e696e0db53eb8da 3210 gutenprint_5.3.4.20220624T01008808d602-2.dsc f070be098b05810df047571faa521c7cec690b54 95036 gutenprint_5.3.4.20220624T01008808d602-2.debian.tar.xz a8e143047c6f88a82d89d031ccff7acd64497c0a 20798 gutenprint_5.3.4.20220624T01008808d602-2_amd64.buildinfo Checksums-Sha256: 6661d2a2c7a9c6615c188217c93ddb7db4635d24474cd61e2f7ac144e8fd7174 3210 gutenprint_5.3.4.20220624T01008808d602-2.dsc 858c4091f2d9418f9e35cb37b0d2bfe181a819ddd4a08c00eedfae8a1816bf68 95036 gutenprint_5.3.4.20220624T01008808d602-2.debian.tar.xz 4e06c6331a979761b6d018a5cd9862099f92da2c2146ec6fb49de6501b07c7ca 20798 gutenprint_5.3.4.20220624T01008808d602-2_amd64.buildinfo Files: ea7ac1f5ff28e39aeaeb7108783a112a 3210 graphics optional gutenprint_5.3.4.20220624T01008808d602-2.dsc 51151ed4e4d37c3ee58d2a49eb1bf9ff 95036 graphics optional
Bug#1064088: marked as done (gutenprint: FTBFS in unstable)
Your message dated Sat, 27 Apr 2024 00:19:32 + with message-id and subject line Bug#1064088: fixed in gutenprint 5.3.4.20220624T01008808d602-2 has caused the Debian Bug report #1064088, regarding gutenprint: FTBFS in unstable 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.) -- 1064088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gutenprint Version: 5.3.4.20220624T01008808d602-1 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble Dear maintainers, gutenprint now fails to build from source in unstable. Initially, it fails to build because debian/libgutenprintui2-2.symbols expects symbols to be present that are not part of this library's API but only a result of using yacc internally. Marking these symbols optional gets past this issue: (optional)yy_create_buffer@Base 5.3.0~pre1 (optional)yy_delete_buffer@Base 5.3.0~pre1 (optional)yy_flex_debug@Base 5.3.0~pre1 (optional)yy_flush_buffer@Base 5.3.0~pre1 (optional)yy_scan_buffer@Base 5.3.0~pre1 (optional)yy_scan_bytes@Base 5.3.0~pre1 (optional)yy_scan_string@Base 5.3.0~pre1 (optional)yy_switch_to_buffer@Base 5.3.0~pre1 (optional)yyalloc@Base 5.3.0~pre1 (optional)yychar@Base 5.3.0~pre1 (optional)yydebug@Base 5.3.1 [...] But then the package fails because dh_missing complains about files installed into debian/tmp not being included in any package: [...] make[1]: Leaving directory '/tmp/time-t/gutenprint-5.3.4.20220624T01008808d602' dh_missing dh_missing: warning: usr/share/gutenprint/doc/reference-html/a2128.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/a2128.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c1723.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c1723.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c193.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c193.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c1974.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c1974.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c199.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c199.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c38.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c38.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c463.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c463.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/c47.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/c47.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/f14.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/f14.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/index.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/index.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x1675.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/x1675.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x1740.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/x1740.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x2159.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/x2159.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x270.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/x270.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x66.html exists in debian/tmp but is not installed to anywhere (related file: "doc/developer/reference-html/x66.html") dh_missing: warning: usr/share/gutenprint/doc/reference-html/x78.html exists in debian/tmp but is not installed to anyw
Bug#1066348: marked as done (hplip: FTBFS: scan/sane/hpaio.c:364:12: error: implicit declaration of function ‘orblite_init’ [-Werror=implicit-function-declaration])
Your message dated Fri, 26 Apr 2024 23:35:05 +
with message-id
and subject line Bug#1066348: fixed in hplip 3.22.10+dfsg0-5
has caused the Debian Bug report #1066348,
regarding hplip: FTBFS: scan/sane/hpaio.c:364:12: error: implicit declaration
of function ‘orblite_init’ [-Werror=implicit-function-declaration]
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.)
--
1066348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hplip
Version: 3.22.10+dfsg0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> /bin/bash ./libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"HP\
> Linux\ Imaging\ and\ Printing\" -DPACKAGE_TARNAME=\"hplip\"
> -DPACKAGE_VERSION=\"3.22.10\" -DPACKAGE_STRING=\"HP\ Linux\ Imaging\ and\
> Printing\ 3.22.10\" -DPACKAGE_BUGREPORT=\"3.22.10\" -DPACKAGE_URL=\"\"
> -DPACKAGE=\"hplip\" -DVERSION=\"3.22.10\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1
> -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1
> -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBDL=1 -DHAVE_PTHREAD_H=1
> -DHAVE_JPEGLIB_H=1 -DHAVE_UINT32_T=1 -DHAVE_LIBHPIP=1 -DHAVE_LIBHPIP=1
> -DDISABLE_IMAGEPROCESSOR=1 -DHAVE_LIBCRYPTO=1 -DHAVE_LIBNETSNMP=1
> -DHAVE_NET_SNMP_NET_SNMP_CONFIG_H=1 -DHAVE_LIBAVAHI=1
> -DHAVE_LIBAVAHI_CLIENT=1 -DHAVE_LIBAVAHI_COMMON=1
> -DHAVE_AVAHI_CLIENT_CLIENT_H=1 -DHAVE_AVAHI_COMMON_MALLOC_H=1
> -DHAVE_CUPS_CUPS_H=1 -DHAVE_CUPS_PPD_H=1 -DHAVE_LIBUSB_1_0_LIBUSB_H=1
> -DHAVE_PYTHON_H=1 -DHAVE_DBUS=1 -I. -Iip -Iio/hpmud -Iscan/sane -Iprnt/hpijs
> -Icommon/ -Iprotocol -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/dbus-1.0
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -Iprotocol -Iprotocol/discovery
> -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -I/usr/include/python3.11 -I/usr/include/python3.11 -DCONFDIR=\"/etc/hp\" -c
> -o libsane_hpaio_la-pml.lo `test -f 'scan/sane/pml.c' || echo
> './'`scan/sane/pml.c
> In file included from scan/sane/mfpdtf.c:28:
> scan/sane/common.h:191:1: warning: ‘visibility’ attribute ignored on
> non-class types [-Wattributes]
> 191 | char* __attribute__ ((visibility ("hidden"))) itoa(int value, char*
> str, int radix);
> | ^~~~
> scan/sane/mfpdtf.c: In function ‘MfpdtfReadInnerBlock’:
> scan/sane/mfpdtf.c:476:13: warning: ignoring return value of ‘write’ declared
> with attribute ‘warn_unused_result’ [-Wunused-result]
> 476 | write( mfpdtf->fdLog, buffer, r ); /* log raw rgb data,
> use imagemagick to display */
> | ^
> In file included from scan/sane/hpaio.h:32,
> from scan/sane/hpaio.c:48:
> scan/sane/common.h:191:1: warning: ‘visibility’ attribute ignored on
> non-class types [-Wattributes]
> 191 | char* __attribute__ ((visibility ("hidden"))) itoa(int value, char*
> str, int radix);
> | ^~~~
> In file included from scan/sane/hpaio.c:57:
> scan/sane/sanei_debug.h:167: warning: "DBG" redefined
> 167 | # define DBGDBG_LOCAL
> |
> In file included from scan/sane/hpaio.c:41:
> protocol/discovery/avahiDiscovery.h:79: note: this is the location of the
> previous definition
>79 |#define DBG(args...)
> |
> scan/sane/hpaio.c: In function ‘GetCupsPrinters’:
> scan/sane/hpaio.c:202:4: warning: ‘httpConnectEncrypt’ is deprecated: Use
> httpConnect2 instead. [-Wdeprecated-declarations]
> 202 |if ((http = httpConnectEncrypt(cupsServer(), ippPort(),
> cupsEncryption())) == NULL)
> |^~
> In file included from /usr/include/cups/ipp.h:18,
>
Processed: [bts-link] source package cups
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package cups > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1033616 (http://bugs.debian.org/1033616) > # Bug title: cups prepends job number to job-name so job names near 255 > characters may be too long > # * https://github.com/OpenPrinting/cups/issues/644 > # * remote status changed: open -> closed > # * closed upstream > tags 1033616 + fixed-upstream Bug #1033616 [cups] cups prepends job number to job-name so job names near 255 characters may be too long Added tag(s) fixed-upstream. > usertags 1033616 - status-open Usertags were: status-open. There are now no usertags set. > usertags 1033616 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1069630 in 2.0.0-1, notfound 1069800 in 21.1.4-1, found 1069800 in 24.1.4-1, tagging 1069790
Processing commands for cont...@bugs.debian.org: > found 1069630 2.0.0-1 Bug #1069630 [libcupsfilters2-dev] libcupsfilters-dev and libcupsfilters2-dev have an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libcupsfilters.a, /usr/lib/x86_64-linux-gnu/libcupsfilters.so and /usr/lib/x86_64-linux-gnu/pkgconfig/libcupsfilters.pc Marked as found in versions libcupsfilters/2.0.0-1. > notfound 1069800 21.1.4-1 Bug #1069800 [src:cloud-init] FTBFS: test failures in buildd environment The source 'cloud-init' and version '21.1.4-1' do not appear to match any binary packages No longer marked as found in versions cloud-init/21.1.4-1. > found 1069800 24.1.4-1 Bug #1069800 [src:cloud-init] FTBFS: test failures in buildd environment The source 'cloud-init' and version '24.1.4-1' do not appear to match any binary packages Marked as found in versions cloud-init/24.1.4-1. > tags 1069790 + sid trixie Bug #1069790 [librust-err-derive-dev] librust-err-derive-dev: impossible to install Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069630 1069790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069790 1069800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: foo2zjs: diff for NMU version 20200505dfsg0-2.1
Processing control commands: > tags 1060769 + pending Bug #1060769 [src:foo2zjs] foo2zjs: mitigate empty directory loss for usrmerge (DEP17 P6) Bug #1063451 [src:foo2zjs] foo2zjs: move all files to /usr DEP17 + empty directory loss Added tag(s) pending. Added tag(s) pending. -- 1060769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060769 1063451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1060769 1063451
Processing commands for cont...@bugs.debian.org: > forcemerge 1060769 1063451 Bug #1060769 [src:foo2zjs] foo2zjs: mitigate empty directory loss for usrmerge (DEP17 P6) Bug #1063451 [src:foo2zjs] foo2zjs: move all files to /usr DEP17 + empty directory loss Merged 1060769 1063451 > thanks Stopping processing here. Please contact me if you need assistance. -- 1060769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060769 1063451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1069313, tagging 1056898, tagging 1069339, tagging 1069313, tagging 1069335, tagging 1069333 ...
.cgi?bug=1069385 1069471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libcupsfilters-dev and libcupsfilters2-dev have an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libcupsfilters.a, /usr/lib/x86_64-linux-gnu/libcupsfilters.so and /usr/lib/x86_64-li
Processing control commands: > affects -1 + libcupsfilters-dev Bug #1069630 [libcupsfilters2-dev] libcupsfilters-dev and libcupsfilters2-dev have an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libcupsfilters.a, /usr/lib/x86_64-linux-gnu/libcupsfilters.so and /usr/lib/x86_64-linux-gnu/pkgconfig/libcupsfilters.pc Added indication that 1069630 affects libcupsfilters-dev -- 1069630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058774: marked as done (cups-filters: use systemd.pc to place systemd system units)
Your message dated Sun, 21 Apr 2024 09:19:07 +
with message-id
and subject line Bug#1058774: fixed in cups-filters 1.28.17-4
has caused the Debian Bug report #1058774,
regarding cups-filters: use systemd.pc to place systemd system units
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.)
--
1058774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cups-filters
Version: 1.28.17-3
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2
Dear Maintainer,
your package install a systemd system unit, currently into /lib.
This file needs to be moved to /usr/lib as part of Debian's
usr-merge effort [1].
Attached you will find a patch using systemd.pc to place these files
(using pkg-config). This works for unstable today, and also for
bookworm, and is safe to do now.
Later during the trixie cycle I expect this bug class to raise in
priority.
If during the trixie cycle your package will undergo structural
changes or any other file moves, please see the wiki and upload
to experimental first when these changes are done.
Thank you for considering,
Chris
[1] https://wiki.debian.org/UsrMerge
diff -Nru cups-filters-1.28.17/debian/changelog
cups-filters-1.28.17/debian/changelog
--- cups-filters-1.28.17/debian/changelog 2023-05-19 18:25:20.0
+0200
+++ cups-filters-1.28.17/debian/changelog 2023-12-15 23:49:17.0
+0100
@@ -1,3 +1,10 @@
+cups-filters (1.28.17-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Let systemd.pc place systemd units. (Closes: #-1)
+
+ -- Chris Hofstaedtler Fri, 15 Dec 2023 23:49:17 +0100
+
cups-filters (1.28.17-3) unstable; urgency=medium
* CVE-2023-24805
diff -Nru cups-filters-1.28.17/debian/control
cups-filters-1.28.17/debian/control
--- cups-filters-1.28.17/debian/control 2023-05-19 10:48:08.0 +0200
+++ cups-filters-1.28.17/debian/control 2023-12-15 23:49:04.0 +0100
@@ -34,6 +34,7 @@
sharutils,
zlib1g-dev,
libexif-dev,
+ systemd-dev,
Standards-Version: 4.6.0
Vcs-Browser: https://salsa.debian.org/printing-team/cups-filters
Vcs-Git: https://salsa.debian.org/printing-team/cups-filters.git
diff -Nru cups-filters-1.28.17/debian/cups-browsed.install
cups-filters-1.28.17/debian/cups-browsed.install
--- cups-filters-1.28.17/debian/cups-browsed.install2023-05-19
10:48:08.0 +0200
+++ cups-filters-1.28.17/debian/cups-browsed.install2023-12-15
23:49:17.0 +0100
@@ -1,4 +1,4 @@
-../../utils/cups-browsed.service lib/systemd/system/
+../../utils/cups-browsed.service ${env:deb_systemdsystemunitdir}/
../apparmor/usr.sbin.cups-browsed etc/apparmor.d/
etc/cups/cups-browsed.conf
usr/lib/cups/backend/implicitclass
diff -Nru cups-filters-1.28.17/debian/rules cups-filters-1.28.17/debian/rules
--- cups-filters-1.28.17/debian/rules 2023-05-19 10:48:08.0 +0200
+++ cups-filters-1.28.17/debian/rules 2023-12-15 23:49:17.0 +0100
@@ -10,6 +10,8 @@
SUBSTVARS = -Vcf:Recommends="lynx"
endif
+export deb_systemdsystemunitdir = $(shell pkg-config
--variable=systemdsystemunitdir systemd | sed s,^/,,)
+
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
%:
--- End Message ---
--- Begin Message ---
Source: cups-filters
Source-Version: 1.28.17-4
Done: Thorsten Alteholz
We believe that the bug you reported is fixed in the latest version of
cups-filters, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thorsten Alteholz (supplier of updated cups-filters
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 21 Apr 2024 09:25:20 +0200
Source: cups-filters
Architecture: source
Version: 1.28.17-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team
Changed-By: Thorsten Alteholz
Closes: 1040699 1058774
Changes:
cups-filters (1.28.17-4) unstable; urgency=medium
.
* debian/watch: watch file now only finds version 1.*
(for version 2.* see cups-filters2)
* debian/control: change dependenci
Bug#1040699: marked as done (cups-filters-core-drivers: Please consider adjusting the Depends: line)
Your message dated Sun, 21 Apr 2024 09:19:07 + with message-id and subject line Bug#1040699: fixed in cups-filters 1.28.17-4 has caused the Debian Bug report #1040699, regarding cups-filters-core-drivers: Please consider adjusting the Depends: line 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.) -- 1040699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cups-filters-core-drivers Version: 1.28.17-3 Severity: important Tags: patch cups-filters-core-drivers depends on cups-ipp-utils, probably because it has ippfind, which is used by the driverless utility. cups-ipp-utils conflicts with ippsample, which also installs ippfind. Installing ippsample is not possible without seriously affecting the printing system. Would a depends of cups-ipp-utils | ippsample be suitable? Regards, Brian. --- End Message --- --- Begin Message --- Source: cups-filters Source-Version: 1.28.17-4 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of cups-filters, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated cups-filters package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 21 Apr 2024 09:25:20 +0200 Source: cups-filters Architecture: source Version: 1.28.17-4 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Thorsten Alteholz Closes: 1040699 1058774 Changes: cups-filters (1.28.17-4) unstable; urgency=medium . * debian/watch: watch file now only finds version 1.* (for version 2.* see cups-filters2) * debian/control: change dependencies of cups-filters-core-drivers cups-ipp-utils|ippsample instead of cups-ipp-utils (Closes: #1040699) * add patch to let systemd.pc place systemd units (Closes: #1058774) Thanks a lot to Chris Hofstaedtler for providing the patch. Checksums-Sha1: b53221eae31eed3de308fd352ed7f178928a7e7c 3028 cups-filters_1.28.17-4.dsc c5a04b7562449b9f0dfae55f02ead8ac9602fd78 86604 cups-filters_1.28.17-4.debian.tar.xz 513f7e517b39f2d9623f2ab1b265bd80bc97014b 14608 cups-filters_1.28.17-4_amd64.buildinfo Checksums-Sha256: 17447174c11e1a9e5a0e2cdcc7b589e631528415ebcab89d140b5107f63b6911 3028 cups-filters_1.28.17-4.dsc 2fa658a4a2a6a68633388473223f1b19689ab677537244bbf9ef1a7b6d1f54e0 86604 cups-filters_1.28.17-4.debian.tar.xz 92c1019d7aa84f9729e01f0a02e0023a075adc90bfd82ca50422818d27b06827 14608 cups-filters_1.28.17-4_amd64.buildinfo Files: 59803624de284a4a1870f73db85daa07 3028 net optional cups-filters_1.28.17-4.dsc 1088317d0625c93e7ea28ee28dfb3d31 86604 net optional cups-filters_1.28.17-4.debian.tar.xz b16e84dd778627275f98f5259ff59429 14608 net optional cups-filters_1.28.17-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmYk1iFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYR+V/D/9wZQ25R/CAuEp3uMIRMgo5SeQNgNvc 6l/5QMYqtyP2v7CBbnzkSrZONhXD2v50YRfxlu+uYJe3e22xCc2FGQwaLtz7flcS 8gZpUzw5oPFEj2HBRZ9QHuJNTs2toha4vitsHlJV3VUXnEFbuQDXzgm2atUCakOQ DTNZ7RP00Ju4CJQiB5+PekXOdAdrPEOoLpB18mb03yUpPIP1rfbGhwHOf8TAmvmk YG9unwqcqSIxRv3uURji8vr/IqbAoCpNsYBZ3AygtoCFrznbhtEiJuRHSLgPDJC9 nGnNus4e4j9u5Yj9zYtqms3QZRBXjnbl+G18MT+Vs9qB9lCgXeZ7BsAXLMy47ZUL Cm81Dk0KYGtXoVYbZSJrUvUpLBo9spA+olLTisLJE+UqNWgkArZKRqoLS8EtGJVK ExRk9EuBCAnzlsBECw9DDJe6AeByyqovbx2SPtTjO0zjhCYVNrDQpUODmaNgI25W QyGBpTWrqF+INs3apaWTygfIZ1jTOplNj4h6MfFJWelYIpaPzKZUF9EWaFkoEK9N FgBH5QExiiOxNpiakxyi2hYei2nyFSXnWJjnOUnTgFmE726jePVm0syioanLS6Hr GyTUfoot91OpuxGMWJqIQfKAktAG/JG7Ge0J6b68+MbtcWFBta/JGeMm74GqNhD3 guFCfA5TA1JDtA== =+OdR -END PGP SIGNATURE- pgpcjpjbXxn41.pgp Description: PGP signature --- End Message ---
Processed: tagging 1069225, tagging 1069299, tagging 1069308, tagging 1069310, tagging 1069313, tagging 1069333 ...
Processing commands for cont...@bugs.debian.org: > tags 1069225 + sid trixie Bug #1069225 [src:freesas] freesas: FTBFS: fatal error: numpy/arrayobject.h: No such file or directory Added tag(s) trixie and sid. > tags 1069299 + sid trixie Bug #1069299 [src:kodi-visualization-waveform] kodi-visualization-waveform FTBFS on arm*: does not agree on gl vs gles Added tag(s) trixie and sid. > tags 1069308 + sid trixie Bug #1069308 [src:gnome-subtitles] FTBFS: tests failed Added tag(s) sid and trixie. > tags 1069310 + sid trixie Bug #1069310 [golang-github-hanwen-go-fuse-dev] FTBFS: tests failed Added tag(s) trixie and sid. > tags 1069313 + sid trixie Bug #1069313 [src:jskeus] FTBFS: implicit declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? Added tag(s) sid and trixie. > tags 1069333 + sid trixie Bug #1069333 [ippsample] Not installable due to hardcoded pre-t64 library deps Added tag(s) sid and trixie. > tags 1069335 + sid trixie Bug #1069335 [prads] Not installable due to hardcoded pre-t64 library deps Added tag(s) trixie and sid. > tags 1069339 + sid trixie Bug #1069339 [libvdeplug-pcap] Not installable due to hardcoded pre-t64 library deps Added tag(s) sid and trixie. > tags 1069344 + sid trixie Bug #1069344 [src:netgen] netgen: FTBFS on armhf [debian/rules:66: override_dh_auto_test] Added tag(s) sid and trixie. > tags 1069347 + sid trixie Bug #1069347 [src:rust-servo-freetype-sys] rust-servo-freetype-sys: FTBFS on armel,armhf CMake Error: The source directory "/<>/freetype2" does not exist. Added tag(s) trixie and sid. > tags 1069348 + sid trixie Bug #1069348 [src:ruby-ethon] ruby-ethon: FTBFS Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069225 1069299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069299 1069308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069308 1069310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069310 1069313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069313 1069333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069333 1069335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069335 1069339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069339 1069344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069344 1069347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069347 1069348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1001172 to printer-driver-cups-pdf: Post processing script execution bug
Processing commands for cont...@bugs.debian.org: > retitle 1001172 printer-driver-cups-pdf: Post processing script execution bug Bug #1001172 [printer-driver-cups-pdf] Post processing script execution bug Changed Bug title to 'printer-driver-cups-pdf: Post processing script execution bug' from 'Post processing script execution bug'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067481: marked as done (cups: package (transitively?) conflicts with KDE)
Your message dated Sat, 23 Mar 2024 23:49:35 + (UTC) with message-id and subject line Re: cups: package (transitively?) conflicts with KDE has caused the Debian Bug report #1067481, regarding cups: package (transitively?) conflicts with KDE 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.) -- 1067481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cups Version: 2.4.7-1+b1 Severity: normal X-Debbugs-Cc: debianb...@schirmeier.com Dear Maintainer, on 2024-03-19, the following apt dist-upgrade removed -- without me noticing -- cups from my system, leaving me without printing capabilities: Commandline: apt -V dist-upgrade Requested-By: hsc (1000) Install: libqt5xml5t64:amd64 (5.15.10+dfsg-7.2+b1, automatic), libhogweed6t64:amd64 (3.9.1-2.2, automatic), libhogweed6t64:i386 (3.9.1-2.2, automatic), libqt5sql5t64:amd64 (5.15.10+dfsg-7.2+b1, automatic), libgsoap-2.8.132t64:amd64 (2.8.132-2.1+b1, automatic), libcups2t64:amd64 (2.4.7-1.2+b1, automatic), libqt5gui5-gles:amd64 (5.15.10+dfsg-5, automatic), libcurl3t64-gnutls:amd64 (8.6.0-4, automatic), libxt6t64:amd64 (1:1.2.1-1.2, automatic), libqt5printsupport5t64:amd64 (5.15.10+dfsg-7.2+b1, automatic), libqt5widgets5t64:amd64 (5.15.10+dfsg-7.2+b1, automatic), libnextcloudsync0t64:amd64 (3.11.0-1.1+b1, automatic), libprotobuf32t64:amd64 (3.21.12-8.2, automatic), libqt5dbus5t64:amd64 (5.15.10+dfsg-7.2+b1, automatic), libqt5network5t64:amd64 (5.15.10+dfsg-7.2+b1, automatic), libssl3t64:amd64 (3.1.5-1.1, automatic), libqt5quick5-gles:amd64 (5.15.10+dfsg-2+b1, automatic), libpng16-16t64:amd64 (1.6.43-3, automatic), libqt5core5t64:amd64 (5.15.10+dfsg-7.2+b1, automatic), libmtdev1t64:amd64 (1.1.6-1.1, automatic) Upgrade: orca:amd64 (45.2-1, 46.0-1), virtualbox:amd64 (7.0.14-dfsg-4, 7.0.14-dfsg-4+b3), android-liblog:amd64 (1:34.0.4-1, 1:34.0.4-1+b1), dosfstools:amd64 (4.2-1, 4.2-1.1), libidn12:amd64 (1.42-1, 1.42-2), adb:amd64 (1:34.0.4-1, 1:34.0.4-1+b1), libwww-perl:amd64 (6.76-1, 6.77-1), google-chrome-stable:amd64 (122.0.6261.128-1, 123.0.6312.58-1), libsuitesparseconfig7:amd64 (1:7.6.0+dfsg-1, 1:7.6.1+dfsg-1), libbz2-dev:amd64 (1.0.8-5+b2, 1.0.8-5.1), libamd3:amd64 (1:7.6.0+dfsg-1, 1:7.6.1+dfsg-1), libgpm2:amd64 (1.20.7-10+b2, 1.20.7-11), bzip2:amd64 (1.0.8-5+b2, 1.0.8-5.1), libcamd3:amd64 (1:7.6.0+dfsg-1, 1:7.6.1+dfsg-1), python3-wheel:amd64 (0.42.0-1, 0.43.0-1), libfontenc1:amd64 (1:1.1.4-1+b2, 1:1.1.8-1), nextcloud-desktop-cmd:amd64 (3.11.0-1, 3.11.0-1.1+b1), android-libbase:amd64 (1:34.0.4-1, 1:34.0.4-1+b1), libssh2-1t64:amd64 (1.11.0-4.1, 1.11.0-4.1+b1), libcholmod5:amd64 (1:7.6.0+dfsg-1, 1:7.6.1+dfsg-1), python3-pyatspi:amd64 (2.46.0-2, 2.46.0-3), ifupdown:amd64 (0.8.41, 0.8.43), gsettings-desktop-schemas:amd64 (46~beta-3, 46~rc-1), android-libcutils:amd64 (1:34.0.4-1, 1:34.0.4-1+b1), libumfpack6:amd64 (1:7.6.0+dfsg-1, 1:7.6.1+dfsg-1), android-libziparchive:amd64 (1:34.0.4-1, 1:34.0.4-1+b1), gzip:amd64 (1.12-1, 1.12-1.1), libcolamd3:amd64 (1:7.6.0+dfsg-1, 1:7.6.1+dfsg-1), luametatex:amd64 (2.10.08+ds-1+b1, 2.11.01+really2.10.08+ds-1), endless-sky:amd64 (0.10.4-1, 0.10.4-1+b1), libgnutls30t64:amd64 (3.8.3-1.1, 3.8.3-1.1+b1), libgnutls30t64:i386 (3.8.3-1.1, 3.8.3-1.1+b1), virtualbox-qt:amd64 (7.0.14-dfsg-4, 7.0.14-dfsg-4+b3), extra-cmake-modules:amd64 (5.107.0-1, 5.107.0-2), nextcloud-desktop:amd64 (3.11.0-1, 3.11.0-1.1+b1), libbz2-1.0:amd64 (1.0.8-5+b2, 1.0.8-5.1), libbz2-1.0:i386 (1.0.8-5+b2, 1.0.8-5.1), libccolamd3:amd64 (1:7.6.0+dfsg-1, 1:7.6.1+dfsg-1), intel-microcode:amd64 (3.20231114.1, 3.20240312.1), bzip2-doc:amd64 (1.0.8-5, 1.0.8-5.1), libglib2.0-0t64:amd64 (2.78.4-4, 2.78.4-5), libglib2.0-0t64:i386 (2.78.4-4, 2.78.4-5) Remove: libcups2:amd64 (2.4.7-1+b1), libnextcloudsync0:amd64 (3.11.0-1), cups-filters:amd64 (1.28.17-3+b1), libcurl3-gnutls:amd64 (8.5.0-2), cups-bsd:amd64 (2.4.7-1+b1), libpango-1.0-0:i386 (1.52.0+ds-1), libqt5core5a:amd64 (5.15.10+dfsg-7), qtgstreamer-plugins-qt5:amd64 (1.2.0-5.2+b1), libcairo2:i386 (1.18.0-1+b1), bluez-cups:amd64 (5.71-1), cups-client:amd64 (2.4.7-1+b1), libpng-dev:amd64 (1.6.43-1), cups-daemon:amd64 (2.4.7-1+b1), r-base-dev:amd64 (4.3.2-1), libqt5network5:amd64 (5.15.10+dfsg-7), libfreetype6:i386 (2.13.2+dfsg-1+b1), libmtdev1:amd64 (1.1.6-1+b1), librsvg2-common:i386 (2.54.7+dfsg-2), qtdeclarative5-dev:amd64 (5.15.10+dfsg-2+b1), libgsoap-2.8.132:amd64 (2.8.132-2), libasound2-plugins:i386 (1.2.7.1-1+b1), libgdk-pixbuf-2.0-0:i386 (2.42.10+dfsg-3+b1), libqt5dbus5:amd64 (5.15.10
Bug#1065396: marked as done (ghostscript: Coordinate uploads for German man page transfer)
Your message dated Fri, 22 Mar 2024 05:07:05 + with message-id and subject line Bug#1065396: fixed in ghostscript 10.03.0~dfsg-1 has caused the Debian Bug report #1065396, regarding ghostscript: Coordinate uploads for German man page transfer 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.) -- 1065396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 10.0.0~dfsg-11+deb12u3 Severity: normal Hello Steve, ghostscript used to contain German man pages, however, they were not properly maintained. As detailed in [1] ghostscript removed the German man pages from its git repository on January 4th 2023. So the files are gone since Version 10.01.0rc1. I imported them into manpages-de and will start shipping them with the next release. As per transition rules [2] you will need to add Breaks: manpages-l10n (<4.22) in your debian/control. I will then add Breaks: ghostscript (<https://bugs.ghostscript.com/show_bug.cgi?id=705881 [2] https://wiki.debian.org/PackageTransition -- System Information: Debian Release: 12.5 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.77 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages ghostscript depends on: ii libc62.36-9+deb12u4 ii libgs10 10.0.0~dfsg-11+deb12u3 ghostscript recommends no packages. ghostscript suggests no packages. -- no debconf information -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ghostscript Source-Version: 10.03.0~dfsg-1 Done: Steve M. Robbins We believe that the bug you reported is fixed in the latest version of ghostscript, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated ghostscript package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 21 Mar 2024 22:44:42 -0500 Source: ghostscript Architecture: source Version: 10.03.0~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Steve M. Robbins Closes: 992893 1065396 Changes: ghostscript (10.03.0~dfsg-1) unstable; urgency=medium . [ Steve Robbins ] * [d50c139] Add "breaks" relationship with manpages-l10n to transition German manpages. Closes: #1065396. * [9adc766] Simplify ps2ascii script. Closes: #992893. * [15664c9] New upstream version 10.03.0~dfsg * [2396e20] Remove 0001_fix_pagelist.patch, applied in new version. * [e3b0739] Add build-dep on python3-sphinx-copybutton * [ff6b89f] Fix break relationship versioning. * [2020bbc] Update obsolete dependency package names. Checksums-Sha1: 61f74d8bf9013efbd3b0f46b1a7e35ea769db3a3 2817 ghostscript_10.03.0~dfsg-1.dsc be930c13717fd4db91998295c6ef81f658f40c6a 30100208 ghostscript_10.03.0~dfsg.orig.tar.xz 4bbbc892e97129e78afdbb07fcfdd6e823989315 84048 ghostscript_10.03.0~dfsg-1.debian.tar.xz d575078430fe345a7b19c0c4723ad59ecb492339 11903 ghostscript_10.03.0~dfsg-1_source.buildinfo Checksums-Sha256: 786795c4c80c1352215826cd09c66d785764245605c5989d8bb422ae3dbe11c2 2817 ghostscript_10.03.0~dfsg-1.dsc b0e9d8acb9e42b8b3244bb2cd5ad0fbf3348204d478ba3e7c00897b81288cd4d 30100208 ghostscript_10.03.0~dfsg.orig.tar.xz b584bb3d96a4091128fd0ba883cbe6f1ebf55f37c8c7ff4a496d904c90c085c6 84048 ghostscript_10.03.0~dfsg-1.debian.tar.xz a70e4575d03aa5428e9a570beffa927c5ae67a6096b415f3b451f5c49602396a 11903 ghostscript_10.03.0~dfsg-1_source.buildinfo Files: b7967c
Bug#992893: marked as done (ps2ascii: odd option handling)
Your message dated Fri, 22 Mar 2024 05:07:04 +
with message-id
and subject line Bug#992893: fixed in ghostscript 10.03.0~dfsg-1
has caused the Debian Bug report #992893,
regarding ps2ascii: odd option handling
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.)
--
992893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghostscript
Version: 9.53.3~dfsg-7
Severity: minor
Tags: patch
Dear Maintainer,
ps2ascii handles default arguments really oddly, including shelling out
for each test (note the "()") and doesn't quote GS_EXECUTABLE,
unlike the other scripts in lib/; please consider the attached patch,
which also uses symbolic names for the trap signals
Best,
наб
-- System Information:
Debian Release: 10.10
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-debug'), (500,
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-17-amd64 (SMP w/24 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ghostscript depends on:
ii libc6 2.28-10
ii libgs9 9.27~dfsg-2+deb10u4
Versions of packages ghostscript recommends:
ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.4
Versions of packages ghostscript suggests:
ii ghostscript-x 9.27~dfsg-2+deb10u4
-- no debconf information
--- ghostscript-9.53.3~dfsg.orig/lib/ps2ascii
+++ ghostscript-9.53.3~dfsg/lib/ps2ascii
@@ -9,13 +9,6 @@
# executable name set in the makefile
GS_EXECUTABLE=gs
-trap "rm -f _temp_.err _temp_.out" 0 1 2 15
+trap "rm -f _temp_.err _temp_.out" EXIT HUP INT TERM
-OPTIONS="-q -dSAFER -sDEVICE=txtwrite"
-if ( test $# -eq 0 ) then
-$GS_EXECUTABLE $OPTIONS -o - -
-elif ( test $# -eq 1 ) then
-$GS_EXECUTABLE $OPTIONS -o - "$1"
-else
-$GS_EXECUTABLE $OPTIONS -o "$2" "$1"
-fi
+"$GS_EXECUTABLE" -q -dSAFER -sDEVICE=txtwrite -o "${2:--}" "${1:--}"
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ghostscript
Source-Version: 10.03.0~dfsg-1
Done: Steve M. Robbins
We believe that the bug you reported is fixed in the latest version of
ghostscript, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 992...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Steve M. Robbins (supplier of updated ghostscript package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 21 Mar 2024 22:44:42 -0500
Source: ghostscript
Architecture: source
Version: 10.03.0~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team
Changed-By: Steve M. Robbins
Closes: 992893 1065396
Changes:
ghostscript (10.03.0~dfsg-1) unstable; urgency=medium
.
[ Steve Robbins ]
* [d50c139] Add "breaks" relationship with manpages-l10n to transition
German manpages. Closes: #1065396.
* [9adc766] Simplify ps2ascii script. Closes: #992893.
* [15664c9] New upstream version 10.03.0~dfsg
* [2396e20] Remove 0001_fix_pagelist.patch, applied in new version.
* [e3b0739] Add build-dep on python3-sphinx-copybutton
* [ff6b89f] Fix break relationship versioning.
* [2020bbc] Update obsolete dependency package names.
Checksums-Sha1:
61f74d8bf9013efbd3b0f46b1a7e35ea769db3a3 2817 ghostscript_10.03.0~dfsg-1.dsc
be930c13717fd4db91998295c6ef81f658f40c6a 30100208
ghostscript_10.03.0~dfsg.orig.tar.xz
4bbbc892e97129e78afdbb07fcfdd6e823989315 84048
ghostscript_10.03.0~dfsg-1.debian.tar.xz
d575078430fe345a7b19c0c4723ad59ecb492339 11903
ghostscript_10.03.0~dfsg-1_source.buildinfo
Checksums-Sha256:
786795c4c80c1352215826cd09c66d785764245605c5989d8bb422ae3dbe11c2 2817
ghostscript_10.03.0~dfsg-1.dsc
b0e9d8acb9e42b8b3244bb2cd5ad0fbf3348204d478ba3e7c00897b81288cd4d 30100208
Bug#1066460: marked as done (epson-inkjet-printer-escpr: FTBFS: mem.c:34:17: error: implicit declaration of function ‘err_system’; did you mean ‘system’? [-Werror=implicit-function-declaration])
Your message dated Mon, 18 Mar 2024 18:49:35 +
with message-id
and subject line Bug#1066460: fixed in epson-inkjet-printer-escpr 1.7.17-4
has caused the Debian Bug report #1066460,
regarding epson-inkjet-printer-escpr: FTBFS: mem.c:34:17: error: implicit
declaration of function ‘err_system’; did you mean ‘system’?
[-Werror=implicit-function-declaration]
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.)
--
1066460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: epson-inkjet-printer-escpr
Version: 1.7.17-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
> -DCUPS_FILTER_NAME=\"epson-escpr\"
> -DCUPS_FILTER_PATH=\"/usr/lib/cups/filter\" -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c -o epson_escpr_wrapper-wrapper.o
> `test -f 'wrapper.c' || echo './'`wrapper.c
> mem.c: In function ‘mem_malloc’:
> mem.c:34:17: error: implicit declaration of function ‘err_system’; did you
> mean ‘system’? [-Werror=implicit-function-declaration]
>34 | err_system ("mem_malloc");
> | ^~
> | system
> cc1: some warnings being treated as errors
> filter.c: In function ‘epsInitJob’:
> filter.c:132:9: error: implicit declaration of function ‘obsClear’
> [-Werror=implicit-function-declaration]
> 132 | obsClear();
> | ^~~~
> filter.c: In function ‘main’:
> filter.c:346:15: error: implicit declaration of function ‘SetupJobAttrib’
> [-Werror=implicit-function-declaration]
> 346 | err = SetupJobAttrib();
> | ^~
> filter.c:355:15: error: implicit declaration of function ‘pageAllocBuffer’
> [-Werror=implicit-function-declaration]
> 355 | err = pageAllocBuffer();
> | ^~~
> filter.c:374:15: error: implicit declaration of function ‘SendStartJob’; did
> you mean ‘epsStartJob’? [-Werror=implicit-function-declaration]
> 374 | err = SendStartJob(FALSE);
> | ^~~~
> | epsStartJob
> filter.c:537:33: error: implicit declaration of function ‘PrintBand’; did you
> mean ‘epsPrintBand’? [-Werror=implicit-function-declaration]
> 537 | PrintBand (rever_buf,
> bandBmp.widthBytes, );
> | ^
> | epsPrintBand
> make[3]: *** [Makefile:547: epson_escpr-mem.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/epson-inkjet-printer-escpr_1.7.17-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: epson-inkjet-printer-escpr
Source-Version: 1.7.17-4
Done: Thorsten Alteholz
We believe that the bug you reported is fixed in the latest version of
epson-inkjet-printer-escpr, which is due to be installed in the Debian FTP
archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please a
Bug#1066639: marked as done (rlpr: FTBFS: error.c:175:43: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 18:22:24 + with message-id and subject line Bug#1066639: fixed in rlpr 2.06-2 has caused the Debian Bug report #1066639, regarding rlpr: FTBFS: error.c:175:43: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration] 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.) -- 1066639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rlpr Version: 2.06-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../intl -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > `test -f 'error.c' || echo './'`error.c > error.c: In function ‘error_at_line’: > error.c:175:43: error: implicit declaration of function ‘strcmp’ > [-Werror=implicit-function-declaration] > 175 | (file_name == old_file_name || !strcmp (old_file_name, > file_name))) > | ^~ > error.c:52:1: note: include ‘’ or provide a declaration of ‘strcmp’ >51 | #include > +++ |+#include >52 | > cc1: some warnings being treated as errors > make[3]: *** [Makefile:221: error.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/rlpr_2.06-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: rlpr Source-Version: 2.06-2 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of rlpr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated rlpr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Mar 2024 14:03:02 +0100 Source: rlpr Architecture: source Version: 2.06-2 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Thorsten Alteholz Closes: 1066639 Changes: rlpr (2.06-2) unstable; urgency=medium . * add implicit.patch (Closes: #1066639) * use dh12 Checksums-Sha1: 6acb80a4e0f0d42974b390d8f404b85f3ed6c9ff 1969 rlpr_2.06-2.dsc 3b14ca164033d529eb8fd6e781301ac93cdf00fd 272200 rlpr_2.06.orig.tar.gz e9013ab885de7e376372f1ef577b91389fd315ac 6028 rlpr_2.06-2.debian.tar.xz 6a6016e19f7161edcb051f050fe51200d74490af 6526 rlpr_2.06-2_amd64.buildinfo Checksums-Sha256: 5fd0fdbf4a713884170dee838abbc138e87b5e7419dd62d8e376291a0238bda2 1969 rlpr_2.06-2.dsc 32ae5893f4b9250b7a02c98a41b5929cfdd5731b6efbd7edfc77c2c5314388f7 272200 rlpr_2.06.orig.tar.gz 0fa3cd2e3f91d9cc19d6c1c03fd189b2cafce8ec644d0878245abb8d2c9efdeb 6028 rlpr_2.06-2.debian.tar.xz 220a61f6504ff90ebe2c933cd047c7d52a053a270baea3ede395c1b990a70a83 6526 rlpr_2.06-2_amd64.buildinfo Files: a32911889
Bug#1066523: marked as done (lprng: FTBFS: auth/krb5_auth.c:55:24: error: implicit declaration of function ‘krb5_read_message’; did you mean ‘krb5_chpw_message’? [-Werror=implicit-function-declaration
Your message dated Sat, 16 Mar 2024 18:20:18 +
with message-id
and subject line Bug#1066523: fixed in lprng 3.8.B-8
has caused the Debian Bug report #1066523,
regarding lprng: FTBFS: auth/krb5_auth.c:55:24: error: implicit declaration of
function ‘krb5_read_message’; did you mean ‘krb5_chpw_message’?
[-Werror=implicit-function-declaration]
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.)
--
1066523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lprng
Version: 3.8.B-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I.. -I./include "-DLOCALEDIR=\"/usr/share/locale\""
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o lpq.o `test -f 'common/lpq.c' || echo './'`common/lpq.c
> auth/krb5_auth.c: In function ‘server_krb5_auth’:
> auth/krb5_auth.c:55:24: error: implicit declaration of function
> ‘krb5_read_message’; did you mean ‘krb5_chpw_message’?
> [-Werror=implicit-function-declaration]
>55 | # define read_message krb5_read_message
> |^
> auth/krb5_auth.c:284:34: note: in expansion of macro ‘read_message’
> 284 | while( (retval = read_message(context,,))
> == 0 ){
> | ^~~~
> auth/krb5_auth.c: In function ‘server_krb5_status’:
> auth/krb5_auth.c:56:25: error: implicit declaration of function
> ‘krb5_write_message’; did you mean ‘krb5_chpw_message’?
> [-Werror=implicit-function-declaration]
>56 | # define write_message krb5_write_message
> | ^~
> auth/krb5_auth.c:386:37: note: in expansion of macro ‘write_message’
> 386 | if((retval=
> write_message(context,,))){
> | ^
> auth/krb5_auth.c: In function ‘client_krb5_auth’:
> auth/krb5_auth.c:642:17: warning: ‘krb5_get_in_tkt_with_keytab’ is deprecated
> [-Wdeprecated-declarations]
> 642 | if((retval = krb5_get_in_tkt_with_keytab(context,
> options, addrs,
> | ^~
> In file included from /usr/include/krb5.h:8,
> from auth/krb5_auth.c:34:
> /usr/include/krb5/krb5.h:5146:1: note: declared here
> 5146 | krb5_get_in_tkt_with_keytab(krb5_context context, krb5_flags options,
> | ^~~
> common/lpq.c: In function ‘Term_clear’:
> common/lpq.c:472:17: warning: ignoring return value of ‘setuid’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 472 | setuid( OriginalRUID );
> | ^~
> gcc -DHAVE_CONFIG_H -I. -I.. -I./include "-DLOCALEDIR=\"/usr/share/locale\""
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o lprm.o `test -f 'common/lprm.c' || echo './'`common/lprm.c
> common/linelist.c: In function ‘Build_printcap_info’:
> common/linelist.c:1552:65: warning: ‘%s’ directive argument is null
> [-Wformat-overflow=]
> 1552 | DEBUG4("Build_printcap_info: old keyid '%s',
> new '%s'",
> | ^~
> common/linelist.c:1552:65: warning: ‘%s’ directive argument is null
> [-Wformat-overflow=]
> gcc -DHAVE_CONFIG_H -I. -I.. -I./include "-DLOCALEDIR=\"/usr/share/locale\""
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=form
Bug#1032342: marked as done ([INTL:ro] Romanian debconf templates translation of lprng)
Your message dated Sat, 16 Mar 2024 18:20:18 + with message-id and subject line Bug#1032342: fixed in lprng 3.8.B-8 has caused the Debian Bug report #1032342, regarding [INTL:ro] Romanian debconf templates translation of lprng 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.) -- 1032342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lprng Severity: wishlist Tags: l10n, patch Dear Maintainer, Please find attached the Romanian translation of the lprng file. Thanks, Remus-Gabriel lprng_debconf_ro.po Description: Binary data --- End Message --- --- Begin Message --- Source: lprng Source-Version: 3.8.B-8 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of lprng, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1032...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated lprng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Mar 2024 10:03:02 +0100 Source: lprng Architecture: source Version: 3.8.B-8 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Thorsten Alteholz Closes: 1032342 1066523 Changes: lprng (3.8.B-8) unstable; urgency=medium . * add implicit.patch (Closes: #1066523) * debian/watch: update to version 4 (probably "upstream" has problems anyway) * add ro.po (Closes: #1032342) Checksums-Sha1: a71087f10531591da36576df065831fb182cecf6 2120 lprng_3.8.B-8.dsc fef9d61a38ab297afb8b8586b359952dcff3abd6 860737 lprng_3.8.B.orig.tar.gz c5197595ea955d5ed341448ec58ab156735ff8d2 34128 lprng_3.8.B-8.debian.tar.xz 76092b6d165e9f2a9272530a4549064669d78e4d 7219 lprng_3.8.B-8_amd64.buildinfo Checksums-Sha256: 9133797bddbcead2f8c0942f30d84ecf7160916d3b8b71e8930cbf1f42d3 2120 lprng_3.8.B-8.dsc 541346a4bccd45acdeff1a8d09e80cc6a8bd22f9088739628ba787924a1806d1 860737 lprng_3.8.B.orig.tar.gz 4b602ca0eebe1b8ff6d33fa83ba8a4bea93ef0a1a20806efac2f278ee4341683 34128 lprng_3.8.B-8.debian.tar.xz fbe7d586c180f14265c33ac5fa38256c1d95f4698a6777817a44661fd7849dff 7219 lprng_3.8.B-8_amd64.buildinfo Files: 6193c4d17dff90141f2921878519fbd7 2120 net optional lprng_3.8.B-8.dsc 74c384b262c490dee31d7e2fa28ecf1d 860737 net optional lprng_3.8.B.orig.tar.gz 05be7fe0f5d9f917ab10d38d546a6050 34128 net optional lprng_3.8.B-8.debian.tar.xz 706df00aef6e497b2892532f6df1ec0b 7219 net optional lprng_3.8.B-8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmX13X9fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYRxD+D/90gwFTMK4D2UsnE1e/ZmHx0/bUlqFP spF48IFfdBvZ0U8jfVdxfzUgoxUtwP0XtPyVbtkeFrCNRBNv2x6nzSivJ1nEf+AN 7/YV6Rq7LZnuQOZynJe/myMEn3T3zazhk49GyPoeLmBYUPBgQk3QzplUHRKcUbMX o+DMR+ekIbW5NygfLNz9czxyn5ckfN1uVsdCPIzqxi0EGtS5RJ+EhO4gcexh3maV SvhOxq67IWjyl7jJIhSZDVAntAIdFi0DaNYvZ3WdT5IfsMGAGrJk1wRzogDlYE+Z aRq99XylRJayUAKmmx/eV2yhQfSbyHjIrKENTJr0AL55G70nQZ1JELDGyz0XP/S5 XvmKbGpcrSP28Entp2LabYG8eXAGm40s17+4rjqT0xg0VfE6ErKp9gdAzBC5sqZO GhohMtBDIrSlDEnDuFSgshzcG8T7wiXQiUXfwkuBhUqnrjCnMCqSAoFQV7W5OSm8 8uASx4IBYMpi2CGM448yFMwaPXjeuobQduvoh7aHB4vXblMKqrC++zUXGy0U4+SU eMxPErJhnZc6YJjl0lSJo0pkMH4UYpjb3+T+AIw0JnX5456UBu/JgU4NGwFdk0cK XccVkdkQQUv86vngNR5caL7c0UKToteR0ecNMMpFHIgF6A7qDuANJg3uXW0xbYUF FZsoqJbS01jsKg== =QN0j -END PGP SIGNATURE- pgpW4n71Q_9VZ.pgp Description: PGP signature --- End Message ---
Bug#1066376: marked as done (cjet: FTBFS: main.c:90:7: error: implicit declaration of function ‘strcpy’ [-Werror=implicit-function-declaration])
Your message dated Thu, 14 Mar 2024 19:04:37 + with message-id and subject line Bug#1066376: fixed in cjet 0.8.9-11 has caused the Debian Bug report #1066376, regarding cjet: FTBFS: main.c:90:7: error: implicit declaration of function ‘strcpy’ [-Werror=implicit-function-declaration] 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.) -- 1066376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cjet Version: 0.8.9-10 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o page.o page.c > main.c: In function ‘parse_args’: > main.c:90:7: error: implicit declaration of function ‘strcpy’ > [-Werror=implicit-function-declaration] >90 | strcpy(prog_name,"CJet"); > | ^~ > main.c:28:1: note: include ‘’ or provide a declaration of ‘strcpy’ >27 | #include "cjet.h" > +++ |+#include >28 | > main.c:90:7: warning: incompatible implicit declaration of built-in function > ‘strcpy’ [-Wbuiltin-declaration-mismatch] >90 | strcpy(prog_name,"CJet"); > | ^~ > main.c:90:7: note: include ‘’ or provide a declaration of ‘strcpy’ > cc1: some warnings being treated as errors > make[1]: *** [: main.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/cjet_0.8.9-10_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: cjet Source-Version: 0.8.9-11 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of cjet, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated cjet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 13 Mar 2024 20:04:01 +0200 Source: cjet Architecture: source Version: 0.8.9-11 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Thorsten Alteholz Closes: 1066376 Changes: cjet (0.8.9-11) unstable; urgency=medium . * add implicit.patch (Closes: #1066376) * debian/control: bump standard to 4.6.2 (no changes) * debian/control: set Rules-Requires-Root: no Checksums-Sha1: 7dc875d8b6781497107cba65779d2d9cadf22853 2098 cjet_0.8.9-11.dsc b15bf946a66365061f7c8e9508141033a152a1eb 50427 cjet_0.8.9.orig.tar.gz b4833b96dff6eb64be9412318c898038e052ad1b 5000 cjet_0.8.9-11.debian.tar.xz de743fabb02dbf653995982c41d282b3d9ce7964 6662 cjet_0.8.9-11_amd64.buildinfo Checksums-Sha256: 7475e787363e6ce59d54f527d3ce70ed99150133175efbbc79a06fff492bc168 2098 cjet_0.8.9-11.dsc c99e833eb7083bc7861166ef97830306605e281f251f85bb63b9496300625f87 50427 cjet_0.8.9.o
Bug#731140: marked as done (ghostscript: on PDF files with embedded fonts, ps2pdf changes the way fonts are rendered)
Your message dated Thu, 07 Mar 2024 21:37:41 -0600 with message-id <2521310.irdbgypaU6@riemann> and subject line Re: Bug#731140: ghostscript: on PDF files with embedded fonts, ps2pdf changes the way fonts are rendered has caused the Debian Bug report #731140, regarding ghostscript: on PDF files with embedded fonts, ps2pdf changes the way fonts are rendered 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.) -- 731140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.05~dfsg-8 Severity: normal ps2pdf should not change the embedded fonts except by optimizing them (e.g. compressing them), but a simple test shows that it changes the way fonts are rendered. I've attached 3 files. font1.pdf is the original file (generated by pdflatex). font2.pdf is the file obtained with "ps2pdf font1.pdf font2.pdf". font.png shows the text of font1.pdf (left) and font2.pdf (right), as obtained with xpdf. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ghostscript depends on: ii debconf [debconf-2.0] 1.5.52 ii gsfonts1:8.11+urwcyr1.0.7~pre44-4.2 ii libc6 2.17-97 ii libgs9 9.05~dfsg-8 ghostscript recommends no packages. Versions of packages ghostscript suggests: ii cups-filters [ghostscript-cups] 1.0.41-2 ii ghostscript-x9.05~dfsg-8 pn hpijs -- no debconf information font1.pdf Description: Adobe PDF document font2.pdf Description: Adobe PDF document --- End Message --- --- Begin Message --- On Thursday, March 7, 2024 8:18:21 A.M. CST Vincent Lefevre wrote: > On 2024-02-28 23:04:41 -0600, Steven Robbins wrote: > > On Mon, 2 Dec 2013 13:54:19 +0100 Vincent Lefevre wrote: > > > font1.pdf is the original file (generated by pdflatex). > > > font2.pdf is the file obtained with "ps2pdf font1.pdf font2.pdf". > > > font.png shows the text of font1.pdf (left) and font2.pdf (right), > > > as obtained with xpdf. > > > > I have repeated the test with ghostscript 10.02.1 and I cannot see any > > difference (using xpdf, or using evince) between font1 and the output of > > ps2pdf. > > Well, with the font*.pdf files I had attached in my bug report, I can > no longer see any difference between font1.pdf and font2.pdf with xpdf > (or zathura). So I assume that this was actually a bug in xpdf (or > poppler), which did something wrong concerning font2.pdf. > > I've also compared the rendering of these attached files on a Debian 11 > machine with xpdf, and I cannot see any difference either. > > So I suppose that this bug can be closed. Thank you for verifying, Vincent! -Steve signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#612199: marked as done (gs-esp: Margins incorrect for ljet2p compatible printers)
Your message dated Sun, 03 Mar 2024 23:13:59 -0600 with message-id <2861881.mvXUDI8C0e@riemann> and subject line Re: [gs-esp] Moreinformation and clone has caused the Debian Bug report #612199, regarding gs-esp: Margins incorrect for ljet2p compatible printers 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.) -- 612199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gs-esp Version: 7.07.1-8 Severity: normal The margins are incorrect for my NEC SuperScript 1260, which uses the the ljet2p driver. Following the directions given when I print out /usr/share/gs-esp/*/lib/align.ps, I was able to modify /usr/share/gs-esp/*/lib/gs_init.ps with the following at the end of the file: << /Margins [-60 10] >> setpagedevice << /.HWMargins [15 5 6 2] >> setpagedevice gs-esp (and gs-gpl?) should include the capability to read /etc/gs/printer.ps to get the proper values so that when I upgrade I don't loose these settings. Note that doing this would probably close Bug#48975. If you include the following to the bottom of gs_init.ps: %% Replace 5 (/etc/gs/printer.ps) %% Add your customization %% to /etc/gs/printer.ps %% and not here. %% %% and then include a /etc/gs/printer.ps: %% Include customization for printer margins and whatnot %% here. To align your margins, print out %% /usr/lib/gs-esp/*/lib/align.ps and follow the directions. You %% may also find step 6 at %% http://www.linuxprinting.org/cups-doc.html helpful. I think the problem would be fixed in a way that is easy to upgrade. (Above is untested, though.) -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.6-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 Versions of packages gs-esp depends on: ii gs-common 0.3.6 Common files for different Ghostsc ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an ii libcupsimage2 1.1.20final+cvs20040330-4 Common UNIX Printing System(tm) - ii libcupsys2-gnu 1.1.20final+cvs20040330-4 Common UNIX Printing System(tm) - ii libgimpprint1 4.2.6-7 The Gimp-Print printer driver libr ii libglib2.0-0 2.4.2-1 The GLib library of C routines ii libjpeg62 6b-9 The Independent JPEG Group's JPEG ii libpaper1 1.1.14Library for handling paper charact ii libpng12-0 1.2.5.0-6 PNG library - runtime ii libstdc++5 1:3.3.4-2 The GNU Standard C++ Library v3 ii libtiff3g 3.5.7-2 Tag Image File Format library ii libx11-6 4.3.0.dfsg.1-5X Window System protocol client li ii libxext6 4.3.0.dfsg.1-5X Window System miscellaneous exte ii libxt6 4.3.0.dfsg.1-4X Toolkit Intrinsics ii xlibs 4.3.0.dfsg.1-4X Window System client libraries m ii zlib1g 1:1.2.1.1-3 compression library - runtime -- no debconf information --- End Message --- --- Begin Message --- On Sun, 6 Feb 2011 18:26:00 +0100 Bastien ROUCARIES wrote: > clone 260281 -1 -2 > reassing -1 ghostscript > retitle -1 "Add custom margin configuration file" > severity -1 wishlist > reassing -2 ghostscript > severity -2 minor > tags 260281 + moreinfo > tags -2 moreinfo > thanks > > I have opened a wishlist bug for the configuration file. Could you also > suplly moreinformation about the margin problem of the NEC > SuperScript 1260? Closing, as no further information received. -Steve signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: Re: ghostscript: Annotate debian/conrol for DEB_BUILD_PROFILES=stage1
Processing control commands: > tags -1 + moreinfo Bug #870679 [src:ghostscript] ghostscript: Annotate debian/conrol for DEB_BUILD_PROFILES=stage1 Ignoring request to alter tags of bug #870679 to the same tags previously set -- 870679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ghostscript: Annotate debian/conrol for DEB_BUILD_PROFILES=stage1
Processing control commands: > tags -1 + moreinfo Bug #870679 [src:ghostscript] ghostscript: Annotate debian/conrol for DEB_BUILD_PROFILES=stage1 Added tag(s) moreinfo. -- 870679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#748880: marked as done (ghostscript-doc: "Raw 'bit' devices" section missing in Devices.htm)
Your message dated Sun, 03 Mar 2024 22:57:45 -0600 with message-id <2855031.mvXUDI8C0e@riemann> and subject line Re: ghostscript-doc: "Raw 'bit' devices" section missing in Devices.htm has caused the Debian Bug report #748880, regarding ghostscript-doc: "Raw 'bit' devices" section missing in Devices.htm 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.) -- 748880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghostscript-doc Severity: minor Tags: upstream Dear Maintainer, when I wanted to learn more about the DEVICE=bit output driver, I was surprised to learn there is a pointer in the ToC of Devices.html, but the link is broken, that section is missing. This applies to all versions I've checked and exists also in the online documentation privided by upstream at http://www.ghostscript.com/doc/current/Devices.htm#bitraw Can you please complete that piece of information? Christoph -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.10.39 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash signature.asc Description: Digital signature --- End Message --- --- Begin Message --- On Wed, 21 May 2014 20:41:56 +0200 Christoph Biedl wrote: > Source: ghostscript-doc > Severity: minor > Tags: upstream > > Dear Maintainer, > > when I wanted to learn more about the DEVICE=bit output driver, I was > surprised to learn there is a pointer in the ToC of Devices.html, but > the link is broken, that section is missing. > > This applies to all versions I've checked and exists also in the > online documentation privided by upstream at > http://www.ghostscript.com/doc/current/Devices.htm#bitraw > > Can you please complete that piece of information? I'm not qualified to write the upstream documentation. Suggest you open a bug in the upstream bugzilla: https://bugs.ghostscript.com/ Regards, -Steve signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: tagging 992893
Processing commands for cont...@bugs.debian.org: > tags 992893 + pending Bug #992893 [ghostscript] ps2ascii: odd option handling Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 992893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 379901
Processing commands for cont...@bugs.debian.org: > tags 379901 + moreinfo Bug #379901 [src:ghostscript] gs-gpl: `ps2pdf' fails to embed URW++ fonts from `gsfonts' Ignoring request to alter tags of bug #379901 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 379901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 931701
Processing commands for cont...@bugs.debian.org: > tags 931701 + moreinfo Bug #931701 [ghostscript] Wrong letter spacing Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 931701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1065396
Processing commands for cont...@bugs.debian.org: > tags 1065396 + pending Bug #1065396 [ghostscript] ghostscript: Coordinate uploads for German man page transfer Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1065396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#721137: marked as done (ghostscript: ps2pdf produces bad pdf on x86_64 (unreadeable text))
Your message dated Sun, 03 Mar 2024 21:45:14 -0600
with message-id <4917057.31r3eYUQgx@riemann>
and subject line Re: Bug#721137: ghostscript: ps2pdf produces bad pdf on x86_64
(unreadeable text)
has caused the Debian Bug report #721137,
regarding ghostscript: ps2pdf produces bad pdf on x86_64 (unreadeable text)
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.)
--
721137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghostscript
Version: 9.05~dfsg-6.3
Severity: normal
Dear Maintainer,
Trying to produce a pdf file as usual (latex, dvi2ps then ps2pdf). Worked like
a charm on squeeze.
here my test postscript document (produced from latex then dvi2ps):
http://dgeo.perso.ec-m.fr/tp2A_scilab_N1.ps .
ps2pdf from a i386 install of wheezy works too (9.05~dfsg-6.3):
http://dgeo.perso.ec-m.fr/tp2A_scilab_N1.wheezy_i386.pdf
ps2pdf from a squeeze install used to work
ps2pdf from a freebsd amd64 workstation works as expected (ghostscript 9.06
there): http://dgeo.perso.ec-m.fr/tp2A_scilab_N1.freebsd_gs_9.06.pdf
for this document it can be worked around with pdflatex (good pdf output)
-- System Information:
Debian Release: 7.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ghostscript depends on:
ii debconf [debconf-2.0] 1.5.49
ii debianutils4.3.2
ii gsfonts1:8.11+urwcyr1.0.7~pre44-4.2
ii libc6 2.13-38
ii libgs9 9.05~dfsg-6.3
ghostscript recommends no packages.
Versions of packages ghostscript suggests:
ii ghostscript-cups 9.05~dfsg-6.3
ii ghostscript-x 9.05~dfsg-6.3
ii hpijs 3.12.6-3.1
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, 17 Sep 2013 16:57:20 +0200 (CEST) whoami...@free.fr wrote:
>
> Hello again,
>
> I took a few minutes to minimize my own example of unreadable pdf.
> I ended with a quite bare test.tex:
>
> \documentclass{article}
> \usepackage[T1]{fontenc}
> \begin{document}
> Bla Bla Bla
> \end{document}
>
> Please find attached this file, plus the corresponding test.ps
> obtained via "latex test && dvips test.dvi" and the test.pdf produced
> by "ps2pdf test.ps".
I repeated this test using Debian sid and xpdf no longer complains about the
bounding box. Therefore I am closing this on the assumption that the
postscript itself was buggy in some fashion. Presumably the new latex version
emits better conforming postscript?
I've attached the ps obtained from latex && dvips, along with the pdf from
ps2pdf.
The latex version run is:
pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023/Debian) (preloaded
format=latex 2024.2.24) 3 MAR 2024 21:39
Regards,
-Steve
>
> As previously, evince doesn't display correctly the text of this test.pdf:
> you only see a few (bottom?) black pixels for each letter. With xpdf the
display
> is ok, but with warnings about "Bad bounding box in Type 3 glyph".
>
> This definitively looks like a font issue, since without the
> "\usepackage[T1]{fontenc}" line the display is back to normal.
>
> Best regards,
> Pierre
>
=<331532228.401465631.1379429840586.JavaMail.root@zimbra19-
e3.priv.proxad.net>
test.ps
Description: PostScript document
test.pdf
Description: Adobe PDF document
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
Processed: tagging 942055
Processing commands for cont...@bugs.debian.org: > tags 942055 + moreinfo Bug #942055 [ghostscript] cups-filters: Fails to print on Brother HL-2035 (foomatic/kl1250) with ghostscript 9.27~dfsg-2+deb10u2 armel Ignoring request to alter tags of bug #942055 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 942055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1065089 to wnpp, reassign 1065090 to wnpp, notfound 1065069 in apt-move/4.2.27-6+b1 ...
/bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065108 1065109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065109 1065110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065110 1065129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065129 1065160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065160 1065162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065162 1065179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065179 1065182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065182 1065186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 612194
Processing commands for cont...@bugs.debian.org: > tags 612194 + moreinfo Bug #612194 [src:ghostscript] gs: Strange printouts with Nec P6 -- might be typo in necp2x.upp Ignoring request to alter tags of bug #612194 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 612194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063207: marked as done (pappl: NMU diff for 64-bit time_t transition)
Your message dated Thu, 29 Feb 2024 21:05:44 +
with message-id
and subject line Bug#1063207: fixed in pappl 1.3.1-2.1
has caused the Debian Bug report #1063207,
regarding pappl: NMU diff for 64-bit time_t transition
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.)
--
1063207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pappl
Version: 1.3.1-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
pappl as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for pappl
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.2.0-39-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru pappl-1.3.1/debian/changelog pappl-1.3.1/debian/changelog
--- pappl-1.3.1/debian/changelog2023-02-25 07:44:24.0 -0300
+++ pappl-1.3.1/debian/changelog2024-02-05 14:19:53.0 -0300
@@ -1,3 +1,10 @@
+pappl (1.3.1-2.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Lucas Kanashiro Mon, 05 Feb 2024 14:19:53 -0300
+
pappl (1.3.1-2) unstable; urgency=medium
* debian/control: add dependency on libavahi-client-dev
diff -Nru pappl-1.3.1/debian/control pappl-1.3.1/debian/control
--- pappl-1.3.1/debian/control 2023-02-25 07:44:24.0 -0300
+++ pappl-1.3.1/debian/control 2024-02-05 14:19:52.0 -0300
@@ -20,7 +20,10 @@
Homepage: https://www.msweet.org/pappl/
Rules-Requires-Root: no
-Package: libpappl1
+Package: libpappl1t64
+Provides: ${t64:Provides}
+Replaces: libpappl1
+Breaks: libpappl1 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Section: libs
@@ -43,7 +46,7 @@
libgnutls28-dev,
libjpeg-dev,
libpam0g-dev,
- libpappl1 (= ${binary:Version}),
+ libpappl1t64 (= ${binary:Version}),
libpng-dev,
libusb-1.0-0-dev,
zlib1g-dev,
diff -Nru pappl-1.3.1/debian/libpappl1.docs pappl-1.3.1/debian/libpappl1.docs
--- pappl-1.3.1/debian/libpappl1.docs 2023-02-25 07:44:24.0 -0300
+++ pappl-1.3.1/debian/libpappl1.docs 1969-12-31 21:00:00.0 -0300
@@ -1 +0,0 @@
-NOTICE
diff -Nru pappl-1.3.1/debian/libpappl1.install
pappl-1.3.1/debian/libpappl1.install
--- pappl-1.3.1/debian/libpappl1.install2023-02-25 07:44:24.0
-0300
+++ pappl-1.3.1/debian/libpappl1.install1969-12-31 21:00:00.0
-0300
@@ -1 +0,0 @@
-usr/lib/${DEB_HOST_MULTIARCH}/libpappl.so.1
diff -Nru pappl-1.3.1/debian/libpappl1.lintian-overrides
pappl-1.3.1/debian/libpappl1.lintian-overrides
--- pappl-1.3.1/debian/libpappl1.lintian-overrides 2023-02-25
07:44:24.0 -0300
+++ pappl-1.3.1/debian/libpappl1.lintian-overrides 1969-12-31
21:00:00.0
Bug#1061916: marked as done (cups: NMU diff for 64-bit time_t transition)
Your message dated Fri, 1 Mar 2024 08:33:42 +1300
with message-id
and subject line
has caused the Debian Bug report #1061916,
regarding cups: NMU diff for 64-bit time_t transition
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.)
--
1061916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cups
Version: 2.4.7-1
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
cups as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for cups
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-15-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru cups-2.4.7/debian/changelog cups-2.4.7/debian/changelog
--- cups-2.4.7/debian/changelog 2023-10-06 18:16:49.0 +
+++ cups-2.4.7/debian/changelog 2024-01-30 01:28:04.0 +
@@ -1,3 +1,10 @@
+cups (2.4.7-1.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle Tue, 30 Jan 2024 01:28:04 +
+
cups (2.4.7-1) unstable; urgency=medium
* Update to new upstream version 2.4.7.
diff -Nru cups-2.4.7/debian/control cups-2.4.7/debian/control
--- cups-2.4.7/debian/control 2023-10-06 18:16:49.0 +
+++ cups-2.4.7/debian/control 2024-01-30 01:28:04.0 +
@@ -36,7 +36,10 @@
Homepage: https://github.com/OpenPrinting/cups/
Rules-Requires-Root: no
-Package: libcups2
+Package: libcups2t64
+Provides: ${t64:Provides}
+Replaces: libcups2
+Breaks: libcups2 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Section: libs
@@ -306,7 +309,10 @@
with cups from different programming languages (Perl, Java, and
PHP).
-Package: libcupsimage2
+Package: libcupsimage2t64
+Provides: ${t64:Provides}
+Replaces: libcupsimage2
+Breaks: libcupsimage2 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Section: libs
diff -Nru cups-2.4.7/debian/libcups2.examples
cups-2.4.7/debian/libcups2.examples
--- cups-2.4.7/debian/libcups2.examples 2023-10-06 18:13:16.0 +
+++ cups-2.4.7/debian/libcups2.examples 1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-debian/client.conf
diff -Nru cups-2.4.7/debian/libcups2.install cups-2.4.7/debian/libcups2.install
--- cups-2.4.7/debian/libcups2.install 2023-10-06 18:13:16.0 +
+++ cups-2.4.7/debian/libcups2.install 1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libcups.so.*
diff -Nru cups-2.4.7/debian/libcups2.README.Debian
cups-2.4.7/debian/libcups2.README.Debian
--- cups-2.4.7/debian/libcups2.README.Debian2023-10-06 18:13:16.0
+
+++ cups-2.4.7/debian/libcups2.README.Debian1970-01-01 00:00:00.0
+
@@ -1,198 +0,0 @@
-Conventions used in t
Processed: tagging 1063563
Processing commands for cont...@bugs.debian.org: > tags 1063563 + help confirmed Bug #1063563 [ghostscript] ghostscript: ps2epsi fails with Error: /undefined in /finddevice Added tag(s) help and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1063563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ghostscript: on PDF files with embedded fonts, ps2pdf changes the way fonts are rendered
Processing control commands: > tags -1 +moreinfo Bug #731140 [ghostscript] ghostscript: on PDF files with embedded fonts, ps2pdf changes the way fonts are rendered Ignoring request to alter tags of bug #731140 to the same tags previously set -- 731140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 612194
Processing commands for cont...@bugs.debian.org: > tags 612194 + moreinfo Bug #612194 [src:ghostscript] gs: Strange printouts with Nec P6 -- might be typo in necp2x.upp Ignoring request to alter tags of bug #612194 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 612194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ghostscript: on PDF files with embedded fonts, ps2pdf changes the way fonts are rendered
Processing control commands: > tags -1 +moreinfo Bug #731140 [ghostscript] ghostscript: on PDF files with embedded fonts, ps2pdf changes the way fonts are rendered Added tag(s) moreinfo. -- 731140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061904: marked as done (cpdb-libs: NMU diff for 64-bit time_t transition)
Your message dated Wed, 28 Feb 2024 21:09:45 +
with message-id
and subject line Bug#1061904: fixed in cpdb-libs 2.0~b5-1.2
has caused the Debian Bug report #1061904,
regarding cpdb-libs: NMU diff for 64-bit time_t transition
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.)
--
1061904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpdb-libs
Version: 1.2.0-3
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
cpdb-libs as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for cpdb-libs
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-15-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru cpdb-libs-1.2.0/debian/changelog cpdb-libs-1.2.0/debian/changelog
--- cpdb-libs-1.2.0/debian/changelog2023-06-27 20:03:02.0 +
+++ cpdb-libs-1.2.0/debian/changelog2024-01-30 01:24:37.0 +
@@ -1,3 +1,10 @@
+cpdb-libs (1.2.0-3.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle Tue, 30 Jan 2024 01:24:37 +
+
cpdb-libs (1.2.0-3) unstable; urgency=medium
* CVE-2023-34095 (Closes: #1038253)
diff -Nru cpdb-libs-1.2.0/debian/control cpdb-libs-1.2.0/debian/control
--- cpdb-libs-1.2.0/debian/control 2023-06-27 20:03:02.0 +
+++ cpdb-libs-1.2.0/debian/control 2024-01-30 01:24:37.0 +
@@ -17,7 +17,10 @@
Vcs-Browser: https://salsa.debian.org/printing-team/cpdb-libs
Vcs-Git: https://salsa.debian.org/printing-team/cpdb-libs.git
-Package: libcpdb-libs-common1
+Package: libcpdb-libs-common1t64
+Provides: ${t64:Provides}
+Replaces: libcpdb-libs-common1
+Breaks: libcpdb-libs-common1 (<< ${source:Version})
Section: libs
Architecture: any
Pre-Depends: ${misc:Pre-Depends}
@@ -41,7 +44,10 @@
This package contains the library which provides the functions needed
by both the frontends and the backends.
-Package: libcpdb-libs-frontend1
+Package: libcpdb-libs-frontend1t64
+Provides: ${t64:Provides}
+Replaces: libcpdb-libs-frontend1
+Breaks: libcpdb-libs-frontend1 (<< ${source:Version})
Section: libs
Architecture: any
Pre-Depends: ${misc:Pre-Depends}
diff -Nru cpdb-libs-1.2.0/debian/libcpdb-libs-common1.install
cpdb-libs-1.2.0/debian/libcpdb-libs-common1.install
--- cpdb-libs-1.2.0/debian/libcpdb-libs-common1.install 2023-06-27
20:03:02.0 +
+++ cpdb-libs-1.2.0/debian/libcpdb-libs-common1.install 1970-01-01
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/*ommon.so.*
diff -Nru cpdb-libs-1.2.0/debian/libcpdb-libs-common1.symbols
cpdb-libs-1.2.0/debian/libcpdb-libs-common1.symbols
--- cpdb-libs-1.2.0/debian/libcpdb-libs-common1.symbols 2023-06-27
20:03:02.000
Bug#1061915: marked as done (cups-filters: NMU diff for 64-bit time_t transition)
Your message dated Tue, 27 Feb 2024 23:35:05 +
with message-id
and subject line Bug#1061915: fixed in cups-filters 1.28.17-3.1
has caused the Debian Bug report #1061915,
regarding cups-filters: NMU diff for 64-bit time_t transition
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.)
--
1061915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cups-filters
Version: 1.28.17-3
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
cups-filters as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for cups-filters
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-15-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru cups-filters-1.28.17/debian/changelog
cups-filters-1.28.17/debian/changelog
--- cups-filters-1.28.17/debian/changelog 2023-05-19 16:25:20.0
+
+++ cups-filters-1.28.17/debian/changelog 2024-01-30 01:27:40.0
+
@@ -1,3 +1,10 @@
+cups-filters (1.28.17-3.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle Tue, 30 Jan 2024 01:27:40 +
+
cups-filters (1.28.17-3) unstable; urgency=medium
* CVE-2023-24805
diff -Nru cups-filters-1.28.17/debian/control
cups-filters-1.28.17/debian/control
--- cups-filters-1.28.17/debian/control 2023-05-19 08:48:08.0 +
+++ cups-filters-1.28.17/debian/control 2024-01-30 01:27:40.0 +
@@ -40,7 +40,10 @@
Homepage: http://www.openprinting.org/
Rules-Requires-Root: no
-Package: libcupsfilters1
+Package: libcupsfilters1t64
+Provides: ${t64:Provides}
+Replaces: libcupsfilters1
+Breaks: libcupsfilters1 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Section: libs
@@ -179,7 +182,10 @@
This package contains the header files to develop applications using
libfontembed.
-Package: libfontembed1
+Package: libfontembed1t64
+Provides: ${t64:Provides}
+Replaces: libfontembed1
+Breaks: libfontembed1 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Section: libs
diff -Nru cups-filters-1.28.17/debian/libcupsfilters1.install
cups-filters-1.28.17/debian/libcupsfilters1.install
--- cups-filters-1.28.17/debian/libcupsfilters1.install 2023-05-19
08:48:08.0 +
+++ cups-filters-1.28.17/debian/libcupsfilters1.install 1970-01-01
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libcupsfilters.so.*
diff -Nru cups-filters-1.28.17/debian/libcupsfilters1.symbols
cups-filters-1.28.17/debian/libcupsfilters1.symbols
--- cups-filters-1.28.17/debian/libcupsfilters1.symbols 2023-05-19
08:48:08.0 +
+++ cups-filters-1.28.17/debian/libcupsfilters1.symbols 1970-01-01
00:00:00.0 +
@@
Processed: tagging 503191
Processing commands for cont...@bugs.debian.org: > tags 503191 + moreinfo Bug #503191 [ghostscript] pdfwrite: AutoRotatePages=/None ignored, PDF rotate Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 503191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 942055
Processing commands for cont...@bugs.debian.org: > tags 942055 + moreinfo Bug #942055 [ghostscript] cups-filters: Fails to print on Brother HL-2035 (foomatic/kl1250) with ghostscript 9.27~dfsg-2+deb10u2 armel Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 942055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#683641: marked as done (gs: -dDuplex ignored for pswrite/psmono/pdfwrite output devices)
Your message dated Sun, 25 Feb 2024 14:20:59 -0600
with message-id <46192170.fMDQidcC6G@riemann>
and subject line Re: gs: -dDuplex ignored for pswrite/psmono/pdfwrite output
devices
has caused the Debian Bug report #683641,
regarding gs: -dDuplex ignored for pswrite/psmono/pdfwrite output devices
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.)
--
683641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gs
Version: 8.62.dfsg.1-3.2lenny5
Severity: normal
Hello,
gs ignores -dDuplex option when using
pswrite/psmono/pdfwrite output drivers, i.e. it
doesn't insert /Duplex true pagedevice entry:
> xrgtn@ux230p:/tmp$ cat hello.ps world.ps
> %!PS
> /Courier 30 selectfont
> 100 400 moveto
> (|-|3110, ) show
> showpage
> %!PS
> /Courier 30 selectfont
> 100 400 moveto
> (\\/\\/0R1d!) show
> showpage
> xrgtn@ux230p:/tmp$ gs -dNOPAUSE -dBATCH -sDEVICE=pswrite -dDuplex
> -sOutputFile=o.ps hello.ps world.ps
> GPL Ghostscript 8.71 (2010-02-10)
> Copyright (C) 2010 Artifex Software, Inc. All rights reserved.
> This software comes with NO WARRANTY: see the file PUBLIC for details.
> Loading NimbusMonL-Regu font from
> /usr/share/fonts/type1/gsfonts/n022003l.pfb... 2528792 1197912 1920356 624719
> 1 done.
> xrgtn@ux230p:/tmp$ grep -i duplex o.ps
> xrgtn@ux230p:/tmp$
So when I need /Duplex, I'm forced to generate
.pdf instead of .ps and then convert .pdf back
to .ps via pstopdf (libpoppler):
> xrgtn@ux230p:/tmp$ gs -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=o.pdf
> -q hello.ps world.ps
> xrgtn@ux230p:/tmp$ pdftops -duplex o.pdf o.ps
> xrgtn@ux230p:/tmp$ grep -i duplex o.ps
> { /Duplex true def } if
> xrgtn@ux230p:/tmp$
-- System Information:
Debian Release: 6.0.5
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'oldstable'),
(500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gs depends on:
ii ghostscript 8.71~dfsg2-9 The GPL Ghostscript PostScript/PDF
ii ghostscript-x 8.71~dfsg2-9 The GPL Ghostscript PostScript/PDF
gs recommends no packages.
gs suggests no packages.
-- no debconf information
--
With best regards,
xrgtn
--- End Message ---
--- Begin Message ---
On Thu, 2 Aug 2012 16:09:43 +0300 Alexander Gattin wrote:
> Package: gs
> Version: 8.62.dfsg.1-3.2lenny5
> Severity: normal
>
>
> Hello,
>
> gs ignores -dDuplex option when using
> pswrite/psmono/pdfwrite output drivers, i.e. it
> doesn't insert /Duplex true pagedevice entry:
I believe that is by design, as the docs [1] only cover -dDuplex for IJS and
Windows output devices.
[1] https://ghostscript.com/docs/9.54.0/Devices.htm
> > xrgtn@ux230p:/tmp$ cat hello.ps world.ps
> > %!PS
> > /Courier 30 selectfont
> > 100 400 moveto
> > (|-|3110, ) show
> > showpage
> > %!PS
> > /Courier 30 selectfont
> > 100 400 moveto
> > (\\/\\/0R1d!) show
> > showpage
> > xrgtn@ux230p:/tmp$ gs -dNOPAUSE -dBATCH -sDEVICE=pswrite -dDuplex -
sOutputFile=o.ps hello.ps world.ps
> > GPL Ghostscript 8.71 (2010-02-10)
> > Copyright (C) 2010 Artifex Software, Inc. All rights reserved.
> > This software comes with NO WARRANTY: see the file PUBLIC for details.
> > Loading NimbusMonL-Regu font from /usr/share/fonts/type1/gsfonts/
n022003l.pfb... 2528792 1197912 1920356 624719 1 done.
> > xrgtn@ux230p:/tmp$ grep -i duplex o.ps
> > xrgtn@ux230p:/tmp$
>
> So when I need /Duplex, I'm forced to generate
> .pdf instead of .ps and then convert .pdf back
> to .ps via pstopdf (libpoppler):
> > xrgtn@ux230p:/tmp$ gs -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -
sOutputFile=o.pdf -q hello.ps world.ps
> > xrgtn@ux230p:/tmp$ pdftops -duplex o.pdf o.ps
> > xrgtn@ux230p:/tmp$ grep -i duplex o.ps
> > { /Duplex true def } if
> > xrgtn@ux230p:/tmp$
>
> -- System Information:
> Debian Release: 6.0.5
> APT prefers stable
> APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'oldstable'),
(500, 'testing')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell
Bug#582846: marked as done (ghostscript: example CJK postscript files cause segfault when gs quit)
Your message dated Sat, 24 Feb 2024 20:55:55 -0600 with message-id <3279508.aeNJFYEL58@riemann> and subject line Re: ghostscript: example CJK postscript files cause segfault when gs quit has caused the Debian Bug report #582846, regarding ghostscript: example CJK postscript files cause segfault when gs quit 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.) -- 582846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 8.71~dfsg2-3 Severity: normal When quitting ghostscript, after some example CJK postscript files processed, it segfault. /usr/share/doc/ghostscript/examples/cjk: all_ac1.ps.gz all_ag1.ps.gz all_aj1.ps.gz all_aj2.ps.gz all_ak1.ps.gz article9.ps gscjk_ac.ps gscjk_ag.ps gscjk_aj.ps gscjk_ak.ps iso2022.ps.gz iso2022v.ps.gz iso2022.ps.gz and iso2022.ps.gz make gs segfault when quit. Others are OK. % zcat /usr/share/doc/ghostscript/examples/cjk/iso2022.ps.gz > iso2022.ps % gs iso2022.ps GPL Ghostscript 8.71 (2010-02-10) Copyright (C) 2010 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. This is a script to test CJK fonts such as CID-keyed fonts. If you have not done CID-keyed fonts installation and definitions at /Resource/CMap and CIDFnmap or /Resource/CIDFont of ghostscript, then this script can't work correctly. For details, please see README at http://www.gyve.org/gs-cjk/supplement. If you throw this script into a printer, it requires PostScript 3 printer and CID-keyed fonts specified in this script. Loading NimbusMonL-Regu font from /usr/share/fonts/type1/gsfonts/n022003l.pfb... 3909104 2177679 6773592 5444181 1 done. Loading NimbusMonL-Bold font from /usr/share/fonts/type1/gsfonts/n022004l.pfb... 3952096 2314304 6773592 5460478 1 done. Loading a TT font from /usr/share/fonts/truetype/ttf-japanese-mincho.ttf to emulate a CID font Japanese-Mincho-Regular ... Done. Loading a TT font from /usr/share/fonts/truetype/arphic/uming.ttc to emulate a CID font BousungEG-Light-GB ... Done. Loading a TT font from /usr/share/fonts/truetype/unfonts/UnBatang.ttf to emulate a CID font UnBatang-Regular ... Done. Can't find (or can't open) font file /usr/share/ghostscript/8.71/Resource/Font/HeiseiMin-W3H-Hojo-H. Can't find (or can't open) font file HeiseiMin-W3H-Hojo-H. Querying operating system for font files... Can't find (or can't open) font file /usr/share/ghostscript/8.71/Resource/Font/HeiseiMin-W3H-Hojo-H. Can't find (or can't open) font file HeiseiMin-W3H-Hojo-H. Didn't find this font on the system! Substituting font Courier for HeiseiMin-W3H-Hojo-H. Loading a TT font from /usr/share/fonts/truetype/arphic/uming.ttc to emulate a CID font ShanHeiSun-Light ... Done. Loading a TT font from /usr/share/fonts/truetype/ttf-japanese-gothic.ttf to emulate a CID font Japanese-Gothic-Regular ... Done. Loading a TT font from /usr/share/fonts/truetype/unfonts/UnDotum.ttf to emulate a CID font UnDotum-Regular ... Done. Can't find (or can't open) font file /usr/share/ghostscript/8.71/Resource/Font/HeiseiKakuGo-W5H-Hojo-H. Can't find (or can't open) font file HeiseiKakuGo-W5H-Hojo-H. Didn't find this font on the system! Substituting font Courier for HeiseiKakuGo-W5H-Hojo-H. Loading a TT font from /usr/share/fonts/truetype/arphic/ukai.ttc to emulate a CID font ZenKai-Medium ... Done. Loading NimbusSanL-Regu font from /usr/share/fonts/type1/gsfonts/n019003l.pfb... 18364328 16950211 7472224 5505865 1 done. Loading NimbusSanL-Bold font from /usr/share/fonts/type1/gsfonts/n019004l.pfb... 18486056 17067725 8252544 6524718 1 done. >>showpage, press to continue<< GS>quit zsh: segmentation fault (core dumped) gs iso2022.ps % I want to get backtrace, so I run not stripped binary. % LD_LIBRARY_PATH=./ghostscript-8.71\~dfsg2/sobin ./ghostscript-8.71\~dfsg2/bin/gs iso2022.ps : zsh: segmentation fault (core dumped) LD_LIBRARY_PATH=./ghostscript-8.71\~dfsg2/sobin iso2022.ps % % gdb ./ghostscript-8.71\~dfsg2/bin/gs core : Core was generated by `./ghostscript-8.71~dfsg2/bin/gs iso2022.ps'. Program terminated with signal 11, Segmentation fault. #0 0x007064ed in i_free_object (mem=0x2a0c848, ptr=0x3132488, cname=0x7a04c0 "subst_CID_on_WMode_finalize") at ./base/gsalloc.c:787 warning: Source file is more recent than executable.
Processed: tagging 1064187, tagging 1064193, tagging 1064139, tagging 1064094, found 1064094 in 1.4-1 ...
Processing commands for cont...@bugs.debian.org:
> tags 1064187 + sid trixie experimental
Bug #1064187 [src:luasocket] lua-socket: identified for time_t transition but
no ABI in shlibs
Added tag(s) experimental, trixie, and sid.
> tags 1064193 + sid trixie experimental
Bug #1064193 [src:lua-cqueues] lua-cqueues: identified for time_t transition
but no ABI in shlibs
Added tag(s) sid, experimental, and trixie.
> tags 1064139 + sid trixie
Bug #1064139 [src:ogre-1.12] ogre-1.12: FTBFS: error: ‘BuildFontAtlas’ is not a
member of ‘ImGuiFreeType’
Added tag(s) sid and trixie.
> tags 1064094 + sid trixie
Bug #1064094 [src:setuptools-scm-git-archive] setuptools-scm-git-archive
shouldn't be in trixie
Added tag(s) trixie and sid.
> found 1064094 1.4-1
Bug #1064094 [src:setuptools-scm-git-archive] setuptools-scm-git-archive
shouldn't be in trixie
Marked as found in versions setuptools-scm-git-archive/1.4-1.
> tags 1064088 + sid trixie
Bug #1064088 [src:gutenprint] gutenprint: FTBFS in unstable
Added tag(s) trixie and sid.
> tags 1064037 + sid trixie
Bug #1064037 {Done: Georges Khaznadar } [src:xhtml2pdf]
xhtml2pdf: the new version of python-reportlab breaks xhtml2pdf/context.py
Added tag(s) trixie and sid.
> tags 1042031 + experimental
Bug #1042031 [src:jruby-utils-clojure] jruby-utils-clojure: FTBFS: E: Build
killed with signal TERM after 150 minutes of inactivity
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1042031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042031
1064037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064037
1064088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064088
1064094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064094
1064139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064139
1064187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064187
1064193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1062554
Processing commands for cont...@bugs.debian.org: > close 1062554 Bug #1062554 [cups-browsed] cups-browsed is not detecting any network printers Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1062554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1061866, tagging 1061872, tagging 1061873, tagging 1061874, tagging 1061875, tagging 1061878 ...
Processing commands for cont...@bugs.debian.org:
> tags 1061866 + sid trixie
Bug #1061866 [src:adns] adns: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061872 + sid trixie
Bug #1061872 [src:adolc] adolc: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061873 + sid trixie
Bug #1061873 [src:afflib] afflib: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061874 + sid trixie
Bug #1061874 [src:colpack] colpack: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061875 + sid trixie
Bug #1061875 [src:afterstep] afterstep: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061878 + sid trixie
Bug #1061878 [src:agg] agg: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061881 + sid trixie
Bug #1061881 [src:akonadi-search] akonadi-search: NMU diff for 64-bit time_t
transition
Added tag(s) trixie and sid.
> tags 1061883 + sid trixie
Bug #1061883 [src:alberta] alberta: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061889 + sid trixie
Bug #1061889 [src:angelscript] angelscript: NMU diff for 64-bit time_t
transition
Added tag(s) sid and trixie.
> tags 1061890 + sid trixie
Bug #1061890 [src:anthy] anthy: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061891 + sid trixie
Bug #1061891 [src:apbs] apbs: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061892 + sid trixie
Bug #1061892 [src:apophenia] apophenia: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061893 + sid trixie
Bug #1061893 [src:apr-util] apr-util: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061894 + sid trixie
Bug #1061894 [src:apr] apr: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061897 + sid trixie
Bug #1061897 [src:aribb24] aribb24: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061900 + sid trixie
Bug #1061900 [src:comedilib] comedilib: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061901 + sid trixie
Bug #1061901 [src:compiz] compiz: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061903 + sid trixie
Bug #1061903 [src:coolkey] coolkey: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061905 + sid trixie
Bug #1061905 [src:cpp-hocon] cpp-hocon: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061908 + sid trixie
Bug #1061908 [src:cppdb] cppdb: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061909 + sid trixie
Bug #1061909 [src:croaring] croaring: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061911 + sid trixie
Bug #1061911 [src:csmith] csmith: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061913 + sid trixie
Bug #1061913 [src:ctpl] ctpl: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061914 + sid trixie
Bug #1061914 [src:cuneiform] cuneiform: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061915 + sid trixie
Bug #1061915 [src:cups-filters] cups-filters: NMU diff for 64-bit time_t
transition
Added tag(s) sid and trixie.
> tags 1061921 + sid trixie
Bug #1061921 [src:asl] asl: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061922 + sid trixie
Bug #1061922 [src:astrometry.net] astrometry.net: NMU diff for 64-bit time_t
transition
Added tag(s) trixie and sid.
> tags 1061928 + sid trixie
Bug #1061928 [src:avro-c] avro-c: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061929 + sid trixie
Bug #1061929 [src:bamf] bamf: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061932 + sid trixie
Bug #1061932 [src:blitz++] blitz++: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061934 + sid trixie
Bug #1061934 [src:boinc] boinc: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061943 + sid trixie
Bug #1061943 [src:forge] forge: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061945 + sid trixie
Bug #1061945 [src:fpgatools] fpgatools: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061953 + sid trixie
Bug #1061953 [src:freewnn] freewnn: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061954 + sid trixie
Bug #1061954 [src:frog] frog: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061955 + sid trixie
Bug #1061955 [src:fsplib] fsplib: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061957 + sid trixie
Bug #1061957 [src:funtools] funtools: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061961 + sid trixie
Bug #1061961 {Done: Bas Couwenberg } [src:fyba] fyba: NMU
diff for 64-bit
Processed: Re: Bug#1061245: Acknowledgement (cups: install systemd units into /usr)
Processing control commands: > tags -1 + patch Bug #1061245 [src:cups] cups: install systemd units into /usr Added tag(s) patch. -- 1061245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992889: marked as done (/usr/sbin/update-gsfontmap: overly complicated)
Your message dated Sat, 20 Jan 2024 22:41:08 + with message-id and subject line Bug#992889: fixed in ghostscript 10.02.1~dfsg-3 has caused the Debian Bug report #992889, regarding /usr/sbin/update-gsfontmap: overly complicated 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.) -- 992889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.27~dfsg-2+deb10u4 Severity: minor File: /usr/sbin/update-gsfontmap Tags: patch Dear Maintainer, The current approach that update-gsfontmap takes is very complicated, to no apparent end, since all it achieves is concatenating all the files; please consider the attached patch, which applies to every version since 7e78b19759ab1e47a3636ffd5c922c536e6cad37 (November of 2018) Best, наб -- System Information: Debian Release: 10.10 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-debug'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-17-amd64 (SMP w/24 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ghostscript depends on: ii libc6 2.28-10 ii libgs9 9.27~dfsg-2+deb10u4 Versions of packages ghostscript recommends: ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.4 Versions of packages ghostscript suggests: ii ghostscript-x 9.27~dfsg-2+deb10u4 -- no debconf information diff --git a/debian/update-gsfontmap.orig b/debian/update-gsfontmap index 5367ff6..c105363 100644 --- a/debian/update-gsfontmap.orig +++ b/debian/update-gsfontmap @@ -8,15 +8,7 @@ FONTMAP=/var/lib/ghostscript/fonts/Fontmap CIDFDIR=/etc/ghostscript/cidfmap.d/ FONTMDIR=/etc/ghostscript/fontmap.d/ -rm -f "$CIDFMAP" "$FONTMAP" -touch "$CIDFMAP" "$FONTMAP" - -for i in "$CIDFDIR"/*.conf; do -cat "$i" >> "$CIDFMAP" -done 2>/dev/null - -for i in "$FONTMDIR"/*.conf; do -cat "$i" >> "$FONTMAP" -done 2>/dev/null +cat "$CIDFDIR"/*.conf > "$CIDFMAP" 2>/dev/null +cat "$FONTMDIR"/*.conf > "$FONTMAP" 2>/dev/null exit 0 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ghostscript Source-Version: 10.02.1~dfsg-3 Done: Steve M. Robbins We believe that the bug you reported is fixed in the latest version of ghostscript, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated ghostscript package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 20 Jan 2024 15:44:07 -0600 Source: ghostscript Architecture: source Version: 10.02.1~dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Steve M. Robbins Closes: 740959 782901 992889 1053377 Changes: ghostscript (10.02.1~dfsg-3) unstable; urgency=medium . [ наб ] * [ee3d1ac] Simplify /sbin/update-gsfontmap (Closes: #992889) . [ Steve Robbins ] * [ccc0e3c] Explicitly set font map files to be world readable. Closes: #740959. * [5fce3d3] Add suggestion for package texlive-binaries, needed to use dvipdf. Closes: #782901. * [9ab8028] ghostscript: add conflicts to ghostcript-x to allow removal of the obsolete transitional package. Closes: #1053377 Checksums-Sha1: d7583a3f735f07dbca4c938fb2e9b3062dcf667f 2796 ghostscript_10.02.1~dfsg-3.dsc 3848f95307726499c0d9bcf6ea8afd03001d6657 84268 ghostscript_10.02.1~dfsg-3.debian.tar.xz 90c5b5eb55c3e27d552945617cf47cb541c50a92 11274 ghostscript_10.02.1~dfsg-3_source.buildinfo Checksums-Sha256: 72b7456cfa3be3caea85d1da6e933099fa0220fb818d7
Bug#782901: marked as done (ghostscript: missing dependency on TeX)
Your message dated Sat, 20 Jan 2024 22:41:08 + with message-id and subject line Bug#782901: fixed in ghostscript 10.02.1~dfsg-3 has caused the Debian Bug report #782901, regarding ghostscript: missing dependency on TeX 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.) -- 782901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.06~dfsg-2 Severity: normal Dear Maintainer, Having DVI from "other sources" then TeX. I've tried to PDF it. This fails because DVIPDF complained, that DVIPS is missing which is a part of TeX package, while TeX wain't installed on my system when I've experienced that. Ghostscript, which owns DVIPDF does not depend on TeX ... and it should not. But may be depending the entire ghostscript package on TeX is not such a good idea. I would think, that DVIPDF linking ghostscript to TeX, should rather be moved to it's own package, depending on both. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ghostscript depends on: ii debconf [debconf-2.0] 1.5.56 ii gsfonts1:8.11+urwcyr1.0.7~pre44-4.2 ii libc6 2.19-18 ii libgs9 9.06~dfsg-2 ghostscript recommends no packages. Versions of packages ghostscript suggests: pn ghostscript-x -- no debconf information --- End Message --- --- Begin Message --- Source: ghostscript Source-Version: 10.02.1~dfsg-3 Done: Steve M. Robbins We believe that the bug you reported is fixed in the latest version of ghostscript, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 782...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated ghostscript package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 20 Jan 2024 15:44:07 -0600 Source: ghostscript Architecture: source Version: 10.02.1~dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Steve M. Robbins Closes: 740959 782901 992889 1053377 Changes: ghostscript (10.02.1~dfsg-3) unstable; urgency=medium . [ наб ] * [ee3d1ac] Simplify /sbin/update-gsfontmap (Closes: #992889) . [ Steve Robbins ] * [ccc0e3c] Explicitly set font map files to be world readable. Closes: #740959. * [5fce3d3] Add suggestion for package texlive-binaries, needed to use dvipdf. Closes: #782901. * [9ab8028] ghostscript: add conflicts to ghostcript-x to allow removal of the obsolete transitional package. Closes: #1053377 Checksums-Sha1: d7583a3f735f07dbca4c938fb2e9b3062dcf667f 2796 ghostscript_10.02.1~dfsg-3.dsc 3848f95307726499c0d9bcf6ea8afd03001d6657 84268 ghostscript_10.02.1~dfsg-3.debian.tar.xz 90c5b5eb55c3e27d552945617cf47cb541c50a92 11274 ghostscript_10.02.1~dfsg-3_source.buildinfo Checksums-Sha256: 72b7456cfa3be3caea85d1da6e933099fa0220fb818d744ca4b4abbf3b53094e 2796 ghostscript_10.02.1~dfsg-3.dsc 647f99e9798d0d2edb80d57cd0203bd363121311cbb7486490559792833d8f42 84268 ghostscript_10.02.1~dfsg-3.debian.tar.xz a784c5b2073b52aa21b0e3fd86ac8db44cb2667c418e2c996d80a0cb763bcedd 11274 ghostscript_10.02.1~dfsg-3_source.buildinfo Files: 309c5d78143fc16c48affa402567bda1 2796 text optional ghostscript_10.02.1~dfsg-3.dsc 9bb73130a477951b974de55cfb9646ad 84268 text optional ghostscript_10.02.1~dfsg-3.debian.tar.xz fefeb9480d6a28fe00f57e203f5c7e69 11274 text optional ghostscript_10.02.1~dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEy89k8fa3rclNjyokyeVeL63I9LkFAmWsPxYPHHNtckBkZWJp YW4ub3JnAAoJEMnlXi+tyPS5Lm4QAJW98420MHxd4y/agrcS85yaFWymrArBmKc7 uJwtgloufYcP10x2iJQuBMPAlUlpAnPEJFeCcGyxc92ojiLSua6qIJBxD/PSc7JG ZeO2IgmfSUnv8o7pQfxRRy1MWzR1sa+VR+bw9bjkaLHGA+JwM1DWykiWaiYPQaSj gvbZqwaQZR0hC7LJT00W+Wmm+peQz
Bug#740959: marked as done (/usr/sbin/update-gsfontmap: sets wrong file permissions)
Your message dated Sat, 20 Jan 2024 22:41:08 + with message-id and subject line Bug#740959: fixed in ghostscript 10.02.1~dfsg-3 has caused the Debian Bug report #740959, regarding /usr/sbin/update-gsfontmap: sets wrong file permissions 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.) -- 740959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.05~dfsg-8+b1 Severity: normal File: /usr/sbin/update-gsfontmap Dear Maintainer, the script update-gsfontmap creates (among others) the /var/lib/ghostscript/fonts/Fontmap file used by ghostscript to map font names. I believe it should make them world-readable. At the moment, it creates them with the umask of the user running it, which in my case happened to make them readable only by root. As a result, ghostscript (called as a normal user) did no longer work for me, since it failed to find some non-standard fonts. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ghostscript depends on: ii debconf [debconf-2.0] 1.5.52 ii gsfonts1:8.11+urwcyr1.0.7~pre44-4.2 ii libc6 2.17-97 ii libgs9 9.05~dfsg-8+b1 ghostscript recommends no packages. Versions of packages ghostscript suggests: ii cups-filters [ghostscript-cups] 1.0.46-1 ii ghostscript-x9.05~dfsg-8+b1 ii hpijs3.13.4-1 -- no debconf information --- End Message --- --- Begin Message --- Source: ghostscript Source-Version: 10.02.1~dfsg-3 Done: Steve M. Robbins We believe that the bug you reported is fixed in the latest version of ghostscript, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 740...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated ghostscript package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 20 Jan 2024 15:44:07 -0600 Source: ghostscript Architecture: source Version: 10.02.1~dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Steve M. Robbins Closes: 740959 782901 992889 1053377 Changes: ghostscript (10.02.1~dfsg-3) unstable; urgency=medium . [ наб ] * [ee3d1ac] Simplify /sbin/update-gsfontmap (Closes: #992889) . [ Steve Robbins ] * [ccc0e3c] Explicitly set font map files to be world readable. Closes: #740959. * [5fce3d3] Add suggestion for package texlive-binaries, needed to use dvipdf. Closes: #782901. * [9ab8028] ghostscript: add conflicts to ghostcript-x to allow removal of the obsolete transitional package. Closes: #1053377 Checksums-Sha1: d7583a3f735f07dbca4c938fb2e9b3062dcf667f 2796 ghostscript_10.02.1~dfsg-3.dsc 3848f95307726499c0d9bcf6ea8afd03001d6657 84268 ghostscript_10.02.1~dfsg-3.debian.tar.xz 90c5b5eb55c3e27d552945617cf47cb541c50a92 11274 ghostscript_10.02.1~dfsg-3_source.buildinfo Checksums-Sha256: 72b7456cfa3be3caea85d1da6e933099fa0220fb818d744ca4b4abbf3b53094e 2796 ghostscript_10.02.1~dfsg-3.dsc 647f99e9798d0d2edb80d57cd0203bd363121311cbb7486490559792833d8f42 84268 ghostscript_10.02.1~dfsg-3.debian.tar.xz a784c5b2073b52aa21b0e3fd86ac8db44cb2667c418e2c996d80a0cb763bcedd 11274 ghostscript_10.02.1~dfsg-3_source.buildinfo Files: 309c5d78143fc16c48affa402567bda1 2796 text optional ghostscript_10.02.1~dfsg-3.dsc 9bb73130a477951b974de55cfb9646ad 84268 text optional ghostscript_10.02.1~dfsg-3.debian.tar.xz fefeb9480d6a28fe00f57e203f5c7e69 11274 text optional ghostscript_10.02.1~dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEy89k8fa3rclNjyokyeVeL63I9LkFAmWsPxYPHHNtckBkZWJp YW4ub3JnAAoJEMnlXi+tyPS5Lm4QAJW98420MHxd4y/agrcS85yaFWymrArBmKc7 uJwtgloufYcP10x2iJQuBMPAlUlpAnPEJFeCcGyxc92ojiLSua6qIJBxD/PSc7JG ZeO2IgmfSUnv8o7pQfxRRy1MWzR1sa+VR+bw9bjkaLHGA+JwM1DWykiWaiYPQaSj
Bug#610580: marked as done (add SEE ALSO to the man pages)
Your message dated Sat, 20 Jan 2024 14:35:39 -0600 with message-id <15878987.O9o76ZdvQC@riemann> and subject line Re: add SEE ALSO to the man pages has caused the Debian Bug report #610580, regarding add SEE ALSO to the man pages 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.) -- 610580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 8.71~dfsg2-6.1 Severity: wishlist File: /usr/share/man/man1/pdf2ps.1.gz $ dlocate -man ghostscript|wc -l 26 However at least pdf2ps lacks a SEE ALSO to its brother programs. I didn't check the others. e.g., pdf2ps could say SEE ALSO ps2pdf(1) etc. --- End Message --- --- Begin Message --- On Wed, 19 Jan 2011 19:18:35 +0800 jida...@jidanni.org wrote: > Package: ghostscript > Version: 8.71~dfsg2-6.1 > Severity: wishlist > File: /usr/share/man/man1/pdf2ps.1.gz > > $ dlocate -man ghostscript|wc -l > 26 > However at least pdf2ps lacks a SEE ALSO to its brother programs. I > didn't check the others. e.g., pdf2ps could say SEE ALSO ps2pdf(1) etc. Closing since there's been no action taken in 13 years, likely because it is too vague to be actionable. signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: tagging 740959
Processing commands for cont...@bugs.debian.org: > tags 740959 + pending Bug #740959 [ghostscript] /usr/sbin/update-gsfontmap: sets wrong file permissions Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 740959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 992889
Processing commands for cont...@bugs.debian.org: > tags 992889 + pending Bug #992889 [ghostscript] /usr/sbin/update-gsfontmap: overly complicated Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 992889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#610668: marked as done (mention gv more)
Your message dated Sat, 20 Jan 2024 15:02:33 -0600 with message-id <6250165.mvXUDI8C0e@riemann> and subject line Re: mention gv more has caused the Debian Bug report #610668, regarding mention gv more 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.) -- 610668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 8.71~dfsg2-6.1 Severity: wishlist None of the man pages etc. mention gv. Nobody can figure out how to view things else wise. Especially the gs command docs. That even belongs to a different package, gconf. --- End Message --- --- Begin Message --- On Fri, 21 Jan 2011 09:14:10 +0800 jida...@jidanni.org wrote: > Package: ghostscript > Version: 8.71~dfsg2-6.1 > Severity: wishlist > > None of the man pages etc. mention gv. > Nobody can figure out how to view things else wise. > Especially the gs command docs. That even belongs to a different > package, gconf. Closing since there's been no action taken in 13 years, likely because it is too vague to be actionable. signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: bug 469761 is not forwarded
Processing commands for cont...@bugs.debian.org: > notforwarded 469761 Bug #469761 [ghostscript] file crashes ps2pdf/epstool/ghostscript Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if you need assistance. -- 469761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 426386 is not forwarded
Processing commands for cont...@bugs.debian.org: > notforwarded 426386 Bug #426386 [src:ghostscript] gs-common: When converting an eps file with ps2pdfwr, the bounding box is lost Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if you need assistance. -- 426386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#414002: marked as done (gs -dSAFER: /invalidfileaccess with "run" operator)
Your message dated Sun, 14 Jan 2024 17:03:32 -0600
with message-id <2731732.mvXUDI8C0e@riemann>
and subject line Re: [gs-common] Retag FTBS
has caused the Debian Bug report #414002,
regarding gs -dSAFER: /invalidfileaccess with "run" operator
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.)
--
414002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-pstricks
Version: 2005.dfsg.3-1
Severity: normal
I try to use the package pst-map2dII using the syntax as in the below minimal
input file, and with all data in the directory ../dataII relative to the
directory of my input file. However, I get the error:
This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com)
' TeX output 2007.02.26:1631' -> report.ps
.
[1] [2] [3] [4] [5] [6] [7] [8]
[9]
ERROR: /invalidfileaccess in --file--
Operand stack:
(../dataII/europe-cil.dat) (r)
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
%--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
%--nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1
%3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop
%.runexec2 --nostringval-- --nostringval-- --nostringval-- 2
%%stopped_push --nostringval-- 1 6 %oparray_pop --nostringval--
Dictionary stack:
--dict:1124/1686(ro)(G)-- --dict:0/20(G)-- --dict:105/200(L)--
--dict:185/300(L)-- --dict:38/200(L)-- --dict:121/200(L)--
Current allocation mode is local
Last OS error: 2
Current file position is 177842
ESP Ghostscript 815.03: Unrecoverable error, exit code 1
-- Package-specific info:
If you report an error when running one of the TeX-related binaries
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report. Don't forget to also include minimal examples of
other files that are needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!
If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at
http://www.latex-einfuehrung.de/mini-en.html (english)
or
http://www.latex-einfuehrung.de/mini.html (german)
##
minimal input file
\documentclass[letterpaper,12pt]{article}
\usepackage[english]{babel}
\usepackage{pstricks}
\usepackage{pst-map2dII}
\begin{document}
\psset{xunit=0.70,yunit=0.70, path=../dataII}
\begin{pspicture*}(-9,-4)(10,9)
\WorldMapII[maillage=false,all=true,level=5,borders=false,linewidth=0.01\pslinewidth,linecolor=gray]
\end{pspicture*}
\end{document}
##
other files
##
List of ls-R files
-rw-r- 1 arnout arnout 1418 2007-02-22 20:11 /home/arnout/texmf/ls-R
-rw-r--r-- 1 root root 1043 2007-02-26 16:03 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 2007-02-05 16:56 /usr/share/texmf/ls-R ->
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 27 2007-01-15 19:19 /usr/share/texmf-texlive/ls-R ->
/var/lib/texmf/ls-R-TEXLIVE
lrwxrwxrwx 1 root root 27 2007-01-15 19:19 /usr/share/texmf-texlive/ls-R ->
/var/lib/texmf/ls-R-TEXLIVE
##
Config files
lrwxrwxrwx 1 root root 20 2007-02-05 16:56 /usr/share/texmf/web2c/texmf.cnf ->
/etc/texmf/texmf.cnf
-rw-r--r-- 1 root root 5303 2007-02-15 18:23 /var/lib/texmf/web2c/fmtutil.cnf
-rw-r--r-- 1 root root 7281 2007-02-15 18:23 /var/lib/texmf/web2c/updmap.cfg
-rw-r--r-- 1 root root 5446 2007-02-15 18:23
/var/lib/texmf/tex/generic/config/language.dat
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.UTF-8)
Versions of packages texlive-pstricks depends on:
ii tetex-bin 3.0-30The teTeX programs
ii texlive-common 2005.dfsg.3-1 TeX Live: Base component
ii texlive-generic-recommende 2005.dfsg.3-1 TeX Live: Miscellaneous generic ma
texlive-pstricks recommends no packages.
Versions of packages tex-common depends on:
ii debconf [debconf-2.0] 1.5.11 Debian
Bug#1022958: marked as done (/usr/bin/ghostscript: ghostscript conflicts with postscript-viewer when using upgrade in Sid)
Your message dated Mon, 08 Jan 2024 23:30:21 -0600 with message-id <4495279.Wku2Vz74k6@riemann> and subject line Re: bug resolved has caused the Debian Bug report #1022958, regarding /usr/bin/ghostscript: ghostscript conflicts with postscript-viewer when using upgrade in Sid 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.) -- 1022958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.56.1~dfsg-1 Severity: normal File: /usr/bin/ghostscript X-Debbugs-Cc: n_jour...@gmx.com Dear Maintainer, When I want to upgrade the ghostscript package to the latest version Sid (to 10.0.0~dfsg-4), the package manager shows me a conflict with the postscript-viewer package. So the upgrade is cancelled by me. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-2-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ghostscript depends on: ii libc6 2.35-4 ii libgs9 9.56.1~dfsg-1 ghostscript recommends no packages. Versions of packages ghostscript suggests: pn ghostscript-x -- no debconf information --- End Message --- --- Begin Message --- On Sat, 29 Oct 2022 14:37:52 +0200 "n_jour...@gmx.com" wrote: > Dear Maintainer, > The version 10.0.0~dfsg-6 of the ghostscript package seems to have removed the conflict. > So that's resolved, thank you. > > Nicolas J signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#987566: marked as done (ghostscript: PDF Interpreter error on armel)
Your message dated Mon, 08 Jan 2024 23:34:12 -0600
with message-id <38753985.J2Yia2DhmK@riemann>
and subject line Re: PDF Interpreter errors
has caused the Debian Bug report #987566,
regarding ghostscript: PDF Interpreter error on armel
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.)
--
987566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghostscript
Version: 9.27~dfsg-2+deb10u4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Initialy, I found the bug by updating from Debian stretch to buster (10.9): the
printer was working on stretch but no more on buster. The device was running on
armel. I did tests on i686 and it works.
After investigation, I was able to identify the « smallest » error context. The
following command:
gs -dPDFDEBUG -dPARANOIDSAFER -dNOPAUSE -dNOINTERPOLATE -dNOMEDIAATTRS
-dShowAcroForm -sstdout=%stderr -sOutputFile=%stdout -sDEVICE=jpeg
-sMediaType=Automatic -sOutputType=0 -r600x600 -dMediaPosition=7
-dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=841 -dcupsMediaType=-1
-dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=17 -dcupsInteger0=26
-scupsPageSizeName=A4 -I/usr/share/cups/fonts -c '<>setpagedevice' -f -_ <
/tmp/ades.cups-pdf >/dev/null
Produces error messages on armel but not on i686:
8.3 0 0 8.3 0 0 cm
BT
Error reading a content stream. The page may be incomplete.
Output may be incorrect.
Error: Form stream has unbalanced q/Q operators (too many q's)
Output may be incorrect.
Q
Q
Error: File did not complete the page properly and may be damaged.
Output may be incorrect.
%Resolving: [1 0]
The input is obtained from hp-setup print test page (PS) converted to cups-pdf
with cupsfilter, which certainly means that gs is not able to read a PDF it
generates.
-- System Information:
Debian Release: 10.9
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)
Kernel: Linux 4.19.158-1
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ghostscript depends on:
ii libc6 2.28-10
ii libgs9 9.27~dfsg-2+deb10u4
Versions of packages ghostscript recommends:
ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.4
Versions of packages ghostscript suggests:
pn ghostscript-x
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 25 Apr 2021 21:34:04 +0200 Guilhem Bonnefille
wrote:
> Dear maintainers,
>
> Please, note that this bug only concerns the armel architecture. I was
> able to double check on i686 with the same package version and it
> worked.
>
> I'm also able to indicate that this bugs is solved/fixed in
> 9.53.3~dfsg-7 (testing).
Stable is now shipping 10.0.0, so I presume the issue may be closed?
-Steve
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
Bug#915104: marked as done (PDF to JPG conversion of single pages partly broken)
Your message dated Mon, 08 Jan 2024 23:58:58 -0600 with message-id <1759308.vCJZsxu672@riemann> and subject line Re: PDF to JPG conversion of single pages partly broken has caused the Debian Bug report #915104, regarding PDF to JPG conversion of single pages partly broken 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.) -- 915104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.26~dfsg-0+deb9u1 When we convert PDF files to JPG using ghostscript, some pages are not convertible by themselves, only when converting the whole PDF file. The command used to extract the first page is: $ convert input.pdf[0] output.jpg convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 '-r72x72' -dFirstPage=1 -dLastPage=1 '-sOutputFile=/tmp/magick-157641emDtZokGRcg%d' '-f/tmp/magick-15764aXydnGwiqrgk' '-f/tmp/magick-15764wo8U_FWjydko'' (-1) @ error/delegate.c/ExternalDelegateCommand/462. convert-im6.q16: no images defined `output.jpg' @ error/convert.c/ConvertImageCommand/3258. This does not(!) happen after downgrading to the previous version 9.25~dfsg-0+deb9u1. We are using Debian GNU/Linux 9, Kernel 4.9.0-8-amd64. --- End Message --- --- Begin Message --- On Fri, 30 Nov 2018 16:08:26 +0100 Andreas Ziegler wrote: > Package: ghostscript > Version: 9.26~dfsg-0+deb9u1 > > When we convert PDF files to JPG using ghostscript, some pages are not > convertible by themselves, only when converting the whole PDF file. > > The command used to extract the first page is: > > $ convert input.pdf[0] output.jpg Tested using ghostscript 10.02.1 and obtained correct output. -Steve signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#985635: marked as done (ghostscript 9.53 produces incorrect output with xelatex and PStricks)
Your message dated Mon, 08 Jan 2024 23:35:54 -0600
with message-id <2948294.o0KrE1Onz3@riemann>
and subject line Re: Bug#985635: ghostscript 9.53 produces incorrect output
with xelatex and PStricks
has caused the Debian Bug report #985635,
regarding ghostscript 9.53 produces incorrect output with xelatex and PStricks
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.)
--
985635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghostscript
Version: 9.53~dfsg-2+deb10u4
X-Debbugs-Cc: mccl...@ucsc.edu, debian-tex-ma...@lists.debian.org
Severity: normal
Tags: upstream
Dear Maintainer,
A LaTeX document which includes a call to PStricks and the pst-jtree package
produces correct
PDF output when compiled with xelatex in Debian buster. Following an upgrade
to bullseye, the
same document compiled in exactly the same way produces incorrect output.
Investigation suggests that the source of the problem was an upgrade to
ghostscript -- as far
as version 9.53. When I downgraded ghostscript to the version in buster
(ghostscript 9.27) and
made no other changes, compiling with xelatex produced correct output. Version
9.52 of
ghostscript is not available in the Debian archive, it seems. But I downloaded
a binary from:
https://github.com/ArtifexSoftware/ghostpdl-downloads/releases/tag/gs952 and
created a symlink
between the 9.52 version in /opt and /usr/bin/gs. This adjustment also led to a
successful
compilation. The problem, then, seems to have been introduced in the transition
from
ghostscript 9.52 to ghostscript 9.53.
The nature of the problem is revealed in the attached files -- one source-file
(tree.tex) was
compiled with xelatex in three different contexts:
- with ghostscript 9.53 in bullseye (tree-gs-9.53.pdf)
- with ghostscript 9.27 in buster (tree-gs-9.27.pdf)
- with ghostscript 9.52 (tree-gs-9.52.pdf)
Under gs-9.53 all of the various labels are incorrectly gathered at the root of
the tree and
are superimposed on one another. Under earlier versions of ghostscript (9.52
and 9.27), the
document is rendered as intended -- with the labels distinct and printed at the
intended nodes.
Thank you for all of your work,
Jim McCloskey
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ghostscript depends on:
ii libc6 2.31-9
ii libgs9 9.27~dfsg-2+deb10u4
Versions of packages ghostscript recommends:
ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.5
Versions of packages ghostscript suggests:
pn ghostscript-x
-- no debconf information
\documentclass[12pt]{article}
%%
%% FONTS
%%
\usepackage{textcomp}
\usepackage{fontspec}
\setmainfont[Numbers={OldStyle}]{Linux Libertine}
%%
%%
%\usepackage{pst-all}% makes no difference
\usepackage{pstricks}
\usepackage{pst-jtree}
%%
%%
\begin{document}
{\centering
\vspace*{4\baselineskip}
\jtree[xunit=1.5,yunit=1.5]
\start
{CP}
{C}!a ^ {TM1P}
{TM1} !b ^ {POLP}
{POL} !c ^ {TLOP}
{subj} ^
{TLO} ^ {VceP}
{Vce} ^ {vP}
{\itshape pro ól an nimh}.
\adjoin at !a {\textit{gu-}}.
\adjoin at !b {\textit{-r}} .
\adjoin at !c {\itshape ól-adar} .
\endjtree
}
\end{document}
tree-gs-9.53.pdf
Description: Adobe PDF document
tree-gs-9.27.pdf
Description: Adobe PDF document
tree-gs-9.52.pdf
Description: Adobe PDF document
--- End Message ---
--- Begin Message ---
On Mon, 3 Jul 2023 23:57:33 + Jim McCloskey wrote:
> This problem is resolved in Debian 12 Bookworm, with the arrival of
ghostscript 10.0.
> The bug should probably be closed.
Thanks for letting us know!
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
Bug#951394: marked as done (pstoedit fails with findfont error with gs 9.26)
Your message dated Mon, 08 Jan 2024 23:51:55 -0600 with message-id <3892345.fW5hKsROvD@riemann> and subject line Re: pstoedit fails with findfont error with gs 9.26 has caused the Debian Bug report #951394, regarding pstoedit fails with findfont error with gs 9.26 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.) -- 951394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript, pstoedit Version: 9.26a~dfsg-0+deb9u6, 3.70-3+b2 Tags: upstream Control: fixed -1 + 9.50~dfsg-5 Hi. Dear maintainers of ghsotscript and pstoedit, Debian buster is affected by this bug: https://sourceforge.net/p/pstoedit/support-requests/4/ I'm afraid I don't understand the details. It appears that DELAYBIND is now deprecated with upstream. Everything works in bullseye. It is broken in stretch. Perhaps surprisingly, the pstoedit -nb option does not help. I am filing this bug here mostly to help other users of pstoedit on Debian. #880650 seems related but not identical. Maybe it would be worth considering a backport of ghostscript 9.50 to buster ? Steps to reproduce: $ cat <<'END' >test.ps %! /NimbusMonoPS-Bold findfont 50 scalefont setfont 100 100 moveto (C) show zealot:play> PS1='$ ' END $ pstoedit -f dump test.ps dump.ou pstoedit: version 3.70 / DLL interface 108 (built: Oct 11 2016 - release build - g++ 6.2.1 20161215 - 64-bit) : Copyright (C) 1993 - 2014 Wolfgang Glunz Error: /undefined in /findfont Operand stack: NimbusMonoPS-Bold Execution stack: %interp_exit .runexec2 --nostringval-- .findfontop --nostringval-- 2 %stopped_push --nostringval-- .findfontop .findfontop false 1 %stopped_push 2044 1 3 %oparray_pop 2043 1 3 %oparray_pop 2024 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- .findfontop --nostringval-- 2 %stopped_push --nostringval-- 2044 1 3 %oparray_pop 2043 1 3 %oparray_pop 2024 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- .findfontop --nostringval-- 2 %stopped_push --nostringval-- .findfontop 1975 1 3 %oparray_pop Dictionary stack: --dict:970/1684(ro)(G)-- --dict:0/20(G)-- --dict:321/450(L)-- Current allocation mode is local Current file position is 31 GPL Ghostscript 9.26: Unrecoverable error, exit code 1 PostScript/PDF Interpreter finished. Return status 256 executed command : /usr/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS "/tmp/psinZUL0CV" The interpreter seems to have failed, cannot proceed ! $ -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter. --- End Message --- --- Begin Message --- On Sat, 15 Feb 2020 21:36:41 + Ian Jackson wrote: > Package: ghostscript, pstoedit > Version: 9.26a~dfsg-0+deb9u6, 3.70-3+b2 > Tags: upstream > Control: fixed -1 + 9.50~dfsg-5 > I am filing this bug here mostly to help other users of pstoedit on > Debian. #880650 seems related but not identical. > > Maybe it would be worth considering a backport of ghostscript 9.50 to > buster ? I'm sorry that no action was taken 3+ years ago. Debian stable now ships 10.0.0 so I will close this bug. -Steve signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#790562: marked as done (Ghostscript: File has unbalanced q/Q operators (too many Q's))
Your message dated Mon, 08 Jan 2024 09:17:23 -0600 with message-id <329.VqM8IeB0Os@riemann> and subject line Re: Ghostscript: File has unbalanced q/Q operators (too many Q's) has caused the Debian Bug report #790562, regarding Ghostscript: File has unbalanced q/Q operators (too many Q's) 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.) -- 790562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: ghostscript version: 9.06~dfsg-2 When running ghostscript, the following errors are being generated in great quantity: stderr: " File has unbalanced q/Q operators (too many Q's) " resulting in log files filling the disk. Additionally, kernel soft lockup warnings appear: kernel:[406101.560749] BUG: soft lockup - CPU#4 stuck for 31s! [gs:21647] Command being run is: gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/screen -dNOPAUSE -dQUIET -dBandBufferSpace=5 -dBandSpace=10 -dBATCH -sOutputFile='out.pdf' 'in.pdf' It may be related to this bug on the ghostscript bug tracker flagged as resolved: http://bugs.ghostscript.com/show_bug.cgi?id=694310 Running on: 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux --- End Message --- --- Begin Message --- I meant to close the bug with the previous email. On Sunday, January 7, 2024 10:51:59 P.M. CST you wrote: > On Tue, 30 Jun 2015 09:17:06 +0100 supp...@compress-pdf.co.uk wrote: > > package: ghostscript > > version: 9.06~dfsg-2 > > > > When running ghostscript, the following errors are being generated in > > great quantity: > > stderr: " File has unbalanced q/Q operators (too many Q's) " > > > > resulting in log files filling the disk. > > > > Additionally, kernel soft lockup warnings appear: > > kernel:[406101.560749] BUG: soft lockup - CPU#4 stuck for 31s! [gs:21647] > > > > > > Command being run is: > > > > gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/screen > > -dNOPAUSE -dQUIET -dBandBufferSpace=5 -dBandSpace=10 > > -dBATCH -sOutputFile='out.pdf' 'in.pdf' > > > > > > It may be related to this bug on the ghostscript bug tracker flagged as > > resolved: > > http://bugs.ghostscript.com/show_bug.cgi?id=694310 > > In the absence of an example file, I will assume you are correct that this > is the upstream bug noted. That fix is now in Debian, so I'll close this > bug. -Steve signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#810080: marked as done (ghostscript: Infinite loop filling server logs with "File has unbalanced q/Q operators")
Your message dated Mon, 08 Jan 2024 09:17:23 -0600 with message-id <329.VqM8IeB0Os@riemann> and subject line Re: Ghostscript: File has unbalanced q/Q operators (too many Q's) has caused the Debian Bug report #790562, regarding ghostscript: Infinite loop filling server logs with "File has unbalanced q/Q operators" 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.) -- 790562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.06~dfsg-2+deb8u1 Severity: important Dear Maintainer, Short version: * What led up to the situation? "gs -o proper.pdf -sDEVICE=pdfwrite -dPDFSETTINGS=/prepress programmheft_2016.pdf" with http://www.naturpark-rheinland.de/programmheft_2016.pdf leads to infinite output of " File has unbalanced q/Q operators (too many Q's) " to stderr * What exactly did you do (or not do) that was effective (or ineffective)? A) Compiled upstream ghostscript 9.06 and executed the command above B) Use the upstream ghostscript Resources directory instead of /usr/share/ghostscript/Resources * What was the outcome of this action? A) Worked without problems B) Leads at least to an unrecoverable error instead * What outcome did you expect instead? Debians ghostscript package to work as upstream correctly rendering the PDF. Long version: One of our Debian wheezy webservers (ghostscript "9.05~dfsg-6.3+deb7u2") was brought down yesterday morning by running out of diskspace very quickly due to a spammed /var/log/apache2/error.log with 700GB of lines with " File has unbalanced q/Q operators (too many Q's) ". It turned out this was due to a process trying to create a thumbnail image of a pdf file "gs -q -dBATCH -dMaxBitmap=5000 -dNOPAUSE -sDEVICE=pnmraw -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72 -dFirstPage=1 -dLastPage=1 -sOutputFile=XXX -- YYY -c quit" The issue is reproducible on a Debian jessie server (ghostscript "9.06~dfsg-2+deb8u1") too by simply executing "gs -o proper.pdf -sDEVICE=pdfwrite -dPDFSETTINGS=/prepress programmheft_2016.pdf" The file is available for download at http://www.naturpark-rheinland.de/programmheft_2016.pdf All pdf viewers I tried had no problems displaying the file. I asked for help at #ghostscript, you can find the log here: http://ghostscript.com/irclogs/2016/01/05.html I compiled both gs905 and gs906 from ghostscripts git sources and could execute "./gs -o proper.pdf -sDEVICE=pdfwrite -dPDFSETTINGS=/prepress programmheft_2016.pdf" without errors. Using the Resource folder of upstream ghostscript for the debian ghostscript package by executing "gs -I../Resource/Init -o proper.pdf -sDEVICE=pdfwrite -dPDFSETTINGS=/prepress programmheft_2016.pdf" leads to Error: /rangecheck in --run-- Operand stack: --dict:12/21(L)-- 1 11 3 --nostringval-- false 7 DataSource --nostringval-- 0 16 --nostringval-- 12 --dict:2/2(L)-- Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1910 1 3 %oparray_pop 1909 1 3 %oparray_pop 1893 1 3 %oparray_pop --nostringval-- --nostringval-- 2 1 1 --nostringval-- %for_pos_int_continue --nostringval-- --nostringval-- false 1 %stopped_push --nostringval-- --nostringval-- Dictionary stack: --dict:1168/1684(ro)(G)-- --dict:1/20(G)-- --dict:83/200(L)-- --dict:83/200(L)-- --dict:109/127(ro)(G)-- --dict:293/300(ro)(G)-- --dict:25/31(L)-- --dict:6/8(L)-- --dict:25/40(L)-- --dict:1/1(ro)(G)-- --dict:14/15(L)-- --dict:1/1(ro)(G)-- --dict:4/5(L)-- --dict:1/1(ro)(G)-- --dict:7/15(L)-- --dict:9/20(L)-- Current allocation mode is local GPL Ghostscript 9.06: Unrecoverable error, exit code 1 which is an unrecoverable error but at least no infinite spamming of the error log. As a workaround I use this on our servers now: git clone --single-branch --branch gs906 "http://git.ghostscript.com/ghostpdl.git; ~/ghostpdl mkdir /usr/local/share/ghostscript/ mv ~/ghostpdl/gs/Resource /usr/local/share/ghostscript/ rm -rf ~/ghostpdl echo "GS_LIB=/usr/local/share/ghostscript/Resource/Init" >> /etc/environment Since the problem does not exist on upstream ghostscript 9.05 or 9.06 but only in the debian package it mus
Processed: forcibly merging 838328 841430
Processing commands for cont...@bugs.debian.org:
> forcemerge 838328 841430
Bug #838328 {Done: Steven Robbins } [ghostscript] ghostscript:
need to backport fix for Ghostscript bug 695862 (segfault on certain machines)
Bug #841430 [ghostscript] ghostscript segfaults converting to pam
Marked Bug as done
Marked as found in versions ghostscript/9.06~dfsg-2+deb8u1.
Bug #838328 {Done: Steven Robbins } [ghostscript] ghostscript:
need to backport fix for Ghostscript bug 695862 (segfault on certain machines)
Marked as found in versions ghostscript/9.06~dfsg-2+deb8u3.
Merged 838328 841430
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
838328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838328
841430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#835126: marked as done (doc package missing VectorDevices.htm)
Your message dated Sun, 07 Jan 2024 22:43:51 -0600 with message-id <2530750.Sgy9Pd6rRy@riemann> and subject line Re: doc package missing VectorDevices.htm has caused the Debian Bug report #835126, regarding doc package missing VectorDevices.htm 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.) -- 835126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript-doc Version: 9.19~dfsg-2 Severity: normal file:///usr/share/doc/ghostscript/Devices.htm#High-level (at the bottom of the section, under 4.5) links to VectorDevices.htm, but it's not in the doc package. I found it on the web at http://www.ghostscript.com/doc/9.19/VectorDevices.htm -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (150, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ghostscript-doc depends on no packages. ghostscript-doc recommends no packages. Versions of packages ghostscript-doc suggests: ii ghostscript 9.19~dfsg-2 -- no debconf information --- End Message --- --- Begin Message --- On Mon, 22 Aug 2016 13:44:01 -0400 Anthony DeRobertis wrote: > Package: ghostscript-doc > Version: 9.19~dfsg-2 > Severity: normal > > file:///usr/share/doc/ghostscript/Devices.htm#High-level (at the bottom > of the section, under 4.5) links to VectorDevices.htm, but it's not in > the doc package. This was corrected at some point. The file is present in current debian/sid package. signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#704112: marked as done (ghostscript: gs -dEPSCrop doesn't work)
Your message dated Sun, 07 Jan 2024 21:46:32 -0600 with message-id <2958304.VdNmn5OnKV@riemann> and subject line Re: ghostscript: gs -dEPSCrop doesn't work has caused the Debian Bug report #704112, regarding ghostscript: gs -dEPSCrop doesn't work 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.) -- 704112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.05~dfsg-6.3 Severity: normal Tags: upstream Hi, The option -dEPSCrop (to make gs respect the BoundingBox when writing to PDF or JPEG for instance) doesn't seem to work on GPL Ghostscript. Here is a minimal example: ~/temp>cat a.ps %!PS-Adobe-2.0 %%BoundingBox: 0 0 100 100 0 0 moveto 100 100 rlineto stroke showpage ~/temp>gs -q -dEPSCrop -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=a.pdf -c save pop -f a.ps ~/temp>strings a.pdf | grep MediaBox <http://ghostscript.com/doc/7.07/Use.htm yielded only the EPS case. This missing option is really problematic for me. As a publisher, I used it in many varied situations. I hope you can make it work soon! Best regards, Sébastien. -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (900, 'stable'), (400, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US.iso88591) Shell: /bin/sh linked to /bin/dash Versions of packages ghostscript depends on: ii debconf [de 1.5.49 Debian configuration management sy ii debianutils 4.3.2Miscellaneous utilities specific t ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2 Fonts for the Ghostscript interpre ii libc6 2.13-38 Embedded GNU C Library: Shared lib ii libgs9 9.05~dfsg-6.3interpreter for the PostScript lan ghostscript recommends no packages. Versions of packages ghostscript suggests: ii ghostscript-cups 9.05~dfsg-6.3 interpreter for the PostScript lan ii ghostscript-x 9.05~dfsg-6.3 interpreter for the PostScript lan ii hpijs 3.12.6-3.1transitional dummy package for hpi -- no debconf information --- End Message --- --- Begin Message --- I meant to close this bug with the previous message: On Sun, 07 Jan 2024 21:26:32 -0600 Steven Robbins wrote: > On Thu, 28 Mar 2013 02:21:25 +0100 Sebastien Desreux wrote: > > > I do realize that the PS file above is not an EPS. Yet this option also > worked > > for PS files with AFPL gs and then ESP gs. Besides, a search for "crop" on > > http://ghostscript.com/doc/7.07/Use.htm > > yielded only the EPS case. > > > > It seems clear that the option EPSCrop is for EPS input, so this doesn't seem > like a bug. Though I sympathise that it may be an irritating change in > behaviour if it did used to work previously. > > -Steve > signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#786827: marked as done (ghostscript: ps2pdf hangs while gv displays the file OK.)
Your message dated Sun, 07 Jan 2024 22:17:48 -0600 with message-id <37890964.XM6RcZxFsP@riemann> and subject line Re: ghostscript: ps2pdf hangs while gv displays the file OK. has caused the Debian Bug report #786827, regarding ghostscript: ps2pdf hangs while gv displays the file OK. 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.) -- 786827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.06~dfsg-2 Severity: normal Dear Maintainer, ps2pdf hangs for me with this postscript file when simply run as: $ ps2pdf test.ps no output is ever generated, except a file in /tmp that slowly grows in size (probably indefinitely), that I found by 'strace' of 'gs' process. $ gv test.ps shows file just fine. The ps2pdf actually runs: /usr/bin/gs -P- -dSAFER -dCompatibilityLevel=1.4 -q -P- -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sstdout=%stderr -sOutputFile=test.pdf -P- -dSAFER -dCompatibilityLevel=1.4 -c .setpdfwrite -f test.ps that hangs when run manually as well. Changing -sDEVICE to =X11 instead of =pdfwrite and removing -dNOPAUSE displays the output on the screen just fine. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ghostscript depends on: ii debconf [debconf-2.0] 1.5.56 ii gsfonts1:8.11+urwcyr1.0.7~pre44-4.2 ii libc6 2.19-18 ii libgs9 9.06~dfsg-2 ghostscript recommends no packages. Versions of packages ghostscript suggests: ii ghostscript-x 9.06~dfsg-2 -- debconf-show failed test.ps Description: PostScript document --- End Message --- --- Begin Message --- On Mon, 25 May 2015 23:50:43 +0300 Sergei Organov wrote: > Package: ghostscript > Version: 9.06~dfsg-2 > Severity: normal > > Dear Maintainer, > > ps2pdf hangs for me with this postscript file when simply run as: > > $ ps2pdf test.ps > > no output is ever generated, except a file in /tmp that slowly grows in size > (probably indefinitely), that I found by 'strace' of 'gs' process. I just tested using ghostscript 10.02.1 (current "Debian/sid" version) and the conversion succeeds; the result displays the same as "gv test.ps". -Steve signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#824207: marked as done (ghostscript: Segmentation fault when printing in color mode)
Your message dated Sun, 07 Jan 2024 22:40:17 -0600 with message-id <6515466.K2JlShyGXD@riemann> and subject line Re: ghostscript: Segmentation fault when printing in color mode has caused the Debian Bug report #824207, regarding ghostscript: Segmentation fault when printing in color mode 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.) -- 824207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.06~dfsg-2+deb8u1 Severity: normal Dear Maintainer, when trying to make a print using colors from any application (gimp, inkscape...) no printing happens. Ghostscript segfaults due to mutex issue in glibc. The problem is related to an already fixed bug in ghostscript's recursive mutex handling: http://bugs.ghostscript.com/show_bug.cgi?id=695862 The problem only occurs on Intel Skylake based machines supporting TSX memory like XEON cpus. (Supporting hardware accelerated mutexes) These mutexes are sensitive to wrong usage, e.g. double unlocking which actually happens in ghostscript due to the buggy implementation Here is a backtrace: Core was generated by `/usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -sDEVICE='. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fc4823de140 in __lll_unlock_elision () from /lib/x86_64-linux-gnu/libpthread.so.0 (gdb) bt #0 0x7fc4823de140 in __lll_unlock_elision () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fc48506c409 in gp_monitor_leave (mona=0x1fbece8) at ./base/gp_psync.c:197 #2 0x7fc48502571a in gsicc_get_link_profile (pis=, dev=, gs_input_profile=0x1fe2600, gs_output_profile=0x1fe2600, rendering_params=0x7ffe6ab60850, memory=, devicegraytok=1) at ./base/gsicc_cache.c:797 #3 0x7fc485025b8b in gsicc_get_link (pis=0x1e485d8, dev_in=0x20e1c58, pcs_in=0x1fbece8, pcs_in@entry=0x20f3860, output_colorspace=0x1, rendering_params=0x7ffe6ab60850, memory=0x0) at ./base/gsicc_cache.c:537 #4 0x7fc485020cf9 in gx_remap_ICC (pcc=0x20f2f30, pcs=0x20f3860, pdc=0x20f32e8, pis=0x1e485d8, dev=0x20e1c58, select=gs_color_select_texture) at ./base/gsicc.c:353 #5 0x7fc4851a1d4c in gx_remap_color (pgs=0x1e485d8) at ./base/gxcmap.c:558 #6 0x7fc48518efb8 in do_stroke (pgs=0x1e485d8) at ./base/gspaint.c:402 #7 gs_stroke (pgs=0x1e485d8) at ./base/gspaint.c:495 #8 0x7fc484f89b0a in interp (pi_ctx_p=0x1e4d518, pref=0x1e64730, perror_object=0x1fbece8, perror_object@entry=0x7ffe6ab61420) at ./psi/interp.c:1287 #9 0x7fc484f8a84b in gs_call_interp (perror_object=0x7ffe6ab61420, pexit_code=0x7ffe6ab6141c, user_errors=1, pref=0x7ffe6ab612a0, pi_ctx_p=) at ./psi/interp.c:501 #10 gs_interpret (pi_ctx_p=, pref=pref@entry=0x7ffe6ab613e0, user_errors=1, pexit_code=0x7ffe6ab6141c, perror_object=0x7ffe6ab61420) at ./psi/interp.c:459 #11 0x7fc484f7fcf8 in gs_main_interpret (perror_object=, pexit_code=, user_errors=, pref=0x7ffe6ab613e0, minst=) at ./psi/imain.c:241 #12 gs_main_run_string_end (minst=, user_errors=, pexit_code=, perror_object=) at ./psi/imain.c:607 #13 0x7fc484f81169 in run_string (minst=minst@entry=0x1e21770, str=str@entry=0x7fc4852036a0 ".runstdin", options=options@entry=2) at ./psi/imainarg.c:834 #14 0x7fc484f8181e in swproc (minst=minst@entry=0x1e21770, arg=0x7ffe6ab62c80 "", arg@entry=0x7ffe6ab62c7e "-_", pal=pal@entry=0x7ffe6ab61be0) at ./psi/imainarg.c:293 #15 0x7fc484f82770 in gs_main_init_with_args (minst=0x1e21770, argc=argc@entry=22, argv=argv@entry=0x7ffe6ab62708) at ./psi/imainarg.c:211 #16 0x7fc484f8363b in gsapi_init_with_args (lib=, argc=argc@entry=22, argv=argv@entry=0x7ffe6ab62708) at ./psi/iapi.c:174 #17 0x00400a0f in main (argc=22, argv=0x7ffe6ab62708) at ./psi/dxmainc.c:86 Updating to ghostscript package from stretch fixes the issue for me. -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.3-proton (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ghostscript depends on: ii debconf [debconf-2.0] 1.5.56 ii gsfonts1:8.11+urwcyr1.0.7~pre44-4.2 ii libc6 2.21-9 ii libgs9 9.06~dfsg-2+deb8u1
Bug#838328: marked as done (ghostscript: need to backport fix for Ghostscript bug 695862 (segfault on certain machines))
Your message dated Sun, 07 Jan 2024 22:45:54 -0600
with message-id <1911575.eGJsNajkDb@riemann>
and subject line Re: ghostscript: need to backport fix for Ghostscript bug
695862 (segfault on certain machines)
has caused the Debian Bug report #838328,
regarding ghostscript: need to backport fix for Ghostscript bug 695862
(segfault on certain machines)
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.)
--
838328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghostscript
Version: 9.06~dfsg-2+deb8u1
Ghostscript <=9.15 has a bug which manifests itself only on certain
machines, causing it to segfault on certain PDF files. This is due to
the incorrect assumption that unlocking an already unlocked mutex is a
no-op, something which is not guaranteed by Single Unix, and may or
may not be true depending on the hardware / kernel / phase of the
moon. See http://bugs.ghostscript.com/show_bug.cgi?id=695862
> for details.
I have been bitten by this bug (changed my processor and suddenly all
sorts of PDF files wouldn't print), so it is not theoretical.
I believe Debian should backport some fix for this. One possible fix
(tested on my machine) is attached: it consists of using
error-checking mutexes instead of fast ones (error-checking mutexes
are documented to return EPERM when unlocked twice). This fix is
called "hacky" by Chris Liddell in the above-mentioned bug report
page, but I think it is perfectly sensible. Otherwise, backport the
patch made to the ghostscript upstream itself.
--
David A. Madore
( http://www.madore.org/~david/ )
Description: fix ghostscript bug #695862 by using error-checking mutexes
Author: David Madore
Last-Update: 2016-09-20
Index: ghostscript-9.06~dfsg/base/gp_psync.c
===
--- ghostscript-9.06~dfsg.orig/base/gp_psync.c
+++ ghostscript-9.06~dfsg/base/gp_psync.c
@@ -20,6 +20,7 @@
#include
#include "gserrors.h"
#include "gpsync.h"
+#include
/*
* Thanks to Larry Jones for this revision of
@@ -64,10 +65,21 @@ gp_semaphore_open(gp_semaphore * sema)
pt_semaphore_t * const sem = (pt_semaphore_t *)sema;
int scode;
+/* Idiotic threads API won't let you create an error-checking mutex
+ * without creating another "mutexattr" object which itself
+ * has to be initialized. This is _absurdly_ verbose! */
+static pthread_mutexattr_t mutexattr;
+static char mutexattr_initialized = 0;
+
if (!sema)
return -1; /* semaphores are not movable */
+if ( ! mutexattr_initialized ) {
+ mutexattr_initialized = 1;
+ pthread_mutexattr_init();
+ pthread_mutexattr_settype(, PTHREAD_MUTEX_ERRORCHECK);
+}
sem->count = 0;
-scode = pthread_mutex_init(>mutex, NULL);
+scode = pthread_mutex_init(>mutex, );
if (scode == 0)
scode = pthread_cond_init(>cond, NULL);
return SEM_ERROR_CODE(scode);
@@ -103,6 +115,8 @@ gp_semaphore_wait(gp_semaphore * sema)
if (scode == 0)
--sem->count;
scode2 = pthread_mutex_unlock(>mutex);
+if ( scode2 == EPERM )
+ scode2 = 0;
if (scode == 0)
scode = scode2;
return SEM_ERROR_CODE(scode);
@@ -120,6 +134,8 @@ gp_semaphore_signal(gp_semaphore * sema)
if (sem->count++ == 0)
scode = pthread_cond_signal(>cond);
scode2 = pthread_mutex_unlock(>mutex);
+if ( scode2 == EPERM )
+ scode2 = 0;
if (scode == 0)
scode = scode2;
return SEM_ERROR_CODE(scode);
@@ -149,11 +165,22 @@ gp_monitor_open(gp_monitor * mona)
pthread_mutex_t *mon;
int scode;
+/* Idiotic threads API won't let you create an error-checking mutex
+ * without creating another "mutexattr" object which itself
+ * has to be initialized. This is _absurdly_ verbose! */
+static pthread_mutexattr_t mutexattr;
+static char mutexattr_initialized = 0;
+
if (!mona)
return -1; /* monitors are not movable */
+if ( ! mutexattr_initialized ) {
+ mutexattr_initialized = 1;
+ pthread_mutexattr_init();
+ pthread_mutexattr_settype(, PTHREAD_MUTEX_ERRORCHECK);
+}
mon = &((gp_pthread_recursive_t *)mona)->mutex;
((gp_pthread_recursive_t *)mona)->self_id = 0; /* Not valid unless mutex is locked */
-scode = pthread_mutex_init(mon, NULL);
+scode = pthread_mutex_init(mon, );
return SEM_ERROR_CODE(scode);
}
@@ -195,6 +222,8 @@ gp_monitor_leave(gp_monitor * mon
Bug#815115: marked as done (ghostscript: FTBFS on hppa: libpng.a: error adding symbols: Bad value)
Your message dated Sun, 07 Jan 2024 22:32:51 -0600 with message-id <2197324.C4sosBPzcN@riemann> and subject line Re: ghostscript: FTBFS on hppa: libpng.a: error adding symbols: Bad value has caused the Debian Bug report #815115, regarding ghostscript: FTBFS on hppa: libpng.a: error adding symbols: Bad value 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.) -- 815115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.18~dfsg-3 Severity: normal Dear Maintainer, On several arches, the following or a similar error occurs building 9.18~dfsg-4: ./soobj/aux/echogs -a ./soobj/ldt.tr -s - -ldl -lm -lidn -lpaper -ltiff -rdynamic -ldl -lfontconfig -lfreetype -lopenjp2 -lpthread -lm if [ x != x ]; then LD_RUN_PATH=; export LD_RUN_PATH; fi; \ XCFLAGS= XINCLUDE= XLDFLAGS= XLIBDIRS= XLIBS= \ PSI_FEATURE_DEVS= FEATURE_DEVS= DEVICE_DEVS= DEVICE_DEVS1= DEVICE_DEVS2= DEVICE_DEVS3= \ DEVICE_DEVS4= DEVICE_DEVS5= DEVICE_DEVS6= DEVICE_DEVS7= DEVICE_DEVS8= \ DEVICE_DEVS9= DEVICE_DEVS10= DEVICE_DEVS11= DEVICE_DEVS12= \ DEVICE_DEVS13= DEVICE_DEVS14= DEVICE_DEVS15= DEVICE_DEVS16= \ DEVICE_DEVS17= DEVICE_DEVS18= DEVICE_DEVS19= DEVICE_DEVS20= \ DEVICE_DEVS_EXTRA= \ /bin/sh <./soobj/ldt.tr /usr/bin/ld: /usr/lib/gcc/hppa-linux-gnu/5/../../../hppa-linux-gnu/libpng.a(libpng12_la-png.o): relocation R_PARISC_DPREL21L can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/hppa-linux-gnu/5/../../../hppa-linux-gnu/libpng.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status base/unixlink.mak:63: recipe for target 'sobin/libgs.so.9.18' failed For full log, see: https://buildd.debian.org/status/fetch.php?pkg=ghostscript=hppa=9.18%7Edfsg-4=1455706435 Regards, Dave Anglin -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 3.18.26+ (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_CA.utf8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages ghostscript depends on: ii debconf [debconf-2.0] 1.5.58 ii libc6 2.21-9 ii libgs9 9.18~dfsg-3 Versions of packages ghostscript recommends: ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2 Versions of packages ghostscript suggests: ii ghostscript-x 9.18~dfsg-3 -- no debconf information --- End Message --- --- Begin Message --- On Thu, 18 Feb 2016 20:18:51 -0500 John David Anglin wrote: > Package: ghostscript > Version: 9.18~dfsg-3 > Severity: normal > > Dear Maintainer, > > On several arches, the following or a similar error occurs building 9.18~dfsg-4: This has since been fixed. Version 10.02.1 is building on all architectures. signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#704682: marked as done (ghostscript: fails to print on HP PhotoSmart C5280)
Your message dated Sun, 07 Jan 2024 21:29:51 -0600 with message-id <16721615.geO5KgaWL5@riemann> and subject line Re: ghostscript: fails to print on HP PhotoSmart C5280 has caused the Debian Bug report #704682, regarding ghostscript: fails to print on HP PhotoSmart C5280 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.) -- 704682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Subject: ghostscript: fails to print on HP PhotoSmart C5280 Package: ghostscript Version: 9.05~dfsg-6.3 Justification: renders package unusable Severity: grave Dear Maintainer, I have tried to print many times but the printer never starts printing. However it works very well with: - ghostcript 8.71~dfsg2-9+squeeze - libgs8 8.71~dfsg2-9+squeeze1 Here is the /var/log/cups/error_log: W [04/Apr/2013:15:23:03 +0200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. E [04/Apr/2013:15:23:03 +0200] Filter "hpgltops" not found. E [04/Apr/2013:15:23:03 +0200] Filter "pstoraster" not found. E [04/Apr/2013:15:23:03 +0200] Filter "oopstops" not found. W [04/Apr/2013:15:23:03 +0200] failed to CreateProfile: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files W [04/Apr/2013:15:23:03 +0200] failed to CreateProfile: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files W [04/Apr/2013:15:23:03 +0200] failed to CreateDevice: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files W [04/Apr/2013:15:23:04 +0200] failed to CreateProfile: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files W [04/Apr/2013:15:23:04 +0200] failed to CreateProfile: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files W [04/Apr/2013:15:23:04 +0200] failed to CreateDevice: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files W [04/Apr/2013:15:23:04 +0200] failed to CreateProfile: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files W [04/Apr/2013:15:23:04 +0200] failed to CreateProfile: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files W [04/Apr/2013:15:23:04 +0200] failed to CreateDevice: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files E [04/Apr/2013:15:23:13 +0200] [Job 56] May not be a PDF file (continuing anyway) E [04/Apr/2013:15:23:13 +0200] [Job 56] PDF file is damaged - attempting to reconstruct xref table... E [04/Apr/2013:15:23:13 +0200] [Job 56] Couldn't find trailer dictionary E [04/Apr/2013:15:23:13 +0200] [Job 56] Couldn't read xref table E [04/Apr/2013:15:23:13 +0200] [Job 56] Can't detect file type E [04/Apr/2013:15:23:13 +0200] [Job 56] Job stopped due to filter errors; please consult the error_log file for details. D [04/Apr/2013:15:23:13 +0200] [Job 56] The following messages were recorded from 15:23:12 to 15:23:13 D [04/Apr/2013:15:23:13 +0200] [Job 56] Adding start banner page "none". D [04/Apr/2013:15:23:13 +0200] [Job 56] Queued on "Photosmart_C5200" by "root". D [04/Apr/2013:15:23:13 +0200] [Job 56] Auto-typing file... D [04/Apr/2013:15:23:13 +0200] [Job 56] Request file type is application/postscript. D [04/Apr/2013:15:23:13 +0200] [Job 56] File of type application/postscript queued by "root". D [04/Apr/2013:15:23:13 +0200] [Job 56] Adding end banner page "none". D [04/Apr/2013:15:23:13 +0200] [Job 56] job-sheets=none,none D [04/Apr/2013:15:23:13 +0200] [Job 56] argv[0]="Photosmart_C5200" D [04/Apr/2013:15:23:13 +0200] [Job 56] argv[1]="56" D [04/Apr/2013:15:23:13 +0200] [Job 56] argv[2]="root" D [04/Apr/2013:15:23:13 +0200] [Job 56] argv[3]="tmpOsWU1n" D [04/Apr/2013:15:23:13 +0200] [Job 56] argv[4]="1" D [04/Apr/2013:15:23:13 +0200] [Job 56] argv[5]="finishings=3 number-up=1 job-uuid=urn:uuid:ea36f717-b507-3c4a-6fcf-a48267c22481 job-originating-host-name=localhost time-at-creation=1365081792 tim
Processed: forcibly merging 790562 810080
Processing commands for cont...@bugs.debian.org: > forcemerge 790562 810080 Bug #790562 [ghostscript] Ghostscript: File has unbalanced q/Q operators (too many Q's) Bug #810080 [ghostscript] ghostscript: Infinite loop filling server logs with "File has unbalanced q/Q operators" Set Bug forwarded-to-address to 'https://bugs.ghostscript.com/show_bug.cgi?id=694310'. Severity set to 'normal' from 'important' Marked as found in versions ghostscript/9.06~dfsg-2. Bug #790562 [ghostscript] Ghostscript: File has unbalanced q/Q operators (too many Q's) Marked as found in versions ghostscript/9.06~dfsg-2+deb8u1. Merged 790562 810080 > thanks Stopping processing here. Please contact me if you need assistance. -- 790562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790562 810080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 790562 is forwarded to https://bugs.ghostscript.com/show_bug.cgi?id=694310
Processing commands for cont...@bugs.debian.org: > forwarded 790562 https://bugs.ghostscript.com/show_bug.cgi?id=694310 Bug #790562 [ghostscript] Ghostscript: File has unbalanced q/Q operators (too many Q's) Set Bug forwarded-to-address to 'https://bugs.ghostscript.com/show_bug.cgi?id=694310'. > thanks Stopping processing here. Please contact me if you need assistance. -- 790562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#789504: marked as done (ghostscript: segfault in pdfwrite)
Your message dated Sun, 07 Jan 2024 22:21:00 -0600 with message-id <5990381.alqRGMn8q6@riemann> and subject line Re: ghostscript: segfault in pdfwrite has caused the Debian Bug report #789504, regarding ghostscript: segfault in pdfwrite 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.) -- 789504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789504 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.06~dfsg-2 Severity: normal Dear Maintainer, segfault. gs loaded with valgrind: > % valgrind gs -sDEVICE=pdfwrite -dNOPAUSE -dBATCH -o alg.pdf alg_geoI.pdf > ==20217== Memcheck, a memory error detector > ==20217== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. > ==20217== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info > ==20217== Command: gs -sDEVICE=pdfwrite -dNOPAUSE -dBATCH -o alg.pdf > alg_geoI.pdf > ==20217== > GPL Ghostscript 9.06 (2012-08-08) > Copyright (C) 2012 Artifex Software, Inc. All rights reserved. > This software comes with NO WARRANTY: see the file PUBLIC for details. > ==20217== Conditional jump or move depends on uninitialised value(s) > ==20217==at 0x4FE04D7: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FE0C96: gs_gc_reclaim (in /usr/lib/libgs.so.9.06) > ==20217==by 0x504FE92: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FAED2F: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FAA8E2: interp_reclaim (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FABC6B: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FAC84A: gs_interpret (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA1CF7: gs_main_run_string_end (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA3168: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA32ED: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA487A: gs_main_init_with_args (in /usr/lib/libgs.so.9.06) > ==20217==by 0x400A0E: main (in /usr/bin/gs) > ==20217== > ==20217== Conditional jump or move depends on uninitialised value(s) > ==20217==at 0x4FE0D6B: gs_gc_reclaim (in /usr/lib/libgs.so.9.06) > ==20217==by 0x504FE92: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FAED2F: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FAA8E2: interp_reclaim (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FABC6B: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FAC84A: gs_interpret (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA1CF7: gs_main_run_string_end (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA3168: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA32ED: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA487A: gs_main_init_with_args (in /usr/lib/libgs.so.9.06) > ==20217==by 0x400A0E: main (in /usr/bin/gs) > ==20217== > ==20217== Conditional jump or move depends on uninitialised value(s) > ==20217==at 0x4FE0D70: gs_gc_reclaim (in /usr/lib/libgs.so.9.06) > ==20217==by 0x504FE92: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FAED2F: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FAA8E2: interp_reclaim (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FABC6B: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FAC84A: gs_interpret (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA1CF7: gs_main_run_string_end (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA3168: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA32ED: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA487A: gs_main_init_with_args (in /usr/lib/libgs.so.9.06) > ==20217==by 0x400A0E: main (in /usr/bin/gs) > ==20217== > ==20217== Conditional jump or move depends on uninitialised value(s) > ==20217==at 0x4FE04D7: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FE0DB9: gs_gc_reclaim (in /usr/lib/libgs.so.9.06) > ==20217==by 0x504FE92: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FAED2F: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FAA8E2: interp_reclaim (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FABC6B: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FAC84A: gs_interpret (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA1CF7: gs_main_run_string_end (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA3168: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA32ED: ??? (in /usr/lib/libgs.so.9.06) > ==20217==by 0x4FA487A: gs_main_init_with_args (in /usr/lib/libgs.so.9.06) &g
Bug#734398: marked as done (Update Suggests for obsolete transitional package hpijs)
Your message dated Sun, 07 Jan 2024 21:51:14 -0600 with message-id <1926552.6tgchFWduM@riemann> and subject line Re: Update Suggests for obsolete transitional package hpijs has caused the Debian Bug report #734398, regarding Update Suggests for obsolete transitional package hpijs 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.) -- 734398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.05~dfsg-8+b1 Severity: normal The hpijs package has been superseded by printer-driver-hpijs and is now a transitional package which simply depends on printer-driver-hpijs. The ghostscript package should be updated accordingly and suggest printer-driver-hpijs instead of hpijs. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ghostscript depends on: ii debconf [debconf-2.0] 1.5.52 ii gsfonts1:8.11+urwcyr1.0.7~pre44-4.2 ii libc6 2.17-97 ii libgs9 9.05~dfsg-8+b1 ghostscript recommends no packages. Versions of packages ghostscript suggests: ii cups-filters [ghostscript-cups] 1.0.43-1 pn ghostscript-x ii hpijs3.13.4-1 -- no debconf information --- End Message --- --- Begin Message --- On Mon, 06 Jan 2014 21:46:40 +0100 Michael Biebl wrote: > Package: ghostscript > Version: 9.05~dfsg-8+b1 > Severity: normal > > The hpijs package has been superseded by printer-driver-hpijs and is now > a transitional package which simply depends on printer-driver-hpijs. > > The ghostscript package should be updated accordingly and suggest > printer-driver-hpijs instead of hpijs. > Versions of packages ghostscript suggests: > ii cups-filters [ghostscript-cups] 1.0.43-1 > pn ghostscript-x > ii hpijs3.13.4-1 This change must have been made. Current package has no Suggests dependences at all. -Steve signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#699550: marked as done (Problems printing with Epson EPL-5800 (eplaser))
Your message dated Sun, 07 Jan 2024 21:19:56 -0600 with message-id <3243715.AJdgDx1Vlc@riemann> and subject line Re: Problems printing with Epson EPL-5800 (eplaser) has caused the Debian Bug report #699550, regarding Problems printing with Epson EPL-5800 (eplaser) 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.) -- 699550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 9.05~dfsg-6.3 After a fresh install of current (beta) Debian 7 wheezy I found that my Epson EPL-5800 printer works strangely: After it is switched on by the power-button it accepts the jobs from the PC well and the result is OK. However, the next job is screwed up and a couple of lines appear on the paper - the first line starts with the following: @EJL JI USER="" MACHINE="" DOCUMENT="" It seems thus that the printer is somehow not properly resetted after the first job and it expects plain text whereas the ghostscript driver send esc/Page language. Previously I used this printer on the Fedora linux distros up to Fedora 14 and it didn't have this problem. Now, i'm using ghostscript 9.05~dfsg-6.3 with cups 1.5.3-2.13. The printer is connected over USB (uname -a: Linux dalet 3.2.0-4-686-pae #1 SMP Debian 3.2.35-2 i686 GNU/Linux) on a server and used by one linux and one windows client - the problem exists with both. Thank You! Petr Tomasek --- End Message --- --- Begin Message --- On Fri, 1 Feb 2013 16:54:53 +0100 Petr Tomasek wrote: I do apologise that no action was taken for this report. >From the description, it is unclear to me whether the issue lies with ghostscript, cups, or some other component. Since this report is nearly 11 years old, I'm closing it. If you still have an issue, please open a report that contains a sample file and a command line that demonstrates the bug. > > Package: ghostscript > Version: 9.05~dfsg-6.3 > > After a fresh install of current (beta) Debian 7 wheezy I found > that my Epson EPL-5800 printer works strangely: After it is switched on > by the power-button it accepts the jobs from the PC well and the > result is OK. However, the next job is screwed up and a couple > of lines appear on the paper - the first line starts with the following: > > @EJL JI USER="" MACHINE="" DOCUMENT="" > > It seems thus that the printer is somehow not properly resetted > after the first job and it expects plain text whereas the > ghostscript driver send esc/Page language. > > Previously I used this printer on the Fedora linux distros up to > Fedora 14 and it didn't have this problem. > > Now, i'm using ghostscript 9.05~dfsg-6.3 with cups 1.5.3-2.13. The printer is > connected over USB (uname -a: > Linux dalet 3.2.0-4-686-pae #1 SMP Debian 3.2.35-2 i686 GNU/Linux) on a server > and used by one linux and one windows client - the problem exists with both. > > Thank You! > Petr Tomasek > > > signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#694371: marked as done (ghostscript: \CropBox on A3 paper- result unreadable to xpdf and evince)
Your message dated Sun, 07 Jan 2024 21:14:52 -0600
with message-id <2103227.KlZ2vcFHjT@riemann>
and subject line Re: ghostscript: \CropBox on A3 paper- result unreadable to
xpdf and evince
has caused the Debian Bug report #694371,
regarding ghostscript: \CropBox on A3 paper- result unreadable to xpdf and
evince
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.)
--
694371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghostscript
Version: 8.71~dfsg2-9
Severity: normal
The following LaTeX document initially displays fine with evince and
xpdf, but after cropping it the resulting file is unusable.
Example:
==[latex_a3_paper.tex]%<-
\documentclass[12pt]{minimal}
\usepackage[a3paper,left=1in,right=1in,top=1in,bottom=1in]{geometry}
\begin{document}
\newsavebox{\sometxt}
\sbox{\sometxt}{\begin{tabular}{@{}l@{}}
One line of text.\\
Another line of text.
\end{tabular}}
\newcommand{\row}{\usebox{\sometxt}\hfill\usebox{\sometxt}\\[5mm]}
\row\row\row\row\row\row
\fbox{Crop Me!!\row}
\row\row\row\row\row\row
\begin{verbatim}
pdflatex latex_a3_paper.tex
gs -sDEVICE=pdfwrite -o latex_a3_paper_cropped.pdf -c "[/CropBox [65 850 303
890] /PAGES pdfmark" -f latex_a3_paper.pdf
\end{verbatim}
\end{document}
%<-
To follow this example, save the text above to a file
"latex_a3_paper.tex". Then run:
pdflatex latex_a3_paper.tex
then:
gs -sDEVICE=pdfwrite -o latex_a3_paper_cropped.pdf -c "[/CropBox [65 850 303
890] /PAGES pdfmark" -f latex_a3_paper.pdf
then:
evince latex_a3_paper_cropped.pdf
xpdf latex_a3_paper_cropped.pdf
To see latex_a3_paper_cropped.pdf render properly, open it with "gv"
or "emacs".
-- System Information:
Debian Release: 6.0.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ghostscript depends on:
ii debconf [de 1.5.36.1 Debian configuration management sy
ii debianutils 3.4 Miscellaneous utilities specific t
ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2 Fonts for the Ghostscript interpre
ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib
ii libgs8 8.71~dfsg2-9 The Ghostscript PostScript/PDF int
ghostscript recommends no packages.
ghostscript suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 25 Nov 2012 22:16:13 +0100 (CET) Nomen Nescio
wrote:
> evince latex_a3_paper_cropped.pdf
>
> xpdf latex_a3_paper_cropped.pdf
>
> To see latex_a3_paper_cropped.pdf render properly, open it with "gv"
> or "emacs".
I tested using ghostscript 10.02.1 and the display with "evince" is the same
as with "gv".
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
Bug#940127: marked as done (gs segfaults in c2esp filter chain)
Your message dated Fri, 05 Jan 2024 23:50:04 -0600 with message-id <2185930.Icojqenx9y@riemann> and subject line Re: ghostscript makes c2esp autopkgtest timeout has caused the Debian Bug report #940127, regarding gs segfaults in c2esp filter chain 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.) -- 940127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghostscript, c2esp Control: found -1 ghostscript/9.28~~rc2~dfsg-1 Control: found -1 c2esp/27-4 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update timeout Dear maintainers, With a recent upload of ghostscript the autopkgtest of c2esp timeouts [1] in testing when that autopkgtest is run with the binary packages of ghostscript from unstable. It passes when run with only packages from testing. In tabular form: passfail ghostscriptfrom testing9.28~~rc2~dfsg-1 c2esp from testing27-4 all others from testingfrom testing The autopkgtest of c2esp also times out in unstable since the upload of ghostscript. 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? Paul [1] https://ci.debian.net/data/autopkgtest/testing/amd64/c/c2esp/2944626/log.gz signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On Thu, 12 Sep 2019 19:27:46 +0200 Paul Gevers wrote: > Source: ghostscript, c2esp > Control: found -1 ghostscript/9.28~~rc2~dfsg-1 > Control: found -1 c2esp/27-4 > Severity: serious > Tags: sid bullseye > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: breaks needs-update timeout > > Dear maintainers, > > With a recent upload of ghostscript the autopkgtest of c2esp timeouts > [1] in testing when that autopkgtest is run with the binary packages of > ghostscript from unstable. It passes when run with only packages from > testing. In tabular form: >passfail > ghostscriptfrom testing9.28~~rc2~dfsg-1 > c2esp from testing27-4 > all others from testingfrom testing > > The autopkgtest of c2esp also times out in unstable since the upload of > ghostscript. > > 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? > > Paul > > [1] > https://ci.debian.net/data/autopkgtest/testing/amd64/c/c2esp/2944626/log.gz > The referenced log file is long since expired, but current CI runs of c2esp do all pass -- suggesting the issue has been fixed. c2esp unstabletesting stable oldstable amd6427-11 pass 27-11 pass 27-11 pass 27-8 pass arm6427-11 pass 27-11 pass 27-11 pass 27-8 pass armel27-11 pass 27-11 pass 27-11 pass 27-8 pass armhf27-11 pass 27-11 pass 27-11 pass 27-4 pass i386 27-11 pass 27-11 pass 27-11 pass 27-4 pass ppc64el 27-11 pass 27-11 pass 27-11 pass 27-8 pass riscv64 27-11 pass No test dataNo test dataNo test data s390x27-11 pass 27-11 pass 27-11 pass 27-8 pass -Steve signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#613580: marked as done (libgs9: please Recommends: (not Depends:) gs-cjk-resource)
Your message dated Thu, 04 Jan 2024 22:24:30 -0600 with message-id <1972976.eGJsNajkDb@riemann> and subject line Re: libgs9: please Recommends: (not Depends:) gs-cjk-resource has caused the Debian Bug report #613580, regarding libgs9: please Recommends: (not Depends:) gs-cjk-resource 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.) -- 613580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgs9 Version: 9.00~dfsg-3 Severity: normal Hi there! What is the rationale for the dependency on gs-cjk-resource? The description for the latter reads: --8<---cut here---start->8--- Description: Resource files for gs-cjk, ghostscript CJK-TrueType extension This package contains several resource files (actually Adobe CMaps) to use CJK TrueType fonts with gs. . gs-cjk enables ghostscript to handle CJK TrueType fonts through CID-keyed font technology. In addition to this package, a language-specific CMap package (named cmap-adobe-*) and a TrueType font package (ttf-*) is needed. . Japanese: needs cmap-adobe-japan1 and ttf-kochi-mincho | ttf-kochi-gothic. Korean: needs cmap-adobe-korea1 and ttf-unfonts-core. Traditional-Chinese: needs cmap-adobe-cns1 and ttf-arphic-ukai | ttf-arphic-uming. Simplified-Chinese: needs cmap-adobe-gb1 and ttf-arphic-ukai | ttf-arphic-uming. --8<---cut here---end--->8--- I do not nothing about CJK and I do not write anything in Japanese, Korean or Chinese. Which also means that I have installed none of the cmap-adobe-* packages. This seems to me an example where you want Recommends: instead of Depends:, as I explained (without success) on #604926: <http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=yes=604926#44> Thx, bye, Gismo / Luca PS1, I reported the bug to the version which introduced the dependency (9.00~dfsg-3), different from the one installed (9.01~dfsg-1). PS2, gs-cjk-resource needs two packages to be fully functional: cmap-adobe-* and ttf-*, but only the former are listed as Recommends:, with the latter being only as Suggests:, which is IMHO a bug, both should be at the same level, according to the Description:... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgs9 depends on: ii gs-cjk-resource 1.20100103-2 Resource files for gs-cjk, ghostsc ii libc6 2.11.2-11Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-2common error description library ii libcups21.4.5-3 Common UNIX Printing System(tm) - ii libcupsimage2 1.4.5-3 Common UNIX Printing System(tm) - ii libfontconfig1 2.8.0-2.1generic font configuration library ii libgcrypt11 1.4.6-5 LGPL Crypto library - runtime libr ii libgnutls26 2.10.4-2 the GNU TLS library - runtime libr ii libgs9-common 9.01~dfsg-1 interpreter for the PostScript lan ii libgssapi-krb5-21.8.3+dfsg-4 MIT Kerberos runtime libraries - k ii libidn111.18-1 GNU Libidn library, implementation ii libijs-0.35 0.35-7 IJS raster image transport protoco ii libjasper1 1.900.1-7+b1 The JasPer JPEG-2000 runtime libra ii libjbig2dec00.11-1 JBIG2 decoder library - shared lib ii libjpeg62 6b1-1The Independent JPEG Group's JPEG ii libk5crypto31.8.3+dfsg-4 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-4 MIT Kerberos runtime libraries ii liblcms11.18.dfsg-1.2+b3 Color management library ii libpaper1 1.1.24 library for handling paper charact ii libpng12-0 1.2.44-1 PNG library - runtime ii libstdc++6 4.4.5-10 The GNU Standard C++ Library v3 ii libtiff43.9.4-5 Tag Image File Format (TIFF) libra ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime libgs9 recommends no packages. libgs9 suggests no packages. -- no debconf information pgpJMvhwcP2ha.pgp Description: PGP s
Bug#1056724: marked as done (libsane-hpaio: Move files into /usr (incl. DEP17 P7 mitigation))
Your message dated Sun, 10 Dec 2023 11:42:40 + with message-id and subject line Bug#1056724: fixed in hplip 3.22.10+dfsg0-4 has caused the Debian Bug report #1056724, regarding libsane-hpaio: Move files into /usr (incl. DEP17 P7 mitigation) 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.) -- 1056724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsane-hpaio Version: 3.22.10+dfsg0-3 Severity: important Tags: patch User: helm...@debian.org Usertags: dep17p7 X-Debbugs-Cc: helm...@debian.org Dear Maintainer, libsane-hpaio contains udev rules which are installed to /lib; these files need to be moved to /usr/lib as part of Debian's usr-merge effort. Because libsane-hpaio is Multi-Arch: same, an unfortunate corner-case can occur whereby shared files (such as the udev rules) may be erroneously removed on upgrades (please see DEP17[1] P7: Shared multiarch file loss). You will find a patch attached to move the udev files, including the mitigation for the file loss scenario. Alternatively, you can also use the salsa merge request I've opened[2]. Please consider applying this patch at your earliest convenience. This bug will be upgraded to release critical soon, as it blocks the overall usr-merge effort which is being undertaken for the trixie release. Many thanks, Chris 1. https://subdivi.de/~helmut/dep17.html 2. https://salsa.debian.org/printing-team/hplip.v2/-/merge_requests/3 --- End Message --- --- Begin Message --- Source: hplip Source-Version: 3.22.10+dfsg0-4 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of hplip, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated hplip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 10 Dec 2023 10:39:02 +0100 Source: hplip Architecture: source Version: 3.22.10+dfsg0-4 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Thorsten Alteholz Closes: 1056724 Changes: hplip (3.22.10+dfsg0-4) unstable; urgency=medium . * libsane-hpaio: move 56-hpmud.rules to /usr. Includes protective diversion against m-a: same file loss on upgrades. Diversion can be removed in forky+1. (Closes: #1056724) (thanks a lot to Christian Hofstaedtler for the patch) Checksums-Sha1: 13cc2dfb884f580d0a149a36bdc8bc9e8c550e19 3216 hplip_3.22.10+dfsg0-4.dsc a96da35d675a42f22b8a9c850d4560576d450088 140568 hplip_3.22.10+dfsg0-4.debian.tar.xz 2746ff7ecece08319ec57b8cd4ffe98d53f3e383 19675 hplip_3.22.10+dfsg0-4_amd64.buildinfo Checksums-Sha256: bc7d345cd955057de8fd649ada067be600163ac70e1c067486800dcc12870021 3216 hplip_3.22.10+dfsg0-4.dsc a042ea4b5d0e012caab7621bb0d0615a7ae15396a369f2104030aa7e70061af0 140568 hplip_3.22.10+dfsg0-4.debian.tar.xz edc2c1ae0c410c443185fd04050ded3544b3de6feeb9b6b615124806e1b4e967 19675 hplip_3.22.10+dfsg0-4_amd64.buildinfo Files: 4201f372e9f03d65324c193a67c410f7 3216 utils optional hplip_3.22.10+dfsg0-4.dsc d1018857d4703a9efd4b0142c0d3fd03 140568 utils optional hplip_3.22.10+dfsg0-4.debian.tar.xz d9ce6f58b24e0712e34beaa7fbab91d9 19675 utils optional hplip_3.22.10+dfsg0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmV1k+pfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYR90XD/0WrkzCJi/lilhWPV2tG9xqUfA4STNz I9X8oftCdUcD6QmuGchkYyHhj5KHpsy5V7F4g/7mMBFyRRolZr+XtDhAGU3GH9bM 42TMOdkawPoOGck2/jwr45sy9Q3KXaa/KBfV/j9ZYZjxmr7F6Ir+KlcHazAAIUd2 gyFpNtLLNRT0MRmFxMo2wJAVJVrZ36UmpwUbKk4HeRsi7R1qT5q6FEdSm7kKjurK b9qmIoVdUW5TbZT1LubROg/lJeMZY7ph6sZlnr4f8e1XsLLiN9BidjlzjxwH0LmK O7h5aoZrYClIOJEb1iZq6ZEmK0le/OK9OxV/Y542A/rWff8TTm4UIAVOiNAqYBy1 ubUuP6C2HiihyxbJkowlKEdmhkcfSCcxOUw6E5m9g7hDjbSCOOrVD3YHZy1vYOfH z8FsiY9T+fuwc+ijjeRGW2Nfs1SlQhqu8zSpVmunbB/nkc3Fq2nLbrawMSfql/ER LTVlDKIqnPNnETZfiIcccBHofo2ySWfe2jk971HB1RyHoLEXYhPbSyeAzDUWuENm
Processed: Re: Bug#1056724: hplip: diff for NMU version 3.22.10+dfsg0-3.1
Processing control commands: > tags -1 - pending Bug #1056724 [libsane-hpaio] libsane-hpaio: Move files into /usr (incl. DEP17 P7 mitigation) Removed tag(s) pending. -- 1056724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 1056925 in libxtrxll/0.0.1+git20201202.1b6eddf-1.1~exp1, notfound 1056911 in 1:0.5.3-3 ...
Processing commands for cont...@bugs.debian.org: > fixed 1056925 libxtrxll/0.0.1+git20201202.1b6eddf-1.1~exp1 Bug #1056925 [libxtrxll0] libxtrxl0: Move files into /usr (incl. DEP17 P7 mitigation) Marked as fixed in versions libxtrxll/0.0.1+git20201202.1b6eddf-1.1~exp1. > notfound 1056911 1:0.5.3-3 Bug #1056911 [libfreenect0.5] libfreenect0.5: Move files into /usr (incl. DEP17 P7 mitigation) Ignoring request to alter found versions of bug #1056911 to the same values previously set > found 1056911 libfreenect0.5/1:0.5.3-3.1 Bug #1056911 [libfreenect0.5] libfreenect0.5: Move files into /usr (incl. DEP17 P7 mitigation) The source libfreenect0.5 and version 1:0.5.3-3.1 do not appear to match any binary packages Marked as found in versions libfreenect0.5/1:0.5.3-3.1. > fixed 1056911 libfreenect0.5/1:0.5.3-3.1~exp1 Bug #1056911 [libfreenect0.5] libfreenect0.5: Move files into /usr (incl. DEP17 P7 mitigation) The source libfreenect0.5 and version 1:0.5.3-3.1~exp1 do not appear to match any binary packages Marked as fixed in versions libfreenect0.5/1:0.5.3-3.1~exp1. > fixed 1056724 hplip/3.22.10+dfsg0-3.1~exp1 Bug #1056724 [libsane-hpaio] libsane-hpaio: Move files into /usr (incl. DEP17 P7 mitigation) Marked as fixed in versions hplip/3.22.10+dfsg0-3.1~exp1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056724 1056911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056911 1056925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1056724
Processing commands for cont...@bugs.debian.org: > tags 1056724 + pending Bug #1056724 [libsane-hpaio] libsane-hpaio: Move files into /usr (incl. DEP17 P7 mitigation) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: jbig2dec: CVE-2023-46361
Processing control commands: > tags -1 patch Bug #1055387 [src:jbig2dec] jbig2dec: CVE-2023-46361 Added tag(s) patch. -- 1055387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopen for unstable
Processing control commands:
> reopen -1
Bug #1056724 {Done: Chris Hofstaedtler } [libsane-hpaio]
libsane-hpaio: Move files into /usr (incl. DEP17 P7 mitigation)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions hplip/3.22.10+dfsg0-3.1~exp1.
--
1056724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1056724: marked as done (libsane-hpaio: Move files into /usr (incl. DEP17 P7 mitigation))
Your message dated Sun, 03 Dec 2023 15:12:39 + with message-id and subject line Bug#1056724: fixed in hplip 3.22.10+dfsg0-3.1~exp1 has caused the Debian Bug report #1056724, regarding libsane-hpaio: Move files into /usr (incl. DEP17 P7 mitigation) 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.) -- 1056724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsane-hpaio Version: 3.22.10+dfsg0-3 Severity: important Tags: patch User: helm...@debian.org Usertags: dep17p7 X-Debbugs-Cc: helm...@debian.org Dear Maintainer, libsane-hpaio contains udev rules which are installed to /lib; these files need to be moved to /usr/lib as part of Debian's usr-merge effort. Because libsane-hpaio is Multi-Arch: same, an unfortunate corner-case can occur whereby shared files (such as the udev rules) may be erroneously removed on upgrades (please see DEP17[1] P7: Shared multiarch file loss). You will find a patch attached to move the udev files, including the mitigation for the file loss scenario. Alternatively, you can also use the salsa merge request I've opened[2]. Please consider applying this patch at your earliest convenience. This bug will be upgraded to release critical soon, as it blocks the overall usr-merge effort which is being undertaken for the trixie release. Many thanks, Chris 1. https://subdivi.de/~helmut/dep17.html 2. https://salsa.debian.org/printing-team/hplip.v2/-/merge_requests/3 --- End Message --- --- Begin Message --- Source: hplip Source-Version: 3.22.10+dfsg0-3.1~exp1 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of hplip, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated hplip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 03 Dec 2023 15:25:26 +0100 Source: hplip Architecture: source Version: 3.22.10+dfsg0-3.1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Printing Team Changed-By: Chris Hofstaedtler Closes: 1056724 Changes: hplip (3.22.10+dfsg0-3.1~exp1) experimental; urgency=medium . * Non-maintainer upload. * libsane-hpaio: move 56-hpmud.rules to /usr. Includes protective diversion against m-a: same file loss on upgrades. Diversion can be removed in forky+1. (Closes: #1056724) Checksums-Sha1: 45a5aa77dbfe440e6aa8a8dbf4ad8442b654ce49 3085 hplip_3.22.10+dfsg0-3.1~exp1.dsc e540f06cc0137f12e81ef04e020f5bfd2758f763 140532 hplip_3.22.10+dfsg0-3.1~exp1.debian.tar.xz 1ab91f242bf8de35bf390a34580cd1f327397459 19775 hplip_3.22.10+dfsg0-3.1~exp1_arm64.buildinfo Checksums-Sha256: b14e7fcfdbc1d70d68bf9180e3ae8f46827b928b61818a1208fae7389433dadd 3085 hplip_3.22.10+dfsg0-3.1~exp1.dsc 54f709ba1368a87f86db78e1ee281c58b403603db9a2025181dbff4acd157b08 140532 hplip_3.22.10+dfsg0-3.1~exp1.debian.tar.xz 525294526a6b10941053fe78590592bdd4a6a222ea10d9e90b677981adb95088 19775 hplip_3.22.10+dfsg0-3.1~exp1_arm64.buildinfo Files: f316dde536abf50bcbd26c249a9e6e93 3085 utils optional hplip_3.22.10+dfsg0-3.1~exp1.dsc f2a8b92e693b3fad617252fdff291e32 140532 utils optional hplip_3.22.10+dfsg0-3.1~exp1.debian.tar.xz b89162c241c0cf753c1c45e1095fe55a 19775 utils optional hplip_3.22.10+dfsg0-3.1~exp1_arm64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmVslCwACgkQXBPW25MF LgNfdQ/+PWTk/LEDmkcdBozmuA2RyKQtMierLi9qXd+LcDLHbdAawCZMHuQKxYXS BYNPZzpgOxD3W1KSVJrakraDnAUoYtMyF2V12kftwQqO5k/6Y+yLH851BCrHzW0p uAidkRgtVQNVmnnBdEVpALwybxo0+v24bEaA3d/VjpJ/urfRnRvj/7Nia1PuSl21 HythyCF8F2b9Ao5GdAzJeXJh+uuNAS6SgDC1i1bXhQh2RiuqStU0IU4OJMiEPHmf fk/WE/Yx8Px8F4zhXFOmUjLUu5wv3DlOf3h7TJ0uYam0QH3frykNogWUycqJ83GF pVqFfjGEq74vFLD4rm6FsFeIFGSxN3d6ilnRwuEMmOe3NwPQ2OoEQCMc4z++9Tu2 f/seMz/S/m2cp4FF4mb9jOU5MzuXF/WHskpgridNcL4WRuGRgrVQocix7MJtgtnc gcORhrurFwJwST40U+6jvIRRPW7xEA3RkMhVPG/wxM3ysyKshEx6BwxEX1S7oa+j ptCnGzouZxbxgB9rJTHDVrJkg9lNIHJFhEIBqRWRdr/Y8IEIP38WCYUZNgg2zCG2 3IjVK3DDXYM3e5c1BMCk1aS2DZzdg8prSlUrbItRoa68nilcFDp
Processed: hplip: diff for NMU version 3.22.10+dfsg0-3.1
Processing control commands: > tags 1056724 + pending Bug #1056724 [libsane-hpaio] libsane-hpaio: Move files into /usr (incl. DEP17 P7 mitigation) Added tag(s) pending. -- 1056724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056581: marked as done (cups-daemon: CUPS 2.4.2 forces monochrome printing when PPD is using ColorModel CMYK)
Your message dated Sun, 03 Dec 2023 12:32:09 + with message-id and subject line Bug#1056581: fixed in cups 2.4.2-3+deb12u5 has caused the Debian Bug report #1056581, regarding cups-daemon: CUPS 2.4.2 forces monochrome printing when PPD is using ColorModel CMYK 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.) -- 1056581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cups-daemon Version: 2.4.2-3+deb12u4 Severity: important Dear Maintainer, when using PPDs with setting ColorModel=CMYK, then cups will set print-color-mode to monochrome in printers.conf thus forcing all prints to be monochrome. This is a known bug and fixed https://github.com/OpenPrinting/cups/issues/401 https://github.com/OpenPrinting/cups/issues/421 https://github.com/OpenPrinting/cups/pull/500 Please update or patch the cups version in bookworm. Thanks! Christian *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-12-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages cups-daemon depends on: ii adduser3.134 ii bc 1.07.1-3+b1 ii init-system-helpers1.65.2 ii libavahi-client3 0.8-10 ii libavahi-common3 0.8-10 ii libc6 2.36-9+deb12u3 ii libcups2 2.4.2-3+deb12u4 ii libdbus-1-31.14.10-1~deb12u1 ii libgssapi-krb5-2 1.20.1-2+deb12u1 ii libpam0g 1.5.2-6+deb12u1 ii libpaper1 1.1.29 ii libsystemd0252.17-1~deb12u1 ii lsb-base 11.6 ii procps 2:4.0.2-3 ii ssl-cert 1.1.2 ii sysvinit-utils [lsb-base] 3.06-4 Versions of packages cups-daemon recommends: pn avahi-daemon pn colord pn cups-browsed pn ipp-usb Versions of packages cups-daemon suggests: ii cups 2.4.2-3+deb12u4 pn cups-bsd ii cups-client2.4.2-3+deb12u4 ii cups-common2.4.2-3+deb12u4 ii cups-filters 1.28.17-3 ii cups-ppdc 2.4.2-3+deb12u4 ii cups-server-common 2.4.2-3+deb12u4 pn foomatic-db-compressed-ppds | foomatic-db ii ghostscript10.0.0~dfsg-11+deb12u2 ii poppler-utils 22.12.0-2+b1 ii printer-driver-cups-pdf [cups-pdf] 3.0.1-14 pn smbclient ii udev 252.17-1~deb12u1 -- Configuration Files: /etc/cups/cups-files.conf changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Source: cups Source-Version: 2.4.2-3+deb12u5 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of cups, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated cups package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Dec 2023 20:35:27 +0100 Source: cups Architecture: source Version: 2.4.2-3+deb12u5 Distribution: bookworm Urgency: medium Maintainer: Debian Printing Team Changed-By: Thorsten Alteholz Closes: 1056581 Changes: cups (2.4.2-3+deb12u5) bookworm
Processed: [bts-link] source package src:jbig2dec
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:jbig2dec > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1055387 (http://bugs.debian.org/1055387) > # Bug title: jbig2dec: CVE-2023-46361 > # * https://bugs.ghostscript.com/show_bug.cgi?id=705041 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > forwarded 1055387 https://bugs.ghostscript.com/show_bug.cgi?id=707308, > merged-upstream: https://bugs.ghostscript.com/show_bug.cgi?id=705041 Bug #1055387 [src:jbig2dec] jbig2dec: CVE-2023-46361 Changed Bug forwarded-to-address to 'https://bugs.ghostscript.com/show_bug.cgi?id=707308, merged-upstream: https://bugs.ghostscript.com/show_bug.cgi?id=705041' from 'https://bugs.ghostscript.com/show_bug.cgi?id=707308'. > tags 1055387 + fixed-upstream Bug #1055387 [src:jbig2dec] jbig2dec: CVE-2023-46361 Added tag(s) fixed-upstream. > usertags 1055387 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. -- 1055387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
