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
ghc-tasty-expected-failure @ 0.11.1.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 185
ghc-hxt-unicode @ 9.0.2.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 158
ghc-aeson-qq @ 0.8.2description

Validate package descriptions

description should start with an upper-case letter or digit
fstrcmp @ 0.7.D001description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 236
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
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
kodi-wayland @ 18.8patch-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
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
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)
js-filesaver @ 1.3.8formatting

Look for formatting issues in the source

line 534 is way too long (99 characters)
idris @ 1.3.3formatting

Look for formatting issues in the source

line 104 is way too long (93 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)
guile-sdl @ 0.5.2formatting

Look for formatting issues in the source

line 607 is way too long (111 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)
gmp @ 6.2.0formatting

Look for formatting issues in the source

line 82 is way too long (96 characters)
ghc-hxt-unicode @ 9.0.2.4formatting

Look for formatting issues in the source

line 1486 is way too long (91 characters)
efitools @ 1.9.2formatting

Look for formatting issues in the source

line 215 is way too long (113 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
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
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
libtomcrypt @ 1.18.2formatting

Look for formatting issues in the source

line 341 is way too long (100 characters)
cfitsio @ 3.49description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 197
ghc-base-unicode-symbols @ 0.2.3formatting

Look for formatting issues in the source

line 956 is way too long (101 characters)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 324, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 326, 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 330, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 339, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 340, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 341, 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 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 349, column 0
lua5.2-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
lua5.1-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
lua-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2 @ 2.7.17patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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
python @ 3.8.2formatting

Look for formatting issues in the source

line 483 is way too long (93 characters)
lua-tablepool @ 0.01formatting

Look for formatting issues in the source

line 1062 is way too long (100 characters)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

line 1027 is way too long (104 characters)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

line 1028 is way too long (93 characters)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

line 1029 is way too long (123 characters)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

line 1030 is way too long (112 characters)
lua-resty-shell @ 0.03formatting

Look for formatting issues in the source

line 1094 is way too long (100 characters)
lua-resty-shell @ 0.03formatting

Look for formatting issues in the source

line 1096 is way too long (119 characters)
lua-resty-shell @ 0.03formatting

Look for formatting issues in the source

line 1097 is way too long (108 characters)
lua-resty-lrucache @ 0.10formatting

Look for formatting issues in the source

line 987 is way too long (100 characters)
lua-resty-lrucache @ 0.10formatting

Look for formatting issues in the source

line 989 is way too long (119 characters)
lua-resty-lrucache @ 0.10formatting

Look for formatting issues in the source

line 990 is way too long (108 characters)
lua-resty-core @ 0.1.18formatting

Look for formatting issues in the source

line 952 is way too long (95 characters)
tesseract-ocr @ 4.1.1-1.97079faformatting

Look for formatting issues in the source

line 121 is way too long (93 characters)
python2 @ 2.7.17formatting

Look for formatting issues in the source

line 183 is way too long (99 characters)
python2 @ 2.7.17formatting

Look for formatting issues in the source

line 292 is way too long (98 characters)
389-ds-base @ 1.4.0.31inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
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)
eigen @ 3.3.8formatting

Look for formatting issues in the source

tabulation on line 1025, column 0
nextcloud-client @ 3.1.3inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
owncloud-client @ 2.7.6.3261patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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
ibus-anthy @ 1.5.9inputs-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
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)
quaternion @ 0.0.9.4finputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
gramps @ 5.1.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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
missfits @ 2.8.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 268
itcl @ 4.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
xplanet @ 1.3.1patch-file-names

Validate file names and availability of patches

xplanet-1.3.1-libdisplay_DisplayOutput.cpp.patch: file name is too long
xplanet @ 1.3.1patch-file-names

Validate file names and availability of patches

xplanet-1.3.1-xpUtil-Add2017LeapSecond.cpp.patch: file name is too long
jimtcl @ 0.80formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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
perl-test-object @ 0.08description

Validate package descriptions

use @code or similar ornament instead of quotes
sonata @ 1.7.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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
glibc-locales-2.29 @ 2.29patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
glibc-locales @ 2.31patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
glibc-hurd-headers @ 2.31patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
coreutils-minimal @ 8.32patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
binutils-gold @ 2.34patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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
lsh @ 2.1patch-headers

Validate patch headers

lsh-fix-x11-forwarding.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
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
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)
glibc @ 2.31formatting

Look for formatting issues in the source

line 828 is way too long (98 characters)
dejagnu @ 1.6.2formatting

Look for formatting issues in the source

line 60 is way too long (91 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)
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 502 is way too long (107 characters)
fcitx-qt5 @ 1.2.6inputs-should-be-native

Identify inputs that should be native inputs

'intltool' should probably be a native input
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-next @ 3.9.2patch-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
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)
dico @ 2.11inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
busybox @ 1.33.1formatting

Look for formatting issues in the source

line 93 is way too long (92 characters)
grantleetheme @ 20.04.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
netsurf @ 3.10patch-headers

Validate patch headers

netsurf-message-timestamp.patch: patch lacks comment and upstream status
tigervnc-server @ 1.11.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile-zstd @ 0.1.1description

Validate package descriptions

use @code or similar ornament instead of quotes
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)
guile-for-guile-emacs @ 2.1.2-1.15ca784formatting

Look for formatting issues in the source

line 544 is way too long (96 characters)
guile-for-guile-emacs @ 2.1.2-1.15ca784formatting

Look for formatting issues in the source

trailing white space on line 548
ucsim @ 0.6-pre68description

Validate package descriptions

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

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
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
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
librecad @ 2.2.0-rc2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 682 is way too long (99 characters)
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
infamous-plugins @ 0.3.0formatting

Look for formatting issues in the source

line 1047 is way too long (104 characters)
faad2 @ 2.8.8formatting

Look for formatting issues in the source

line 1745 is way too long (95 characters)
gcompris @ 17.05formatting

Look for formatting issues in the source

line 136 is way too long (96 characters)
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
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.1formatting

Look for formatting issues in the source

line 870 is way too long (92 characters)
lxqt-session @ 0.17.1formatting

Look for formatting issues in the source

line 877 is way too long (100 characters)
lxqt-session @ 0.17.1formatting

Look for formatting issues in the source

line 895 is way too long (98 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)
libdqlite @ 1.7.0description

Validate package descriptions

description should start with an upper-case letter or digit
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
fcitx5-gtk @ 5.0.7inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-clf @ 0.5.7inputs-should-be-native

Identify inputs that should be native inputs

'python2-nose' should probably be a native input
python-pytest-httpbin @ 0.2.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-clf @ 0.5.7inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
http-parser @ 2.9.4-1.ec8b5eepatch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
cawbird @ 1.4.1formatting

Look for formatting issues in the source

line 86 is way too long (104 characters)
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)
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-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-microemulator-cldc @ 2.0.4source-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-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
antlr3 @ 3.5.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-stringtemplate@3.2.1 and java-stringtemplate@4.0.6 collide
java-tunnelvisionlabs-antlr4-runtime-annotations @ 4.7.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-tunnelvisionlabs-antlr4-runtime-annotations @ 4.7.4patch-file-names

Validate file names and availability of patches

java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long
java-tunnelvisionlabs-antlr4-runtime @ 4.7.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-tunnelvisionlabs-antlr4-runtime @ 4.7.4patch-file-names

Validate file names and availability of patches

java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long
java-tunnelvisionlabs-antlr4 @ 4.7.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-tunnelvisionlabs-antlr4 @ 4.7.4patch-file-names

Validate file names and availability of patches

java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long
java-antlr4-runtime @ 4.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
antlr4 @ 4.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-ops4j-pax-exam-core-spi @ 4.11.0formatting

Look for formatting issues in the source

line 9960 is way too long (92 characters)
java-ops4j-pax-exam-core-spi @ 4.11.0formatting

Look for formatting issues in the source

line 9964 is way too long (98 characters)
java-ops4j-pax-exam-core-spi @ 4.11.0formatting

Look for formatting issues in the source

line 9968 is way too long (99 characters)
java-ops4j-pax-exam-core-spi @ 4.11.0formatting

Look for formatting issues in the source

line 9969 is way too long (91 characters)
java-ops4j-pax-exam-core-spi @ 4.11.0formatting

Look for formatting issues in the source

line 9972 is way too long (100 characters)
java-ops4j-base-lang @ 1.5.0formatting

Look for formatting issues in the source

line 9656 is way too long (110 characters)
java-fasterxml-jackson-dataformat-yaml @ 2.9.4formatting

Look for formatting issues in the source

line 10286 is way too long (104 characters)
java-fasterxml-jackson-dataformat-xml @ 2.9.4formatting

Look for formatting issues in the source

line 10401 is way too long (98 characters)
java-fasterxml-jackson-databind @ 2.9.4formatting

Look for formatting issues in the source

line 10118 is way too long (96 characters)
java-fasterxml-jackson-core @ 2.9.4formatting

Look for formatting issues in the source

line 10067 is way too long (93 characters)
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

line 9841 is way too long (91 characters)
antlr4 @ 4.8formatting

Look for formatting issues in the source

line 8713 is way too long (96 characters)
antlr4 @ 4.8formatting

Look for formatting issues in the source

line 8787 is way too long (100 characters)
boost-static @ 1.72.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
boost-python2 @ 1.72.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
boost-mpi @ 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)
python2-pybedtools @ 0.8.2description

Validate package descriptions

description should start with an upper-case letter or digit
python-pybedtools @ 0.8.2description

Validate package descriptions

description should start with an upper-case letter or digit
blasr-libcpp @ 5.3.3formatting

Look for formatting issues in the source

line 682 is way too long (95 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
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
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
emilua @ 0.3.2formatting

Look for formatting issues in the source

line 1151 is way too long (98 characters)
java-plexus-archiver @ 4.2.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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
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
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
java-openjfx-media @ 8.202patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-openjfx-graphics @ 8.202patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-openjfx-controls @ 8.202patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-openjfx-base @ 8.202patch-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)
java-sisu-build-api @ 0.0.7formatting

Look for formatting issues in the source

line 5120 is way too long (98 characters)
java-plexus-sec-dispatcher @ 1.4formatting

Look for formatting issues in the source

line 4997 is way too long (107 characters)
java-plexus-compiler-javac @ 2.8.4formatting

Look for formatting issues in the source

line 4878 is way too long (95 characters)
java-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

line 2829 is way too long (99 characters)
java-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

line 2840 is way too long (98 characters)
java-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

line 2879 is way too long (96 characters)
java-openjfx-base @ 8.202formatting

Look for formatting issues in the source

line 2769 is way too long (111 characters)
java-openjfx-base @ 8.202formatting

Look for formatting issues in the source

line 2784 is way too long (99 characters)
java-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

line 4009 is way too long (112 characters)
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

tabulation on line 7541, column 20
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

tabulation on line 7542, column 20
java-eclipse-jdt-core @ 3.16.0formatting

Look for formatting issues in the source

line 7601 is way too long (98 characters)
java-commons-jxpath @ 1.3formatting

Look for formatting issues in the source

line 6345 is way too long (93 characters)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

line 6113 is way too long (91 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)
audacity @ 2.4.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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
mia @ 2.4.6inputs-should-be-native

Identify inputs that should be native inputs

'doxygen' should probably be a native input
vtk @ 9.0.1formatting

Look for formatting issues in the source

line 299 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
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
python2-sure @ 1.4.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-mock' should probably be a native input
python-sure @ 1.4.11inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python2-packaging @ 20.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
rapicorn @ 16.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-cython' should probably be a native input
ctl @ 1.5.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
blender @ 2.92.0formatting

Look for formatting issues in the source

line 540 is way too long (97 characters)
libreoffice @ 7.1.4.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
aws-checksums @ 0.1.11patch-headers

Validate patch headers

aws-checksums-cmake-prefix.patch: patch lacks comment and upstream status
aws-c-io @ 0.9.2patch-headers

Validate patch headers

aws-c-io-cmake-prefix.patch: patch lacks comment and upstream status
aws-c-io @ 0.9.2patch-headers

Validate patch headers

aws-c-io-disable-networking-tests.patch: patch lacks comment and upstream status
aws-c-event-stream @ 0.2.7patch-headers

Validate patch headers

aws-c-event-stream-cmake-prefix.patch: patch lacks comment and upstream status
aws-c-cal @ 0.4.5patch-headers

Validate patch headers

aws-c-cal-cmake-prefix.patch: patch lacks comment and upstream status
python-faiss @ 1.5.0inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
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
librsvg @ 2.50.3formatting

Look for formatting issues in the source

line 3495 is way too long (104 characters)
glade @ 3.36.0formatting

Look for formatting issues in the source

line 3195 is way too long (91 characters)
spiped @ 1.6.1formatting

Look for formatting issues in the source

line 2640 is way too long (94 characters)
restinio @ 0.6.13formatting

Look for formatting issues in the source

line 3373 is way too long (105 characters)
restinio @ 0.6.13formatting

Look for formatting issues in the source

line 3387 is way too long (95 characters)
libmediaart @ 1.9.5inputs-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
zeitgeist @ 1.0.3formatting

Look for formatting issues in the source

tabulation on line 756, column 18
zeitgeist @ 1.0.3formatting

Look for formatting issues in the source

tabulation on line 759, column 18
gnome-keyring @ 3.34.0formatting

Look for formatting issues in the source

line 2532 is way too long (91 characters)
gnome-initial-setup @ 3.32.1formatting

Look for formatting issues in the source

line 1473 is way too long (91 characters)
shell-functools @ 0.3.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 121, 206
sh-z @ 1.11description

Validate package descriptions

use @code or similar ornament instead of quotes
tigervnc-server @ 1.11.0formatting

Look for formatting issues in the source

line 285 is way too long (102 characters)
tigervnc-server @ 1.11.0formatting

Look for formatting issues in the source

line 288 is way too long (102 characters)
tigervnc-server @ 1.11.0formatting

Look for formatting issues in the source

tabulation on line 297, column 0
perl-specio @ 0.38description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 185, 314
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
gtkspell3 @ 3.0.10inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile2.2-rsvg @ 2.18.1-0.05c6a2fpatch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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
cairo-xcb @ 1.16.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
volctl @ 0.8.2formatting

Look for formatting issues in the source

line 2464 is way too long (98 characters)
telepathy-glib @ 0.24.1formatting

Look for formatting issues in the source

line 952 is way too long (92 characters)
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 9743 is way too long (97 characters)
mkvtoolnix @ 52.0.0formatting

Look for formatting issues in the source

line 924 is way too long (96 characters)
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

tabulation on line 831, column 0
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

tabulation on line 832, column 0
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

tabulation on line 833, column 0
at-spi2-core @ 2.34.0formatting

Look for formatting issues in the source

line 677 is way too long (97 characters)
vim-full @ 8.2.2689formatting

Look for formatting issues in the source

line 231 is way too long (98 characters)
ecasound @ 2.9.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471
audio-to-midi @ 2020.7inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
zita-resampler @ 1.6.2formatting

Look for formatting issues in the source

line 3850 is way too long (93 characters)
vamp @ 2.6formatting

Look for formatting issues in the source

line 3333 is way too long (94 characters)
maven-wagon-provider-api @ 3.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/qg1n5gy83igc3bx3bm796g9cgqw3nwvq-maven-wagon-provider-api-3.3.4 and /gnu/store/4dm35z81yh2j7rs2p9hdiz92r7lq0klb-maven-wagon-provider-api-3.3.4 collide
qemu-minimal @ 6.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
opencv @ 3.4.3formatting

Look for formatting issues in the source

line 513 is way too long (132 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
python2-pygpgme @ 0.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-pygpgme @ 0.3patch-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)
python2-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1174 is way too long (96 characters)
python-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1141 is way too long (94 characters)
fc-host-tools @ 15formatting

Look for formatting issues in the source

line 1261 is way too long (122 characters)
emacs-erlang @ 24.0.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
elixir @ 1.12.0formatting

Look for formatting issues in the source

line 77 is way too long (97 characters)
elixir @ 1.12.0formatting

Look for formatting issues in the source

line 78 is way too long (99 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)
kuserfeedback @ 1.0.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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-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
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)
python-pytest-vcr @ 1.0.2-1.4d6c7b3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-isort @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-checkdocs @ 1.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-pytest-helpers-namespace @ 2021.3.24inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
jucipp @ 1.6.3description

Validate package descriptions

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

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
gajim @ 1.3.2inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
gajim @ 1.3.2patch-headers

Validate patch headers

gajim-honour-GAJIM_PLUGIN_PATH.patch: patch lacks comment and upstream status
perl-search-xapian @ 1.2.25.4description

Validate package descriptions

use @code or similar ornament instead of quotes
rseqc @ 3.0.1inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
python2-pbcore @ 1.2.10inputs-should-be-native

Identify inputs that should be native inputs

'python2-cython' should probably be a native input
newick-utils @ 1.6-1.da121155inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
newick-utils @ 1.6-1.da121155inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
mosaicatcher @ 0.3.1patch-headers

Validate patch headers

mosaicatcher-unbundle-htslib.patch: patch lacks comment and upstream status
ncbi-vdb @ 2.10.6formatting

Look for formatting issues in the source

tabulation on line 6378, column 26
jellyfish @ 2.3.0formatting

Look for formatting issues in the source

line 4751 is way too long (92 characters)
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)
conda @ 4.10.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
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
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-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-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-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-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-cdi-api @ 2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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
java-powermock-reflect @ 1.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-powermock-modules-junit4-common @ 1.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-powermock-modules-junit4 @ 1.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-powermock-core @ 1.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-powermock-api-support @ 1.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-powermock-api-easymock @ 1.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-apache-ivy @ 2.4.0patch-file-names

Validate file names and availability of patches

java-apache-ivy-port-to-latest-bouncycastle.patch: file name is too long
java-testng @ 6.14.3formatting

Look for formatting issues in the source

line 10984 is way too long (91 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

line 12745 is way too long (92 characters)
java-native-access @ 4.5.1formatting

Look for formatting issues in the source

line 12925 is way too long (91 characters)
java-logback-classic @ 1.2.3formatting

Look for formatting issues in the source

line 13504 is way too long (102 characters)
java-joda-time @ 2.9.9formatting

Look for formatting issues in the source

line 12318 is way too long (92 characters)
java-jnacl @ 0.1.0-2.094e819formatting

Look for formatting issues in the source

line 11061 is way too long (93 characters)
java-jnacl @ 0.1.0-2.094e819formatting

Look for formatting issues in the source

line 11071 is way too long (92 characters)
java-jgit @ 4.2.0.201601211800-rformatting

Look for formatting issues in the source

line 13607 is way too long (93 characters)
java-hawtjni @ 1.15formatting

Look for formatting issues in the source

line 12004 is way too long (92 characters)
java-geronimo-xbean-reflect @ 4.5formatting

Look for formatting issues in the source

line 11755 is way too long (92 characters)
java-geronimo-xbean-bundleutils @ 4.5formatting

Look for formatting issues in the source

line 11870 is way too long (122 characters)
java-eclipse-sisu-plexus @ 0.3.4formatting

Look for formatting issues in the source

line 13321 is way too long (104 characters)
java-eclipse-sisu-plexus @ 0.3.4formatting

Look for formatting issues in the source

line 13328 is way too long (95 characters)
java-commons-httpclient @ 3.1formatting

Look for formatting issues in the source

line 12787 is way too long (91 characters)
java-apache-ivy @ 2.4.0formatting

Look for formatting issues in the source

line 13145 is way too long (101 characters)
xkbprint @ 1.0.5description

Validate package descriptions

use @code or similar ornament instead of quotes
r-demultiplex @ 1.0.2-1.6e2a142description

Validate package descriptions

description should start with an upper-case letter or digit
variant-tools @ 3.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
vsearch @ 2.9.1patch-headers

Validate patch headers

vsearch-unbundle-cityhash.patch: patch lacks comment and upstream status
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)
salmon @ 1.4.0formatting

Look for formatting issues in the source

line 9772 is way too long (92 characters)
r-cellchat @ 1.0.0-1.21edd22formatting

Look for formatting issues in the source

line 8677 is way too long (92 characters)
minimap2 @ 2.18formatting

Look for formatting issues in the source

line 11003 is way too long (113 characters)
dropseq-tools @ 1.13formatting

Look for formatting issues in the source

tabulation on line 10350, column 0
dropseq-tools @ 1.13formatting

Look for formatting issues in the source

tabulation on line 10362, column 0
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
mesa-headers @ 20.2.4patch-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 300 is way too long (120 characters)
julia-openspecfun-jll @ 0.5.3+4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 129
julia-compilersupportlibraries-jll @ 0.4.0+1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 134
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
julia-xorg-xcb-util-renderutil-jll @ 0.3.9+1formatting

Look for formatting issues in the source

line 2375 is way too long (93 characters)
julia-libuuid-jll @ 2.36.0+0formatting

Look for formatting issues in the source

line 1141 is way too long (92 characters)
julia-compilersupportlibraries-jll @ 0.4.0+1formatting

Look for formatting issues in the source

line 155 is way too long (91 characters)
python-distributed @ 2021.07.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
python-distributed @ 2021.07.1formatting

Look for formatting issues in the source

line 894 is way too long (104 characters)
ppsspp @ 1.11.3-1.69fa207description

Validate package descriptions

use @code or similar ornament instead of quotes
cc65 @ 2.19formatting

Look for formatting issues in the source

line 2568 is way too long (167 characters)
julia-chainrulestestutils @ 1.0.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 260
php @ 7.4.22formatting

Look for formatting issues in the source

line 191 is way too long (93 characters)
php @ 7.4.22formatting

Look for formatting issues in the source

line 192 is way too long (93 characters)
php @ 7.4.22formatting

Look for formatting issues in the source

line 203 is way too long (91 characters)
php @ 7.4.22formatting

Look for formatting issues in the source

line 211 is way too long (93 characters)
php @ 7.4.22formatting

Look for formatting issues in the source

line 233 is way too long (92 characters)
php @ 7.4.22formatting

Look for formatting issues in the source

line 234 is way too long (96 characters)
php @ 7.4.22formatting

Look for formatting issues in the source

line 239 is way too long (96 characters)
php @ 7.4.22formatting

Look for formatting issues in the source

line 281 is way too long (91 characters)
php @ 7.4.22formatting

Look for formatting issues in the source

line 294 is way too long (92 characters)
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)
libblockdev @ 2.25formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
google-brotli @ 1.0.9formatting

Look for formatting issues in the source

line 2189 is way too long (94 characters)
dmraid @ 1.0.0.rc16-3formatting

Look for formatting issues in the source

line 886 is way too long (91 characters)
eid-mw @ 5.0.14formatting

Look for formatting issues in the source

line 163 is way too long (97 characters)
eid-mw @ 5.0.14formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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)
geany @ 1.37.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
u-boot-wandboard @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-sifive-unmatched @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-qemu-riscv64 @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-mx6cuboxi @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-malta @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-cubietruck @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-cubieboard @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-bananapi-m2-ultra @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-am335x-evm @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-a20-olinuxino-micro @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-a20-olinuxino-lime2 @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-a20-olinuxino-lime @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-wandboard @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-tools @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-sifive-unmatched @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-qemu-riscv64 @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-mx6cuboxi @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-malta @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-cubietruck @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-cubieboard @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-bananapi-m2-ultra @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-am335x-evm @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-a20-olinuxino-micro @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-a20-olinuxino-lime2 @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-a20-olinuxino-lime @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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
u-boot-wandboard @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
u-boot-tools @ 2021.07formatting

Look for formatting issues in the source

line 592 is way too long (97 characters)
u-boot-sifive-unmatched @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
u-boot-qemu-riscv64 @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
u-boot-mx6cuboxi @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
u-boot-malta @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
u-boot-cubietruck @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
u-boot-cubieboard @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
u-boot-bananapi-m2-ultra @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
u-boot-am335x-evm @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
u-boot-a20-olinuxino-micro @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
u-boot-a20-olinuxino-lime2 @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
u-boot-a20-olinuxino-lime @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
c-blosc @ 1.18.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
iml @ 1.0.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 798
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 1459 is way too long (100 characters)
gap @ 4.11.0formatting

Look for formatting issues in the source

line 1181 is way too long (98 characters)
python2-pygame @ 1.9.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 123
python-xsge @ 2020.09.07description

Validate package descriptions

description should start with an upper-case letter or digit
python-pygame @ 1.9.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 123
grfcodec @ 6.0.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 100
deutex @ 5.2.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 60
python2-renpy @ 7.4.8patch-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
freehdl @ 0.0.8inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
freehdl @ 0.0.8inputs-should-be-native

Identify inputs that should be native inputs

'libtool' 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)
meshlab @ 2020.06formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
freehdl @ 0.0.8formatting

Look for formatting issues in the source

line 1952 is way too long (101 characters)
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
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
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
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
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
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
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
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

line 3347 is way too long (92 characters)
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

tabulation on line 3367, column 0
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

tabulation on line 3368, column 0
slepc-openmpi @ 3.11.1formatting

Look for formatting issues in the source

tabulation on line 2941, column 0
slepc-complex-openmpi @ 3.11.1formatting

Look for formatting issues in the source

line 2957 is way too long (92 characters)
scalapack @ 2.0.2formatting

Look for formatting issues in the source

tabulation on line 983, column 0
pt-scotch32 @ 6.1.1formatting

Look for formatting issues in the source

tabulation on line 3628, column 0
pt-scotch @ 6.1.1formatting

Look for formatting issues in the source

tabulation on line 3606, 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 3717, column 0
nomad-optimizer @ 4.1.0formatting

Look for formatting issues in the source

line 1918 is way too long (92 characters)
mumps-openmpi @ 5.2.1formatting

Look for formatting issues in the source

tabulation on line 3186, column 0
mumps @ 5.2.1formatting

Look for formatting issues in the source

line 3100 is way too long (94 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)
u-boot-sifive-unleashed @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-pinebook @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-pine64-plus @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-pine64-lts @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-am335x-boneblack @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-sifive-unleashed @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-pinebook @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-pine64-plus @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-pine64-lts @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-am335x-boneblack @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-sifive-unleashed @ 2021.07formatting

Look for formatting issues in the source

line 702 is way too long (93 characters)
u-boot-pinebook @ 2021.07formatting

Look for formatting issues in the source

line 789 is way too long (127 characters)
u-boot-pine64-plus @ 2021.07formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
u-boot-pine64-lts @ 2021.07formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
u-boot-am335x-boneblack @ 2021.07formatting

Look for formatting issues in the source

line 740 is way too long (95 characters)
ibus-libhangul @ 1.5.3description

Validate package descriptions

description should start with an upper-case letter or digit
librime @ 1.7.3formatting

Look for formatting issues in the source

line 334 is way too long (93 characters)
r-tidyr @ 1.1.3description

Validate package descriptions

description should start with an upper-case letter or digit
r-minqa @ 1.2.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 133, 136, 139
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-cardata @ 3.0-4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 45, 56
r-boot @ 1.3-28description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 125, 142
python-rpy2 @ 3.4.5description

Validate package descriptions

description should start with an upper-case letter or digit
r-esc @ 0.5.1formatting

Look for formatting issues in the source

line 6111 is way too long (94 characters)
julia @ 1.6.2formatting

Look for formatting issues in the source

line 373 is way too long (107 characters)
julia @ 1.6.2formatting

Look for formatting issues in the source

line 375 is way too long (106 characters)
julia @ 1.6.2formatting

Look for formatting issues in the source

line 572 is way too long (101 characters)
julia @ 1.6.2formatting

Look for formatting issues in the source

line 577 is way too long (124 characters)
ruby-rb-inotify @ 0.9.10description

Validate package descriptions

description should start with an upper-case letter or digit
ruby-tzinfo-data @ 1.2021.1formatting

Look for formatting issues in the source

line 5870 is way too long (101 characters)
ruby-tzinfo-data @ 1.2021.1formatting

Look for formatting issues in the source

line 5871 is way too long (107 characters)
ruby-iruby @ 0.3formatting

Look for formatting issues in the source

line 501 is way too long (112 characters)
ruby-asciidoctor-pdf @ 1.5.3-1.d257440formatting

Look for formatting issues in the source

line 1896 is way too long (99 characters)
python-coveralls @ 3.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
openexr @ 2.5.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
tuxmath @ 2.0.3description

Validate package descriptions

description should start with an upper-case letter or digit
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)
python2-psycopg2 @ 2.8.6description

Validate package descriptions

description should start with an upper-case letter or digit
python2-ccm @ 2.1.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 84
python-psycopg2 @ 2.8.6description

Validate package descriptions

description should start with an upper-case letter or digit
python-ccm @ 2.1.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 84
guile-wiredtiger @ 0.7.0description

Validate package descriptions

use @code or similar ornament instead of quotes
sqlcipher @ 3.4.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
dune-istl-openmpi @ 2.7.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
sundials-openmpi @ 3.1.1formatting

Look for formatting issues in the source

tabulation on line 5742, column 0
hypre-openmpi @ 2.15.1formatting

Look for formatting issues in the source

tabulation on line 5171, column 0
ublock-origin-chromium @ 1.37.2description

Validate package descriptions

description should start with an upper-case letter or digit
libchop @ 0.5.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 257, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 258, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 259, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 260, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 261, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 262, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 263, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 264, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 265, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 268, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 269, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 271, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 272, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 273, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 274, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 275, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 277, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 278, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 279, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 280, column 0
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
gnome-shell-extension-gsconnect @ 33inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
gnome-shell-extension-dash-to-panel @ 38inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
icedove @ 78.13.0formatting

Look for formatting issues in the source

line 1338 is way too long (98 characters)
icedove @ 78.13.0formatting

Look for formatting issues in the source

line 1493 is way too long (105 characters)
icedove @ 78.13.0formatting

Look for formatting issues in the source

line 1495 is way too long (102 characters)
rtl-sdr @ 0.6.0description

Validate package descriptions

use @code or similar ornament instead of quotes
hackrf @ 2021.03.1description

Validate package descriptions

use @code or similar ornament instead of quotes
mkbootimg @ 7.1.2_r36patch-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
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
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
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
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
mbedtls-apache @ 2.26.0formatting

Look for formatting issues in the source

line 980 is way too long (96 characters)
fdroidserver @ 1.1.9formatting

Look for formatting issues in the source

line 941 is way too long (106 characters)
fastboot @ 7.1.2_r36formatting

Look for formatting issues in the source

line 701 is way too long (105 characters)
android-safe-iop @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 278, column 20
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 386 is way too long (97 characters)
sbcl-trivial-gray-streams @ 0.0.0-1.ebd59b1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 75
sbcl-quri @ 0.4.0description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
sbcl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

description should start with an upper-case letter or digit
sbcl-cl-reexport @ 0.1-1.312f366description

Validate package descriptions

description should start with an upper-case letter or digit
sbcl-cl-libxml2 @ 0.3.4-1.8d03110description

Validate package descriptions

description should start with an upper-case letter or digit
sbcl-cl-cookie @ 0.9.10-1.cea55aedescription

Validate package descriptions

description should start with an upper-case letter or digit
sbcl-circular-streams @ 0.1.0-1.e770baddescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 79
ecl-trivial-gray-streams @ 0.0.0-1.ebd59b1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 75
ecl-quri @ 0.4.0description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
ecl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

description should start with an upper-case letter or digit
ecl-cl-reexport @ 0.1-1.312f366description

Validate package descriptions

description should start with an upper-case letter or digit
ecl-cl-libxml2 @ 0.3.4-1.8d03110description

Validate package descriptions

description should start with an upper-case letter or digit
ecl-cl-cookie @ 0.9.10-1.cea55aedescription

Validate package descriptions

description should start with an upper-case letter or digit
ecl-circular-streams @ 0.1.0-1.e770baddescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 79
cl-trivial-gray-streams @ 0.0.0-1.ebd59b1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 75
cl-reexport @ 0.1-1.312f366description

Validate package descriptions

description should start with an upper-case letter or digit
cl-quri @ 0.4.0description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
cl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

description should start with an upper-case letter or digit
cl-circular-streams @ 0.1.0-1.e770baddescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 79
sbcl-cl-gobject-introspection @ 0.3-1.d0136c8inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
ecl-cl-gobject-introspection @ 0.3-1.d0136c8inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
cl-gobject-introspection @ 0.3-1.d0136c8inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
cl-clml @ 0.0.0-0.95505b5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
sbcl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 6389 is way too long (91 characters)
sbcl-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

line 295 is way too long (96 characters)
sbcl-cl-strings @ 0.0.0-1.c5c5cbaformatting

Look for formatting issues in the source

line 1352 is way too long (98 characters)
sbcl-cl-libxml2 @ 0.3.4-1.8d03110formatting

Look for formatting issues in the source

line 18694 is way too long (114 characters)
sbcl-caveman @ 2.4.0-1.faa5f7eformatting

Look for formatting issues in the source

line 12960 is way too long (140 characters)
sbcl-caveman @ 2.4.0-1.faa5f7eformatting

Look for formatting issues in the source

line 12962 is way too long (97 characters)
sbcl-caveman @ 2.4.0-1.faa5f7eformatting

Look for formatting issues in the source

line 12963 is way too long (110 characters)
ecl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 6389 is way too long (91 characters)
ecl-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

line 295 is way too long (96 characters)
ecl-cl-strings @ 0.0.0-1.c5c5cbaformatting

Look for formatting issues in the source

line 1352 is way too long (98 characters)
ecl-cl-libxml2 @ 0.3.4-1.8d03110formatting

Look for formatting issues in the source

line 18694 is way too long (114 characters)
ecl-caveman @ 2.4.0-1.faa5f7eformatting

Look for formatting issues in the source

line 12960 is way too long (140 characters)
ecl-caveman @ 2.4.0-1.faa5f7eformatting

Look for formatting issues in the source

line 12962 is way too long (97 characters)
ecl-caveman @ 2.4.0-1.faa5f7eformatting

Look for formatting issues in the source

line 12963 is way too long (110 characters)
cl-strings @ 0.0.0-1.c5c5cbaformatting

Look for formatting issues in the source

line 1352 is way too long (98 characters)
cl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 6389 is way too long (91 characters)
cl-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

line 295 is way too long (96 characters)
cl-libxml2 @ 0.3.4-1.8d03110formatting

Look for formatting issues in the source

line 18694 is way too long (114 characters)
tor @ 0.4.6.7description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 574
ocaml-zarith @ 1.12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
ocaml-topkg @ 1.0.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 51
ocaml-qcheck @ 0.12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 52, 156
ocaml-down @ 0.0.3description

Validate package descriptions

use @code or similar ornament instead of quotes
ocaml-cmdliner @ 1.0.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 304
ocaml-dose3 @ 5.0.1patch-headers

Validate patch headers

ocaml-dose3-dont-make-printconf.patch: patch lacks comment and upstream status
opam @ 2.1.0formatting

Look for formatting issues in the source

line 874 is way too long (99 characters)
opam @ 2.1.0formatting

Look for formatting issues in the source

line 876 is way too long (99 characters)
opam @ 2.1.0formatting

Look for formatting issues in the source

line 878 is way too long (99 characters)
opam @ 2.1.0formatting

Look for formatting issues in the source

line 880 is way too long (102 characters)
ocaml-sedlex @ 2.3formatting

Look for formatting issues in the source

line 2689 is way too long (97 characters)
ocaml-migrate-parsetree @ 2.1.0formatting

Look for formatting issues in the source

line 1807 is way too long (101 characters)
ocaml-dose3 @ 5.0.1formatting

Look for formatting issues in the source

line 633 is way too long (92 characters)
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)
rust-nu-plugin-query-json @ 0.36.0description

Validate package descriptions

description should start with an upper-case letter or digit
nushell @ 0.36.0description

Validate package descriptions

use @code or similar ornament instead of quotes
r-wmtsa @ 2.0-3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 105, 128
r-sapa @ 2.0-3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 97, 120
r-palmerpenguins @ 0.1.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 268
r-squarem @ 2021.1formatting

Look for formatting issues in the source

line 4327 is way too long (91 characters)
r-shiny @ 1.6.0formatting

Look for formatting issues in the source

line 1993 is way too long (103 characters)
r-shiny @ 1.6.0formatting

Look for formatting issues in the source

line 2001 is way too long (94 characters)
r-shiny @ 1.6.0formatting

Look for formatting issues in the source

line 2033 is way too long (92 characters)
r-bslib @ 0.2.5.1formatting

Look for formatting issues in the source

line 1961 is way too long (102 characters)
xygrib @ 1.2.6.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 256
osm-gps-map @ 1.1.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
tegola @ 0.7.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
imposm3 @ 0.6.0-alpha.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
libgeotiff @ 1.5.1patch-file-names

Validate file names and availability of patches

libgeotiff-adapt-test-script-for-proj-6.2.patch: file name is too long
xygrib @ 1.2.6.1formatting

Look for formatting issues in the source

line 1256 is way too long (95 characters)
proj.4 @ 4.9.3formatting

Look for formatting issues in the source

line 573 is way too long (92 characters)
python-pytools @ 2021.2.7description

Validate package descriptions

use @code or similar ornament instead of quotes
darktable @ 3.6.0formatting

Look for formatting issues in the source

line 499 is way too long (102 characters)
python2-pytest-subtesthack @ 0.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 106
python2-flexmock @ 0.10.4description

Validate package descriptions

description should start with an upper-case letter or digit
python-pytest-subtesthack @ 0.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 106
python-flexmock @ 0.10.4description

Validate package descriptions

description should start with an upper-case letter or digit
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-warnings @ 0.2.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 @ 3.6.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-mock' should probably be a native input
python2-pytest-mock @ 3.6.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
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
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-pytest-cache @ 1.0inputs-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-nose2 @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest-cov' 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
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-warnings @ 0.2.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-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-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-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-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-pytest-cache @ 1.0inputs-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-nose2 @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' 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-fixtures @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' 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
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
python2-unittest2 @ 1.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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
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
xftwidth @ 20170402description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 96, 234
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
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1898, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1899, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1901, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1902, column 0
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
trf @ 4.09.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 387
samblaster @ 0.1.24description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 263
repeat-masker @ 4.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 387
r-bseqsc @ 1.0-1.fef3f3edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 395
python2-twobitreader @ 3.1.6description

Validate package descriptions

description should start with an upper-case letter or digit
python2-plastid @ 0.4.8description

Validate package descriptions

description should start with an upper-case letter or digit
python2-bx-python @ 0.8.2description

Validate package descriptions

description should start with an upper-case letter or digit
python-twobitreader @ 3.1.6description

Validate package descriptions

description should start with an upper-case letter or digit
python-pytest-mp @ 0.0.4p2description

Validate package descriptions

description should start with an upper-case letter or digit
python-pyfit-sne @ 1.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
python-plastid @ 0.4.8description

Validate package descriptions

description should start with an upper-case letter or digit
python-nbclient @ 0.5.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 62
python-mypy @ 0.790description

Validate package descriptions

use @code or similar ornament instead of quotes
python-jupyterlab-widgets @ 1.0.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-drep @ 3.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-dnaio @ 0.3description

Validate package descriptions

description should start with an upper-case letter or digit
python-bx-python @ 0.8.2description

Validate package descriptions

description should start with an upper-case letter or digit
kraken2 @ 2.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 206
python-velocyto @ 0.17.17inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
python-robber @ 1.1.5inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-pytest-tornasync @ 0.6.0.post2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-sanic @ 1.7.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-mp @ 0.0.4p2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-console-scripts @ 1.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-pytest-console-scripts @ 1.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
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-drep @ 3.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-bbknn @ 1.3.6inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
clipper @ 2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
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
vcflib @ 1.0.2formatting

Look for formatting issues in the source

line 13764 is way too long (92 characters)
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)
python-scanpy @ 1.8.1formatting

Look for formatting issues in the source

line 11519 is way too long (96 characters)
python-pytorch @ 1.9.0formatting

Look for formatting issues in the source

line 2672 is way too long (94 characters)
phast @ 1.5formatting

Look for formatting issues in the source

tabulation on line 14017, column 30
kraken2 @ 2.1.1formatting

Look for formatting issues in the source

tabulation on line 14237, column 0
kraken2 @ 2.1.1formatting

Look for formatting issues in the source

tabulation on line 14238, column 0
kraken2 @ 2.1.1formatting

Look for formatting issues in the source

tabulation on line 14239, column 0
java-picard @ 2.3.0formatting

Look for formatting issues in the source

line 4266 is way too long (104 characters)
java-picard @ 2.10.3formatting

Look for formatting issues in the source

line 4325 is way too long (104 characters)
java-picard @ 2.10.3formatting

Look for formatting issues in the source

line 4355 is way too long (91 characters)
java-picard @ 1.113formatting

Look for formatting issues in the source

line 4412 is way too long (96 characters)
java-picard @ 1.113formatting

Look for formatting issues in the source

line 4413 is way too long (117 characters)
fastahack @ 1.0.0formatting

Look for formatting issues in the source

line 13651 is way too long (91 characters)
ensembl-vep @ 103.1formatting

Look for formatting issues in the source

line 14566 is way too long (92 characters)
ensembl-vep @ 103.1formatting

Look for formatting issues in the source

line 14614 is way too long (100 characters)
discrover @ 1.6.0formatting

Look for formatting issues in the source

line 3163 is way too long (91 characters)
mrrescue @ 1.02edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 2
fifengine @ 0.4.2inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
cockatrice @ 2.8.0inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
tuxpaint @ 0.9.23patch-headers

Validate patch headers

tuxpaint-stamps-path.patch: patch lacks comment and upstream status
pinball @ 0.3.20201218patch-headers

Validate patch headers

pinball-system-ltdl.patch: patch lacks comment and upstream status
bsd-games @ 2.17.0patch-headers

Validate patch headers

bsd-games-bad-ntohl-cast.patch: patch lacks comment and upstream status
bsd-games @ 2.17.0patch-headers

Validate patch headers

bsd-games-gamescreen.h.patch: patch lacks comment and upstream status
bsd-games @ 2.17.0patch-headers

Validate patch headers

bsd-games-null-check.patch: patch lacks comment and upstream status
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3268, column 0
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3269, column 0
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3270, column 0
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3271, column 0
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3272, column 0
einstein @ 2.0formatting

Look for formatting issues in the source

line 4714 is way too long (96 characters)
python-pybbi @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
python-coolbox @ 0.3.8inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
instead @ 3.3.5inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
warsow-qfusion @ 2.5-1.c4de15dpatch-headers

Validate patch headers

warsow-qfusion-fix-bool-return-type.patch: patch lacks comment and upstream status
cataclysm-dda @ 0.F-2formatting

Look for formatting issues in the source

line 905 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-fibers @ 1.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
electron-cash @ 4.2.5inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
emacs-beancount @ 2.3.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
monero @ 0.17.2.3patch-headers

Validate patch headers

monero-use-system-miniupnpc.patch: patch lacks comment and upstream status
bitcoin-unlimited @ 1.9.2.0formatting

Look for formatting issues in the source

line 1468 is way too long (91 characters)
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-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-pycrypto @ 2.6.1patch-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-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
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
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
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
perl-unicode-utf8 @ 0.62tests-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
inkscape @ 1.1tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ghc-bsb-http-chunked @ 0.0.0.4tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
fennel @ 0.9.1tests-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 @ 21.2.1tests-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
sbcl-trivial-benchmark @ 2.0.0-1.42d7673description

Validate package descriptions

description contains trailing whitespace
sbcl-hu.dwim.common-lisp @ 2021-01-27description

Validate package descriptions

description contains trailing whitespace
ruby-ox @ 2.6.0description

Validate package descriptions

description contains trailing whitespace
quazip @ 0.9.1description

Validate package descriptions

description contains trailing whitespace
python2-stdnum @ 1.14description

Validate package descriptions

description contains trailing whitespace
python-stdnum @ 1.14description

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
ivar @ 1.3.1description

Validate package descriptions

description contains trailing whitespace
ghc-yesod-form @ 1.6.7description

Validate package descriptions

description contains trailing whitespace
ghc-crypto-cipher-tests @ 0.0.11description

Validate package descriptions

description contains leading whitespace
ecl-trivial-benchmark @ 2.0.0-1.42d7673description

Validate package descriptions

description contains trailing whitespace
ecl-hu.dwim.common-lisp @ 2021-01-27description

Validate package descriptions

description contains trailing whitespace
dirvish @ 1.2.1description

Validate package descriptions

description contains trailing whitespace
cl-trivial-benchmark @ 2.0.0-1.42d7673description

Validate package descriptions

description contains trailing whitespace
cl-hu.dwim.common-lisp @ 2021-01-27description

Validate package descriptions

description contains trailing whitespace
buildapp @ 1.5.6description

Validate package descriptions

description contains trailing whitespace
bindfs @ 1.15.1description

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
youtube-viewer @ 3.8.1wrapper-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
wxmaxima @ 21.05.2wrapper-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
volk @ 2.4.1wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
vlc @ 3.0.16wrapper-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
virt-viewer @ 7.0wrapper-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
vapoursynth @ 53wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
utox @ 0.18.1wrapper-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
ungoogled-chromium @ 92.0.4515.159-0.8164c91wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
tuxpaint @ 0.9.23wrapper-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
tetoolkit @ 2.0.3wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
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
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
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
sushi @ 3.32.1wrapper-inputs

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
sqitch @ 1.1.0wrapper-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
sonata @ 1.7.0wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
signing-party @ 2.11wrapper-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
shorah @ 1.99.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
rsem @ 1.3.1wrapper-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
roary @ 3.12.0wrapper-inputs

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
repeat-masker @ 4.1.1wrapper-inputs

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

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

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
redshift @ 1.12wrapper-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
rcas-web @ 0.1.0wrapper-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
ranger @ 1.9.3wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
raincat @ 1.2.1wrapper-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
qtox @ 1.17.3wrapper-inputs

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

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

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

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

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
python-git-review @ 1.28.0wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-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
prosody @ 0.11.9wrapper-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
prank @ 170427wrapper-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
ploticus @ 2.42wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
pinentry-rofi @ 2.0.3wrapper-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-sgmls @ 1.1wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
perl-net-psyc @ 1.3wrapper-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
perl-cworld-dekker @ 1.01wrapper-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
pdfarranger @ 1.7.1wrapper-inputs

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
patchutils @ 0.3.4wrapper-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
parcimonie @ 0.11.0wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
parallel @ 20210822wrapper-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
ocrodjvu @ 0.12wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
obs @ 27.0.1wrapper-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
nestopia-ue @ 1.48wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
nanopolish @ 0.11.1-1.6331dc4wrapper-inputs

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
mcg @ 2.1.2wrapper-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
manuskript @ 0.12.0wrapper-inputs

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
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
lxpanel @ 0.10.0wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
lightdm-gtk-greeter @ 2.0.7wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
lightdm @ 1.30.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
licensecheck @ 3.0.37wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
librecad @ 2.2.0-rc2wrapper-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
krita @ 4.4.5wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
knot-resolver @ 5.4.1wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
kicad @ 5.1.6wrapper-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
kdenlive @ 20.08.3wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-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
julia @ 1.6.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
jack2 @ 1.9.14wrapper-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
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
isc-dhcp @ 4.4.2-P1wrapper-inputs

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
impressive @ 0.12.1wrapper-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
icedove @ 78.13.0wrapper-inputs

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ibus-libhangul @ 1.5.3wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ibus-anthy @ 1.5.9wrapper-inputs

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
guix-build-coordinator @ 0-33.c2f0c5bwrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
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-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
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
gtk-doc @ 1.28wrapper-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
grass @ 7.8.5wrapper-inputs

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

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

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
godot @ 3.2.3wrapper-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
gnucash @ 4.2wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnome-shell-extension-gsconnect @ 33wrapper-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
gnome-maps @ 3.38.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
giara @ 0.3wrapper-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
gfeeds @ 0.16.2wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
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
gccgo @ 10.3.0wrapper-inputs

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

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

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

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

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

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

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
foo2zjs @ 20200610.1wrapper-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
fntsample @ 5.3wrapper-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
fio @ 3.27wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
find-circ @ 1.2-1.8655dcawrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
filtlong @ 0.2.0-1.d1bb46dwrapper-inputs

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

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

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

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

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ensembl-vep @ 103.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 @ 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
edirect @ 13.3.20200128wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-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 @ 21.2.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
dvdstyler @ 3.0.4wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
dirvish @ 1.2.1wrapper-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
deluge @ 2.0.3wrapper-inputs

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
darktable @ 3.6.0wrapper-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
couger @ 1.8.2wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
corsix-th @ 0.65wrapper-inputs

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cloud-utils @ 0.32wrapper-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
ceph @ 14.2.16wrapper-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
cawbird @ 1.4.1wrapper-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
bioperl-minimal @ 1.7.0wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
bamm @ 1.7.3wrapper-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
asymptote @ 2.70wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-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
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
arriba @ 1.0.1wrapper-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
arandr @ 0.1.10wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
anki @ 2.1.16wrapper-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
akku @ 1.0.1wrapper-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
389-ds-base @ 1.4.0.31wrapper-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?
zsh-autosuggestions @ 0.7.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
z3 @ 4.8.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
xapian @ 1.4.18optional-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?
unknown-horizons @ 2019.1optional-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?
tomsfastmath @ 0.13.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
tng @ 1.8.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
terminology @ 1.9.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
taxtastic @ 0.8.11optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
tadbit @ 1.0.1optional-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?
sqlcipher @ 3.4.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
sparql-query @ 1.1optional-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?