Your message dated Fri, 06 Nov 2020 15:08:38 +0100
with message-id <5406974.dvuyhmx...@odyx.org>
and subject line Re: Bug#972089: Backport hplip 3.20.5 to buster-backports
has caused the Debian Bug report #972089,
regarding Backport hplip 3.20.5 to buster-backports
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
972089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 <https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/index> 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

--- End Message ---
--- Begin Message ---
Version: 3.20.9+dfsg0-4~bpo10+1

Le jeudi, 15 octobre 2020, 08.33:26 h CET Didier 'OdyX' Raboud a écrit :
> 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.

Hplip backport uploaded, accepted, and built.

sane-airscan is being uploaded currently.


-- 
    OdyX

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


--- End Message ---

Reply via email to