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
java-jblas @ 1.2.4description

Validate package descriptions

description should start with an upper-case letter or digit
shell-functools @ 0.3.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 121, 206
nsis-i686 @ 3.05description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
connman @ 1.38description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
rcm @ 1.3.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 183
r-boot @ 1.3-25description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 125, 142
perl6-grammar-debugger @ 1.0.1-1.0375008description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 203
fstrcmp @ 0.7.D001description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
sh-z @ 1.11description

Validate package descriptions

use @code or similar ornament instead of quotes
gnome-shell-extension-gsconnect @ 33inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
python-oslotest @ 3.4.0inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
gramps @ 5.1.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python2-hacking @ 1.1.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
python2-langkit @ 0.0.0-0.fe0bc8binputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
shogun @ 6.1.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
libtool @ 2.4.6inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-hacking @ 1.1.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-mock' should probably be a native input
python-tempest-lib @ 1.0.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-openstackdocstheme @ 1.18.1inputs-should-be-native

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
emacs-cmake-mode @ 3.16.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libmhash @ 0.9.9.9patch-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
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
nsis-x86_64 @ 3.05patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
xplanet @ 1.3.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

xplanet-1.3.1-xpUtil-Add2017LeapSecond.cpp.patch: file name is too long
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
grub-minimal @ 2.04patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
mingw-w64-x86_64 @ 7.0.0patch-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
pth @ 2.0.7formatting

Look for formatting issues in the source

trailing white space on line 42
libsigsegv @ 2.12formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1116 is way too long (96 characters)
js-mathjax @ 2.7.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 169 is way too long (105 characters)
axoloti-runtime @ 1.0.12-2formatting

Look for formatting issues in the source

line 196 is way too long (96 characters)
jose @ 10formatting

Look for formatting issues in the source

line 37 is way too long (92 characters)
mingw-w64-i686 @ 7.0.0formatting

Look for formatting issues in the source

line 90 is way too long (91 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)
shogun @ 6.1.3formatting

Look for formatting issues in the source

line 519 is way too long (91 characters)
js-filesaver @ 1.3.8formatting

Look for formatting issues in the source

line 392 is way too long (99 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)
sdl-image @ 1.2.12formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
mingw-w64-x86_64-winpthreads @ 7.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 607 is way too long (111 characters)
ncurses @ 6.2formatting

Look for formatting issues in the source

trailing white space on line 165
ncurses @ 6.2formatting

Look for formatting issues in the source

line 179 is way too long (94 characters)
abc @ 0.0-1.5ae4b97formatting

Look for formatting issues in the source

line 86 is way too long (95 characters)
ldc @ 1.10.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 90 is way too long (91 characters)
ldc @ 0.17.4formatting

Look for formatting issues in the source

line 137 is way too long (98 characters)
efitools @ 1.9.2formatting

Look for formatting issues in the source

line 176 is way too long (113 characters)
mingw-w64-x86_64 @ 7.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 260 is way too long (92 characters)
python-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1083 is way too long (94 characters)
bash-minimal @ 5.0.16patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'flex' should probably be a native input
perl-test-file-contents @ 0.23description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
perl-test2-plugin-nowarnings @ 0.06formatting

Look for formatting issues in the source

line 106 is way too long (92 characters)
syncthing @ 1.5.0formatting

Look for formatting issues in the source

line 109 is way too long (93 characters)
perl-search-xapian @ 1.2.25.2description

Validate package descriptions

use @code or similar ornament instead of quotes
netpbm @ 10.78.3formatting

Look for formatting issues in the source

line 86 is way too long (127 characters)
vorbis-tools @ 1.4.0formatting

Look for formatting issues in the source

trailing white space on line 323
dejagnu @ 1.6.2formatting

Look for formatting issues in the source

line 60 is way too long (91 characters)
wicd @ 1.7.4formatting

Look for formatting issues in the source

line 109 is way too long (95 characters)
guile @ 2.0.14formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 191 is way too long (93 characters)
python2-pybedtools @ 0.8.1description

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
blasr-libcpp @ 5.3.3formatting

Look for formatting issues in the source

line 575 is way too long (95 characters)
clang-runtime @ 3.8.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.9-libsanitizer-mode-field.patch: file name is too long
python-libfreenect @ 0.6.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
xf86-video-intel @ 2.99.917-16.5ca3ac1formatting

Look for formatting issues in the source

line 3025 is way too long (91 characters)
gdb-arm-none-eabi @ 9.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ghc @ 8.6.5formatting

Look for formatting issues in the source

line 591 is way too long (91 characters)
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
busybox @ 1.31.1formatting

Look for formatting issues in the source

trailing white space on line 93
busybox @ 1.31.1formatting

Look for formatting issues in the source

line 95 is way too long (92 characters)
presentty @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
presentty @ 0.2.1formatting

Look for formatting issues in the source

line 45 is way too long (117 characters)
grfcodec @ 6.0.6description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 60
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 292, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 294, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 297, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 298, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 307, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 308, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 309, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 310, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 311, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 312, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 313, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 315, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 316, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 317, column 0
syncthing-gtk @ 0.9.4.4inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python2-setuptools' should probably not be an input at all
zbar @ 0.23inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
arm-trusted-firmware-rk3328 @ 2.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
elixir @ 1.10.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 76 is way too long (99 characters)
wine @ 5.12formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
zn-poly @ 0.9.2description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 185
maven-model-builder @ 3.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 1636 is way too long (110 characters)
maven-resolver-impl @ 1.3.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 221 is way too long (93 characters)
maven-wagon-http @ 3.3.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 284 is way too long (102 characters)
java-jbzip2 @ 0.9.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 165 is way too long (99 characters)
maven-shared-utils @ 3.2.1formatting

Look for formatting issues in the source

line 583 is way too long (109 characters)
ghc-operational @ 0.2.3.5description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
tigervnc-server @ 1.10.1-1.920d9c4patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 188, column 0
libchop @ 0.5.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
wine-staging @ 5.13inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'autoconf' should probably be a native input
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 247, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 248, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 249, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 250, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 251, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 252, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 253, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 254, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 255, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 258, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 259, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 261, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 262, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 263, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 264, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 265, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 267, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 268, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 269, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 270, column 0
wine-staging @ 5.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libsigrok @ 0.5.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 211 is way too long (92 characters)
python-sphinx-rtd-theme @ 0.2.4inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
libextractor @ 1.10formatting

Look for formatting issues in the source

line 128 is way too long (140 characters)
python-coveralls @ 1.11.1inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-ccm @ 2.1.6description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 84
lxde-common @ 0.99.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
clang @ 7.0.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 405 is way too long (91 characters)
clang @ 9.0.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 405 is way too long (91 characters)
clang @ 3.6.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 405 is way too long (91 characters)
rtl-sdr @ 0.6.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ocaml-dose3 @ 5.0.1formatting

Look for formatting issues in the source

line 363 is way too long (92 characters)
wxwidgets-gtk2 @ 3.1.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-pytest-vcr @ 1.0.2-1.4d6c7b3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
xfce4-volumed-pulse @ 0.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
xfce4-clipman-plugin @ 1.6.1formatting

Look for formatting issues in the source

line 408 is way too long (91 characters)
ghc-llvm-hs @ 9.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-inline-c @ 0.7.0.1description

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-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-llvm-hs-pure @ 9.0.0description

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
gnome-shell-extension-dash-to-panel @ 38inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
libringclient @ 20200710.1.6bd18d2inputs-should-be-native

Identify inputs that should be native inputs

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

Validate file names and availability of patches

file names of patches should start with the package name
pjproject-jami @ 2.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
pandoc @ 2.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 95 is way too long (93 characters)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 145 is way too long (91 characters)
libringclient @ 20200710.1.6bd18d2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 953 is way too long (101 characters)
tumbler @ 0.2.9formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
jami @ 20200710.1.6bd18d2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 177 is way too long (123 characters)
tuxmath @ 2.0.3description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 78
r-dplyr @ 1.0.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-pytools @ 2020.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
mate-applets @ 1.24.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 917
guile2.2-sjson @ 0.2.1description

Validate package descriptions

description should start with an upper-case letter or digit
go-github.com-smartystreets-goconvey @ 1.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 33
ghc-unsafe @ 0.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-th-reify-many @ 0.1.9description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-regex-tdfa @ 1.2.3.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 139
espeak-ng @ 1.50description

Validate package descriptions

description should start with an upper-case letter or digit
cfitsio @ 3.49description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 197
python2-testtools @ 2.3.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-warnings @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-catchlog @ 1.2.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python2-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pytest-cov' should probably be a native input
python2-nose-timer @ 0.7.5inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
python2-coverage-test-runner @ 1.15inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-warnings @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-sugar @ 0.9.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-lazy-fixture @ 0.6.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python-nose-timer @ 0.7.5inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
openfoam @ 4.1inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
mate-polkit @ 1.24.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-cython' should probably be a native input
awesome @ 4.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' 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
racket-minimal @ 7.8patch-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
python2-testtools-bootstrap @ 2.3.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
kodi-wayland @ 18.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.2-rsvg @ 2.18.1-0.05c6a2fpatch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gtk+ @ 2.24.32patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2306 is way too long (93 characters)
texlive-latex-l3packages @ 51265formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1142 is way too long (91 characters)
openfoam @ 4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 146 is way too long (91 characters)
omnitux @ 1.2.1formatting

Look for formatting issues in the source

line 580 is way too long (99 characters)
mate-panel @ 1.24.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 509 is way too long (91 characters)
malcontent @ 0.8.0formatting

Look for formatting issues in the source

line 165 is way too long (91 characters)
libsecp256k1 @ 20191213-1.d644ddaformatting

Look for formatting issues in the source

line 1043 is way too long (106 characters)
java-picard @ 2.3.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4009 is way too long (117 characters)
help2man @ 1.47.13formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 809, column 0
go-github.com-smartystreets-goconvey @ 1.6.3formatting

Look for formatting issues in the source

line 627 is way too long (91 characters)
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

line 481 is way too long (107 characters)
ghc-xdg-basedir @ 0.2.2formatting

Look for formatting issues in the source

line 14640 is way too long (93 characters)
ghc-vector @ 0.12.0.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ghc-th-orphans @ 0.13.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 12529 is way too long (250 characters)
geany @ 1.36formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
gcompris @ 17.05formatting

Look for formatting issues in the source

line 135 is way too long (96 characters)
flite @ 2.1formatting

Look for formatting issues in the source

line 90 is way too long (419 characters)
discrover @ 1.6.0formatting

Look for formatting issues in the source

line 2764 is way too long (91 characters)
childsplay @ 3.4formatting

Look for formatting issues in the source

line 489 is way too long (92 characters)
chez-srfi @ 1.0formatting

Look for formatting issues in the source

line 245 is way too long (91 characters)
atril @ 1.22.0formatting

Look for formatting issues in the source

line 744 is way too long (92 characters)
at-spi2-core @ 2.34.0formatting

Look for formatting issues in the source

line 653 is way too long (97 characters)
lxqt @ 0.15.0inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
lxqt-session @ 0.15.0formatting

Look for formatting issues in the source

line 863 is way too long (100 characters)
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1346, column 0
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1347, column 0
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1348, column 0
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1349, column 0
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1350, column 0
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1352, column 0
xygrib @ 1.2.6.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 256
u-boot-wandboard @ 2020.07description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
tor @ 0.4.4.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 574
robin-map @ 0.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 281
r-yapsa @ 1.14.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 93, 96
r-rgadem @ 2.36.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-bioassayr @ 1.26.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-xsge @ 2020.09.07description

Validate package descriptions

description should start with an upper-case letter or digit
python-mypy @ 0.782description

Validate package descriptions

use @code or similar ornament instead of quotes
jucipp @ 1.6.1description

Validate package descriptions

description should start with an upper-case letter or digit
ibus-libhangul @ 1.5.3description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-hxt-unicode @ 9.0.2.4description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
tao @ 1.0-beta-10May2006inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
tao @ 1.0-beta-10May2006inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
spice-gtk @ 0.37inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-cython' 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
qucs @ 0.0.19-0.b4f27d9inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-pytest-django @ 3.10.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'swig' should probably be a native input
osm-gps-map @ 1.1.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'doxygen' should probably be a native input
libvirt-glib @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
lepton-eda @ 1.9.11-20200604inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
keybinder-3.0 @ 0.3.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
geda-gaf @ 1.10.0inputs-should-be-native

Identify inputs that should be native inputs

'm4' 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
electron-cash @ 4.1.1inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
dico @ 2.10inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
tegola @ 0.7.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
qucs-s @ 0.0.21source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-mapnik @ 3.0.16source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
librecad @ 2.1.3source-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
ctl @ 1.5.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
u-boot-qemu-riscv64-smode @ 2020.07patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
qemu-minimal @ 5.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
openssh-sans-x @ 8.4p1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
openexr @ 2.5.2patch-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
libstdc++-doc @ 9.3.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
libgeotiff @ 1.5.1patch-file-names

Validate file names and availability of patches

libgeotiff-adapt-test-script-for-proj-6.2.patch: file name is too long
libgccjit @ 9.3.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
grantleetheme @ 20.04.1patch-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++ @ 9.3.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
gcc-objc++ @ 7.5.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
emacs-next @ 28.0.50-0.2ea3466patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
audiofile @ 0.3.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

audiofile-division-by-zero-BlockCodec-runPull.patch: file name is too long
android-libziparchive @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 1126 is way too long (95 characters)
virt-manager @ 2.2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 641 is way too long (93 characters)
u-boot-tools @ 2020.07formatting

Look for formatting issues in the source

line 509 is way too long (91 characters)
u-boot-tools @ 2020.07formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 641 is way too long (93 characters)
u-boot-pinebook @ 2020.07formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
u-boot-nintendo-nes-classic-edition @ 2020.07formatting

Look for formatting issues in the source

line 641 is way too long (93 characters)
u-boot-mx6cuboxi @ 2020.07formatting

Look for formatting issues in the source

line 641 is way too long (93 characters)
u-boot-malta @ 2020.07formatting

Look for formatting issues in the source

line 641 is way too long (93 characters)
u-boot-cubietruck @ 2020.07formatting

Look for formatting issues in the source

line 641 is way too long (93 characters)
u-boot-cubieboard @ 2020.07formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 682 is way too long (95 characters)
u-boot-a20-olinuxino-micro @ 2020.07formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 641 is way too long (93 characters)
sdsl-lite @ 2.1.1formatting

Look for formatting issues in the source

line 234 is way too long (145 characters)
r-unifiedwmwqpcr @ 1.24.0formatting

Look for formatting issues in the source

line 7152 is way too long (92 characters)
r-monocle @ 2.16.0formatting

Look for formatting issues in the source

line 2924 is way too long (101 characters)
r-lumi @ 2.40.0formatting

Look for formatting issues in the source

line 3344 is way too long (95 characters)
r-hsmmsinglecell @ 1.2.0formatting

Look for formatting issues in the source

line 1015 is way too long (95 characters)
r-genomicinteractions @ 1.22.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 475 is way too long (92 characters)
php @ 7.4.11formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 285 is way too long (92 characters)
patchwork @ 2.2.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
openmpi @ 4.0.5formatting

Look for formatting issues in the source

line 254 is way too long (94 characters)
openmpi @ 4.0.5formatting

Look for formatting issues in the source

line 256 is way too long (96 characters)
opencv @ 3.4.3formatting

Look for formatting issues in the source

line 363 is way too long (132 characters)
nyxt @ 2-pre-release-2formatting

Look for formatting issues in the source

line 485 is way too long (99 characters)
nyxt @ 2-pre-release-2formatting

Look for formatting issues in the source

line 518 is way too long (100 characters)
minizip @ 1.2.11formatting

Look for formatting issues in the source

line 154 is way too long (115 characters)
meshlab @ 2020.06formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
maven-surefire-plugin @ 3.0.0-M4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3606 is way too long (111 characters)
librime @ 1.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 919 is way too long (106 characters)
kpackage @ 5.70.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2296 is way too long (113 characters)
java-surefire-booter @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3269 is way too long (107 characters)
git-crypt @ 0.6.0formatting

Look for formatting issues in the source

line 771 is way too long (91 characters)
ghc-hxt-unicode @ 9.0.2.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 630 is way too long (99 characters)
freehdl @ 0.0.8formatting

Look for formatting issues in the source

line 1791 is way too long (104 characters)
fdroidserver @ 1.1.9formatting

Look for formatting issues in the source

line 940 is way too long (106 characters)
fc-host-tools @ 13formatting

Look for formatting issues in the source

line 1207 is way too long (122 characters)
fastboot @ 7.1.2_r36formatting

Look for formatting issues in the source

line 700 is way too long (105 characters)
extra-cmake-modules @ 5.70.0formatting

Look for formatting issues in the source

line 112 is way too long (91 characters)
cryptsetup-static @ 2.3.4formatting

Look for formatting issues in the source

line 102 is way too long (93 characters)
calibre @ 4.18.0formatting

Look for formatting issues in the source

line 245 is way too long (93 characters)
bazaar @ 2.7.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 560 is way too long (93 characters)
audacity @ 2.4.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
android-safe-iop @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 277, column 20
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 385 is way too long (97 characters)
sky @ 1.2description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-seqlogo @ 1.54.3description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 133, 136, 139
r-cardata @ 3.0-4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 45, 56
r-biomart @ 2.44.1description

Validate package descriptions

description should start with an upper-case letter or digit
python-rpy2 @ 3.3.5description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
mrrescue @ 1.02edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 2
mosquitto @ 1.6.12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 347
kget @ 20.04.1description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 798
guile2.2-email @ 0.2.2description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-commonmark @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.0-commonmark @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
guile-stis-parser @ 1.2.4.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 117
guile-dbd-sqlite3 @ 2.1.6description

Validate package descriptions

description should start with an upper-case letter or digit
chroma @ 1.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 33
variant-tools @ 3.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
rust-dav1d-sys @ 0.3.2inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' 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
quaternion @ 0.0.9.4einputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-cython' should probably be a native input
python-trezor-agent @ 0.13.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'swig' should probably be a native input
guile2.2-gi @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile-gi @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
g-golf @ 0.1.0-822.84e894einputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'swig' should probably be a native input
conda @ 4.8.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
tensorflow @ 1.9.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
poezio @ 0.13.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
crawl-tiles @ 0.25.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
unbound @ 1.10.1formatting

Look for formatting issues in the source

trailing white space on line 683
unbound @ 1.10.1formatting

Look for formatting issues in the source

trailing white space on line 719
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1622 is way too long (137 characters)
symmetrica @ 2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9336 is way too long (118 characters)
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 2204 is way too long (114 characters)
ri-li @ 2.0.1formatting

Look for formatting issues in the source

line 9432 is way too long (100 characters)
queen-it @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9233 is way too long (205 characters)
queen-fr @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9233 is way too long (205 characters)
queen @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9233 is way too long (205 characters)
python2-fastlmm @ 0.2.21formatting

Look for formatting issues in the source

line 1060 is way too long (92 characters)
python-rpy2 @ 3.3.5formatting

Look for formatting issues in the source

line 5687 is way too long (104 characters)
python-rpy2 @ 3.3.5formatting

Look for formatting issues in the source

line 5694 is way too long (104 characters)
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 6742, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 6743, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 5872, column 26
mkvtoolnix @ 50.0.0formatting

Look for formatting issues in the source

line 904 is way too long (96 characters)
lure-it @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9133 is way too long (93 characters)
lure @ 1.1formatting

Look for formatting issues in the source

line 9133 is way too long (93 characters)
kget @ 20.04.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
guile-dbi @ 2.1.6formatting

Look for formatting issues in the source

line 1332 is way too long (94 characters)
giac @ 1.6.0-25formatting

Look for formatting issues in the source

line 365 is way too long (95 characters)
gap @ 4.11.0formatting

Look for formatting issues in the source

line 1167 is way too long (98 characters)
freeorion @ 0.4.10formatting

Look for formatting issues in the source

line 9517 is way too long (92 characters)
freedink-engine @ 109.6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2760, column 0
einstein @ 2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 1038, column 0
drascula @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 8108, column 18
btanks @ 0.9.8083formatting

Look for formatting issues in the source

tabulation on line 8109, column 17
perl-class-load @ 0.25description

Validate package descriptions

use @code or similar ornament instead of quotes
sbcl-trivial-gray-streams @ 0.0.0-1.ebd59b1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 75
sbcl-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.ebd59b1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
sbcl-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 955 is way too long (98 characters)
rust @ 1.26.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4647 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
ecl-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 137 is way too long (96 characters)
netdde @ 2.6.32.65-1.4a1016fderivation

Report failure to compile a package to a derivation

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

Report failure to compile a package to a derivation

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

Report failure to compile a package to a derivation

failed to create i686-gnu derivation: could not find bootstrap binary 'tar' for system 'i686-gnu'
libcanberra-gtk2 @ 0.30patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
abseil-cpp @ 20200225.2formatting

Look for formatting issues in the source

line 616 is way too long (116 characters)
abseil-cpp @ 20200225.2formatting

Look for formatting issues in the source

line 617 is way too long (144 characters)
catdoc @ 0.95description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 157
zathura-pdf-poppler @ 0.3.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 472 is way too long (93 characters)
krona-tools @ 2.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 472 is way too long (92 characters)
system-config-printer @ 1.5.12inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gnome-contacts @ 3.34inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
mongodb @ 3.4.10source-unstable-tarball

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Look for formatting issues in the source

tabulation on line 693, column 18
zeitgeist @ 1.0.2formatting

Look for formatting issues in the source

tabulation on line 696, column 18
mongodb @ 3.4.10formatting

Look for formatting issues in the source

line 591 is way too long (99 characters)
gnome-keyring @ 3.34.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1338 is way too long (91 characters)
glade @ 3.36.0formatting

Look for formatting issues in the source

line 3031 is way too long (91 characters)
rust-serde-urlencoded @ 0.6.1description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
rust-libnghttp2-sys @ 0.1.4+1.41.0inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
rust-parking-lot @ 0.11.0formatting

Look for formatting issues in the source

line 17681 is way too long (102 characters)
rust-packed-struct @ 0.3.0formatting

Look for formatting issues in the source

tabulation on line 32822, column 0
rust-packed-struct @ 0.3.0formatting

Look for formatting issues in the source

tabulation on line 32824, column 0
rust-packed-struct @ 0.3.0formatting

Look for formatting issues in the source

tabulation on line 32825, column 0
rust-nix @ 0.15.0formatting

Look for formatting issues in the source

line 15829 is way too long (93 characters)
rust-inflections @ 1.1.1formatting

Look for formatting issues in the source

line 32923 is way too long (107 characters)
rust-inflections @ 1.1.1formatting

Look for formatting issues in the source

line 32925 is way too long (107 characters)
rust-gimli @ 0.20.0formatting

Look for formatting issues in the source

line 10026 is way too long (91 characters)
rust-bitstream-io @ 0.8.5formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2222 is way too long (111 characters)
rust-async-compression @ 0.3.5formatting

Look for formatting issues in the source

line 1170 is way too long (92 characters)
rav1e @ 0.3.3inputs-should-be-native

Identify inputs that should be native inputs

'nasm' should probably be a native input
gst-transcoder @ 1.12.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
restinio @ 0.6.1.1formatting

Look for formatting issues in the source

line 3286 is way too long (105 characters)
restinio @ 0.6.1.1formatting

Look for formatting issues in the source

line 3300 is way too long (95 characters)
restbed @ 4.6-1.6eb385fformatting

Look for formatting issues in the source

line 3261 is way too long (92 characters)
gaupol @ 1.7formatting

Look for formatting issues in the source

line 4362 is way too long (95 characters)
mergerfs @ 2.31.0formatting

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
glusterfs @ 7.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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
xdg-user-dirs @ 0.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
sbcl-quri @ 0.1.0-2.b53231cdescription

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 395
qtwebglplugin @ 5.14.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 244
python-pyfit-sne @ 1.0.1description

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-jsch-agentproxy-usocket-jna @ 0.0.8description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
java-fasterxml-jackson-core @ 2.9.4description

Validate package descriptions

description should not be empty
ecl-quri @ 0.1.0-2.b53231cdescription

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
cl-quri @ 0.1.0-2.b53231cdescription

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
cl-circular-streams @ 0.1.0-1.e770baddescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 79
udiskie @ 2.1.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gtk-doc' should probably be a native input
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
qwt @ 6.1.5inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
python2-pyqt @ 5.14.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-cython' should probably be a native input
python-pyqt-without-qtwebkit @ 5.14.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-cython' should probably be a native input
ecl-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
java-xmlunit-matchers @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-xmlunit-legacy @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-xmlunit @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-xerial-core @ 2.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-woodstox-core @ 5.0.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-stringtemplate @ 4.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-stax2-api @ 4.0.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-powermock-modules-junit4-common @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-archiver @ 4.2.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-tinybundles @ 2.1.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-native-access-platform @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-native-access @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-mvel2 @ 2.3.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-microemulator-cldc @ 2.0.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-mail @ 1.6.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-logback-core @ 1.2.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-logback-classic @ 1.2.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-lmax-disruptor @ 3.3.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-usocket-nc @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-usocket-jna @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-sshagent @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-pageant @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-jsch @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-core @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-connector-factory @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-joda-time @ 2.9.9source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-joda-convert @ 1.9.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jline @ 2.14.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jline @ 1.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-jms-api-spec @ 2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-interceptors-api-spec @ 1.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-el-api-spec @ 3.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jansi-native @ 1.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jansi @ 1.16source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-hawtjni @ 1.15source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-gson @ 2.8.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-modules-base-mrbean @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-modules-base-jaxb @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-dataformat-yaml @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-dataformat-xml @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-databind @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-core @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-annotations @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-datanucleus-javax-persistence @ 2.2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-cdi-api @ 2.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-pyqt @ 5.14.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long
java-powermock-reflect @ 1.7.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

java-apache-ivy-port-to-latest-bouncycastle.patch: file name is too long
java-antlr4-runtime @ 4.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gtk+ @ 3.24.23patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
vcflib @ 1.0.1formatting

Look for formatting issues in the source

line 15148 is way too long (92 characters)
sbcl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10926 is way too long (110 characters)
salmon @ 0.13.1formatting

Look for formatting issues in the source

line 11716 is way too long (99 characters)
qtserialport @ 5.14.2formatting

Look for formatting issues in the source

line 1044 is way too long (115 characters)
qtsensors @ 5.14.2formatting

Look for formatting issues in the source

line 893 is way too long (97 characters)
qtremoteobjects @ 5.14.2formatting

Look for formatting issues in the source

line 1516 is way too long (94 characters)
qtmultimedia @ 5.14.2formatting

Look for formatting issues in the source

line 936 is way too long (96 characters)
qtbase @ 5.14.2formatting

Look for formatting issues in the source

line 445 is way too long (96 characters)
qtbase @ 5.14.2formatting

Look for formatting issues in the source

line 572 is way too long (97 characters)
qtbase @ 5.14.2formatting

Look for formatting issues in the source

line 577 is way too long (94 characters)
qtbase @ 5.14.2formatting

Look for formatting issues in the source

line 579 is way too long (94 characters)
python-pyqt @ 5.14.2formatting

Look for formatting issues in the source

line 2061 is way too long (105 characters)
plymouth @ 0.9.4formatting

Look for formatting issues in the source

line 1833 is way too long (91 characters)
phast @ 1.5formatting

Look for formatting issues in the source

tabulation on line 15431, column 30
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2389, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2390, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2391, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2392, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2393, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2394, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2395, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2396, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2397, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2402, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2403, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2347, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2348, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2349, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2350, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2351, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2352, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2353, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2354, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2355, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2356, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2357, column 0
localed @ 241formatting

Look for formatting issues in the source

line 626 is way too long (96 characters)
linux-pam @ 1.4.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
java-testng @ 6.14.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9253 is way too long (110 characters)
java-openjfx-base @ 8.202formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2631 is way too long (99 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 11577 is way too long (92 characters)
java-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9664 is way too long (93 characters)
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 7278, column 20
java-eclipse-sisu-plexus @ 0.3.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 12292 is way too long (91 characters)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

line 5820 is way too long (91 characters)
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 12650 is way too long (101 characters)
icedtea @ 3.7.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1455 is way too long (100 characters)
freebayes @ 1.0.2-1.3ce827dformatting

Look for formatting issues in the source

tabulation on line 15223, column 28
fastahack @ 1.0.0formatting

Look for formatting issues in the source

line 15037 is way too long (91 characters)
ecl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10926 is way too long (110 characters)
dropseq-tools @ 1.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 12295, column 0
cl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8384 is way too long (100 characters)
xwallpaper @ 0.6.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 72
xftwidth @ 20170402description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 96, 234
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1613, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1614, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1616, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1617, column 0
python2-html2text @ 2019.8.11description

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
perl-specio @ 0.38description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 185, 314
perl-file-which @ 1.23description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-file-readbackwards @ 1.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-extutils-pkgconfig @ 1.16inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
python-tornado @ 5.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9352 is way too long (97 characters)
r-xyz @ 0.2description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 105, 128
r-topicmodels @ 0.2-11description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-survminer @ 0.4.8description

Validate package descriptions

use @code or similar ornament instead of quotes
r-sapa @ 2.0-2description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-r2glmm @ 0.1.2description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-iml @ 0.10.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-hapassoc @ 1.2-8description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 92, 113
r-dorng @ 1.8.2description

Validate package descriptions

use @code or similar ornament instead of quotes
r-diagram @ 1.6.5description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 242
r-clusterr @ 1.2.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 606, 945
r-circular @ 0.4-93description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-brms @ 2.13.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 109, 532, 653, 784
r-bootstrap @ 2019.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 92, 105
r-arm @ 1.11-2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 46, 60
r-haplo-stats @ 1.8.5formatting

Look for formatting issues in the source

line 14289 is way too long (103 characters)
r-gamlss-dist @ 5.1-7formatting

Look for formatting issues in the source

line 12871 is way too long (91 characters)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 15512 is way too long (96 characters)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 15526 is way too long (96 characters)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 15533 is way too long (117 characters)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 15540 is way too long (100 characters)
r-colourpicker @ 1.1.0formatting

Look for formatting issues in the source

line 12980 is way too long (94 characters)
r-abps @ 0.3formatting

Look for formatting issues in the source

line 8343 is way too long (93 characters)
sonata @ 1.7b1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
julia @ 1.5.2formatting

Look for formatting issues in the source

line 299 is way too long (107 characters)
julia @ 1.5.2formatting

Look for formatting issues in the source

line 301 is way too long (106 characters)
sendmail @ 8.15.2inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
mailutils @ 3.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
guile2.2-mailutils @ 3.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
python-mailman-hyperkitty @ 1.1.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python-mailman-hyperkitty @ 1.1.0formatting

Look for formatting issues in the source

line 3083 is way too long (168 characters)
ocaml4.07-sexplib @ 0.11.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 304
dune-configurator @ 2.7.1description

Validate package descriptions

description should not be empty
ocaml4.07-sedlex @ 2.1formatting

Look for formatting issues in the source

line 2181 is way too long (97 characters)
python2-pygame @ 1.9.4description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 123
love-nuklear @ v2.6-1.fef4e00formatting

Look for formatting issues in the source

trailing white space on line 723
pan @ 0.146description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
hackrf @ 2018.01.1-0.43e6f99description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-vcsh @ 0.4.4description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-trashed @ 1.9.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 178
emacs-swiper @ 0.13.1description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-pyvenv @ 1.21description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-nhexl-mode @ 1.5description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-hercules @ 0.2.1description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 220
emacs-el-x @ 0.3.1description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-dhall-mode @ 0.1.3-1.484bcf8description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
emacs-windsize @ 0.1-1.62c2846source-file-name

Validate file names of sources

the source file name should contain 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-no-x-toolkit @ 0.24patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-telega @ 0.6.28-0.e539967formatting

Look for formatting issues in the source

line 23105 is way too long (99 characters)
emacs-telega @ 0.6.28-0.e539967formatting

Look for formatting issues in the source

tabulation on line 23127, column 0
emacs-telega @ 0.6.28-0.e539967formatting

Look for formatting issues in the source

tabulation on line 23128, column 0
emacs-telega @ 0.6.28-0.e539967formatting

Look for formatting issues in the source

tabulation on line 23131, column 0
emacs-telega @ 0.6.28-0.e539967formatting

Look for formatting issues in the source

tabulation on line 23135, column 0
emacs-sqlite @ 1.0-0.dad42b8formatting

Look for formatting issues in the source

tabulation on line 4192, column 0
emacs-sqlite @ 1.0-0.dad42b8formatting

Look for formatting issues in the source

tabulation on line 4193, column 0
emacs-mit-scheme-doc @ 20140203formatting

Look for formatting issues in the source

line 5540 is way too long (94 characters)
emacs-gtk-look @ 29formatting

Look for formatting issues in the source

line 19156 is way too long (94 characters)
emacs-exwm @ 0.24formatting

Look for formatting issues in the source

line 11540 is way too long (96 characters)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 21487 is way too long (91 characters)
python2-psutil @ 5.7.2description

Validate package descriptions

description should start with an upper-case letter or digit
python-psutil @ 5.7.2description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-gdscript-mode @ 1.4.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
guile3.0-ncurses-with-gpm @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-ncurses @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
guile-ncurses-with-gpm @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
python2-hacking @ 1.1.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python2-pyflakes@2.2.0 and python2-pyflakes@1.2.3 collide
python-requests @ 2.20.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-urllib3@1.24.3 and python-urllib3@1.25.9 collide
python-hyperkitty @ 1.3.3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-django@2.2.16 and python-django@3.1.1 collide
python-hacking @ 1.1.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-pep8@1.7.0 and python-pep8@1.5.7 collide
maven-surefire-plugin @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide
maven-resolver-provider @ 3.6.1profile-collisions

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide
java-sonatype-aether-impl @ 1.7profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-forge-parent-pom@6 and java-sonatype-forge-parent-pom@10 collide
xen @ 4.13.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
icedove @ 78.3.2formatting

Look for formatting issues in the source

line 1193 is way too long (98 characters)
icedove @ 78.3.2formatting

Look for formatting issues in the source

line 1348 is way too long (105 characters)
icedove @ 78.3.2formatting

Look for formatting issues in the source

line 1350 is way too long (102 characters)
icecat @ 78.3.1-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 859 is way too long (102 characters)
icecat @ 78.3.1-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 951 is way too long (139 characters)
icecat @ 78.3.1-guix0-preview1formatting

Look for formatting issues in the source

line 957 is way too long (95 characters)
icecat @ 78.3.1-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1001 is way too long (94 characters)
icecat @ 78.3.1-guix0-preview1formatting

Look for formatting issues in the source

line 1003 is way too long (95 characters)
icecat @ 78.3.1-guix0-preview1formatting

Look for formatting issues in the source

line 1016 is way too long (98 characters)
icecat @ 78.3.1-guix0-preview1formatting

Look for formatting issues in the source

line 1145 is way too long (92 characters)
faad2 @ 2.8.8formatting

Look for formatting issues in the source

line 1709 is way too long (95 characters)
ecasound @ 2.9.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471
zita-resampler @ 1.6.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3184 is way too long (94 characters)
lua5.2-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
vim-full @ 8.2.1852formatting

Look for formatting issues in the source

line 213 is way too long (94 characters)
lua-tablepool @ 0.01formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1051 is way too long (108 characters)
lua-resty-lrucache @ 0.09formatting

Look for formatting issues in the source

line 941 is way too long (100 characters)
lua-resty-lrucache @ 0.09formatting

Look for formatting issues in the source

line 943 is way too long (119 characters)
lua-resty-lrucache @ 0.09formatting

Look for formatting issues in the source

line 944 is way too long (108 characters)
lua-resty-core @ 0.1.17formatting

Look for formatting issues in the source

line 906 is way too long (95 characters)
docker @ 19.03.12formatting

Look for formatting issues in the source

line 350 is way too long (95 characters)
docker @ 19.03.12formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 214 is way too long (105 characters)
r-squarem @ 2020.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1210 is way too long (92 characters)
perl-libxml @ 0.08description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
libxmlplusplus @ 2.40.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 1821
emacs-beancount @ 2.2.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libreoffice @ 6.4.6.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
sooperlooper @ 1.7.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
beets @ 1.4.9inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
sorcer @ 1.1.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-pycrypto @ 2.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-pyportmidi @ 217patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
vmpk @ 0.7.2formatting

Look for formatting issues in the source

line 2370 is way too long (91 characters)
solfege @ 3.22.2formatting

Look for formatting issues in the source

line 1538 is way too long (92 characters)
rosegarden @ 20.06formatting

Look for formatting issues in the source

line 4427 is way too long (94 characters)
rosegarden @ 20.06formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
librsvg @ 2.50.1formatting

Look for formatting issues in the source

line 3330 is way too long (104 characters)
gtklick @ 0.6.4formatting

Look for formatting issues in the source

line 973 is way too long (94 characters)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4901, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4902, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4903, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4904, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4906, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4913, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4914, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4915, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4916, column 0
drumstick @ 1.1.3formatting

Look for formatting issues in the source

line 2325 is way too long (91 characters)
beets-bandcamp @ 0.1.3formatting

Look for formatting issues in the source

line 3274 is way too long (149 characters)
python2-psycopg2 @ 2.8.6description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-psycopg2 @ 2.8.6description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
go-github-com-muesli-termenv @ 0.7.0description

Validate package descriptions

description should start with an upper-case letter or digit
go-github-com-mitchellh-reflectwalk @ 1.0.1description

Validate package descriptions

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

Identify inputs that should be native inputs

'itstool' should probably be a native input
terminator @ 1.91inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-pytest-httpbin @ 0.2.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-nose' should probably be a native input
lollypop @ 1.4.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
go-github-com-wtolson-go-taglib @ 0.0.0-0.6e68349inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
gnome-tweaks @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
gjs @ 1.58.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
eolie @ 0.9.99inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
sqlcipher @ 3.4.2source-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-xml @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-webapp @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-webapp @ 9.2.22source-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-util @ 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-servlet @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-server @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-server @ 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-security @ 9.2.22source-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-jmx @ 9.2.22source-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-io @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-http @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-http @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

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

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-bpf @ 5.4.71derivation

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

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

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'
java-plexus-sec-dispatcher @ 1.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide
java-plexus-digest @ 1.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@3.1 collide
java-plexus-container-default @ 1.7.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-component-metadata @ 1.7.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@13 and apache-parent-pom@21 collide
java-plexus-compiler-manager @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-compiler-javac @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-compiler-api @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide
java-plexus-archiver @ 4.2.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@6.1 collide
java-modello-test @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-plugins-xpp3 @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-plugins-xml @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-plugins-java @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-core @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-eclipse-sisu-plexus @ 0.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
antlr3 @ 3.5.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-stringtemplate@3.2.1 and java-stringtemplate@4.0.6 collide
python2-paste @ 3.0.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm64-generic @ 5.8.15patch-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.71patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-omap2plus @ 5.8.15patch-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.151patch-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.201patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-generic @ 5.8.15patch-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.71patch-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.151patch-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.201patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
http-parser @ 2.9.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
varnish @ 6.4.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 5190 is way too long (110 characters)
serf @ 1.3.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3558 is way too long (100 characters)
python-wtforms @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3558 is way too long (100 characters)
linux-libre-riscv64-generic @ 5.8.15formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre @ 5.8.15formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre @ 5.4.71formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre @ 4.9.239formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre @ 4.4.239formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre @ 4.19.151formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre @ 4.14.201formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
khal @ 0.10.1formatting

Look for formatting issues in the source

line 193 is way too long (113 characters)
go-github-com-rogpeppe-go-internal @ 1.6.1formatting

Look for formatting issues in the source

line 5709 is way too long (101 characters)
go-github-com-multiformats-go-multiaddr-net @ 1.6.3-0.1cb9a0eformatting

Look for formatting issues in the source

line 2984 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 2985 is way too long (93 characters)
go-github-com-multiformats-go-multiaddr @ 1.3.0-0.fe1c46fformatting

Look for formatting issues in the source

line 2941 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 2828 is way too long (95 characters)
go-github-com-mattn-go-shellwords @ 1.0.5-1.2444a32formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
go-github-com-libp2p-go-libp2p-peer @ 2.3.8-0.993d742formatting

Look for formatting issues in the source

line 2733 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 2789 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 2792 is way too long (93 characters)
go-github-com-gorilla-context @ 0.0.0-0.08b5f42formatting

Look for formatting issues in the source

line 1281 is way too long (164 characters)
go-github-com-davecgh-go-spew @ 1.1.1formatting

Look for formatting issues in the source

line 2396 is way too long (129 characters)
gdm @ 3.34.1formatting

Look for formatting issues in the source

line 7998 is way too long (103 characters)
python2-rst.linker @ 1.11description

Validate package descriptions

description should start with an upper-case letter or digit
python2-q @ 2.6description

Validate package descriptions

description should start with an upper-case letter or digit
python2-dbus @ 1.2.16description

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-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
snakemake @ 5.7.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python2-matplotlib @ 2.2.4inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-pytest-black @ 0.3.8inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-numpydoc @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-legacy-api-wrap @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-legacy-api-wrap @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python-jsonrpc-server @ 0.3.4inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-jsonrpc-server @ 0.3.4inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-jaraco-packaging @ 6.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-jaraco-packaging @ 6.1inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-jaraco-packaging @ 6.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-get-version @ 2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-get-version @ 2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
pelican @ 4.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python2-ipython-cluster-helper @ 0.6.4inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python2-setuptools' should probably not be an input at all
python-legacy-api-wrap @ 1.2inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-jaraco-packaging @ 6.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-ipython-cluster-helper @ 0.6.4inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
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-pep8 @ 1.7.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-cairocffi @ 0.9.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-robotframework @ 3.1.2patch-file-names

Validate file names and availability of patches

python-robotframework-honor-source-date-epoch.patch: file name is too long
python-numpy @ 1.17.3formatting

Look for formatting issues in the source

line 4380 is way too long (152 characters)
python-matplotlib @ 3.1.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4976 is way too long (105 characters)
python-ipython-documentation @ 7.9.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python2-asn1crypto @ 1.4.0description

Validate package descriptions

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

Validate package descriptions

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

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
ruby-rb-inotify @ 0.9.10description

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-gevent @ 20.6.2description

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-dukpy @ 0.3description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python2-argcomplete @ 1.11.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-pypandoc @ 1.5description

Validate package descriptions

description should start with an upper-case letter or digit
python-pyaml @ 18.11.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-py3status @ 3.21description

Validate package descriptions

description should start with an upper-case letter or digit
python-jinja2-time @ 0.2.0description

Validate package descriptions

use @code or similar ornament instead of quotes
python-gevent @ 20.6.2description

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-dukpy @ 0.3description

Validate package descriptions

description should start with an upper-case letter or digit
python-dnspython @ 1.16.0description

Validate package descriptions

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

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
ptpython2 @ 3.0.5description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
perftest @ 4.4-0.4description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
mdadm-static @ 4.1description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
guile3.0-ncurses @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
guile3.0-email @ 0.2.2description

Validate package descriptions

description should start with an upper-case letter or digit
guile3.0-commonmark @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
fakeroot @ 1.25.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 114, 240
f2fs-fsck-static @ 1.13.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 91
ecryptfs-utils @ 111description

Validate package descriptions

description should start with an upper-case letter or digit
c-blosc @ 1.18.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
slurp @ 1.2.0inputs-should-be-native

Identify inputs that should be native inputs

'scdoc' should probably be a native input
python2-xopen @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-setuptools-scm' should probably be a native input
python2-sure @ 1.4.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-mock' should probably be a native input
python2-setuptools-scm-git-archive @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-setuptools-scm' should probably be a native input
python2-pkgconfig @ 1.3.1inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
python2-numpydoc @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-docutils' should probably be a native input
python2-botocore @ 1.15.26inputs-should-be-native

Identify inputs that should be native inputs

'python2-docutils' should probably be a native input
python-xopen @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-sure @ 1.4.11inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-setuptools-scm-git-archive @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-rst2ansi @ 0.1.5inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-restructuredtext-lint @ 1.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-readme-renderer @ 26.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-pytest-check-links @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-pytest-check-links @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pkgconfig @ 1.3.1inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
python-pifpaf @ 2.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-mamba @ 0.11.1inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-m2r @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-iocapture @ 0.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-iocapture @ 0.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python-docusign-esign @ 3.1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-doc8 @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-conda @ 4.8.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-botocore @ 1.15.26inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-argh @ 0.26.2-1.dcd3253inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-argh @ 0.26.2-1.dcd3253inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-argh @ 0.26.2-1.dcd3253inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
guile3.0-mailutils @ 3.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
guile3.0-gi @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'm4' should probably be a native input
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
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
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-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
x86-energy-perf-policy @ 5.8.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
util-linux-with-udev @ 2.35.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

python2-larch-coverage-4.0a6-compatibility.patch: file name is too long
python2-babel @ 2.8.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
proot-static @ 5.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perl-parent @ 5.30.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perl-base @ 5.30.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
hplip-minimal @ 3.20.9patch-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
guile3.0-readline @ 3.0.4patch-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-mailutils @ 3.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-gnutls @ 3.6.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-gdbm-ffi @ 20120209.fa1d5b6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-fibers @ 1.0.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
guile2.2-gdbm-ffi @ 20120209.fa1d5b6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.0-gdbm-ffi @ 20120209.fa1d5b6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
guile-next @ 3.0.4patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gdb-minimal @ 9.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
enlightenment-wayland @ 0.24.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
cpupower @ 5.8.15patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.5-libsanitizer-mode-field.patch: file name is too long
binutils-static-stripped-tarball @ 2.35.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 3537 is way too long (104 characters)
texlive-latex-pgf @ 51265formatting

Look for formatting issues in the source

line 6474 is way too long (98 characters)
scons @ 3.0.4formatting

Look for formatting issues in the source

line 2178 is way too long (96 characters)
ruby-iruby @ 0.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1685 is way too long (99 characters)
perftest @ 4.4-0.4formatting

Look for formatting issues in the source

line 5441 is way too long (98 characters)
mesa @ 20.1.9formatting

Look for formatting issues in the source

line 298 is way too long (120 characters)
libjxr @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 372 is way too long (94 characters)
guile-readline @ 3.0.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 484 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 488
crda @ 3.18formatting

Look for formatting issues in the source

line 3644 is way too long (100 characters)
clang @ 11.0.0formatting

Look for formatting issues in the source

line 405 is way too long (91 characters)
python2 @ 2.7.18patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

line 182 is way too long (99 characters)
guile2.2-gnutls @ 3.6.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.0-gnutls @ 3.6.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gnutls-dane @ 3.6.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
openssl @ 1.1.1gformatting

Look for formatting issues in the source

tabulation on line 340, column 0
openssl @ 1.1.1gformatting

Look for formatting issues in the source

tabulation on line 341, column 0
openssl @ 1.1.1gformatting

Look for formatting issues in the source

tabulation on line 342, column 0
openssl @ 1.1.1gformatting

Look for formatting issues in the source

tabulation on line 343, column 0
openssl @ 1.1.1gformatting

Look for formatting issues in the source

tabulation on line 344, column 0
openssl @ 1.1.1gformatting

Look for formatting issues in the source

tabulation on line 345