Bug#1008175: #1008175
Brian:
PRINT_QUEUE_NAME is the actual name of the queue as given in Okular or
by 'lpstat -a'.
Sorry! Was out at a pub with a friend before responding! Should have
waited! ;^)
driverless
ipps://HP%20LaserJet%20Pro%20M148fdw%20(6CA573)._ipps._tcp.local/
As root:
lpadmin -p testq -v
"ipps://HP%20LaserJet%20Pro%20M148fdw%20(6CA573)._ipps._tcp.local/" -E
-m everywhere
as regular user:
lp -d testq -o sides=two-sided-long-edge lipsum.txt.pdf
Still printed single-sided
The printer was originally setup by the Debian netinst.
Thanks!
Rick
On 2022-03-27 17:01, Brian Potkin wrote:
On Sun 27 Mar 2022 at 15:13:30 -0500, r...@scotsgeek.com wrote:
Brian:
avahi-browse -rt _ipp._tcp
+ enp2s0 IPv6 HP LaserJet Pro M148fdw (6CA573) Internet
Printer
local
+ enp2s0 IPv4 HP LaserJet Pro M148fdw (6CA573) Internet
Printer
local
= enp2s0 IPv6 HP LaserJet Pro M148fdw (6CA573) Internet
Printer
local
hostname = [NPI6CA573.local]
address = [192.168.1.207]
port = [631]
txt = ["mopria-certified=1.3" "mac=f8:b4:6a:6c:a5:73" "usb_MDL=HP
LaserJet Pro M148f-M149f" "usb_MFG=HP" "TLS=1.2" "PaperMax=legal-A4"
"kind=document,envelope,photo"
"UUID=564e4733-5931-3235-3934-f8b46a6ca573"
"Fax=T" "Scan=T" "Duplex=T" "Color=F" "note=unitedStates"
"adminurl=http://NPI6CA573.local./hp/device/info_config_AirPrint.html?tab=Networking=AirPrintStatus;
The text record advertises that the printer is capable of automatic
duplex ("Duplex=T").
[Snipped text]
driverless
ipps://HP%20LaserJet%20Pro%20M148fdw%20(6CA573)._ipps._tcp.local/
ipp://... is a URI for the printer. We will try setting up and printing
to a new print queue. Do
lpadmin -p testq -v "URI" -E -m everywhere
Subdtitute URI with what is above. Test with
lp -d testq -o sides=two-sided-long-edge test.pdf
lpoptions -p PRINT_QUEUE_NAME -l
lpoptions: Unable to get PPD file for PRINT_QUEUE_NAME: No such file
or
directory
PRINT_QUEUE_NAME is the actual name of the queue as given in Okular or
by 'lpstat -a'.
Cheers,
Brian.
Bug#1008175: #1008175
On Sun 27 Mar 2022 at 15:13:30 -0500, r...@scotsgeek.com wrote:
> Brian:
>
> avahi-browse -rt _ipp._tcp
> + enp2s0 IPv6 HP LaserJet Pro M148fdw (6CA573) Internet Printer
> local
> + enp2s0 IPv4 HP LaserJet Pro M148fdw (6CA573) Internet Printer
> local
> = enp2s0 IPv6 HP LaserJet Pro M148fdw (6CA573) Internet Printer
> local
>hostname = [NPI6CA573.local]
>address = [192.168.1.207]
>port = [631]
>txt = ["mopria-certified=1.3" "mac=f8:b4:6a:6c:a5:73" "usb_MDL=HP
> LaserJet Pro M148f-M149f" "usb_MFG=HP" "TLS=1.2" "PaperMax=legal-A4"
> "kind=document,envelope,photo" "UUID=564e4733-5931-3235-3934-f8b46a6ca573"
> "Fax=T" "Scan=T" "Duplex=T" "Color=F" "note=unitedStates"
> "adminurl=http://NPI6CA573.local./hp/device/info_config_AirPrint.html?tab=Networking=AirPrintStatus;
The text record advertises that the printer is capable of automatic
duplex ("Duplex=T").
[Snipped text]
> driverless
> ipps://HP%20LaserJet%20Pro%20M148fdw%20(6CA573)._ipps._tcp.local/
ipp://... is a URI for the printer. We will try setting up and printing
to a new print queue. Do
lpadmin -p testq -v "URI" -E -m everywhere
Subdtitute URI with what is above. Test with
lp -d testq -o sides=two-sided-long-edge test.pdf
> lpoptions -p PRINT_QUEUE_NAME -l
> lpoptions: Unable to get PPD file for PRINT_QUEUE_NAME: No such file or
> directory
PRINT_QUEUE_NAME is the actual name of the queue as given in Okular or
by 'lpstat -a'.
Cheers,
Brian.
Bug#1008175: #1008175
Brian: avahi-browse -rt _ipp._tcp + enp2s0 IPv6 HP LaserJet Pro M148fdw (6CA573) Internet Printer local + enp2s0 IPv4 HP LaserJet Pro M148fdw (6CA573) Internet Printer local = enp2s0 IPv6 HP LaserJet Pro M148fdw (6CA573) Internet Printer local hostname = [NPI6CA573.local] address = [192.168.1.207] port = [631] txt = ["mopria-certified=1.3" "mac=f8:b4:6a:6c:a5:73" "usb_MDL=HP LaserJet Pro M148f-M149f" "usb_MFG=HP" "TLS=1.2" "PaperMax=legal-A4" "kind=document,envelope,photo" "UUID=564e4733-5931-3235-3934-f8b46a6ca573" "Fax=T" "Scan=T" "Duplex=T" "Color=F" "note=unitedStates" "adminurl=http://NPI6CA573.local./hp/device/info_config_AirPrint.html?tab=Networking=AirPrintStatus; "priority=10" "product=(HP LaserJet Pro M148f-M149f)" "ty=HP LaserJet Pro M148f-M149f" "URF=V1.4,CP99,W8,OB10,PQ3-4-5,DM1,IS1,MT1-3-5,RS600" "rfo=ipp/faxout" "rp=ipp/print" "pdl=image/urf,application/PCLm,application/octet-stream,application/pdf,application/postscript,application/vnd.hp-PCL,application/vnd.hp-PCLXL,image/jpeg" "qtotal=1" "txtvers=1"] = enp2s0 IPv4 HP LaserJet Pro M148fdw (6CA573) Internet Printer local hostname = [NPI6CA573.local] address = [192.168.1.207] port = [631] txt = ["mopria-certified=1.3" "mac=f8:b4:6a:6c:a5:73" "usb_MDL=HP LaserJet Pro M148f-M149f" "usb_MFG=HP" "TLS=1.2" "PaperMax=legal-A4" "kind=document,envelope,photo" "UUID=564e4733-5931-3235-3934-f8b46a6ca573" "Fax=T" "Scan=T" "Duplex=T" "Color=F" "note=unitedStates" "adminurl=http://NPI6CA573.local./hp/device/info_config_AirPrint.html?tab=Networking=AirPrintStatus; "priority=10" "product=(HP LaserJet Pro M148f-M149f)" "ty=HP LaserJet Pro M148f-M149f" "URF=V1.4,CP99,W8,OB10,PQ3-4-5,DM1,IS1,MT1-3-5,RS600" "rfo=ipp/faxout" "rp=ipp/print" "pdl=image/urf,application/PCLm,application/octet-stream,application/pdf,application/postscript,application/vnd.hp-PCL,application/vnd.hp-PCLXL,image/jpeg" "qtotal=1" "txtvers=1"] driverless ipps://HP%20LaserJet%20Pro%20M148fdw%20(6CA573)._ipps._tcp.local/ lpoptions -p PRINT_QUEUE_NAME -l lpoptions: Unable to get PPD file for PRINT_QUEUE_NAME: No such file or directory Thanks! Rick On 2022-03-27 12:49, Brian Potkin wrote: On Sun 27 Mar 2022 at 10:25:37 -0500, r...@scotsgeek.com wrote: The printer is"HP LaserJet Plus Pro M148fdw", connected by ethernet. I first created a .txt file, then converted it to a .ps file, then converted to a .pdf file. I then ran the following commands: lpr -o sides=two-sided-long-edge lipsum.txt.ps lp -o sides=two-sided-long-edge lipsum.txt.ps lpr -o sides=two-sided-long-edge lipsum.txt.pdf lp -o sides=two-sided-long-edge lipsum.txt.pdf All printed one-sided. Thanks for doing that. Then, as root, I ran the command cupsctl --debug-logging Then as regular user, I ran: lp -o sides=two-sided-long-edge lipsum.txt.pdf After many seconds, error reported: lp: Error - scheduler not responding. No output to the printer. Pass on this for the moment. My understanding is that there is no difference in what lp and lpr do. I then ran: lpr -o sides=two-sided-long-edge lipsum.txt.pdf It printed one-sided. This used to work correctly, then a few months ago, it stopped working. I had hoped it would have been corrected, but now I am reporting it. Please let me know if I can help in any other way. The error_log shows that two-sided-long-edge is sent to the printing system. See argv[5]. It should then be sent on to the printer. The printer supports two-sided-long-edge. But we have [Job 238] Unable to do two-sided printing, setting sides to \'one-sided\'. Now, where is that coming from and why? Investigating. Rick, you can help with more information. Please give what you get for avahi-browse -rt _ipp._tcp driverless lpoptions -p PRINT_QUEUE_NAME -l avahi-browse is in the avahi-utils package. Cheers, Brian.
Bug#1008175: #1008175
The log message "Unable to do two-sided printing" comes from the "ipp"
CUPS backend, part of CUPS. It seems that the backend does not find the
"sides" attribute in the printer's IPP attributes.
See the code here:
--
if (ipp_status == IPP_STATUS_OK_IGNORED_OR_SUBSTITUTED ||
ipp_status == IPP_STATUS
_OK_CONFLICTING)
{
/*
* One or more options are not supported...
*/
if (ippFindAttribute(response, "sides", IPP_TAG_ZERO))
{
/*
* The sides value is not supported, revert to one-sided as
needed...
*/
const char *sides = cupsGetOption("sides", num_options, options);
if (!sides || !strncmp(sides, "two-sided-", 10))
{
fputs("DEBUG: Unable to do two-sided printing, setting sides
to 'one-sided'.\n", stderr);
num_options = cupsAddOption("sides", "one-sided",
num_options, );
}
}
--
cups-filters 1.28.13 released!
Hi,
I have released cups-filters 1.28.13 now, with the following changes:
- pdftopdf: Fix N-up printing when paper is taken
long-edge-first by the printer.
- pdftopdf: Fix cropping ("print-scaling=none" and
"print-scaling=fill") when paper is taken long-edge-first by
the printer (Issue #454).
- pdftops: Use Poppler for all Apple LaserWriter models (Issue
#452).
Bug fix release, for correct printing on printers which take in the
paper long-edge-first and for Apple LaserWriter printers.
Please release this on Debian so that it can be synced into Ubuntu.
Thanks in advance.
Till
Bug#1008175: #1008175
On Sun 27 Mar 2022 at 10:25:37 -0500, r...@scotsgeek.com wrote: > The printer is"HP LaserJet Plus Pro M148fdw", connected by ethernet. > > I first created a .txt file, then converted it to a .ps file, then converted > to a .pdf file. I then ran the following commands: > lpr -o sides=two-sided-long-edge lipsum.txt.ps > lp -o sides=two-sided-long-edge lipsum.txt.ps > lpr -o sides=two-sided-long-edge lipsum.txt.pdf > lp -o sides=two-sided-long-edge lipsum.txt.pdf > > All printed one-sided. Thanks for doing that. > Then, as root, I ran the command > cupsctl --debug-logging > > Then as regular user, I ran: > lp -o sides=two-sided-long-edge lipsum.txt.pdf > > After many seconds, error reported: > lp: Error - scheduler not responding. > > No output to the printer. Pass on this for the moment. My understanding is that there is no difference in what lp and lpr do. > I then ran: > lpr -o sides=two-sided-long-edge lipsum.txt.pdf > > It printed one-sided. > > This used to work correctly, then a few months ago, it stopped working. I > had hoped it would have been corrected, but now I am reporting it. > > Please let me know if I can help in any other way. The error_log shows that two-sided-long-edge is sent to the printing system. See argv[5]. It should then be sent on to the printer. The printer supports two-sided-long-edge. But we have [Job 238] Unable to do two-sided printing, setting sides to \'one-sided\'. Now, where is that coming from and why? Investigating. Rick, you can help with more information. Please give what you get for avahi-browse -rt _ipp._tcp driverless lpoptions -p PRINT_QUEUE_NAME -l avahi-browse is in the avahi-utils package. Cheers, Brian.
Bug#1008175: #1008175
The printer is"HP LaserJet Plus Pro M148fdw", connected by ethernet. I first created a .txt file, then converted it to a .ps file, then converted to a .pdf file. I then ran the following commands: lpr -o sides=two-sided-long-edge lipsum.txt.ps lp -o sides=two-sided-long-edge lipsum.txt.ps lpr -o sides=two-sided-long-edge lipsum.txt.pdf lp -o sides=two-sided-long-edge lipsum.txt.pdf All printed one-sided. Then, as root, I ran the command cupsctl --debug-logging Then as regular user, I ran: lp -o sides=two-sided-long-edge lipsum.txt.pdf After many seconds, error reported: lp: Error - scheduler not responding. No output to the printer. I then ran: lpr -o sides=two-sided-long-edge lipsum.txt.pdf It printed one-sided. This used to work correctly, then a few months ago, it stopped working. I had hoped it would have been corrected, but now I am reporting it. Please let me know if I can help in any other way. Thank you! Rick On 2022-03-27 08:08, Brian Potkin wrote: tags 1008175 moreinfo thanks On Wed 23 Mar 2022 at 13:01:18 -0400, Rick Stanley wrote: Now neither option works correctly executing from the command line. "lpr -o sides=two-sided-long-edge test.pdf" "lpr -o sides=one-sided test.pdf" And same for lp. Thank you for your report, Rick. What is the printer make and model? The situation is that neither command gives double-sided printing? Printing from Okular works correctly as expected. There is a slight difference between your lp command and what Okular does. Okular sends a PostScript file to the ptinter. Not that I can see why that should make any difference, but printing from Evince or Firefox sens a PDF. You could try that. Anyway, let's have a log. Enable debug logging with cupsctl --debug-logging Empty error_log with >/var/log/cups/error_log Print and send error_log as an attachment after compressing it. Regards, Brian. error.7z Description: application/7z-compressed
foomatic-db_20220223-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 27 Mar 2022 11:03:02 +0200 Source: foomatic-db Architecture: source Version: 20220223-1 Distribution: unstable Urgency: medium Maintainer: Debian Printing Group Changed-By: Thorsten Alteholz Changes: foomatic-db (20220223-1) unstable; urgency=medium . * New upstream version 20220223 * debian/control: Add myself to Uploaders: * debian/control: use dh13 * debian/coypright: fix BSD license name * debian/copyright: lintian seems to have a problem with hyphens Checksums-Sha1: 5ce1d0744cfa0fd76489aff0d2b03e543337b29a 2344 foomatic-db_20220223-1.dsc 92bbcc2e455c45fb02e9b0e19cafe0122e3176f5 7468196 foomatic-db_20220223.orig.tar.xz a903904fe3e699e56d765be35daac2876d10e0cb 24096 foomatic-db_20220223-1.debian.tar.xz 453dd1848260ca80fb39832587713637482b35f8 8704 foomatic-db_20220223-1_amd64.buildinfo Checksums-Sha256: 288fb0b800bf5858b9894b9d247531d900c75125e5d3f01962f4600f6a308e80 2344 foomatic-db_20220223-1.dsc 2dff4766b7be839722c8405975f82fff841825a29e19507ede56ff85b31cfe03 7468196 foomatic-db_20220223.orig.tar.xz de44ae7e750c96f5542d95dbcb159a155daeac9a54136965c85b53a67496b169 24096 foomatic-db_20220223-1.debian.tar.xz 2a720cd11371fb0846cb8399ab954a9c0a5f23d6a46aae2e886de0536a4e40a3 8704 foomatic-db_20220223-1_amd64.buildinfo Files: bc558d3e3f3c4879e11ac80b2793ed1b 2344 text optional foomatic-db_20220223-1.dsc 4399a8e45bb60d829b592051e2d9ad7a 7468196 text optional foomatic-db_20220223.orig.tar.xz afe669b04e567280a3407322b16a5746 24096 text optional foomatic-db_20220223-1.debian.tar.xz 52f84eb4b039e5bdc9e6722ec20ac76a 8704 text optional foomatic-db_20220223-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmJAfFNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYR1U9D/9svxQ5iIXOLxyg4hQEjGioQpCZO7e7 QTFIqDpCxbw6oHsnT1d2Meis5e/+aSe+9d7unrFs8rDT8+Bjo0clyol2V3r+g7lk AZ+4hRZZVnpgI+4XcUotitUnGPgCMOMf6SJllv+KzHC12ssvRk4gUDOm2a8SfpTt f9DCO8Qj7fj1c69PK8GyWg8S4u4YQFsqqGUOE5D5Hx5796QeMN2BO8+1m1BZF69X 136PTBZTpy2NeglR1LXcCTc4QTSRIXYXN8liAsHwp3Dqj5bnqmMgQa62kICqiVPh IDNRF2fymjFSV601w+ENue3QQdLZ/rbsofhq9hOmmf8hIeFzZZV1bWVmuscmawQ9 enlPX4ThhSIIcAr3ufuLw1T7RJFrG+ppwAeDL7ed+9ziIAHqLbeMa1PeHAFeGJsZ DNxW2ozUo2a88q00cOr5jEYOUUmeDnw6mV7p9ckCfNgDiV5KBvH54SOlVFXzeft6 JkEFFajHOFhqdHeHTkhZXNUHULdyFbk5rcZ2GjW6IFE9YcRyDs9GWrHkC7QVZNxT gGJAcOLl5Y2a4hhVfPKQ0NEgkhTaeMNiHTfzKpac9Dlo/LftlPKFTOeUkWqeRiOq WkVmZriYKF/ASHg60zNWGBW31pzPLDS0mEWNPLl1Hu1zJcQtCkk/UxD5W85njWNG K8pE6QjgA5vmyQ== =kWwU -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of foomatic-db_20220223-1_source.changes
foomatic-db_20220223-1_source.changes uploaded successfully to localhost along with the files: foomatic-db_20220223-1.dsc foomatic-db_20220223.orig.tar.xz foomatic-db_20220223-1.debian.tar.xz foomatic-db_20220223-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed: Re: Bug#1007110: cups printing dialogue: broad scrollbar overlaps with pull-down Icon
Processing commands for cont...@bugs.debian.org: > reassign 1007110 libreoffice-gtk3 Bug #1007110 [cups] cups printing dialogue: broad scrollbar overlaps with pull-down Icon Bug #1007111 [cups] reportbug: cups printing dialogue: broad scrollbar overlaps with pull-down Icon Bug #1007112 [cups] reportbug: cups printing dialogue: broad scrollbar overlaps with pull-down Icon Bug #1007114 [cups] reportbug: cups printing dialogue: broad scrollbar overlaps with pull-down Icon Bug reassigned from package 'cups' to 'libreoffice-gtk3'. Bug reassigned from package 'cups' to 'libreoffice-gtk3'. Bug reassigned from package 'cups' to 'libreoffice-gtk3'. Bug reassigned from package 'cups' to 'libreoffice-gtk3'. No longer marked as found in versions cups/2.4.1op1-2. No longer marked as found in versions cups/2.4.1op1-2. No longer marked as found in versions cups/2.4.1op1-2. No longer marked as found in versions cups/2.4.1op1-2. Ignoring request to alter fixed versions of bug #1007110 to the same values previously set Ignoring request to alter fixed versions of bug #1007111 to the same values previously set Ignoring request to alter fixed versions of bug #1007112 to the same values previously set Ignoring request to alter fixed versions of bug #1007114 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1007110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007110 1007111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007111 1007112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007112 1007114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1007110: cups printing dialogue: broad scrollbar overlaps with pull-down Icon
reassign 1007110 libreoffice-gtk3 thanks On Sun 27 Mar 2022 at 15:59:55 +0200, mh wrote: > Hi > > Can't you move it to where it belongs? libreoffice? gtk? > Or do I really need to go through this whole reportbug thing? > Is there a way for me to direct this already written report to where > it belongs? I thought had sent it to libreoffice-gtk3 but forgot to tell the control server. Cheers, Brian.
Bug#1007110: cups printing dialogue: broad scrollbar overlaps with pull-down Icon
reassign 1007110 libreoffice-gtk3 thanks. On Fri 11 Mar 2022 at 13:26:52 +0100, Michael Hatzold wrote: > Package: cups > Version: 2.4.1op1-2 > Severity: normal > > Dear Maintainer, > > first, I file my bugreport against "cups" as I don't know to which exact > package it really belongs. The bug shows up in the print dialogue. > > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > I wanted to print a document from within Libreoffice (gtk3) > ** > apt policy libreoffice-gtk3 > libreoffice-gtk3: > Installiert: 1:7.3.1-1 > ** > > >* What exactly did you do (or not do) that was effective (or > ineffective)? > I opened the document which I wanted to print and clicked the file/print menue > >* What was the outcome of this action? > printing menu opened. > But when I tried to open one of the pulldown menue using one of the little > triangular icons on the right the hidden scrollbar popped up overlapping the > icon which thus could not been activated. > > Please Note: > I use a much broader scrollbar than the default one. (I find the default > ergonimically inapt). But this customisation was made one ore two years ago > and > never effected negatively any menue in whatever program. Until today when I > wanted to print. So there must have been a change recently which now changes > the behavior. > > >* What outcome did you expect instead? > Obviously I do not want the scrollbar to overlap a region meant for operating > a > menue and thus making it unusable. Thank you for your report, Michael. Print dialogs in an application are not the responsibility of the printing system. Hence reassigning. Regards, Brian.
Processed: Re: Bug#1008175: #1008175
Processing commands for cont...@bugs.debian.org: > tags 1008175 moreinfo Bug #1008175 [cups-bsd] cups-bsd: lp & lpr options sides=one-sided and sides=two-sided-long-edge are reversed. one-sided prints duplex (Two-sided) and vice-versa Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008175: #1008175
tags 1008175 moreinfo thanks On Wed 23 Mar 2022 at 13:01:18 -0400, Rick Stanley wrote: > Now neither option works correctly executing from the command line. > "lpr -o sides=two-sided-long-edge test.pdf" > "lpr -o sides=one-sided test.pdf" > > And same for lp. Thank you for your report, Rick. What is the printer make and model? The situation is that neither command gives double-sided printing? > Printing from Okular works correctly as expected. There is a slight difference between your lp command and what Okular does. Okular sends a PostScript file to the ptinter. Not that I can see why that should make any difference, but printing from Evince or Firefox sens a PDF. You could try that. Anyway, let's have a log. Enable debug logging with cupsctl --debug-logging Empty error_log with >/var/log/cups/error_log Print and send error_log as an attachment after compressing it. Regards, Brian.
gutenprint_5.3.3-9_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 27 Mar 2022 12:03:02 +0200 Source: gutenprint Architecture: source Version: 5.3.3-9 Distribution: unstable Urgency: medium Maintainer: Debian Printing Group Changed-By: Thorsten Alteholz Changes: gutenprint (5.3.3-9) unstable; urgency=medium . * debian/rules: try to find build failure on buildd Checksums-Sha1: dd33e71bcbaa3e68fe4fd7ae2609e10e95820a4e 3032 gutenprint_5.3.3-9.dsc 2df261fa39433968110259afcff81392b029722c 95632 gutenprint_5.3.3-9.debian.tar.xz ff33fabe0b7716403b3aa65f00d53aee3cd7f9a3 20032 gutenprint_5.3.3-9_amd64.buildinfo Checksums-Sha256: 4bf5f817f4fb26864dab5a43d9f5751cd9711ec06486fd22cf32b3d0aa071861 3032 gutenprint_5.3.3-9.dsc ee980441c9abfea2239cdf82a71134d8d7e65c33f55a0adb6141d9337206c82d 95632 gutenprint_5.3.3-9.debian.tar.xz 1491e2b88459f7d81d3de7c6101338d914256cd99cc28605e61f4d7158653020 20032 gutenprint_5.3.3-9_amd64.buildinfo Files: 2c17a6e26cbebddeb2d18ab937d5b88d 3032 graphics optional gutenprint_5.3.3-9.dsc a8b26fcb7abdc054213e6cb53a00e14f 95632 graphics optional gutenprint_5.3.3-9.debian.tar.xz 9125fe5b5a0da68584ad5fe0cab21076 20032 graphics optional gutenprint_5.3.3-9_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmJAQXNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYR48SD/92nv2F3270G2VwcwKuhVgTM/asujSM kW434TpJMBlGTIYrVZyBgWEI52ljSYifM7bQqCiFLXiCxKosuG0/OGC617pRafKb Y7G6koZU3lG8+8v1EA0abQEXy2KQv6RLOna9pIsmU+8KzfZFbR53X2DKNpBsJOV8 6fzSXiZCEJrCR7tODJPmsoe0fE8zK5jK0ZHWTKjrR6oSRN9dTK7q12ha9JfUdQ6+ ZagIIgQAVVpzMtpCZ5N3FiclpfGVJq4Fw9WBJaHfgpIIOxan4dP6gQOHV7aTq5Cb 9SGn98DDsYVbrUqs2WgG99NJhNRlopSm1jwldinpwPPEr0rpCXj+KcMWuoCjJp3/ pJKbbECVKyrYe3O4Z4XeXY235kc2ASf5rGo8gopE0qgc61yvpjRn/M2MOCawAuTS 2uQSESbSgLWGyH47tBLVWQdpQxIL2sYJF2zK0Ge9vNSKo6pm0K570rtCxYIQ8XQS JsMO0ESb25F4ACNpRL43JWPS4JSxakDQxDrPvfsH/E6zq5USXiVVGrBU1iiNMF1V saU68tY9Fm2oHAsGkLaU8yhl75o1XgTX53eTSJrI1w/r14dQE8TPLPnwIUNIgpcf QAISPFQej1HcgdbfgOfgZKeNzpRwJlZINcHhzclyzjqE7o+r6q4QWwj6I1UTyHY8 49JX1atJ0NIZsQ== =96am -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of gutenprint_5.3.3-9_source.changes
gutenprint_5.3.3-9_source.changes uploaded successfully to localhost along with the files: gutenprint_5.3.3-9.dsc gutenprint_5.3.3-9.debian.tar.xz gutenprint_5.3.3-9_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
