bug#28159: Closing bug #28159? Updater needs to support HTTP(S) servers

Hi Brice, Brice Waegeneire skribis: > It looks like now most of the major updaters that relied on FTP (GNU, > kernel.org, KDE and Gnbome) now support HTTP(S). I think we can close > this > bug. Yup. There’s still the ‘gnu-ftp’ and the ‘xorg’ updaters which, according to ‘guix refresh --list-up

bug#28159: Closing bug #28159? Updater needs to support HTTP(S) servers

Hello Guix, It looks like now most of the major updaters that relied on FTP (GNU, kernel.org, KDE and Gnbome) now support HTTP(S). I think we can close this bug. Ludovic Courtès wrote on Tue Aug 22 10:57:20+0200 2017: More precisely, several updaters rely on FTP (gnu, kernel.org, kde, etc. se

bug#28159: Updater needs to support HTTP(S) servers

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 f

bug#28159: Updater needs to support HTTP(S) servers

l...@gnu.org (Ludovic Courtès) skribis: > l...@gnu.org (Ludovic Courtès) skribis: > >> This one is nice and smaller than ‘ls-lR’. I reimplemented the GNU >> updater in terms of this file, and kept the previous FTP-based updater >> around for GNU packages not hosted on ftp.gnu.org: >> >> >> htt

bug#28159: Updater needs to support HTTP(S) servers

l...@gnu.org (Ludovic Courtès) skribis: > This one is nice and smaller than ‘ls-lR’. I reimplemented the GNU > updater in terms of this file, and kept the previous FTP-based updater > around for GNU packages not hosted on ftp.gnu.org: > > > https://git.savannah.gnu.org/cgit/guix.git/commit/?id

bug#28159: [gnu.org #1238656] Re: bug#28159: Updater needs to support HTTP(S) servers

Hi Rubén, "Rubén Rodríguez Pérez via RT" skribis: > On Fri Sep 08 04:31:05 2017, l...@gnu.org wrote: [...] >> Could we arrange to have it regenerated every time a new file is >> uploaded? >> >> I suppose uploads aren’t this frequent, but regenerating ‘find.txt.gz’ >> right after an upload wou

bug#28159: [gnu.org #1238656] Re: bug#28159: Updater needs to support HTTP(S) servers

On Fri Sep 08 04:31:05 2017, l...@gnu.org wrote: > Hello sysadmins! Hi Ludo > How frequently is ftp.gnu.org/find.txt.gz updated? It seems to be > less > than once a day. It is run by cron.daily > Could we arrange to have it regenerated every time a new file is > uploaded? > > I suppose upload

bug#28159: [gnu.org #1238656] Re: bug#28159: Updater needs to support HTTP(S) servers

On Fri Sep 08 04:31:05 2017, l...@gnu.org wrote: > Hello sysadmins! Hi Ludo > How frequently is ftp.gnu.org/find.txt.gz updated? It seems to be > less > than once a day. It is run by cron.daily > Could we arrange to have it regenerated every time a new file is > uploaded? > > I suppose upload

bug#28159: Updater needs to support HTTP(S) servers

Hello sysadmins! How frequently is ftp.gnu.org/find.txt.gz updated? It seems to be less than once a day. Could we arrange to have it regenerated every time a new file is uploaded? I suppose uploads aren’t this frequent, but regenerating ‘find.txt.gz’ right after an upload would ensure that it’s

bug#28159: Updater needs to support HTTP(S) servers

Hi Hartmut, Hartmut Goebel skribis: > Also by chance ftp.gnu.org also provides a file `find.txt.gz`, listing > all files, including the full path: > > ./video/Stephen_Fry-Happy_Birthday_GNU-nq_600px_425kbit.ogv > ./old-gnu/g77/g77-0.5.21.tar.gz > ./old-gnu/guile > ./old-gnu/guile

bug#28159: Updater needs to support HTTP(S) servers

Hi, > I just learned that ftp://ftp.gnu.org will be retired on Nov. 1st, 2017, > so we’ll have to implement a replacement for the ‘gnu’ updater at least. By change, also this server provides a `ls-lrRt.txt.gz` file. Unfurtunaly is as a slightly different (date-) format than the one at kde.org: kd

bug#28159: Updater needs to support HTTP(S) servers

Hello, I just learned that ftp://ftp.gnu.org will be retired on Nov. 1st, 2017, so we’ll have to implement a replacement for the ‘gnu’ updater at least. At worst, we’ll parse HTML index files like the one at , but I’m trying to see if the FSF sysadmin could generat

bug#28159: Updater needs to support HTTP(S) servers

Hartmut Goebel skribis: > Am 22.08.2017 um 10:57 schrieb Ludovic Courtès: >> So I would suggest picking one updater, say kde, and implementing it >> using whatever metadata can be retrieved from kde.org. > > I'm not sure if I understood what you mean with "whatever metadata can > be retrieved fro

bug#28159: Updater needs to support HTTP(S) servers

Am 22.08.2017 um 10:57 schrieb Ludovic Courtès: > So I would suggest picking one updater, say kde, and implementing it > using whatever metadata can be retrieved from kde.org. I'm not sure if I understood what you mean with "whatever metadata can be retrieved from kde.org". By change, download.kd

bug#28159: Updater needs to support HTTP(S) servers

Hi Hartmut, Hartmut Goebel skribis: > our updater currently only supports FTP servers, 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.) > but more and more pr

bug#28159: Updater needs to support HTTP(S) servers

Hi, our updater currently only supports FTP servers, but more and more projects shutdown the FTP service and provide HTTP(S) servers only (e.g the Linux kernel). For other projects, the main distribution point has changed to HTTP and the mirrors still providing FTP at lagging (e.g. KDE, see [1]).