Upstream Release Monitoring

Upstream Release Monitoring

[Jason Self]

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

With the number of packages available using Guix (and it seems to keep
increasing) keeping up on the latest upstream versions manually is
gonna be a pain. :) Shouldn't the checking be automated in some way?
One idea might be to create a bug in the GNU Bug Tracker when a new
upstream release is detected.

Re: Upstream Release Monitoring

[Omar Radwan]

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

Another way might be to create a program that checks all the source repos
of all the packages. When a new package source file with a higher version
number gets uploaded, guix automatically builds the package and uploads it.
On Sep 11, 2014 8:31 PM, "Jason Self" <jason@bluehome.net> wrote:

> With the number of packages available using Guix (and it seems to keep
> increasing) keeping up on the latest upstream versions manually is
> gonna be a pain. :) Shouldn't the checking be automated in some way?
> One idea might be to create a bug in the GNU Bug Tracker when a new
> upstream release is detected.
>

[-- Attachment #2: Type: text/html, Size: 869 bytes --]

Re: Upstream Release Monitoring

[Andreas Enge]

On Thu, Sep 11, 2014 at 08:31:00PM -0700, Jason Self wrote:
> With the number of packages available using Guix (and it seems to keep
> increasing) keeping up on the latest upstream versions manually is
> gonna be a pain. :) Shouldn't the checking be automated in some way?
> One idea might be to create a bug in the GNU Bug Tracker when a new
> upstream release is detected.

There is already "guix refresh", but so far it works only for gnu packages;
with the parameter "-u", it even updates the version and hash, so if the
source uri is written using "string-append" and "version", it can update
package recipes automatically.

It would be interesting to generalise this to arbitrary packages. Maybe
an idea for the hackathon?

Andreas

Re: Upstream Release Monitoring

[Andreas Enge]

PS: And "guix refresh" lacks the automatic creation of the log message and
    the execution of "git commit" (while I would reserve the "git push"
    for some manual intervention).

Re: Upstream Release Monitoring

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> There is already "guix refresh", but so far it works only for gnu packages;
> with the parameter "-u", it even updates the version and hash, so if the
> source uri is written using "string-append" and "version", it can update
> package recipes automatically.
>
> It would be interesting to generalise this to arbitrary packages. Maybe
> an idea for the hackathon?

Definitely!

Ludo’.