| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
This is useful when looking back through history at what package versions were
previously available.
|
|
|
|
|
|
|
|
| |
Previously, if you searched for packages like Ruby or Guile, the actual Ruby
and Guile packages would be low in the rankings, as the terms Ruby or Guile
don't appear much in the descriptions.
Therefore, change the ordering to make these exact matches appear higher up.
|
| |
|
|
|
|
|
| |
As this is easier to handle when doing queries with PostgreSQL, as you can use
the type information to determine how to handle the values.
|
|
|
|
|
| |
Represent non-string home pages as NULL, and delete duplicates, as package
metadata entries can be duplicated.
|
| |
|
|
|
|
|
|
| |
This is useful when you want to pass in data with some duplicates, and get
back a list of ids, where the duplicate entries are represented by the same
id.
|
|
|
|
|
|
|
| |
Add tests around the package module, extract out the use of the
inferior-package record assessors so that they aren't part of the tests, and
switch across the package-metadata module to use
insert-missing-data-and-return-all-ids.
|
|
|
|
|
|
|
|
|
| |
squee, returns all data as strings, and expects strings as inputs to
queries. So, keeping the ids as strings was easy initially, but it means that
you can't tell from the type whether it should be quoted, or not...
Therefore, handle ids as strings, converting them to numbers when they're
fetched from the database, and back to strings as part of the queries.
|
|
|
|
| |
By using insert-missing-data-and-return-all-ids.
|
|
|
|
| |
Through using insert-missing-data-and-return-all-ids.
|
|
|
|
| |
As this now supports inserting sets of data.
|
|
|
|
|
|
| |
Use exec-query-with-null-handling to distinguish NULL values, change it to
just take a list of fields and remove the handlers. Also, add a sets-of-data?
parameter so that this can be used licenses.
|
|
|
|
| |
As these values are not from the database, which is why they're not strings.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
To associate a set of lint checkers with a specific revision. While there is
the association through the lint warnings, that only works for checkers where
there are lint warnings for that revision.
Therefore, to allow finding all the checkers for a specific revision, also
associate them directly with the revision.
|
|
|
|
|
|
|
|
| |
The first field is now a <derivation> record, rather than a store path for the
derivation.
It's probably not necessary to cope with two versions, but this is what I've
done currently.
|
| |
|
|
|
|
|
| |
To return counts of lint warnings, grouped by lint checker for a specific
revision.
|
|
|
|
|
|
|
|
|
|
| |
This commit adds the relevant tables and code to store lint warnings in the
database.
Currently, only lint checkers which don't require access to the network will
be run, as this allows the processing to happen without network access. Also,
this functionality won't work in older versions of Guix which don't expose the
lint warnings in a compatible way.
|
|
|
|
|
| |
This should help greatly with populating the database with new entries, and
greatly reduce code duplication.
|
| |
|
| |
|
|
|
|
| |
Rather than an id wrapped in a list.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The licenses table, along with the package_metadata table had duplicate
values. This could happen as the unique constraints on those tables didn't
properly account for the nullable fields.
The duplicates in those tables also affected the license_sets, packages,
package_derivations tables in a similar way. Finally, the
guix_revision_package_derivations table was also affected.
This commit adds a migration to fix the data, as well as the constraints. THe
code to populate the licenses and package_metadata tables is also updated.
|
|
|
|
| |
To enable adding a link to cgit to the comparison page.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Make the link between repositories and branches clearer, replacing the
/branches and /branch pages by /repository/ and /repository/*/branch/* pages.
|
|
|
|
|
| |
This happened for a package with #f as the licenses. That's incorrect, but try
to handle it without erroring.
|
|
|
|
|
| |
Also flip the branch and revision columns around, and add date information to
the branch column.
|
|
|
|
|
| |
And always link to the revision page. Now the label let's you know if you
should expect information or not for that revision.
|
|
|
|
|
| |
As these are used for logging, which is done on a line by line basis. Remove
the now redundant calls to (force-output).
|
|
|
|
|
|
| |
This makes is easier to get the latest data for a branch in a single request,
rather than making one request to find the latest revision, then another to
get the data.
|
|
|
|
|
|
| |
I'm not sure quite how to treat these yet, but for now, just stick with the
previous behaviour of showing revisions which haven't been processed yet,
along with the ones that have been successfully processed.
|
|
|
|
|
|
|
|
| |
Create a new events table for the new guix revision jobs, and update this when
processing a job starts, as well as finished with success or failure.
Additionally, remove the dependnency on open-inferior/container, as this
functionality isn't merged in to Guix master yet.
|
|
|
|
|
| |
To get git repository and git branch information suitable for the revision
page.
|
|
|
|
| |
This is useful for some queries with duplicated parts of the results.
|
|
|
|
|
| |
This is mostly for the JSON output, as it allows much more information to be
included.
|
|
|
|
|
| |
Previously, the timezone was stripped off, so the timestamps were off. This
commit changes the code to use a Unix timestamp, which avoids this issue.
|
|
|
|
|
|
|
|
|
|
| |
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.
|