Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: James Knight <james.d.knight@live.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 3/5] package/rpm: bump to version 4.18.1
Date: Thu, 08 Jun 2023 22:39:49 +0200	[thread overview]
Message-ID: <87edml3cyy.fsf@48ers.dk> (raw)
In-Reply-To: <SN4P221MB0682AD37886082711DF0E5EAA0709@SN4P221MB0682.NAMP221.PROD.OUTLOOK.COM> (James Knight's message of "Sun, 7 May 2023 17:34:31 -0400")

>>>>> "James" == James Knight <james.d.knight@live.com> writes:

 > The most recent release of RPM is v4.18.1 [1].
 > Adding an upstream patch to prevent build failures for certain
 > toolchains (0001-fix-var-declare-in-label-error.patch). Fix should be
 > available next release.

 > [1]: https://rpm.org/wiki/Releases/4.18.1

 > Signed-off-by: James Knight <james.d.knight@live.com>
 > ---
 > Changes v1 -> v2:
 >   - New patch in v2, with changes from the original first patch.

Committed to 2023.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-06-08 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230507213433.4128-1-james.d.knight@live.com>
2023-05-07 21:34 ` [Buildroot] [PATCH v2 2/5] package/rpm: add more disabling options James Knight
2023-06-08 20:39   ` Peter Korsgaard
2023-05-07 21:34 ` [Buildroot] [PATCH v2 3/5] package/rpm: bump to version 4.18.1 James Knight
2023-06-08 20:39   ` Peter Korsgaard [this message]
2023-05-07 21:34 ` [Buildroot] [PATCH v2 4/5] package/rpm: add python support James Knight
2023-05-07 21:34 ` [Buildroot] [PATCH v2 5/5] package/rpm: add readline support James Knight

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=87edml3cyy.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=james.d.knight@live.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