all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: Andreas Enge <andreas@enge.fr>
Cc: jgart <jgart@dismail.de>,
	"Simon Tournier" <zimon.toutoune@gmail.com>,
	Kaelyn <kaelyn.alexi@protonmail.com>,
	"Ricardo Wurmus" <rekado@elephly.net>,
	"Julien Lepiller" <julien@lepiller.eu>,
	"Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>,
	"Lars-Dominik Braun" <lars@6xq.net>,
	guix-devel@gnu.org
Subject: Re: i686 core-updates failure.
Date: Fri, 14 Apr 2023 17:12:40 +0200	[thread overview]
Message-ID: <87bkjqzdvr.fsf@riseup.net> (raw)
In-Reply-To: <ZDgHCnjAy31KDwWo@jurong>


Andreas Enge <andreas@enge.fr> writes:

> Am Thu, Apr 13, 2023 at 01:23:15PM +0000 schrieb jgart:
>> 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?
>
> Well, we can certainly remove a few hopeless, outdated, non-maintained
> broken packages. But if we start to remove packages such as wget, and
> Java, and Haskell, and much of R, and big chunks of Python, for i686,
> this amounts to removing the architecture altogether. It is a decision
> we may want to take at some point in time, but we should not do so casually.
> And definitely not in this core-updates merge.
>
> One argument for keeping i686 was that problems there were often indicative
> of problems in "more exotic" architectures, whereas i686 is relatively easy
> to build on x86_64 without specific (often slow) hardware. I am not sure
> if this still holds for the 32 bit problems we have seen recently; so there
> is a certain argument to make for removing the 32 bit architectures i686
> and armhf (x86_64 will soon celebrate its 25th birthday, aarch64 is half
> as old; I do not expect much hardware for the corresponding 32 bit
> architectures to be around any more).
>
> Andreas

That is a pretty terrible direction to take.  There are still plenty of
people who rely on old hardware who can't afford to buy new machines.
When discussing these issues, it is important to keep in mind that the
people who have enough spare time to contribute to this project and hang
out on the mailing lists come from a rather privileged background.  What
you think is reasonable to categorize as obsolete might be the only
machine a poor family could afford on the second hand market.
If Linux distros keep dropping support for old hardware, then they are
not liberatory, no matter how "free" their licenses are.

We are also in the middle of a massive climate crisis, so we should aim
to prolong the usefulness of existing hardware and not give in to this
planned obsolescence BS.


  reply	other threads:[~2023-04-14 15: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
2023-04-13 13:43   ` Andreas Enge
2023-04-14 15:12     ` Csepp [this message]
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=87bkjqzdvr.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=andreas@enge.fr \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --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.