Some ideas for DESCRIPTION checking

[maelle]

Possibly some of these are already implemented 🙈

• valid URLs (crul::ok() or httr equivalent) anywhere where there's an URL - including checking whether there's a redirect, i.e. when a repo was transferred to a new owner on GitHub, the URL should be changed although the old one is still valid because redirected.
• has the URLs (BugReports, Repository)
• only roles that exist
• no duplicate authors (tricky one when not for exact match)
• the description check that's already done somewhere else (stating it shouldn't start by "This package")
• no duplicate dependency, e.g. the same package twice once under Depends once under Suggests
• no missing necessary field
• no non-accepted fields
• ORCIDs (that would be "best-practice" and quite opiniated so probably not in scope) also cf Check for valid ORCID pkgcheck#200
• Anything that's in R CMD Check reg DESCRIPTION except with regard to the rest of the package.

[sda030]

Just got this one:
"It seems like you have too many spaces in your description field.
Probably because linebreaks count as spaces too.
Please remove unecassary ones."