| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
This computes and displays the tokens needed to send build events to the Guix
Data Service.
|
| |
|
|
|
| |
This can be used with the mbox files for the guix-commits mailing list to add
older emails in to the database.
|
| |
|
|
|
|
| |
This allows easily processing an individual job by id. This may be useful to
use manually, but also when processing jobs in parallel, as forking doesn't
work well with the libpq library used by squee.
|
| |
|
|
|
|
| |
And use it for the hosting the inferiors, rather than computing the guix
package at runtime. This simplifies the behaviour when the Guix Data Service
is deployed as a Guix package.
|
| |
|
|
| |
So that it can always find psql.
|
| |
|
|
|
|
| |
This runs Sqitch on startup, which should make managing the database easier,
as you just have to restart the service with this option, and the database
should be updated if necessary.
|
| |
|
|
| |
Along with the buildsystem changes to make `make check` work.
|
| | |
|
| | |
|
|
|
This is a service designed to provide information about Guix. At the
moment, this initial prototype gathers up information about packages,
the associated metadata and derivations.
The initial primary use case is to compare two different revisions of
Guix, detecting which packages are new, no longer present, updated or
otherwise different.
It's based on the Mumi project.
[1]: https://git.elephly.net/software/mumi.git
|