Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] package/libwpe: bump to version 1.4.0
Date: Mon, 30 Sep 2019 11:38:46 +0300	[thread overview]
Message-ID: <20190930113846.GC242161@momiji> (raw)
In-Reply-To: <20190928233148.23c8a78c@windsurf>

Hello,

On Sat, 28 Sep 2019 23:31:48 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Sat, 21 Sep 2019 00:38:23 +0300
> Adrian Perez de Castro <aperez@igalia.com> wrote:
> 
> > WPE WebKit 2.26.0 requires libwpe 1.4.x, as indicated at:
> > 
> >   https://wpewebkit.org/release/schedule/#compatible-components
> > 
> > Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
> > ---
> >  package/libwpe/libwpe.hash | 8 ++++----
> >  package/libwpe/libwpe.mk   | 2 +-
> >  2 files changed, 5 insertions(+), 5 deletions(-)
> > 
> > diff --git a/package/libwpe/libwpe.hash b/package/libwpe/libwpe.hash
> > index c46e205dcf..91332ca51f 100644
> > --- a/package/libwpe/libwpe.hash
> > +++ b/package/libwpe/libwpe.hash
> > @@ -1,7 +1,7 @@
> > -# From https://wpewebkit.org/releases/libwpe-1.2.1.tar.xz.sums
> > -md5 9f26865f06ecf933ddbbf067a7be735f libwpe-1.2.1.tar.xz
> > -sha1 d3f6211a2acafe1bd1f41e826c8efae35335fc92 libwpe-1.2.1.tar.xz
> > -sha256 00e103c6fa226b0d979c29d14c9e8168c4bec7b0b5108f3705a037cda5609d7d libwpe-1.2.1.tar.xz
> > +# From https://wpewebkit.org/releases/libwpe-1.4.0.tar.xz.sums
> > +md5 4b6dbaa2d40408975fe1be935367b4e8 libwpe-1.4.0.tar.xz
> > +sha1 18825932749edecd92a3bd31d4feffb5fd1150b4 libwpe-1.4.0.tar.xz
> > +sha256 e2d3494fc33fe946ad917fd6a3abd127462b91bba62ef8b35507e92f8ede4188 libwpe-1.4.0.tar.xz
> >  
> >  # Hashes for license files:
> >  sha256 6efc9991641b47b1f4e727db7f090d0ade00117dcbbc74be622f2baceddb1f22 COPYING
> 
> You forgot to update the hash of the license file, which has changed
> with this update. That was breaking "make legal-info". I fixed that and
> updated the commit log to give some details about why the license file
> has changed. Applied with this fix!

/me facepalms

Good catch, thanks for taking care of it.

?Adri?n
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190930/d20648d0/attachment-0001.asc>

  reply	other threads:[~2019-09-30  8:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 21:38 [Buildroot] [PATCH 0/4] Update WPE WebKit to 2.26.0 (and its related components) Adrian Perez de Castro
2019-09-20 21:38 ` [Buildroot] [PATCH 1/4] package/libwpe: bump to version 1.4.0 Adrian Perez de Castro
2019-09-28 21:31   ` Thomas Petazzoni
2019-09-30  8:38     ` Adrian Perez de Castro [this message]
2019-09-20 21:38 ` [Buildroot] [PATCH 2/4] package/wpebackend-fdo: " Adrian Perez de Castro
2019-09-28 21:32   ` Thomas Petazzoni
2019-09-20 21:38 ` [Buildroot] [PATCH 3/4] package/wpewebkit: bump to version 2.26.0 Adrian Perez de Castro
2019-09-28 21:32   ` Thomas Petazzoni
2019-09-29 11:23   ` James Hilliard
2019-09-29 11:51     ` Baruch Siach
2019-09-29 12:02       ` James Hilliard
2019-09-20 21:38 ` [Buildroot] [PATCH 4/4] package/cog: bump to version 0.4.0 Adrian Perez de Castro
2019-09-28 21:32   ` Thomas Petazzoni

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=20190930113846.GC242161@momiji \
    --to=aperez@igalia.com \
    --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