archweb - Main repo is at https://projects.archlinux.org/archweb.git/

Age	Commit message (Collapse)	Author	Files	Lines
2010-02-28	Make reporead.py not executable	Dan McGee	1	-0/+0
	Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-27	reporead: add --filesonly option	Dan McGee	1	-26/+47
	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-27	reporead: support reading files entries again	Dan McGee	1	-8/+19
	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-27	reporead: whitespace cleanups	Dan McGee	1	-11/+11
	Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-27	reporead: only reset needsupdate when setting last_update	Dan McGee	1	-1/+1
	Otherwise a --force will clear out all our flagged packages. :/ Whoops. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-27	reporead: build date data is crazy	Dan McGee	1	-1/+4
	Just ignore it if it is completely screwed up. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-27	reporead: accommodate old-school build date	Dan McGee	1	-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-27	reporead: allow a force update	Dan McGee	1	-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-27	Add some additional fields to package import	Dan McGee	1	-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-17	reporead: use different timestamp for each package	Dan McGee	1	-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-11	reporead: small touchups, mostly in argument validation	Dan McGee	1	-23/+30
	Check the arch, check the filename for existence, etc. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-11	reporead: turn into a django-admin command	Dan McGee	3	-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>