summaryrefslogtreecommitdiffstats
path: root/devel/management
AgeCommit message (Collapse)AuthorFilesLines
2010-02-27reporead: whitespace cleanupsDan McGee1-11/+11
Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-27reporead: only reset needsupdate when setting last_updateDan McGee1-1/+1
Otherwise a --force will clear out all our flagged packages. :/ Whoops. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-27reporead: build date data is crazyDan McGee1-1/+4
Just ignore it if it is completely screwed up. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-27reporead: accommodate old-school build dateDan McGee1-1/+4
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-27reporead: allow a force updateDan McGee1-11/+20
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-27Add some additional fields to package importDan McGee1-0/+4
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-17reporead: use different timestamp for each packageDan McGee1-3/+2
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-11reporead: small touchups, mostly in argument validationDan McGee1-23/+30
Check the arch, check the filename for existence, etc. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-11reporead: turn into a django-admin commandDan McGee3-0/+339
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>