This bug was fixed in the package poppler - 0.26.0-1ubuntu2
---------------
poppler (0.26.0-1ubuntu2) utopic; urgency=medium
* Don't have libpoppler-dev depend on libpoppler-private-dev. If a package
needs this to build then it should Build-Depend on libpoppler-private-dev
directly. (LP: #1325174)
-- Iain Lane <[email protected]> Thu, 05 Jun 2014 11:01:06 +0100
** Changed in: poppler (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1325174
Title:
please remove libpoppler-private-dev dependency from libpoppler-dev
Status in “poppler” package in Ubuntu:
Fix Released
Bug description:
After the move of all the libpoppler private headers from libpoppler-
dev to libpoppler-private-dev two years ago in Debian, I took care to
having all the sources fixed in Debian within the Wheezy freeze.
Hence, for almost two years, there were no sources in Debian using the
private libpoppler and not build-depending on libpoppler-private-dev.
On the other hand, somebody in Ubuntu added the aforementioned dependency to
"easy a transition", without actually checking it was still an issue, and
introducing a circular dependency (libpoppler-private-dev -> libpoppler-dev,
and libpoppler-dev -> libpoppler-private-dev).
Please remove this dependency. If there are still sources affected by this
(which should not happen to anything being synchronized from Debian), then the
solution is to just change the build dependency from libpoppler-dev to
libpoppler-private-dev.
Thanks,
Pino (the current poppler maintainer in Debian)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1325174/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
