From: corigan01 <corigan01@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: WIP: GNOME 45
Date: Mon, 30 Oct 2023 22:12:36 +0100 [thread overview]
Message-ID: <20231030211236.NyTBe2QP-gkVLui1B_TuuS4LEYNzatzZAhAaUqQT1S0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46531@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]
New comment by corigan01 on void-packages repository
https://github.com/void-linux/void-packages/pull/46531#issuecomment-1786054007
Comment:
I was able to build with the following changes. Hopefully they help someone.
- gnome-connections required `fuse3-devel` to build.
- Mutter required averyterrel's change to `libei-devel`
- I updated Pango to 1.51.0
srcpkgs/gnome-connections/template
```diff
makedepends="gtk+3-devel libhandy1-devel gtk-vnc-devel libgcrypt-devel
- gnutls-devel libsasl-devel libsecret-devel freerdp-devel"
+ gnutls-devel libsasl-devel libsecret-devel freerdp-devel fuse3-devel"
```
srcpkgs/mutter/template
```diff
makedepends="elogind-devel glib-devel gnome-desktop-devel graphene-devel
json-glib-devel libglib-devel libSM-devel libXtst-devel libcanberra-devel
libinput-devel MesaLib-devel pipewire-devel startup-notification-devel gtk4-devel
- wayland-protocols gnome-settings-daemon-devel libgudev-devel libwacom-devel libei"
+ wayland-protocols gnome-settings-daemon-devel libgudev-devel libwacom-devel libei-devel"
```
srcpkgs/pango/template
```diff
# Template file for 'pango'
pkgname=pango
-version=1.50.14
+version=1.51.0
revision=1
build_style=meson
build_helper=gir
@@ -14,7 +14,7 @@ license="LGPL-2.1-or-later"
homepage="https://www.pango.org/"
changelog="https://gitlab.gnome.org/GNOME/pango/-/raw/main/NEWS"
distfiles="${GNOME_SITE}/pango/${version%.*}/pango-${version}.tar.xz"
-checksum=1d67f205bfc318c27a29cfdfb6828568df566795df0cb51d2189cde7f2d581e8
+checksum=74efc109ae6f903bbe6af77eaa2ac6094b8ee245a2e23f132a7a8f0862d1a9f5
make_check=no # doesn't pass its own tests
```
next prev parent reply other threads:[~2023-10-30 21:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 12:41 [PR PATCH] " paper42
2023-10-11 21:29 ` [PR PATCH] [Updated] " paper42
2023-10-12 8:14 ` let-the-world-forget-the-flower
2023-10-16 11:36 ` chrysos349
2023-10-17 1:06 ` [PR REVIEW] " averyterrel
2023-10-30 21:12 ` corigan01 [this message]
2023-10-30 21:54 ` corigan01
2023-10-30 21:55 ` corigan01
2023-10-30 22:45 ` paper42
2023-10-30 22:46 ` paper42
2023-11-01 18:40 ` corigan01
2024-01-26 7:38 ` LokiRazer
2024-01-26 14:37 ` paper42
2024-01-26 14:37 ` [PR PATCH] [Closed]: " paper42
2024-01-26 15:12 ` Jaymz665
2024-01-26 15:12 ` Jaymz665
2024-01-26 16:17 ` fvalasiad
2024-02-14 13:21 ` Jaymz665
2024-02-14 14:12 ` fvalasiad
2024-02-17 18:19 ` Jaymz665
2024-02-17 19:15 ` corigan01
2024-02-17 19:22 ` fvalasiad
2024-02-17 20:49 ` Jaymz665
2024-02-18 7:08 ` Jaymz665
2024-02-18 13:14 ` zuranota
2024-02-18 13:40 ` Jaymz665
2024-02-18 13:40 ` Jaymz665
2024-02-18 13:40 ` Jaymz665
2024-02-18 13:45 ` zuranota
2024-02-18 13:48 ` fvalasiad
2024-02-18 14:19 ` fanyx
2024-02-18 18:16 ` Jaymz665
2024-02-22 3:56 ` zuranota
2024-02-22 11:05 ` Jaymz665
2024-02-23 22:23 ` GGTNT
2024-02-25 17:37 ` Jaymz665
2024-02-25 17:37 ` Jaymz665
2024-02-25 18:29 ` GGTNT
2024-02-26 1:01 ` shnaps
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=20231030211236.NyTBe2QP-gkVLui1B_TuuS4LEYNzatzZAhAaUqQT1S0@z \
--to=corigan01@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).