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
r-boot @ 1.3-24description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 125, 142
ghc-tasty-expected-failure @ 0.11.1.2description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
perl-test-file-contents @ 0.23description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 236
perl-search-xapian @ 1.2.25.2description

Validate package descriptions

use @code or similar ornament instead of quotes
perl6-grammar-debugger @ 1.0.1-1.0375008description

Validate package descriptions

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

Identify inputs that should be native inputs

'bison' should probably be a native input
bison @ 3.4.1inputs-should-be-native

Identify inputs that should be native inputs

'flex' 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
aseba @ 1.6.0-0.3b35de8inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'flex' should probably be a native input
python2-pygobject @ 3.28.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
spice-gtk @ 0.37inputs-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
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
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
ijs @ 9.27patch-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
python2 @ 2.7.16patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
sdsl-lite @ 2.1.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
python2-minimal @ 2.7.16patch-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
readline @ 7.0.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
enlightenment-wayland @ 0.23.1patch-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
python2-cffi @ 1.11.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
avr-binutils @ 2.32patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
icu4c @ 64.2patch-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-settings @ 3.6.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
binutils-static-stripped-tarball @ 2.32patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python-cffi-documentation @ 1.11.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-next @ 3.8.0patch-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
oath-toolkit @ 2.6.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
bash-minimal @ 5.0.7patch-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
telepathy-glib @ 0.24.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
bash @ 5.0.7patch-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-repository-metadata @ 3.6.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
bash-static @ 5.0.7patch-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
ghostscript-with-cups @ 9.27patch-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
idutils @ 4.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2 @ 2.7.16formatting

Look for formatting issues in the source

line 164 is way too long (99 characters)
python2 @ 2.7.16formatting

Look for formatting issues in the source

line 257 is way too long (98 characters)
sdsl-lite @ 2.1.1formatting

Look for formatting issues in the source

line 224 is way too long (145 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)
netpbm @ 10.78.3formatting

Look for formatting issues in the source

line 86 is way too long (127 characters)
axoloti-runtime @ 1.0.12-2formatting

Look for formatting issues in the source

line 196 is way too long (96 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)
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)
cryptsetup-static @ 2.2.2formatting

Look for formatting issues in the source

line 102 is way too long (93 characters)
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)
perl-test2-plugin-nowarnings @ 0.06formatting

Look for formatting issues in the source

line 104 is way too long (92 characters)
enlightenment @ 0.23.1formatting

Look for formatting issues in the source

line 344 is way too long (102 characters)
enlightenment @ 0.23.1formatting

Look for formatting issues in the source

line 345 is way too long (104 characters)
enlightenment @ 0.23.1formatting

Look for formatting issues in the source

line 346 is way too long (100 characters)
enlightenment @ 0.23.1formatting

Look for formatting issues in the source

line 347 is way too long (99 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)
wgetpaste @ 2.29formatting

Look for formatting issues in the source

line 99 is way too long (113 characters)
wicd @ 1.7.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 176 is way too long (99 characters)
ruby-iruby @ 0.3formatting

Look for formatting issues in the source

line 414 is way too long (112 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)
jose @ 10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 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)
guile-wm @ 1.0-1.f3c7b3bformatting

Look for formatting issues in the source

line 126 is way too long (92 characters)
python-pygobject @ 3.28.3formatting

Look for formatting issues in the source

line 701 is way too long (95 characters)
maven-shared-utils @ 3.2.1formatting

Look for formatting issues in the source

line 357 is way too long (109 characters)
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 207, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 208, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 209, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 213, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 214, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 216, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

line 281 is way too long (94 characters)
julia @ 1.1.1formatting

Look for formatting issues in the source

line 283 is way too long (99 characters)
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 313, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 315, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 316, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 317, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 321, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 322, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 324, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 325, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 326, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 327, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 328, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 329, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 330, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 331, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 374, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 376, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 377, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 378, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 379, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 380, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 381, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 382, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 383, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 384, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 385, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 386, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 387, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 389, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 390, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 391, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 392, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 393, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 394, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

line 426 is way too long (91 characters)
julia @ 1.1.1formatting

Look for formatting issues in the source

line 428 is way too long (119 characters)
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 430, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 431, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 432, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 436, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 437, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 438, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 456, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 461, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 462, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 467, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 468, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 469, column 0
telepathy-glib @ 0.24.1formatting

Look for formatting issues in the source

line 831 is way too long (92 characters)
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-embedder @ 3.6.1formatting

Look for formatting issues in the source

line 1271 is way too long (110 characters)
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)
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)
pth @ 2.0.7formatting

Look for formatting issues in the source

trailing white space on line 42
ldc @ 0.17.4formatting

Look for formatting issues in the source

line 134 is way too long (98 characters)
libsigsegv @ 2.12formatting

Look for formatting issues in the source

line 48 is way too long (133 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)
python @ 3.7.4formatting

Look for formatting issues in the source

line 396 is way too long (92 characters)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 231, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 233, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 236, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 237, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 246, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 247, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 248, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 249, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 250, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 251, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 252, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 254, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 255, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 256, column 0
libdaemon @ 0.14formatting

Look for formatting issues in the source

line 35 is way too long (147 characters)
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-hxt-unicode @ 9.0.2.4formatting

Look for formatting issues in the source

line 1287 is way too long (91 characters)
zn-poly @ 0.9.2description

Validate package descriptions

description should start with an upper-case letter or digit
perl-libxml @ 0.08description

Validate package descriptions

description should start with an upper-case letter or digit
java-xom @ 127formatting

Look for formatting issues in the source

trailing white space on line 1675
rcm @ 1.3.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 183
graphviz @ 2.40.1inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
graphviz @ 2.38.0-1.f54ac2cinputs-should-be-native

Identify inputs that should be native inputs

'swig' 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
terminator @ 1.91inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
grantleetheme @ 19.08.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 183 is way too long (102 characters)
tigervnc-server @ 1.10.1formatting

Look for formatting issues in the source

line 186 is way too long (99 characters)
tigervnc-server @ 1.10.1formatting

Look for formatting issues in the source

tabulation on line 195, column 0
python2-libmpsse @ 1.4formatting

Look for formatting issues in the source

line 1085 is way too long (96 characters)
python-libmpsse @ 1.4formatting

Look for formatting issues in the source

line 1052 is way too long (94 characters)
fc-host-tools @ 11formatting

Look for formatting issues in the source

line 1176 is way too long (122 characters)
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)
openldap @ 2.4.47inputs-should-be-native

Identify inputs that should be native inputs

'groff' 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
zbar @ 0.23inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' 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
gtk+ @ 2.24.32patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
at-spi2-core @ 2.34.0formatting

Look for formatting issues in the source

line 579 is way too long (97 characters)
mig @ 1.8inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
aspell @ 0.60.6.1formatting

Look for formatting issues in the source

line 76 is way too long (101 characters)
ibus-libhangul @ 1.5.3description

Validate package descriptions

description should start with an upper-case letter or digit
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)
gcompris @ 17.05formatting

Look for formatting issues in the source

line 127 is way too long (96 characters)
pcmanfm-qt @ 0.14.1inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
lxqt-session @ 0.14.1formatting

Look for formatting issues in the source

line 852 is way too long (100 characters)
childsplay @ 3.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 569 is way too long (99 characters)
mkvtoolnix @ 37.0.0formatting

Look for formatting issues in the source

line 418 is way too long (96 characters)
python2-xsge @ 2018.02.26description

Validate package descriptions

description should start with an upper-case letter or digit
deutex @ 5.2.1description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
grfcodec @ 6.0.6description

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

line 484 is way too long (95 characters)
lua-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'groff' 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)
python-pytools @ 2020.1description

Validate package descriptions

use @code or similar ornament instead of quotes
editorconfig-core-c @ 0.12.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 755 is way too long (125 characters)
kdevelop-pg-qt @ 2.2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
flatbuffers @ 1.10.0source-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
java-usb4java @ 1.2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
sonata @ 1.7b1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
rdmd @ 2.077.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ninja @ 1.9.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
spacefm @ 1.0.6source-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 i586-gnu derivation: could not find bootstrap binary 'tar' for system 'i586-gnu'
gnumach @ 1.8-1.097f9cfderivation

Report failure to compile a package to a derivation

failed to create i686-gnu derivation: could not find bootstrap binary 'tar' for system 'i686-gnu'
efitools @ 1.9.2formatting

Look for formatting issues in the source

line 175 is way too long (113 characters)
connman @ 1.38description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
racket-minimal @ 7.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gnunet @ 0.12.2formatting

Look for formatting issues in the source

line 297 is way too long (92 characters)
calibre @ 3.42.0formatting

Look for formatting issues in the source

trailing white space on line 94
java-rsyntaxtextarea @ 2.6.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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
mkbootimg @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 619 is way too long (114 characters)
fastboot @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 423 is way too long (95 characters)
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)
go-github.com-smartystreets-goconvey @ 1.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 33
asciidoc @ 8.6.10source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
gcc-objc++ @ 4.9.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc @ 4.9.4patch-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
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
gccgo @ 4.9.4patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 511 is way too long (91 characters)
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
qtdatavis3d @ 5.12.7description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'dejagnu' should probably be a native input
python2-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
gdb @ 8.2.1inputs-should-be-native

Identify inputs that should be native inputs

'dejagnu' 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
gdb-arm-none-eabi @ 9.1inputs-should-be-native

Identify inputs that should be native inputs

'dejagnu' 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
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 @ 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
qtserialport @ 5.12.7formatting

Look for formatting issues in the source

line 1012 is way too long (115 characters)
qtsensors @ 5.12.7formatting

Look for formatting issues in the source

line 869 is way too long (97 characters)
qtmultimedia @ 5.12.7formatting

Look for formatting issues in the source

line 912 is way too long (96 characters)
python-pyqt @ 5.12.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 577 is way too long (94 characters)
r-hsmmsinglecell @ 1.2.0formatting

Look for formatting issues in the source

line 936 is way too long (95 characters)
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.7.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

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
emacs-clang-rename @ 9.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-clang-format @ 9.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-llvmlite @ 0.30.0formatting

Look for formatting issues in the source

line 764 is way too long (92 characters)
arm-trusted-firmware-rk3399 @ 2.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
arm-trusted-firmware-sun50i-a64 @ 2.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
arm-trusted-firmware-rk3328 @ 2.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
qucs @ 0.0.19-0.b4f27d9inputs-should-be-native

Identify inputs that should be native inputs

'libtool' 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
qucs-s @ 0.0.21source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
guile-stis-parser @ 0-1.6e85d37description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 117
elixir @ 1.10.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
dmraid @ 1.0.0.rc16-3formatting

Look for formatting issues in the source

line 683 is way too long (91 characters)
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
wine-staging @ 5.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'autoconf' 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
ibus @ 1.5.22inputs-should-be-native

Identify inputs that should be native inputs

'gettext' should probably be a native input
kodi-wayland @ 18.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
appstream-glib @ 0.7.17formatting

Look for formatting issues in the source

line 943 is way too long (93 characters)
minizip @ 1.2.11formatting

Look for formatting issues in the source

line 143 is way too long (115 characters)
unbound @ 1.10.0formatting

Look for formatting issues in the source

trailing white space on line 466
unbound @ 1.10.0formatting

Look for formatting issues in the source

trailing white space on line 502
tuxmath @ 2.0.3description

Validate package descriptions

description should start with an upper-case letter or digit
gcc-objc++ @ 8.4.0patch-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
next @ 1.5.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 588 is way too long (106 characters)
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
qemu-minimal @ 4.2.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
qemu-minimal @ 4.2.0formatting

Look for formatting issues in the source

line 278 is way too long (103 characters)
qemu @ 4.2.0formatting

Look for formatting issues in the source

line 133 is way too long (97 characters)
plotutils @ 2.6formatting

Look for formatting issues in the source

trailing white space on line 81
hplip-minimal @ 3.20.3patch-file-names

Validate file names and availability of patches

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
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.05patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

line 141 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)
zathura-djvu @ 0.2.9formatting

Look for formatting issues in the source

line 471 is way too long (93 characters)
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-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 @ 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-winpthreads @ 7.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
catdoc @ 0.95description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 157
java-jbzip2 @ 0.9.1formatting

Look for formatting issues in the source

line 275 is way too long (92 characters)
libical @ 3.0.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libical @ 3.0.7formatting

Look for formatting issues in the source

line 126 is way too long (93 characters)
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
udiskie @ 2.1.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
localed @ 241formatting

Look for formatting issues in the source

line 531 is way too long (96 characters)
udisks @ 2.7.7formatting

Look for formatting issues in the source

line 936 is way too long (97 characters)
lightgbm @ 2.0.12source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
nanovg-for-extempore @ 0.7.1source-unstable-tarball

Check for autogenerated tarballs

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

Look for formatting issues in the source

line 296 is way too long (100 characters)
xftwidth @ 20170402description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 96, 234
wpa-supplicant @ 2.9description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-fpylll @ 0.4.1description

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
xcalib @ 0.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1480, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1481, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1483, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1484, column 0
giac @ 1.5.0-87formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2935 is way too long (91 characters)
java-kxml2 @ 2.4.2description

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
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

line 2025 is way too long (91 characters)
wxwidgets-gtk2 @ 3.0.4description

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
wxwidgets-gtk2 @ 3.1.0description

Validate package descriptions

description should start with an upper-case letter or digit
python2-mox3 @ 0.24.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ocaml-topkg @ 1.0.0description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 304
ocaml4.07-piqi @ 0.7.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ocamlify @ 0.0.1formatting

Look for formatting issues in the source

line 2251 is way too long (98 characters)
go-github-com-gorilla-context @ 0.0.0-0.08b5f42formatting

Look for formatting issues in the source

line 1102 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 1935 is way too long (129 characters)
shogun @ 6.1.3inputs-should-be-native

Identify inputs that should be native inputs

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

Look for formatting issues in the source

line 517 is way too long (91 characters)
syncthing @ 1.4.0formatting

Look for formatting issues in the source

line 96 is way too long (93 characters)
bind @ 9.16.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 253
git-crypt @ 0.6.0formatting

Look for formatting issues in the source

line 706 is way too long (91 characters)
rust-rustc-tools-util @ 0.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
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
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)
vim-full @ 8.2.0411formatting

Look for formatting issues in the source

line 197 is way too long (94 characters)
containerd @ 1.2.5formatting

Look for formatting issues in the source

line 214 is way too long (102 characters)
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 21912 is way too long (114 characters)
php @ 7.4.4formatting

Look for formatting issues in the source

line 187 is way too long (93 characters)
php @ 7.4.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 196 is way too long (91 characters)
php @ 7.4.4formatting

Look for formatting issues in the source

line 204 is way too long (93 characters)
php @ 7.4.4formatting

Look for formatting issues in the source

line 216 is way too long (92 characters)
php @ 7.4.4formatting

Look for formatting issues in the source

line 217 is way too long (96 characters)
php @ 7.4.4formatting

Look for formatting issues in the source

line 222 is way too long (96 characters)
php @ 7.4.4formatting

Look for formatting issues in the source

line 246 is way too long (91 characters)
php @ 7.4.4formatting

Look for formatting issues in the source

line 259 is way too long (92 characters)
xorg-server @ 1.20.7patch-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
xproto @ 7.0.31formatting

Look for formatting issues in the source

line 4871 is way too long (91 characters)
nethogs @ 0.8.5source-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
librdkafka @ 0.9.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
pidentd @ 3.0.19source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
libstdc++-doc @ 5.5.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
libgccjit @ 9.3.0patch-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
restbed @ 4.6-1.6eb385fformatting

Look for formatting issues in the source

line 2569 is way too long (92 characters)
restinio @ 0.6.0.1formatting

Look for formatting issues in the source

line 2594 is way too long (105 characters)
restinio @ 0.6.0.1formatting

Look for formatting issues in the source

line 2608 is way too long (95 characters)
ruby-rb-inotify @ 0.9.10description

Validate package descriptions

description should start with an upper-case letter or digit
rhash @ 1.3.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ruby-sanitize @ 4.6.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
hyperledger-iroha @ 1.1.1formatting

Look for formatting issues in the source

line 169 is way too long (105 characters)
libsecp256k1 @ 20191213-1.d644ddaformatting

Look for formatting issues in the source

line 922 is way too long (106 characters)
glibc-hurd-headers @ 2.29patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
glibc @ 2.29formatting

Look for formatting issues in the source

line 692 is way too long (98 characters)
u-boot-wandboard @ 2020.01description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-puma-rk3399 @ 2020.01description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-nintendo-nes-classic-edition @ 2020.01description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-rock64-rk3328 @ 2020.01description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-rockpro64-rk3399 @ 2020.01description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-firefly-rk3399 @ 2020.01description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-vexpress-ca9x4 @ 2020.01description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
grub-hybrid @ 2.04patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-wandboard @ 2020.01formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 592 is way too long (93 characters)
u-boot-nintendo-nes-classic-edition @ 2020.01formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 592 is way too long (93 characters)
u-boot-pinebook @ 2020.01formatting

Look for formatting issues in the source

line 682 is way too long (127 characters)
u-boot-am335x-evm @ 2020.01formatting

Look for formatting issues in the source

line 592 is way too long (93 characters)
u-boot-tools @ 2020.01formatting

Look for formatting issues in the source

line 460 is way too long (91 characters)
u-boot-tools @ 2020.01formatting

Look for formatting issues in the source

line 482 is way too long (97 characters)
u-boot-sifive-fu540 @ 2020.01formatting

Look for formatting issues in the source

line 592 is way too long (93 characters)
u-boot-cubieboard @ 2020.01formatting

Look for formatting issues in the source

line 592 is way too long (93 characters)
u-boot-mx6cuboxi @ 2020.01formatting

Look for formatting issues in the source

line 592 is way too long (93 characters)
u-boot-am335x-boneblack @ 2020.01formatting

Look for formatting issues in the source

line 633 is way too long (95 characters)
u-boot-cubietruck @ 2020.01formatting

Look for formatting issues in the source

line 592 is way too long (93 characters)
u-boot-vexpress-ca9x4 @ 2020.01formatting

Look for formatting issues in the source

line 592 is way too long (93 characters)
u-boot-malta @ 2020.01formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 592 is way too long (93 characters)
libosinfo @ 1.7.1formatting

Look for formatting issues in the source

line 330 is way too long (106 characters)
krona-tools @ 2.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 505 is way too long (92 characters)
serf @ 1.3.9formatting

Look for formatting issues in the source

line 1656 is way too long (92 characters)
go-github-com-multiformats-go-multiaddr @ 1.3.0-0.fe1c46fformatting

Look for formatting issues in the source

line 2379 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 2302 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 2305 is way too long (93 characters)
go-github-com-libp2p-go-libp2p-peer @ 2.3.8-0.993d742formatting

Look for formatting issues in the source

line 2246 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 2422 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 2423 is way too long (93 characters)
go-github-com-mitchellh-go-homedir @ 1.0.0-0.ae18d6bformatting

Look for formatting issues in the source

line 2341 is way too long (95 characters)
abc @ 0.0-1.5ae4b97formatting

Look for formatting issues in the source

line 86 is way too long (95 characters)
libchop @ 0.5.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xygrib @ 1.2.6.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 256
python2-asn1crypto @ 0.24.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python2-cryptography @ 2.7description

Validate package descriptions

description should start with an upper-case letter or digit
python-cryptography @ 2.7description

Validate package descriptions

description should start with an upper-case letter or digit
osm-gps-map @ 1.1.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-mapnik @ 3.0.16source-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
imposm3 @ 0.6.0-alpha.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-axolotl @ 0.1.39patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-next @ 27.0.50-0.36abf68patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-pygpgme @ 0.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
patchwork @ 2.1.5formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ncurses @ 6.1-20190609formatting

Look for formatting issues in the source

trailing white space on line 165
ncurses @ 6.1-20190609formatting

Look for formatting issues in the source

line 179 is way too long (94 characters)
wine64 @ 5.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 475 is way too long (92 characters)
libdaemon @ 0.14formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
glusterfs @ 7.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
arm-trusted-firmware-rk3328 @ 2.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
xygrib @ 1.2.6.1formatting

Look for formatting issues in the source

line 1056 is way too long (95 characters)
abseil-cpp @ 20200225.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 465 is way too long (144 characters)
wine-staging @ 5.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libnfs @ 3.0.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
proj.4 @ 4.9.3formatting

Look for formatting issues in the source

line 409 is way too long (92 characters)
lxde-common @ 0.99.2formatting

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
u-boot-pine64-lts @ 2020.01formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
josm @ 15937formatting

Look for formatting issues in the source

tabulation on line 1178, column 0
josm @ 15937formatting

Look for formatting issues in the source

line 1218 is way too long (91 characters)
ldc @ 1.10.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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
python2-bx-python @ 0.8.2description

Validate package descriptions

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

Validate package descriptions

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

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-bx-python @ 0.8.2description

Validate package descriptions

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

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
python-dnaio @ 0.3description

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
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
clipper @ 1.2.1inputs-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
guile-readline @ 2.2.6patch-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
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
rust @ 1.25.0formatting

Look for formatting issues in the source

line 735 is way too long (91 characters)
ncbi-vdb @ 2.9.6formatting

Look for formatting issues in the source

tabulation on line 5774, column 26
rust @ 1.26.2formatting

Look for formatting issues in the source

line 771 is way too long (94 characters)
discrover @ 1.6.0formatting

Look for formatting issues in the source

line 2689 is way too long (91 characters)
guile-readline @ 2.2.6formatting

Look for formatting issues in the source

line 347 is way too long (94 characters)
java-picard @ 1.113formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3928 is way too long (117 characters)
mrustc @ 0.9formatting

Look for formatting issues in the source

line 175 is way too long (123 characters)
guile3.0-readline @ 3.0.2formatting

Look for formatting issues in the source

line 347 is way too long (94 characters)
java-picard @ 2.10.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3870 is way too long (91 characters)
blasr-libcpp @ 5.3.3formatting

Look for formatting issues in the source

line 586 is way too long (95 characters)
java-picard @ 2.3.0formatting

Look for formatting issues in the source

line 3781 is way too long (104 characters)
mdadm-static @ 4.1description

Validate package descriptions

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

Identify inputs that should be native inputs

'swig' should probably be a native input
guile2.0-commonmark @ 0.1.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
guile-ncurses-with-gpm @ 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
guile-dbd-sqlite3 @ 2.1.6description

Validate package descriptions

description should start with an upper-case letter or digit
libreoffice @ 6.4.2.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile-dbi @ 2.1.6formatting

Look for formatting issues in the source

line 1242 is way too long (94 characters)
iml @ 1.0.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 798
gap @ 4.10.2formatting

Look for formatting issues in the source

trailing white space on line 1164
symmetrica @ 2.0formatting

Look for formatting issues in the source

line 1370 is way too long (100 characters)
eigen @ 3.3.7formatting

Look for formatting issues in the source

tabulation on line 949, column 0
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
gst-transcoder @ 1.12.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gnome-shell-extension-gsconnect @ 28inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
xen @ 4.11.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
conda @ 4.3.16formatting

Look for formatting issues in the source

line 751 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
python2-fastlmm @ 0.2.21formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1565 is way too long (137 characters)
ghc-llvm-hs-pure @ 9.0.0description

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-operational @ 0.2.3.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
ghc-fsnotify @ 0.3.0.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 81
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-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-regex-tdfa @ 1.2.3.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 139
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
espeak-ng @ 1.50description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-hsyaml @ 0.1.2.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-doclayout @ 0.3description

Validate package descriptions

description should start with an upper-case letter or digit
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 @ 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-no-x-toolkit @ 26.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ghc-vector @ 0.12.0.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ghc-base-unicode-symbols @ 0.2.3formatting

Look for formatting issues in the source

line 904 is way too long (101 characters)
ghc-xdg-basedir @ 0.2.2formatting

Look for formatting issues in the source

line 13335 is way too long (93 characters)
ghc-th-orphans @ 0.13.9formatting

Look for formatting issues in the source

line 11884 is way too long (92 characters)
ghc-system-filepath @ 0.4.14formatting

Look for formatting issues in the source

line 11452 is way too long (250 characters)
gmp @ 6.1.2formatting

Look for formatting issues in the source

line 81 is way too long (96 characters)
python2-ccm @ 2.1.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 84
python-psycopg2 @ 2.8.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
guile-wiredtiger @ 0.7.0description

Validate package descriptions

use @code or similar ornament instead of quotes
python-ccm @ 2.1.6description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python2-lmdb @ 0.95description

Validate package descriptions

description should start with an upper-case letter or digit
sparql-query @ 1.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
mongodb @ 3.4.10source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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
python2-unittest2 @ 1.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mongodb @ 3.4.10formatting

Look for formatting issues in the source

line 595 is way too long (99 characters)
mariadb @ 10.1.44formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 805 is way too long (91 characters)
diffoscope @ 138formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
cl-circular-streams @ 0.1.0-1.e770baddescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 79
sbcl-circular-streams @ 0.1.0-1.e770baddescription

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
sbcl-md5 @ 2.0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
ecl-trivial-gray-streams @ 0.0.0-1.0483adedescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 75
cl-trivial-gray-streams @ 0.0.0-1.0483adedescription

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
sbcl-trivial-gray-streams @ 0.0.0-1.0483adedescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 75
i3-wm @ 4.18description

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-quri @ 0.1.0-1.76b7510description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
sbcl-quri @ 0.1.0-1.76b7510description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
keybinder-3.0 @ 0.3.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' 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
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-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
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
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
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
cl-portable-threads @ 2.3-1.c0e61a1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2329 is way too long (96 characters)
cl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 133 is way too long (96 characters)
ecl-portable-threads @ 2.3-1.c0e61a1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1145 is way too long (98 characters)
sbcl-portable-threads @ 2.3-1.c0e61a1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1145 is way too long (98 characters)
sbcl-trivia.trivial @ 0.0.0-1.574901aformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 133 is way too long (96 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)
cl-sqlite @ 0.2-1.c738e66formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2651 is way too long (130 characters)
stumpwm-with-slynk @ 19.11formatting

Look for formatting issues in the source

line 1650 is way too long (94 characters)
sbcl-cl-cffi-gtk-glib @ 0.11.2-1.29443c5formatting

Look for formatting issues in the source

line 2897 is way too long (91 characters)
sbcl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 5954 is way too long (91 characters)
slurp @ 1.2.0inputs-should-be-native

Identify inputs that should be native inputs

'scdoc' should probably be a native input
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)
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

line 219 is way too long (106 characters)
sdl-mixer @ 1.2.12formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 229 is way too long (91 characters)
guile-sdl @ 0.5.2formatting

Look for formatting issues in the source

line 615 is way too long (111 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 506 is way too long (116 characters)
gimp-resynthesizer @ 2.0.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
hurd @ 0.9derivation

Report failure to compile a package to a derivation

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

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'
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

tabulation on line 342, column 0
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

line 350 is way too long (107 characters)
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

tabulation on line 354, column 0
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

tabulation on line 355, column 0
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

tabulation on line 356, column 0
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

tabulation on line 357, column 0
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

tabulation on line 358, column 0
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

tabulation on line 367, column 0
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

tabulation on line 368, column 0
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-core @ 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-native-access-platform @ 4.5.1description

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-fasterxml-jackson-core @ 2.9.4description

Validate package descriptions

description should not be empty
java-jsch-agentproxy-jsch @ 0.0.8description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
java-jsch-agentproxy-usocket-jna @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
java-jsch-agentproxy-usocket-jna @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
java-jsch-agentproxy-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-powermock-modules-junit4 @ 1.7.3source-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-guice-servlet @ 4.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-jsch-agentproxy-sshagent @ 0.0.8source-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-gson @ 2.8.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fest-assert @ 2.0M10source-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-ops4j-pax-exam-core-junit @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-lz4 @ 1.4.0source-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-jsch-agentproxy-core @ 0.0.8source-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-fasterxml-jackson-annotations @ 2.9.4source-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-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-plexus-archiver @ 4.1.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-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-hawtjni @ 1.15source-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-interceptors-api-spec @ 1.2source-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-javax-inject @ tck-1source-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-ops4j-base-io @ 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-bnd-annotation @ 3.5.0source-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-powermock-api-support @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-powermock-core @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-el-api-spec @ 3.0source-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-native-access-platform @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core-spi @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fest-test @ 2.1.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-xmlunit-matchers @ 2.5.1source-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-guice @ 4.1source-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-core @ 2.9.4source-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-datanucleus-javax-persistence @ 2.2.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-powermock-api-easymock @ 1.7.3source-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-lmax-disruptor @ 3.3.7source-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-joda-time @ 2.9.9source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fest-util @ 1.2.5source-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-jansi-native @ 1.7source-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-xmlunit @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-powermock-reflect @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jansi @ 1.16source-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-jsch-agentproxy-jsch @ 0.0.8source-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-jboss-javassist @ 3.21.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-woodstox-core @ 5.0.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-util-property @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-spi @ 1.5.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-pax-tinybundles @ 2.1.1source-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-jsch-agentproxy-usocket-jna @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-bouncycastle @ 1.60source-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-native-access @ 4.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-powermock-modules-junit4 @ 1.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-powermock-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-core @ 1.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-powermock-api-easymock @ 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-reflect @ 1.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8750 is way too long (98 characters)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 11448 is way too long (102 characters)
java-commons-jxpath @ 1.3formatting

Look for formatting issues in the source

line 5273 is way too long (93 characters)
java-commons-httpclient @ 3.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8470 is way too long (96 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)
icedtea @ 3.7.0formatting

Look for formatting issues in the source

line 1703 is way too long (109 characters)
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6435, column 20
java-ops4j-pax-exam-core-spi @ 4.11.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8327 is way too long (100 characters)
java-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4181 is way too long (98 characters)
java-jnacl @ 0.1.0-2.094e819formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8422 is way too long (93 characters)
java-jgit @ 4.2.0.201601211800-rformatting

Look for formatting issues in the source

line 11551 is way too long (93 characters)
java-openjfx-base @ 8.202formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8638 is way too long (104 characters)
java-joda-time @ 2.9.9formatting

Look for formatting issues in the source

line 10399 is way too long (92 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

line 10728 is way too long (92 characters)
java-testng @ 6.14.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 11292 is way too long (95 characters)
java-apache-ivy @ 2.4.0formatting

Look for formatting issues in the source

line 11128 is way too long (101 characters)
java-native-access @ 4.5.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4061 is way too long (107 characters)
r-mixomics @ 6.10.9description

Validate package descriptions

description should start with an upper-case letter or digit
r-dplyr @ 0.8.5description

Validate package descriptions

description should start with an upper-case letter or digit
r-rgadem @ 2.34.1description

Validate package descriptions

description should start with an upper-case letter or digit
r-biosigner @ 1.14.4description

Validate package descriptions

use @code or similar ornament instead of quotes
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-monocle @ 2.14.0formatting

Look for formatting issues in the source

line 2707 is way too long (101 characters)
r-unifiedwmwqpcr @ 1.22.0formatting

Look for formatting issues in the source

line 6675 is way too long (92 characters)
r-genomicinteractions @ 1.20.2formatting

Look for formatting issues in the source

line 1991 is way too long (92 characters)
r-lumi @ 2.38.0formatting

Look for formatting issues in the source

line 3117 is way too long (95 characters)
r-seqlogo @ 1.52.0description

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
python-pyfit-sne @ 1.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
r-bseqsc @ 1.0-1.fef3f3edescription

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
imp @ 2.6.2inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
freebayes @ 1.0.2-1.3ce827dformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10696 is way too long (104 characters)
dropseq-tools @ 1.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 12614, column 0
salmon @ 0.13.1formatting

Look for formatting issues in the source

line 12035 is way too long (99 characters)
python2-flexmock @ 0.10.4description

Validate package descriptions

description should start with an upper-case letter or digit
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
python2-pytest-subtesthack @ 0.1.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
umockdev @ 0.13.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-pyfakefs @ 3.7.1patch-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
python2-paste @ 3.0.6patch-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
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
python-wtforms @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2899 is way too long (100 characters)
mrrescue @ 1.02edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 2
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
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
queen-de @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8094 is way too long (205 characters)
freeorion @ 0.4.9formatting

Look for formatting issues in the source

line 8378 is way too long (92 characters)
einstein @ 2.0formatting

Look for formatting issues in the source

line 3451 is way too long (96 characters)
lure-de @ 1.1formatting

Look for formatting issues in the source

line 7994 is way too long (93 characters)
ri-li @ 2.0.1formatting

Look for formatting issues in the source

line 8293 is way too long (100 characters)
sky @ 1.2formatting

Look for formatting issues in the source

line 8197 is way too long (118 characters)
btanks @ 0.9.8083formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6974, column 18
btanks @ 0.9.8083formatting

Look for formatting issues in the source

tabulation on line 6975, column 17
queen @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8094 is way too long (205 characters)
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5705, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5706, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5709, column 0
queen-fr @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7994 is way too long (93 characters)
lure-fr @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8094 is way too long (205 characters)
lure-es @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7994 is way too long (93 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
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)
atril @ 1.22.0formatting

Look for formatting issues in the source

line 754 is way too long (92 characters)
python2-psutil @ 5.6.5description

Validate package descriptions

description should start with an upper-case letter or digit
xwallpaper @ 0.6.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 72
emacs-dhall-mode @ 0.1.3-0.ef4d33ddescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 89
python-psutil @ 5.6.5description

Validate package descriptions

description should start with an upper-case letter or digit
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-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 380 is way too long (92 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 381 is way too long (96 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 382 is way too long (92 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 384 is way too long (94 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 385 is way too long (91 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 386 is way too long (94 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 387 is way too long (99 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 388 is way too long (106 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 389 is way too long (110 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 390 is way too long (117 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 391 is way too long (98 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 393 is way too long (102 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 395 is way too long (92 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 396 is way too long (116 characters)
emacs-magit @ 2.90.1-3.c761d28formatting

Look for formatting issues in the source

line 397 is way too long (95 characters)
pan @ 0.146description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
notifymuch @ 0.1-1.9d4aaf5inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' 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
calibre @ 3.42.0formatting

Look for formatting issues in the source

line 203 is way too long (93 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
perl-file-readbackwards @ 1.05description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 47
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-class-load @ 0.25description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-file-which @ 1.23description

Validate package descriptions

use @code or similar ornament instead of quotes
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-util @ 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-xml @ 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-servlet @ 9.4.6source-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-jmx @ 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.4.6source-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-io @ 9.2.22source-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-servlet @ 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-perf-helper @ 4.2source-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-security @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-test-helper @ 4.2source-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
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5272, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5273, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5274, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5275, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5276, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5282, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5283, column 0
varnish @ 6.4.0formatting

Look for formatting issues in the source

line 5583 is way too long (91 characters)
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 8701 is way too long (97 characters)
python-dnspython @ 1.15.0description

Validate package descriptions

description should start with an upper-case letter or digit
python2-dukpy @ 0.3description

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
python2-dbus @ 1.2.14description

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-jinja2-time @ 0.2.0description

Validate package descriptions

use @code or similar ornament instead of quotes
python-py3status @ 3.21description

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
python-pywinrm @ 0.4.1description

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
python2-argcomplete @ 1.10.3description

Validate package descriptions

description should start with an upper-case letter or digit
python2-gevent @ 1.4.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-apispec @ 0.25.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
python-pyaml @ 18.11.0description

Validate package descriptions

description should start with an upper-case letter or digit
python2-dnspython @ 1.15.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-argcomplete @ 1.10.3description

Validate package descriptions

description should start with an upper-case letter or digit
python-gevent @ 1.4.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-pyaml @ 18.11.0description

Validate package descriptions

description should start with an upper-case letter or digit
python2-rst.linker @ 1.11description

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
python2-q @ 2.6description

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-pkgconfig @ 1.3.1inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' 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-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-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-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
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-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
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-pybugz @ 0.6.11patch-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-file @ 5.33patch-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-configobj @ 5.0.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with 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
python-file @ 5.33patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python-cloudpickle @ 0.6.1formatting

Look for formatting issues in the source

line 17022 is way too long (97 characters)
python-cloudpickle @ 0.6.1formatting

Look for formatting issues in the source

line 17023 is way too long (97 characters)
python2-hy @ 0.17.0formatting

Look for formatting issues in the source

tabulation on line 9360, column 0
python2-hy @ 0.17.0formatting

Look for formatting issues in the source

tabulation on line 9361, column 0
python2-hy @ 0.17.0formatting

Look for formatting issues in the source

tabulation on line 9362, column 0
scons @ 3.0.4formatting

Look for formatting issues in the source

line 2014 is way too long (96 characters)
python-matplotlib @ 3.1.2formatting

Look for formatting issues in the source

line 4526 is way too long (107 characters)
python-matplotlib @ 3.1.2formatting

Look for formatting issues in the source

line 4567 is way too long (96 characters)
python-matplotlib @ 3.1.2formatting

Look for formatting issues in the source

line 4588 is way too long (105 characters)
python2-cloudpickle @ 0.6.1formatting

Look for formatting issues in the source

line 17022 is way too long (97 characters)
python2-cloudpickle @ 0.6.1formatting

Look for formatting issues in the source

line 17023 is way too long (97 characters)
python-hy @ 0.17.0formatting

Look for formatting issues in the source

tabulation on line 9360, column 0
python-hy @ 0.17.0formatting

Look for formatting issues in the source

tabulation on line 9361, column 0
python-hy @ 0.17.0formatting

Look for formatting issues in the source

tabulation on line 9362, column 0
python-ipython-documentation @ 7.9.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python-numpy @ 1.17.3formatting

Look for formatting issues in the source

line 4023 is way too long (152 characters)
linux-libre-riscv64-generic @ 5.4.30derivation

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.30derivation

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-headers @ 4.14.175patch-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.30patch-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.175patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-headers @ 5.4.30patch-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.30patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-headers @ 4.4.218patch-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.114patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre @ 4.14.175patch-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.30patch-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.114patch-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.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre @ 4.4.218patch-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.2patch-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.175patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-headers @ 5.6.2patch-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.30patch-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.30formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 779 is way too long (117 characters)
linux-libre @ 4.19.114formatting

Look for formatting issues in the source

line 779 is way too long (117 characters)
linux-libre @ 5.4.30formatting

Look for formatting issues in the source

line 779 is way too long (117 characters)
linux-libre @ 4.9.218formatting

Look for formatting issues in the source

line 779 is way too long (117 characters)
linux-libre @ 4.14.175formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 779 is way too long (117 characters)
linux-libre @ 4.4.218formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 779 is way too long (117 characters)
icecat @ 68.6.1-guix0-preview1formatting

Look for formatting issues in the source

line 856 is way too long (102 characters)
icecat @ 68.6.1-guix0-preview1formatting

Look for formatting issues in the source

trailing white space on line 859
icecat @ 68.6.1-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 949 is way too long (139 characters)
icecat @ 68.6.1-guix0-preview1formatting

Look for formatting issues in the source

line 954 is way too long (95 characters)
icecat @ 68.6.1-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 998 is way too long (94 characters)
icecat @ 68.6.1-guix0-preview1formatting

Look for formatting issues in the source

line 1000 is way too long (95 characters)
icecat @ 68.6.1-guix0-preview1formatting

Look for formatting issues in the source

line 1013 is way too long (98 characters)
r-sapa @ 2.0-2description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 105, 128
r-squarem @ 2020.2formatting

Look for formatting issues in the source

line 2685 is way too long (91 characters)
r-shiny @ 1.4.0.2formatting

Look for formatting issues in the source

line 843 is way too long (92 characters)
ocaml-qcheck @ 0.12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 52, 165
ocaml-zarith @ 1.9.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
ocaml4.07-sexplib @ 0.11.0description

Validate package descriptions

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

Look for formatting issues in the source

line 2081 is way too long (97 characters)
texlive-latex-cyrillic @ 49435description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 78
lpsolve @ 5.5.2.5description

Validate package descriptions

description should start with an upper-case letter or digit
texlive-hyphen-occitan @ 49435description

Validate package descriptions

use @code or similar ornament instead of quotes
texlive-lm @ 49435description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 42
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
texlive-latex-hyperref @ 6.84a2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
arpack-ng @ 3.3.0source-unstable-tarball

Check for autogenerated tarballs

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

Validate file names and availability of patches

file names of patches should start with the package name
scotch32 @ 6.0.6patch-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
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
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
texlive-bin @ 20180414patch-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
hdf4-alt @ 4.2.14patch-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 2800, column 0
pt-scotch @ 6.0.6formatting

Look for formatting issues in the source

tabulation on line 2778, column 0
texlive-hyph-utf8 @ 49435formatting

Look for formatting issues in the source

line 2269 is way too long (108 characters)
texlive-hyph-utf8 @ 49435formatting

Look for formatting issues in the source

line 2270 is way too long (108 characters)
texlive-hyph-utf8 @ 49435formatting

Look for formatting issues in the source

line 2271 is way too long (95 characters)
libblockdev @ 2.23formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
pjproject-jami @ 2.9formatting

Look for formatting issues in the source

line 846 is way too long (103 characters)
sundials-openmpi @ 3.1.1formatting

Look for formatting issues in the source

tabulation on line 4532, column 0
lyx @ 2.3.3formatting

Look for formatting issues in the source

line 6260 is way too long (101 characters)
hdf4 @ 4.2.14formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
superlu-dist @ 6.2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2603, column 0
p4est @ 2.0formatting

Look for formatting issues in the source

tabulation on line 2864, column 0
libringclient @ 20191101.3.67671e7formatting

Look for formatting issues in the source

line 948 is way too long (105 characters)
hypre-openmpi @ 2.15.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2442 is way too long (100 characters)
texlive-hyphen-ethiopic @ 49435formatting

Look for formatting issues in the source

line 1575 is way too long (91 characters)
texlive-ruhyphen @ 49435formatting

Look for formatting issues in the source

line 2447 is way too long (92 characters)
texlive-ruhyphen @ 49435formatting

Look for formatting issues in the source

line 2450 is way too long (93 characters)
help2man @ 1.47.10formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
jami @ 20191101.3.67671e7formatting

Look for formatting issues in the source

line 993 is way too long (92 characters)
texlive-latex-pgf @ 49435formatting

Look for formatting issues in the source

line 6609 is way too long (98 characters)
texlive-bin @ 20180414formatting

Look for formatting issues in the source

line 271 is way too long (91 characters)
mumps-openmpi @ 5.2.1formatting

Look for formatting issues in the source

tabulation on line 2413, column 0
petsc @ 3.11.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
vorbis-tools @ 1.4.0formatting

Look for formatting issues in the source

trailing white space on line 323
texlive-latex-l3packages @ 49435formatting

Look for formatting issues in the source

line 3103 is way too long (91 characters)
texlive-latex-l3packages @ 49435formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
texlive-amsfonts @ 49435formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1140 is way too long (91 characters)
pjproject @ 2.9formatting

Look for formatting issues in the source

line 724 is way too long (103 characters)
slepc-openmpi @ 3.11.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 689, column 0
hdf-java @ 3.3.2formatting

Look for formatting issues in the source

line 1063 is way too long (92 characters)
mumps @ 5.2.1formatting

Look for formatting issues in the source

line 2327 is way too long (94 characters)
quaternion @ 0.0.9.4cinputs-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
libsignal-protocol-c @ 2.3.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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-i686-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 @ 7.0.0formatting

Look for formatting issues in the source

line 90 is way too long (91 characters)
sorcer @ 1.1.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-pyportmidi @ 217patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4620, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4621, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4622, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4623, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4625, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4632, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4633, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4634, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4635, column 0
solfege @ 3.22.2formatting

Look for formatting issues in the source

line 1199 is way too long (92 characters)
powertabeditor @ 2.0.0-alpha10formatting

Look for formatting issues in the source

line 1297 is way too long (94 characters)
emacs-nhexl-mode @ 1.4description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-flx @ 0.6.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 220
emacs-cnfonts @ 0.9.1description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-el-x @ 0.3.1description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-hercules @ 0.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 137
emacs-pyvenv @ 1.21description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-beancount @ 2.2.3patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

line 9972 is way too long (96 characters)
emacs-gtk-look @ 29formatting

Look for formatting issues in the source

line 17266 is way too long (94 characters)
emacs-mit-scheme-doc @ 20140203formatting

Look for formatting issues in the source

line 4508 is way too long (94 characters)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10290, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10291, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10294, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10295, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10307, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10308, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10309, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10310, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10311, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10312, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10313, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10314, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10315, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10316, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10317, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10318, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10319, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10320, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10321, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10322, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10323, column 0
emacs-lua-mode @ 20191204-1.1f596a9formatting

Look for formatting issues in the source

tabulation on line 7845, column 0
emacs-lua-mode @ 20191204-1.1f596a9formatting

Look for formatting issues in the source

tabulation on line 7848, column 0
emacs-dash-docs @ 1.4.0-1.111fd9bformatting

Look for formatting issues in the source

line 19549 is way too long (91 characters)
xfce4-volumed-pulse @ 0.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
librecad @ 2.1.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
vlc @ 3.0.8formatting

Look for formatting issues in the source

line 1198 is way too long (109 characters)
vlc @ 3.0.8formatting

Look for formatting issues in the source

line 1316 is way too long (107 characters)
gaupol @ 1.7formatting

Look for formatting issues in the source

line 3790 is way too long (95 characters)
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 614 is way too long (99 characters)
xfce4-clipman-plugin @ 1.4.4formatting

Look for formatting issues in the source

line 393 is way too long (91 characters)
tumbler @ 0.2.8formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
cfitsio @ 3.47description

Validate package descriptions

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
graphene @ 1.6.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
gtk+ @ 3.24.14patch-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
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
geoclue @ 2.5.5inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
deja-dup @ 34.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' 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
d-feet @ 0.3.14inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gnome-tweaks @ 3.32.0inputs-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
cheese @ 3.32.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gnome-contacts @ 3.32.1inputs-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
network-manager @ 1.18.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcr @ 3.28.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
network-manager @ 1.18.4formatting

Look for formatting issues in the source

line 6432 is way too long (110 characters)
network-manager @ 1.18.4formatting

Look for formatting issues in the source

line 6434 is way too long (117 characters)
gdm @ 3.32.0formatting

Look for formatting issues in the source

line 6887 is way too long (103 characters)
gnome-initial-setup @ 3.32.1formatting

Look for formatting issues in the source

line 590 is way too long (91 characters)
upower @ 0.99.11formatting

Look for formatting issues in the source

line 4128 is way too long (110 characters)
glade @ 3.22.1formatting

Look for formatting issues in the source

line 2079 is way too long (91 characters)
libsoup @ 2.70.0formatting

Look for formatting issues in the source

line 3641 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.28.2formatting

Look for formatting issues in the source

line 1536 is way too long (91 characters)
python2-discogs-client @ 2.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
sooperlooper @ 1.7.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 120
python-discogs-client @ 2.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
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
rosegarden @ 19.12formatting

Look for formatting issues in the source

line 4146 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
kcmutils @ 5.63.0formatting

Look for formatting issues in the source

line 2197 is way too long (113 characters)
extra-cmake-modules @ 5.63.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2723 is way too long (113 characters)
vmpk @ 0.7.2formatting

Look for formatting issues in the source

line 2132 is way too long (91 characters)
kpackage @ 5.63.0formatting

Look for formatting issues in the source

line 1890 is way too long (106 characters)
drumstick @ 1.1.3formatting

Look for formatting issues in the source

line 2087 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)
kdbusaddons @ 5.63.0formatting

Look for formatting issues in the source

line 643 is way too long (107 characters)
opencv @ 3.4.3formatting

Look for formatting issues in the source

line 283 is way too long (132 characters)
gtklick @ 0.6.4formatting

Look for formatting issues in the source

line 839 is way too long (94 characters)
ecasound @ 2.9.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471
audacity @ 2.3.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
vamp @ 2.6formatting

Look for formatting issues in the source

line 2670 is way too long (94 characters)
zita-resampler @ 1.3.0formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
openexr @ 2.4.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perftest @ 4.4-0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
fakeroot @ 1.24description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 114, 240
ecryptfs-utils @ 111description

Validate package descriptions

description should start with an upper-case letter or digit
ddate @ 0.2.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
pflask @ 0.2source-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
procenv @ 0.51source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
x86-energy-perf-policy @ 5.4.30patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
util-linux-with-udev @ 2.34patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
proot-static @ 5.1.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
cpupower @ 5.4.30patch-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 3100 is way too long (104 characters)
linux-pam @ 1.3.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
perftest @ 4.4-0.4formatting

Look for formatting issues in the source

line 4889 is way too long (98 characters)
crda @ 3.18formatting

Look for formatting issues in the source

line 3194 is way too long (105 characters)
util-linux @ 2.34formatting

Look for formatting issues in the source

line 1258 is way too long (91 characters)
msopenh264 @ 1.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
r-iheatmapr @ 0.4.12description

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-cmprsk @ 2.2-9description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 92, 113
r-minqa @ 1.2.4description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 173, 176
python-rpy2 @ 3.0.4-1.19868a8description

Validate package descriptions

description should start with an upper-case letter or digit
r-oai @ 0.3.0description

Validate package descriptions

use @code or similar ornament instead of quotes
r-bootstrap @ 2019.6description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 139
r-diagram @ 1.6.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 336
r-arm @ 1.10-1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 46, 60
r-circular @ 0.4-93description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-topicmodels @ 0.2-9description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-cardata @ 3.0-3description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 232, 243, 262
emacs-ess @ 17.11source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
r-flexdashboard @ 0.5.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 14778 is way too long (100 characters)
emacs-ess @ 17.11formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 12153 is way too long (91 characters)
r-colourpicker @ 1.0formatting

Look for formatting issues in the source

line 12259 is way too long (94 characters)
r-haplo-stats @ 1.7.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 424 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 428
r-abps @ 0.3formatting

Look for formatting issues in the source

line 7639 is way too long (93 characters)
texlive-fonts-lm @ 49435description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 93
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
linux-libre-arm-veyron @ 5.4.30patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
perl-base @ 5.30.0patch-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
perl-parent @ 5.30.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.0-gnutls @ 3.6.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-gnutls @ 3.6.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gnutls-dane @ 3.6.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name