Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] zet: fix for rust-178
Date: Fri, 03 May 2024 21:33:10 +0200	[thread overview]
Message-ID: <20240503193310.5FDC7217D8@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50180@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 469 bytes --]

There is an updated pull request by icp1994 against master on the void-packages repository

https://github.com/icp1994/void-packages zet
https://github.com/void-linux/void-packages/pull/50180

zet: fix for rust-178
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture: **x86_64**

A patch file from https://github.com/void-linux/void-packages/pull/50180.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-zet-50180.patch --]
[-- Type: text/x-diff, Size: 1854 bytes --]

From f0f34c25e0c4c0194aaafca1d0a93156de64a3fe Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Sat, 4 May 2024 00:19:39 +0530
Subject: [PATCH] zet: fix for rust-178

---
 srcpkgs/zet/patches/fix-rust178.patch | 23 +++++++++++++++++++++++
 srcpkgs/zet/template                  |  2 +-
 2 files changed, 24 insertions(+), 1 deletion(-)
 create mode 100644 srcpkgs/zet/patches/fix-rust178.patch

diff --git a/srcpkgs/zet/patches/fix-rust178.patch b/srcpkgs/zet/patches/fix-rust178.patch
new file mode 100644
index 00000000000000..839a4113995b4c
--- /dev/null
+++ b/srcpkgs/zet/patches/fix-rust178.patch
@@ -0,0 +1,23 @@
+From b6a0c67f6ac76fb7bf8234951678b77fbac12d76 Mon Sep 17 00:00:00 2001
+From: Yarrow Angelweed <yarrow.angelweed@gmail.com>
+Date: Wed, 6 Mar 2024 12:17:38 -0500
+Subject: [PATCH] Take nightly clippy advice
+
+---
+ src/help.rs | 3 +--
+ 1 file changed, 1 insertion(+), 2 deletions(-)
+
+diff --git a/src/help.rs b/src/help.rs
+index 23c79aa..0e8c3c3 100644
+--- a/src/help.rs
++++ b/src/help.rs
+@@ -123,8 +123,7 @@ impl<'a> Section<'a> {
+         Ok(0)
+     }
+     fn next_line_help_indent(&self) -> &'a str {
+-        let max_indent =
+-            self.entries.iter().map(|e| e.item.indented_by()).fold(0, std::cmp::Ord::max);
++        let max_indent = self.entries.iter().map(|e| e.item.indented_by()).fold(0, Ord::max);
+         let indent_len = (max_indent + 4).min(BLANKS.len());
+         &BLANKS[..indent_len]
+     }
diff --git a/srcpkgs/zet/template b/srcpkgs/zet/template
index 86c2fdad2b295c..e1d88e28136d53 100644
--- a/srcpkgs/zet/template
+++ b/srcpkgs/zet/template
@@ -1,7 +1,7 @@
 # Template file for 'zet'
 pkgname=zet
 version=1.0.0
-revision=1
+revision=2
 build_style=cargo
 short_desc="CLI to find union, intersection, set difference, etc of files"
 maintainer="icp <pangolin@vivaldi.net>"

  reply	other threads:[~2024-05-03 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 18:54 [PR PATCH] " icp1994
2024-05-03 19:33 ` icp1994 [this message]
2024-05-07  6:30 ` [PR PATCH] [Merged]: " classabbyamp

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=20240503193310.5FDC7217D8@inbox.vuxu.org \
    --to=icp1994@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).