summaryrefslogtreecommitdiffstats
path: root/devel
AgeCommit message (Collapse)AuthorFilesLines
2010-05-26Have reporead populate filename columnDan McGee1-0/+1
Signed-off-by: Dan McGee <dan@archlinux.org>
2010-05-24reporead: use the DB package we already haverelease_2010-05-24Dan McGee1-5/+3
Rather than go to the database for every single package on something like a files update, use the one we already have. Duh. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-05-24Fix null field issues exposed by Django 1.1.2Dan McGee1-5/+0
Apparently Django 1.1.1 let null fields pass right through but this now causes reporead to blow up in 1.1.2. Fix the issue and get things working again by allowing nulls where it probably makes sense and including a migration to fix the issue, which for the real database will be a no-op. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-05-24Change link to new dev site locationDan McGee1-1/+1
Signed-off-by: Dan McGee <dan@archlinux.org>
2010-05-04Ensure changing profile email doesn't reset passwordDan McGee1-9/+6
We weren't checking to see if the password form fields were empty before setting the user password, causing it to get reset if anything was filled out and submitted on this page. FS#19345. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-04-16reporead: allow removal of last package in an archDan McGee1-10/+8
We had a situation where the last 'any' architecture package was present in the [testing] repo and never got removed because we never did the db_update() call on that architecture. Instead of looping all possible architectures and only calling if len() > 0, always call db_update() for both the primary architecture and the 'any' architecture. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-03-27Simplify code now that pkgbase is always definedrelease_2010-03-28Dan McGee1-1/+1
This allows some of our queries to get a lot simpler as well as removing the pkgbase_safe property added earlier. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-03-27Make reporead always populate pkgbaseDan McGee1-1/+4
And also add a data migration to add the value retroactively for anything already in our database. We simply fall back to pkgname if pkgbase isn't available. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-03-27Move package maintainer off of package modelDan McGee1-3/+10
This is an attempt to fix our long-standing problems dealing with maintainer information. Move the actual maintainer information off of the package model into a PackageRelation object, which has some flexibility to later represent more than just maintainership. This solves multiple problems: * If a package gets accidentally deleted, so did the maintainer info * Testing packages have always shown up as orphans * With split packages, it was easy to miss some of the sub-packages This commit does not include the deletion of the original maintainer column; that will come at a later time when I feel more confident that the data was migrated correctly. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-03-10Fix one missed testing repo checkDan McGee1-1/+1
Signed-off-by: Dan McGee <dan@archlinux.org>
2010-03-01Merge branch 'package-files'Dan McGee1-29/+61
2010-02-27Make reporead.py not executableDan McGee1-0/+0
Signed-off-by: Dan McGee <dan@archlinux.org>
2010-02-27reporead: add --filesonly optionDan McGee1-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-27reporead: support reading files entries againDan McGee1-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-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-26reporead: build date data is crazyrelease_2010-02-26Dan McGee1-1/+4
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 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-26reporead: 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-26Add 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-16reporead: use different timestamp for each packagerelease_2010-02-17Dan 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-10reporead: 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-10reporead: 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>
2010-02-10Remove archweb prefix from all importsDan McGee1-4/+4
Unnecessary, and lets us standardize on not using it everywhere. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-01-31Make marking out of date actually workDan McGee1-5/+3
And honor the packager's notify flag, as Pierre pointed out. Signed-off-by: Dan McGee <dan@archlinux.org>
2010-01-31Adjust models and views for nullable maintainerEvangelos Foutras1-1/+1
Signed-off-by: Evangelos Foutras <foutrelis@gmail.com> [Dan: made a few other small touchups] Signed-off-by: Dan McGee <dan@archlinux.org>
2010-01-30Use select_related() for some mirror pagesDan McGee1-1/+1
We also traverse relationships here, so select the associated items. Signed-off-by: Dan McGee <dan@archlinux.org>
2009-12-01Add credential requirements tests to devel appIsmael Carnales3-4/+41
* Add models.py required file to app * Use user_passes_test instead of custom superuser checking in new_user_form as it implements the same "next" redirection as login_required Signed-off-by: Ismael Carnales <icarnales@gmail.com>
2009-11-09added login_required to devel viewsIsmael Carnales1-0/+5
2009-11-09changed landing viewIsmael Carnales1-9/+0
- moved devel.views.siteindex to public.views.index - using template from public view with added devel menu - added extra styles and images
2009-11-09modified import paths from archweb_dev to archwebIsmael Carnales1-4/+4
2009-09-15Add a basic mirror view for the dev siteDan McGee1-0/+6
Signed-off-by: Dan McGee <dan@archlinux.org>
2009-08-12merge fixDusty Phillips1-3/+3
2009-08-11So now the created user passwords should work and Aaron will be less pissed ↵Dusty Phillips1-4/+4
off at me.
2009-08-10Sometimes its better if you test your code before deploying. Other times, ↵Dusty Phillips1-0/+1
you just fix the missing imports in a second commit.
2009-08-10Add a page to aid Aaron in user creation.Dusty Phillips1-1/+52
2009-01-30Put maintainer list by last name.Dusty Phillips1-1/+1
2008-11-15alphabetical order on maintainers and packagesDusty Phillips1-1/+1
2008-11-09don't show inactive users in dev listDusty Phillips1-1/+1
2008-10-11simplify both look and code for dashboardDusty Phillips1-13/+11
2008-10-10use RequestContext because its standardDusty Phillips1-6/+7
2008-10-10drop useless viewDusty Phillips1-6/+3
2008-10-10fix broken maintainer packages linksDusty Phillips1-14/+6
2008-10-07make form submit some but not all valuesDusty Phillips1-2/+2
2008-10-07move validation template tage temporarily; it will be removed eventuallyDusty Phillips2-15/+0
2008-10-07fairly invasive refactor to developer dashboard to be more django friendlyDusty Phillips1-22/+5
2008-10-07indicate that index is the dev dashboardDusty Phillips1-1/+1
2008-10-07fix bug introduced by previous code removalDusty Phillips1-0/+2
2008-10-07Dusty's 80 char issueDusty Phillips1-2/+2
2008-10-07remove senseless codeDusty Phillips1-5/+0
generated by cgit v1.2.3-55-g3dc8 (git 2.39.1) at 2024-04-26 03:39:47 +0000