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>
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>
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>
They look kind of silly on the front page when they are wrapped even though
the text is extremely short. Add a CSS property to hopefully prevent
wrapping.
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>
Since at least two repositories currently fall under this flag, add some
help text and visibility to this column.
Signed-off-by: Dan McGee <dan@archlinux.org>
Split it up as it is growing rather large, and add all the package files
views to the mix so Google or anyone can pick those up. They get a slightly
lower priority (if that even matters).
Signed-off-by: Dan McGee <dan@archlinux.org>
We were not handing depends of 'any' packages correctly if they depended on
arch-dependent packages; we labeled them all as virtual. If we have an 'any'
package, drop the arch screening and just pick one to link to.
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>
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>
We didn't include them on many pages, or the ones we did weren't always
useful. Also try to keep the boilerplate to a minimum so you can see the
important bits in the title. 'Arch Linux - ' comes first in all titles, and
from there it can be filled in with something useful.
Signed-off-by: Dan McGee <dan@archlinux.org>
For now, this contains one new template tag- 'jquery'. This will allow us to
use the Google AJAX CDN in non-debug environments, since there is really no
need for us to be the source of this common file. In the future this package
may gain other static media resource tags as well.
Signed-off-by: Dan McGee <dan@archlinux.org>
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>
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>
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>
Since the same URLs serve two different responses based on the request being
AJAX or not, we want to ensure we don't cache the wrong one and serve it up
incorrectly.
Signed-off-by: Dan McGee <dan@archlinux.org>
This will put the filelist inline on the package details page if using a
capable browser. It should still fallback to a separate page if necessary
(e.g. all those users using links on the site).
Signed-off-by: Dan McGee <dan@archlinux.org>
Put the link that has been commented back on the page, and point it at the
new URL for package files. Also fix the page title to be more in line with
all the other pages on the site.
Signed-off-by: Dan McGee <dan@archlinux.org>
