From: "Andreas Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/pdf2htmlEX/
Date: Sun, 3 Jun 2018 11:36:51 +0000 (UTC) [thread overview]
Message-ID: <1528025778.e9e3cad70a654164462c8011bdf1b3d1f313a0be.dilfridge@gentoo> (raw)
commit: e9e3cad70a654164462c8011bdf1b3d1f313a0be
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 3 11:36:18 2018 +0000
Commit: Andreas Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Sun Jun 3 11:36:18 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e9e3cad7
app-text/pdf2htmlEX: Drop poppler requirement only in live ebuild
It builds, but it doesnt produce any reasonable output yet... :/
Needs further code analysis and testing.
Bug: https://bugs.gentoo.org/656108
Package-Manager: Portage-2.3.40, Repoman-2.3.9
app-text/pdf2htmlEX/pdf2htmlEX-9999.ebuild | 1 -
1 file changed, 1 deletion(-)
diff --git a/app-text/pdf2htmlEX/pdf2htmlEX-9999.ebuild b/app-text/pdf2htmlEX/pdf2htmlEX-9999.ebuild
index 327250408f9..4bba2c9ce1e 100644
--- a/app-text/pdf2htmlEX/pdf2htmlEX-9999.ebuild
+++ b/app-text/pdf2htmlEX/pdf2htmlEX-9999.ebuild
@@ -22,7 +22,6 @@ IUSE=""
CDEPEND="
>=app-text/poppler-0.61.1:=[jpeg,png]
- <app-text/poppler-0.64.0
app-text/poppler-data
~media-gfx/fontforge-20170731
media-libs/freetype
next reply other threads:[~2018-06-03 11:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 11:36 Andreas Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-02 18:00 [gentoo-commits] repo/gentoo:master commit in: app-text/pdf2htmlEX/ Mikle Kolyada
2018-06-16 21:24 Andreas Hüttel
2018-06-16 19:41 Andreas Hüttel
2018-05-21 21:54 Andreas Hüttel
2018-05-20 20:43 Andreas Hüttel
2018-05-20 20:43 Andreas Hüttel
2018-05-18 22:33 Andreas Sturmlechner
2017-12-31 11:28 Andreas Hüttel
2017-12-31 10:08 Andreas Hüttel
2017-12-30 21:57 Andreas Hüttel
2017-12-30 19:37 Andreas Hüttel
2017-04-03 10:34 Andreas Hüttel
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=1528025778.e9e3cad70a654164462c8011bdf1b3d1f313a0be.dilfridge@gentoo \
--to=dilfridge@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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