Github messages for voidlinux
 help / color / mirror / Atom feed
From: realcharmer <realcharmer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] inxi: update to 3.3.26
Date: Sat, 01 Apr 2023 15:12:17 +0200	[thread overview]
Message-ID: <20230401131217.hwZ7PcsAr3K3NlmiqSmrhxNq8qUhC_LQRsaHNjQQJQI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43160@inbox.vuxu.org>

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

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

https://github.com/realcharmer/void-packages inxi
https://github.com/void-linux/void-packages/pull/43160

inxi: update to 3.3.26
#### 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/43160.patch is attached

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

From 5a38ce43892cde6fdeaad42492f2ce01a448bdd2 Mon Sep 17 00:00:00 2001
From: Emil Miler <em@0x45.cz>
Date: Sat, 1 Apr 2023 13:27:31 +0200
Subject: [PATCH] inxi: update to 3.3.26

---
 srcpkgs/inxi/template | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/inxi/template b/srcpkgs/inxi/template
index 349225861087..302777ceab02 100644
--- a/srcpkgs/inxi/template
+++ b/srcpkgs/inxi/template
@@ -1,7 +1,8 @@
 # Template file for 'inxi'
 pkgname=inxi
-version=3.3.25
+version=3.3.26.1
 revision=1
+_distver="${version%.*}-${version##*.}"
 depends="dmidecode file glxinfo pciutils perl procps-ng usbutils xdpyinfo
  xprop xrandr"
 short_desc="Full featured system information script"
@@ -9,8 +10,8 @@ maintainer="Emil Miler <em@0x45.cz>"
 license="GPL-3.0-or-later"
 homepage="https://smxi.org/docs/inxi.htm"
 changelog="https://raw.githubusercontent.com/smxi/inxi/master/inxi.changelog"
-distfiles="https://github.com/smxi/inxi/archive/refs/tags/${version}-1.tar.gz"
-checksum=17176e70516adae4adced317905ab759316e5658a55c4a002c130bbcc21af3b7
+distfiles="https://github.com/smxi/inxi/archive/refs/tags/${_distver}.tar.gz"
+checksum=9c76b90044a5840d9e32fd83d1b3c1bb0d7c39c89904ac387cf6be339785451e
 
 do_install() {
 	vbin inxi

  parent reply	other threads:[~2023-04-01 13:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01 11:30 [PR PATCH] " realcharmer
2023-04-01 11:31 ` [PR REVIEW] " realcharmer
2023-04-01 11:32 ` realcharmer
2023-04-01 12:39 ` mhmdanas
2023-04-01 12:39 ` mhmdanas
2023-04-01 12:41 ` mhmdanas
2023-04-01 13:10 ` [PR PATCH] [Updated] " realcharmer
2023-04-01 13:12 ` realcharmer [this message]
2023-04-01 13:14 ` [PR REVIEW] " realcharmer
2023-04-01 13:16 ` mhmdanas
2023-04-01 13:18 ` [PR PATCH] [Updated] " realcharmer
2023-04-01 13:20 ` [PR REVIEW] inxi: update to 3.3.26.1 realcharmer
2023-04-01 13:20 ` realcharmer
2023-04-01 13:39 ` mhmdanas
2023-04-01 13:39 ` mhmdanas
2023-04-01 21:13 ` [PR PATCH] [Merged]: " Chocimier

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=20230401131217.hwZ7PcsAr3K3NlmiqSmrhxNq8qUhC_LQRsaHNjQQJQI@z \
    --to=realcharmer@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).