public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Yu, Mingli" <mingli.yu@eng.windriver.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/3] gnupg: Make the version consistent
Date: Fri, 19 Jan 2024 11:43:26 +0000	[thread overview]
Message-ID: <503e3e63ea9a2062f60c8675cd4f7fa63fb8376f.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240119113354.3000697-2-mingli.yu@windriver.com>

On Fri, 2024-01-19 at 19:33 +0800, Yu, Mingli wrote:
> From: Mingli Yu <mingli.yu@windriver.com>
> 
> The commit [b67e4e523 Improve the beta number generation.] [1]
> extends the version to make it work well for no release version,
> but it introduces the version inconsistency.
> 
> Considering we mainly use a release version in oe, so remove the
> added suffix to keep consistent.
> 
> Before the patch:
>  # rpm -qa | grep gnupg
>  gnupg-gpg-2.4.3-r0.core2_64
>  gnupg-2.4.3-r0.core2_64
>  # gpgv --version
>  gpgv (GnuPG) 2.4.3-unknown
>  [snip]
> 
> After the patch:
>  # rpm -qa | grep gnupg
>  gnupg-gpg-2.4.3-r0.core2_64
>  gnupg-2.4.3-r0.core2_64
>  # gpgv --version
>  gpgv (GnuPG) 2.4.3
>  [snip]
> 
> [1] https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blobdiff;f=autogen.sh;h=2b0a5dc51a7386ef90ff6c8358d26b9cc65c0c72;hp=471193c2af6a298fdde466950061dd890feb230e;hb=b67e4e523e6d19d384e23c5bb03010caebd150e7;hpb=518d835380a2ae01d6a9cc19de92684baade96a4
> 
> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
> ---
>  ...autogen.sh-Remove-the-unknown-suffix.patch | 43 +++++++++++++++++++
>  meta/recipes-support/gnupg/gnupg_2.4.3.bb     |  1 +
>  2 files changed, 44 insertions(+)
>  create mode 100644 meta/recipes-support/gnupg/gnupg/0001-autogen.sh-Remove-the-unknown-suffix.patch

We're not carrying a patch to do this, particularly one marked as not
suitable for upstream. Please work with upstream to fix the version
shown when you build a release tarball.

Same for the other patch, 3/3.

Cheers,

Richard


  reply	other threads:[~2024-01-19 11:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 11:33 [PATCH 1/3] xmlto: Remove the explicit PV setting mingli.yu
2024-01-19 11:33 ` [PATCH 2/3] gnupg: Make the version consistent mingli.yu
2024-01-19 11:43   ` Richard Purdie [this message]
2024-01-19 17:41   ` [OE-core] " Ross Burton
2024-01-22  5:18     ` Yu, Mingli
2024-01-19 11:33 ` [PATCH 3/3] libgcrypt: " mingli.yu

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=503e3e63ea9a2062f60c8675cd4f7fa63fb8376f.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mingli.yu@eng.windriver.com \
    --cc=openembedded-core@lists.openembedded.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