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
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
mkbootimg @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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
fastboot @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 42
presentty @ 0.2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 165
ncurses @ 6.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 95 is way too long (93 characters)
gmp @ 6.2.0formatting

Look for formatting issues in the source

line 82 is way too long (96 characters)
fastboot @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 277, column 20
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

tabulation on line 297, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 299, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 301, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 303, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 305, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 307, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 309, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 311, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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
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
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 673 is way too long (99 characters)
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
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
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)
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)
nextcloud-client @ 3.1.3inputs-should-be-native

Identify inputs that should be native inputs

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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)
zbar @ 0.23inputs-should-be-native

Identify inputs that should be native inputs

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Identify inputs that shouldn't be inputs at all

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

Identify inputs that shouldn't be inputs at all

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

Identify inputs that shouldn't be inputs at all

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

Identify inputs that shouldn't be inputs at all

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

Validate package descriptions

description should start with an upper-case letter or digit
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
mesa-opencl-icd @ 20.2.4patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate package descriptions

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Check for autogenerated tarballs

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 241 is way too long (137 characters)
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
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
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
gcompris @ 17.05formatting

Look for formatting issues in the source

line 136 is way too long (96 characters)
mrrescue @ 1.02edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 2
tuxpaint @ 0.9.23patch-headers

Validate patch headers

tuxpaint-stamps-path.patch: patch lacks comment and upstream status
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
axoloti-runtime @ 1.0.12-2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Validate package descriptions

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

Validate file names and availability of patches

file names of patches should start with the package name
fcitx5-gtk @ 5.0.7inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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)
font-canada1500 @ 1.101formatting

Look for formatting issues in the source

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

enlightenment-fix-setuid-path.patch: patch lacks comment and upstream status
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)
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
chroma @ 1.18description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 33
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
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
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 3497 is way too long (104 characters)
glade @ 3.36.0formatting

Look for formatting issues in the source

line 3197 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
cairo-xcb @ 1.16.0patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9743 is way too long (97 characters)
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)
rust-winit @ 0.24.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Validate package descriptions

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Validate patch headers

tcsh-fix-autotest.patch: patch lacks comment and upstream status
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
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)
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-compilersupportlibraries-jll @ 0.4.0+1formatting

Look for formatting issues in the source

line 155 is way too long (91 characters)
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
php @ 7.4.22formatting

Look for formatting issues in the source

line 192 is way too long (93 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
xdg-user-dirs @ 0.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
python-cchardet @ 2.1.7description

Validate package descriptions

description should start with an upper-case letter or digit
udiskie @ 2.1.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
telepathy-mission-control @ 5.16.5inputs-should-be-native

Identify inputs that should be native inputs

'gtk-doc' should probably be a native input
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)
malcontent @ 0.8.0formatting

Look for formatting issues in the source

line 356 is way too long (91 characters)
localed @ 241formatting

Look for formatting issues in the source

line 819 is way too long (96 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)
u-boot-tools @ 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-tools @ 2021.07formatting

Look for formatting issues in the source

line 592 is way too long (97 characters)
shogun @ 6.1.3inputs-should-be-native

Identify inputs that should be native inputs

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

Look for formatting issues in the source

line 526 is way too long (91 characters)
emacs-geiser-racket @ 0.16formatting

Look for formatting issues in the source

tabulation on line 397, column 0
netcdf-parallel-openmpi @ 4.7.4patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate patch headers

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

Validate patch headers

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 945 is way too long (91 characters)
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)
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-iruby @ 0.3formatting

Look for formatting issues in the source

line 501 is way too long (112 characters)
openexr @ 2.5.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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)
awscli @ 1.18.203inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
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
mbedtls-apache @ 2.26.0formatting

Look for formatting issues in the source

line 980 is way too long (96 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
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
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
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)
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)
cl-strings @ 0.0.0-1.c5c5cbaformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 295 is way too long (96 characters)
tor @ 0.4.6.7description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
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-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
python-pytools @ 2021.2.7description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Validate patch headers

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

Validate patch headers

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Validate patch headers

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that shouldn't be inputs at all

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

Identify inputs that shouldn't be inputs at all

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

Identify inputs that shouldn't be inputs at all

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

Identify inputs that shouldn't be inputs at all

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

Identify inputs that shouldn't be inputs at all

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

Identify inputs that shouldn't be inputs at all

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

Identify inputs that shouldn't be inputs at all

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1337 is way too long (92 characters)
perl-crypt-unixcrypt_xs @ 0.11name

Validate package names

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

Validate package names

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

Validate package names

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

Validate package names

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

Check if tests are explicitly enabled

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

Check if tests are explicitly enabled

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

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
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
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 @ 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
quazip @ 0.9.1description

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
dirvish @ 1.2.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
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
xdg-utils @ 1.1.3wrapper-inputs

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
qutebrowser @ 2.3.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
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
presentty @ 0.2.1wrapper-inputs

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ploticus @ 2.42wrapper-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-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-file-mimeinfo @ 0.29wrapper-inputs

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
luakit @ 2.3wrapper-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
licensecheck @ 3.0.37wrapper-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
kristall @ 0.3-1.204b08awrapper-inputs

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

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

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
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
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
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
guile-wm @ 1.0-1.f3c7b3bwrapper-inputs

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
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?
uthash @ 2.1.0optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
tomsfastmath @ 0.13.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?
solid @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
selene @ 2017.08.25optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-protobuf @ 3.10.3optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
rsnapshot @ 1.4.4optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ranger @ 1.9.3optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-s3transfer @ 0.3.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-pyxdg @ 0.27optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-pypdf2 @ 1.26.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-pygpgme @ 0.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-pastel @ 0.2.0optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-webassets @ 2.0optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pyxdg @ 0.27optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pypdf2 @ 1.26.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pygpgme @ 0.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pure-protobuf @ 2.0.1optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pastel @ 0.2.0optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-geventhttpclient @ 1.4.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-flask-wtf @ 0.14.3optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ocaml @ 4.11.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ocaml @ 4.09.0optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mes-rb5 @ 0.22optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
lua5.2-socket @ 3.0-rc1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
lua5.2-expat @ 1.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
lua5.1-socket @ 3.0-rc1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
lua5.1-expat @ 1.3.0optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libtommath @ 1.2.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libtomcrypt @ 1.18.2optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
java-testng @ 6.14.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
java-jnacl @ 0.1.0-2.094e819optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
genimage @ 11optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
dvdisaster @ 0.79.5optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
dejagnu @ 1.6.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
date @ 2.4.1-9a0ee254optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
crossguid @ 0.0-2.fef89a4optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bmaptools @ 3.6optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bind @ 9.16.16optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bear @ 3.0.4optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
autotrace @ 0.40.0-20190624.59optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
antlr4 @ 4.1optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
cgit @ 1.2.3inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
cgit @ 1.2.3inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
myrepos @ 1.20180726wrapper-inputs

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
guix-data-service @ 0.0.1-27.df2a0a7wrapper-inputs

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

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

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

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

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

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

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
stgit @ 1.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-gitdb @ 4.0.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
aegis @ 4.24optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
aegis @ 4.24patch-headers

Validate patch headers

aegis-perl-tempdir2.patch: patch lacks comment and upstream status
serf @ 1.3.9formatting

Look for formatting issues in the source

line 2010 is way too long (92 characters)
git-crypt @ 0.6.0formatting

Look for formatting issues in the source

line 846 is way too long (91 characters)
bazaar @ 2.7.0formatting

Look for formatting issues in the source

line 166 is way too long (93 characters)
libicns @ 0.8.1tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
qtwebglplugin @ 5.15.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 244
openjpeg-data @ 2020.05.19description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
libjxr @ 1.1description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
mypaint @ 2.0.1wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
lodepng @ 20200215-1.48e5364optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libavif @ 0.9.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pyqt-without-qtwebkit @ 5.15.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
steghide @ 0.5.1patch-headers

Validate patch headers

steghide-fixes.patch: patch lacks comment and upstream status
qtserialport @ 5.15.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2151 is way too long (105 characters)
libjxr @ 1.1formatting

Look for formatting issues in the source

line 523 is way too long (95 characters)
python-locust @ 1.4.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mergerfs @ 2.32.6formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python-mpd2 @ 3.0.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
verilator @ 4.204description

Validate package descriptions

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

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

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

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

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

Validate file names and availability of patches

file names of patches should start with the package name
libxt @ 1.2.0patch-headers

Validate patch headers

libxt-guix-search-paths.patch: patch lacks comment and upstream status
xproto @ 7.0.31formatting

Look for formatting issues in the source

line 5009 is way too long (91 characters)
remmina @ 1.4.20wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
mdadm-static @ 4.1description

Validate package descriptions

description should start with an upper-case letter or digit
ecryptfs-utils @ 111description

Validate package descriptions

description should start with an upper-case letter or digit
singularity @ 2.6.1wrapper-inputs

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wireless-tools @ 30.pre9formatting

Look for formatting issues in the source

line 4053 is way too long (104 characters)
crda @ 3.18formatting

Look for formatting issues in the source

line 4160 is way too long (100 characters)
r-bsgenome-dmelanogaster-ucsc-dm3-masked @ 1.3.99formatting

Look for formatting issues in the source

line 276 is way too long (95 characters)
r-seqlogo @ 1.58.0description

Validate package descriptions

description should start with an upper-case letter or digit
r-rtracklayer @ 1.52.1description

Validate package descriptions

description should start with an upper-case letter or digit
r-biomart @ 2.48.3description

Validate package descriptions

description should start with an upper-case letter or digit
blueman @ 2.2.1wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
r-hsmmsinglecell @ 1.2.0formatting

Look for formatting issues in the source

line 1277 is way too long (95 characters)
help2man @ 1.47.13formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
go @ 1.16.8tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 861 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 862 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 863 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 864 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 865 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 866 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 867 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 868 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 873 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 874 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 883 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 884 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 886 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 887 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 888 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 889 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 890 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 891 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 893 is way too long (97 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 894 is way too long (97 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 896 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 898 is way too long (92 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 899 is way too long (92 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 900 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 901 is way too long (97 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 911 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 912 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 913 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 914 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 915 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 916 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 917 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 918 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 923 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 924 is way too long (98 characters)
rocm-bandwidth-test @ 4.3.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 122
clang-runtime @ 3.9.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.9-libsanitizer-mode-field.patch: file name is too long
clang-runtime @ 3.8.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.8-libsanitizer-mode-field.patch: file name is too long
clang-runtime @ 3.7.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.8-libsanitizer-mode-field.patch: file name is too long
clang @ 9.0.1formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 8.0.0formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 7.1.0formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 6.0.1formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 3.9.1formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 3.8.1formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 3.7.1formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 3.5.2formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 11.0.0formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
clang @ 10.0.0formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
blanket @ 0.4.1wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python-pytest-django @ 4.4.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-django-taggit @ 1.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-tagging @ 0.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-statici18n @ 2.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-sortedm2m @ 3.0.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-simple-math-captcha @ 1.0.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-rq @ 2.3.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-redis @ 4.12.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-picklefield @ 3.0.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-override-storage @ 0.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-filter @ 2.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-debug-toolbar @ 3.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-contact-form @ 1.8.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-auth-ldap @ 2.4.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-appconf @ 1.0.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-allauth @ 0.42.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
perl-libxml @ 0.08description

Validate package descriptions

description should start with an upper-case letter or digit
java-xpp3 @ 1.1.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 188
java-mxparser @ 1.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 188, 473
java-kxml2 @ 2.4.2description

Validate package descriptions

description should start with an upper-case letter or digit
xlsx2csv @ 0.7.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
tinyxml @ 2.6.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-lxml @ 4.4.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-lxml @ 4.4.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-libxml2 @ 2.9.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

line 2376 is way too long (91 characters)
java-xom @ 127formatting

Look for formatting issues in the source

trailing white space on line 1927
java-xmlpull-api-v1 @ 1.1.3.4bformatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
i3-wm @ 4.18.3description

Validate package descriptions

description should start with an upper-case letter or digit
docbook2x @ 0.8.8inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
dblatex @ 0.3.11wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
quickswitch-i3 @ 2.2-1.ed692b1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
kontactinterface @ 20.04.1description

Validate package descriptions

description contains leading whitespace
kldap @ 20.04.1description

Validate package descriptions

description contains leading whitespace
kldap @ 20.04.1description

Validate package descriptions

description contains trailing whitespace
cuirass @ 1.1.0-4.6019040wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python-requests_ntlm @ 1.1.0name

Validate package names

name should use hyphens instead of underscores
python2-empy @ 3.3.3tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
wpa-supplicant-minimal @ 2.9description

Validate package descriptions

description should start with an upper-case letter or digit
wpa-supplicant-gui @ 2.9description

Validate package descriptions

description should start with an upper-case letter or digit
wpa-supplicant @ 2.9description

Validate package descriptions

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

Validate package descriptions

description contains trailing whitespace
texlive-fonts-iwona @ 0.995bdescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 42
texlive-charter @ 51265description

Validate package descriptions

description contains trailing whitespace
rust-async-process @ 1.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
python2-html2text @ 2019.8.11description

Validate package descriptions

description should start with an upper-case letter or digit
python2-babel @ 2.9.0description

Validate package descriptions

description contains trailing whitespace
python-html2text @ 2020.1.16description

Validate package descriptions

description should start with an upper-case letter or digit
python-babel @ 2.9.0description

Validate package descriptions

description contains trailing whitespace
minetest-basic-trains @ 1.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
fakeroot @ 1.25.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 114, 240
python-requests-unixsocket @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-case @ 1.5.3inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-case @ 1.5.3inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
notifymuch @ 0.1-1.9d4aaf5inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-argopt @ 0.7.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
wpa-supplicant-gui @ 2.9wrapper-inputs

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
notifymuch @ 0.1-1.9d4aaf5wrapper-inputs

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

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

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

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

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

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

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python2-zope-exceptions @ 4.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-zope-component @ 4.6.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-webencodings @ 0.5.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-verboselogs @ 1.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-six @ 1.14.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-oauthlib @ 3.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-mimeparse @ 1.6.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-html2text @ 2019.8.11optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-et-xmlfile @ 1.0.1optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-click @ 7.1.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-babel @ 2.9.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-zope-exceptions @ 4.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-zope-copy @ 4.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-zope-component @ 4.6.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-wsproto @ 0.15.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-webencodings @ 0.5.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-verboselogs @ 1.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-tornado @ 6.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-terminado @ 0.10.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-tenacity @ 6.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-six @ 1.14.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-sh @ 1.12.14optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-requests-unixsocket @ 0.2.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-querystring-parser @ 1.2.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-priority @ 1.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-parse @ 1.18.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-openpyxl @ 3.0.5optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-openid @ 3.2.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-oauthlib @ 3.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-mimeparse @ 1.6.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-jsonpickle @ 1.4.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-hypercorn @ 0.10.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-html2text @ 2020.1.16optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-hdf4 @ 0.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-flask-babel @ 1.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-falcon @ 2.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-et-xmlfile @ 1.0.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-databricks-cli @ 0.14.1optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-click @ 7.1.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-cfn-lint @ 0.54.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-caniusepython3 @ 7.2.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-bidict @ 0.21.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-babel @ 2.9.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-aws-xray-sdk @ 2.6.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-asgiref @ 3.3.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-apiron @ 5.1.0optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-aenum @ 2.2.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-requests @ 2.20.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-urllib3@1.24.3 and python-urllib3@1.26.2 collide
wpa-supplicant-minimal @ 2.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
wpa-supplicant-gui @ 2.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-pybugz @ 0.6.11patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
hostapd @ 2.9patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
bpftrace @ 0.11.4patch-headers

Validate patch headers

bpftrace-disable-bfd-disasm.patch: patch lacks comment and upstream status
xfce4-clipman-plugin @ 1.6.2formatting

Look for formatting issues in the source

line 504 is way too long (91 characters)
tumbler @ 4.16.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
texlive-latex-pgf @ 51265formatting

Look for formatting issues in the source

line 6968 is way too long (98 characters)
texlive-context @ 51265formatting

Look for formatting issues in the source

trailing white space on line 7335
scons @ 3.0.4formatting

Look for formatting issues in the source

line 2871 is way too long (96 characters)
rust-async-compression @ 0.3.7formatting

Look for formatting issues in the source

line 2984 is way too long (92 characters)
rust-actix-derive @ 0.5.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python-tornado @ 5.1.1formatting

Look for formatting issues in the source

line 1708 is way too long (91 characters)
patchwork @ 3.0.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ghc @ 8.6.5formatting

Look for formatting issues in the source

line 593 is way too long (91 characters)
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-sifive-unleashed @ 2021.07description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-qemu-riscv64-smode @ 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-puma-rk3399 @ 2021.07description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-pinebook-pro-rk3399 @ 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-novena @ 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-firefly-rk3399 @ 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-am335x-boneblack @ 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
rtl-sdr @ 0.6.0description

Validate package descriptions

use @code or similar ornament instead of quotes
r-bioassayr @ 1.30.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-pymol @ 2.5.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
patchutils @ 0.4.2wrapper-inputs

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
parallel @ 20210922wrapper-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
tng @ 1.8.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
quickjs @ 2021-03-27optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
maven-wagon-provider-api @ 3.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/d2fsa2092739rs59l2w4dydzzw5p8rld-maven-wagon-provider-api-3.3.4 and /gnu/store/cqhfmjr46drhymxlmxszcr14srqyp55l-maven-wagon-provider-api-3.3.4 collide
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-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-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-rockpro64-rk3399 @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-rock64-rk3328 @ 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-smode @ 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-puma-rk3399 @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-pinebook-pro-rk3399 @ 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-novena @ 2021.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-nintendo-nes-classic-edition @ 2018.11patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-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-firefly-rk3399 @ 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-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-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
python-clang @ 12.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-clang @ 11.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-clang @ 10.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ocaml-llvm @ 9.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-erlang @ 24.0.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-clang-rename @ 9.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-clang-format @ 9.0.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.5-libsanitizer-mode-field.patch: file name is too long
u-boot-wandboard @ 2021.07formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 703 is way too long (93 characters)
u-boot-sifive-unleashed @ 2021.07formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 790 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-mx6cuboxi @ 2021.07formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 703 is way too long (93 characters)
r-unifiedwmwqpcr @ 1.28.0formatting

Look for formatting issues in the source

line 10993 is way too long (92 characters)
r-genomicinteractions @ 1.26.0formatting

Look for formatting issues in the source

line 5508 is way too long (92 characters)
js-filesaver @ 1.3.8formatting

Look for formatting issues in the source

line 533 is way too long (99 characters)
elixir @ 1.12.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 78 is way too long (99 characters)
clang @ 12.0.1formatting

Look for formatting issues in the source

line 370 is way too long (91 characters)
go-github-com-xanzy-ssh-agent @ 0.2.1description

Validate package descriptions

description contains trailing whitespace
go-github-com-songmu-gitconfig @ 0.1.0description

Validate package descriptions

description should start with an upper-case letter or digit
go-github-com-muesli-termenv @ 0.7.0description

Validate package descriptions

description should start with an upper-case letter or digit
go-github-com-mitchellh-reflectwalk @ 1.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
go-github-com-mattn-go-zglob @ 0.0.3description

Validate package descriptions

description contains leading whitespace
go-github-com-mattn-go-zglob @ 0.0.3description

Validate package descriptions

description contains trailing whitespace
go-github-com-wtolson-go-taglib @ 0.0.0-0.6e68349inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
go-github-com-mesilliac-pulse-simple @ 0.0.0-0.75ac54einputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
go-gitlab-com-ambrevar-golua-unicode @ 0.0.0-0.97ce517optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-wtolson-go-taglib @ 0.0.0-0.6e68349optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-operatorfoundation-shapeshifter-ipc @ 2.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-operatorfoundation-obfs4 @ 1.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-blanu-dust @ 1.0.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-apparentlymart-go-openvpn-mgmt @ 0.0.0-0.4d2ce95optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-rogpeppe-go-internal @ 1.6.1formatting

Look for formatting issues in the source

line 7848 is way too long (101 characters)
go-github-com-multiformats-go-multiaddr-net @ 1.6.3-0.1cb9a0eformatting

Look for formatting issues in the source

line 4957 is way too long (93 characters)
go-github-com-multiformats-go-multiaddr-net @ 1.6.3-0.1cb9a0eformatting

Look for formatting issues in the source

line 4958 is way too long (93 characters)
go-github-com-multiformats-go-multiaddr @ 1.3.0-0.fe1c46fformatting

Look for formatting issues in the source

line 4914 is way too long (93 characters)
go-github-com-mitchellh-go-homedir @ 1.0.0-0.ae18d6bformatting

Look for formatting issues in the source

line 4801 is way too long (95 characters)
go-github-com-mattn-go-shellwords @ 1.0.5-1.2444a32formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
go-github-com-libp2p-go-libp2p-peer @ 2.3.8-0.993d742formatting

Look for formatting issues in the source

line 4706 is way too long (93 characters)
go-github-com-libp2p-go-libp2p-metrics @ 2.1.6-0.a10ff6eformatting

Look for formatting issues in the source

line 4762 is way too long (93 characters)
go-github-com-libp2p-go-libp2p-metrics @ 2.1.6-0.a10ff6eformatting

Look for formatting issues in the source

line 4765 is way too long (93 characters)
go-github-com-gorilla-context @ 0.0.0-0.08b5f42formatting

Look for formatting issues in the source

line 3132 is way too long (164 characters)
go-github-com-davecgh-go-spew @ 1.1.1formatting

Look for formatting issues in the source

line 4369 is way too long (129 characters)
xwallpaper @ 0.7.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 72
xftwidth @ 20170402description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 96, 234
sqitch @ 1.1.0wrapper-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
mysql @ 5.7.33wrapper-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
gammastep @ 2.0.7wrapper-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
cloc @ 1.90wrapper-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
sparql-query @ 1.1optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libproxy @ 0.4.17optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libdrm @ 2.4.103optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
j4-dmenu-desktop @ 2.18optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
clipmenu @ 6.0.1-1.bcbe7b1optional-tests

Make sure tests are only run when requested

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2 @ 2.7.17patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-next @ 3.9.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate patch headers

python-3.8-fix-tests.patch: patch lacks comment and upstream status
python-debug @ 3.8.2patch-headers

Validate patch headers

python-3.8-fix-tests.patch: patch lacks comment and upstream status
python @ 3.8.2patch-headers

Validate patch headers

python-3.8-fix-tests.patch: patch lacks comment and upstream status
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1897, column 0
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 1900, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1901, column 0
python2 @ 2.7.17formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 290 is way too long (98 characters)
python @ 3.8.2formatting

Look for formatting issues in the source

line 481 is way too long (93 characters)
plymouth @ 0.9.5formatting

Look for formatting issues in the source

line 2100 is way too long (91 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
wxmaxima @ 21.05.2wrapper-inputs

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

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

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

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

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

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
z3 @ 4.8.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
pt-scotch32 @ 6.1.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
pt-scotch @ 6.1.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mumps-openmpi @ 5.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mumps-metis-openmpi @ 5.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mumps-metis @ 5.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mumps @ 5.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
maxima @ 5.45.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
hypre @ 2.15.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
scotch32 @ 6.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
scotch-shared @ 6.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
pt-scotch32 @ 6.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
pt-scotch-shared @ 6.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
pt-scotch @ 6.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mumps-openmpi @ 5.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mumps-metis-openmpi @ 5.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mumps-metis @ 5.2.1patch-file-names

Validate file names and availability of patches

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