From: "Ludovic Courtès" <ludo@gnu.org>
To: 47597@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#47597] [PATCH 0/3] Add SourceForge updater and lint warnings
Date: Sun, 4 Apr 2021 22:58:35 +0200 [thread overview]
Message-ID: <20210404205835.30850-1-ludo@gnu.org> (raw)
Hi!
These patches add a ‘sourceforge’ updater. Initially I tried
implementing it in terms of ‘latest-html-release’ but that doesn’t
work because of the peculiar URL scheme that SF uses, with “/download”
appended to otherwise nice-looking URLs.
Instead, this one looks at the /latest URL supported by SourceForge.
It’s less efficient than ‘generic-html’ for instance because there’s
no caching and there’s up to three additional HEAD requests performed
to find if there are detached signatures.
The last patch has ‘guix lint -c refresh’ emit warnings when a package
lacks an updater or when its updater doesn’t work. This should help us
find out which updaters need to be improved or implemented.
Feedback welcome!
Ludo’.
Ludovic Courtès (3):
gnu-maintenance: Add 'sourceforge' updater.
upstream: 'package-latest-release' tries all the matching updaters.
lint: refresh: Warn about missing or dysfunctional updaters.
doc/guix.texi | 2 ++
guix/gnu-maintenance.scm | 55 ++++++++++++++++++++++++++++++++++++++++
guix/lint.scm | 41 +++++++++++++++++++-----------
guix/upstream.scm | 15 ++++++-----
4 files changed, 92 insertions(+), 21 deletions(-)
--
2.31.1
next reply other threads:[~2021-04-04 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 20:58 Ludovic Courtès [this message]
2021-04-04 21:03 ` [bug#47597] [PATCH 1/3] gnu-maintenance: Add 'sourceforge' updater Ludovic Courtès
2021-04-04 21:03 ` [bug#47597] [PATCH 2/3] upstream: 'package-latest-release' tries all the matching updaters Ludovic Courtès
2021-04-04 21:03 ` [bug#47597] [PATCH 3/3] lint: refresh: Warn about missing or dysfunctional updaters Ludovic Courtès
2021-04-05 15:38 ` [bug#47597] [PATCH 0/3] Add SourceForge updater and lint warnings Mathieu Othacehe
2021-04-05 16:03 ` Ludovic Courtès
2021-04-06 22:01 ` bug#47597: " Ludovic Courtès
2021-04-05 15:46 ` [bug#47597] " Léo Le Bouter via Guix-patches via
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=20210404205835.30850-1-ludo@gnu.org \
--to=ludo@gnu.org \
--cc=47597@debbugs.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.