From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] hplip: update to 3.22.10.
Date: Thu, 10 Nov 2022 08:19:33 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40434@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 591 bytes --]
There is a new pull request by dataCobra against master on the void-packages repository
https://github.com/dataCobra/void-packages hplip
https://github.com/void-linux/void-packages/pull/40434
hplip: update to 3.22.10.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl (crossbuild)
A patch file from https://github.com/void-linux/void-packages/pull/40434.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-hplip-40434.patch --]
[-- Type: text/x-diff, Size: 1251 bytes --]
From 8c4e7128749974ccf43c764be54b7149c35f845b Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Thu, 10 Nov 2022 08:16:16 +0100
Subject: [PATCH] hplip: update to 3.22.10.
---
srcpkgs/hplip/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/hplip/template b/srcpkgs/hplip/template
index 063581e4e899..0fd338c7f680 100644
--- a/srcpkgs/hplip/template
+++ b/srcpkgs/hplip/template
@@ -1,7 +1,7 @@
# Template file for 'hplip'
pkgname=hplip
-version=3.22.6
-revision=2
+version=3.22.10
+revision=1
build_style=gnu-configure
pycompile_dirs="usr/share/hplip"
# configure checks sys.version[:3] for Python versioning, so 3.10 becomes 3.1;
@@ -36,7 +36,7 @@ license="GPL-2.0-only, BSD-3-Clause, MIT"
homepage="https://developers.hp.com/hp-linux-imaging-and-printing"
changelog="https://developers.hp.com/hp-linux-imaging-and-printing/release_notes"
distfiles="${SOURCEFORGE_SITE}/hplip/hplip/${version}/hplip-${version}.tar.gz"
-checksum=27ed0d492febb0b47c656234820d3ce573b24ff5b62e3bf4b2c47f82868d6bb4
+checksum=533c3f2f6b53e4163ded4fd81d1f11ae6162a0f6451bd5e62a8382d0c1366624
conflicts="hplip-gui"
CFLAGS="-I${XBPS_CROSS_BASE}/usr/include/libusb-1.0 -I${XBPS_CROSS_BASE}/${py3_inc}"
next reply other threads:[~2022-11-10 7:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 7:19 dataCobra [this message]
2022-11-10 10:11 ` [PR REVIEW] " paper42
2022-11-10 10:38 ` dataCobra
2022-11-10 11:46 ` biopsin
2022-11-11 8:05 ` [PR PATCH] [Updated] " dataCobra
2022-11-11 8:09 ` [PR REVIEW] " dataCobra
2022-11-16 14:07 ` [PR PATCH] [Updated] " dataCobra
2022-11-16 14:26 ` [PR PATCH] [Updated] hplip: update to 3.22.10. + New package: hplip-plugin 3.22.10 dataCobra
2022-11-16 14:27 ` dataCobra
2022-11-16 15:21 ` ahesford
2022-11-16 15:40 ` dataCobra
2022-11-16 15:58 ` biopsin
2022-11-16 16:06 ` ahesford
2022-11-17 12:25 ` biopsin
2022-11-17 12:54 ` biopsin
2022-11-17 13:03 ` paper42
2022-11-17 13:03 ` paper42
2022-11-17 13:17 ` biopsin
2022-11-17 13:23 ` biopsin
2022-11-17 18:57 ` ahesford
2022-11-18 10:36 ` dataCobra
2022-12-18 11:40 ` [PR PATCH] [Updated] " dataCobra
2022-12-18 11:49 ` dataCobra
2022-12-18 12:20 ` dataCobra
2022-12-18 13:52 ` biopsin
2022-12-24 11:15 ` biopsin
2022-12-24 11:15 ` biopsin
2022-12-24 23:27 ` [PR REVIEW] " paper42
2022-12-24 23:27 ` paper42
2022-12-25 1:29 ` ahesford
2022-12-28 7:12 ` [PR PATCH] [Updated] " dataCobra
2022-12-28 8:31 ` [PR REVIEW] " dataCobra
2022-12-28 8:32 ` [PR PATCH] [Updated] " dataCobra
2022-12-28 10:19 ` [PR REVIEW] " dataCobra
2022-12-28 16:05 ` biopsin
2022-12-28 16:36 ` ahesford
2022-12-28 16:36 ` ahesford
2022-12-28 16:36 ` ahesford
2023-01-04 7:44 ` [PR PATCH] [Updated] " dataCobra
2023-01-13 9:08 ` biopsin
2023-01-13 11:30 ` [PR PATCH] [Merged]: " ahesford
2023-01-13 11:46 ` ahesford
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40434@inbox.vuxu.org \
--to=datacobra@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).