From: Marius Bakke <mbakke@fastmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>, 34198@debbugs.gnu.org
Subject: [bug#34198] [PATCH 1/2] gnu: poppler-qt4: Enable qt4 frontend.
Date: Thu, 31 Jan 2019 22:59:02 +0100 [thread overview]
Message-ID: <87tvho8p5l.fsf@fastmail.com> (raw)
In-Reply-To: <20190125164802.17853-1-dannym@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
Danny Milosavljevic <dannym@scratchpost.org> writes:
> * gnu/packages/pdf.scm (poppler-qt4)[version]: Downgrade to 0.61.1.
> [source]: Apply CVE patch.
> ---
> gnu/packages/pdf.scm | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/gnu/packages/pdf.scm b/gnu/packages/pdf.scm
> index 96c0f9e3a..956e25c6d 100644
> --- a/gnu/packages/pdf.scm
> +++ b/gnu/packages/pdf.scm
> @@ -174,6 +174,16 @@ When present, Poppler is able to correctly render CJK and Cyrillic text.")
> (define-public poppler-qt4
> (package/inherit poppler
> (name "poppler-qt4")
> + (version "0.61.1")
> + (source (origin
Since this adds a completely different source I think package/inherit is
inappropriate, because we no longer want Poppler grafts applying here.
That said, I would rather we abandoned this package, since Qt4 is
unmaintained for a really long time now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-01-31 22:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 16:43 [bug#34198] [PATCH 0/2] Add diffpdf Danny Milosavljevic
2019-01-25 16:48 ` [bug#34198] [PATCH 1/2] gnu: poppler-qt4: Enable qt4 frontend Danny Milosavljevic
2019-01-25 16:48 ` [bug#34198] [PATCH 2/2] gnu: Add diffpdf Danny Milosavljevic
2019-01-29 17:08 ` Ricardo Wurmus
2019-01-29 20:12 ` Danny Milosavljevic
2019-01-29 17:05 ` [bug#34198] [PATCH 1/2] gnu: poppler-qt4: Enable qt4 frontend Ricardo Wurmus
2019-01-29 20:09 ` Danny Milosavljevic
2019-01-31 21:59 ` Marius Bakke [this message]
2020-09-05 20:47 ` bug#34198: Closing Andreas Enge
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvho8p5l.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=34198@debbugs.gnu.org \
--cc=dannym@scratchpost.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).