From: "jgart" <jgart@dismail.de>
To: "Simon Tournier" <zimon.toutoune@gmail.com>,
"Kaelyn" <kaelyn.alexi@protonmail.com>,
"guix-devel" <guix-devel@gnu.org>
Cc: "Ricardo Wurmus" <rekado@elephly.net>,
"Julien Lepiller" <julien@lepiller.eu>,
"Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>,
"Lars-Dominik Braun" <lars@6xq.net>
Subject: Re: i686 core-updates failure.
Date: Thu, 13 Apr 2023 13:23:15 +0000 [thread overview]
Message-ID: <dd337ae78d4a9dfafd6fed0d7ad3a348@dismail.de> (raw)
In-Reply-To: <86cz48ta1g.fsf@gmail.com>
My thoughts on this are that unless someone has the time to maintain those broken packages we should just remove them and clean up shop a bit.
Is there a reason to keep around the broken packages?
A news entry about the removals would also be helpful if we decide to remove them in order for people to know and so future contributors can pick up the work if they are interested in maintaining them at a later date.
Anyways, one idea for what to do, WDYT
next prev parent reply other threads:[~2023-04-13 13:24 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 16:11 i686 core-updates failure Kaelyn
2023-04-12 21:05 ` Josselin Poiret
2023-04-12 21:31 ` Andreas Enge
2023-04-13 4:37 ` Kaelyn
2023-04-13 16:25 ` Andreas Enge
2023-04-14 8:28 ` Andreas Enge
2023-04-14 20:05 ` Kaelyn
2023-04-15 11:20 ` python-pytest on core-updates (was: i686 core-updates failure.) Andreas Enge
2023-04-15 11:32 ` python-pytest on core-updates Andreas Enge
2023-04-15 14:08 ` [PATCH core-updates] gnu: python-pytest: Fix failing test_raising_repr Josselin Poiret
2023-04-15 16:14 ` Kaelyn
2023-04-15 19:59 ` Andreas Enge
2023-04-15 20:47 ` Andreas Enge
2023-04-15 20:49 ` python-pytest on core-updates (was: i686 core-updates failure.) Andreas Enge
2023-04-13 9:18 ` i686 core-updates failure Simon Tournier
2023-04-13 13:23 ` jgart [this message]
2023-04-13 13:43 ` Andreas Enge
2023-04-14 15:12 ` Csepp
2023-04-14 16:58 ` Simon Tournier
2023-04-14 17:30 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-13 15:31 ` Simon Tournier
2023-04-13 16:21 ` Simon Tournier
2023-04-13 15:47 ` Ricardo Wurmus
2023-04-13 16:15 ` Greg Hogan
2023-04-13 16:39 ` Simon Tournier
2023-04-13 16:47 ` Ricardo Wurmus
2023-04-13 20:02 ` Lars-Dominik Braun
2023-04-13 20:15 ` Simon Tournier
2023-04-13 20:45 ` Andreas Enge
2023-04-13 20:57 ` Simon Tournier
2023-04-14 8:25 ` Andreas Enge
2023-04-14 9:45 ` Simon Tournier
2023-04-14 18:16 ` Andreas Enge
2023-04-14 18:40 ` Lars-Dominik Braun
2023-04-15 9:48 ` ghc in core-updates on i686 Andreas Enge
2023-04-14 10:49 ` i686 core-updates failure Lars-Dominik Braun
2023-04-14 17:00 ` Simon Tournier
2023-04-13 20:33 ` wget (was Re: i686 core-updates failure.) Simon Tournier
2023-04-13 20:37 ` Andreas Enge
2023-04-13 20:43 ` Simon Tournier
2023-04-13 20:49 ` wget Andreas Enge
2023-04-15 0:51 ` wget (was Re: i686 core-updates failure.) Maxim Cournoyer
2023-04-15 10:43 ` Andreas Enge
2023-04-15 16:37 ` Kaelyn
2023-04-15 18:25 ` Kaelyn
2023-04-15 21:00 ` wget on i686 in core-updates Andreas Enge
2023-04-16 17:06 ` wget (was Re: i686 core-updates failure.) Andreas Enge
2023-04-16 17:49 ` Kaelyn
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=dd337ae78d4a9dfafd6fed0d7ad3a348@dismail.de \
--to=jgart@dismail.de \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
--cc=kaelyn.alexi@protonmail.com \
--cc=lars@6xq.net \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.com \
/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.