[PATCH] gnu: libusb update to 1.0.26

  • Open
  • quality assurance status badge
Details
2 participants
  • Andreas Enge
  • Rick Huijzer
Owner
unassigned
Submitted by
Rick Huijzer
Severity
normal
R
R
Rick Huijzer wrote on 10 Jul 10:39 +0200
(address . guix-patches@gnu.org)(name . Rick Huijzer)(address . r.huijzer@dca-ict.nl)
20240710084001.3514-1-ikbenrickhuyzer@gmail.com
From: Rick Huijzer <r.huijzer@dca-ict.nl>

---
gnu/packages/libusb.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Toggle diff (26 lines)
diff --git a/gnu/packages/libusb.scm b/gnu/packages/libusb.scm
index d5157a6eeb..d804f0d882 100644
--- a/gnu/packages/libusb.scm
+++ b/gnu/packages/libusb.scm
@@ -66,7 +66,7 @@ (define-module (gnu packages libusb)
(define-public libusb
(package
(name "libusb")
- (version "1.0.25")
+ (version "1.0.26")
(source
(origin
(method url-fetch)
@@ -74,7 +74,7 @@ (define-public libusb
"releases/download/v" version
"/libusb-" version ".tar.bz2"))
(sha256
- (base32 "0j88ym7afy4wj3x789zzxsr04asyjy0mw29gf31blzkrg8cyya4a"))))
+ (base32 "19dmh41m0iks0vk5khlml3drvhgsnpvrbq7zl79d2m4qzihpmkhj"))))
(build-system gnu-build-system)
;; XXX: Enabling udev is now recommended, but eudev indirectly depends on

base-commit: 71694363f6cc79e44955acbd9f7ca108e658caca
--
2.45.2
A
A
Andreas Enge wrote on 11 Jul 19:15 +0200
QA
(address . 72032@debbugs.gnu.org)
ZpATM2MrvPbHumgM@jurong
Hello,

thanks for the patch! Unfortunately changing libusb requires rebuilding
more than 3000 packages ("guix refresh -l libusb"). So this should be done
in a concerted effort, probably after regrouping with a few other packages.

I would suggest to wait with this until core-updates is merged (which does
not contain the newer libusb version yet).

Andreas
A
A
Andreas Enge wrote on 11 Jul 19:18 +0200
Block
(address . control@debbugs.gnu.org)
ZpAT5A8L_dPrGplw@jurong
block 72033 by 72032
thanks
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 72032@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 72032
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch