public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: elfutils 0.185 released
Date: Sat, 22 May 2021 21:47:20 +0200	[thread overview]
Message-ID: <YKlfyLLH/+Up3Sjm@wildebeest.org> (raw)

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

ELFUTILS 0.185 - http://elfutils.org/

A new release of elfutils is available at:
ftp://sourceware.org/pub/elfutils/0.185/
or https://sourceware.org/elfutils/ftp/0.185/

This is a fixup release for two small regression bugs introduced in
0.184.  eu-elfcompress would return a non-zero exit code if no
(de)compression needed to be done.  Reusing a debuginfod handle would
not retry downloads that produced an error earlier.  Both those issues
have been fixed in 0.185

Visit us on the Libera.Chat irc channel #elfutils

* NEWS *

debuginfod-client: Simplify curl handle reuse so downloads which
                   return an error are retried.

elfcompress: Always exit with code 0 when the operation succeeds (even
             when nothing was done). On error the exit code is now always 1.

* GIT SHORTLOG *

Dmitry V. Levin (3):
   elfcompress: fix exit status regression in case of "Nothing to do"
   elfcompress: remove redundant assignment
   elfcompress: fix exit status in case of an error

Frank Ch. Eigler (2):
   elfutils.spec: Add procps as a %check BuildRequires:.
   PR27859: correct 404-latch bug in debuginfod client reuse

Mark Wielaard (1):
   Prepare for 0.185

Martin Liska (1):
   Come up with startswith function.

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

                 reply	other threads:[~2021-05-22 19:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=YKlfyLLH/+Up3Sjm@wildebeest.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.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.
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).