all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Mark Wielaard <mark@klomp.org>, 38803@debbugs.gnu.org
Cc: control@debbugs.gnu.org, Marius Bakke <mbakke@fastmail.com>,
	Brett Gilio <brettg@gnu.org>
Subject: [bug#38803] [PATCH] gnu: elfutils: Update to 0.178
Date: Sat, 02 Sep 2023 11:39:32 -0700	[thread overview]
Message-ID: <87zg24mnbv.fsf@wireframe> (raw)
In-Reply-To: <20191230014101.2425-1-mark@klomp.org>

[-- Attachment #1: Type: text/plain, Size: 534 bytes --]

retitle 38803 gnu: elfutils: Enable debuginfod
thanks

On 2019-12-30, Mark Wielaard wrote:
> This introduces debuginfod support which requires a couple of new inputs.
>
> * gnu/packages/elf.scm (elfutils): Update to 0.178

Newer versions of elfutils have been included:

1a97959b22668af999ebc79c3ddc1664420eadd4 gnu: elfutils: Update to 0.187.

The outstanding issue from this bug is to enable the debuginfod server,
which is referred to in the comments for the current elfutils
package. Retitled appropriately.

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

      parent reply	other threads:[~2023-09-02 18:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30  1:41 [bug#38803] [PATCH] gnu: elfutils: Update to 0.178 Mark Wielaard
2019-12-30  1:44 ` Brett Gilio
2019-12-30  2:04   ` Mark Wielaard
2020-01-12 20:39 ` Mark Wielaard
2020-01-12 20:54   ` Marius Bakke
2020-01-13  0:03     ` Mark Wielaard
2020-01-13 22:26       ` Marius Bakke
2020-01-31 12:43         ` Mark Wielaard
2020-01-31 15:49           ` Marius Bakke
2020-01-31 16:55             ` Mark Wielaard
2020-02-05 20:41               ` Marius Bakke
2020-02-06 11:04                 ` Mark Wielaard
2020-02-06 11:36                   ` Marius Bakke
2020-02-06 13:23                   ` Mark Wielaard
2020-02-06 14:31                     ` Marius Bakke
2023-09-02 18:39 ` Vagrant Cascadian [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zg24mnbv.fsf@wireframe \
    --to=vagrant@debian.org \
    --cc=38803@debbugs.gnu.org \
    --cc=brettg@gnu.org \
    --cc=control@debbugs.gnu.org \
    --cc=mark@klomp.org \
    --cc=mbakke@fastmail.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.