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
perl6-grammar-debugger @ 1.0.1-1.0375008description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 203
aseba @ 1.6.0-0.3b35de8inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
libmhash @ 0.9.9.9patch-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
libcanberra-gtk2 @ 0.30patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libsigsegv @ 2.12formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 79 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 80 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 83 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 86 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 87 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 93 is way too long (93 characters)
jose @ 10formatting

Look for formatting issues in the source

line 37 is way too long (92 characters)
efitools @ 1.9.2formatting

Look for formatting issues in the source

line 176 is way too long (113 characters)
libdaemon @ 0.14formatting

Look for formatting issues in the source

line 35 is way too long (147 characters)
pth @ 2.0.7formatting

Look for formatting issues in the source

trailing white space on line 42
busybox @ 1.29.3formatting

Look for formatting issues in the source

trailing white space on line 82
busybox @ 1.29.3formatting

Look for formatting issues in the source

line 84 is way too long (92 characters)
openfoam @ 4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 144 is way too long (91 characters)
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)
oath-toolkit @ 2.6.2patch-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
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-libsparse @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 373 is way too long (97 characters)
android-safe-iop @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 128 is way too long (92 characters)
rapicorn @ 16.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-cython' should probably be a native input
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-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-embedder @ 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
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-compat @ 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-core @ 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-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-model @ 3.6.1patch-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-wagon-file @ 3.1.0formatting

Look for formatting issues in the source

line 466 is way too long (125 characters)
maven-wagon-http @ 3.1.0formatting

Look for formatting issues in the source

line 627 is way too long (105 characters)
maven-wagon-http @ 3.1.0formatting

Look for formatting issues in the source

line 632 is way too long (138 characters)
maven-wagon-http @ 3.1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 232 is way too long (93 characters)
maven-embedder @ 3.6.1formatting

Look for formatting issues in the source

line 1271 is way too long (110 characters)
maven-shared-utils @ 3.2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 176 is way too long (99 characters)
maven-core @ 3.6.1formatting

Look for formatting issues in the source

line 1183 is way too long (94 characters)
maven-core @ 3.6.1formatting

Look for formatting issues in the source

line 1184 is way too long (110 characters)
maven-core @ 3.6.1formatting

Look for formatting issues in the source

line 1212 is way too long (99 characters)
maven-core @ 3.6.1formatting

Look for formatting issues in the source

line 1213 is way too long (103 characters)
maven-core @ 3.6.1formatting

Look for formatting issues in the source

line 1214 is way too long (115 characters)
maven-core @ 3.6.1formatting

Look for formatting issues in the source

line 1215 is way too long (118 characters)
fstrcmp @ 0.7.D001description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 236
cryptsetup-static @ 2.2.2formatting

Look for formatting issues in the source

line 102 is way too long (93 characters)
java-jblas @ 1.2.4description

Validate package descriptions

description should start with an upper-case letter or digit
python-pygpgme @ 0.3patch-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
perl-search-xapian @ 1.2.25.2description

Validate package descriptions

use @code or similar ornament instead of quotes
gx-go @ 1.9.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 190 is way too long (95 characters)
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
axoloti-runtime @ 1.0.12-2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 573 is way too long (103 characters)
wgetpaste @ 2.29formatting

Look for formatting issues in the source

line 99 is way too long (113 characters)
libsigrok @ 0.5.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 212 is way too long (92 characters)
ibus-libhangul @ 1.5.3description

Validate package descriptions

description should start with an upper-case letter or digit
jfsutils-static @ 1.1.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
openfoam @ 4.1inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
sonata @ 1.7b1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' 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
flex @ 2.6.4inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
zn-poly @ 0.9.2description

Validate package descriptions

description should start with an upper-case letter or digit
rcm @ 1.3.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 183
graphviz @ 2.38.0-1.f54ac2cinputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
d-feet @ 0.3.14inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
docbook-xml @ 4.5formatting

Look for formatting issues in the source

trailing white space on line 63
docbook-xml @ 4.5formatting

Look for formatting issues in the source

trailing white space on line 64
gramps @ 5.1.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
dejagnu @ 1.6.2formatting

Look for formatting issues in the source

line 60 is way too long (91 characters)
graphviz @ 2.42.3inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
owncloud-client @ 2.5.3.11470patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
js-filesaver @ 1.3.8formatting

Look for formatting issues in the source

line 392 is way too long (99 characters)
js-mathjax @ 2.7.2formatting

Look for formatting issues in the source

line 90 is way too long (91 characters)
ocaml-dose3 @ 5.0.1formatting

Look for formatting issues in the source

line 362 is way too long (92 characters)
r-cardata @ 3.0-3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 45, 56
grantleetheme @ 19.08.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ibus-anthy @ 1.5.9inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
librime @ 1.5.3formatting

Look for formatting issues in the source

line 327 is way too long (93 characters)
lxqt-session @ 0.14.1formatting

Look for formatting issues in the source

line 852 is way too long (100 characters)
lua5.1-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
lua5.2-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
python-pytools @ 2020.1description

Validate package descriptions

use @code or similar ornament instead of quotes
zbar @ 0.23inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
sonata @ 1.7b1source-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
connman @ 1.38description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
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
python-xsge @ 2018.02.26description

Validate package descriptions

description should start with an upper-case letter or digit
python2-xsge @ 2018.02.26description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 123
python2-pygame @ 1.9.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 123
openmw @ 0.45.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
love-nuklear @ v2.6-1.fef4e00formatting

Look for formatting issues in the source

trailing white space on line 704
emacs-erlang @ 21.3.8.13patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ibus @ 1.5.22inputs-should-be-native

Identify inputs that should be native inputs

'gettext' should probably be a native input
plotutils @ 2.6formatting

Look for formatting issues in the source

trailing white space on line 81
gx @ 0.14.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 135 is way too long (99 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 143 is way too long (91 characters)
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.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
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 118 is way too long (114 characters)
mingw-w64-i686-winpthreads @ 7.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mingw-w64-i686 @ 7.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-winpthreads @ 7.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 @ 7.0.0patch-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 275 is way too long (92 characters)
gdb @ 9.1inputs-should-be-native

Identify inputs that should be native inputs

'dejagnu' should probably be a native input
wxwidgets-gtk2 @ 3.1.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-wxpython @ 4.0.7.post1description

Validate package descriptions

description should start with an upper-case letter or digit
gnunet @ 0.12.2formatting

Look for formatting issues in the source

line 297 is way too long (92 characters)
docker @ 19.03.7formatting

Look for formatting issues in the source

line 345 is way too long (95 characters)
docker @ 19.03.7formatting

Look for formatting issues in the source

line 381 is way too long (93 characters)
containerd @ 1.2.5formatting

Look for formatting issues in the source

line 214 is way too long (102 characters)
vim-full @ 8.2.0411formatting

Look for formatting issues in the source

line 197 is way too long (94 characters)
hyperledger-iroha @ 1.1.1formatting

Look for formatting issues in the source

line 169 is way too long (105 characters)
abc @ 0.0-1.5ae4b97formatting

Look for formatting issues in the source

line 86 is way too long (95 characters)
wine @ 5.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
papi @ 5.5.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libdaemon @ 0.14formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
wine64 @ 5.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python2-mapnik @ 3.0.16source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
proj.4 @ 4.9.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 175 is way too long (123 characters)
python-faiss @ 1.5.0inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
espeak-ng @ 1.50description

Validate package descriptions

description should start with an upper-case letter or digit
sbcl-cl-strings @ 0.0.0-1.c5c5cbaformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 133 is way too long (96 characters)
java-openmpi @ 4.0.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
openmpi-thread-multiple @ 4.0.3patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

line 250 is way too long (94 characters)
openmpi @ 4.0.3formatting

Look for formatting issues in the source

line 252 is way too long (96 characters)
icedtea @ 3.7.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1376 is way too long (100 characters)
mate-applets @ 1.24.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 917
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 754 is way too long (92 characters)
mate-menus @ 1.24.0formatting

Look for formatting issues in the source

line 516 is way too long (91 characters)
mate-panel @ 1.24.0formatting

Look for formatting issues in the source

line 679 is way too long (92 characters)
kget @ 19.08.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 169
kget @ 19.08.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ocaml-zarith @ 1.9.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 51
ocaml4.07-sedlex @ 2.1formatting

Look for formatting issues in the source

line 2081 is way too long (97 characters)
vorbis-tools @ 1.4.0formatting

Look for formatting issues in the source

trailing white space on line 323
mingw-w64-x86_64-winpthreads @ 7.0.0formatting

Look for formatting issues in the source

line 90 is way too long (91 characters)
mingw-w64-x86_64 @ 7.0.0formatting

Look for formatting issues in the source

line 90 is way too long (91 characters)
mingw-w64-i686-winpthreads @ 7.0.0formatting

Look for formatting issues in the source

line 90 is way too long (91 characters)
mingw-w64-i686 @ 7.0.0formatting

Look for formatting issues in the source

line 90 is way too long (91 characters)
cfitsio @ 3.47description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 197
mia @ 2.4.6inputs-should-be-native

Identify inputs that should be native inputs

'doxygen' should probably be a native input
kdelibs4support @ 5.63.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
kpackage @ 5.63.0formatting

Look for formatting issues in the source

line 1890 is way too long (106 characters)
extra-cmake-modules @ 5.63.0formatting

Look for formatting issues in the source

line 108 is way too long (91 characters)
kimageformats @ 5.63.0formatting

Look for formatting issues in the source

line 1753 is way too long (103 characters)
opencv @ 3.4.3formatting

Look for formatting issues in the source

line 283 is way too long (132 characters)
kio @ 5.63.0formatting

Look for formatting issues in the source

line 2723 is way too long (113 characters)
kdbusaddons @ 5.63.0formatting

Look for formatting issues in the source

line 643 is way too long (107 characters)
kcmutils @ 5.63.0formatting

Look for formatting issues in the source

line 2197 is way too long (113 characters)
dico @ 2.9inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
dsfmt @ 2.2.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-sphinxcontrib-programoutput @ 0.15inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' 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
python-sphinx-repoze-autointerface @ 0.8inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' 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-sphinx-rtd-theme @ 0.2.4inputs-should-be-native

Identify inputs that should be native inputs

'python-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
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-sphinx-copybutton @ 0.2.6inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' 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
python-breathe @ 4.13.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-breathe @ 4.13.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
python2-pytest-django @ 3.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
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
mate @ 1.24.0inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
python-pytest-django @ 3.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' 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
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-guzzle-sphinx-theme @ 0.7.11inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
kdepim-runtime @ 19.08.3patch-file-names

Validate file names and availability of patches

kdepim-runtime-Fix-missing-link-libraries.patch: file name is too long
libgeotiff @ 1.5.1patch-file-names

Validate file names and availability of patches

libgeotiff-adapt-test-script-for-proj-6.2.patch: file name is too long
mongodb @ 3.4.10source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
mongodb @ 3.4.10patch-file-names

Validate file names and availability of patches

mongodb-support-unknown-linux-distributions.patch: file name is too long
mongodb @ 3.4.10formatting

Look for formatting issues in the source

line 582 is way too long (99 characters)
ocaml-qcheck @ 0.12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 52, 156
ocamlify @ 0.0.1formatting

Look for formatting issues in the source

line 2251 is way too long (98 characters)
sdsl-lite @ 2.1.1patch-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 226 is way too long (145 characters)
rdmd @ 2.077.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ldc @ 0.17.4formatting

Look for formatting issues in the source

line 137 is way too long (98 characters)
ldc @ 1.10.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
tuxmath @ 2.0.3description

Validate package descriptions

description should start with an upper-case letter or digit
childsplay @ 3.4formatting

Look for formatting issues in the source

line 482 is way too long (92 characters)
omnitux @ 1.2.1formatting

Look for formatting issues in the source

line 573 is way too long (99 characters)
elixir @ 1.10.3formatting

Look for formatting issues in the source

line 75 is way too long (97 characters)
elixir @ 1.10.3formatting

Look for formatting issues in the source

line 76 is way too long (99 characters)
mailutils @ 3.9inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
r-shiny @ 1.4.0.2formatting

Look for formatting issues in the source

line 937 is way too long (92 characters)
r-hsmmsinglecell @ 1.2.0formatting

Look for formatting issues in the source

line 1010 is way too long (95 characters)
r-biosigner @ 1.14.4description

Validate package descriptions

use @code or similar ornament instead of quotes
r-rgadem @ 2.34.1description

Validate package descriptions

description should start with an upper-case letter or digit
r-mixomics @ 6.10.9description

Validate package descriptions

description should start with an upper-case letter or digit
r-bioassayr @ 1.24.0description

Validate package descriptions

description should start with an upper-case letter or digit
r-iclusterplus @ 1.22.0description

Validate package descriptions

description should start with an upper-case letter or digit
r-yapsa @ 1.12.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 93, 96
r-genomicinteractions @ 1.20.3formatting

Look for formatting issues in the source

line 2122 is way too long (92 characters)
r-unifiedwmwqpcr @ 1.22.0formatting

Look for formatting issues in the source

line 6957 is way too long (92 characters)
r-monocle @ 2.14.0formatting

Look for formatting issues in the source

line 2875 is way too long (101 characters)
r-lumi @ 2.38.0formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

'swig' should probably be a native input
lightgbm @ 2.0.12source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-fastlmm @ 0.2.21formatting

Look for formatting issues in the source

line 1050 is way too long (92 characters)
shogun @ 6.1.3formatting

Look for formatting issues in the source

line 518 is way too long (91 characters)
keybinder-3.0 @ 0.3.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' 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
python-hacking @ 1.1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python2-oslo.context @ 2.20.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-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
python-oslo.log @ 3.36.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
python-oslo.context @ 2.20.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
python-openstackdocstheme @ 1.18.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python2-openstackdocstheme @ 1.18.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
awesome @ 4.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' 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
python2-oslotest @ 3.4.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-mock' should probably be a native input
python-oslotest @ 3.4.0inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-stevedore @ 1.28.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
python2-hacking @ 1.1.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-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-tempest-lib @ 1.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
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
python2-mox3 @ 0.24.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
stumpwm-with-slynk @ 19.11formatting

Look for formatting issues in the source

line 1649 is way too long (94 characters)
pan @ 0.146description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
deutex @ 5.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 60
mesa-headers @ 19.3.4patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gtklick @ 0.6.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 151 is way too long (92 characters)
python-pyportmidi @ 217patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
powertabeditor @ 2.0.0-alpha10formatting

Look for formatting issues in the source

line 1328 is way too long (94 characters)
solfege @ 3.22.2formatting

Look for formatting issues in the source

line 1230 is way too long (92 characters)
drumstick @ 1.1.3formatting

Look for formatting issues in the source

line 2121 is way too long (91 characters)
vmpk @ 0.7.2formatting

Look for formatting issues in the source

line 2166 is way too long (91 characters)
python2-pybedtools @ 0.8.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'python2-cython' should probably be a native input
rseqc @ 3.0.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'bison' should probably be a native input
java-picard @ 1.113formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3985 is way too long (117 characters)
blasr-libcpp @ 5.3.3formatting

Look for formatting issues in the source

line 587 is way too long (95 characters)
java-picard @ 2.10.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3927 is way too long (91 characters)
discrover @ 1.6.0formatting

Look for formatting issues in the source

line 2746 is way too long (91 characters)
java-picard @ 2.3.0formatting

Look for formatting issues in the source

line 3838 is way too long (104 characters)
rust-rustc-hash @ 1.1.0description

Validate package descriptions

description should start with an upper-case letter or digit
rust-rustc-tools-util @ 0.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
rust-dav1d-sys @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
rust-winit @ 0.20.0-alpha6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
rust-ctor @ 0.1.13formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
rust-bitstream-io @ 0.8.5formatting

Look for formatting issues in the source

line 1667 is way too long (111 characters)
rust-bitstream-io @ 0.8.5formatting

Look for formatting issues in the source

line 1669 is way too long (111 characters)
rust-gimli @ 0.20.0formatting

Look for formatting issues in the source

line 8238 is way too long (91 characters)
rust-colored @ 1.9.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 27101 is way too long (114 characters)
r-boot @ 1.3-25description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 125, 142
r-dplyr @ 0.8.5description

Validate package descriptions

description should start with an upper-case letter or digit
jucipp @ 1.5.1description

Validate package descriptions

description should start with an upper-case letter or digit
editorconfig-core-c @ 0.12.3formatting

Look for formatting issues in the source

line 699 is way too long (97 characters)
geany @ 1.36formatting

Look for formatting issues in the source

line 852 is way too long (125 characters)
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-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-sqlite @ 0.2-1.c738e66formatting

Look for formatting issues in the source

line 2655 is way too long (130 characters)
cl-string-match @ 0-1.5048480formatting

Look for formatting issues in the source

line 2333 is way too long (96 characters)
sbcl-cl-string-match @ 0-1.5048480formatting

Look for formatting issues in the source

line 2333 is way too long (96 characters)
sbcl-cl-sqlite @ 0.2-1.c738e66formatting

Look for formatting issues in the source

line 2655 is way too long (130 characters)
ecl-cl-string-match @ 0-1.5048480formatting

Look for formatting issues in the source

line 2333 is way too long (96 characters)
audiofile @ 0.3.6patch-file-names

Validate file names and availability of patches

audiofile-Check-the-number-of-coefficients.patch: file name is too long
audiofile @ 0.3.6patch-file-names

Validate file names and availability of patches

audiofile-Fix-overflow-in-MSADPCM-decodeSam.patch: file name is too long
audiofile @ 0.3.6patch-file-names

Validate file names and availability of patches

audiofile-Fix-multiply-overflow-sfconvert.patch: file name is too long
audiofile @ 0.3.6patch-file-names

Validate file names and availability of patches

audiofile-signature-of-multiplyCheckOverflow.patch: file name is too long
audiofile @ 0.3.6patch-file-names

Validate file names and availability of patches

audiofile-division-by-zero-BlockCodec-runPull.patch: file name is too long
audacity @ 2.3.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 258, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 260, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 263, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 264, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 273, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 274, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 275, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 276, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 277, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 278, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 279, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 281, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 282, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 283, column 0
icecat @ 68.8.0-guix0-preview1formatting

Look for formatting issues in the source

line 862 is way too long (102 characters)
icecat @ 68.8.0-guix0-preview1formatting

Look for formatting issues in the source

trailing white space on line 865
icecat @ 68.8.0-guix0-preview1formatting

Look for formatting issues in the source

trailing white space on line 871
icecat @ 68.8.0-guix0-preview1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
icecat @ 68.8.0-guix0-preview1formatting

Look for formatting issues in the source

line 955 is way too long (139 characters)
icecat @ 68.8.0-guix0-preview1formatting

Look for formatting issues in the source

line 960 is way too long (95 characters)
icecat @ 68.8.0-guix0-preview1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
icecat @ 68.8.0-guix0-preview1formatting

Look for formatting issues in the source

line 1004 is way too long (94 characters)
icecat @ 68.8.0-guix0-preview1formatting

Look for formatting issues in the source

line 1006 is way too long (95 characters)
icecat @ 68.8.0-guix0-preview1formatting

Look for formatting issues in the source

line 1019 is way too long (98 characters)
ghc-regex-tdfa @ 1.2.3.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ghc-unsafe @ 0.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-llvm-hs-pure @ 9.0.0description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-tasty-expected-failure @ 0.11.1.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 185
ghc-doclayout @ 0.3description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-gtk2hs-buildtools @ 0.13.5.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 95, 367
ghc-fsnotify @ 0.3.0.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 81
ghc-hsyaml @ 0.1.2.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-inline-c @ 0.7.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-th-reify-many @ 0.1.9description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-rio @ 0.1.12.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-llvm-hs @ 9.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-operational @ 0.2.3.5description

Validate package descriptions

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

Look for formatting issues in the source

line 1401 is way too long (91 characters)
ghc-th-orphans @ 0.13.9formatting

Look for formatting issues in the source

line 12037 is way too long (92 characters)
ghc-xdg-basedir @ 0.2.2formatting

Look for formatting issues in the source

line 13609 is way too long (93 characters)
ghc-base-unicode-symbols @ 0.2.3formatting

Look for formatting issues in the source

line 932 is way too long (101 characters)
ghc-system-filepath @ 0.4.14formatting

Look for formatting issues in the source

line 11605 is way too long (250 characters)
ghc-vector @ 0.12.0.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
pjproject @ 2.10formatting

Look for formatting issues in the source

line 789 is way too long (103 characters)
perl-class-load @ 0.25description

Validate package descriptions

use @code or similar ornament instead of quotes
python-asn1crypto @ 0.24.0description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 78
texlive-fonts-iwona @ 0.995bdescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 42
python2-cryptography @ 2.7description

Validate package descriptions

description should start with an upper-case letter or digit
guile-wiredtiger @ 0.7.0description

Validate package descriptions

use @code or similar ornament instead of quotes
python-pytest-subtesthack @ 0.1.1description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
iml @ 1.0.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 798
python-cryptography @ 2.7description

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-lm @ 51265description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
python-fpylll @ 0.4.1description

Validate package descriptions

description should start with an upper-case letter or digit
python2-asn1crypto @ 0.24.0description

Validate package descriptions

description should start with an upper-case letter or digit
libjxr @ 1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
python2-pytest-subtesthack @ 0.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 106
c-blosc @ 1.18.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
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-nose2 @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest-cov' should probably be a native input
python-pytest-mock @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-timeout @ 1.3.4inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
libtool @ 2.4.6inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
python-testtools @ 2.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python2-pytest-mock @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-pytest-cache @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
gdb @ 8.2.1inputs-should-be-native

Identify inputs that should be native inputs

'dejagnu' should probably be a native input
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
python-pytest-subtesthack @ 0.1.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-codecov @ 2.0.15inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python2-testtools @ 2.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
slurp @ 1.2.0inputs-should-be-native

Identify inputs that should be native inputs

'scdoc' should probably be a native input
python2-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python2-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
python-fixtures @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-pytest-forked @ 1.1.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python2-fixtures @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
python2-pytest-xdist @ 1.25.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python-pytest-cache @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-cov-core @ 1.15.0inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-pytest-xprocess @ 0.9.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python2-cov-core @ 1.15.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
libmypaint @ 1.5.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile2.2-mailutils @ 3.9inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
python-testscenarios @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python2-testscenarios @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
mig @ 1.8inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
python-fpylll @ 0.4.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python2-pytest-subtesthack @ 0.1.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python-testresources @ 2.0.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python2-testresources @ 2.0.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
389-ds-base @ 1.4.0.21inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-xdist @ 1.25.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
flatbuffers @ 1.10.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
texlive-latex-hyperref @ 6.84a2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
asciidoc @ 8.6.10source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-usb4java @ 1.2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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'
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'
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'
gcc-objc @ 8.4.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gnutls-dane @ 3.6.12patch-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
libimobiledevice @ 1.2.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
clang-runtime @ 3.5.2patch-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
guile-static-stripped @ 2.0.14patch-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

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
ghostscript-with-cups @ 9.52patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-minimal @ 2.7.17patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
khal @ 0.10.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mercurial @ 5.3.1patch-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
msopenh264 @ 1.2.1patch-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++ @ 5.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-pycrypto @ 2.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-axolotl @ 0.1.39patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python2-testtools @ 2.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-testtools-bootstrap @ 2.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xorg-server-xwayland @ 1.20.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-pyfakefs @ 3.7.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.0-gnutls @ 3.6.12patch-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
readline @ 7.0.5patch-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
python2-testtools-bootstrap @ 2.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-unittest2 @ 1.1.0patch-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
xorg-server @ 1.20.7patch-file-names

Validate file names and availability of patches

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

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
libgccjit @ 9.3.0patch-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
python-minimal @ 3.8.2patch-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
libstdc++-doc @ 9.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile-static-stripped-tarball @ 2.0.14patch-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 @ 6.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
texlive-bin @ 20190410patch-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
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
ghostscript-with-x @ 9.52patch-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
guile2.2-gnutls @ 3.6.12patch-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
icu4c-build-root @ 66.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-gst @ 1.16.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
emacs-cmake-mode @ 3.16.5patch-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
mariadb @ 10.1.44formatting

Look for formatting issues in the source

line 805 is way too long (92 characters)
mariadb @ 10.1.44formatting

Look for formatting issues in the source

line 806 is way too long (91 characters)
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)
texlive-latex-l3packages @ 51265formatting

Look for formatting issues in the source

line 2958 is way too long (91 characters)
texlive-latex-l3packages @ 51265formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
bazaar @ 2.7.0formatting

Look for formatting issues in the source

line 142 is way too long (93 characters)
symmetrica @ 2.0formatting

Look for formatting issues in the source

line 1377 is way too long (100 characters)
gmp @ 6.2.0formatting

Look for formatting issues in the source

line 81 is way too long (96 characters)
eigen @ 3.3.7formatting

Look for formatting issues in the source

tabulation on line 982, column 0
khal @ 0.10.1formatting

Look for formatting issues in the source

line 195 is way too long (113 characters)
lyx @ 2.3.3formatting

Look for formatting issues in the source

line 6142 is way too long (101 characters)
android-libutils @ 7.1.2_r36formatting

Look for formatting issues in the source

line 630 is way too long (114 characters)
texlive-latex-pgf @ 51265formatting

Look for formatting issues in the source

line 6491 is way too long (98 characters)
mesa @ 19.3.4formatting

Look for formatting issues in the source

line 297 is way too long (120 characters)
gap @ 4.10.2formatting

Look for formatting issues in the source

trailing white space on line 1197
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 336, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 337, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 338, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 339, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 340, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 341, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 342, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 343, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 344, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 345, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 346, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 347, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 348, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 349, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 350, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 351, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 352, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 353, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 354, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 365, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 366, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 378, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 379, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 380, column 0
guile-sdl @ 0.5.2formatting

Look for formatting issues in the source

line 607 is way too long (111 characters)
icedove @ 68.8.0formatting

Look for formatting issues in the source

line 1167 is way too long (98 characters)
icedove @ 68.8.0formatting

Look for formatting issues in the source

line 1235 is way too long (93 characters)
icedove @ 68.8.0formatting

Look for formatting issues in the source

line 1328 is way too long (105 characters)
icedove @ 68.8.0formatting

Look for formatting issues in the source

line 1330 is way too long (102 characters)
python2 @ 2.7.17formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 285 is way too long (98 characters)
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

line 367 is way too long (107 characters)
giac @ 1.5.0-87formatting

Look for formatting issues in the source

line 359 is way too long (95 characters)
texlive-hyph-utf8 @ 51265formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2125 is way too long (95 characters)
zita-resampler @ 1.3.0formatting

Look for formatting issues in the source

line 3233 is way too long (93 characters)
git-crypt @ 0.6.0formatting

Look for formatting issues in the source

line 746 is way too long (91 characters)
texlive-amsfonts @ 51265formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1140 is way too long (91 characters)
python-llvmlite @ 0.30.0formatting

Look for formatting issues in the source

line 862 is way too long (92 characters)
vamp @ 2.6formatting

Look for formatting issues in the source

line 2730 is way too long (94 characters)
arm-trusted-firmware-rk3328 @ 2.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
rust @ 1.26.2formatting

Look for formatting issues in the source

line 778 is way too long (94 characters)
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 521 is way too long (92 characters)
xf86-video-intel @ 2.99.917-15.f66d395formatting

Look for formatting issues in the source

line 3025 is way too long (91 characters)
rust @ 1.25.0formatting

Look for formatting issues in the source

line 742 is way too long (91 characters)
help2man @ 1.47.13formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libical @ 3.0.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 688 is way too long (105 characters)
texlive-ruhyphen @ 51265formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2304 is way too long (93 characters)
libsecp256k1 @ 20191213-1.d644ddaformatting

Look for formatting issues in the source

line 936 is way too long (106 characters)
linux-pam @ 1.3.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
texlive-latex-base @ 51265formatting

Look for formatting issues in the source

tabulation on line 2412, column 22
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 496, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 497, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 498, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 499, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 500, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 501, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 502, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 503, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 504, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 506, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 507, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 508, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 509, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 510, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 512, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 513, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 514, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 515, column 0
libjxr @ 1.1formatting

Look for formatting issues in the source

line 487 is way too long (95 characters)
xproto @ 7.0.31formatting

Look for formatting issues in the source

line 4989 is way too long (91 characters)
python @ 3.8.2formatting

Look for formatting issues in the source

line 432 is way too long (93 characters)
go-github.com-smartystreets-goconvey @ 1.6.3formatting

Look for formatting issues in the source

line 514 is way too long (91 characters)
libsignal-protocol-c @ 2.3.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
abseil-cpp @ 20200225.1formatting

Look for formatting issues in the source

line 477 is way too long (116 characters)
abseil-cpp @ 20200225.1formatting

Look for formatting issues in the source

line 478 is way too long (144 characters)
mdadm-static @ 4.1description

Validate package descriptions

description should start with an upper-case letter or digit
pflask @ 0.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ddate @ 0.2.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
util-linux-with-udev @ 2.35.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
wireless-tools @ 30.pre9formatting

Look for formatting issues in the source

line 3284 is way too long (104 characters)
util-linux @ 2.35.1formatting

Look for formatting issues in the source

line 1315 is way too long (91 characters)
crda @ 3.18formatting

Look for formatting issues in the source

line 3394 is way too long (100 characters)
gnome-shell-extension-dash-to-panel @ 26inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
gnome-shell-extension-gsconnect @ 33inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
xygrib @ 1.2.6.1description

Validate package descriptions

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
imposm3 @ 0.6.0-alpha.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
tegola @ 0.7.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
xygrib @ 1.2.6.1formatting

Look for formatting issues in the source

line 1057 is way too long (95 characters)
emacs-next @ 27.0.91-0.c36c5a3patch-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.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-xwidgets @ 26.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-no-x-toolkit @ 26.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-wide-int @ 26.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-no-x @ 26.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-minimal @ 26.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-next @ 27.0.91-0.c36c5a3formatting

Look for formatting issues in the source

line 326 is way too long (134 characters)
guile-readline @ 3.0.2formatting

Look for formatting issues in the source

line 368 is way too long (94 characters)
guile2.2-readline @ 2.2.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 191 is way too long (93 characters)
calibre @ 3.42.0formatting

Look for formatting issues in the source

trailing white space on line 95
calibre @ 3.42.0formatting

Look for formatting issues in the source

line 204 is way too long (93 characters)
tigervnc-server @ 1.10.1-1.920d9c4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
tigervnc-server @ 1.10.1-1.920d9c4formatting

Look for formatting issues in the source

line 175 is way too long (102 characters)
tigervnc-server @ 1.10.1-1.920d9c4formatting

Look for formatting issues in the source

line 178 is way too long (102 characters)
tigervnc-server @ 1.10.1-1.920d9c4formatting

Look for formatting issues in the source

tabulation on line 187, column 0
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
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
guile-for-guile-emacs @ 2.1.2-1.15ca784formatting

Look for formatting issues in the source

line 478 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 482
glibc @ 2.31formatting

Look for formatting issues in the source

line 802 is way too long (98 characters)
conda @ 4.3.16formatting

Look for formatting issues in the source

line 816 is way too long (94 characters)
wxwidgets-gtk2 @ 3.0.5.1description

Validate package descriptions

description should start with an upper-case letter or digit
i3-wm @ 4.18.1description

Validate package descriptions

description should start with an upper-case letter or digit
openexr @ 2.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ctl @ 1.5.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
julia @ 1.4.1formatting

Look for formatting issues in the source

line 309 is way too long (107 characters)
julia @ 1.4.1formatting

Look for formatting issues in the source

line 311 is way too long (106 characters)
r-diagram @ 1.6.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 336
r-fda @ 5.1.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 92, 113
r-hapassoc @ 1.2-8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 139
r-cmprsk @ 2.2-9description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 242
python-rpy2 @ 3.0.4-1.19868a8description

Validate package descriptions

description should start with an upper-case letter or digit
r-dorng @ 1.8.2description

Validate package descriptions

use @code or similar ornament instead of quotes
r-tidyr @ 1.0.3description

Validate package descriptions

description should start with an upper-case letter or digit
r-topicmodels @ 0.2-11description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 151
r-minqa @ 1.2.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 133, 136, 139
r-sapa @ 2.0-2description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 173, 176
r-wmtsa @ 2.0-3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 105, 128
r-rstan @ 2.19.3description

Validate package descriptions

use @code or similar ornament instead of quotes
r-iheatmapr @ 0.4.12description

Validate package descriptions

description should start with an upper-case letter or digit
r-circular @ 0.4-93description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 98, 123
r-bootstrap @ 2019.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 92, 105
r-xyz @ 0.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 232, 243, 262
r-arm @ 1.11-1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 46, 60
r-oai @ 0.3.0description

Validate package descriptions

use @code or similar ornament instead of quotes
r-systemfonts @ 0.2.1description

Validate package descriptions

use @code or similar ornament instead of quotes
r-colourpicker @ 1.0formatting

Look for formatting issues in the source

line 12442 is way too long (94 characters)
r-squarem @ 2020.2formatting

Look for formatting issues in the source

line 2808 is way too long (91 characters)
r-haplo-stats @ 1.7.9formatting

Look for formatting issues in the source

line 13703 is way too long (103 characters)
r-abps @ 0.3formatting

Look for formatting issues in the source

line 7815 is way too long (93 characters)
r-flexdashboard @ 0.5.1.1formatting

Look for formatting issues in the source

line 14942 is way too long (96 characters)
r-flexdashboard @ 0.5.1.1formatting

Look for formatting issues in the source

line 14956 is way too long (96 characters)
r-flexdashboard @ 0.5.1.1formatting

Look for formatting issues in the source

line 14963 is way too long (117 characters)
r-flexdashboard @ 0.5.1.1formatting

Look for formatting issues in the source

line 14970 is way too long (100 characters)
r-gamlss-dist @ 5.1-6formatting

Look for formatting issues in the source

line 12336 is way too long (91 characters)
glusterfs @ 7.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
dmraid @ 1.0.0.rc16-3formatting

Look for formatting issues in the source

line 756 is way too long (91 characters)
libnfs @ 3.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 471
unbound @ 1.10.0formatting

Look for formatting issues in the source

trailing white space on line 507
ruby-iruby @ 0.3formatting

Look for formatting issues in the source

line 477 is way too long (112 characters)
electron-cash @ 4.0.14inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
electron-cash @ 4.0.14formatting

Look for formatting issues in the source

line 528 is way too long (116 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
qtcharts @ 5.12.7description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 244
qtwebglplugin @ 5.12.7description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 107, 250
python2-pyqt @ 5.12.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
qwt @ 6.1.4inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
python2-pyqt @ 5.12.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-pyqt-without-qtwebkit @ 5.12.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
qtmultimedia @ 5.12.7formatting

Look for formatting issues in the source

line 925 is way too long (96 characters)
qtsensors @ 5.12.7formatting

Look for formatting issues in the source

line 882 is way too long (97 characters)
python-pyqt @ 5.12.3formatting

Look for formatting issues in the source

line 1998 is way too long (105 characters)
qtbase @ 5.12.7formatting

Look for formatting issues in the source

line 451 is way too long (96 characters)
qtbase @ 5.12.7formatting

Look for formatting issues in the source

line 575 is way too long (99 characters)
qtbase @ 5.12.7formatting

Look for formatting issues in the source

line 577 is way too long (105 characters)
qtbase @ 5.12.7formatting

Look for formatting issues in the source

line 580 is way too long (117 characters)
qtbase @ 5.12.7formatting

Look for formatting issues in the source

line 583 is way too long (97 characters)
qtbase @ 5.12.7formatting

Look for formatting issues in the source

line 588 is way too long (94 characters)
qtbase @ 5.12.7formatting

Look for formatting issues in the source

line 590 is way too long (94 characters)
qtserialport @ 5.12.7formatting

Look for formatting issues in the source

line 1025 is way too long (115 characters)
libblockdev @ 2.23formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
gdb-arm-none-eabi @ 9.1inputs-should-be-native

Identify inputs that should be native inputs

'dejagnu' should probably be a native input
hackrf @ 2018.01.1-0.43e6f99description

Validate package descriptions

use @code or similar ornament instead of quotes
rtl-sdr @ 0.6.0description

Validate package descriptions

use @code or similar ornament instead of quotes
libvirt-glib @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libosinfo @ 1.7.1formatting

Look for formatting issues in the source

line 395 is way too long (106 characters)
qemu @ 5.0.0formatting

Look for formatting issues in the source

line 131 is way too long (97 characters)
xfce4-volumed-pulse @ 0.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
tumbler @ 0.2.8formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
xfce4-clipman-plugin @ 1.6.1formatting

Look for formatting issues in the source

line 407 is way too long (91 characters)
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
python2-pygobject @ 2.28.7inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
template-glib @ 3.32.0inputs-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
python2-pygobject @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
telepathy-glib @ 0.24.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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
python2-pygobject @ 2.28.7patch-file-names

Validate file names and availability of patches

python2-pygobject-2-gi-info-type-error-domain.patch: file name is too long
localed @ 241formatting

Look for formatting issues in the source

line 533 is way too long (96 characters)
appstream-glib @ 0.7.17formatting

Look for formatting issues in the source

line 951 is way too long (93 characters)
telepathy-glib @ 0.24.1formatting

Look for formatting issues in the source

line 829 is way too long (92 characters)
python2-pygobject @ 3.34.0formatting

Look for formatting issues in the source

line 756 is way too long (95 characters)
php @ 7.4.6formatting

Look for formatting issues in the source

line 188 is way too long (93 characters)
php @ 7.4.6formatting

Look for formatting issues in the source

line 189 is way too long (93 characters)
php @ 7.4.6formatting

Look for formatting issues in the source

line 197 is way too long (91 characters)
php @ 7.4.6formatting

Look for formatting issues in the source

line 205 is way too long (93 characters)
php @ 7.4.6formatting

Look for formatting issues in the source

line 224 is way too long (92 characters)
php @ 7.4.6formatting

Look for formatting issues in the source

line 225 is way too long (96 characters)
php @ 7.4.6formatting

Look for formatting issues in the source

line 230 is way too long (96 characters)
php @ 7.4.6formatting

Look for formatting issues in the source

line 272 is way too long (91 characters)
php @ 7.4.6formatting

Look for formatting issues in the source

line 285 is way too long (92 characters)
libringclient @ 20200401.1.6f090deinputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
libringclient @ 20200401.1.6f090deformatting

Look for formatting issues in the source

line 539 is way too long (105 characters)
pjproject-jami @ 2.10formatting

Look for formatting issues in the source

line 186 is way too long (103 characters)
jami @ 20200401.1.6f090deformatting

Look for formatting issues in the source

line 573 is way too long (92 characters)
grfcodec @ 6.0.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 100
geda-gaf @ 1.10.0inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
lepton-eda @ 1.9.9-20191003inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
librecad @ 2.1.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

line 213 is way too long (106 characters)
minizip @ 1.2.11formatting

Look for formatting issues in the source

line 153 is way too long (115 characters)
zathura-djvu @ 0.2.9formatting

Look for formatting issues in the source

line 471 is way too long (93 characters)
zathura-pdf-poppler @ 0.3.0formatting

Look for formatting issues in the source

line 551 is way too long (107 characters)
sdl-image @ 1.2.12formatting

Look for formatting issues in the source

line 223 is way too long (91 characters)
sdl-mixer @ 1.2.12formatting

Look for formatting issues in the source

line 260 is way too long (92 characters)
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 617 is way too long (99 characters)
debops @ 1.1.0patch-file-names

Validate file names and availability of patches

debops-constants-for-external-program-names.patch: file name is too long
ocaml4.07-piqi @ 0.7.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
fc-host-tools @ 11formatting

Look for formatting issues in the source

line 1207 is way too long (122 characters)
librdkafka @ 0.9.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2310, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2311, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2312, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2313, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2314, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2315, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2316, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2317, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2318, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2323, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2324, column 0
java-openjfx-base @ 8.202formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2551 is way too long (99 characters)
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2268, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2269, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2270, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2271, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2272, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2273, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2274, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2275, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2276, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2277, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2278, column 0
ocaml4.07-sexplib @ 0.11.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
catdoc @ 0.95description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 157
wine-staging @ 5.8inputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
wine64-staging @ 5.8inputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
java-rsyntaxtextarea @ 2.6.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
wine-staging @ 5.8formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
wine64-staging @ 5.8formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ecryptfs-utils @ 111description

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-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
perftest @ 4.4-0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
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-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-fasterxml-jackson-core @ 2.9.4description

Validate package descriptions

description should not be empty
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-native-access-platform @ 4.5.1description

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
f2fs-fsck-static @ 1.13.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 91
java-jsch-agentproxy-core @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
java-picocli @ 4.3.2source-file-name

Validate file names of sources

the source file name should contain the package name
java-native-access @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-archiver @ 4.1.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-powermock-core @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-woodstox-core @ 5.0.3source-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-fasterxml-jackson-dataformat-xml @ 2.9.4source-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-lmax-disruptor @ 3.3.7source-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-logback-classic @ 1.2.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jcommander @ 1.71source-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-jsch-agentproxy-usocket-jna @ 0.0.8source-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-jansi-native @ 1.7source-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-stringtemplate @ 4.0.8source-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-xerial-core @ 2.1source-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-logback-core @ 1.2.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-jline @ 2.14.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-javassist @ 3.21.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-javax-inject @ tck-1source-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-hdrhistogram @ 2.1.9source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-assertj @ 3.8.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-fasterxml-jackson-annotations @ 2.9.4source-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-hawtjni @ 1.15source-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-fasterxml-jackson-modules-base-mrbean @ 2.9.4source-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-guice @ 4.1source-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-ops4j-base-monitors @ 1.5.0source-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-jansi @ 1.16source-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-jboss-el-api-spec @ 3.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-fasterxml-jackson-databind @ 2.9.4source-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-bsh @ 2.0b6source-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-mvel2 @ 2.3.1source-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-powermock-reflect @ 1.7.3source-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-stax2-api @ 4.0.0source-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-jboss-jms-api-spec @ 2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-aqute-bnd-annotation @ 3.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-datanucleus-javax-persistence @ 2.2.0source-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-xmlunit-matchers @ 2.5.1source-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-native-access-platform @ 4.5.1source-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-cdi-api @ 2.0source-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-guice-servlet @ 4.1source-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-fasterxml-jackson-modules-base-jaxb @ 2.9.4source-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-jsch-agentproxy-core @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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-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-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-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-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-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-native-access @ 4.5.1formatting

Look for formatting issues in the source

line 10990 is way too long (91 characters)
java-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8819 is way too long (98 characters)
java-logback-classic @ 1.2.3formatting

Look for formatting issues in the source

line 11531 is way too long (102 characters)
java-jnacl @ 0.1.0-2.094e819formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9384 is way too long (92 characters)
josm @ 15937formatting

Look for formatting issues in the source

tabulation on line 1180, column 0
josm @ 15937formatting

Look for formatting issues in the source

line 1220 is way too long (91 characters)
java-testng @ 6.14.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10066 is way too long (92 characters)
java-commons-jxpath @ 1.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8396 is way too long (100 characters)
perftest @ 4.4-0.4formatting

Look for formatting issues in the source

line 5177 is way too long (98 characters)
java-eclipse-jdt-core @ 3.16.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10119 is way too long (122 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

line 10811 is way too long (92 characters)
java-apache-ivy @ 2.4.0formatting

Look for formatting issues in the source

line 11211 is way too long (101 characters)
java-joda-time @ 2.9.9formatting

Look for formatting issues in the source

line 10482 is way too long (92 characters)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

line 5092 is way too long (91 characters)
java-hawtjni @ 1.15formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8539 is way too long (96 characters)
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

line 8254 is way too long (91 characters)
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6504, column 20
java-plexus-sec-dispatcher @ 1.4formatting

Look for formatting issues in the source

line 4130 is way too long (107 characters)
java-jgit @ 4.2.0.201601211800-rformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8491 is way too long (93 characters)
java-sisu-build-api @ 0.0.7formatting

Look for formatting issues in the source

line 4250 is way too long (98 characters)
racket-minimal @ 7.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
next @ 1.5.0formatting

Look for formatting issues in the source

line 651 is way too long (94 characters)
next @ 1.5.0formatting

Look for formatting issues in the source

line 652 is way too long (106 characters)
lpsolve @ 5.5.2.5description

Validate package descriptions

description should start with an upper-case letter or digit
octave-cli @ 5.2.0inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
octave @ 5.2.0inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
opencascade-occt @ 7.3.0p3inputs-should-be-native

Identify inputs that should be native inputs

'doxygen' should probably be a native input
arpack-ng @ 3.3.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
hdf5-parallel-openmpi @ 1.8.21patch-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
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
pt-scotch32 @ 6.0.6patch-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
mumps-openmpi @ 5.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
pt-scotch @ 6.0.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
netcdf-parallel-openmpi @ 4.4.1.1patch-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
scotch32 @ 6.0.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
pt-scotch32 @ 6.0.6formatting

Look for formatting issues in the source

tabulation on line 2949, column 0
ruby-asciimath @ 1.0.4formatting

Look for formatting issues in the source

line 2591 is way too long (100 characters)
hdf-java @ 3.3.2formatting

Look for formatting issues in the source

line 1162 is way too long (92 characters)
superlu-dist @ 6.2.0formatting

Look for formatting issues in the source

line 2731 is way too long (92 characters)
superlu-dist @ 6.2.0formatting

Look for formatting issues in the source

tabulation on line 2751, column 0
superlu-dist @ 6.2.0formatting

Look for formatting issues in the source

tabulation on line 2752, column 0
mumps-openmpi @ 5.2.1formatting

Look for formatting issues in the source

tabulation on line 2562, column 0
scalapack @ 2.0.2formatting

Look for formatting issues in the source

tabulation on line 788, column 0
sundials-openmpi @ 3.1.1formatting

Look for formatting issues in the source

tabulation on line 4701, column 0
pt-scotch @ 6.0.6formatting

Look for formatting issues in the source

tabulation on line 2927, column 0
hdf4 @ 4.2.14formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
hypre-openmpi @ 2.15.1formatting

Look for formatting issues in the source

tabulation on line 4182, column 0
p4est @ 2.0formatting

Look for formatting issues in the source

tabulation on line 3013, column 0
mumps @ 5.2.1formatting

Look for formatting issues in the source

line 2476 is way too long (94 characters)
petsc @ 3.11.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
slepc-openmpi @ 3.11.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2363 is way too long (92 characters)
hplip-minimal @ 3.20.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
warzone2100 @ 3.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 76
sky @ 1.2description

Validate package descriptions

use @code or similar ornament instead of quotes
mrrescue @ 1.02edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 2
chroma @ 1.17description

Validate package descriptions

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

Identify inputs that should be native inputs

'swig' should probably be a native input
crawl-tiles @ 0.24.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
warzone2100 @ 3.2.3formatting

Look for formatting issues in the source

line 3973 is way too long (107 characters)
freeorion @ 0.4.9formatting

Look for formatting issues in the source

line 8566 is way too long (92 characters)
ri-li @ 2.0.1formatting

Look for formatting issues in the source

line 8481 is way too long (100 characters)
queen @ 1.1formatting

Look for formatting issues in the source

line 8281 is way too long (184 characters)
queen @ 1.1formatting

Look for formatting issues in the source

line 8282 is way too long (205 characters)
sky @ 1.2formatting

Look for formatting issues in the source

line 8385 is way too long (118 characters)
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5898, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5899, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5902, column 0
lure-fr @ 1.1formatting

Look for formatting issues in the source

line 8182 is way too long (93 characters)
lure-de @ 1.1formatting

Look for formatting issues in the source

line 8182 is way too long (93 characters)
queen-it @ 1.0formatting

Look for formatting issues in the source

line 8281 is way too long (184 characters)
queen-it @ 1.0formatting

Look for formatting issues in the source

line 8282 is way too long (205 characters)
queen-de @ 1.0formatting

Look for formatting issues in the source

line 8281 is way too long (184 characters)
queen-de @ 1.0formatting

Look for formatting issues in the source

line 8282 is way too long (205 characters)
lure @ 1.1formatting

Look for formatting issues in the source

line 8182 is way too long (93 characters)
lure-it @ 1.1formatting

Look for formatting issues in the source

line 8182 is way too long (93 characters)
lure-es @ 1.1formatting

Look for formatting issues in the source

line 8182 is way too long (93 characters)
drascula @ 1.0formatting

Look for formatting issues in the source

line 8079 is way too long (93 characters)
drascula @ 1.0formatting

Look for formatting issues in the source

line 8083 is way too long (93 characters)
btanks @ 0.9.8083formatting

Look for formatting issues in the source

line 7141 is way too long (99 characters)
btanks @ 0.9.8083formatting

Look for formatting issues in the source

tabulation on line 7166, column 18
btanks @ 0.9.8083formatting

Look for formatting issues in the source

tabulation on line 7167, column 17
einstein @ 2.0formatting

Look for formatting issues in the source

line 3586 is way too long (96 characters)
queen-fr @ 1.0formatting

Look for formatting issues in the source

line 8281 is way too long (184 characters)
queen-fr @ 1.0formatting

Look for formatting issues in the source

line 8282 is way too long (205 characters)
python2-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1083 is way too long (94 characters)
r-bseqsc @ 1.0-1.fef3f3edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 395
r-seqlogo @ 1.52.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
samblaster @ 0.1.24description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 263
r-rtracklayer @ 1.46.0description

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'python-cython' should probably be a native input
imp @ 2.6.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-cython' should probably be a native input
multiqc @ 1.5inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-velocyto @ 0.17.17inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
miniasm @ 0.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
dropseq-tools @ 1.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 12728, column 0
ncbi-vdb @ 2.10.6formatting

Look for formatting issues in the source

tabulation on line 5841, column 26
salmon @ 0.13.1formatting

Look for formatting issues in the source

line 12149 is way too long (99 characters)
freebayes @ 1.0.2-1.3ce827dformatting

Look for formatting issues in the source

tabulation on line 15593, column 28
r-rhdf5lib @ 1.8.0formatting

Look for formatting issues in the source

line 10808 is way too long (102 characters)
r-rhdf5lib @ 1.8.0formatting

Look for formatting issues in the source

line 10809 is way too long (104 characters)
bind @ 9.16.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 253
serf @ 1.3.9formatting

Look for formatting issues in the source

line 1648 is way too long (92 characters)
krona-tools @ 2.7formatting

Look for formatting issues in the source

trailing white space on line 995
nginx-accept-language-module @ 0.0.0-1.2f69842formatting

Look for formatting issues in the source

line 511 is way too long (92 characters)
python-html2text @ 2019.8.11description

Validate package descriptions

description should start with an upper-case letter or digit
python2-html2text @ 2019.8.11description

Validate package descriptions

description should start with an upper-case letter or digit
awscli @ 1.18.6inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python2-paste @ 3.0.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-wtforms @ 2.1formatting

Look for formatting issues in the source

line 2978 is way too long (92 characters)
python-wtforms @ 2.1formatting

Look for formatting issues in the source

line 2979 is way too long (100 characters)
python-tornado @ 5.1.1formatting

Look for formatting issues in the source

line 884 is way too long (91 characters)
python2-wtforms @ 2.1formatting

Look for formatting issues in the source

line 2978 is way too long (92 characters)
python2-wtforms @ 2.1formatting

Look for formatting issues in the source

line 2979 is way too long (100 characters)
python-psycopg2 @ 2.8.4description

Validate package descriptions

description should start with an upper-case letter or digit
python2-psycopg2 @ 2.8.4description

Validate package descriptions

description should start with an upper-case letter or digit
apache-arrow @ 0.10.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 84, 235
python-ccm @ 2.1.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 84
python2-ccm @ 2.1.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 84
sqlcipher @ 3.4.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-alembic @ 1.4.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
nototools @ 20170925source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
fntsample @ 5.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
linux-libre-riscv64-generic @ 5.4.42derivation

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
linux-libre @ 5.4.42derivation

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
linux-libre-riscv64-generic @ 5.4.42patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre @ 4.9.224patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-headers @ 5.4.42patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-headers @ 4.4.224patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-headers @ 5.6.14patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm64-generic @ 5.6.14patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-headers @ 4.14.181patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre @ 4.4.224patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-generic @ 5.6.14patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-omap2plus @ 4.14.181patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-generic @ 4.19.124patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre @ 5.4.42patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm64-generic @ 5.4.42patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-headers @ 4.9.224patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-omap2plus @ 4.19.124patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-generic @ 5.4.42patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-headers @ 4.19.124patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
freefall @ 5.4.42patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-omap2plus @ 5.4.42patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre @ 4.19.124patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-generic @ 4.14.181patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
cpupower @ 5.4.42patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
x86-energy-perf-policy @ 5.4.42patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre @ 4.14.181patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perf @ 5.4.42patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-riscv64-generic @ 5.4.42formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre @ 4.9.224formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre-arm64-generic @ 5.6.14formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre @ 4.4.224formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre-arm-generic @ 5.6.14formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre-arm-omap2plus @ 4.14.181formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre-arm-generic @ 4.19.124formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre @ 5.4.42formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre-arm64-generic @ 5.4.42formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre-arm-omap2plus @ 4.19.124formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre-arm-generic @ 5.4.42formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre-arm-omap2plus @ 5.4.42formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre @ 4.19.124formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre-arm-generic @ 4.14.181formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
linux-libre @ 4.14.181formatting

Look for formatting issues in the source

line 758 is way too long (117 characters)
python-flexmock @ 0.10.4description

Validate package descriptions

description should start with an upper-case letter or digit
python2-flexmock @ 0.10.4description

Validate package descriptions

description should start with an upper-case letter or digit
python-pytest-catchlog @ 1.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python2-pytest-capturelog @ 0.7inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-warnings @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python-nose-timer @ 0.7.5inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-pytest-capturelog @ 0.7inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-pytest-warnings @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
gtkspell3 @ 3.0.9inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-pytest-sugar @ 0.9.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python2-coverage-test-runner @ 1.15inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python2-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python2-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-nose' should probably be a native input
python2-nose-timer @ 0.7.5inputs-should-be-native

Identify inputs that should be native inputs

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

Validate file names and availability of patches

file names of patches should start with the package name
gtk+ @ 2.24.32patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gtk+ @ 3.24.14patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
sbcl-md5 @ 2.0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
cl-quri @ 0.1.0-2.b53231cdescription

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
cl-md5 @ 2.0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
cl-circular-streams @ 0.1.0-1.e770baddescription

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ecl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

description should start with an upper-case letter or digit
sbcl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 79
sbcl-quri @ 0.1.0-2.b53231cdescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 68
sbcl-cl-cookie @ 0.9.10-1.cea55aedescription

Validate package descriptions

description should start with an upper-case letter or digit
sbcl-cl-gobject-introspection @ 0.3-0.7b703e2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
cl-gobject-introspection @ 0.3-0.7b703e2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
sbcl-md5 @ 2.0.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
cl-md5 @ 2.0.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
sbcl-graph-json @ 0.0.0-0.78bf9ecpatch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
cl-graph @ 0.0.0-0.78bf9ecpatch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
sbcl-graph-dot @ 0.0.0-0.78bf9ecpatch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ecl-portable-threads @ 2.3-1.c0e61a1formatting

Look for formatting issues in the source

line 3312 is way too long (94 characters)
cl-portable-threads @ 2.3-1.c0e61a1formatting

Look for formatting issues in the source

line 3312 is way too long (94 characters)
sbcl-trivia.trivial @ 0.0.0-2.37698b4formatting

Look for formatting issues in the source

line 6264 is way too long (104 characters)
sbcl-portable-threads @ 2.3-1.c0e61a1formatting

Look for formatting issues in the source

line 3312 is way too long (94 characters)
sbcl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 6038 is way too long (91 characters)
cl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 6038 is way too long (91 characters)
python-libfreenect @ 0.6.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-libfreenect @ 0.6.1source-file-name

Validate file names of sources

the source file name should contain the package name
libfreenect-examples @ 0.6.1source-file-name

Validate file names of sources

the source file name should contain the package name
libfreenect @ 0.6.1source-file-name

Validate file names of sources

the source file name should contain the package name
libfreenect-opencv @ 0.6.1source-file-name

Validate file names of sources

the source file name should contain the package name
perl-libxml @ 0.08description

Validate package descriptions

description should start with an upper-case letter or digit
java-kxml2 @ 2.4.2description

Validate package descriptions

description should start with an upper-case letter or digit
perl-file-readbackwards @ 1.05description

Validate package descriptions

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

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
perl-file-which @ 1.23description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-devel-globaldestruction @ 0.14description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-specio @ 0.38description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 185, 314
perl-extutils-pkgconfig @ 1.16inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
python-pytest-httpbin @ 0.2.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-libxml2 @ 2.9.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
http-parser @ 2.9.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 9113 is way too long (97 characters)
varnish @ 6.4.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 105 is way too long (92 characters)
java-xom @ 127formatting

Look for formatting issues in the source

trailing white space on line 1667
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

line 2017 is way too long (91 characters)
python-clf @ 0.5.7inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-nose' should probably be a native input
java-eclipse-jetty-servlet @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-webapp @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-server @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-xml @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-util @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-servlet @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-http @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-http @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-jmx @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-webapp @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-security @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-server @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-util @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-io @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-xml @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-security @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-io @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-jmx @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
xplanet @ 1.3.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

xplanet-1.3.1-xpUtil-Add2017LeapSecond.cpp.patch: file name is too long
ruby-rb-inotify @ 0.9.10description

Validate package descriptions

description should start with an upper-case letter or digit
ruby-sanitize @ 4.6.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
kodi-wayland @ 18.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-ncurses @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
guile3.0-email @ 0.2.2description

Validate package descriptions

description should start with an upper-case letter or digit
guile3.0-commonmark @ 0.1.2description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 93
guile3.0-mailutils @ 3.9inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
guile3.0-gi @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
bash-minimal @ 5.0.16patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-veyron @ 5.4.42patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-sqlite3 @ 0.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.0-sqlite3 @ 0.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.2-sqlite3 @ 0.1.0patch-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
bash-static @ 5.0.16patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-gdbm-ffi @ 20120209.fa1d5b6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
guile2.2-gdbm-ffi @ 20120209.fa1d5b6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
perl-parent @ 5.30.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.0-gdbm-ffi @ 20120209.fa1d5b6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-gnutls @ 3.6.12patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-readline @ 3.0.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-rsvg @ 2.18.1-0.05c6a2fpatch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
perl-base @ 5.30.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-fibers @ 1.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xdg-user-dirs @ 0.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
telepathy-mission-control @ 5.16.5inputs-should-be-native

Identify inputs that should be native inputs

'gtk-doc' should probably be a native input
libmediaart @ 1.9.4inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
plymouth @ 0.9.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 623 is way too long (91 characters)
syncthing @ 1.5.0formatting

Look for formatting issues in the source

line 98 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 2405 is way too long (93 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-multiformats-go-multiaddr-net @ 1.6.3-0.1cb9a0eformatting

Look for formatting issues in the source

line 2448 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 2449 is way too long (93 characters)
spice-gtk @ 0.37inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
mkvtoolnix @ 37.0.0formatting

Look for formatting issues in the source

line 424 is way too long (96 characters)
python-psutil @ 5.7.0description

Validate package descriptions

description should start with an upper-case letter or digit
python2-psutil @ 5.7.0description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
libchamplain @ 0.12.16inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
gnome @ 3.34.2inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
libpeas @ 1.24.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
system-config-printer @ 1.5.12inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gnome-contacts @ 3.34inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gnome-tweaks @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
yelp-tools @ 3.32.2inputs-should-be-native

Identify inputs that should be native inputs

'itstool' should probably be a native input
libsoup @ 2.70.0formatting

Look for formatting issues in the source

line 3663 is way too long (128 characters)
libsoup @ 2.70.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
gnome-keyring @ 3.34.0formatting

Look for formatting issues in the source

line 1564 is way too long (91 characters)
glade @ 3.22.1formatting

Look for formatting issues in the source

line 2110 is way too long (91 characters)
gdm @ 3.34.1formatting

Look for formatting issues in the source

line 6916 is way too long (103 characters)
upower @ 0.99.11formatting

Look for formatting issues in the source

line 4150 is way too long (110 characters)
xwallpaper @ 0.6.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 72
xcalib @ 0.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
quaternion @ 0.0.9.4einputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
qtox @ 1.16.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
enlightenment-wayland @ 0.24.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-ncurses-with-gpm @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-sjson @ 0.2.1description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-email @ 0.2.2description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.0-commonmark @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
guile-dbd-sqlite3 @ 2.1.6description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-ncurses @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
guile-ncurses-with-gpm @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
guile-stis-parser @ 0-1.6e85d37description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 117
guile2.2-commonmark @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
g-golf @ 1-683.4a4edf2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile2.2-gi @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile-gi @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile2.2-fibers @ 1.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile-dbi @ 2.1.6formatting

Look for formatting issues in the source

line 1292 is way too long (94 characters)
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
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1612 is way too long (137 characters)
wpa-supplicant-minimal @ 2.9description

Validate package descriptions

description should start with an upper-case letter or digit
fakeroot @ 1.24description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 114, 240
ecasound @ 2.9.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471
wpa-supplicant @ 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
procenv @ 0.51source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
jmtpfs @ 0.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
proot-static @ 5.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcompris @ 17.05formatting

Look for formatting issues in the source

line 131 is way too long (96 characters)
patchwork @ 2.1.5formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
xftwidth @ 20170402description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 96, 234
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1553, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1554, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1556, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1557, column 0
rav1e @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'nasm' should probably be a native input
gst-transcoder @ 1.12.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gaupol @ 1.7formatting

Look for formatting issues in the source

line 3766 is way too long (95 characters)
sendmail @ 8.15.2inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
qucs-s @ 0.0.21inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
qucs @ 0.0.19-0.b4f27d9inputs-should-be-native

Identify inputs that should be native inputs

'libtool' should probably be a native input
alot @ 0.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
qucs-s @ 0.0.21source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
freehdl @ 0.0.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
lxde-common @ 0.99.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1694 is way too long (104 characters)
sooperlooper @ 1.7.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 120
python2-discogs-client @ 2.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
python-discogs-client @ 2.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
python-pytest-checkdocs @ 1.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-pytest-vcr @ 1.0.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-coveralls @ 1.11.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-iml @ 0.6.2inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
sorcer @ 1.1.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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 241, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 242, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 243, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 244, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 245, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 246, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 247, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 248, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 249, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 252, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 253, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 255, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 256, column 0
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 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
rosegarden @ 19.12formatting

Look for formatting issues in the source

line 4179 is way too long (94 characters)
rosegarden @ 19.12formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4653, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4654, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4655, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4656, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4658, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4665, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4666, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4667, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4668, column 0
pidentd @ 3.0.19source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
nzbget @ 21.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
restinio @ 0.6.1.1formatting

Look for formatting issues in the source

line 2738 is way too long (105 characters)
restinio @ 0.6.1.1formatting

Look for formatting issues in the source

line 2752 is way too long (95 characters)
diffoscope @ 145formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
restbed @ 4.6-1.6eb385fformatting

Look for formatting issues in the source

line 2713 is way too long (92 characters)
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-libp2p-go-libp2p-peer @ 2.3.8-0.993d742formatting

Look for formatting issues in the source

line 2270 is way too long (93 characters)
go-github-com-mitchellh-go-homedir @ 1.1.0formatting

Look for formatting issues in the source

line 2367 is way too long (93 characters)
go-github-com-gorilla-context @ 0.0.0-0.08b5f42formatting

Look for formatting issues in the source

line 1100 is way too long (164 characters)
go-github-com-davecgh-go-spew @ 0.0.0-0.d8f796aformatting

Look for formatting issues in the source

line 1933 is way too long (129 characters)
go-github-com-libp2p-go-libp2p-metrics @ 2.1.6-0.a10ff6eformatting

Look for formatting issues in the source

line 2326 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 2329 is way too long (93 characters)
emacs-dhall-mode @ 0.1.3-0.ef4d33ddescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 89
emacs-pyvenv @ 1.21description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-vcsh @ 0.4.4description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-cnfonts @ 0.9.1description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-flx @ 0.6.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 220
emacs-nhexl-mode @ 1.4description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-hercules @ 0.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 137
emacs-el-x @ 0.3.1description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-trashed @ 1.9.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 178
emacs-undohist-el @ 0-1.d2239a5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-haskell-mode @ 16.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-gtk-look @ 29formatting

Look for formatting issues in the source

line 17854 is way too long (94 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 386 is way too long (92 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 387 is way too long (96 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 388 is way too long (92 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 390 is way too long (94 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 391 is way too long (91 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 392 is way too long (94 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 393 is way too long (99 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 394 is way too long (106 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 395 is way too long (110 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 396 is way too long (117 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 397 is way too long (98 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 399 is way too long (102 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 401 is way too long (92 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 402 is way too long (116 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 403 is way too long (95 characters)
emacs-exwm @ 0.23formatting

Look for formatting issues in the source

line 10441 is way too long (96 characters)
emacs-dash-docs @ 1.4.0-1.111fd9bformatting

Look for formatting issues in the source

line 20134 is way too long (91 characters)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10782, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10783, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10786, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10787, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10799, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10800, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10801, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10802, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10803, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10804, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10805, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10806, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10807, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10808, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10809, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10810, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10811, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10812, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10813, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10814, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10815, column 0
emacs-mit-scheme-doc @ 20140203formatting

Look for formatting issues in the source

line 4798 is way too long (94 characters)
emacs-lua-mode @ 20191204-1.1f596a9formatting

Look for formatting issues in the source

tabulation on line 8249, column 0
emacs-lua-mode @ 20191204-1.1f596a9formatting

Look for formatting issues in the source

tabulation on line 8252, column 0
u-boot-qemu-riscv64-smode @ 2020.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-vexpress-ca9x4 @ 2020.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-puma-rk3399 @ 2020.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-rockpro64-rk3399 @ 2020.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-nintendo-nes-classic-edition @ 2020.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-firefly-rk3399 @ 2020.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-rock64-rk3328 @ 2020.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-qemu-riscv64-smode @ 2020.04patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
grub-minimal @ 2.04patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 639 is way too long (93 characters)
u-boot-wandboard @ 2020.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 639 is way too long (93 characters)
u-boot-mx6cuboxi @ 2020.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 639 is way too long (93 characters)
u-boot-cubietruck @ 2020.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 639 is way too long (93 characters)
u-boot-pine64-plus @ 2020.04formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
u-boot-vexpress-ca9x4 @ 2020.04formatting

Look for formatting issues in the source

line 639 is way too long (93 characters)
u-boot-sifive-fu540 @ 2020.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 639 is way too long (93 characters)
u-boot-am335x-boneblack @ 2020.04formatting

Look for formatting issues in the source

line 680 is way too long (95 characters)
u-boot-cubieboard @ 2020.04formatting

Look for formatting issues in the source

line 639 is way too long (93 characters)
u-boot-tools @ 2020.04formatting

Look for formatting issues in the source

line 507 is way too long (91 characters)
u-boot-tools @ 2020.04formatting

Look for formatting issues in the source

line 529 is way too long (97 characters)
u-boot-pine64-lts @ 2020.04formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
u-boot-malta @ 2020.04formatting

Look for formatting issues in the source

line 639 is way too long (93 characters)
u-boot-nintendo-nes-classic-edition @ 2020.04formatting

Look for formatting issues in the source

line 639 is way too long (93 characters)
u-boot-pinebook @ 2020.04formatting

Look for formatting issues in the source

line 729 is way too long (127 characters)
python2-dukpy @ 0.3description

Validate package descriptions

description should start with an upper-case letter or digit
python2-pyaml @ 18.11.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-q @ 2.6description

Validate package descriptions

description should start with an upper-case letter or digit
python2-dbus @ 1.2.14description

Validate package descriptions

description should start with an upper-case letter or digit
python-gevent @ 20.5.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-pyquery @ 1.2.17description

Validate package descriptions

description should start with an upper-case letter or digit
python2-q @ 2.6description

Validate package descriptions

description should start with an upper-case letter or digit
python-eliot @ 1.12.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 153
python-apispec @ 0.25.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
python2-argcomplete @ 1.11.1description

Validate package descriptions

description should start with an upper-case letter or digit
python-argcomplete @ 1.11.1description

Validate package descriptions

description should start with an upper-case letter or digit
ptpython2 @ 0.34description

Validate package descriptions

description should start with an upper-case letter or digit
python2-editor @ 1.0.4description

Validate package descriptions

description should start with an upper-case letter or digit
python-jinja2-time @ 0.2.0description

Validate package descriptions

use @code or similar ornament instead of quotes
python2-rst.linker @ 1.11description

Validate package descriptions

description should start with an upper-case letter or digit
python2-dnspython @ 1.16.0description

Validate package descriptions

description should start with an upper-case letter or digit
python2-gevent @ 20.5.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-py3status @ 3.21description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-dnspython @ 1.16.0description

Validate package descriptions

description should start with an upper-case letter or digit
python2-apispec @ 0.25.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
python-pywinrm @ 0.4.1description

Validate package descriptions

description should start with an upper-case letter or digit
python-rst.linker @ 1.11description

Validate package descriptions

description should start with an upper-case letter or digit
python-pyaml @ 18.11.0description

Validate package descriptions

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

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-jsonrpc-server @ 0.3.4inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-jsonrpc-server @ 0.3.4inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python2-pkgconfig @ 1.3.1inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
python-setuptools-scm-git-archive @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-doc8 @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-iocapture @ 0.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-iocapture @ 0.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python2-setuptools-scm-git-archive @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-setuptools-scm' should probably be a native input
lollypop @ 1.2.32inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-pifpaf @ 2.4.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
terminator @ 1.91inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-xopen @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-setuptools-scm' should probably be a native input
python2-m2r @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-docutils' should probably be a native input
python2-botocore @ 1.15.26inputs-should-be-native

Identify inputs that should be native inputs

'python2-docutils' should probably be a native input
python-rst2ansi @ 0.1.5inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-mock' should probably be a native input
python-docusign-esign @ 3.1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
snakemake @ 5.7.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
pelican @ 4.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-restructuredtext-lint @ 1.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-numpydoc @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-pkgconfig @ 1.3.1inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
python-pytest-check-links @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-pytest-check-links @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-get-version @ 2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-get-version @ 2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python-argh @ 0.26.2-1.dcd3253inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-argh @ 0.26.2-1.dcd3253inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-argh @ 0.26.2-1.dcd3253inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python2-matplotlib @ 2.2.4inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-matplotlib @ 3.1.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-legacy-api-wrap @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-legacy-api-wrap @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python-pytest-black @ 0.3.8inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python2-numpydoc @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-jaraco-packaging @ 6.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-jaraco-packaging @ 6.1inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-jaraco-packaging @ 6.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-m2r @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-botocore @ 1.15.26inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-eliot @ 1.12.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-get-version @ 2.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-ipython-cluster-helper @ 0.6.4inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python2-virtualenv @ 20.0.10inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python2-setuptools' should probably not be an input at all
python2-ipython-cluster-helper @ 0.6.4inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python2-setuptools' should probably not be an input at all
python-legacy-api-wrap @ 1.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-jaraco-packaging @ 6.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-virtualenv @ 20.0.10inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
piper @ 0.4source-file-name

Validate file names of sources

the source file name should contain the package name
python2-cairocffi @ 0.9.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-larch @ 1.20151025patch-file-names

Validate file names and availability of patches

python2-larch-coverage-4.0a6-compatibility.patch: file name is too long
python2-pybugz @ 0.6.11patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-argcomplete @ 1.11.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-packaging @ 20.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python2-jedi @ 0.17.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-configobj @ 5.0.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-pep8 @