libpoppler1-glib dependency problem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
poppler (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: libpoppler1-glib
Right now, updating my x86_64 Ubuntu Gutsy Gibbon system does not work completely because of a dependency problem with libpoppler1 and libpoppler1-glib. As this is the case since some days, I am reporting it here so it does not get lost.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages are BROKEN:
libpoppler1-glib
The following packages will be upgraded:
dmsetup gtk2-engines-pixbuf libbeagle0 libdevmapper1.02.1 libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglu1-mesa
libglu1-mesa-dev libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libnautilus-burn4 libpoppler1 libvolume-id0
mesa-common-dev mesa-utils nautilus-cd-burner python2.5 python2.5-dev python2.5-examples python2.5-minimal udev
volumeid xserver-xorg-core
25 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/30.1MB of archives. After unpacking 4096B will be freed.
The following packages have unmet dependencies:
libpoppler1-glib: Depends: libpoppler1 (= 0.5.4-0ubuntu8) but 0.5.4-4ubuntu1 is to be installed.
Resolving dependencies...
The following actions will resolve these dependencies:
Keep the following packages at their current version:
libpoppler1 [0.5.4-0ubuntu8 (now)]
Score is 1
Accept this solution? [Y/n/q/?]
Thanks for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #117119 and is being marked as such. Please feel free to report any other bugs you may find.