unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Vivien Kraus via Guix-patches via <guix-patches@gnu.org>
To: 69652@debbugs.gnu.org
Cc: liliana.prikler@gmail.com, maxim.cournoyer@gmail.com,
	rg@raghavgururajan.name, vivien@planete-kraus.eu
Subject: [bug#69652] [PATCH gnome-team 0/1] What should we do with orbit2?
Date: Fri, 8 Mar 2024 18:29:35 +0100	[thread overview]
Message-ID: <cover.1709918975.git.vivien@planete-kraus.eu> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

Dear Guix,

Orbit2 is an old, unmaintained package that was used for the Gtk+2 stack, as
far as I understand. We still have Gtk+2 around, mainly for OCaml lablgtk2
(and _3, yes).

On gnome-team, this package fails to build on 32-bit systems.  I fail to
understand why it would fail on gnome-team and not on master.  If I
understood, maybe a clear solution would appear.  As of now, I can see
different mitigations:
— pretend there is no problem, skip the failing tests (they are everywhere, so
  maybe skip tests entirely) and ship it;
— remove it (I can’t see it on Debian, for instance);
— fix the test crashes (I won’t, and it is unmaintained);
— mark it as unsupported.

I went with the last option because I feel it is the most neutral thing to do.

What do you think?

Best regards,

Vivien

Vivien Kraus (1):
  gnu: orbit2: Mark it unsupported in 32-bits systems.

 gnu/packages/gnome.scm | 53 ++++++++++++++++++++++--------------------
 1 file changed, 28 insertions(+), 25 deletions(-)


base-commit: 25c14c893f05019d746321285acf55d1aa65b943
-- 
2.41.0




             reply	other threads:[~2024-03-08 17:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 17:29 Vivien Kraus via Guix-patches via [this message]
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 ` [bug#69652] [PATCH gnome-team 0/1] What should we do with orbit2? Aaron Covrig via Guix-patches via

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=cover.1709918975.git.vivien@planete-kraus.eu \
    --to=guix-patches@gnu.org \
    --cc=69652@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=maxim.cournoyer@gmail.com \
    --cc=rg@raghavgururajan.name \
    --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 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).