unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
	Leo Famulari <leo@famulari.name>
Cc: 53197@debbugs.gnu.org, kiasoc5@tutanota.com
Subject: bug#53197: wpewebkit: Fails to build (a required package was not found)
Date: Sat, 15 Jan 2022 12:12:25 +0100	[thread overview]
Message-ID: <bbf1efe5e549b6f53164effa7d3209ba6667de87.camel@gmail.com> (raw)
In-Reply-To: <d9d67773d3237d684767da6531cdf988fa597e6a.camel@ist.tugraz.at>

Am Donnerstag, dem 13.01.2022 um 08:45 +0100 schrieb Liliana Marie
Prikler:
> some hitherto unpackaged... package[1]
> [1] https://github.com/Igalia/WPEBackend-fdo
It turns out we actually do have wpebackend-fdo and are even using it
in our webkitgtk build.  I'll try updating the wpe libs to 1.12.0 and
wpewebkit to 2.34.3, with a libsoup-2 variant thrown in if need be.




  reply	other threads:[~2022-01-15 11:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 21:49 bug#53197: wpewebkit: Fails to build (a required package was not found) kiasoc5--- via Bug reports for GNU Guix
2022-01-12  7:28 ` Liliana Marie Prikler
2022-01-12 18:28   ` Leo Famulari
2022-01-13  7:45     ` Liliana Marie Prikler
2022-01-15 11:12       ` Liliana Marie Prikler [this message]
2022-01-16  7:29 ` bug#53197: [PATCH 1/3] gnu: libwpe: Update to 1.12.0 Liliana Marie Prikler
2022-01-16  7:29 ` bug#53197: [PATCH 2/3] gnu: wpebackend-fdo: " Liliana Marie Prikler
2022-01-16  7:31 ` bug#53197: [PATCH 3/3] gnu: wpewebkit: Update to 2.34.3 Liliana Marie Prikler
2022-01-16  7:36 ` bug#53197: [PATCH 0/3] Update WPEWebkit " Liliana Marie Prikler
2022-01-16 18:30   ` Leo Famulari
2022-01-16 19:29     ` Liliana Marie Prikler
2022-01-29 21:42       ` Leo Famulari
2022-01-16 18:55   ` Leo Famulari

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bbf1efe5e549b6f53164effa7d3209ba6667de87.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=53197@debbugs.gnu.org \
    --cc=kiasoc5@tutanota.com \
    --cc=leo@famulari.name \
    --cc=liliana.prikler@ist.tugraz.at \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).