From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v2 1/4] meson: bump version to 0.47.1
Date: Thu, 19 Jul 2018 08:00:53 +0200 [thread overview]
Message-ID: <20180719060053.GA10375@itchy> (raw)
In-Reply-To: <20180718221640.03319bc8@gmx.net>
On 2018-07-18 22:16, Peter Seiderer wrote:
> Hello Eric,
>
> On Tue, 17 Jul 2018 22:23:11 +0200, Eric Le Bihan <eric.le.bihan.dev@free.fr> wrote:
>
> > Hi!
> >
> > On 2018-07-17 21:16, Peter Seiderer wrote:
> > > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > > ---
> > > Notes:
> > > Hash not checked against the pgp signature, tried
> > > $ gpg --verify meson-0.47.1.tar.gz.asc meson-0.47.1.tar.gz
> > > gpg: Signature made Di 10 Jul 2018 23:28:12 CEST
> > > gpg: using RSA key 95181F4EED14FDF4E41B518D3BF4693BFEEB9428
> > > gpg: Can't check signature: No public key
> > >
> > > Any advice which public key is used to sign the meson package?
> >
> > I check the signature as follows:
> >
> > ```
> > $ gpg --recv-keys 3BF4693BFEEB9428
> > $ gpg --verify meson-0.47.1.tar.gz.asc meson-0.47.1.tar.gz
> > gpg: Signature made Tue Jul 10 23:28:12 2018 CEST using RSA key ID
> > FEEB9428
> > gpg: Good signature from "Jussi Pakkanen <jpakkane@gmail.com>"
> > gpg: WARNING: This key is not certified with a trusted signature!
> > gpg: There is no indication that the signature belongs to the
> > owner.
> > Primary key fingerprint: 9518 1F4E ED14 FDF4 E41B 518D 3BF4 693B FEEB
> > 9428
> > ```
> >
> > BTW, shouldn't a signed-off-by line be added to the refreshed patch? I
> > was about to send this package bump, so I can send mine if you want.
>
> Which Signed-off-by line do you think is missing? Sorry for the double
> effort, will send an updated version of the patch series soon (some
> fixes for libdrm conversion), maybe better send a Reviewed-by to
> my patch?
Sorry, I misread your patch. I thought it refreshed the
Buildroot-specific patch for fixing RPATH, whereas it removed it. See
commit 7a23af4773665d2ee40e2d4e525746ebe38456dd for details.
This specific patch applies to 0.46.1 but not to 0.47.1, as the function
to modify is not in mesonbuild/scripts/meson_install.py anymore, but in
mesonbuild/minstall.py:
```
next prev parent reply other threads:[~2018-07-19 6:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 19:16 [Buildroot] [RFC v2 1/4] meson: bump version to 0.47.1 Peter Seiderer
2018-07-17 19:16 ` [Buildroot] [RFC v2 2/4] meson: change from global to per package cross-compilation.conf Peter Seiderer
2018-07-17 19:16 ` [Buildroot] [RFC v2 3/4] libdrm: change to meson build system Peter Seiderer
2018-07-17 19:16 ` [Buildroot] [RFC v2 4/4] libinput: bump version to 1.11.0 and convert to meson build Peter Seiderer
2018-07-17 20:02 ` [Buildroot] [RFC v2 1/4] meson: bump version to 0.47.1 Baruch Siach
2018-07-17 21:23 ` Peter Seiderer
2018-07-18 3:03 ` Baruch Siach
2018-07-18 19:46 ` Peter Seiderer
2018-07-17 20:23 ` Eric Le Bihan
2018-07-18 20:16 ` Peter Seiderer
2018-07-19 6:00 ` Eric Le Bihan [this message]
2018-07-19 20:48 ` Peter Seiderer
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=20180719060053.GA10375@itchy \
--to=eric.le.bihan.dev@free.fr \
--cc=buildroot@busybox.net \
/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