From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Maxim Kochetkov <fido_max@inbox.ru>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/postgis: bump version to 3.3.1
Date: Wed, 21 Sep 2022 22:15:23 +0200 [thread overview]
Message-ID: <20220921221523.21e6656d@windsurf> (raw)
In-Reply-To: <20220919062023.1091771-1-fido_max@inbox.ru>
On Mon, 19 Sep 2022 09:20:23 +0300
Maxim Kochetkov <fido_max@inbox.ru> wrote:
> Release-notes: https://git.osgeo.org/gitea/postgis/postgis/src/tag/3.3.1/NEWS
>
> Signed-off-by: Maxim Kochetkov <fido_max@inbox.ru>
> ---
> ...kefile.in-do-not-force-static-linkin.patch | 23 ++++++++++---------
> package/postgis/postgis.hash | 2 +-
> package/postgis/postgis.mk | 2 +-
> 3 files changed, 14 insertions(+), 13 deletions(-)
>
> diff --git a/package/postgis/0002-raster-loader-Makefile.in-do-not-force-static-linkin.patch b/package/postgis/0002-raster-loader-Makefile.in-do-not-force-static-linkin.patch
> index 756a7c10dd..20a359fadd 100644
> --- a/package/postgis/0002-raster-loader-Makefile.in-do-not-force-static-linkin.patch
> +++ b/package/postgis/0002-raster-loader-Makefile.in-do-not-force-static-linkin.patch
> @@ -1,6 +1,6 @@
> -From 29c33c483e22a4445d870739187d128df0f11f60 Mon Sep 17 00:00:00 2001
> -From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> -Date: Wed, 27 Jul 2022 15:12:40 +0200
> +From 50af3f4fc2353ba35fd054060e27e034d29b1c78 Mon Sep 17 00:00:00 2001
> +From: Maxim Kochetkov <mkochetkov@airspan.com>
> +Date: Mon, 19 Sep 2022 09:09:44 +0300
Since you are not doing substantial changes on this patch, it would be
nicer to preserve the authorship as it is.
> Subject: [PATCH] raster/loader/Makefile.in: do not force static linking
>
> This is similar to commit
> @@ -13,23 +13,24 @@ object XYZ".
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Upstream: https://github.com/postgis/postgis/pull/702
Do you think you could follow-up with upstream on this? I did an
initial fix, but that wasn't accepted as-is. However, my interest in
postgis is limited, so I don't think I will have the chance to look
into this in the near future.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-09-21 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 6:20 [Buildroot] [PATCH 1/1] package/postgis: bump version to 3.3.1 Maxim Kochetkov
2022-09-21 20:15 ` Thomas Petazzoni [this message]
2022-09-22 6:54 ` Maxim Kochetkov via buildroot
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=20220921221523.21e6656d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fido_max@inbox.ru \
/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