mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Bruno Thomsen <bruno.thomsen@gmail.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] libgpg-error: version bump 1.45 -> 1.47
Date: Wed, 10 Jan 2024 18:11:06 +0100	[thread overview]
Message-ID: <ZZ7PqsgKrMuQGUsm@pengutronix.de> (raw)
In-Reply-To: <20240102175650.5092-1-bruno.thomsen@gmail.com>

On Tue, Jan 02, 2024 at 06:56:50PM +0100, Bruno Thomsen wrote:
> New option --enable-install-gpg-error-config to install deprecated
> gpg-error-config.
> 
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> ---
> v2:
> - Move existing patches forward, applies clean.

I somehow misst the new version and applied the old version with a fixup
to move keep the patch. Just in case you're wondering why I added the
comment in the commit message... Sorry about that.

Michael

>  .../0001-gpgrt-config-improve-pkg-config-file-parsing.patch   | 0
>  patches/{libgpg-error-1.45 => libgpg-error-1.47}/series       | 0
>  rules/libgpg-error.make                                       | 4 ++--
>  3 files changed, 2 insertions(+), 2 deletions(-)
>  rename patches/{libgpg-error-1.45 => libgpg-error-1.47}/0001-gpgrt-config-improve-pkg-config-file-parsing.patch (100%)
>  rename patches/{libgpg-error-1.45 => libgpg-error-1.47}/series (100%)
> 
> diff --git a/patches/libgpg-error-1.45/0001-gpgrt-config-improve-pkg-config-file-parsing.patch b/patches/libgpg-error-1.47/0001-gpgrt-config-improve-pkg-config-file-parsing.patch
> similarity index 100%
> rename from patches/libgpg-error-1.45/0001-gpgrt-config-improve-pkg-config-file-parsing.patch
> rename to patches/libgpg-error-1.47/0001-gpgrt-config-improve-pkg-config-file-parsing.patch
> diff --git a/patches/libgpg-error-1.45/series b/patches/libgpg-error-1.47/series
> similarity index 100%
> rename from patches/libgpg-error-1.45/series
> rename to patches/libgpg-error-1.47/series
> diff --git a/rules/libgpg-error.make b/rules/libgpg-error.make
> index 61e7e0a11990..32f1390d1774 100644
> --- a/rules/libgpg-error.make
> +++ b/rules/libgpg-error.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBGPG_ERROR) += libgpg-error
>  #
>  # Paths and names
>  #
> -LIBGPG_ERROR_VERSION	:= 1.45
> -LIBGPG_ERROR_MD5	:= 3bb15e0c29d3a680db7cef15143615e1
> +LIBGPG_ERROR_VERSION	:= 1.47
> +LIBGPG_ERROR_MD5	:= 58e054ca192a77226c4822bbee1b7fdb
>  LIBGPG_ERROR		:= libgpg-error-$(LIBGPG_ERROR_VERSION)
>  LIBGPG_ERROR_SUFFIX	:= tar.bz2
>  LIBGPG_ERROR_URL	:= \
> 
> base-commit: 6c8952685f05b011c21dec645d990bad4776e6a4
> -- 
> 2.43.0
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2024-01-10 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02 17:56 Bruno Thomsen
2024-01-10 17:11 ` Michael Olbrich [this message]
2024-01-13 17:33   ` Bruno Thomsen

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=ZZ7PqsgKrMuQGUsm@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=bruno.thomsen@gmail.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