From: Aaron Covrig via Guix-patches via <guix-patches@gnu.org>
To: 69652@debbugs.gnu.org
Subject: [bug#69652] [PATCH gnome-team 0/1] What should we do with orbit2?
Date: Sat, 9 Mar 2024 10:57:48 -0500 [thread overview]
Message-ID: <CAK7qAcQ2YZgX5s+4aLkaoEQs=nPPrM+yisbQ16wDLERyeKm6gg@mail.gmail.com> (raw)
In-Reply-To: <cover.1709918975.git.vivien@planete-kraus.eu>
[-- Attachment #1: Type: text/plain, Size: 149 bytes --]
Is the version of glib on the gnome branch different from that on the
master branch? If so, what happens if you pin to the version on master?
Aaron
[-- Attachment #2: Type: text/html, Size: 195 bytes --]
prev parent reply other threads:[~2024-03-09 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 17:29 [bug#69652] [PATCH gnome-team 0/1] What should we do with orbit2? Vivien Kraus via Guix-patches via
2024-03-08 17:20 ` [bug#69652] [PATCH gnome-team 1/1] gnu: orbit2: Mark it unsupported in 32-bits systems Vivien Kraus via Guix-patches via
2024-03-08 19:11 ` Liliana Marie Prikler
2024-03-08 20:03 ` Vivien Kraus via Guix-patches via
2024-03-09 6:36 ` Liliana Marie Prikler
2024-03-09 8:47 ` [bug#69652] [PATCH gnome-team v2 0/3] FIX that damn orbit2 Vivien Kraus via Guix-patches via
2024-03-09 7:48 ` [bug#69652] [PATCH gnome-team v2 1/3] gnu: orbit2: Update style Vivien Kraus via Guix-patches via
2024-03-09 7:52 ` [bug#69652] [PATCH gnome-team v2 2/3] gnu: orbit2: Propagate inputs Vivien Kraus via Guix-patches via
2024-03-09 8:43 ` [bug#69652] [PATCH gnome-team v2 3/3] gnu: orbit2: Fix bug on 32-bit systems Vivien Kraus via Guix-patches via
2024-03-09 17:50 ` [bug#69652] [PATCH gnome-team v2 0/3] FIX that damn orbit2 Maxim Cournoyer
2024-03-09 18:40 ` bug#69652: " Liliana Marie Prikler
2024-03-09 15:57 ` Aaron Covrig via Guix-patches via [this message]
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='CAK7qAcQ2YZgX5s+4aLkaoEQs=nPPrM+yisbQ16wDLERyeKm6gg@mail.gmail.com' \
--to=guix-patches@gnu.org \
--cc=69652@debbugs.gnu.org \
--cc=aaron.covrig.us@ieee.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.
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.