From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: hplip: update to 3.22.6.
Date: Wed, 28 Sep 2022 16:01:00 +0200 [thread overview]
Message-ID: <20220928140100.khssd-R37c4URbRHWE-ULjZ_WIgON6mnq8E_AEVnvxQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39146@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
There's a closed pull request on the void-packages repository
hplip: update to 3.22.6.
https://github.com/void-linux/void-packages/pull/39146
Description:
* Remove 1 patch and add 1 build dependency
* Tested both packages with hplip-scan & xsane on HP Neverstop Laser MFP 120x.
* Continue from PR hplip: update to 3.22.6 #37287
I've split the former PR into two separate branches to make sure at least hplip gets updated.
The corresponding `hplip-plugin` PR is #39147.
#### Testing the changes
- I tested the changes in this PR: **YES - tested by @biopsin and myself**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl (crossbuild)
- armv7l (crossbuild)
- armv6l-musl (crossbuild)
prev parent reply other threads:[~2022-09-28 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 8:51 [PR PATCH] " dataCobra
2022-09-07 8:52 ` [PR PATCH] [Updated] " dataCobra
2022-09-14 4:27 ` dataCobra
2022-09-14 4:52 ` [PR PATCH] [Updated] " dataCobra
2022-09-21 9:07 ` dataCobra
2022-09-21 9:08 ` dataCobra
2022-09-21 10:45 ` [PR REVIEW] " ahesford
2022-09-21 10:45 ` ahesford
2022-09-21 11:01 ` dataCobra
2022-09-21 11:01 ` dataCobra
2022-09-28 12:39 ` [PR PATCH] [Updated] " dataCobra
2022-09-28 12:40 ` dataCobra
2022-09-28 14:01 ` ahesford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220928140100.khssd-R37c4URbRHWE-ULjZ_WIgON6mnq8E_AEVnvxQ@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).