Re: Issue trying to rebuild the hplip deb package
Hello,
I have subscribed to debian-printing for the occasion.
I have followed the steps you have described, resulting in this merge
request:
https://salsa.debian.org/printing-team/hplip/-/merge_requests/2
Could you please have a look?
================
There's something that puzzles me though: you said that the branch is
"patches-applied", but you also said to do only this commit:
git add -A ./debian/patches
which, to me, sound like the patches are present but not applied?
================
Another think puzzles me: the patch
0001-models.dat-Fix-scanning-with-M281fdw-LaserJet.patch
indicates
@@ -61924,8 +61924,8 @@
monitor-type=0
panel-check-type=0
pcard-type=0
-plugin=0
-plugin-reason=0
+plugin=1
+plugin-reason=64
power-settings=0
ppd-name=hp-color_laserjet_mfp_m278-m281-ps.ppd
which means changes at around line 61924, but the
"ppd-name=hp-color_laserjet_mfp_m278-m281-ps.ppd" is really at line
62466 of the actual upstream file. I can see in the upstream file that
the patch is indeed applied, but shouldn't the patchfile nevertheless be
refreshed or updated, to target the correct line and apply cleanly?
Don't Debian's buildd/sbuild builders complain when they build the
package?
Thanks!
Didier 'OdyX' Raboud <odyx@debian.org> writes:
> Also, please be made aware of the current Debian freeze; that is not
> likely to make it into Debian bullseye, but for the longer future, it
> will!
If this fix is accepted in unstable, and I prepare a backport/update for
bullseye, do you think there is a chance that this backport would be
accepted into a bullseye point release?
Thanks!
Best regards
--
Fabrice Bauzac-Stehly
PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6
old PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Reply to: