Just another annotation to the queryset to get this data, and a little more
manipulation in the group data function. This will help when adding a
sitemap in a subsequent commit.
Signed-off-by: Dan McGee <dan@archlinux.org>
This makes the support asked for in FS#19801 a lot more useful since we
actually have an overview page for the entire group.
Signed-off-by: Dan McGee <dan@archlinux.org>
Show all the details the developer page does, make the lists always visible,
and add JS table sorting to each table on the page. This commit also adds
table sorting to the developer list view as well.
Signed-off-by: Dan McGee <dan@archlinux.org>
Anything that it makes sense to add it to gets the treatment here. Anything
with pagination can wait as that will be tougher. We also need to deal with
odd/even formatting.
Signed-off-by: Dan McGee <dan@archlinux.org>
We can rip out a lot of the code for SVN and bugs links now that this data
is pulled off the model instead.
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>
Implements FS#20416. Port over the architecture differences view from
archlinux.de and reimplement in Django with our DB schema. Also use a far
simpler SQL query to do the dirty work rather than the triple UNION
operation. This is accomplished by doing a bit more of the fetching work in
code once we know what packages are actually involved.
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>
Instead of just showing usernames. It is especially helpful since we have
many similarly named developers at this point. In addition, only show active
developers/TUs and remove the rest from the list.
Also remove some cargo-cult code that set widget.choices; this is not
necesary as the widget automatically grabs the choices from the field.
Signed-off-by: Dan McGee <dan@archlinux.org>
This will work out well when using memcached in production, and should just
fall back to using the DB when developing locally with no cache or any other
sort of caching.
Signed-off-by: Dan McGee <dan@archlinux.org>
Every once in a while we see this command hanging on the main server but it
isn't making any system calls, so it is hard to tell where it is getting
stuck. Add a signal handler on SIGQUIT that will listen and print a
traceback when signaled.
This is the easiest thing to implement; future additions may need to be able
to hook up to a remote debugger (e.g. pdb) if this doesn't work.
Signed-off-by: Dan McGee <dan@archlinux.org>
With suggestions from Jason Chu, make the code a bit less repetitive with
regards to exception handling and fallthrough to the next method of finding
the user.
Signed-off-by: Dan McGee <dan@archlinux.org>
Otherwise we get duplicate groups each time we update the package, and any
group removals would never actually happen.
Signed-off-by: Dan McGee <dan@archlinux.org>
This is a bit more work than just a simple field addition. We attempt to map
packager specs (e.g. "A. U. Thor <author@example.com>") to actual Django
users in a relatively robust way- first try matching on User.email, then
fall back to UserProfile.public_email, then finally try a name-based match.
For those packages we can't generate a mapping, the raw string is still
stored so it can be displayed.
Signed-off-by: Dan McGee <dan@archlinux.org>
