From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-process/psinfo/
Date: Mon, 26 Sep 2022 12:27:33 +0000 (UTC) [thread overview]
Message-ID: <1664195174.2e82ad643d809c8ac1cb5b92e46c10344e3c6be5.sam@gentoo> (raw)
commit: 2e82ad643d809c8ac1cb5b92e46c10344e3c6be5
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Sep 26 12:26:14 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Sep 26 12:26:14 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2e82ad64
sys-process/psinfo: revbump for unsigned char fix
it's only keyworded on amd64/x86, but it affects runtime and it'll
avoid confusion if any say, arm users have been using it (or trying to).
Closes: https://bugs.gentoo.org/872821
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-process/psinfo/psinfo-0.12-r1.ebuild | 1 -
sys-process/psinfo/{psinfo-0.12-r1.ebuild => psinfo-0.12-r2.ebuild} | 0
2 files changed, 1 deletion(-)
diff --git a/sys-process/psinfo/psinfo-0.12-r1.ebuild b/sys-process/psinfo/psinfo-0.12-r1.ebuild
index fdf62188a826..033fcddb450b 100644
--- a/sys-process/psinfo/psinfo-0.12-r1.ebuild
+++ b/sys-process/psinfo/psinfo-0.12-r1.ebuild
@@ -15,7 +15,6 @@ LICENSE="GPL-2"
PATCHES=(
"${FILESDIR}/${P}-asneeded.patch"
- "${FILESDIR}/${P}-char.patch"
)
src_prepare() {
diff --git a/sys-process/psinfo/psinfo-0.12-r1.ebuild b/sys-process/psinfo/psinfo-0.12-r2.ebuild
similarity index 100%
copy from sys-process/psinfo/psinfo-0.12-r1.ebuild
copy to sys-process/psinfo/psinfo-0.12-r2.ebuild
next reply other threads:[~2022-09-26 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 12:27 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-27 4:13 [gentoo-commits] repo/gentoo:master commit in: sys-process/psinfo/ Yixun Lan
2020-06-21 7:31 Patrice Clement
2020-06-21 7:31 Patrice Clement
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=1664195174.2e82ad643d809c8ac1cb5b92e46c10344e3c6be5.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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