From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: 28159@debbugs.gnu.org
Subject: bug#28159: Updater needs to support HTTP(S) servers
Date: Tue, 10 Sep 2019 19:25:58 +0200 [thread overview]
Message-ID: <901a1993-ed8e-4306-d3f2-f3dbcac30424@crazy-compilers.com> (raw)
In-Reply-To: <87poboasjz.fsf@gnu.org>
Am 22.08.17 um 10:57 schrieb Ludovic Courtès:
> More precisely, several updaters rely on FTP (gnu, kernel.org, kde,
> etc. see (guix gnu-maintenance)), but others rely on structured data
> retrieved over HTTP(S) (pypi, cran, elpa, etc.)
For the records: KDE no longer relies on FTP access. It now fetches the
ls-lR.bz2 file list using HTTPS from download.kde.org, converts it into
a list of file paths and caches the list.
See http://debbugs.gnu.org/cgi/bugreport.cgi?bug=36919
commit 4eb69bf0d33810886ee118f38989cef696e4c868
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2019-09-10 17:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-1238656@rt.gnu.org>
2017-08-20 12:06 ` bug#28159: Updater needs to support HTTP(S) servers Hartmut Goebel
2017-08-22 8:57 ` Ludovic Courtès
2017-08-23 10:20 ` Hartmut Goebel
2017-08-23 21:30 ` Ludovic Courtès
2017-08-26 9:54 ` Ludovic Courtès
2017-08-26 10:33 ` Hartmut Goebel
2017-09-03 21:40 ` Ludovic Courtès
2017-09-08 8:30 ` Ludovic Courtès
2017-09-14 16:50 ` bug#28159: [gnu.org #1238656] " Rubén Rodríguez Pérez via RT
2017-09-14 16:50 ` =?UTF-8?B?UnViw6luIFJvZHLDrWd1ZXogUMOpcmV6?= via RT
2017-09-15 7:50 ` Ludovic Courtès
2017-09-25 22:39 ` Ludovic Courtès
2018-11-10 22:38 ` Ludovic Courtès
2019-09-10 17:25 ` Hartmut Goebel [this message]
2020-04-29 8:21 ` bug#28159: Closing bug #28159? " Brice Waegeneire
2020-04-30 21:14 ` Ludovic Courtès
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=901a1993-ed8e-4306-d3f2-f3dbcac30424@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=28159@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.