From: "\=\?UTF-8\?B\?UnViw6luIFJvZHLDrWd1ZXogUMOpcmV6\?\= via RT" <sysadmin@gnu.org>
To: ludo@gnu.org
Subject: bug#28159: [gnu.org #1238656] Re: bug#28159: Updater needs to support HTTP(S) servers
Date: Thu, 14 Sep 2017 12:50:28 -0400 [thread overview]
Message-ID: <rt-4.2.13-5-gc649048-446-1505407828-1344.1238656-5-0@rt.gnu.org> (raw)
In-Reply-To: <87r2vhk2x9.fsf@gnu.org>
On Fri Sep 08 04:31:05 2017, ludo@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 uploads aren’t this frequent, but regenerating ‘find.txt.gz’
> right after an upload would ensure that it’s always current.
I've modified the cron script to apply that change, now on the look for the next upload to see if it worked.
Regards,
--
Ruben Rodriguez | Senior Systems Administrator, Free Software Foundation
GPG Key: 05EF 1D2F FE61 747D 1FC8 27C3 7FAC 7D26 472F 4409
https://fsf.org | https://gnu.org
next prev parent reply other threads:[~2017-09-15 7:50 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 ` =?UTF-8?B?UnViw6luIFJvZHLDrWd1ZXogUMOpcmV6?= via RT [this message]
2017-09-15 7:50 ` bug#28159: [gnu.org #1238656] " Ludovic Courtès
2017-09-14 16:50 ` Rubén Rodríguez Pérez via RT
2017-09-25 22:39 ` Ludovic Courtès
2018-11-10 22:38 ` Ludovic Courtès
2019-09-10 17:25 ` Hartmut Goebel
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rt-4.2.13-5-gc649048-446-1505407828-1344.1238656-5-0@rt.gnu.org \
--to=sysadmin@gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).