mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] procps-ng: Version bump 3.3.17 -> 4.0.3
Date: Mon,  6 Mar 2023 17:21:12 +0100	[thread overview]
Message-ID: <20230306162112.3705319-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230227173331.3592538-1-christian.melki@t2data.com>

Thanks, applied as 269a9ad76864692df19fb21d99a55b2ba1dfc7ba.

Michael

[sent from post-receive hook]

On Mon, 06 Mar 2023 17:21:12 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Approx 2 year worth of changes.
> A major release, afaiu, denoting newlib compatibility.
> A bunch of bugfixes and other stuff.
> Changelog: https://gitlab.com/procps-ng/procps/-/releases
> 
> * Be explicit with configure options.
> * No need to build W if we're not in need of it.
> * Minor whitespace fix.
> * Library renamed to libproc2. This might cause issues
> if anyone is depending on a specific library name and SO library versions.
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230227173331.3592538-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 42fec7bfe9ea..9ed658f70176 100644
> --- a/rules/procps.make
> +++ b/rules/procps.make
> @@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_PROCPS) += procps
>  #
>  # Paths and names
>  #
> -PROCPS_VERSION	:= 3.3.17
> -PROCPS_MD5	:= d60613e88c2f442ebd462b5a75313d56
> +PROCPS_VERSION	:= 4.0.3
> +PROCPS_MD5	:= 22b287bcd758831cbaf3356cd3054fe7
>  PROCPS		:= procps-ng-$(PROCPS_VERSION)
>  PROCPS_SUFFIX	:= tar.xz
>  PROCPS_URL	:= $(call ptx/mirror, SF, procps-ng/Production/$(PROCPS).$(PROCPS_SUFFIX))
> @@ -46,8 +46,10 @@ PROCPS_CONF_OPT	:= \
>  	--disable-rpath \
>  	--disable-watch8bit \
>  	--disable-libselinux \
> +	--disable-harden-flags \
>  	--$(call ptx/endis, PTXCONF_PROCPS_PIDOF)-pidof \
>  	--disable-kill \
> +	--$(call ptx/endis, PTXCONF_PROCPS_W)-w \
>  	--disable-skill \
>  	--disable-examples \
>  	--disable-sigwinch \
> @@ -63,7 +65,6 @@ PROCPS_CONF_OPT	:= \
>  	--$(call ptx/wwo, PTXCONF_PROCPS_WITH_SYSTEMD)-systemd \
>  	--without-elogind
>  
> -
>  # ----------------------------------------------------------------------------
>  # Target-Install
>  # ----------------------------------------------------------------------------
> @@ -77,7 +78,7 @@ $(STATEDIR)/procps.targetinstall:
>  	@$(call install_fixup, procps,AUTHOR,"Clemens Gruber <clemens.gruber@pqgruber.com>")
>  	@$(call install_fixup, procps,DESCRIPTION,missing)
>  
> -	@$(call install_lib, procps, 0, 0, 0644, libprocps)
> +	@$(call install_lib, procps, 0, 0, 0644, libproc2)
>  
>  ifdef PTXCONF_PROCPS_FREE
>  	@$(call install_copy, procps, 0, 0, 0755, -, /usr/bin/free)



      reply	other threads:[~2023-03-06 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 17:33 [ptxdist] [PATCH] " Christian Melki
2023-03-06 16:21 ` 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=20230306162112.3705319-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