all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Marius Bakke <marius@gnu.org>
Cc: 60076@debbugs.gnu.org, contact@carldong.me
Subject: [bug#60076] [PATCH RFC] Revert "gnu: glibc: Remove old versions."
Date: Wed, 14 Dec 2022 16:03:38 -0500	[thread overview]
Message-ID: <87359h3dg5.fsf@gmail.com> (raw)
In-Reply-To: <87a63pso18.fsf@gnu.org> (Marius Bakke's message of "Wed, 14 Dec 2022 21:55:47 +0100")

Hi Marius,

Marius Bakke <marius@gnu.org> writes:

> Maxim Cournoyer <maxim.cournoyer@gmail.com> skriver:
>
>> This reinstates glibc 2.22 through 2.28, by reverting commit
>> ebd1ba713cbefc9ad5dac609255e1344a328e360 ("gnu: glibc: Remove old versions."),
>> adding two patches removed in d2bb4847b96e51b71126778bb16daa7674a6690c ("gnu:
>> Remove leftover patch files."), and partially reverting
>> 1feca4be5296d7f0c0e2269ccb612cadded6573b ("gnu: glibc: Remove versions 2.27
>> and 2.28.").
>>
>> Rationale: Keeping older glibc versions around is useful when experimenting
>> with 'package-with-c-toolchain'.
>
> IMO it's better to add these to 'guix-past'[0] instead of keeping them
> in the main channel.
>
> [0]: https://gitlab.inria.fr/guix-hpc/guix-past

Good suggestion.  If someone shows interested in the series we could try
to have these contributed to guix-past.  Otherwise if there's no
interest I'll close the ticket without merge in 2 weeks time.

Thanks for tipping in!

-- 
Thanks,
Maxim




  reply	other threads:[~2022-12-14 21:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 20:39 [bug#60076] [PATCH RFC] Revert "gnu: glibc: Remove old versions." Maxim Cournoyer
2022-12-14 20:50 ` Maxim Cournoyer
2022-12-14 20:55 ` Marius Bakke
2022-12-14 21:03   ` Maxim Cournoyer [this message]
2022-12-18 19:29     ` Carl Dong
2022-12-19  2:37       ` bug#60076: " Maxim Cournoyer

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=87359h3dg5.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=60076@debbugs.gnu.org \
    --cc=contact@carldong.me \
    --cc=marius@gnu.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.