This is a major bug in my opinion. I am not a n00b and I spent the last 2 hours trying to figure out what the heck was going on with my system. I knew foomatic-db was the only printing-related package on my system that I have upgraded in the last few days so I knew it was the reason that printing was no longer working whatsoever. To make matters worse, I had suspected that foomatic-db was the problem. Downgrading doesn't work though, there are errors emerging any of the older foomatic-db ebuilds. See here for more info: http://forums.gentoo.org/viewtopic-t-383818-highlight-lib64+cups+filter+foomaticrip.html This was where I finally realized I should try emerging foomatic-filters again.
I don't see why are you referring us to some 3/4-year old forums post which contains no reply, a confused description and a broken link. foomatic-filters installs a wrapper, that's all. No information here.
I second this bugreport. After upgrading foomatic-db as suggested after emerge -pv world I could not print anymore. After searching in various error-logs I found that cups could not find /usr/lib/cups/filter/foomatic-rip. So foomatic-db removes the foomatic-rip wrapper without warning and leaves the user with a broken system. That is what I call a bug. So please reopen this bug and add a warning to re-emerge foomatic-filter when needed to the foomatic-db ebuild script. Now I am going to re-emerge foomatic-filter.
*** Bug 131568 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > So foomatic-db removes the foomatic-rip wrapper without warning and > leaves the user with a broken system. That is what I call a bug. Well, you only get this if you ignored the collision and emerged foomatic-filters anyway (see Bug 104734). Not much we could do besides the warning. Thanks for the info, the original description in this bug was completely useless.
Sorry I copied and pasted the wrong forum post by accident. Here is the one I meant to copy and it is just a few days old: http://forums.gentoo.org/viewtopic-t-455728.html That forum post shows that at least 4 people had this problem. Sorry my report was "completely useless" as you say. I had intended for the forum post to do most of the explaining for me as it seemed to detail the symptoms and its solution quite thoroughly. No need to get snarky. Also this is a separate issue, but both the old foomatic-db ebuilds don't work. So they probably shouldn't be in portage.
This sure seems like a bug to me. CUPS calls foomatic-rip, which is part of foomatic-filters. The foomatic-db update removes foomatic-rip, without warning or explanation, yet cups still calls it. If there truly is a collision between these two packages, yet both are needed, what then?
My printing also stopped functioning without warning after upgrading to foomatic-db-20050910. I received this message when I tried to revert to 20050606. ACCESS DENIED symlink: /var/tmp/portage/foomatic-db-20050606/image/usr/share/cups/model/foomatic-ppds ln: creating symbolic link `/var/tmp/portage/foomatic-db-20050606/image//usr/share/cups/model/foomatic-ppds' to ` /usr/share/ppd': Permission denied Printing returned to normal with foomatic-db-20050910 only after re-emerging foomatic-filters-3.0.2.
I don't know if this has any bearing on the problem (see previous post), but I use the gimp-print-ijs driver with CUPS.
I am also of the opinion that this behaviour constitutes a bug. If packages collide, it is portages job to tell the user so. That is what the blocks-flag from the emerge output is for. It is not proper behaviour to just rm files belonging to another package. >Well, you only get this if you ignored the collision and emerged >foomatic-filters anyway (see Bug 104734). Not much we could do besides the >warning. (in reply to comment #4) I did not notice any warning. I do not doubt that you did warn, but I (and I belive other people as well if look at what the forums say) did not see it. If these packages block one another, the block-feature of emerge constitutes the best warning you can have.
I second this bug. Printing broke on my system too, after upgrading foomatic-db. Maybe a warning was printed, but since I usually do an "emerge -auDvN world" once a week, I have no chance to see any warnings scrolling by during the hourlong merge. At least this bug was easy to find, once I discovered I could not emerge the old version of foomatic-db and wanted to report it, this popped up. Thanks folks! :-) /Jakob
*** Bug 130986 has been marked as a duplicate of this bug. ***
OK, I added a new revision of foomatic-filters - just to make you remerge it :)