Can't upate foomatic due to conflicting dependencies.

Thetargos · #1 6th February 2008, 06:51 AM

I tried to perform an update today of my system only to be greeted with an error in dependencies. These dependencies are packages that I am not fully sure what are they used for, or why were they installed in the first place (as rpm -q --whatrequires <package> yields nothing). The error in question is as follows:

Code:

Running Transaction Test
Finished Transaction Test


Transaction Check Error:
  file /usr/share/foomatic/db/source/printer/HP-LaserJet_M1005_MFP.xml from install of foomatic-3.0.2-53.fc8.x86_64 conflicts with file from package foo2xqx-0.20070822-1.lvn8.x86_64
  file /usr/share/foomatic/db/source/printer/Xerox-Phaser-6115MFP.xml from install of foomatic-3.0.2-53.fc8.x86_64 conflicts with file from package foo2qpdl-0.20070822-1.lvn8.x86_64

Error Summary
-------------

I have no idea what those two packages there are used for: foo2xqx and foo2qpdl. Running a yum info on both packages yields:

Code:

Installed Packages
Name   : foo2xqx
Arch   : x86_64
Version: 0.20070822
Release: 1.lvn8
Size   : 79 k
Repo   : installed
Summary: Linux printer driver for HP LaserJet M1005 MFP
Description:
foo2xqx is an open source printer driver for printers that use the
HP/Software Imaging "XQX" stream wire protocol for their print data,
such as the HP LaserJet M1005 MFP. These printers are often
erroneously referred to as winprinters or GDI printers. However,
Microsoft GDI only mandates the API between an application and the
printer driver, not the protocol on the wire between the printer
driver and the printer. In fact, "XQX" printers are raster printers
which happen to use a very efficient wire protocol which was developed
by HP/Software Imaging. "XQX" is just one of many wire protocols that
are in use today, such as Postscript, PCL, Epson, ZjStream, etc.

Users of this package are requested to visit the author's web page at
http://foo2xqx.rkkda.com/ and consider contributing.

Name   : foo2qpdl
Arch   : x86_64
Version: 0.20070822
Release: 1.lvn8
Size   : 1.7 M
Repo   : installed
Summary: Linux printer driver for Samsung CLP-300, CLP-600, CLP-3160
Description:
foo2qpdl is an open source printer driver for printers that use the
QPDL wire protocol for their print data, such as the Samsung CLP-300
or the Samsung CLP-600 or the Xerox Phaser 6110. These printers are
often erroneously referred to as winprinters or GDI printers. However,
Microsoft GDI only mandates the API between an application and the
printer driver, not the protocol on the wire between the printer
driver and the printer. In fact, QPDL printers are raster printers
which happen to use a very efficient wire protocol. QPDL is just one
of many wire protocols that are in use today, such as Postscript, PCL,
Epson, ZjStream, etc.

Users of this package are requested to visit the author's web page at
http://foo2lava.rkkda.com/ and consider contributing.

I assume it would be harmless to remove these two packages and update foomatic. I just can't figure out how did these packages get installed in the first place

Edit

I'm even more intrigued how these packages got installed, as they are found on Livna... Strange, however removing them, solved the update problem. Will most likely have to post a bug report to Livna.

savage · #2 6th February 2008, 09:03 AM

I had the same kind of conflict with the nvidia drivers, the 96xx drivers were conflicting with the non-96xx drivers, I got around it by excluding the 96xx drivers during the yum process:

Code:

yum install foomatic-3.0.2-53.fc8.x86_64 --exclude=foo2xqx-0.20070822-1.lvn8.x86_64

If you're conflict is across repos, you could just use '--disablerepo=livna'.

Savage

Thetargos · #3 6th February 2008, 10:28 AM

The problem is not about the repos, is about conflicting files. Installed files against new package. The files present were from those packages, which conflicted with the new files in foomatic update. I guess Livna packages didn't get updated against the newer foomatic so weren't pulled as deps... or the dependencies were "broken" by foomatic. In any case, I removed those packages which I don't need anyway, and am still not sure how did they get installed in the first place.