| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
| |
And display this on the package page.
This uses a couple of new tables, and an additional field in the
package_metadata table.
Currently, the order of the licenses in the package definition isn't stored,
as I'm not sure the order in the list is significant.
|
| |
|
|
|
|
|
|
| |
On one code path, they were handled as numbers, whereas elsewhere they were
handled as strings. This led to the package-metadata code trying to insert
duplicate entries.
Instead, just handle them as strings everywhere.
|
| |
|
|
| |
So at least they're stable.
|
| |
|
|
|
|
|
| |
Store the location a package can be found at, and display this on the package
page.
If available, link off to the git repository containing the package.
|
| | |
|
| |
|
|
|
| |
Lower powered devices will have problems displaying all ~9000+ packages, so
return a smaller number by default.
|
| |
|
|
|
|
|
|
| |
I'm thinking about adding more fields to this table, and the sha1_hash values
will make this tricker.
Therefore, remove the value, and adjust the existing code to cope. This commit
also adds a new test which coveres some of the changed functionality.
|
| | |
|
| |
|
|
|
|
| |
Add handling for some query parameters to the branch page. This takes
advantage of the improvements for building forms and query parameter
validation.
|
| |
|
|
|
|
| |
Add some new pages /branches and /branch/... as well as a new git_branches
table. Also extend the email processing to enter the branch information in to
the database.
|
| |
|
|
|
|
| |
Rather than just storing the URL in the guix_revisions and
load_new_guix_revision_jobs tables. This will help when storing more
information like tags and branches in the future.
|
| | |
|
| | |
|
| |
|
|
|
| |
This can happen when the same package is defined with two names, for example,
with deprecated-package.
|
| | |
|
| |
|
|
|
|
| |
An empty list of derivation-file-names should result in no results,
but in the case of the systems, targets and build-statuses, we want
all of the results.
|
| |
|
|
| |
Fix handling derivations which target multiple systems (somehow?).
|
| |
|
|
| |
As this can make the queries a bit more readable.
|
| | |
|
| |
|
|
|
| |
Add support for filtering the results, and add the system and target
to the output.
|
| |
|
|
|
| |
Just load in the ones that are not already in the database, as this
will hopefully be faster and require less memory.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
A large proportion of these changes relate to changing the way
packages relate to derivations. Previously, a package at a given
revision had a single derivation. This was OK, but didn't account for
multiple architectures.
Therefore, these changes mean that a package has multiple derivations,
depending on the system of the derivation, and the target system.
There are multiple changes, small and large to the web interface as
well. More pages link to each other, and the visual display has been
improved somewhat.
|
| | |
|
| | |
|
| |
|
|
| |
For showing more information about builds, revisions and derivations.
|
| |
|
|
| |
On the comparison page.
|
| |
|
|
| |
These will allow tracking what's going on with build servers.
|
| |
|
|
|
|
| |
These changes mean that more information about derivations is
recorded. There are a number of corresponding changes in the database
schema that are not tracked in the repository unfortunately.
|
| | |
|
|
|
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
|