From: Remco van 't Veer <remco@remworks.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Vivien Kraus <vivien@planete-kraus.eu>,
Leo Famulari <leo@famulari.name>,
72042-done@debbugs.gnu.org,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
Andrew Tropin <andrew@trop.in>
Subject: bug#72042: [PATCH 1/1] gnu: python-gst: Fix build.
Date: Wed, 11 Sep 2024 09:29:17 +0200 [thread overview]
Message-ID: <87a5ge3aya.fsf@remworks.net> (raw)
In-Reply-To: <87cyla3euk.fsf@gmail.com> (Maxim Cournoyer's message of "Wed, 11 Sep 2024 15:05:07 +0900")
Hi Maxim,
2024/09/11, Maxim Cournoyer:
> It's nice that this fixes the package build, but propagating various
> version of Python libraries a road that to leads to problems. Currently
> it's important that propagated things are all compatible together.
>
> I'd suggest trying to update python-gst to see if it works with the
> newer python-pygobject instead.
It does because this is the newer version. I proposed to do a graft or
just go for the upgrade[1] but python-pygobject has a lot of dependent
packages.
$ guix refresh --list-dependent python-pygobject
Building the following 2015 packages would ensure 4466 dependent packages are rebuilt: ..
Should I provide a patch to just go for the newer version?
Remco
next prev parent reply other threads:[~2024-09-11 7:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 19:37 bug#72042: [core-updates] Python-gst fails its test suite Leo Famulari
2024-09-02 15:12 ` Remco van 't Veer
2024-09-02 18:18 ` Leo Famulari
2024-09-02 19:38 ` bug#72042: [PATCH 0/1] introduce python-pygobject-3.48 to fix python-gst build Remco van 't Veer
2024-09-02 19:38 ` bug#72042: [PATCH 1/1] gnu: python-gst: Fix build Remco van 't Veer
2024-09-05 15:14 ` Andrew Tropin via Bug reports for GNU Guix
2024-09-11 6:05 ` Maxim Cournoyer
2024-09-11 7:29 ` Remco van 't Veer [this message]
2024-09-11 16:59 ` Liliana Marie Prikler
2024-09-12 0:37 ` Maxim Cournoyer
2024-09-12 7:04 ` Remco van 't Veer
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=87a5ge3aya.fsf@remworks.net \
--to=remco@remworks.net \
--cc=72042-done@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=leo@famulari.name \
--cc=liliana.prikler@gmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=vivien@planete-kraus.eu \
/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.