unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: mail@cbaines.net, guix-devel@gnu.org
Subject: Re: Fedora/Debian release monitoring inspiration for Guix Data Service
Date: Tue, 16 Mar 2021 12:14:32 +0100	[thread overview]
Message-ID: <fc19c33fbdbb40c6c1010949ec3a05e7e0088a6d.camel@zaclys.net> (raw)
In-Reply-To: <87k0q7mjxa.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]

On Tue, 2021-03-16 at 12:12 +0100, Ricardo Wurmus wrote:
> Léo Le Bouter <lle-bout@zaclys.net> writes:
> 
> > I am thinking we should really get something like this with the
> > Guix
> > Data Service, start including something similar to Debian
> > uscan/watch
> > rules in every package so we can get reliable (in majority of
> > cases)
> > update notifications.
> 
> “guix lint” has a checker for releases:
> 
> --8<---------------cut here---------------start------------->8---
> $ guix lint -l
> Available checkers:
> […]
> - refresh: Check the package for new upstream releases
> --8<---------------cut here---------------end--------------->8---
> 
> It just needs to be extended to cover more packages.
> 
> Developing a service that runs this for all packages is an orthogonal
> issue.
> 

Just to clarify, I do know it exists and use it often :-)
Indeed it needs to be extended and that's what I am talking about
there, also Guix Data Service is important here because we cannot
possibly each on our sides spam the various URLs or APIs to generate
the release monitoring dataset. Instead, using Guix Data Service for
that with specially configured API keys and else sounds like a better
idea.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-03-16 11:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 10:57 Fedora/Debian release monitoring inspiration for Guix Data Service Léo Le Bouter
2021-03-16 11:12 ` Ricardo Wurmus
2021-03-16 11:14   ` Léo Le Bouter [this message]
2021-03-16 23:28 ` Christopher Baines
2021-03-17 10:24   ` Léo Le Bouter
2021-03-17 17:35 ` Ludovic Courtès
2021-03-17 17:47   ` Léo Le Bouter
2021-03-20 11:22     ` 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=fc19c33fbdbb40c6c1010949ec3a05e7e0088a6d.camel@zaclys.net \
    --to=lle-bout@zaclys.net \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    --cc=rekado@elephly.net \
    /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).