[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#965144: ipp-usb replaces ippusbxd; remove?



On Thu 16 Jul 2020 at 20:40:05 +0200, Didier 'OdyX' Raboud wrote:

> Source: ippusbxd
> Version: 1.34-2
> Severity: important
> 
> Now that ipp-usb landed in Debian unstable [0], and is said to be a
> better-on-all-fronts replacement to ippusbxd; should we be completely removing
> ippusbxd from Debian unstable (and therefore, Bullseye, the next stable
> release)?
> 
> Let's discuss in this bug, before eventually reassigning to ftp-master for the
> actual removal, if we can agree it's a reasonable next steps.
> 
> A side question; ippusbxd is not a dependency nor a recommends of anything
> currently in Debian; should ipp-usb become a recommends of CUPS for instance?
> 
> [0] https://tracker.debian.org/news/1160616/accepted-ipp-usb-099-1-amd64-source-into-unstable-unstable/

I am very much attracted by the idea of a USB connected printer becoming
immediately available when it is plugged in, so a Recommends: ipp-usb
would be ok with me. However, it is as well to be aware that there is a
difference in user experience compared to the situation when driverless
printing was fully introduced on buster.

In the later case, a user who pressed on with the installation of vendor
drivers was generally successful in getting to use them with a wireless
or ethernet connection. With ipp-usb, on the other hand, printing and
scanning can only take place through IPP-over-USB (AFAIK). Users who
expect their previous setup methods to work will probably be due a
disappointment.

I believe scanning to be possible only with sane-escl and sane-airscan.
sane-escl is not yet in unstable to test.

Recommends: ipp-usb | ippusbxd is an option that does not seem to benefit
a Debian user. ippusbxd is supported upstream but there may be plans for
its future we are unaware of. I'm a little unsure about its removal from
unstable, but, overall, there does not appear to a glaring downside to it.
It would simplify the rewriting of the relevant sections of the wiki if
only one daemon was available. :)

Regards,

Brian.


Reply to: