| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
As this means that like psql, the unix socket will be used.
|
| |
|
|
|
| |
This can be used with the mbox files for the guix-commits mailing list to add
older emails in to the database.
|
| |
|
|
|
| |
This is better, as different parts of the email might be encoded differently,
and guile-email will take care of this if handed a bytevector.
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
This helps when working out which connection to the database is doing what.
|
| |
|
|
|
| |
As these are used for logging, which is done on a line by line basis. Remove
the now redundant calls to (force-output).
|
| | |
|
| |
|
|
|
| |
This'll help the a service manager (like the shepherd) know when the service
is ready, which at the moment, means the database migrations have happened.
|
| |
|
|
| |
As this means it can find the relevant files.
|
| |
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
| |
It should never have been committed.
|
| | |
|
| | |
|
|
|
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
|