When moving the news model and updating the content type, I forgot to update
these strings to reflect the new permission name. Whoops.
Signed-off-by: Dan McGee <dan@archlinux.org>
Set up a default DATE_FORMAT in settings.py and use it everywhere we do the
'|date' template filter rather than hardcoding the value in the template.
This also fixes a regression with news date/time now that we changed the
field to store both date and time.
Signed-off-by: Dan McGee <dan@archlinux.org>
By using the condition decorator (in a slightly odd way because these are
class-based views), we can cut down a lot on the response time for returning
304 status code for feeds that haven't changed. The decorator means we no
longer have to completely render the view to see if we can return a 304
status code.
Signed-off-by: Dan McGee <dan@archlinux.org>
This will come in handy when determining whether resources are out of date,
such as our news RSS feed. Also bump the Date fields to DateTime fields for
sake of sorting and if we have more than one news item on the same date.
Signed-off-by: Dan McGee <dan@archlinux.org>
This needed a little sprucing up as it has grown quite organically over the
life of this script. Make things a bit more pythonic through the use of
iterators rather than collection indexing, and try to generalize the special
cases of things a bit.
Also catch encoding problems early and fail gracefully rather than blow up
the entire package parser. A failed decode of a file should cause us to just
skip it rather than stop the entire parser. Worst case, this leaves that
package out of the web interface.
Signed-off-by: Dan McGee <dan@archlinux.org>
We need to do a little dropping into SQL to accomplish this, but it isn't
all that bad to actually do and we can do the whole thing in one query.
Signed-off-by: Dan McGee <dan@archlinux.org>
When I have caught reporead behaving badly on the production box, I haven't
been able to successfully get a traceback without killing the process.
Hopefully using a different signal will allow me to actually capture some
data.
Signed-off-by: Dan McGee <dan@archlinux.org>
Add total package count and incomplete package count columns. Also reduce
the number of total queries by killing the query per row that was happening
before.
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>
With package pooling we don't put things in the '/any/' folder anymore under
each repository; they only show up in the actual architectures. Use a 'real'
architecture as part of the download link to rectify this. Fixes FS#20779.
Signed-off-by: Dan McGee <dan@archlinux.org>
As reported by Thomas, the dashboard JS dies when we try to apply table
sorting to a table with no entries (those in the top section). Use some
selector magic to only apply tablesorting if the table actually has rows
worth sorting.
Also move the package todo lists table down in the dashboard as the other
two tables are more relevant for the individual developer.
Signed-off-by: Dan McGee <dan@archlinux.org>
This view was getting huge with ~500 items on it, and most people are not
really interested in seeing every single news item. Use the drop in
pagination and add some controls that still allow browsing to any page of
the list.
Signed-off-by: Dan McGee <dan@archlinux.org>
And also add the new style class we will need so the search form retains the
prior look, now that we are using this style elsewhere.
Signed-off-by: Dan McGee <dan@archlinux.org>
This is done as client-side JS which makes the page nice and fast. Minor
versions can be excluded, as can packages in [multilib]. In addition,
architecture filtering is in place so you can limit the subset of shown
packages to those in any, both, one or the other.
Signed-off-by: Dan McGee <dan@archlinux.org>
Add a second file for use in production environments where we know we
use memcached and MySQL, and for those that want to replicate the
production environment as close as possible. Slim down the primary file
to those requirements the app directly needs rather than how it is
installed. Also bump the version of South to the newer point release.
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>
Rather than the need to include RequestContext() calls directly, we can
just use direct_to_template to do all the work for us.
Signed-off-by: Dan McGee <dan@archlinux.org>
We can't cache most of the package actions links stuff because we look at
the user there, but we can cache everything on the left and the content of
the bottom boxes.
Signed-off-by: Dan McGee <dan@archlinux.org>
This will allow clicking through to a few more associated packages from a
given package, including those for the other architecture and potentially in
other repositories. The box floats to the right with the package actions,
which have also been restyled slightly so the whole area is a bit more
styled and set off from the rest of the page.
This should allow us to close the current oldest bug open in the Arch bug
tracker, FS#7787. I remember the days when every bug was a four-digit
number...
Signed-off-by: Dan McGee <dan@archlinux.org>
E.g. if we are looking at one version for a particular architecture, I want
to see all versions for all architectures in all repositories.
Signed-off-by: Dan McGee <dan@archlinux.org>
