Age | Commit message (Collapse) | Author | Files | Lines |
|
This follows the earlier commit where we make sure any value going to or
being pulled from the database is UTC.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
First steps towards implementing FS#23298.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
This comes with pacman 3.5, replacing the old "force" PKGBUILD option.
We parse it and store it for now, but don't display it anywhere just
yet. Also update a few queries relying on version differences in any of
the multiple parts.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
This datamigration is a bit more tricky and we do some DB-specific stuff
so it can be done a lot faster- we are dealing with millions of rows in
this migration in production.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
This allows us to store multiple licenses per package in a more elegant
fashion, and will later allow us to search and filter on this information.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
This will be used by the developer world clock page soon to come. Default
everyone to "UTC" for now.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
We had this set up as a unique ForeignKey before, which adds some
indirection due to the RelatedManager object being there. By making it a
OneToOneField, we can get the profile object directly, enforce uniqueness,
and also use it in select_related() calls to make our profiles page a bit
more efficient.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
The one thing that people forget to mention when moving models from one
Django app to another. I was fooled here.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Add a column flagging whether this architecture is agnostic (e.g. 'any') or
not. This will remove the hardcoded name checks we have all over the place
and replace it with a boolean.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Never would have guessed it should actually be in news/models.py.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
South actually makes this relatively painless if you get everything right,
so might as well start getting these out of the legacy main application to
eventually eliminate models being separate from their views.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Also update the repos fixture to include the new fields and [multilib]
repository.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Things like the flyspray project ID and SVN repo path should go here rather
than being hardcoded in the code.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
We had a package go in today that has an installed size > 2GB, which
makes PostgreSQL blow up when trying to create the package entry.
Enlarge these fields to big integers so they can store all conceivable
package size values.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
We had some dependency issues between migrations that needed to be
explicitly defined in order to get things fully moving, and do to some
braindeadness in Django tests not including the project url config, we need
to do some clever business when using the url tag in the base template so
tests don't doe with a NoReverseMatch exception.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
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>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Now that we always populate it, this change will make it a lot easier to use
when relating to other tables, such as our maintainer relations.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
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>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
I think I bumbled this up a while back, but make sure they aren't required
and we use the empty string for all of those that don't provide a value.
Fixes FS#18763.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
This will eventually lead into a cleanup where we don't do checks on the
repo name all over the place like we currently do.
There are two migrations involved here; one to add the column and one to
deduce the correct value from the existing names of the repos.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Rather than a short 255 character field.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
This wasn't strictly necessary and was more hassle than it was worth.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Allow this to be stored in the database for later use by an external
generation script for the rsyncd secrets file.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Add ability to track tier and upstream mirror in the database.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
This is necessary to keep all of our junk in sync since we aren't guaranteed
to have an up to date files database all the time.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
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>
|
|
Unnecessary, and lets us standardize on not using it everywhere.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Why issue lots of UPDATE queries when you can only issue one? My fail.
Signed-off-by: Evangelos Foutras <foutrelis@gmail.com>
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Put an actual NULL in the database and handle it for both display and
import. Also add a migration to clean up any bad data we currently have in
there. Fixes FS#17144.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Evangelos Foutras <foutrelis@gmail.com>
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Thanks to Evangelos Foutras for the inspiration. Recreated from scratch only
to make sure everything is in sync.
From this point on, you will need to have the 'south' Django/Python package
installed to use archweb.
Signed-off-by: Dan McGee <dan@archlinux.org>
|