Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/procps-ng: bump to version 4.0.4
Date: Tue, 23 Jul 2024 23:15:14 +0200	[thread overview]
Message-ID: <20240723231514.0c81f86a@windsurf> (raw)
In-Reply-To: <20240723120140.176562-1-fontaine.fabrice@gmail.com>

On Tue, 23 Jul 2024 14:01:40 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> - Drop all patches (already in version) and so also drop autoreconf
> - This bump will also fix the following build failure with gcc >= 14:
> 
>   pgrep.c: In function 'main':
>   pgrep.c:1066:37: error: implicit declaration of function 'pidfd_open'; did you mean 'fdopen'? [-Wimplicit-function-declaration]
>    1066 |                         int pidfd = pidfd_open(procs[i].num, 0);
>         |                                     ^~~~~~~~~~
>         |                                     fdopen
> 
> https://gitlab.com/procps-ng/procps/-/blob/v4.0.4/NEWS
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/bd7b49123905c580842a3dd3b7a338d5aedf55d7
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  .checkpackageignore                           |  3 -
>  .../0001-configure-Add--disable-w.patch       | 93 -------------------
>  ...ssing-nl_langinfo-on-certain-configs.patch | 34 -------
>  .../procps-ng/0003-fix-pifd_open-check.patch  | 59 ------------
>  package/procps-ng/procps-ng.hash              |  8 +-
>  package/procps-ng/procps-ng.mk                |  4 +-
>  6 files changed, 5 insertions(+), 196 deletions(-)
>  delete mode 100644 package/procps-ng/0001-configure-Add--disable-w.patch
>  delete mode 100644 package/procps-ng/0002-escape-c-Fix-missing-nl_langinfo-on-certain-configs.patch
>  delete mode 100644 package/procps-ng/0003-fix-pifd_open-check.patch

Applied to master after tweaking the commit title and commit log to
mention that it's also a security bump. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-07-23 21:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 12:01 [Buildroot] [PATCH 1/1] package/procps-ng: bump to version 4.0.4 Fabrice Fontaine
2024-07-23 12:29 ` Thomas Petazzoni via buildroot
2024-07-23 12:42   ` Fabrice Fontaine
2024-07-23 21:15 ` Thomas Petazzoni via buildroot [this message]
2024-08-31 17:10   ` Peter Korsgaard
2024-09-09  9:49 ` Michael Nosthoff via buildroot
     [not found] <20240324090325.1768623-1-nemaakhilesh__15532.5242479861$1711271038$gmane$org@gmail.com>
2024-03-24 13:53 ` Bernd Kuhls
  -- strict thread matches above, loose matches on Subject: below --
2024-03-24  9:03 Akhilesh Nema

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=20240723231514.0c81f86a@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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