Language
Lint warnings where the package name matches the query.
Lint warnings for specific lint checkers.
Lint warnings where the message matches the query.
Fields to return in the response.

Lint warnings

PackageLinterMessageLocation
zn-poly @ 0.9.2description

Validate package descriptions

description should start with an upper-case letter or digit
wxwidgets-gtk2 @ 3.1.0description

Validate package descriptions

description should start with an upper-case letter or digit
wxwidgets-gtk2 @ 3.0.5.1description

Validate package descriptions

description should start with an upper-case letter or digit
robin-map @ 0.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 281
rcm @ 1.3.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 183
python-wxpython @ 4.0.7.post1description

Validate package descriptions

description should start with an upper-case letter or digit
perl6-grammar-debugger @ 1.0.1-1.0375008description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 203
perl-test-file-contents @ 0.23description

Validate package descriptions

description should start with an upper-case letter or digit
kget @ 20.04.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 169
java-jblas @ 1.2.4description

Validate package descriptions

description should start with an upper-case letter or digit
python2-langkit @ 0.0.0-0.fe0bc8binputs-should-be-native

Identify inputs that should be native inputs

'python2-docutils' should probably be a native input
python-debtcollector @ 1.19.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
presentty @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
flex @ 2.6.4inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
flex @ 2.6.4inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
cinnamon-desktop @ 3.4.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
bison @ 3.6.3inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
bison @ 3.6.3inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
bison @ 3.5.3inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
bison @ 3.5.3inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
bison @ 3.0.5inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
bison @ 3.0.5inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
aseba @ 1.6.0-0.3b35de8inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
rdmd @ 2.077.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
infiniband-diags @ 2.0.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
mkbootimg @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-settings-builder @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-settings @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-resolver-provider @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-repository-metadata @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-plugin-api @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-model-builder @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-model @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-builder-support @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-artifact @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libmhash @ 0.9.9.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libcanberra-gtk2 @ 0.30patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
jfsutils-static @ 1.1.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
idutils @ 4.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
fastboot @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
bash-static @ 5.0.16patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
bash-minimal @ 5.0.16patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
android-libziparchive @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
android-libutils @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
android-libsparse @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
android-liblog @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
android-libcutils @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
adb @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
sdsl-lite @ 2.1.1formatting

Look for formatting issues in the source

line 237 is way too long (145 characters)
sdl-mixer @ 1.2.12formatting

Look for formatting issues in the source

line 260 is way too long (92 characters)
sdl-image @ 1.2.12formatting

Look for formatting issues in the source

line 223 is way too long (91 characters)
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

line 213 is way too long (106 characters)
raspi-arm64-chainloader @ 0.1formatting

Look for formatting issues in the source

line 211 is way too long (139 characters)
raspi-arm64-chainloader @ 0.1formatting

Look for formatting issues in the source

line 224 is way too long (97 characters)
raspi-arm-chainloader @ 0.1formatting

Look for formatting issues in the source

line 131 is way too long (129 characters)
raspi-arm-chainloader @ 0.1formatting

Look for formatting issues in the source

line 137 is way too long (102 characters)
pth @ 2.0.7formatting

Look for formatting issues in the source

trailing white space on line 42
presentty @ 0.2.1formatting

Look for formatting issues in the source

line 45 is way too long (117 characters)
perl-test2-plugin-nowarnings @ 0.06formatting

Look for formatting issues in the source

line 106 is way too long (92 characters)
papi @ 5.5.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ncurses @ 6.2formatting

Look for formatting issues in the source

trailing white space on line 165
ncurses @ 6.2formatting

Look for formatting issues in the source

line 179 is way too long (94 characters)
musl-cross @ 0.1-3.a8a6649formatting

Look for formatting issues in the source

line 152 is way too long (92 characters)
mrustc @ 0.9formatting

Look for formatting issues in the source

line 178 is way too long (123 characters)
maven-wagon-http @ 3.3.4formatting

Look for formatting issues in the source

line 901 is way too long (105 characters)
maven-wagon-http @ 3.3.4formatting

Look for formatting issues in the source

line 906 is way too long (138 characters)
maven-wagon-http @ 3.3.4formatting

Look for formatting issues in the source

line 907 is way too long (129 characters)
maven-wagon-file @ 3.3.4formatting

Look for formatting issues in the source

line 738 is way too long (125 characters)
maven-shared-utils @ 3.2.1formatting

Look for formatting issues in the source

line 583 is way too long (109 characters)
maven-resolver-transport-wagon @ 1.3.1formatting

Look for formatting issues in the source

line 255 is way too long (91 characters)
maven-resolver-transport-wagon @ 1.3.1formatting

Look for formatting issues in the source

line 270 is way too long (106 characters)
maven-resolver-transport-wagon @ 1.3.1formatting

Look for formatting issues in the source

line 284 is way too long (102 characters)
maven-resolver-impl @ 1.3.1formatting

Look for formatting issues in the source

line 201 is way too long (92 characters)
maven-resolver-impl @ 1.3.1formatting

Look for formatting issues in the source

line 210 is way too long (92 characters)
maven-resolver-impl @ 1.3.1formatting

Look for formatting issues in the source

line 218 is way too long (95 characters)
maven-resolver-impl @ 1.3.1formatting

Look for formatting issues in the source

line 221 is way too long (93 characters)
maven-resolver-connector-basic @ 1.3.1formatting

Look for formatting issues in the source

line 165 is way too long (99 characters)
lxde-common @ 0.99.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libsigsegv @ 2.12formatting

Look for formatting issues in the source

line 48 is way too long (133 characters)
libdaemon @ 0.14formatting

Look for formatting issues in the source

line 35 is way too long (147 characters)
libdaemon @ 0.14formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ldc @ 1.10.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ldc @ 0.17.6formatting

Look for formatting issues in the source

line 130 is way too long (98 characters)
kget @ 20.04.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
js-mathjax @ 2.7.2formatting

Look for formatting issues in the source

line 150 is way too long (91 characters)
hyperledger-iroha @ 1.1.1formatting

Look for formatting issues in the source

line 169 is way too long (105 characters)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

line 186 is way too long (91 characters)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

line 191 is way too long (91 characters)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

line 196 is way too long (91 characters)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

line 197 is way too long (99 characters)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

line 198 is way too long (91 characters)
gx @ 0.14.3formatting

Look for formatting issues in the source

line 126 is way too long (91 characters)
gx @ 0.14.3formatting

Look for formatting issues in the source

line 131 is way too long (91 characters)
gx @ 0.14.3formatting

Look for formatting issues in the source

line 136 is way too long (91 characters)
gx @ 0.14.3formatting

Look for formatting issues in the source

line 137 is way too long (99 characters)
gx @ 0.14.3formatting

Look for formatting issues in the source

line 138 is way too long (91 characters)
gx @ 0.14.3formatting

Look for formatting issues in the source

line 145 is way too long (91 characters)
guile-wm @ 1.0-1.f3c7b3bformatting

Look for formatting issues in the source

line 128 is way too long (92 characters)
go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1formatting

Look for formatting issues in the source

line 81 is way too long (93 characters)
go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1formatting

Look for formatting issues in the source

line 82 is way too long (91 characters)
go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1formatting

Look for formatting issues in the source

line 85 is way too long (93 characters)
go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1formatting

Look for formatting issues in the source

line 88 is way too long (93 characters)
go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1formatting

Look for formatting issues in the source

line 89 is way too long (101 characters)
go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1formatting

Look for formatting issues in the source

line 95 is way too long (93 characters)
fastboot @ 7.1.2_r36formatting

Look for formatting issues in the source

line 700 is way too long (105 characters)
efitools @ 1.9.2formatting

Look for formatting issues in the source

line 215 is way too long (113 characters)
android-safe-iop @ 7.1.2_r36formatting

Look for formatting issues in the source

line 435 is way too long (95 characters)
android-libutils @ 7.1.2_r36formatting

Look for formatting issues in the source

line 642 is way too long (114 characters)
android-libcutils @ 7.1.2_r36formatting

Look for formatting issues in the source

tabulation on line 277, column 20
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

line 366 is way too long (91 characters)
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

line 385 is way too long (97 characters)
abc @ 0.0-1.5ae4b97formatting

Look for formatting issues in the source

line 95 is way too long (95 characters)
python-openstackdocstheme @ 1.18.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-mox3 @ 0.24.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 297, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 299, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 301, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 303, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 305, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 307, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 309, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 311, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 313, column 18
python2-minimal @ 2.7.17patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-minimal @ 3.8.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-debug @ 3.8.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ijs @ 9.52patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ghostscript-with-x @ 9.52patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ghostscript-with-cups @ 9.52patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mesa @ 20.2.4formatting

Look for formatting issues in the source

line 299 is way too long (120 characters)
mingw-w64-x86_64-winpthreads @ 8.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mingw-w64-x86_64 @ 8.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mingw-w64-i686-winpthreads @ 8.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mingw-w64-i686 @ 8.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

line 672 is way too long (91 characters)
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

line 673 is way too long (99 characters)
nsis-x86_64 @ 3.05patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
nsis-i686 @ 3.05patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
tesseract-ocr @ 4.1.1-1.97079faformatting

Look for formatting issues in the source

line 121 is way too long (93 characters)
sbcl-md5 @ 2.0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
ecl-md5 @ 2.0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
cl-md5 @ 2.0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
mumble @ 1.3.4formatting

Look for formatting issues in the source

tabulation on line 544, column 0
mumble @ 1.3.4formatting

Look for formatting issues in the source

tabulation on line 545, column 0
mumble @ 1.3.4formatting

Look for formatting issues in the source

tabulation on line 546, column 0
rust @ 1.26.2formatting

Look for formatting issues in the source

line 790 is way too long (94 characters)
rust @ 1.25.0formatting

Look for formatting issues in the source

line 751 is way too long (91 characters)
rust @ 1.47.0formatting

Look for formatting issues in the source

line 1403 is way too long (98 characters)
rust @ 1.47.0formatting

Look for formatting issues in the source

line 1409 is way too long (91 characters)
nextcloud-client @ 3.1.3inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
python-libfreenect @ 0.6.2description

Validate package descriptions

description should start with an upper-case letter or digit
libfreenect-opencv @ 0.6.2description

Validate package descriptions

description should start with an upper-case letter or digit
libfreenect-examples @ 0.6.2description

Validate package descriptions

description should start with an upper-case letter or digit
python2-pygobject @ 2.28.7inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-pygobject @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gobject-introspection @ 1.62.0inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
gobject-introspection @ 1.62.0inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
gobject-introspection @ 1.62.0patch-file-names

Validate file names and availability of patches

gobject-introspection-absolute-shlib-path.patch: file name is too long
mate-applets @ 1.24.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 917
python2-pygobject @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gexiv2 @ 0.12.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-pygobject @ 3.34.0formatting

Look for formatting issues in the source

line 853 is way too long (97 characters)
mate-panel @ 1.24.1formatting

Look for formatting issues in the source

line 671 is way too long (92 characters)
mate-menus @ 1.24.1formatting

Look for formatting issues in the source

line 511 is way too long (91 characters)
mate-polkit @ 1.24.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
atril @ 1.22.0formatting

Look for formatting issues in the source

line 748 is way too long (92 characters)
glibc-bootstrap @ 0formatting

Look for formatting issues in the source

line 653 is way too long (100 characters)
gcc-bootstrap @ 0formatting

Look for formatting issues in the source

line 749 is way too long (100 characters)
zbar @ 0.23inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
docker @ 19.03.15formatting

Look for formatting issues in the source

line 355 is way too long (95 characters)
docker @ 19.03.15formatting

Look for formatting issues in the source

line 391 is way too long (93 characters)
chez-srfi @ 1.0formatting

Look for formatting issues in the source

line 289 is way too long (91 characters)
python-bcj-cffi @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-py7zr @ 0.14.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-ppmd-cffi @ 0.3.3inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-multivolumefile @ 0.2.2inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-bcj-cffi @ 0.5.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
itcl @ 4.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-tempest-lib @ 1.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-stevedore @ 3.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-reno @ 2.7.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-oslo.log @ 3.36.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-oslo.config @ 5.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-keystoneclient @ 1.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
mesa-opencl-icd @ 20.2.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mesa-opencl @ 20.2.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perl-test-object @ 0.08description

Validate package descriptions

use @code or similar ornament instead of quotes
maven-shared-utils @ 3.2.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@16 and apache-parent-pom@18 collide
maven-settings-builder @ 3.6.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide
maven-resolver-provider @ 3.6.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-plugin-api @ 3.6.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide
java-sonatype-aether-impl @ 1.7profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-forge-parent-pom@6 and java-sonatype-forge-parent-pom@10 collide
sdl-pango @ 0.1.2patch-headers

Validate patch headers

sdl-pango-header-guard.patch: patch lacks comment and upstream status
nsis-x86_64 @ 3.05patch-headers

Validate patch headers

nsis-env-passthru.patch: patch lacks comment and upstream status
nsis-i686 @ 3.05patch-headers

Validate patch headers

nsis-env-passthru.patch: patch lacks comment and upstream status
mono @ 4.4.1.0patch-headers

Validate patch headers

mono-mdoc-timestamping.patch: patch lacks comment and upstream status
mkbootimg @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
mkbootimg @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
mkbootimg @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
mkbootimg @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
libmhash @ 0.9.9.9patch-headers

Validate patch headers

libmhash-hmac-fix-uaf.patch: patch lacks comment and upstream status
gobject-introspection @ 1.62.0patch-headers

Validate patch headers

gobject-introspection-girepository.patch: patch lacks comment and upstream status
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
cyrus-sasl @ 2.1.27patch-headers

Validate patch headers

cyrus-sasl-ac-try-run-fix.patch: patch lacks comment and upstream status
apr @ 1.6.5patch-headers

Validate patch headers

apr-skip-getservbyname-test.patch: patch lacks comment and upstream status
android-libziparchive @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
android-libziparchive @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
android-libziparchive @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
android-libziparchive @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
android-libutils @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
android-libutils @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
android-libutils @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
android-libutils @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
android-libsparse @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
android-libsparse @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
android-libsparse @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
android-libsparse @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
android-liblog @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
android-liblog @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
android-liblog @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
android-liblog @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
android-libcutils @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
android-libcutils @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
android-libcutils @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
android-libcutils @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
adb @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
adb @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
adb @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
adb @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
wicd @ 1.7.4formatting

Look for formatting issues in the source

line 109 is way too long (95 characters)
netpbm @ 10.78.3formatting

Look for formatting issues in the source

line 86 is way too long (127 characters)
guile @ 2.0.14formatting

Look for formatting issues in the source

line 189 is way too long (94 characters)
guile @ 2.0.14formatting

Look for formatting issues in the source

line 192 is way too long (93 characters)
spice-gtk @ 0.37inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libsigrok @ 0.5.2formatting

Look for formatting issues in the source

line 216 is way too long (101 characters)
libsigrok @ 0.5.2formatting

Look for formatting issues in the source

line 217 is way too long (92 characters)
python-orange-canvas-core @ 0.1.19inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
libextractor @ 1.11formatting

Look for formatting issues in the source

line 128 is way too long (140 characters)
clang-runtime @ 3.5.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
clang-runtime @ 3.5.2patch-file-names

Validate file names and availability of patches

clang-runtime-3.5-libsanitizer-mode-field.patch: file name is too long
fcitx-qt5 @ 1.2.6inputs-should-be-native

Identify inputs that should be native inputs

'intltool' should probably be a native input
openmpi-thread-multiple @ 4.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-openmpi @ 4.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
openmpi @ 4.1.1formatting

Look for formatting issues in the source

line 276 is way too long (94 characters)
openmpi @ 4.1.1formatting

Look for formatting issues in the source

line 278 is way too long (96 characters)
laminar @ 1.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
laminar @ 1.0formatting

Look for formatting issues in the source

line 239 is way too long (97 characters)
laminar @ 1.0formatting

Look for formatting issues in the source

line 241 is way too long (137 characters)
blender @ 2.92.0formatting

Look for formatting issues in the source

line 541 is way too long (97 characters)
dico @ 2.11inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
mrrescue @ 1.02edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 2
busybox @ 1.33.1formatting

Look for formatting issues in the source

line 93 is way too long (92 characters)
meshlab @ 2020.06formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
grantleetheme @ 20.04.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.2-readline @ 2.2.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile-readline @ 3.0.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.2-readline @ 2.2.7formatting

Look for formatting issues in the source

line 432 is way too long (94 characters)
guile-readline @ 3.0.2formatting

Look for formatting issues in the source

line 432 is way too long (94 characters)
python-trezor-agent @ 0.13.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python2-pydot @ 1.4.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mig @ 1.8inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
netdde @ 2.6.32.65-1.4a1016fderivation

Report failure to compile a package to a derivation

failed to create i686-gnu derivation: could not find bootstrap binary 'tar' for system 'i686-gnu'
hurd @ 0.9-1.91a5167derivation

Report failure to compile a package to a derivation

failed to create i686-gnu derivation: could not find bootstrap binary 'tar' for system 'i686-gnu'
gnumach @ 1.8-1.097f9cfderivation

Report failure to compile a package to a derivation

failed to create i686-gnu derivation: could not find bootstrap binary 'tar' for system 'i686-gnu'
python-pytest-click @ 1.0.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
gcompris @ 17.05formatting

Look for formatting issues in the source

line 136 is way too long (96 characters)
axoloti-runtime @ 1.0.12-2formatting

Look for formatting issues in the source

line 197 is way too long (96 characters)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

line 415 is way too long (94 characters)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

line 561 is way too long (93 characters)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

line 574 is way too long (103 characters)
cryptsetup-static @ 2.3.6formatting

Look for formatting issues in the source

line 110 is way too long (93 characters)
python-pep-adapter @ 2.1.3inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
icu4c-build-root @ 66.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
nsis-x86_64 @ 3.05description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
nsis-i686 @ 3.05description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 66 is way too long (115 characters)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 67 is way too long (112 characters)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 81 is way too long (112 characters)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 95 is way too long (92 characters)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 115 is way too long (97 characters)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 119 is way too long (122 characters)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 129 is way too long (114 characters)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 66 is way too long (115 characters)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 67 is way too long (112 characters)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 81 is way too long (112 characters)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 95 is way too long (92 characters)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 115 is way too long (97 characters)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 119 is way too long (122 characters)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 129 is way too long (114 characters)
rust-avif-serialize @ 0.6.5description

Validate package descriptions

use @code or similar ornament instead of quotes
pjproject-jami @ 2.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
espeak-ng @ 1.50description

Validate package descriptions

description should start with an upper-case letter or digit
flite @ 2.2formatting

Look for formatting issues in the source

line 93 is way too long (419 characters)
boost-python2 @ 1.72.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
irods-client-icommands @ 4.2.8formatting

Look for formatting issues in the source

line 238 is way too long (91 characters)
irods @ 4.2.8formatting

Look for formatting issues in the source

line 104 is way too long (93 characters)
irods @ 4.2.8formatting

Look for formatting issues in the source

line 135 is way too long (91 characters)
font-canada1500 @ 1.101formatting

Look for formatting issues in the source

line 187 is way too long (91 characters)
t1lib @ 5.1.2patch-headers

Validate patch headers

t1lib-CVE-2010-2642.patch: patch lacks comment and upstream status
ratpoints @ 2.1.3patch-headers

Validate patch headers

ratpoints-sturm_and_rp_private.patch: patch lacks comment and upstream status
mcrypt @ 2.6.8patch-headers

Validate patch headers

mcrypt-CVE-2012-4426.patch: patch lacks comment and upstream status
enlightenment @ 0.24.2patch-headers

Validate patch headers

enlightenment-fix-setuid-path.patch: patch lacks comment and upstream status
maven-surefire-plugin @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide
maven-surefire-common @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide
maven-shared-utils @ 3.1.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@16 and apache-parent-pom@18 collide
maven-shared-utils @ 3.0.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-shared-io @ 3.0.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@39 collide
maven-shared-incremental @ 1.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-settings-builder @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide
maven-resources-plugin @ 3.1.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide
maven-plugin-api @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide
maven-model-builder @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide
maven-model @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide
maven-jar-plugin @ 3.2.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@39 and apache-commons-parent-pom@41 collide
maven-install-plugin @ 3.0.0-M1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide
maven-filtering @ 3.1.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@39 collide
maven-file-management @ 3.0.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@39 collide
maven-enforcer-rules @ 3.0.0-M3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide
maven-enforcer-plugin @ 3.0.0-M3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@18 collide
maven-enforcer-api @ 3.0.0-M3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-embedder @ 3.6.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide
maven-dependency-tree @ 3.0.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-compiler-plugin @ 3.8.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-compat @ 3.6.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide
maven-compat @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide
maven-common-artifact-filters @ 3.1.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-artifact-transfer @ 0.12.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide
maven-artifact @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide
maven-archiver @ 3.5.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@39 and apache-commons-parent-pom@41 collide
maven-aether-provider @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide
java-surefire-extensions-api @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide
java-surefire-common-junit4 @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide
java-surefire-common-junit3 @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide
java-surefire-common-java5 @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@16 and apache-parent-pom@21 collide
java-surefire-booter @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide
java-surefire-api @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide
maven-settings-builder @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-settings @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-repository-metadata @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-plugin-api @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-model-builder @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-model @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-enforcer-rules @ 3.0.0-M3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-enforcer-plugin @ 3.0.0-M3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-embedder @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-compat @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-compat @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-artifact @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-aether-provider @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-surefire-plugin @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3633 is way too long (113 characters)
maven-surefire-plugin @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3634 is way too long (111 characters)
maven-embedder @ 3.6.1formatting

Look for formatting issues in the source

line 1661 is way too long (110 characters)
java-surefire-booter @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3303 is way too long (107 characters)
icedtea @ 3.7.0formatting

Look for formatting issues in the source

line 1792 is way too long (109 characters)
icedtea @ 2.6.13formatting

Look for formatting issues in the source

line 1279 is way too long (102 characters)
icedtea @ 2.6.13formatting

Look for formatting issues in the source

line 1460 is way too long (100 characters)
python-fpylll @ 0.5.2description

Validate package descriptions

description should start with an upper-case letter or digit
python-fpylll @ 0.5.2inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
python-fpylll @ 0.5.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
connman @ 1.40description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
libstdc++-doc @ 9.4.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libstdc++-doc @ 5.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libiberty @ 7.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libgccjit @ 9.4.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gccgo @ 4.9.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gccgo @ 10.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc++ @ 9.4.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc++ @ 8.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc++ @ 7.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc++ @ 6.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc++ @ 5.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc++ @ 4.9.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc++ @ 4.8.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc++ @ 10.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc @ 9.4.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc @ 8.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc @ 7.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc @ 6.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc @ 5.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc @ 4.9.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc @ 4.8.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc @ 10.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libstdc++-doc @ 9.4.0patch-headers

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
libgccjit @ 9.4.0patch-headers

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
gcc-objc++ @ 9.4.0patch-headers

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
gcc-objc @ 9.4.0patch-headers

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
libreoffice @ 7.1.4.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-faiss @ 1.5.0inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
perl-file-which @ 1.23description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-file-readbackwards @ 1.06description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 47
perl-digest-sha @ 6.02description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 82
perl-devel-globaldestruction @ 0.14description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-class-load @ 0.25description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-glib-object-introspection @ 0.049inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
perl-extutils-pkgconfig @ 1.16inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
cairo-xcb @ 1.16.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
telepathy-glib @ 0.24.1formatting

Look for formatting issues in the source

line 952 is way too long (92 characters)
guile-static-stripped-tarball @ 3.0.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile-static-stripped @ 3.0.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
go-github.com-smartystreets-goconvey @ 1.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 33
python2-sphinxcontrib-programoutput @ 0.15inputs-should-be-native

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
python2-sphinx-rtd-theme @ 0.2.4inputs-should-be-native

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
python2-sphinx-repoze-autointerface @ 0.8inputs-should-be-native

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
python2-sphinx @ 1.7.7inputs-should-be-native

Identify inputs that should be native inputs

'python2-docutils' should probably be a native input
python2-guzzle-sphinx-theme @ 0.7.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
python-sphinxcontrib-svg2pdfconverter @ 1.0.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinxcontrib-programoutput @ 0.15inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinxcontrib-newsfeed @ 0.1.4inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinxcontrib-github-alt @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-sphinxcontrib-github-alt @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-rtd-theme @ 0.2.4inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-repoze-autointerface @ 0.8inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-intl @ 2.0.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-copybutton @ 0.2.6inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-autodoc-typehints @ 1.11.1inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-sphinx-autodoc-typehints @ 1.11.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-argparse @ 0.2.5inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx @ 3.3.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-nbsphinx @ 0.7.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-nbsphinx @ 0.7.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-guzzle-sphinx-theme @ 0.7.11inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-breathe @ 4.30.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-breathe @ 4.30.0inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-copybutton @ 0.2.6inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
go-github.com-smartystreets-goconvey @ 1.6.3formatting

Look for formatting issues in the source

line 668 is way too long (91 characters)
nettle @ 3.5.1patch-file-names

Validate file names and availability of patches

nettle-3.5-check-_pkcs1_sec_decrypt-msg-len.patch: file name is too long
cups-minimal @ 2.3.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-jbzip2 @ 0.9.1formatting

Look for formatting issues in the source

line 280 is way too long (92 characters)
rust-winit @ 0.24.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
rust-winit @ 0.20.0-alpha6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
rust-winit @ 0.19.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 2914 is way too long (114 characters)
texlive-lm @ 51265description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 93
texlive-libkpathsea @ 20190410description

Validate package descriptions

description should start with an upper-case letter or digit
texlive-latex-cyrillic @ 51265description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 166
texlive-hyphen-occitan @ 51265description

Validate package descriptions

use @code or similar ornament instead of quotes
texlive-hyphen-latin @ 51265description

Validate package descriptions

use @code or similar ornament instead of quotes
texlive-fonts-latex @ 51265description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 78
texlive-latex-hyperref @ 6.84a2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
texlive-libkpathsea @ 20190410patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
texlive-ruhyphen @ 51265formatting

Look for formatting issues in the source

line 2553 is way too long (92 characters)
texlive-ruhyphen @ 51265formatting

Look for formatting issues in the source

line 2556 is way too long (93 characters)
texlive-latex-base @ 51265formatting

Look for formatting issues in the source

tabulation on line 2664, column 22
texlive-hyph-utf8 @ 51265formatting

Look for formatting issues in the source

line 2375 is way too long (108 characters)
texlive-hyph-utf8 @ 51265formatting

Look for formatting issues in the source

line 2376 is way too long (108 characters)
texlive-hyph-utf8 @ 51265formatting

Look for formatting issues in the source

line 2377 is way too long (95 characters)
texlive-amsfonts @ 51265formatting

Look for formatting issues in the source

line 1338 is way too long (94 characters)
texlive-amsfonts @ 51265formatting

Look for formatting issues in the source

line 1364 is way too long (93 characters)
texlive-amsfonts @ 51265formatting

Look for formatting issues in the source

line 1366 is way too long (91 characters)
jucipp @ 1.6.3description

Validate package descriptions

description should start with an upper-case letter or digit
openfoam @ 4.1inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
openfoam @ 4.1formatting

Look for formatting issues in the source

line 135 is way too long (109 characters)
openfoam @ 4.1formatting

Look for formatting issues in the source

line 149 is way too long (91 characters)
tmux-themepack @ 1.1.0formatting

Look for formatting issues in the source

line 94 is way too long (95 characters)
tcsh @ 6.22.02patch-headers

Validate patch headers

tcsh-fix-autotest.patch: patch lacks comment and upstream status
xkbprint @ 1.0.5description

Validate package descriptions

use @code or similar ornament instead of quotes
zathura-pdf-poppler @ 0.3.0formatting

Look for formatting issues in the source

line 577 is way too long (107 characters)
zathura-djvu @ 0.2.9formatting

Look for formatting issues in the source

line 491 is way too long (93 characters)
catdoc @ 0.95description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 157
opencc @ 1.1.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
emacs-cmake-mode @ 3.21.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
nginx-accept-language-module @ 0.0.0-1.2f69842formatting

Look for formatting issues in the source

line 624 is way too long (92 characters)
krona-tools @ 2.8formatting

Look for formatting issues in the source

trailing white space on line 1304
pzstd @ 1.4.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
p7zip @ 16.02patch-headers

Validate patch headers

p7zip-remove-unused-code.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-case-insensitive.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-CVE-2018-1000035.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-CVE-2018-18384.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-manpage-fix.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-overflow.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-valgrind.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-x-option.patch: patch lacks comment and upstream status
minizip @ 1.2.11formatting

Look for formatting issues in the source

line 165 is way too long (115 characters)
calibre @ 5.21.0formatting

Look for formatting issues in the source

line 258 is way too long (92 characters)
calibre @ 5.21.0formatting

Look for formatting issues in the source

line 283 is way too long (93 characters)
grub-minimal @ 2.06patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
grub-hybrid @ 2.06patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
grub-efi @ 2.06patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
shogun @ 6.1.3inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
shogun @ 6.1.3formatting

Look for formatting issues in the source

line 526 is way too long (91 characters)
netcdf-parallel-openmpi @ 4.7.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
hdf5-parallel-openmpi @ 1.10.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
hdf4-alt @ 4.2.14patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
dsfmt @ 2.2.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
netcdf-parallel-openmpi @ 4.7.4patch-headers

Validate patch headers

netcdf-date-time.patch: patch lacks comment and upstream status
netcdf @ 4.7.4patch-headers

Validate patch headers

netcdf-date-time.patch: patch lacks comment and upstream status
scalapack @ 2.0.2formatting

Look for formatting issues in the source

tabulation on line 983, column 0
nomad-optimizer @ 4.1.0formatting

Look for formatting issues in the source

line 1918 is way too long (92 characters)
hdf-java @ 3.3.2formatting

Look for formatting issues in the source

line 1393 is way too long (92 characters)
clapack @ 3.2.1formatting

Look for formatting issues in the source

line 945 is way too long (91 characters)
ruby-iruby @ 0.3formatting

Look for formatting issues in the source

line 501 is way too long (112 characters)
omnitux @ 1.2.1formatting

Look for formatting issues in the source

line 620 is way too long (99 characters)
childsplay @ 3.4formatting

Look for formatting issues in the source

line 529 is way too long (92 characters)
emacs-geiser-racket @ 0.16formatting

Look for formatting issues in the source

tabulation on line 400, column 0
template-glib @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
appstream-glib @ 0.7.18formatting

Look for formatting issues in the source

line 1118 is way too long (93 characters)
python-pytools @ 2021.2.7description

Validate package descriptions

use @code or similar ornament instead of quotes
python2-nose2 @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest-cov' should probably be a native input
python-nose2 @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python2-unittest2 @ 1.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-unittest2 @ 1.1.0patch-headers

Validate patch headers

python-unittest2-remove-argparse.patch: patch lacks comment and upstream status
python-unittest2 @ 1.1.0patch-headers

Validate patch headers

python-unittest2-remove-argparse.patch: patch lacks comment and upstream status
kdelibs4support @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
kconfigwidgets @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
plasma-framework @ 5.70.1patch-file-names

Validate file names and availability of patches

plasma-framework-fix-KF5PlasmaMacros.cmake.patch: file name is too long
kpackage @ 5.70.0patch-headers

Validate patch headers

kpackage-allow-external-paths.patch: patch lacks comment and upstream status
plasma-framework @ 5.70.1formatting

Look for formatting issues in the source

line 3431 is way too long (93 characters)
kpackage @ 5.70.0formatting

Look for formatting issues in the source

line 1963 is way too long (106 characters)
kio @ 5.70.1formatting

Look for formatting issues in the source

line 2802 is way too long (113 characters)
kimageformats @ 5.70.0formatting

Look for formatting issues in the source

line 1825 is way too long (103 characters)
kdbusaddons @ 5.70.0formatting

Look for formatting issues in the source

line 655 is way too long (107 characters)
kcmutils @ 5.70.0formatting

Look for formatting issues in the source

line 2274 is way too long (113 characters)
extra-cmake-modules @ 5.70.0formatting

Look for formatting issues in the source

line 120 is way too long (91 characters)
wine64-staging @ 6.6inputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
wine-staging @ 6.6inputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
wine64-staging @ 6.6formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
wine-staging @ 6.6formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python-nbclient @ 0.5.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 62
python-jupyterlab-widgets @ 1.0.0description

Validate package descriptions

description should start with an upper-case letter or digit
tensorflow @ 1.9.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-voila @ 0.2.10inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-nbclient @ 0.5.3inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-pip' should probably not be an input at all
python-nbclient @ 0.5.3inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-jupyterlab-widgets @ 1.0.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-jupyter-packaging @ 0.9.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-cmaes @ 0.8.2inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1758 is way too long (92 characters)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1861 is way too long (91 characters)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1948 is way too long (137 characters)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1949 is way too long (131 characters)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1950 is way too long (137 characters)
python2-fastlmm @ 0.2.21formatting

Look for formatting issues in the source

line 1337 is way too long (92 characters)
electron-cash @ 4.2.5inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
monero @ 0.17.2.3patch-headers

Validate patch headers

monero-use-system-miniupnpc.patch: patch lacks comment and upstream status
perl-crypt-unixcrypt_xs @ 0.11name

Validate package names

name should use hyphens instead of underscores
nsis-x86_64 @ 3.05name

Validate package names

name should use hyphens instead of underscores
mingw-w64-x86_64-winpthreads @ 8.0.0name

Validate package names

name should use hyphens instead of underscores
mingw-w64-x86_64 @ 8.0.0name

Validate package names

name should use hyphens instead of underscores
swi-prolog @ 8.3.20tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
pjproject-jami @ 2.10tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
pjproject @ 2.11tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
lean @ 3.23.0tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
extra-cmake-modules @ 5.70.0tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ecl @ 16.1.3tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
belcard @ 4.4.34tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
texlive-unicode-data @ 51265description

Validate package descriptions

description contains trailing whitespace
python-plotly @ 4.14.3description

Validate package descriptions

description contains trailing whitespace
python-plotly @ 2.4.1description

Validate package descriptions

description contains trailing whitespace
python-myhdl @ 0.11description

Validate package descriptions

description contains trailing whitespace
openmpi-thread-multiple @ 4.1.1description

Validate package descriptions

description contains leading whitespace
leafpad @ 0.8.18.1description

Validate package descriptions

description contains trailing whitespace
js-commander @ 6.2.1description

Validate package descriptions

description contains trailing whitespace
buildapp @ 1.5.6description

Validate package descriptions

description contains trailing whitespace
zeal @ 0.6.1-1.d3c5521wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
xorriso @ 1.5.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
xdot @ 1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wordnet @ 3.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wine64-staging @ 6.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wine64 @ 6.16wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wine-staging @ 6.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wine @ 6.16wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
windowmaker @ 0.95.9wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wgetpaste @ 2.32wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
vis @ 0.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
units @ 2.21wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
translate-shell @ 0.9.6.12wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
synfigstudio @ 1.2.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
syncthing-gtk @ 0.9.4.4-1.c46fbd8wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
spice-gtk @ 0.37wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
shroud @ 0.1.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
scanmem @ 0.17wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
sawfish @ 1.12.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
rust @ 1.20.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ronn-ng @ 0.9.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
roffit @ 0.12-1.b59e6c855wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
rednotebook @ 2.22wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
rapid-photo-downloader @ 0.9.18wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
quilt @ 0.66wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
qtpass @ 1.3.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
protonvpn-cli @ 2.2.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
presentty @ 0.2.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
po4a @ 0.63wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
piet-toolchain @ 0.0.0-0.f002ff6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
perl-image-exiftool @ 12.16wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
perl-eval-withlexicals @ 1.003006wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
pencil2d @ 0.6.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
password-store @ 1.7.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
papagayo @ 2.0b1-1.e143684b3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
orange @ 3.28.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
openconnect-sso @ 0.7.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
npiet @ 1.3fwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
nicotine+ @ 2.1.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
manuskript @ 0.12.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
lxpanel @ 0.10.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
licensecheck @ 3.0.37wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
lcov @ 1.15wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
krona-tools @ 2.8wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
keepassxc @ 2.6.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
kawa @ 3.1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
k3b @ 20.04.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
jucipp @ 1.6.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
itstool @ 2.0.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
guile-wm @ 1.0-1.f3c7b3bwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnucash @ 4.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ghostwriter @ 2.0.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gccgo @ 10.3.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
fontforge @ 20200314wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
flyer-composer @ 1.0rc2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs @ 27.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
electron-cash @ 4.2.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
econnman @ 1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ecl @ 16.1.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cups-filters @ 1.27.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cloc @ 1.90wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
calibre @ 5.21.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
c-reduce @ 2.10.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
byobu @ 5.133wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
browserpass-native @ 3.0.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
assword @ 0.11wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
artanis @ 0.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ark @ 20.04.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
arcanist @ 0.0.0-2.ceb082ewrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
arcan-sdl @ 0.5.5.2-1.b4dd1fbwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
arcan @ 0.5.5.2-1.b4dd1fbwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
akregator @ 20.04.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
zxing-cpp @ 1.0.8optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
uthash @ 2.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
unshield @ 1.4.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
toot @ 0.27.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
syslinux @ 6.04-pre-1.bb41e93optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
solid @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
sloccount @ 2.26optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
rxcpp @ 4.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
rust @ 1.46.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
rust @ 1.26.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
rust @ 1.20.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-rspec-wait @ 0.0.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-debug-inspector @ 0.0.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-awesome-print @ 1.8.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
robin-map @ 0.6.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
rnp @ 0.13.1-0.203224foptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
rgbds @ 0.4.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-unittest2 @ 1.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-scikit-learn @ 0.20.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-iso8601 @ 0.1.13optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-hidapi @ 0.7.99.post21optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-graphviz @ 0.13.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-dateutil @ 2.8.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-cffi @ 1.14.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-autograd @ 0.0.0-0.442205doptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-unittest2 @ 1.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-sphinx @ 3.3.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-scikit-learn @ 0.24.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-podcastparser @ 0.6.6optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-mygpoclient @ 1.8optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-meshio @ 4.4.6optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-libtmux @ 0.10.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-leather @ 0.3.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-iso8601 @ 0.1.13optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-hidapi @ 0.7.99.post21optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-graphviz @ 0.13.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-fenics-ufl @ 2019.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-fenics-fiat @ 2019.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-fenics-ffc @ 2019.1.0.post0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-fenics-dijitso @ 2019.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-dateutil @ 2.8.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-daemux @ 0.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-cffi @ 1.14.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-autograd @ 0.0.0-0.442205doptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-agate-excel @ 0.2.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-agate-dbf @ 0.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-agate @ 1.6.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
perl6-zef @ 0.6.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
perl6-tap-harness @ 0.0.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
pcc @ 20170109optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
pass-git-helper @ 1.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
p7zip @ 16.02optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
onionshare-cli @ 2.3.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
onionshare @ 2.3.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
nss @ 3.59optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
node-far @ 0.0.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ninja @ 1.10.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
networkmanager-qt @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
monero @ 0.17.2.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
modemmanager-qt @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
lightgbm @ 2.0.12optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libksysguard @ 5.19.5optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ldc @ 1.10.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
kwindowsystem @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
krunner @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
knotifications @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
kdbusaddons @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
kconfig @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
kauth @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
java-iq80-snappy @ 0.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
icedtea @ 2.6.13optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
gnurl @ 7.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
fullswof-2d @ 1.09.01optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
fifo-map @ 1.1.1-0.0dfbf5doptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
fenics-dolfin @ 2019.1.0.post0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
fenics @ 2019.1.0.post0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
fann @ 2.2.0-1.d71d5478optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
faiss @ 1.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
emacs-ledger-mode @ 4.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
docker @ 19.03.15optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
dlib @ 19.20optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
dico @ 2.11optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
curl @ 7.77.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
curl @ 7.74.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
clitest @ 0.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
cedille @ 1.1.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
c-reduce @ 2.10.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
busybox @ 1.33.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bcunit @ 3.0.2-0.74021ccoptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bctoolbox @ 4.4.34optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bcg729 @ 1.1.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
baloo @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
attr @ 2.4.48optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
armips @ 0.11.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
anthy @ 9100hoptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
amalgamate @ 1.1.1-0.c91f07eoptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
serf @ 1.3.9formatting

Look for formatting issues in the source

line 2010 is way too long (92 characters)
qtwebglplugin @ 5.15.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 41
qtdatavis3d @ 5.15.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 107, 250
qtcharts @ 5.15.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 244
qwt @ 6.1.5inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
python-pyqt-without-qtwebkit @ 5.15.2inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
python-pyqt @ 5.15.2inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
python-pyqt-without-qtwebkit @ 5.15.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-pyqt @ 5.15.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
qtserialport @ 5.15.2formatting

Look for formatting issues in the source

line 1101 is way too long (115 characters)
qtsensors @ 5.15.2formatting

Look for formatting issues in the source

line 964 is way too long (97 characters)
qtremoteobjects @ 5.15.2formatting

Look for formatting issues in the source

line 1525 is way too long (94 characters)
qtmultimedia @ 5.15.2formatting

Look for formatting issues in the source

line 1004 is way too long (96 characters)
qtbase @ 5.15.2formatting

Look for formatting issues in the source

line 444 is way too long (96 characters)
qtbase @ 5.15.2formatting

Look for formatting issues in the source

line 522 is way too long (97 characters)
qtbase @ 5.15.2formatting

Look for formatting issues in the source

line 527 is way too long (94 characters)
qtbase @ 5.15.2formatting

Look for formatting issues in the source

line 529 is way too long (94 characters)
python-pyqt @ 5.15.2formatting

Look for formatting issues in the source

line 2151 is way too long (105 characters)
verilator @ 4.204description

Validate package descriptions

use @code or similar ornament instead of quotes
meld @ 3.20.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
mkfontdir @ 1.0.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
xorg-server-xwayland @ 1.20.11patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libxt @ 1.2.0patch-headers

Validate patch headers

libxt-guix-search-paths.patch: patch lacks comment and upstream status
xproto @ 7.0.31formatting

Look for formatting issues in the source

line 5009 is way too long (91 characters)
xdg-user-dirs @ 0.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
python-cchardet @ 2.1.7description

Validate package descriptions

description should start with an upper-case letter or digit
telepathy-mission-control @ 5.16.5inputs-should-be-native

Identify inputs that should be native inputs

'gtk-doc' should probably be a native input
xdg-utils @ 1.1.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
udisks @ 2.8.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
perl-file-mimeinfo @ 0.29wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python2-pyxdg @ 0.27optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pyxdg @ 0.27optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
malcontent @ 0.8.0formatting

Look for formatting issues in the source

line 357 is way too long (91 characters)
localed @ 241formatting

Look for formatting issues in the source

line 820 is way too long (96 characters)
r-bsgenome-dmelanogaster-ucsc-dm3-masked @ 1.3.99formatting

Look for formatting issues in the source

line 276 is way too long (95 characters)
help2man @ 1.47.13formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
rocm-bandwidth-test @ 4.3.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 122
clang-runtime @ 3.9.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
clang-runtime @ 3.9.1patch-file-names

Validate file names and availability of patches

clang-runtime-3.9-libsanitizer-mode-field.patch: file name is too long
clang-runtime @ 3.8.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
clang-runtime @ 3.8.1patch-file-names

Validate file names and availability of patches

clang-runtime-3.8-libsanitizer-mode-field.patch: file name is too long
clang-runtime @ 3.7.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
clang-runtime @ 3.7.1patch-file-names

Validate file names and availability of patches

clang-runtime-3.8-libsanitizer-mode-field.patch: file name is too long
clang @ 9.0.1formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 8.0.0formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 7.1.0formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 6.0.1formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 3.9.1formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 3.8.1formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 3.7.1formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 3.5.2formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 11.0.0formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 10.0.0formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
python-pytest-django @ 4.4.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-django-taggit @ 1.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-simple-math-captcha @ 1.0.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-filter @ 2.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-debug-toolbar @ 3.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-allauth @ 0.42.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
perl-libxml @ 0.08description

Validate package descriptions

description should start with an upper-case letter or digit
java-xpp3 @ 1.1.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 188
java-mxparser @ 1.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 188, 473
java-kxml2 @ 2.4.2description

Validate package descriptions

description should start with an upper-case letter or digit
xlsx2csv @ 0.7.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
tinyxml @ 2.6.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-lxml @ 4.4.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-lxml @ 4.4.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-libxml2 @ 2.9.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

line 2376 is way too long (91 characters)
java-xom @ 127formatting

Look for formatting issues in the source

trailing white space on line 1927
java-xmlpull-api-v1 @ 1.1.3.4bformatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
kontactinterface @ 20.04.1description

Validate package descriptions

description contains leading whitespace
kldap @ 20.04.1description

Validate package descriptions

description contains leading whitespace
kldap @ 20.04.1description

Validate package descriptions

description contains trailing whitespace
tryton @ 6.0.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cozy @ 1.1.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python-agate-sql @ 0.5.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
xfce4-clipman-plugin @ 1.6.2formatting

Look for formatting issues in the source

line 504 is way too long (91 characters)
tumbler @ 4.16.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
patchwork @ 3.0.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ghc @ 8.6.5formatting

Look for formatting issues in the source

line 593 is way too long (91 characters)
rtl-sdr @ 0.6.0description

Validate package descriptions

use @code or similar ornament instead of quotes
libmediaart @ 1.9.5inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-pymol @ 2.5.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
sushi @ 3.32.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
patchutils @ 0.4.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnuradio @ 3.9.2.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnome-photos @ 3.34.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnome-music @ 3.34.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
tng @ 1.8.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
quickjs @ 2021-03-27optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
emacs-erlang @ 24.0.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
zeitgeist @ 1.0.3formatting

Look for formatting issues in the source

tabulation on line 757, column 18
zeitgeist @ 1.0.3formatting

Look for formatting issues in the source

tabulation on line 760, column 18
js-filesaver @ 1.3.8formatting

Look for formatting issues in the source

line 533 is way too long (99 characters)
gnome-initial-setup @ 3.32.1formatting

Look for formatting issues in the source

line 1474 is way too long (91 characters)
clang @ 12.0.1formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
perftest @ 4.4-0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
python2 @ 2.7.17patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-next @ 3.9.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mesa-headers @ 20.2.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-minimal @ 3.8.2patch-headers

Validate patch headers

python-3.8-fix-tests.patch: patch lacks comment and upstream status
python-debug @ 3.8.2patch-headers

Validate patch headers

python-3.8-fix-tests.patch: patch lacks comment and upstream status
python @ 3.8.2patch-headers

Validate patch headers

python-3.8-fix-tests.patch: patch lacks comment and upstream status
python2 @ 2.7.17formatting

Look for formatting issues in the source

line 181 is way too long (99 characters)
python2 @ 2.7.17formatting

Look for formatting issues in the source

line 290 is way too long (98 characters)
python @ 3.8.2formatting

Look for formatting issues in the source

line 481 is way too long (93 characters)
perftest @ 4.4-0.4formatting

Look for formatting issues in the source

line 6092 is way too long (98 characters)
python-hmmlearn @ 0.2.6inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
python-hmmlearn @ 0.2.6inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-keras @ 2.2.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-xgboost @ 1.4.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
thunar @ 4.16.10inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
entangle @ 3.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
darktable @ 3.6.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
detox @ 1.4.5optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python2-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python-pytest-random-order @ 1.0.4inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-mock @ 3.6.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-lazy-fixture @ 0.6.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-assume @ 2.4.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-coveralls @ 3.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python2-pytest-cov @ 2.8.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-ordering @ 0.6optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-lazy-fixture @ 0.6.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-httpserver @ 1.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-cov @ 2.8.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-junit-xml @ 1.9-0.4bd08a2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
texlive-latex-l3packages @ 51265formatting

Look for formatting issues in the source

line 3214 is way too long (91 characters)
texlive-latex-l3packages @ 51265formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python2-pytest-subtesthack @ 0.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 106
python-pytest-subtesthack @ 0.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 106
python2-pytest-xdist @ 1.34.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-subtesthack @ 0.1.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-mock @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-mock' should probably be a native input
python2-pytest-mock @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-cache @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-cov-core @ 1.15.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python-testtools @ 2.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-testscenarios @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-testresources @ 2.0.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-pytest-xprocess @ 0.18.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-xdist @ 2.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-xdist @ 1.34.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-timeout @ 1.4.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-timeout @ 1.4.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python-pytest-sugar @ 0.9.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-subtesthack @ 0.1.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-cache @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-fixtures @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-cov-core @ 1.15.0inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-codecov @ 2.0.15inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-testtools @ 2.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-testscenarios-bootstrap @ 0.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-testscenarios @ 0.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-timeout @ 1.4.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-localserver @ 0.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-fixtures @ 3.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-testtools-bootstrap @ 2.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
r-esc @ 0.5.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 178
r-dplyr @ 1.0.7description

Validate package descriptions

description should start with an upper-case letter or digit
r-datasaurus @ 0.1.4description

Validate package descriptions

use @code or similar ornament instead of quotes
r-boot @ 1.3-28description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 125, 142
python2-cryptography @ 3.3.1description

Validate package descriptions

description should start with an upper-case letter or digit
python2-asn1crypto @ 1.4.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-rpy2 @ 3.4.5description

Validate package descriptions

description should start with an upper-case letter or digit
python-cryptography @ 3.3.1description

Validate package descriptions

description should start with an upper-case letter or digit
python-asn1crypto @ 1.4.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-keyring @ 22.0.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python2-patsy @ 0.5.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-ecdsa @ 0.14.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-asn1crypto @ 1.4.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-trustme @ 0.6.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-rpy2 @ 3.4.5optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pynacl @ 1.4.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-privy @ 6.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-patsy @ 0.5.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-ecdsa @ 0.14.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-blurhash @ 1.1.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-asn1crypto @ 1.4.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-argon2-cffi @ 20.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
emacs-ess @ 18.10.2-0.24da603optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-pycrypto @ 2.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
r-esc @ 0.5.1formatting

Look for formatting issues in the source

line 6471 is way too long (94 characters)
guile-f-scm @ 0.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-dsv @ 0.4.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
guile-dsv @ 0.4.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
guile2.2-fibers @ 1.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
hackrf @ 2021.03.1description

Validate package descriptions

use @code or similar ornament instead of quotes
gnuradio @ 3.9.2.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
at-spi2-atk @ 2.34.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
gtk+ @ 3.24.24patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gtk+ @ 2.24.32patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gdk-pixbuf+svg @ 2.40.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

tabulation on line 844, column 0
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

tabulation on line 845, column 0
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

tabulation on line 846, column 0
at-spi2-core @ 2.34.0formatting

Look for formatting issues in the source

line 690 is way too long (97 characters)
guile-sdl @ 0.5.2formatting

Look for formatting issues in the source

line 613 is way too long (111 characters)
xpra @ 4.2.2formatting

Look for formatting issues in the source

tabulation on line 6379, column 0
gramps @ 5.1.4inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gramps @ 5.1.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
lepton-eda @ 1.9.14-20210407inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
geda-gaf @ 1.10.0inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
pcb @ 4.0.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python-uqbar @ 0.5.6inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python2-stdnum @ 1.14description

Validate package descriptions

description contains trailing whitespace
python-stdnum @ 1.14description

Validate package descriptions

description contains trailing whitespace
python2-stdnum @ 1.14optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-stdnum @ 1.14optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
flowee @ 2020.04.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bitcoin-unlimited @ 1.9.2.0formatting

Look for formatting issues in the source

line 1495 is way too long (91 characters)
virt-viewer @ 7.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
liferea @ 1.13.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gpsd @ 3.23.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
giara @ 0.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gfeeds @ 0.16.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cawbird @ 1.4.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python-androguard @ 3.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
git-repo @ 2.4.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
fdroidserver @ 1.1.9formatting

Look for formatting issues in the source

line 939 is way too long (106 characters)
cawbird @ 1.4.2formatting

Look for formatting issues in the source

line 86 is way too long (104 characters)
openssh-sans-x @ 8.8p1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
lxqt @ 17.0inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
lxqt-session @ 0.17.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
lxqt-session @ 0.17.1formatting

Look for formatting issues in the source

line 871 is way too long (92 characters)
lxqt-session @ 0.17.1formatting

Look for formatting issues in the source

line 878 is way too long (100 characters)
lxqt-session @ 0.17.1formatting

Look for formatting issues in the source

line 896 is way too long (98 characters)
catfish @ 4.16.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
xfce4-volumed-pulse @ 0.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
xfce4-screensaver @ 4.16.0description

Validate package descriptions

description contains trailing whitespace
mousepad @ 0.5.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
config @ 0.0.0-1.c8ddc84description

Validate package descriptions

use @code or similar ornament instead of quotes
libtool @ 2.4.6inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 631 is way too long (92 characters)
adcli @ 0.9.1formatting

Look for formatting issues in the source

line 87 is way too long (95 characters)
tuxmath @ 2.0.3description

Validate package descriptions

description should start with an upper-case letter or digit
anki @ 2.1.16wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ceph @ 14.2.16wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ruby-progress_bar @ 1.1.0name

Validate package names

name should use hyphens instead of underscores
ruby-data_uri @ 0.1.0name

Validate package names

name should use hyphens instead of underscores
ruby-yard-with-tests @ 0.9.25tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ruby-ffi-rzmq @ 2.0.7tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ruby-byebug @ 11.1.3tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ruby-rb-inotify @ 0.9.10description

Validate package descriptions

description should start with an upper-case letter or digit
ruby-ox @ 2.6.0description

Validate package descriptions

description contains trailing whitespace
ghc-th-reify-many @ 0.1.10description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-tasty-expected-failure @ 0.12.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 185
ghc-doctest-lib @ 0.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 35
ghc-crypto-cipher-tests @ 0.0.11description

Validate package descriptions

description contains leading whitespace
raincat @ 1.2.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ruby-yard-tomdoc @ 0.7.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-thor @ 1.0.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-spectroscope @ 0.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-rack-test @ 0.8.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-permutation @ 0.1.8optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-netrc @ 0.11.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-minitest-pretty-diff @ 0.1-1.11f32e93optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-hydra @ 0.0-0.5abfa37optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-ffi-rzmq-core @ 1.0.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-ffi-rzmq @ 2.0.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-cucumber-messages @ 12.2.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-cucumber-html-formatter @ 7.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-cucumber-create-meta @ 1.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-blankslate @ 3.1.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-activesupport @ 6.1.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-tzinfo-data @ 1.2021.1formatting

Look for formatting issues in the source

line 5862 is way too long (101 characters)
ruby-tzinfo-data @ 1.2021.1formatting

Look for formatting issues in the source

line 5863 is way too long (107 characters)
ruby-asciidoctor-pdf @ 1.5.3-1.d257440formatting

Look for formatting issues in the source

line 1888 is way too long (99 characters)
idris @ 1.3.3formatting

Look for formatting issues in the source

line 105 is way too long (100 characters)
ghc-th-orphans @ 0.13.12formatting

Look for formatting issues in the source

line 13466 is way too long (92 characters)
ghc-optparse-applicative @ 0.15.1.0formatting

Look for formatting issues in the source

line 178 is way too long (95 characters)
ghc-doctest-exitcode-stdio @ 0.0formatting

Look for formatting issues in the source

line 1168 is way too long (99 characters)
elm-compiler @ 0.19.0formatting

Look for formatting issues in the source

line 58 is way too long (97 characters)
ppsspp @ 1.11.3-1.69fa207description

Validate package descriptions

use @code or similar ornament instead of quotes
pcsxr @ 1.9.95wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ppsspp @ 1.11.3-1.69fa207optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
cc65 @ 2.19formatting

Look for formatting issues in the source

line 2546 is way too long (167 characters)
ghc @ 8.10.7formatting

Look for formatting issues in the source

line 719 is way too long (93 characters)
ghc-template-haskell @ 2.16.0.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 111
ghc-genvalidity-hspec @ 0.7.0.4description

Validate package descriptions

description contains trailing whitespace
ghc-template-haskell-compat-v0208 @ 0.1.6formatting

Look for formatting issues in the source

line 16143 is way too long (111 characters)
ghc-indexed-traversable @ 0.1.1formatting

Look for formatting issues in the source

line 15483 is way too long (91 characters)
geany @ 1.38formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
newsboat @ 2.25optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libmypaint @ 1.6.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

line 526 is way too long (107 characters)
owncloud-client @ 2.9.0.5150patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libdqlite @ 1.9.0description

Validate package descriptions

description should start with an upper-case letter or digit
krita @ 4.4.8wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
kdenlive @ 21.08.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
kuserfeedback @ 1.0.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ganeti @ 3.0.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
quazip @ 1.1description

Validate package descriptions

description contains trailing whitespace
quazip @ 0.9.1description

Validate package descriptions

description contains trailing whitespace
brotli @ 1.0.9formatting

Look for formatting issues in the source

line 2189 is way too long (94 characters)
python-git-review @ 2.1.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
libicns @ 0.8.1tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
openjpeg-data @ 2020.05.19description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
libjxr @ 1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
libcyaml @ 1.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bind @ 9.16.16optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libjxr @ 1.1formatting

Look for formatting issues in the source

line 525 is way too long (95 characters)
cloudflare-cli @ 0.0.0-1.2d986d3formatting

Look for formatting issues in the source

line 122 is way too long (92 characters)
cscope @ 15.9description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
libvirt-glib @ 4.0.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
virt-manager @ 3.2.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
virt-manager @ 3.2.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libosinfo @ 1.7.1formatting

Look for formatting issues in the source

line 1046 is way too long (106 characters)
go @ 1.16.8tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
go-github-com-xanzy-ssh-agent @ 0.2.1description

Validate package descriptions

description contains trailing whitespace
go-github-com-songmu-gitconfig @ 0.1.0description

Validate package descriptions

description should start with an upper-case letter or digit
go-github-com-muesli-termenv @ 0.7.0description

Validate package descriptions

description should start with an upper-case letter or digit
go-github-com-mitchellh-reflectwalk @ 1.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
go-github-com-mattn-go-zglob @ 0.0.3description

Validate package descriptions

description contains leading whitespace
go-github-com-mattn-go-zglob @ 0.0.3description

Validate package descriptions

description contains trailing whitespace
go-github-com-wtolson-go-taglib @ 0.0.0-0.6e68349inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
go-github-com-mesilliac-pulse-simple @ 0.0.0-0.75ac54einputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
ranger @ 1.9.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ranger @ 1.9.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-gitlab-com-ambrevar-golua-unicode @ 0.0.0-0.97ce517optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-wtolson-go-taglib @ 0.0.0-0.6e68349optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-operatorfoundation-shapeshifter-ipc @ 2.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-operatorfoundation-obfs4 @ 1.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-blanu-dust @ 1.0.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-apparentlymart-go-openvpn-mgmt @ 0.0.0-0.4d2ce95optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-gopkg-in-djherbis-times-v1 @ 1.5.0formatting

Look for formatting issues in the source

line 8840 is way too long (91 characters)
go-github-com-rogpeppe-go-internal @ 1.6.1formatting

Look for formatting issues in the source

line 7884 is way too long (101 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 862 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 863 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 864 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 865 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 866 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 867 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 868 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 869 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 874 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 875 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 884 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 885 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 887 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 888 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 889 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 890 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 891 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 892 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 894 is way too long (97 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 895 is way too long (97 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 897 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 899 is way too long (92 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 900 is way too long (92 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 901 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 902 is way too long (97 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 912 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 913 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 914 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 915 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 916 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 917 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 918 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 919 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 924 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 925 is way too long (98 characters)
go-github-com-multiformats-go-multiaddr-net @ 1.6.3-0.1cb9a0eformatting

Look for formatting issues in the source

line 4993 is way too long (93 characters)
go-github-com-multiformats-go-multiaddr-net @ 1.6.3-0.1cb9a0eformatting

Look for formatting issues in the source

line 4994 is way too long (93 characters)
go-github-com-multiformats-go-multiaddr @ 1.3.0-0.fe1c46fformatting

Look for formatting issues in the source

line 4950 is way too long (93 characters)
go-github-com-mitchellh-go-homedir @ 1.0.0-0.ae18d6bformatting

Look for formatting issues in the source

line 4837 is way too long (95 characters)
go-github-com-mattn-go-shellwords @ 1.0.5-1.2444a32formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
go-github-com-libp2p-go-libp2p-peer @ 2.3.8-0.993d742formatting

Look for formatting issues in the source

line 4742 is way too long (93 characters)
go-github-com-libp2p-go-libp2p-metrics @ 2.1.6-0.a10ff6eformatting

Look for formatting issues in the source

line 4798 is way too long (93 characters)
go-github-com-libp2p-go-libp2p-metrics @ 2.1.6-0.a10ff6eformatting

Look for formatting issues in the source

line 4801 is way too long (93 characters)
go-github-com-gorilla-context @ 0.0.0-0.08b5f42formatting

Look for formatting issues in the source

line 3168 is way too long (164 characters)
go-github-com-davecgh-go-spew @ 1.1.1formatting

Look for formatting issues in the source

line 4405 is way too long (129 characters)
dmraid @ 1.0.0.rc16-3formatting

Look for formatting issues in the source

line 887 is way too long (91 characters)
elixir @ 1.12.3formatting

Look for formatting issues in the source

line 76 is way too long (97 characters)
elixir @ 1.12.3formatting

Look for formatting issues in the source

line 77 is way too long (99 characters)
ecl @ 21.2.1tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
gcl @ 2.6.12-2.d3335e2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ecl @ 21.2.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
minetest-basic-trains @ 1.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
crawl-tiles @ 0.27.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
crawl @ 0.27.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
crawl-tiles @ 0.27.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
tao @ 1.0-beta-10May2006inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
tao @ 1.0-beta-10May2006inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
audio-to-midi @ 2020.7inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
strawberry @ 0.9.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
jack2 @ 1.9.14wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
clementine @ 1.4.0rc1-450-g2725ef99dwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
libexpected @ 1.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
denemo @ 2.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
infamous-plugins @ 0.3.0formatting

Look for formatting issues in the source

line 1092 is way too long (104 characters)
gtklick @ 0.6.4formatting

Look for formatting issues in the source

line 1304 is way too long (94 characters)
faad2 @ 2.8.8formatting

Look for formatting issues in the source

line 1824 is way too long (95 characters)
audacity @ 2.4.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
system-config-printer @ 1.5.15inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libpeas @ 1.28.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gnome-contacts @ 3.34inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
system-config-printer @ 1.5.15wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
icon-naming-utils @ 0.8.90wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gtg @ 0.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnome-characters @ 3.30.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
drawing @ 0.8.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
librsvg @ 2.50.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
librsvg @ 2.50.3formatting

Look for formatting issues in the source

line 3504 is way too long (104 characters)
gnome-keyring @ 3.34.0formatting

Look for formatting issues in the source

line 2541 is way too long (91 characters)
glade @ 3.36.0formatting

Look for formatting issues in the source

line 3204 is way too long (91 characters)
dejagnu @ 1.6.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
dejagnu @ 1.6.2formatting

Look for formatting issues in the source

line 60 is way too long (91 characters)
python2-flexmock @ 0.10.4description

Validate package descriptions

description should start with an upper-case letter or digit
python-flexmock @ 0.10.4description

Validate package descriptions

description should start with an upper-case letter or digit
keyutils @ 1.6.1description

Validate package descriptions

description contains trailing whitespace
python2-pytest-warnings @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-catchlog @ 1.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-capturelog @ 0.7inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python2-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-nose' should probably be a native input
python2-nose-timer @ 0.7.5inputs-should-be-native

Identify inputs that should be native inputs

'python2-nose' should probably be a native input
python2-coverage-test-runner @ 1.15inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python-pytest-warnings @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-dependency @ 0.5.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-datadir @ 1.3.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-catchlog @ 1.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-capturelog @ 0.7inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-nose-timer @ 0.7.5inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-coverage-test-runner @ 1.15inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
tomb @ 2.9wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python2-lit @ 0.5.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-freezegun @ 0.3.14optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-coverage-test-runner @ 1.15optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pyhamcrest @ 2.0.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-lit @ 0.5.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-freezegun @ 0.3.14optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-coverage-test-runner @ 1.15optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
giac @ 1.7.0-39formatting

Look for formatting issues in the source

line 353 is way too long (95 characters)
docbook2x @ 0.8.8inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
dblatex @ 0.3.12wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
bindfs @ 1.15.1description

Validate package descriptions

description contains trailing whitespace
dvdstyler @ 3.0.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cdemu-client @ 3.2.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ausweisapp2 @ 1.22.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
asunder @ 2.9.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
abcde @ 2.9.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
criu @ 3.16.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
xen @ 4.14.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python-pytest-csv @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
ublock-origin-chromium @ 1.38.6description

Validate package descriptions

description should start with an upper-case letter or digit
mia @ 2.4.6inputs-should-be-native

Identify inputs that should be native inputs

'doxygen' should probably be a native input
itk-snap @ 3.8.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
vtk @ 9.0.1formatting

Look for formatting issues in the source

line 301 is way too long (93 characters)
vtk @ 9.0.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
opencv @ 3.4.3formatting

Look for formatting issues in the source

line 515 is way too long (132 characters)
fntsample @ 5.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
bcachefs-tools @ 0.1-12.f9f5778wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
lodepng @ 20200215-1.48e5364optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libavif @ 0.9.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
steghide @ 0.5.1patch-headers

Validate patch headers

steghide-fixes.patch: patch lacks comment and upstream status
php @ 7.4.25formatting

Look for formatting issues in the source

line 191 is way too long (93 characters)
php @ 7.4.25formatting

Look for formatting issues in the source

line 192 is way too long (93 characters)
php @ 7.4.25formatting

Look for formatting issues in the source

line 203 is way too long (91 characters)
php @ 7.4.25formatting

Look for formatting issues in the source

line 211 is way too long (93 characters)
php @ 7.4.25formatting

Look for formatting issues in the source

line 233 is way too long (92 characters)
php @ 7.4.25formatting

Look for formatting issues in the source

line 234 is way too long (96 characters)
php @ 7.4.25formatting

Look for formatting issues in the source

line 239 is way too long (96 characters)
php @ 7.4.25formatting

Look for formatting issues in the source

line 281 is way too long (91 characters)
php @ 7.4.25formatting

Look for formatting issues in the source

line 294 is way too long (92 characters)
jfs_fsck-static @ 1.1.15name

Validate package names

name should use hyphens instead of underscores
mergerfs @ 2.32.6formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libnfs @ 4.0.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
glusterfs @ 7.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
autotrace @ 0.40.0-20190624.59optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
execline @ 2.8.1.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
blanket @ 0.4.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-wide-int @ 27.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-next-pgtk @ 28.0.50-1.ae18c8ewrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-next @ 28.0.50-0.2ea3466wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-xwidgets @ 27.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-wide-int @ 27.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-no-x-toolkit @ 27.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-no-x @ 27.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-next @ 28.0.50-0.2ea3466patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-minimal @ 27.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
qutebrowser @ 2.3.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
luakit @ 2.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
kristall @ 0.3-1.204b08awrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
parallel @ 20211022wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
lpsolve @ 5.5.2.5description

Validate package descriptions

description should start with an upper-case letter or digit
opencascade-occt @ 7.3.0p3inputs-should-be-native

Identify inputs that should be native inputs

'doxygen' should probably be a native input
octave-cli @ 6.2.0inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
octave @ 6.2.0inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
wxmaxima @ 21.05.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
veusz @ 3.3.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
maxima @ 5.45.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
z3 @ 4.8.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
pt-scotch32 @ 6.1.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
pt-scotch @ 6.1.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mumps-openmpi @ 5.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mumps-metis-openmpi @ 5.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mumps-metis @ 5.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mumps @ 5.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
maxima @ 5.45.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
hypre @ 2.15.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
scotch32 @ 6.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
scotch-shared @ 6.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
pt-scotch32 @ 6.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
pt-scotch-shared @ 6.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
pt-scotch @ 6.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mumps-openmpi @ 5.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mumps-metis-openmpi @ 5.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mumps-metis @ 5.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
scotch32 @ 6.1.1patch-headers

Validate patch headers

scotch-integer-declarations.patch: patch lacks comment and upstream status
scotch-shared @ 6.1.1patch-headers

Validate patch headers

scotch-integer-declarations.patch: patch lacks comment and upstream status
scotch @ 6.1.1patch-headers

Validate patch headers

scotch-integer-declarations.patch: patch lacks comment and upstream status
pt-scotch32 @ 6.1.1patch-headers

Validate patch headers

scotch-integer-declarations.patch: patch lacks comment and upstream status
pt-scotch-shared @ 6.1.1patch-headers

Validate patch headers

scotch-integer-declarations.patch: patch lacks comment and upstream status
pt-scotch @ 6.1.1patch-headers

Validate patch headers

scotch-integer-declarations.patch: patch lacks comment and upstream status
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

line 3705 is way too long (92 characters)
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

tabulation on line 3725, column 0
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

tabulation on line 3726, column 0
slepc-openmpi @ 3.11.1formatting

Look for formatting issues in the source

tabulation on line 3169, column 0
slepc-complex-openmpi @ 3.11.1formatting

Look for formatting issues in the source

line 3185 is way too long (92 characters)
pt-scotch32 @ 6.1.1formatting

Look for formatting issues in the source

tabulation on line 3986, column 0
pt-scotch @ 6.1.1formatting

Look for formatting issues in the source

tabulation on line 3964, column 0
petsc @ 3.11.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
p4est @ 2.0formatting

Look for formatting issues in the source

tabulation on line 4075, column 0
mumps-openmpi @ 5.2.1formatting

Look for formatting issues in the source

tabulation on line 3544, column 0
mumps @ 5.2.1formatting

Look for formatting issues in the source

line 3458 is way too long (94 characters)
hypre-openmpi @ 2.15.1formatting

Look for formatting issues in the source

tabulation on line 5529, column 0
u-boot-tools @ 2021.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-nintendo-nes-classic-edition @ 2018.11patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-tools @ 2021.10formatting

Look for formatting issues in the source

line 594 is way too long (108 characters)
u-boot-tools @ 2021.10formatting

Look for formatting issues in the source

line 598 is way too long (97 characters)
trytond-timesheet @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-stock-split @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-stock-package @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-stock-lot-unit @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-stock-location-move @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-sale-promotion @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-sale-extra @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-production-work-timesheet @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-production-work @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-production-split @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-production-outsourcing @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-party-relationship @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-notification-email @ 6.0.1description

Validate package descriptions

description contains typo 'allows to'
trytond-ldap-authentication @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-customs @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-commission-waiting @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-commission @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-analytic-sale @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-analytic-purchase @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-analytic-invoice @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-tax-cash @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-stock-landed-cost @ 6.0.1description

Validate package descriptions

description contains typo 'allows to'
trytond-account-statement @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-payment-sepa @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-payment-clearing @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-invoice-line-standalone @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-invoice-defer @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-es @ 6.0.2description

Validate package descriptions

description contains typo 'allows to'
trytond-account-deposit @ 6.0.1description

Validate package descriptions

description contains typo 'allows to'
udiskie @ 2.3.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
udiskie @ 2.3.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
guile2.2-gnutls @ 3.6.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.0-gnutls @ 3.6.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gnutls-dane @ 3.6.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.2-gnutls @ 3.6.16patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.0-gnutls @ 3.6.16patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gnutls-dane @ 3.6.16patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
plymouth @ 0.9.5formatting

Look for formatting issues in the source

line 2099 is way too long (91 characters)
libportal @ 0.4formatting

Look for formatting issues in the source

line 2265 is way too long (93 characters)
openexr @ 2.5.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ruby_version @ 1.0.2name

Validate package names

name should use hyphens instead of underscores
ruby-yell @ 2.2.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-turn @ 0.9.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-shoulda-matchers @ 3.1.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-shoulda-matchers @ 2.8.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-shoulda-context @ 1.2.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-shoulda @ 3.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-rubytest @ 0.8.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-rc4 @ 0.1.5optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-qed @ 2.9.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-pdf-inspector @ 1.3.0-1.00ee4c9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-lemon @ 0.9.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-htmlentities @ 4.3.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-hashery @ 2.1.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-brass @ 1.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-bio-commandeer @ 0.4.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-ansi @ 1.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-ae @ 1.8.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
tor @ 0.4.6.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 574
ocrodjvu @ 0.12wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
didjvu @ 0.9wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
kicad @ 5.1.10wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
sundials-openmpi @ 3.1.1formatting

Look for formatting issues in the source

tabulation on line 6159, column 0
lightdm @ 1.30.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
memtester @ 4.5.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 327, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 329, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 332, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 333, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 342, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 343, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 344, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 345, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 346, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 347, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 348, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 350, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 351, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 352, column 0
impressive @ 0.12.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python2-pypdf2 @ 1.26.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pypdf2 @ 1.26.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
efi_analyzer @ 0.0.0-0.77c9e3aname

Validate package names

name should use hyphens instead of underscores
texlive-generic-unicode-data @ 51265description

Validate package descriptions

description contains trailing whitespace
texlive-fonts-lm @ 51265description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 93
texlive-fonts-charter @ 51265description

Validate package descriptions

description contains trailing whitespace
iml @ 1.0.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 798
tomsfastmath @ 0.13.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libtommath @ 1.2.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libtomcrypt @ 1.18.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
gappa @ 1.3.5optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
eigen-for-tensorflow-lite @ 3.3.7-1.d10b27foptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
eigen-for-tensorflow @ 3.3.5-1.fd6845384b86optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
eigen @ 3.3.8optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-onnx @ 1.9.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perl-parent @ 5.30.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perl-base @ 5.30.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linphoneqt @ 4.2.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.2-gdbm-ffi @ 20120209.fa1d5b6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.0-gdbm-ffi @ 20120209.fa1d5b6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
symmetrica @ 2.0patch-headers

Validate patch headers

symmetrica-bruch.patch: patch lacks comment and upstream status
symmetrica @ 2.0formatting

Look for formatting issues in the source

line 1490 is way too long (100 characters)
libtomcrypt @ 1.18.2formatting

Look for formatting issues in the source

line 365 is way too long (100 characters)
gmp @ 6.2.0formatting

Look for formatting issues in the source

line 83 is way too long (96 characters)
gap @ 4.11.0formatting

Look for formatting issues in the source

line 1212 is way too long (98 characters)
eigen @ 3.3.8formatting

Look for formatting issues in the source

tabulation on line 1056, column 0
perl-search-xapian @ 1.2.25.4description

Validate package descriptions

use @code or similar ornament instead of quotes
recoll @ 1.31.2inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
swish-e @ 2.4.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
recoll @ 1.31.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
xapian @ 1.4.18optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libtocc @ 1.0.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
blueman @ 2.2.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
hash-extender @ 0.0-2.cb8aaeeoptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libsecp256k1 @ 20200615-1.dbd41dbformatting

Look for formatting issues in the source

line 1110 is way too long (103 characters)
python2-babel @ 2.9.0description

Validate package descriptions

description contains trailing whitespace
python-babel @ 2.9.0description

Validate package descriptions

description contains trailing whitespace
python-argopt @ 0.7.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python2-babel @ 2.9.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-tenacity @ 6.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-hdf4 @ 0.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-colorlog @ 4.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-bidict @ 0.21.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-babel @ 2.9.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
qemu-minimal @ 6.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
yelp-xsl @ 3.34.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 300
tracker @ 2.3.5description

Validate package descriptions

description contains trailing whitespace
soundconverter @ 3.0.2description

Validate package descriptions

description contains trailing whitespace
yelp-tools @ 3.32.2inputs-should-be-native

Identify inputs that should be native inputs

'itstool' should probably be a native input
lollypop @ 1.4.6inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libgee @ 0.20.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libdazzle @ 3.37.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libchamplain @ 0.12.16inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
gnome-tweaks @ 3.34.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gnome @ 3.34.5inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
gjs @ 1.58.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
geoclue @ 2.5.7inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
eolie @ 0.9.101inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
d-feet @ 0.3.14inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
cheese @ 3.38.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
apostrophe @ 2.5inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
totem @ 3.38.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
terminator @ 2.1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
soundconverter @ 3.0.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
setzer @ 0.4.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
rhythmbox @ 3.4.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
remmina @ 1.4.21wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
polari @ 3.36.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
passwordsafe @ 5.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
orca @ 3.34.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
lollypop @ 1.4.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnome-weather @ 3.34.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnome-tweaks @ 3.34.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnome-todo @ 3.28.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnome-shell @ 3.34.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnome-session @ 3.34.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gitg @ 3.32.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gedit @ 3.34.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
eolie @ 0.9.101wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
eog @ 3.34.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
d-feet @ 0.3.14wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cheese @ 3.38.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
caribou @ 0.4.21wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
authenticator @ 3.32.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
apostrophe @ 2.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
tigervnc-server @ 1.11.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
upower @ 0.99.12formatting

Look for formatting issues in the source

line 5366 is way too long (103 characters)
tigervnc-server @ 1.11.0formatting

Look for formatting issues in the source

line 284 is way too long (102 characters)
tigervnc-server @ 1.11.0formatting

Look for formatting issues in the source

line 287 is way too long (102 characters)
tigervnc-server @ 1.11.0formatting

Look for formatting issues in the source

tabulation on line 296, column 0
libsoup @ 2.72.0formatting

Look for formatting issues in the source

line 4817 is way too long (128 characters)
libsoup @ 2.72.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
gdm @ 3.34.1formatting

Look for formatting issues in the source

line 8231 is way too long (103 characters)
vim-full @ 8.2.3487formatting

Look for formatting issues in the source

line 234 is way too long (98 characters)
ghc-bsb-http-chunked @ 0.0.0.4tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ghc-yesod-form @ 1.7.0description

Validate package descriptions

description contains trailing whitespace
ghc-tasty-silver @ 3.2.3description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-operational @ 0.2.4.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
ghc-llvm-hs-pure @ 9.0.0description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-llvm-hs @ 9.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-inline-c @ 0.9.1.5description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-hxt-unicode @ 9.0.2.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 158
ghc-hsyaml @ 0.2.1.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-gtk2hs-buildtools @ 0.13.8.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 95, 367
ghc-fsnotify @ 0.3.0.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 81
ghc-doclayout @ 0.3.1.1description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-aeson-qq @ 0.8.4description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-wai-cors @ 0.2.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ghc-monad-par @ 0.3.5formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ghc-language-javascript @ 0.7.1.0formatting

Look for formatting issues in the source

line 1961 is way too long (91 characters)
ghc-hxt-unicode @ 9.0.2.4formatting

Look for formatting issues in the source

line 1506 is way too long (91 characters)
ghc-base-unicode-symbols @ 0.2.4.2formatting

Look for formatting issues in the source

line 967 is way too long (93 characters)
ghc-base-unicode-symbols @ 0.2.4.2formatting

Look for formatting issues in the source

line 981 is way too long (101 characters)
java-jsch-agentproxy-usocket-nc @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
java-jsch-agentproxy-usocket-nc @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
java-jsch-agentproxy-usocket-jna @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
java-jsch-agentproxy-usocket-jna @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
java-jsch-agentproxy-sshagent @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
java-jsch-agentproxy-sshagent @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
java-jsch-agentproxy-pageant @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
java-jsch-agentproxy-pageant @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
java-jsch-agentproxy-jsch @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
java-jsch-agentproxy-jsch @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
java-jsch-agentproxy-core @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
java-jsch-agentproxy-connector-factory @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
java-jsch-agentproxy-connector-factory @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
java-testng @ 6.14.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
java-jnacl @ 0.1.0-2.094e819optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
antlr4 @ 4.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
java-xmlunit-matchers @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-xmlunit-legacy @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-xmlunit @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-xerial-core @ 2.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-stringtemplate @ 4.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-stax2-api @ 4.0.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-powermock-reflect @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-powermock-modules-junit4-common @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-powermock-modules-junit4 @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-powermock-core @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-powermock-api-support @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-powermock-api-easymock @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-archiver @ 4.2.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-tinybundles @ 2.1.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core-spi @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core-junit @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-util-property @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-util @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-store @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-spi @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-monitors @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-lang @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-io @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-native-access-platform @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-native-access @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-mvel2 @ 2.3.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-microemulator-cldc @ 2.0.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-mail @ 1.6.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-logback-core @ 1.2.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-logback-classic @ 1.2.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-lmax-disruptor @ 3.3.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-usocket-nc @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-usocket-jna @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-sshagent @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-pageant @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-jsch @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-core @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-connector-factory @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-joda-time @ 2.9.9source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-joda-convert @ 1.9.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jline @ 2.14.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jline @ 1.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-jms-api-spec @ 2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-interceptors-api-spec @ 1.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-el-api-spec @ 3.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jansi-native @ 1.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jansi @ 1.16source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-hawtjni @ 1.15source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-gson @ 2.8.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-modules-base-mrbean @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-modules-base-jaxb @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-dataformat-yaml @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-databind @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-core @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-annotations @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-datanucleus-javax-persistence @ 2.2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-cdi-api @ 2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-aqute-libg @ 3.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-aqute-bndlib @ 3.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-aqute-bnd-annotation @ 3.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-sec-dispatcher @ 1.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide
java-plexus-digest @ 1.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@3.1 collide
java-plexus-container-default @ 1.7.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-component-metadata @ 1.7.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@13 and apache-parent-pom@21 collide
java-plexus-compiler-manager @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-compiler-javac @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-compiler-api @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide
java-plexus-archiver @ 4.2.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@6.1 collide
java-modello-test @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-plugins-xpp3 @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-plugins-xml @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-plugins-java @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-core @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-eclipse-sisu-plexus @ 0.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide