evorepo/devel
Dan McGee 9da8a63dd4 Add DeveloperKey model
We're starting to see developers use subkeys of their primary key to
sign packages, which we aren't handling well in the web interface. These
subkeys show up as unknown, which isn't strictly true. Start the process
of being able to handle these keys by adding a model that will store all
known keys and subkeys and the relationships among them, as well as
which developer owns each.

Signed-off-by: Dan McGee <dan@archlinux.org>
2013-02-03 13:56:35 -06:00
..
management Handle connection and transaction more properly in reporead 2013-01-15 20:49:56 -06:00
migrations Add DeveloperKey model 2013-02-03 13:56:35 -06:00
__init__.py Initial import for public release... 2007-11-03 03:45:10 -04:00
admin.py Add DeveloperKey model 2013-02-03 13:56:35 -06:00
fields.py UserProfile model and fields shuffle 2012-04-20 11:15:03 -05:00
forms.py Split devel forms out of devel/views.py 2012-09-05 08:44:33 -05:00
models.py Add DeveloperKey model 2013-02-03 13:56:35 -06:00
tests.py UserProfile model and fields shuffle 2012-04-20 11:15:03 -05:00
urls.py Change Django urls.py import 2012-03-23 19:54:40 -05:00
utils.py Add ability to rematch developers on <username>@archlinux.org addresses 2012-08-15 08:11:00 -05:00
views.py Mark todolist packages as removed rather than deleting them 2012-12-31 11:31:35 -06:00