Bugzilla – Bug 551785
hplip package does not pull hplip-hpijs package and thus fails to find printer
Last modified: 2009-11-03 09:25:30 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 I updated from 11.1 to 11.2 via zypper dup and my hp printer stopped working. hp-setup did not find any devices either and using hp-setup -i USB-ID showed: error: option -i not recognized I had a look at the packages installed and there was still hplip-hpcups from packman. Removing it pulled in hplip-hpijs and the printer got recognised by hp-setup. Why did hplip not pull hplip-hpijs when it was updated if that package is needed by it? Reproducible: Always
Our hplip package has a hard RPM requirement for its exactly matching hplip-hpijs package in our hplip.spec ------------------------------------------------------------------- # Require the exact matching version-release of the hpijs # sub-package to make sure to have the exact matching version # of libhpip and libhpmud installed. # The exact matching version-release of the sub-package # is available on the same repository where the main-package is # (compare the "Recommends: hplip" entry below). # A wrong library version may let libsane-hpaio crash # (e.g. segfault) which lets the whole scanning stack # frontend<->libsane-dll<->libsane-backend crash # also for any other backend when the hpaio backend # is enabled (e.g. "scanimage -L"): Requires: %{name}-hpijs = %{version}-%{release} ------------------------------------------------------------------- Because you wrote "there was still hplip-hpcups from packman" I assume this bug is whatever else kind of bad consequence or whatever kind of side effect of bug #515005 "HPLIP packman packages do not work for openSUSE 11.0" As far as I see (I neither use nor test packman packages) it looks as if you have a mixed-up HPLIP installation which is partially from packman and partially from us. Therefore it should work when you either get rid of packman's HPLIP and use only our HPLIP or use only packman's HPLIP and get rid of our HPLIP. In particular note https://bugzilla.novell.com/show_bug.cgi?id=515005#c19 which indicates that you may also need whatever of packman's Python stuff if you use packman's HPLIP. *** This bug has been marked as a duplicate of bug 515005 ***
(In reply to comment #1) > Our hplip package has a hard RPM requirement for > its exactly matching hplip-hpijs package in our hplip.spec > ------------------------------------------------------------------- > # Require the exact matching version-release of the hpijs > # sub-package to make sure to have the exact matching version > # of libhpip and libhpmud installed. > # The exact matching version-release of the sub-package > # is available on the same repository where the main-package is > # (compare the "Recommends: hplip" entry below). > # A wrong library version may let libsane-hpaio crash > # (e.g. segfault) which lets the whole scanning stack > # frontend<->libsane-dll<->libsane-backend crash > # also for any other backend when the hpaio backend > # is enabled (e.g. "scanimage -L"): > Requires: %{name}-hpijs = %{version}-%{release} > ------------------------------------------------------------------- Then why did zypper dup update the hplip package from the oss repo but did not install the hpijs package? This is not about the obvious fact that mixing packages will not work but about hplip not pulling the hpijs package but being happy with the hplip-hpcups package from packman and thus failing.
I am afraid I cannot answer questions regarding our package management and/or repository management software because I am no expert at all regarding this software. If you find bugs there, please file bugs for the matching Bugzilla component (i.e. not "Printing" but e.g. "libzypp").