[PATCH] gnu: rust-lock-api-0.4: Update to 0.4.6.

  • Open
  • quality assurance status badge
Details
One participant
  • Reza Alizadeh Majd
Owner
unassigned
Submitted by
Reza Alizadeh Majd
Severity
normal
R
R
Reza Alizadeh Majd wrote on 18 Dec 2022 10:47
(address . guix-patches@gnu.org)(name . Reza Alizadeh Majd)(address . r.majd@pantherx.org)
20221218094741.31403-1-r.majd@pantherx.org
* gnu/packages/crates-io.scm (rust-lock-api-0.4): Update to 0.4.6.
---
gnu/packages/crates-io.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Toggle diff (24 lines)
diff --git a/gnu/packages/crates-io.scm b/gnu/packages/crates-io.scm
index f0f40207b9..f822b6856b 100644
--- a/gnu/packages/crates-io.scm
+++ b/gnu/packages/crates-io.scm
@@ -31037,7 +31037,7 @@ (define-public rust-locale-config-0.3
(define-public rust-lock-api-0.4
(package
(name "rust-lock-api")
- (version "0.4.5")
+ (version "0.4.6")
(source
(origin
(method url-fetch)
@@ -31045,7 +31045,7 @@ (define-public rust-lock-api-0.4
(file-name (string-append name "-" version ".tar.gz"))
(sha256
(base32
- "028izfyraynijd9h9x5miv1vmg6sjnw1v95wgm7f4xlr7h4lsaki"))))
+ "0frbbqqiwngg33xrc69xagi4rqqk62msllr7z95mlbjaxzbkv548"))))
(build-system cargo-build-system)
(arguments
`(#:cargo-inputs
--
2.37.1
R
R
Reza Alizadeh Majd wrote on 18 Dec 2022 11:32
(address . 60174@debbugs.gnu.org)
9ddb8a85-3077-47fa-8e27-f1962e53a880@app.fastmail.com
after updating the following packages:

- rust-tokio-1 from `1.15.0` to `1.22.0`[1]
- `rust-parking-lot-0.11` package to `rust-parking-lot-0.12`[2]

build fails for the packages that use these two as dependency: https://ci.guix.gnu.org/build/222062/details

since `rust-parking-lot-0.12` depends on the `lock_api@^0.4.6` crate[3], I submitted this patch and updated the `rust-lock-api` package to `0.4.6`:



--
Reza Alizadeh Majd
PantherX Team
?
Your comment

Commenting via the web interface is currently disabled.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 60174
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