Common practice for downstreams (whether complete derivatives or end users) is
to version modified packages with a version number like
4.16.5-1+something1
Where "something" is the name of a project, the name of the person performing
the modification etc.
Unfortunately with 4.16.5-1 of the kernel package such a version number is no longer
accepted with the error message "Invalid debian linux version". It seems the
cause of this was the following change.
(?P<revision_other>
- [^-]+
+ [^-+]+
)
Reverting this change allowed me to get a succesful control files generation.
