Another impasse: conflict between poppler-glib and (nonexistent?) poppler-gtk
robbak at robbak.com
Sat Oct 27 09:10:40 UTC 2012
Note in updating:
Affects: users of graphics/poppler-gtk
Author: Koop Mast <kwm at FreeBSD.org>
Poppler was update to 0.18.0, and the gtk slave port was renamed to
match the library it installs. Please run the following command to migrate.
# portmaster -o graphics/poppler-glib poppler-gtk-0.16.7
Yes, poppler-gtk was deleted. You can find information about things
like that from freshports.org, or searching UPDATING and/or MOVED
On 27 October 2012 18:49, Thomas Mueller <mueller23 at insightbb.com> wrote:
> In my many-times-interrupted attempt to upgrade all ports that depend on png, I hit another snag: poppler-glib allegedly trying to install files to the same place as poppler-gtk.
> I find no poppler-gtk in the ports tree but find it in /var/db/pkg ; find poppler-glib in ports tree but not /var/db/pkg .
> Here is the section of the log that shows the snag:
> /sbin/ldconfig -m /usr/local/lib
> ===> Registering installation for poppler-glib-0.18.4_2
> Installing poppler-glib-0.18.4_2...pkg: poppler-glib-0.18.4_2 conflicts with pop
> pler-gtk-0.16.7 (installs files into the same place). Problematic file: /usr/lo
> *** [fake-pkg] Error code 70
> Stop in /BETA1/usr/ports/graphics/poppler-glib.
> Now running ls -d /BETA1/usr/ports/*/poppler* shows
> Running ls -d /var/db/pkg/poppler* shows
> Checking the Makefiles and running "make showconfig" provided no useful help.
> Strange when a port, poppler-gtk, does not show in ports tree.
> So where do I go from here?
> freebsd-ports at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
More information about the freebsd-ports