Bug#964446: RFP: sane-airscan - SANE backend for AirScan (eSCL) and WSD document scanners
On Fri 10 Jul 2020 at 18:02:33 +0200, Didier 'OdyX' Raboud wrote: > Control: retitle -1 ITP: sane-airscan - SANE backend for AirScan (eSCL) and > WSD document scanners > Control: owner -1 ! > > Le mardi, 7 juillet 2020, 22.25:14 h CEST Didier 'OdyX' Raboud a écrit : > > > sane-airscan is a SANE backend (scanner driver) for two > > > manufacturer-neutral, standardized communication protocols (AirScan/eSCL > > > and WSD) which are used by the scanners in most modern printer/scanner > > > multi-function devices and so used by thousands of scanners. > > > > For the record, I am primarily concerned about the printing support in > > Debian, which packaging I carry mostly alone (I get great help from Brian > > Potkin for bug triaging, and Till Kamppeter for upstream and Ubuntu > > support). I don't really intend to also start carrying the scanning stack > > on my shoulders too. > > > > (While I state this, I also know that I might end up taking on this > > packaging, just don't wait on me if you're interested!) > > As sadly predicted, I came around to doing it. Should be uploaded to NEW > later today. The independent sane-airscan stands alongside the official sane-escl as being equally as competent. My experience with recommending its use outside Debian has been very positive. I totally agree that the focus of the Debian printing team should be on printing. There is more than enough work there to occupy the time of its principal participant. Having said that, I am pleased to see sane-airscan as a candidate for inclusion in Debian. Regards, Brian.
Bug#961218: RFP: ipp-usb -- Daemon for IPP over USB printer support
Package: wnpp Severity: wishlist * Package name: ipp-usb Version : 0.9.3+34.1 Upstream Author : Alexander Pevzner * URL : https://github.com/alexpevzner/ipp-usb * License : BSD 2-Clause "Simplified" License Programming Lang: Go Description : Daemon for IPP-over-USB printer support ipp-usb is a userland driver for USB devices (printers, scanners, MFDs), supporting the IPP-over-USB protocol. It enables these USB devices to be seen as regular network printers. . It is designed to be a replacement for the ippusbxd daemon, previously used for this purpose. It has a greatly rethought architecture in comparison with ippusbxd, and fixes all of its major flaws and issues. Dear Prospective Packager, Bug #909564 has been attended to in avahi 0.8-1 and Avahi now handles the loopback device lo for local services. Therefore, local-only IPP-over-USB printers now get advertised. Thank you to Trent Lloyd and Till Kamppeter. By all accounts, ipp-usb is a better ippusbxd. Please see slide #12 at https://ftp.pwg.org/pub/pwg/liaison/openprinting/presentations/cups-filters-ippusbxd-2020.pdf In https://github.com/alexpevzner/sane-airscan/issues/29#issuecomment-629628416 Alexander Pevzner says: ippusbxd has serious problems, and these problems are by design, not by implementation. All these problems are fixed in ipp-usb, it uses very different design, so it works absolutely reliable (this is Till's words, not mine). It seems to me that Chrome OS not accepting software in Go hasn't any relevance when packaging for Debian. In any case, Alexander Pevzner would dispute the claim: Frankly speaking, I don't quite understand ChromeOS reasoning. I've recently measured memory consumption of ipp-usb vs ippusbxd. To my surprise, RSS (Resident Set Size, i.e. amount of memory really used) of ipp-usb is even slightly less. If there are more that 1 devices connected, ipp-usb will handle them all in a single process, adding a small amount of memory per device, while ippusbxd requires a process per device. The remainder of his argument is at https://github.com/alexpevzner/sane-airscan/issues/29#issuecomment-630438806 It would be good to see ipp-usb enter unstable alongside ippusbxd. Regards, Brian.
Bug#942741: ITP: lxqt-organizer -- LXQt Pim, right now only an basic organizer
On Sun 20 Oct 2019 at 21:03:17 +0200, Alf Gaida wrote: > Package: wnpp > Severity: wishlist > Owner: Alf Gaida > > * Package name: lxqt-organizer > Version : 0.1.0 > Upstream Author : crispinalan > * URL : https://github.com/lxqt/lxqt-organizer > * License : LGPL > Programming Lang: C++ > Description : LXQt Pim, right now only an basic organizer > > The LXQt Team will maintain the package One would hope that it is '... a basic organizer'. -- Brian.
Bug#803789: RFP: RasterView -- a simple GUI image viewer for CUPS and PWG Raster files
On Mon 02 Nov 2015 at 20:47:24 +0100, Kurt Pfeifle wrote: > Package: wnpp > Severity: RFP > > RasterView is a simple GUI image viewer which specializes in displaying > CUPS raster and PWG Raster files. > > The CUPS and PWG Raster formats are used by CUPS in some printing > workflows. Both can handle multi-page image files, and can embed job > specific settings in page headers (such as page size or duplex settings). > > PWG Raster was specified by the Printer Working Group working on the > upcoming "IPP Everywhere" standard which aims at ubiquituos "driverless > printing" for all major OS platforms. It is one of the three core formats > (besides JPEG and PDF) to be supported by print devices for compliance with > the IPP Everywhere standard. > > A viewer for the generated raster files in such a printing workflow is > important not just for debugging print problems... > > RasterView has a dependency on FLTK. It was written by Mike Sweet (CUPS > developer). Its license is GPL v2. Its latest release is v1.4.1 (Aug 27, > 2015). The latest release (28 Oct 2018) is 1.7.1 > I was able to compile it on Debian Jessie "out of the box". It also compiles on buster. > License: GPL v2 1.7.1 is under the Apache License Version 2.0. > Source Tarball: > https://www.msweet.org/files/project7/rasterview-1.4.1.tar.gz > URL: https://www.msweet.org/projects.php?Z7 A new URL: https://github.com/michaelrsweet/rasterview/releases -- Brian.
Bug#532097: RFA: cups -- Common UNIX Printing System
On Sat 06 Jun 2009 at 14:05:10 +0200, Martin Pitt wrote: > Package: wnpp > Severity: normal > > Hello all, > > cups is in severe need for a dedicated Debian maintainer. I became an > uploader some years ago for more efficient integration of > improvements/fixes done in Ubuntu, but now I have been the only > uploader for 1.5 years. I cleaned up the patch mess, brought the > package and test suite into a well working state, follow up on RC > bugs, and prepare most security updates; Till Kamppeter is developing > the PDF filters. > > However, that's not enough. Neither Till nor I have a Debian unstable > as primary workstation where we could test printing in a real Debian > system, and neither of us has time to look at the Debian bug reports. > > Right now, cups has hundreds of bug reports, many of them years old; > many of them were probably fixed long ago, many aren't problems in > cups but some driver (gutenprint, foomatic, ghostscript). > > To get the Debian cups bugs into some useful state again, someone who > knows the Linux printing system very well needs to sit down and write > a comprehensive "how to debug printing problems" document: in > particular, how to identify in which package the problem is, which > debug information to collect, and common workarounds/tests which help > the reporter's immediate problem and are useful for diagnosis. > > Then we can declare a "bug bancrupcy" and mass-close all bugs which > were filed before the Lenny release, with an honest apology and the > request to re-file bugs again with following the debugging document. > For all newer bugs we can just followup with the debugging document. > > On the plus side, cups' upstream Mike Sweet is very responsive. It > takes some dispassionateness to argue with him about patches and > rejected bug reports, but he responds very fast. So the genuine > problems remaining in the Debian BTS should be spoonfed to upstream, > after making sure that it isn't a Debian specific or driver problem. > > I'm happy to continue basic package maintenance as pointed out above, > do sponsoring, and mentor interested newcomers. You don't need to be a > DD, but you should have a printer or two, use Debian unstable > regularly, and willing to learn about the printing architecture (cups > spooler, drivers, etc.). > > Many thanks in advance, [...] This bug report should be closed. For a number of years Didier 'OdyX' Raboud has been the dedicated Debian maintainer of cups and other packages and kept them in excellent shape with timely package uploads and attention to detail. The printing team's activities have also run smoothly. The "hundreds of bug reports" have been reduced to a handful and the wiki and cups documentation have been transformed. Regards, Brian.
Bug#904257: [printer-driver-escpr] Missing drivers for "Expression Premium XP-6000"
On Wed 25 Jul 2018 at 10:16:44 +0100, Brian Potkin wrote: > According to > > https://www.epson.co.uk/viewcon/corporatesite/site/149/products/mainunits/specs/21503 > > this printer is an AirPrint and Google Cloud Print printer, so it should > be capable of operating without a driver from Epson: > > https://wiki.debian.org/DriverlessPrinting Forgot to mention: I would be interested in what avahi-browse (which is in the avahi-utils package) gives for the XP-6000. Having log from avahi-browse -art > log would be useful. Cheers, Brian.
Bug#904257: [printer-driver-escpr] Missing drivers for "Expression Premium XP-6000"
On Wed 25 Jul 2018 at 09:09:14 +0200, Didier 'OdyX' Raboud wrote: > Control: reassign -1 wnpp > Control: retitle -1 ITP: epson-inkjet-printer-escpr2 - Epson Printer Driver > ESC/P-R Driver 2 > Control: severity -1 wishlist > Control: owner -1 ! > Control: affects -1 src:printer-driver-escpr > > Hi Robert, > > Le dimanche, 22 juillet 2018, 13.09:39 h CEST Robert Braumann a écrit : > > got an "EPSON Expression Premium XP-6000", but unfortunately there are no > > drivers for it in "printer-driver-escpr". Please add the driver for the > > "XP-6000" to the package. > > According to Epson's download center [0], the XP-6000 series printers > need the printer-driver-escpr2 driver, which is a new package that needs > to be prepared and uploaded: > > Package name: epson-inkjet-printer-escpr2 > Version : 1.0.18 > Upstream Author : Seiko Epson Corporation > URL : > http://download.ebz.epson.net/dsc/search/01/search/searchModule > License : LGPL2.1 + EPSON restrictions > Programming Lang: C > Description : Epson Inkjet Printer Driver 2 (ESC/P-R) > > This would be maintained under the Debian Printing Team umbrella. > > That said, given this COPYING.EPSON at the root of the tarball, I'm afraid > it might be non-free. It might not even be redistributable: > > In particular: > > This software includes source codes which are distributed under GNU Lesser > > General > > Public License v2.1 (COPYING.LIB). This software also includes objects > > codes > > which are distributed under the conditions of > > SEIKO EPSON CORPORATION SOFTWARE LICENSE AGREEMENT(COPYING.EPSON). > > and: > > 2. Other Rights and Limitations. You agree not to modify, adapt or > > translate the Software. You also agree not to attempt to reverse > > engineer, decompile, disassemble or otherwise attempt to discover the > > source code of the Software > > Indeed, the tarball contains escprlib/lib/libescpr2*.a > > I'll check if these can be recompiled, but I really doubt it. > > You will have to download the .deb for yourself I'm afraid. > > Cheers, > OdyX > [0] http://download.ebz.epson.net/dsc/search/01/search/searchModule According to https://www.epson.co.uk/viewcon/corporatesite/site/149/products/mainunits/specs/21503 this printer is an AirPrint and Google Cloud Print printer, so it should be capable of operating without a driver from Epson: https://wiki.debian.org/DriverlessPrinting Regards, Brian.
