From my point of view this sequence of issues is a perfect example
why we should prefer stability in Leap over newest greatest stuff
which we do provide in Tumbleweed for those who need it and
http://bugzilla.suse.com/show_bug.cgi?id=1005395
http://bugzilla.suse.com/show_bug.cgi?id=1005395#c2
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Johannes Meixner ---
This is another consequence of the poppler version upgrade in Leap 42.2
which requires a cups-filters version upgrade in Leap 42.2, see bug#983517
which now requires a cups-backends update in Leap 42.2 to the one
in the Printing project where it is already fixed:
--------------------------------------------------------------------------
$ osc rdiff openSUSE:Leap:42.2 cups-backends Printing cups-backends
...
--- cups-backends.changes (revision 3)
+++ cups-backends.changes (revision 15)
...
+Thu Mar 3 16:44:47 CET 2016 - jsmeix@suse.de
+
+- Since cups-filters version 1.6.0 the beh backend is provided
+ by the cups-filters RPM as /usr/lib/cups/backend/beh which is
+ a C re-write of the beh backend written in Perl that is still
+ provided here but now named /usr/lib/cups/backend/beh.pl
+ to avoid that cups-backends conflicts with cups-filters.
...
$ osc submitrequest -m 'The poppler version upgrade in Leap 42.2
required a cups-filters version upgrade in Leap 42.2 (see boo#983517)
which now requires a cups-backends update in Leap 42.2 to the one
in the Printing project (see boo#1005395)'
Printing cups-backends openSUSE:Leap:42.2 cups-backends
created request id 436056
--------------------------------------------------------------------------
this is also a perfect example for the difference between
SUSE Linux Enterprise products where things are kept stable
(in particular in SLE12 backward compatiblility is maintained
so that in SLE12 no cups-filters version upgrade is needed)
versus community projects like Leap where things are not
so much kept stable and backward compatible.
--
You are receiving this mail because:
You are on the CC list for the bug.
