From: Vagrant Cascadian <vagrant@debian.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>, kiasoc5@disroot.org
Cc: guix-devel@gnu.org
Subject: Re: Repology and outdated packages
Date: Thu, 11 Aug 2022 15:46:17 -0700 [thread overview]
Message-ID: <87ilmy7612.fsf@contorta> (raw)
In-Reply-To: <871qw0s43n.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
On 2022-06-07, Nicolas Goaziou wrote:
> kiasoc5@disroot.org writes:
>
>> I've been watching the Repology page for Guix and I've noticed that
>> we've dropped to 51% outdated packages
>> [https://repology.org/repository/gnuguix]. We used to be at 40%
>> outdated packages a few months ago.
>
> Repology hasn't been able to caught Guix package updates for a while
> now. As a consequence, many packages are marked as outdated in Repology
> even though they are not.
I wondered about this again, and was pointed to:
https://github.com/repology/repology-updater/issues/1261
Appears that where the website is hosted might indirectly (e.g. nobody
explicitly configured this on guix infrastructure) have traffic
originating in Russian blocked...
Wonder if it makes sense to sync the files to multiple sites and put in
round-robin DNS? Apparently it is already available at bayfront.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-08-11 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 18:39 Repology and outdated packages kiasoc5
2022-06-07 18:47 ` Nicolas Goaziou
2022-08-11 22:46 ` Vagrant Cascadian [this message]
2022-08-14 2:32 ` Maxim Cournoyer
2022-06-07 21:32 ` Maxime Devos
2022-06-09 8:02 ` Maxime Devos
2022-06-07 21:41 ` Maxime Devos
2022-06-08 21:38 ` Ludovic Courtès
2022-06-09 3:07 ` Oleg Pykhalov
2022-06-09 3:49 ` kiasoc5
2022-06-09 4:05 ` kiasoc5
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=87ilmy7612.fsf@contorta \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=kiasoc5@disroot.org \
--cc=mail@nicolasgoaziou.fr \
/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).