summaryrefslogtreecommitdiff
path: root/devel/management/commands
AgeCommit message (Collapse)Author
2010-02-27reporead: add --filesonly optionDan McGee
This will allow files to be imported for all existing packages in the database while not worrying about the files database being a touch out of date. It utilizes the new files_last_update column to perform the insertion and updating of file lists intelligently. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-27reporead: support reading files entries againDan McGee
This depends on some changes I made to our script that generates the file list databases, but it allows us to treat the files databases in an almost identical manner to a regular database. The only difference is the fact that it contains 'files' entries. One catch that will be addressed in a separate patch: if the files DB lags behind the regular DB, running an update from it could cause packages in the web interface to be downgraded. A 'no-add/remove' option could be helpful for this case. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-27reporead: whitespace cleanupsDan McGee
Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-27reporead: only reset needsupdate when setting last_updateDan McGee
Otherwise a --force will clear out all our flagged packages. :/ Whoops. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-26reporead: build date data is crazyrelease_2010-02-26Dan McGee
Just ignore it if it is completely screwed up. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-26reporead: accommodate old-school build dateDan McGee
I can't believe we still have some of these around, but they are relatively straightforward to handle. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-26reporead: allow a force updateDan McGee
This allows re-running repoadd on all packages in case of adding data or fixing a bug without rendering the last_update values in the database useless. For packages that aren't geting their version bumped, don't touch last_update on a force import but do touch the rest of the fields. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-26Add some additional fields to package importDan McGee
We can capture the build date, compressed size, and installed size when reporead runs. Even if we don't show all of it, we should pull it in. FS#14270 is requesting that the package size be shown on the website. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-16reporead: use different timestamp for each packagerelease_2010-02-17Dan McGee
Since these timestamps will differ across repos and arches anyway (for a total of 10 distinct timestamps currently per hour), it isn't really necessary to only use one timestamp. Allow each package to get a unique creation time. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-10reporead: small touchups, mostly in argument validationDan McGee
Check the arch, check the filename for existence, etc. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-10reporead: turn into a django-admin commandDan McGee
Rather than struggle with getting the environment set up, let's make this a custom Django admin command and use the flexibility that gives us. This is the initial rough cut of making it happen; further commits should clean up some of the rough edges. Signed-off-by: Dan McGee <dan@archlinux.org>