From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] procps: Version bump. 4.0.5 -> 4.0.6
Date: Fri, 13 Feb 2026 11:02:57 +0100 [thread overview]
Message-ID: <20260213100257.2786027-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260201193551.3584489-1-christian.melki@t2data.com>
Thanks, applied as 44d9790977e3e6f0beb42fe5248c3c04159b7835.
Michael
[sent from post-receive hook]
On Fri, 13 Feb 2026 11:02:57 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> https://gitlab.com/procps-ng/procps/-/releases/v4.0.6
>
> * Adjust build options that have appeared.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260201193551.3584489-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/procps.make b/rules/procps.make
> index 79ecaf927833..9714d2a966c8 100644
> --- a/rules/procps.make
> +++ b/rules/procps.make
> @@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_PROCPS) += procps
> #
> # Paths and names
> #
> -PROCPS_VERSION := 4.0.5
> -PROCPS_MD5 := 90803e64f51f192f3325d25c3335d057
> +PROCPS_VERSION := 4.0.6
> +PROCPS_MD5 := 20c23dc3dd1569a2bb1d1fa93de213ed
> PROCPS := procps-ng-$(PROCPS_VERSION)
> PROCPS_SUFFIX := tar.xz
> PROCPS_URL := $(call ptx/mirror, SF, procps-ng/Production/$(PROCPS).$(PROCPS_SUFFIX))
> @@ -41,10 +41,12 @@ PROCPS_CONF_OPT := \
> $(CROSS_AUTOCONF_USR) \
> $(GLOBAL_LARGE_FILE_OPTION) \
> --disable-nls \
> + --disable-assert \
> --enable-shared \
> --disable-static \
> --disable-rpath \
> --disable-watch8bit \
> + --disable-colorwatch \
> --disable-libselinux \
> --disable-harden-flags \
> --$(call ptx/endis, PTXCONF_PROCPS_PIDOF)-pidof \
prev parent reply other threads:[~2026-02-13 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 19:35 [ptxdist] [PATCH] " Christian Melki
2026-02-13 10:02 ` Michael Olbrich [this message]
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=20260213100257.2786027-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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