group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #06269
[Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore
Any printer installation is the problems you confront allow the
professional to take a step ahead to fix the driver, install it well and
ensure that it is compatible with your computer software and works well.
The specialist guide you well how to make over it well. To get quotes
for your queries dial toll free number 1-888-924-5460 now OR Visit your
website for more details : https://www.vfix365.us/hp
** Also affects: lsb
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1536353
Title:
[regression] Printer drivers install is broken as lsb package is not
available anymore
Status in lsb:
New
Status in cups-filters package in Ubuntu:
Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
Fix Released
Status in lsb package in Ubuntu:
Fix Released
Status in cups-filters source package in Xenial:
Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
Fix Released
Status in lsb source package in Xenial:
Fix Released
Bug description:
[SRU justification]
Previous releases were compatible with third-party printer drivers provided in LSB package format (and also as .deb packages depending on the lsb package). As of 16.04, because the LSB specifies ABIs for various libraries that are no longer supported in Ubuntu as obsolete, the packages for the lsb modules have been dropped in both Debian and Ubuntu. This includes dropping of lsb-core, which is the component which provides the LSB-mandated ELF loader path - without which no lsb executable will work.
This SRU will restore the bare minimum of LSB compatibility necessary
to support known third-party LSB printer driver packages on Ubuntu
16.04.
[Regression potential]
The reintroduced 'lsb' binary package is known to not fully satisfy the requirements for a complete LSB-compliant system. This is a regression vs. Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to Ubuntu 16.04 may have the upgrade succeed without any warning from the package manager.
As there are very few lsb packages in use in the wild, this is
considered an acceptable regression, especially as this will land
before the first 16.04 point release.
[Test case]
1. Download the epsion 201106w printer driver package from http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
2. Install the package and confirm that its dependencies are not satisfiable.
3. Enable xenial-proposed.
4. Install the package again and confirm that the dependencies are satisfied.
5. Verify that /opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter can be run without errors about missing lsb ld.so or missing libraries.
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