MR: !191

This a more robust way of handling comments for mask as this work with
no comment or multi comments (not that it should happen but it's cleaner
anyway)

Signed-off-by: Baptiste Beauplat <lyknode@debian.org>

Signed-off-by: Baptiste Beauplat <lyknode@debian.org>

MR: !187


Signed-off-by: Mattia Rizzolo <mattia@debian.org>

In a class-based view, form_valid is only called when the form has been
validated. Moreover, we only call the dispatch parent class if the reset
link has been validated. Checking it again in form_valid is not needed.

The form is composed of two checkbox which are either absent for False
or present with any value for True. It's not possible for it to be not
valid.

The test is kept here for future needs.

Parses arbitrary email format such as Deb822's Maintainer or Changed-By
fields (Vincent Time <vtime@example.org>).

Allow mapping severity values directly using the dict key since the tag
list is (relatively) static and we actually want it to fail on unknown
tags.

While this could techincally allow reusing already parsed values for
uid, debexpo doesn't call this function twice for the same uid.

Since the pub: + fpr: sequence always appear in that order, once and on
top of a gpg with-colons output, the condition will always be true.

Since the default arguments have no action, an optional args doesn't
make sense.

Technically there is one more possibility but this never can be called
by the code.