desktop-packages team mailing list archive

[Richard Elkins <richard.elkins@xxxxxxxxx>]

Confirmed fixed and functional.

The user only sees cups-filters (version 1.8.2-2ubuntu2) installed as a
binary package which is more transparent.

Thanks, Till.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1536353

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in lsb:
  Invalid
Status in cups-filters package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Invalid
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
      - Drop packages-availability checking in lsb-release
      - Truncate README.Debian to a minimum
      - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
      version.date, with version being Debian next stable's

   -- Didier Raboud <odyx@xxxxxxxxxx>  Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lsb/+bug/1536353/+subscriptions