Github messages for voidlinux
 help / color / mirror / Atom feed
From: zenny <zenny@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: cups-pdf producing a single blank page after upgrade today (2021-05-01)
Date: Fri, 18 Jun 2021 13:31:41 +0200	[thread overview]
Message-ID: <20210618113141.PvPXTC3j0aGatcoLDrXLcXsUhQ3MpqCbMMBM9h-U7pA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30615@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 3885 bytes --]

New comment by zenny on void-packages repository

https://github.com/void-linux/void-packages/issues/30615#issuecomment-863952541

Comment:
> > > Hi, do you know how long it's been since your last update?
> > 
> > 
> > a week earlier.
> > > Both ghostscript and cups were updated semi-recently (ghostscript being the most recent one). You could try downgrading either of them to test :)
> > 
> > 
> > Ok thanks for the pointer.
> 
> @ericonr The issue is not yet resolved. :(
> 
> Both cups-pdf and cups-filters are installed. Physical printers are working alright.
> 
> Fyi, tried with the solutions provided in https://askubuntu.com/questions/601836/cups-pdf-prints-a-blank-page, didn't work either. ;-)
> 
> Just wondering, does it have anything to do with this repo: https://github.com/alexivkin/CUPS-PDF-to-PDF?! The reason I asked it it uses the same ppd files from this repo in void, too. Found a similar issue in https://www.reddit.com/r/voidlinux/comments/nlp4nl/cupspdf_printing_a_blank_page/ which pointed to a patch ( https://github.com/archlinux/svntogit-packages/tree/packages/cups-pdf/trunk) that is associated with ghostscript's deprecated parameter `setpdfwrite`?!
> 
> Any inputs to get out of this issue shall be appreciated.

I even tried to build `cups-pdf` from the source with the patch from https://github.com/archlinux/svntogit-packages/raw/packages/cups-pdf/trunk/remove-deprecated-ghostscript-setpdfwrite-operator.diff (pointer from https://www.linuxquestions.org/questions/slackware-14/cups-pdf-printer-prints-a-blank-pdf-after-ghostscript-9-54-0-update-4175694164/ and )https://bugs.archlinux.org/task/70313), even failed with:

```
$ ./xbps-src pkg cups-pdf
...
=> cups-pdf-3.0.1_1: removing autodeps, please wait...
=> cups-pdf-3.0.1_1: building for x86_64...
   [target] cups-devel-2.3.3op2_1: found (https://alpha.de.repo.voidlinux.org/current)
   [runtime] ghostscript-9.54.0_1: found (https://alpha.de.repo.voidlinux.org/current)
=> cups-pdf-3.0.1_1: installing target dependencies: cups-devel-2.3.3op2_1 ...
=> cups-pdf-3.0.1_1: running do-fetch hook: 00-distfiles ...
=> cups-pdf-3.0.1_1: fetching distfile 'cups-pdf_3.0.1.tar.gz'...
cups-pdf_3.0.1.tar.gz: [29KB 13%] 104KB/s ETA: 00m06s
cups-pdf_3.0.1.tar.gz: 29KB [avg rate: 756KB/s]
=> cups-pdf-3.0.1_1: verifying checksum for distfile 'cups-pdf_3.0.1.tar.gz'... OK.
=> cups-pdf-3.0.1_1: running do-extract hook: 00-distfiles ...
=> cups-pdf-3.0.1_1: extracting distfile(s), please wait...
=> cups-pdf-3.0.1_1: running do-patch hook: 00-patches ...
=> cups-pdf-3.0.1_1: patching: print-to-home.patch.
=> cups-pdf-3.0.1_1: patching: remove-deprecated-ghostscript-setpdfwrite-operator.diff
.
The text leading up to this was:
--------------------------
|--- cups-pdf-3.0.1/src/cups-pdf.h      2017-02-24 16:31:00.901661190 +0100
|+++ cups-pdf-3.0.1/src/cups-pdf.h.new  2021-04-06 17:05:57.553854742 +0200
--------------------------
File to patch:
Skip this patch? [y]
1 out of 1 hunk ignored
The text leading up to this was:
--------------------------
|--- cups-pdf-3.0.1/extra/cups-pdf.conf 2017-02-24 16:30:18.476524443 +0100
|+++ cups-pdf-3.0.1/extra/cups-pdf.conf.new     2021-04-06 17:06:26.364602843 +0200
--------------------------
File to patch:
Skip this patch? [y]
1 out of 1 hunk ignored
=> ERROR: cups-pdf-3.0.1_1: do-patch_00-patches: 'patch -sl ${_args} -i ${_patch} 2> /
dev/null' exited with 1
=> ERROR:   in _process_patch() at common/hooks/do-patch/00-patches.sh:34
=> ERROR:   in hook() at common/hooks/do-patch/00-patches.sh:51
=> ERROR:   in run_func() at common/xbps-src/shutils/common.sh:21
=> ERROR:   in run_pkg_hooks() at common/xbps-src/shutils/common.sh:245
=> ERROR:   in run_step() at common/xbps-src/shutils/common.sh:71
=> ERROR:   in main() at common/xbps-src/libexec/xbps-src-dopatch.sh:33
```

!!

  parent reply	other threads:[~2021-06-18 11:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01 17:06 [ISSUE] " zenny
2021-05-01 21:58 ` ericonr
2021-05-03 10:55 ` zenny
2021-06-17 16:09 ` zenny
2021-06-17 16:23 ` zenny
2021-06-17 16:24 ` zenny
2021-06-17 16:30 ` zenny
2021-06-17 16:31 ` zenny
2021-06-17 16:45 ` zenny
2021-06-17 16:49 ` zenny
2021-06-18 10:57 ` zenny
2021-06-18 11:11 ` zenny
2021-06-18 11:31 ` zenny [this message]
2021-06-18 12:00 ` zenny
2021-06-18 12:18 ` zenny
2021-06-22 17:30 ` Piraty
2021-06-22 17:44 ` zenny
2021-06-22 18:14 ` zenny
2021-07-05 13:07 ` Piraty
2021-07-06 14:34 ` zenny
2021-07-07  9:25 ` [ISSUE] [CLOSED] " Piraty
2021-07-07  9:25 ` Piraty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210618113141.PvPXTC3j0aGatcoLDrXLcXsUhQ3MpqCbMMBM9h-U7pA@z \
    --to=zenny@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).