unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 34198@debbugs.gnu.org
Subject: [bug#34198] [PATCH 1/2] gnu: poppler-qt4: Enable qt4 frontend.
Date: Tue, 29 Jan 2019 21:09:59 +0100	[thread overview]
Message-ID: <20190129210959.7ab17a2e@scratchpost.org> (raw)
In-Reply-To: <877eenpf71.fsf@elephly.net>

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

Hi Ricardo,

On Tue, 29 Jan 2019 18:05:22 +0100
Ricardo Wurmus <rekado@elephly.net> wrote:

> Could the previous higher version of the package not be built?
> Otherwise we’d have to deal with the downgrade somehow to make sure that
> installed packages get downgraded to this version as well.

It could technically be built, but it was missing the qt4 frontend because
newer poppler versions had removed it from its source entirely.

Nobody else uses poppler-qt4 in Guix - otherwise the client would have noticed
that it did not work at all.

I just needed a PDF differ which requires poppler-qt4, so I fixed poppler-qt4.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-01-29 20:11 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 [this message]
2019-01-31 21:59   ` Marius Bakke
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=20190129210959.7ab17a2e@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=34198@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).