unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Greg Hogan <code@greghogan.com>
Cc: Ashish SHUKLA <ashish.is@lostca.se>, 73615@debbugs.gnu.org
Subject: [bug#73615] [PATCH] gnu: gdb: Update to 15.2.
Date: Sat, 30 Nov 2024 17:19:25 +0100	[thread overview]
Message-ID: <87frn8y9rm.fsf@gnu.org> (raw)
In-Reply-To: <87wmhx4qdr.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 24 Oct 2024 14:49:52 +0200")

Ludovic Courtès <ludo@gnu.org> skribis:

> Greg Hogan <code@greghogan.com> skribis:
>
>> On Thu, Oct 3, 2024 at 6:04 PM Ashish SHUKLA <ashish.is@lostca.se> wrote:
>>>
>>> I'm not sure the point of having an indirect reference, so this is why I
>>> have not updated the `gdb' variable.
>>
>> Yes, that's a nice observation, if we only have one public choice then
>> why the default selector?
>>
>> 'guix refresh' shows gdb with 414 dependent packages. It would be
>> helpful if that partial dependency tree could be exported as in 'guix
>> graph' to better identity packages which could be pinned to reduce
>> that number. Even a simple option, means, or tool to filter out leaves
>> would greatly reduce the list.
>
> See <https://issues.guix.gnu.org/70393>.
>
> I’ll rebase that pydevd patch and eventually apply it.

Done in 94bb6a5a88b17da1178fdc1d16cb87b9913bc1c1.

Should we (finally!) upgrade ‘gdb’ after renaming ‘gdb-14’ to ‘gdb’?

Ludo’.




      reply	other threads:[~2024-11-30 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03 14:23 [bug#73615] [PATCH] gnu: gdb: Update to 15.2 Ashish SHUKLA via Guix-patches via
2024-10-03 19:36 ` Greg Hogan
2024-10-03 22:04   ` Ashish SHUKLA via Guix-patches via
2024-10-06 11:05     ` Greg Hogan
2024-10-24 12:49       ` Ludovic Courtès
2024-11-30 16:19         ` Ludovic Courtès [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

  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=87frn8y9rm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=73615@debbugs.gnu.org \
    --cc=ashish.is@lostca.se \
    --cc=code@greghogan.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 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).