Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] dua-cli: update to 2.23.0.
Date: Sat, 16 Dec 2023 10:09:29 +0100	[thread overview]
Message-ID: <20231216090929.je9dEa25ukdYe_k35Y_bMKnRKMLn3aOSDJ5DRgDs9w0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47774@inbox.vuxu.org>

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

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

https://github.com/jcgruenhage/void-packages dua-cli-2.23.0_1
https://github.com/void-linux/void-packages/pull/47774

dua-cli: update to 2.23.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### 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
  - armv7l
  - armv6l-musl
-->


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-dua-cli-2.23.0_1-47774.patch --]
[-- Type: text/x-diff, Size: 2725 bytes --]

From c40d1b6656a6842a22e47f350dd260e07e7bd8eb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
 <jan.christian@gruenhage.xyz>
Date: Fri, 15 Dec 2023 19:58:27 +0100
Subject: [PATCH] dua-cli: update to 2.23.0.

---
 ...yData-size-test-passes-on-32-bit-197.patch | 33 +++++++++++++++++++
 srcpkgs/dua-cli/template                      |  4 +--
 2 files changed, 35 insertions(+), 2 deletions(-)
 create mode 100644 srcpkgs/dua-cli/patches/0001-fix-EntryData-size-test-passes-on-32-bit-197.patch

diff --git a/srcpkgs/dua-cli/patches/0001-fix-EntryData-size-test-passes-on-32-bit-197.patch b/srcpkgs/dua-cli/patches/0001-fix-EntryData-size-test-passes-on-32-bit-197.patch
new file mode 100644
index 0000000000000..9a7154e097522
--- /dev/null
+++ b/srcpkgs/dua-cli/patches/0001-fix-EntryData-size-test-passes-on-32-bit-197.patch
@@ -0,0 +1,33 @@
+From 392e808ebae97faecdaadf044c7ebd112b82cc94 Mon Sep 17 00:00:00 2001
+From: cinerea0 <cinerea0@disroot.org>
+Date: Mon, 11 Dec 2023 14:51:53 -0500
+Subject: [PATCH] fix: EntryData size test passes on 32-bit (#197)
+
+EntryData doesn't need to be exactly 80 to test memory consumption, just
+less than it.
+---
+ src/traverse.rs | 8 ++++----
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/src/traverse.rs b/src/traverse.rs
+index 157ce2c..b2c8724 100644
+--- a/src/traverse.rs
++++ b/src/traverse.rs
+@@ -312,10 +312,10 @@ mod tests {
+ 
+     #[test]
+     fn size_of_entry_data() {
+-        assert_eq!(
+-            std::mem::size_of::<EntryData>(),
+-            80,
+-            "the size of this should not change unexpectedly as it affects overall memory consumption"
++        assert!(
++            std::mem::size_of::<EntryData>() <= 80,
++            "the size of this ({}) should not exceed 80 as it affects overall memory consumption",
++            std::mem::size_of::<EntryData>()
+         );
+     }
+ }
+-- 
+2.43.0
+
diff --git a/srcpkgs/dua-cli/template b/srcpkgs/dua-cli/template
index 327aa1247a183..1be4fd8325d4c 100644
--- a/srcpkgs/dua-cli/template
+++ b/srcpkgs/dua-cli/template
@@ -1,6 +1,6 @@
 # Template file for 'dua-cli'
 pkgname=dua-cli
-version=2.20.3
+version=2.23.0
 revision=1
 build_style=cargo
 short_desc="Tool to conveniently learn about the disk usage of directories"
@@ -9,7 +9,7 @@ license="MIT"
 homepage="https://github.com/Byron/dua-cli"
 changelog="https://raw.githubusercontent.com/Byron/dua-cli/main/CHANGELOG.md"
 distfiles="https://github.com/Byron/dua-cli/archive/refs/tags/v${version}.tar.gz"
-checksum=b526c8c43853943f025ba36bf7297fbd9b1beb395ad92e70c41fed7d8d584be7
+checksum=61f6fd0c13949d23224d9776c2fd444956d73dd363501e867cf11df6ca89ddfa
 
 post_install() {
 	vlicense LICENSE

  parent reply	other threads:[~2023-12-16  9:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15 18:58 [PR PATCH] " jcgruenhage
2023-12-15 19:11 ` cinerea0
2023-12-15 19:13 ` [PR PATCH] [Closed]: " jcgruenhage
2023-12-15 19:13 ` jcgruenhage
2023-12-15 19:14 ` cinerea0
2023-12-15 19:19 ` jcgruenhage
2023-12-15 19:23 ` [PR PATCH] [Updated] " jcgruenhage
2023-12-16  9:04 ` jcgruenhage
2023-12-16  9:09 ` jcgruenhage [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-06 20:35 [PR PATCH] dua-cli: update to 2.21.0 cinerea0
2023-12-11 19:21 ` [PR PATCH] [Updated] dua-cli: update to 2.23.0 cinerea0

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=20231216090929.je9dEa25ukdYe_k35Y_bMKnRKMLn3aOSDJ5DRgDs9w0@z \
    --to=jcgruenhage@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).