Bug#972089: Backport hplip 3.20.5 to buster-backports

2020-10-15 Thread Didier 'OdyX' Raboud
Le mardi, 13 octobre 2020, 16.37:38 h CEST Brian Potkin a écrit :
> > It seems sane-airscan is not available on Debian 10, only on Debian 11.
> 
> Alex Pevzner provides packages for Debian 10. I use one very successfully.
> 
>   https://download.opensuse.org/repositories/home:/pzz/Debian_10/

Backporting sane-airscan is straightforward (just tried), and could make a 
nice improvement to buster(-backports).

It seems I'll upload both hplip and sane-airscan once their version reach 
bullseye.

Cheers,
OdyX

signature.asc
Description: This is a digitally signed message part.


Bug#972089: Backport hplip 3.20.5 to buster-backports

2020-10-13 Thread Brian Potkin
On Tue 13 Oct 2020 at 10:07:10 +0200, Alex ARNAUD wrote:

> Hello Didier,
> 
> Thanks for your quick answer.
> 
> There are multiple reasons why I use hplip:
> 
>  * First of all, I'm a visual-impaired guy and I help many other
>visual-impaired people using Debian, so the consequence we couldn't
>use the printer screen, we rely exclusively on HP Toolbox to get
>informations such as the status, the cartridge level, etc.
>  * To configure our printer to work on WIFI, we use hp-setup
> 
> Can I do the same with DriverlessPrinting?

As someone who has given a fair bit of help to other users I have
abandoned advising any use of vendor solutions (free or non-free) for
setting up a print queue with a modern printer. To my knowledge the
number of dissatisfied customers is zero :).

Alex, I would urge you to trial setting up queues for the printers you
have available. Personally, I always use lpadmin; two commands and this
fundamental job is done for a network connection. An alternative is to
rely on the auto-setup feature of cups-browsed.

  https://wiki.debian.org/DriverlessPrinting#shortlpadmin

There is also a big advantage in not having to deal with HP non-free
plugins. The amount of trouble they can give during an installation
is a pain.

Ink levels are generally shown in the Embedded Web Interface (EWS). I
do not comment on "status" because I am unsure what it involves.

> It seems sane-airscan is not available on Debian 10, only on Debian 11.

Alex Pevzner provides packages for Debian 10. I use one very successfully.

  https://download.opensuse.org/repositories/home:/pzz/Debian_10/

Cheers,

Brian.



Bug#972089: Backport hplip 3.20.5 to buster-backports

2020-10-13 Thread Alex ARNAUD

Hello Didier,

Thanks for your quick answer.

There are multiple reasons why I use hplip:

 * First of all, I'm a visual-impaired guy and I help many other
   visual-impaired people using Debian, so the consequence we couldn't
   use the printer screen, we rely exclusively on HP Toolbox to get
   informations such as the status, the cartridge level, etc.
 * To configure our printer to work on WIFI, we use hp-setup

Can I do the same with DriverlessPrinting?

It seems sane-airscan is not available on Debian 10, only on Debian 11.

Thanks in advance.

Le 12/10/2020 à 21:15, Didier 'OdyX' Raboud a écrit :

Hello Alex, and thanks for your bugreport,

Thankfully, now with driverless printing [0] and sane-airscan [1], printers
such as yours shouldn't need hplip anymore. (Also, hplip's code quality isn't
monotonously upwards, so printing without hplip is often a preferable option).
That said, the situation in sid and bullseye (current testing) is likely much
better in these respects than in buster. Could you maybe test driverless
printing, and/or sane-airscan?

As for the backporting; thank you for the patch removal proposals. As I've
just uploaded 3.20.9+dfsg0-3 to unstable; it should migrate to testing in
about 5-10 days, so , if your testing isn't successful, I'll prepare a 3.20.9
backport. I'm testing a build as I write this.

Please report the results of your tests if you have the occasion.

Best regards, and thanks for your work!

Cheers,
OdyX



[0] https://wiki.debian.org/DriverlessPrinting
[1] https://github.com/alexpevzner/sane-airscan

Le lundi, 12 octobre 2020, 15.10:35 h CEST Alex ARNAUD a écrit :

Package: hplip
Severity: wishlist patch
Tags: ||buster||

Hello,

Why I'd like this to be backported to buster-backports ?
My new printer, an HP 2700 series is only compatible with HP Lip
3.20.5+. This is based on my own tests where only half of printed pages
are printed. This is also based on the upstream table
 where it is indicated the "HP DeskJet 2700 All-in-One Printer series"
is compatible with 3.20.5.

What did I already do to figure this out?
With the help of Samuel Thibault, I was able to recompile HP Lip 3.20.5
on a Buster virtual machine and I produced two patch for it. The patches
are attached to this mail. One is to update the debian/patches/series
file and the second one is to refresh the patch 0072 (just a quilt
refresh on it). I initially would like to propose a pull request on
Salsa but there is no branch to submit the changes.

What my patch does?
It reverts all the python3.8 specific patches because Debian Buster is
based on Python 3.7 and because python3.7 library is named "python3.7m",
not only python3.7.

What I think HP Lip should be backported to buster-backports?
I think it'd be really helpful for people would like to stay on stable
with new HP printers which require new HP Lip to have a new version in
backports.

How do I check if it works?

1. I upgraded the compiled packages with the following command:

sudo dpkg -iO .../*.deb

2) I rebooted my virtual machine to ensure the new HP Lip version is loaded

3) I configured my HP Desktop 3630 printer (launched with
system-config-printer)

4) I tried a print test job launched with system-config-printer

5) I tried a scan with simple-scan

Result:
Everything seems to work correctly.

Thanks in advance,
Alex.






Bug#972089: Backport hplip 3.20.5 to buster-backports

2020-10-12 Thread Didier 'OdyX' Raboud
Hello Alex, and thanks for your bugreport,

Thankfully, now with driverless printing [0] and sane-airscan [1], printers 
such as yours shouldn't need hplip anymore. (Also, hplip's code quality isn't 
monotonously upwards, so printing without hplip is often a preferable option). 
That said, the situation in sid and bullseye (current testing) is likely much 
better in these respects than in buster. Could you maybe test driverless 
printing, and/or sane-airscan?

As for the backporting; thank you for the patch removal proposals. As I've 
just uploaded 3.20.9+dfsg0-3 to unstable; it should migrate to testing in 
about 5-10 days, so , if your testing isn't successful, I'll prepare a 3.20.9 
backport. I'm testing a build as I write this.

Please report the results of your tests if you have the occasion.

Best regards, and thanks for your work!

Cheers,
OdyX



[0] https://wiki.debian.org/DriverlessPrinting
[1] https://github.com/alexpevzner/sane-airscan

Le lundi, 12 octobre 2020, 15.10:35 h CEST Alex ARNAUD a écrit :
> Package: hplip
> Severity: wishlist patch
> Tags: ||buster||
> 
> Hello,
> 
> Why I'd like this to be backported to buster-backports ?
> My new printer, an HP 2700 series is only compatible with HP Lip
> 3.20.5+. This is based on my own tests where only half of printed pages
> are printed. This is also based on the upstream table
>  ndex> where it is indicated the "HP DeskJet 2700 All-in-One Printer series"
> is compatible with 3.20.5.
> 
> What did I already do to figure this out?
> With the help of Samuel Thibault, I was able to recompile HP Lip 3.20.5
> on a Buster virtual machine and I produced two patch for it. The patches
> are attached to this mail. One is to update the debian/patches/series
> file and the second one is to refresh the patch 0072 (just a quilt
> refresh on it). I initially would like to propose a pull request on
> Salsa but there is no branch to submit the changes.
> 
> What my patch does?
> It reverts all the python3.8 specific patches because Debian Buster is
> based on Python 3.7 and because python3.7 library is named "python3.7m",
> not only python3.7.
> 
> What I think HP Lip should be backported to buster-backports?
> I think it'd be really helpful for people would like to stay on stable
> with new HP printers which require new HP Lip to have a new version in
> backports.
> 
> How do I check if it works?
> 
> 1. I upgraded the compiled packages with the following command:
> > sudo dpkg -iO .../*.deb
> 
> 2) I rebooted my virtual machine to ensure the new HP Lip version is loaded
> 
> 3) I configured my HP Desktop 3630 printer (launched with
> system-config-printer)
> 
> 4) I tried a print test job launched with system-config-printer
> 
> 5) I tried a scan with simple-scan
> 
> Result:
> Everything seems to work correctly.
> 
> Thanks in advance,
> Alex.


-- 
OdyX

signature.asc
Description: This is a digitally signed message part.


Bug#972089: Backport hplip 3.20.5 to buster-backports

2020-10-12 Thread Alex ARNAUD
I just re-generated the two patches with the option "-u" to diff to make 
them more readable.


Le 12/10/2020 à 15:10, Alex ARNAUD a écrit :

Package: hplip
Severity: wishlist patch
Tags: ||buster||

Hello,

Why I'd like this to be backported to buster-backports ?
My new printer, an HP 2700 series is only compatible with HP Lip 
3.20.5+. This is based on my own tests where only half of printed 
pages are printed. This is also based on the upstream table 
 
where it is indicated the "HP DeskJet 2700 All-in-One Printer series" 
is compatible with 3.20.5.


What did I already do to figure this out?
With the help of Samuel Thibault, I was able to recompile HP Lip 
3.20.5 on a Buster virtual machine and I produced two patch for it. 
The patches are attached to this mail. One is to update the 
debian/patches/series file and the second one is to refresh the patch 
0072 (just a quilt refresh on it). I initially would like to propose a 
pull request on Salsa but there is no branch to submit the changes.


What my patch does?
It reverts all the python3.8 specific patches because Debian Buster is 
based on Python 3.7 and because python3.7 library is named 
"python3.7m", not only python3.7.


What I think HP Lip should be backported to buster-backports?
I think it'd be really helpful for people would like to stay on stable 
with new HP printers which require new HP Lip to have a new version in 
backports.


How do I check if it works?
1. I upgraded the compiled packages with the following command:

sudo dpkg -iO .../*.deb


2) I rebooted my virtual machine to ensure the new HP Lip version is 
loaded


3) I configured my HP Desktop 3630 printer (launched with 
system-config-printer)


4) I tried a print test job launched with system-config-printer

5) I tried a scan with simple-scan

Result:
Everything seems to work correctly.

Thanks in advance,
Alex.



--- ../hplip-3.20.5+dfsg0.orig/debian/patches/series	2020-10-12 14:43:13.346892324 +0200
+++ debian/patches/series	2020-10-12 14:47:20.678512933 +0200
@@ -68,7 +68,4 @@
 0068-abrt-hplip-strlen-hp-killed-by-SIGSEGV.patch
 0069-abrt-hp-systray-BlockingIOError-Errno-11-Resource-te.patch
 0070-Missing-drivers.patch
-0071-Fix-building-with-Python-3.8.patch
 0072-Fix-upstream-CFLAGS-override.patch
-0073-py3.8-Fix-SyntaxWarning-is-is-not-with-a-literal.patch
-0074-py3.8-Assume-the-python3-distro-package-is-available.patch
--- ../hplip-3.20.5+dfsg0.orig/debian/patches/0072-Fix-upstream-CFLAGS-override.patch	2020-10-12 14:43:13.346892324 +0200
+++ debian/patches/0072-Fix-upstream-CFLAGS-override.patch	2020-10-12 14:44:03.893473185 +0200
@@ -10,11 +10,11 @@
  configure.in | 36 +++-
  1 file changed, 23 insertions(+), 13 deletions(-)
 
-diff --git a/configure.in b/configure.in
-index 7f6982c..ced1f47 100755
 a/configure.in
-+++ b/configure.in
-@@ -604,20 +604,31 @@ if test "$class_driver" = "no" && test "$hpijs_only_build" = "no" && test "$hpcu
+Index: hplip-3.20.5+dfsg0/configure.in
+===
+--- hplip-3.20.5+dfsg0.orig/configure.in
 hplip-3.20.5+dfsg0/configure.in
+@@ -604,20 +604,31 @@ if test "$class_driver" = "no" && test "
 fi
  fi
  
@@ -58,9 +58,9 @@
  if test "$class_driver" = "no" && test "$hpijs_only_build" = "no" && test "$lite_build" = "no" && test "$hpcups_only_build" = "no"; then
 AC_ARG_VAR([PYTHON], [Python interpreter/compiler command])
 AM_PATH_PYTHON([2.2])
-@@ -633,7 +644,6 @@ if test "$class_driver" = "no" && test "$hpijs_only_build" = "no" && test "$lite
+@@ -630,7 +641,6 @@ if test "$class_driver" = "no" && test "
+AS_IF([test "x$FOUND_HEADER" != "xyes"],
[AC_MSG_ERROR([cannot find python-devel support], 6)])
-CPPFLAGS=$save_CPPFLAGS
  fi
 -CFLAGS="$save_CFLAGS"
  


Bug#972089: Backport hplip 3.20.5 to buster-backports

2020-10-12 Thread Alex ARNAUD

Package: hplip
Severity: wishlist patch
Tags: ||buster||

Hello,

Why I'd like this to be backported to buster-backports ?
My new printer, an HP 2700 series is only compatible with HP Lip 
3.20.5+. This is based on my own tests where only half of printed pages 
are printed. This is also based on the upstream table 
 
where it is indicated the "HP DeskJet 2700 All-in-One Printer series" is 
compatible with 3.20.5.


What did I already do to figure this out?
With the help of Samuel Thibault, I was able to recompile HP Lip 3.20.5 
on a Buster virtual machine and I produced two patch for it. The patches 
are attached to this mail. One is to update the debian/patches/series 
file and the second one is to refresh the patch 0072 (just a quilt 
refresh on it). I initially would like to propose a pull request on 
Salsa but there is no branch to submit the changes.


What my patch does?
It reverts all the python3.8 specific patches because Debian Buster is 
based on Python 3.7 and because python3.7 library is named "python3.7m", 
not only python3.7.


What I think HP Lip should be backported to buster-backports?
I think it'd be really helpful for people would like to stay on stable 
with new HP printers which require new HP Lip to have a new version in 
backports.


How do I check if it works?
1. I upgraded the compiled packages with the following command:

sudo dpkg -iO .../*.deb


2) I rebooted my virtual machine to ensure the new HP Lip version is loaded

3) I configured my HP Desktop 3630 printer (launched with 
system-config-printer)


4) I tried a print test job launched with system-config-printer

5) I tried a scan with simple-scan

Result:
Everything seems to work correctly.

Thanks in advance,
Alex.

71d70
< 0071-Fix-building-with-Python-3.8.patch
73,74d71
< 0073-py3.8-Fix-SyntaxWarning-is-is-not-with-a-literal.patch
< 0074-py3.8-Assume-the-python3-distro-package-is-available.patch
13,17c13,17
< diff --git a/configure.in b/configure.in
< index 7f6982c..ced1f47 100755
< --- a/configure.in
< +++ b/configure.in
< @@ -604,20 +604,31 @@ if test "$class_driver" = "no" && test "$hpijs_only_build" = "no" && test "$hpcu
---
> Index: hplip-3.20.5+dfsg0/configure.in
> ===
> --- hplip-3.20.5+dfsg0.orig/configure.in
> +++ hplip-3.20.5+dfsg0/configure.in
> @@ -604,20 +604,31 @@ if test "$class_driver" = "no" && test "
61c61,62
< @@ -633,7 +644,6 @@ if test "$class_driver" = "no" && test "$hpijs_only_build" = "no" && test "$lite
---
> @@ -630,7 +641,6 @@ if test "$class_driver" = "no" && test "
> AS_IF([test "x$FOUND_HEADER" != "xyes"],
63d63
< CPPFLAGS=$save_CPPFLAGS