Bug#814930: jessie-pu: package hplip/3.15.11+repack0-1

2016-02-23 Thread Stefano Rivera
Hi Julien (2016.02.20_17:04:29_+0200) > How much do the changes affect existing code paths for already-supported > printers? There's a reasonable amount of code churn: __init__.py |2 align.py| 12 base/LedmWifi.py|

Bug#814930: jessie-pu: package hplip/3.15.11+repack0-1

2016-02-20 Thread Julien Cristau
Control: tag -1 moreinfo On Tue, Feb 16, 2016 at 12:15:56 -0500, Stefano Rivera wrote: > Package: release.debian.org > Severity: normal > Tags: jessie > User: release.debian@packages.debian.org > Usertags: pu > > I asked the printing people how they felt about an backport of hplip, > and

Bug#814930: jessie-pu: package hplip/3.15.11+repack0-1

2016-02-20 Thread Julien Cristau
On Tue, Feb 16, 2016 at 12:15:56 -0500, Stefano Rivera wrote: > Package: release.debian.org > Severity: normal > Tags: jessie > User: release.debian@packages.debian.org > Usertags: pu > > I asked the printing people how they felt about an backport of hplip, > and OdyX suggested [0]: > > >

Bug#814930: jessie-pu: package hplip/3.15.11+repack0-1

2016-02-16 Thread Stefano Rivera
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu I asked the printing people how they felt about an backport of hplip, and OdyX suggested [0]: > As far as I remember (but could never take the time to actively > check), the Debian