santosh83
April 6th, 2012, 07:10 AM
Hi all,
Just now when I was installing xpdf to try out a lightweight PDF viewer, when I tried to mark the package 'xpdf-utils' to be installed in Synaptic, a dialog popped up telling me that the following list of installed packages would be removed:
bluez-cups
cups
cups-driver-gutenprint
foo2zjs
foomatic-db-compressed-ppds
ghostscript-cups
hplip
hplip-cups
kubuntu-desktop
lsb
lsb-printing
poppler-utils
pxljr
splix
ubuntu-desktop
xubuntu-desktop
This seems to me to be a bug in xpdf-utils package. Surely it shouldn't need to uninstall all these packages to function!! Most of them have no relation to PDF files at all!
My system is fully updated Maverick (64-bit.)
The package 'xpdf-utils' seems to have two versions available:
3.02-9ubuntu1.1 (maverick updates) - this is default
3.02-9ubuntu1 (maverick)
When I force the 2nd version, largely the same 'to be uninstalled' list as above is displayed, with the addition of 'xpdf-reader' as well!
Do others have the same issue, either in Maverick or more recent releases? Is this a package bug? Should I report a bug?
Thanks.
Just now when I was installing xpdf to try out a lightweight PDF viewer, when I tried to mark the package 'xpdf-utils' to be installed in Synaptic, a dialog popped up telling me that the following list of installed packages would be removed:
bluez-cups
cups
cups-driver-gutenprint
foo2zjs
foomatic-db-compressed-ppds
ghostscript-cups
hplip
hplip-cups
kubuntu-desktop
lsb
lsb-printing
poppler-utils
pxljr
splix
ubuntu-desktop
xubuntu-desktop
This seems to me to be a bug in xpdf-utils package. Surely it shouldn't need to uninstall all these packages to function!! Most of them have no relation to PDF files at all!
My system is fully updated Maverick (64-bit.)
The package 'xpdf-utils' seems to have two versions available:
3.02-9ubuntu1.1 (maverick updates) - this is default
3.02-9ubuntu1 (maverick)
When I force the 2nd version, largely the same 'to be uninstalled' list as above is displayed, with the addition of 'xpdf-reader' as well!
Do others have the same issue, either in Maverick or more recent releases? Is this a package bug? Should I report a bug?
Thanks.