all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 60864-done@debbugs.gnu.org
Subject: bug#60864: [PATCH v2] gnu: Unify webkitgtk and webkitgtk-next.
Date: Sun, 29 Jan 2023 08:27:59 +0100	[thread overview]
Message-ID: <637aaaa3f37a5aed6a32ec8fef8bf8f2f8c0a09a.camel@gmail.com> (raw)
In-Reply-To: <877cxdz7on.fsf@gmail.com>

Am Montag, dem 23.01.2023 um 08:44 -0500 schrieb Maxim Cournoyer:
> Hi Liliana,
> 
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> 
> > * gnu/packages/webkit.scm (%webkit-version): Update to 2.38.3.
> > (webkitgtk)[source]: Update hash.
> > [arguments]<#:phases>: Add ‘set-CC’.  Remove ‘patch-gtk-doc-scan’.
> > [native-inputs]: Remove gtk-doc/stable and docbook-xml.  Add gi-
> > docgen.
> > (webkitgtk-next)[name]: Rename to ‘webkitgtk-next’.
> > [source, native-inputs]: Inherit fully.
> > [arguments]<#:phases>: Inherit fully.
> > (wpewebkit)[source]: Update hash.
> > ---
> > In the previous version, I forgot to update teh hash of WPEWebkit.
> > This is now done.
> > 
> > Sadly, I've already had two builds failing due to the compiler
> > getting killed near the end.  I hope this is just a limitation on
> > my end and not a general feature.
> 
> I just built both successfully here (x86_64); LGTM.
Thanks for the review.  Pushed now.





  reply	other threads:[~2023-01-29  7:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 17:02 [bug#60864] [PATCH] gnu: Unify webkitgtk and webkitgtk-next Liliana Marie Prikler
2023-01-16 17:02 ` [bug#60864] [PATCH v2] " Liliana Marie Prikler
2023-01-23 13:44   ` Maxim Cournoyer
2023-01-29  7:27     ` Liliana Marie Prikler [this message]
2023-01-16 21:42 ` [bug#60864] [PATCH] " Maxim Cournoyer

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=637aaaa3f37a5aed6a32ec8fef8bf8f2f8c0a09a.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=60864-done@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.