Instead of linking the package name, link the architecture. This will
prevent the lost links we had when we collapsed the list to show multiple
architectures at the same time.
Signed-off-by: Dan McGee <dan@archlinux.org>
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>
We were double nesting the filelist div. Have the AJAX call only return the
contents and not the enclosing div.
Signed-off-by: Dan McGee <dan@archlinux.org>
Attempt to mark all packages built from the same PKGBUILD out of date at the
same time by using pkgbase instead of pkgname. Ensure testing and
non-testing repos are segregated as well.
Signed-off-by: Dan McGee <dan@archlinux.org>
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>
