From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: please update recutils - I know there's a script for that, in this case it didn't work
Date: Tue, 27 Apr 2021 14:32:25 +0200 [thread overview]
Message-ID: <20210427123225.KEW6JiXpnuKTpgHjl1vB46p72AxbmgIElooTuUx39dw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30546@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/30546#issuecomment-827570226
Comment:
> For some deep GNU reasons https://ftp.gnu.org/gnu/recutils/?C=M;O=A stops at 1.8,
> while https://alpha.gnu.org/gnu/recutils/ has the version with the bugfix included
1.8 is the latest version, 1.8.90 is a pre release before 1.9.
> (I'm reporting this here because it's not 100% clear to me if the GNU folks messed up updating the tarball
> or there's a problem with the update script; fwiw the exact same issue happens on debian/sid)
No one messed anything up I think, there just wasn't a release which fixes this bug yet. I am not sure what the update script you are talking about is, but debian packages recutils v1.8 without any patches just like void, so it's expected to not work there.
next prev parent reply other threads:[~2021-04-27 12:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 12:09 [ISSUE] " loreb
2021-04-27 12:32 ` paper42 [this message]
2021-04-27 14:29 ` loreb
2021-04-27 22:10 ` ericonr
2021-04-28 12:19 ` loreb
2021-04-28 12:56 ` loreb
2021-04-28 13:04 ` ericonr
2021-04-28 14:41 ` loreb
2021-04-28 15:08 ` ericonr
2021-04-28 16:00 ` loreb
2021-04-28 16:18 ` ericonr
2021-04-28 21:26 ` loreb
2021-04-28 21:28 ` ericonr
2021-04-28 21:34 ` loreb
2021-04-28 21:40 ` loreb
2022-05-18 2:09 ` github-actions
2022-05-21 18:40 ` [ISSUE] [CLOSED] " paper42
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=20210427123225.KEW6JiXpnuKTpgHjl1vB46p72AxbmgIElooTuUx39dw@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).