All reports of package-uses-vendor-specific-patch-series for the archive. The extended description of this tag is:
The specified series file for patches is vendor-specific.
Source packages may contain vendor (i.e. distribution) specific patches, but such packages must not be uploaded to the Debian archive if they are used in conjunction with vendor-specific series files.
Vendor specific series files were carefully implemented as a dpkg feature. Unfortunately, they currently conflict with some workflow goals in Debian. They are presently disallowed in Debian.
The preferred approach for distributions other than Debian is now to apply such patches programmatically via debian/rules. You can also create multiple, vendor-specific sources and upload them separately for each distribution.
The decision to prohibit the use of that particular dpkg feature in Debian was made by the project's technical committee in consideration of other planned workflow modifications, and may be revisited.
You should only see this tag in Debian or other distributions when targeting an upload for Debian.
Refer to https://bugs.debian.org/904302, https://bugs.debian.org/922531, and https://lists.debian.org/debian-devel-announce/2018/11/msg00004.html for details.
Severity: important, Certainty: certain
Check: patch-systems, Type: source
Emitted (non-overridden): 3, overridden: 0, total: 3
The package names link to the relevant maintainer page and the corresponding report for the source package. The links go to the full maintainer report page, which includes info and experimental tags and overridden tags, rather than the default page that shows only errors and warnings.
fail2ban 0.10.2-2.1 (source) (Yaroslav Halchenko <firstname.lastname@example.org>)
libfreenect 1:0.5.3-1 (source) (Nicolas Bourdaud <email@example.com>)
smuxi 1.0.7-5 (source) (Mirco Bauer <firstname.lastname@example.org>)