hub.darcs.net :: simon -> hackage-server -> changes

We still accept it if the client offers it pre-emptively.

When someone tries to authenticate for a user account that has a legacy password, we previously returned 401 without any auth methods. It turns out that returning 401 in this case is a violation of the http spec because you must provide at least one auth method. So change it to use 403 Forbidden.

Maintainers and truestees can make new revisions without uploading a new tarball. Only certain changes are allowed. In particular adjusting dependency version constraints is allowed.

The feedback was that the links for maintainers were confusing for ordinary users because it is not clear if they are allowed to use them or not, and "maintain" is not very descriptive as a link name.

This patch removes the tags edit link from the package page. It moves the maintainer edit link to the bottom of the page and make it clearer that it is only for maintainers and trustees. The new maintainer page is now a lot clearer (and uses a template so easier to edit).

Center content, bigger font, wider page body, no justification of text

The public URI for the server may involve proxying etc, so the public URI might be http://new-hackage.haskell.org/ while we're actually serving on port 18512, which is reverse proxied to port 80. So we need to be able to set the public URI independently of our serving port, otherwise we would make links to http://new-hackage.haskell.org:18512/ which isn't accessable. (Most links are relative, but some have to be absolute, e.g. in emails and in rss feeds)

So we can now use throwError for auth errors. Previously we had to use finishWith which would bypass all the custom error page stuff. So this will give us pretty pages for auth errors.

Involves rewriting how the group lookup works. For groupResourcesAt we have not a single group but an indexed collection of groups, and so we need a way to lookup a group / check if a group exists. The previous solution involved the lookup never failing and having a method on the group to check if it is actually exists / if it's backed by something. Not only is that annoying and backwards but it meant we were doing the wrong thing in some cases. For maintainer groups we were checking if the maintainer group existed in the db, which meant we could not add members to the group if it was initially empty (because it was counted as not existing). That showed up as the import client failing to add users to the per-package maintainer groups (which all start out empty). So we get rid of the groupExists checks and instead allow the group lookup function to fail.

It's needed by lots of them now, as several features now load templates.

Previously a full backup would cost about 17Gb, now the incremental cost can be around 13Mb.

The backup and restore commands in particular really need that verbosity control, if only for testing/debugging.

Turns out IE just does not do xhtml at all, but can parse it in quirks mode if served it as text/html. We should probably just switch to using blaze-html and serve html5.

For all resources, we can now format errors in either plain text or in html, with themeing via templates. All resource handlers now operate in ServerPartE, features are allowed to provide error handlers for different content types and those are used by the resource serving system. They're picked usung content negotiation with backup choices from the default content type for the resource in question.

Update the data-files list in the .cabal file and add the little haskell png logo

So now the whole site has a consistent style. Previously we were using the Ocean theme for the per-package pages, and the old hackage style for everything else.

Modifications to the Ocean theme: * Larger text for the title bar * Paragraphs have max width and are justified

For the moment, have to list the top level templates explicitly since otherwise we clash with the legacy redirects.