Language
Lint warnings where the package name matches the query.
Lint warnings for specific lint checkers.
Lint warnings where the message matches the query.
Fields to return in the response.

Lint warnings

PackageLinterMessageLocation
r-boot @ 1.3-25description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
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
sh-z @ 1.11description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
python2-guzzle-sphinx-theme @ 0.7.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
python-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-repoze-autointerface @ 0.8inputs-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 @ 1.7.7inputs-should-be-native

Identify inputs that should be native inputs

'python2-docutils' 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
python2-reno @ 2.7.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' 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
python2-hacking @ 1.1.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
gnome-shell-extension-gsconnect @ 33inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' 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-debtcollector @ 1.19.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'flex' should probably be a native input
python-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-sphinxcontrib-programoutput @ 0.15inputs-should-be-native

Identify inputs that should be native inputs

'python2-sphinx' 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
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
gramps @ 5.1.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pbr' 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
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
rdmd @ 2.077.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
infiniband-diags @ 2.0.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
flatbuffers @ 1.10.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
nsis-i686 @ 3.05patch-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
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
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
libmhash @ 0.9.9.9patch-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
jfsutils-static @ 1.1.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
boost-static @ 1.72.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gobject-introspection @ 1.62.0patch-file-names

Validate file names and availability of patches

gobject-introspection-absolute-shlib-path.patch: file name is too long
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
libcanberra-gtk2 @ 0.30patch-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
ghostscript-with-cups @ 9.52patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
idutils @ 4.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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
nsis-x86_64 @ 3.05patch-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
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)
jose @ 10formatting

Look for formatting issues in the source

line 37 is way too long (92 characters)
abc @ 0.0-1.5ae4b97formatting

Look for formatting issues in the source

line 86 is way too long (95 characters)
js-filesaver @ 1.3.8formatting

Look for formatting issues in the source

line 392 is way too long (99 characters)
ldc @ 0.17.4formatting

Look for formatting issues in the source

line 137 is way too long (98 characters)
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 521 is way too long (92 characters)
js-mathjax @ 2.7.2formatting

Look for formatting issues in the source

line 90 is way too long (91 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
pth @ 2.0.7formatting

Look for formatting issues in the source

trailing white space on line 42
ldc @ 1.10.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
sdl-mixer @ 1.2.12formatting

Look for formatting issues in the source

line 260 is way too long (92 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)
efitools @ 1.9.2formatting

Look for formatting issues in the source

line 176 is way too long (113 characters)
python-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 90 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)
python2-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1116 is way too long (96 characters)
sdl-image @ 1.2.12formatting

Look for formatting issues in the source

line 223 is way too long (91 characters)
julia @ 1.4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 311 is way too long (106 characters)
python2 @ 2.7.17formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 290 is way too long (98 characters)
mingw-w64-x86_64 @ 7.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 196 is way too long (96 characters)
libsigsegv @ 2.12formatting

Look for formatting issues in the source

line 48 is way too long (133 characters)
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

line 213 is way too long (106 characters)
hyperledger-iroha @ 1.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 151 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
gmp @ 6.2.0formatting

Look for formatting issues in the source

line 82 is way too long (96 characters)
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)
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)
kget @ 20.04.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 169
ibus-anthy @ 1.5.9inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
mesa-opencl-icd @ 20.0.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mesa-headers @ 20.0.7patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 304 is way too long (120 characters)
kget @ 20.04.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
perl-test-object @ 0.08description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-test-file-contents @ 0.23description

Validate package descriptions

description should start with an upper-case letter or digit
perl-test2-plugin-nowarnings @ 0.06formatting

Look for formatting issues in the source

line 106 is way too long (92 characters)
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
perl-file-readbackwards @ 1.05description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 47
perl-file-which @ 1.23description

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
hplip-minimal @ 3.20.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perl-devel-globaldestruction @ 0.14description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-class-load @ 0.25description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-search-xapian @ 1.2.25.2description

Validate package descriptions

use @code or similar ornament instead of quotes
guile-static-stripped @ 3.0.2patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

line 471 is way too long (93 characters)
vorbis-tools @ 1.4.0formatting

Look for formatting issues in the source

trailing white space on line 323
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)
netpbm @ 10.78.3formatting

Look for formatting issues in the source

line 86 is way too long (127 characters)
glibc @ 2.31formatting

Look for formatting issues in the source

line 807 is way too long (98 characters)
wicd @ 1.7.4formatting

Look for formatting issues in the source

line 109 is way too long (95 characters)
zathura-pdf-poppler @ 0.3.0formatting

Look for formatting issues in the source

line 551 is way too long (107 characters)
dejagnu @ 1.6.2formatting

Look for formatting issues in the source

line 60 is way too long (91 characters)
guile-readline @ 3.0.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
guile-readline @ 3.0.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 381 is way too long (94 characters)
python-pybedtools @ 0.8.1description

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

line 575 is way too long (95 characters)
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
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
lua-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gdb-minimal @ 9.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
sbcl-md5 @ 2.0.4description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
cl-portable-threads @ 2.3-1.c0e61a1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3322 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
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)
gnumach @ 1.8-1.097f9cfderivation

Report failure to compile a package to a derivation

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

Report failure to compile a package to a derivation

failed to create i686-gnu derivation: could not find bootstrap binary 'tar' for system 'i686-gnu'
netdde @ 2.6.32.65-1.4a1016fderivation

Report failure to compile a package to a derivation

failed to create i686-gnu derivation: could not find bootstrap binary 'tar' for system 'i686-gnu'
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)
python2-minimal @ 2.7.17patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python @ 3.8.2formatting

Look for formatting issues in the source

line 448 is way too long (93 characters)
deutex @ 5.2.1description

Validate package descriptions

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

Validate package descriptions

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

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.9-libsanitizer-mode-field.patch: file name is too long
clang-runtime @ 3.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.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
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
icu4c-build-root @ 66.1patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
coreutils-minimal @ 8.32patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
mariadb @ 10.1.45formatting

Look for formatting issues in the source

line 842 is way too long (92 characters)
mariadb @ 10.1.45formatting

Look for formatting issues in the source

line 843 is way too long (91 characters)
wine64 @ 5.12formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
wine @ 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
c-blosc @ 1.18.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
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-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-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-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
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-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-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-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-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-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-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-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-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
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
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-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-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-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-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-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-shared-utils @ 3.2.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@16 and apache-parent-pom@18 collide
maven-settings-builder @ 3.6.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide
maven-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-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-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-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-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-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-settings @ 3.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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-aether-provider @ 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-artifact @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-plugin-api @ 3.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
java-openjfx-base @ 8.202patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
maven-model-builder @ 3.6.1patch-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
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-compat @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2324, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2325, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2326, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2327, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2328, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2329, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2330, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2331, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2332, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2333, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2608 is way too long (99 characters)
maven-resolver-impl @ 1.3.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1432 is way too long (100 characters)
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2366, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2367, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2368, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2369, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2370, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2371, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2372, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2373, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2374, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2379, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2380, column 0
icedtea @ 3.7.0formatting

Look for formatting issues in the source

line 1759 is way too long (109 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-wagon-provider-api @ 3.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/rn3d1ljc14jr897qs8z8gnra0fnrfpci-maven-wagon-provider-api-3.3.4 and /gnu/store/nbaplfhhfm9d521l2x6id4bbc2p8c9r6-maven-wagon-provider-api-3.3.4 collide
java-plexus-archiver @ 4.2.2source-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-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-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-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-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-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-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
antlr3 @ 3.5.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-stringtemplate@3.2.1 and java-stringtemplate@4.0.6 collide
java-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-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-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-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-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-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-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-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

line 3722 is way too long (112 characters)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4710 is way too long (107 characters)
java-commons-jxpath @ 1.3formatting

Look for formatting issues in the source

line 5963 is way too long (93 characters)
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 7189, column 20
java-sisu-build-api @ 0.0.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 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
wine64-staging @ 5.13inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 109 is way too long (93 characters)
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)
glibc-hurd-headers @ 2.31patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
libextractor @ 1.10formatting

Look for formatting issues in the source

line 128 is way too long (140 characters)
lxde-common @ 0.99.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python-coveralls @ 1.11.1inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' 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
clang @ 9.0.1formatting

Look for formatting issues in the source

line 405 is way too long (91 characters)
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 @ 3.5.2formatting

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.9.1formatting

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)
clang @ 10.0.0formatting

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 @ 8.0.0formatting

Look for formatting issues in the source

line 405 is way too long (91 characters)
mongodb @ 3.4.10formatting

Look for formatting issues in the source

line 589 is way too long (99 characters)
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
bison @ 3.6.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'm4' should probably be a native input
bison @ 3.5.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Validate package descriptions

use @code or similar ornament instead of quotes
ocaml-qcheck @ 0.12description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 51
rtl-sdr @ 0.6.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ocaml-zarith @ 1.9.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
ocaml-dose3 @ 5.0.1formatting

Look for formatting issues in the source

line 363 is way too long (92 characters)
elixir @ 1.10.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 75 is way too long (99 characters)
xfce4-volumed-pulse @ 0.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
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-clipman-plugin @ 1.6.1formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

line 520 is way too long (91 characters)
khal @ 0.10.1formatting

Look for formatting issues in the source

line 182 is way too long (113 characters)
python-pytest-isort @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' 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
pjproject-jami @ 2.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
serf @ 1.3.9formatting

Look for formatting issues in the source

line 1672 is way too long (92 characters)
libringclient @ 20200710.1.6bd18d2formatting

Look for formatting issues in the source

line 502 is way too long (105 characters)
krona-tools @ 2.7formatting

Look for formatting issues in the source

trailing white space on line 1021
jami @ 20200710.1.6bd18d2formatting

Look for formatting issues in the source

line 536 is way too long (92 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)
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)
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
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-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
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
qtserialport @ 5.14.2formatting

Look for formatting issues in the source

line 1062 is way too long (115 characters)
qtsensors @ 5.14.2formatting

Look for formatting issues in the source

line 911 is way too long (97 characters)
qtremoteobjects @ 5.14.2formatting

Look for formatting issues in the source

line 1534 is way too long (94 characters)
qtmultimedia @ 5.14.2formatting

Look for formatting issues in the source

line 954 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 569 is way too long (97 characters)
qtbase @ 5.14.2formatting

Look for formatting issues in the source

line 574 is way too long (94 characters)
qtbase @ 5.14.2formatting

Look for formatting issues in the source

line 576 is way too long (94 characters)
python-pyqt @ 5.14.2formatting

Look for formatting issues in the source

line 2079 is way too long (105 characters)
emacs-clang-rename @ 9.0.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.5-libsanitizer-mode-field.patch: file name is too long
tumbler @ 0.2.9formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
catdoc @ 0.95description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 157
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
i3-wm @ 4.18.2description

Validate package descriptions

description should start with an upper-case letter or digit
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
ghc-operational @ 0.2.3.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
ghc-llvm-hs-pure @ 9.0.0description

Validate package descriptions

description should start with an upper-case letter or digit
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-gtk2hs-buildtools @ 0.13.5.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
pandoc @ 2.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ghc-base-unicode-symbols @ 0.2.3formatting

Look for formatting issues in the source

line 953 is way too long (101 characters)
ghc @ 8.6.5formatting

Look for formatting issues in the source

line 591 is way too long (91 characters)
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
mergerfs @ 2.29.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
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
cfitsio @ 3.49description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 197
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-biomart @ 2.44.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
rseqc @ 3.0.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-cython' should probably be a native input
ncbi-vdb @ 2.10.6formatting

Look for formatting issues in the source

tabulation on line 5865, column 26
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)
discrover @ 1.6.0formatting

Look for formatting issues in the source

line 2764 is way too long (91 characters)
guile2.2-sjson @ 0.2.1description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-fibers @ 1.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libjxr @ 1.1description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
zbar @ 0.23inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
malcontent @ 0.8.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 634 is way too long (96 characters)
libjxr @ 1.1formatting

Look for formatting issues in the source

line 512 is way too long (95 characters)
flite @ 2.1formatting

Look for formatting issues in the source

line 90 is way too long (419 characters)
python2-pytest-subtesthack @ 0.1.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
openjpeg-data @ 2020.05.19description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
go-github.com-smartystreets-goconvey @ 1.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 33
template-glib @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-testtools @ 2.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
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-pygobject @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-pygobject @ 2.28.7inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

python2-pygobject-2-gi-info-type-error-domain.patch: file name is too long
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
telepathy-glib @ 0.24.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
go-github.com-smartystreets-goconvey @ 1.6.3formatting

Look for formatting issues in the source

line 615 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)
appstream-glib @ 0.7.17formatting

Look for formatting issues in the source

line 994 is way too long (93 characters)
gtk+ @ 3.24.20patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gtk+ @ 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
at-spi2-core @ 2.34.0formatting

Look for formatting issues in the source

line 653 is way too long (97 characters)
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
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)
mate-applets @ 1.24.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 917
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)
atril @ 1.22.0formatting

Look for formatting issues in the source

line 744 is way too long (92 characters)
python2-gst @ 1.16.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
r-dplyr @ 1.0.2description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-gnutls @ 3.6.12patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.0-gnutls @ 3.6.12patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gnutls-dane @ 3.6.12patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 336, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 337, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 338, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 339, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 340, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 341, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 342, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 343, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 344, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 345, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 346, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 347, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 348, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 349, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 350, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 351, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 352, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 353, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 354, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 365, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 366, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 378, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 379, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 380, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 496, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 497, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 498, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 499, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 500, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 501, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 502, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 503, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 504, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 506, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 507, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 508, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 509, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 510, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 512, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 513, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 514, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 515, column 0
ruby-rb-inotify @ 0.9.10description

Validate package descriptions

description should start with an upper-case letter or digit
ruby-iruby @ 0.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1718 is way too long (99 characters)
openfoam @ 4.1inputs-should-be-native

Identify inputs that should be native inputs

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

Look for formatting issues in the source

line 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)
unbound @ 1.10.1formatting

Look for formatting issues in the source

trailing white space on line 679
unbound @ 1.10.1formatting

Look for formatting issues in the source

trailing white space on line 715
libblockdev @ 2.24formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 754 is way too long (91 characters)
opencascade-occt @ 7.3.0p3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
scotch32 @ 6.0.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
mumps-openmpi @ 5.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mumps-metis-openmpi @ 5.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mumps-metis @ 5.2.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
debops @ 1.1.0patch-file-names

Validate file names and availability of patches

debops-constants-for-external-program-names.patch: file name is too long
zeitgeist @ 1.0.2formatting

Look for formatting issues in the source

tabulation on line 689, column 18
zeitgeist @ 1.0.2formatting

Look for formatting issues in the source

tabulation on line 692, column 18
superlu-dist @ 6.2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 891, column 0
pt-scotch32 @ 6.0.6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 3212, column 0
petsc @ 3.11.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
p4est @ 2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2858, column 0
mumps @ 5.2.1formatting

Look for formatting issues in the source

line 2772 is way too long (94 characters)
hdf-java @ 3.3.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 853 is way too long (91 characters)
python2-pygpgme @ 0.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
mate-polkit @ 1.24.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
chez-srfi @ 1.0formatting

Look for formatting issues in the source

line 245 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)
libreoffice @ 6.4.6.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
r-tidyr @ 1.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
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
gnome-keyring @ 3.34.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1334 is way too long (91 characters)
python-pytools @ 2020.4description

Validate package descriptions

use @code or similar ornament instead of quotes
tuxmath @ 2.0.3description

Validate package descriptions

description should start with an upper-case letter or digit
omnitux @ 1.2.1formatting

Look for formatting issues in the source

line 580 is way too long (99 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)
childsplay @ 3.4formatting

Look for formatting issues in the source

line 489 is way too long (92 characters)
xorg-server-xwayland @ 1.20.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xproto @ 7.0.31formatting

Look for formatting issues in the source

line 4999 is way too long (91 characters)
xf86-video-intel @ 2.99.917-16.5ca3ac1formatting

Look for formatting issues in the source

line 3036 is way too long (91 characters)
gtkspell3 @ 3.0.10inputs-should-be-native

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
sbcl-trivial-gray-streams @ 0.0.0-1.ebd59b1description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 75
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
sbcl-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 136 is way too long (96 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
racket-minimal @ 7.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-libxml2 @ 2.9.10patch-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
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 1820
perl-specio @ 0.38description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 185, 314
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 9302 is way too long (97 characters)
awesome @ 4.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' 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
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
texlive-fonts-iwona @ 0.995bdescription

Validate package descriptions

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

Check for autogenerated tarballs

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

Look for formatting issues in the source

line 6478 is way too long (98 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)
fakeroot @ 1.24description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 114, 240
proot-static @ 5.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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
go-github-com-muesli-termenv @ 0.7.0description

Validate package descriptions

description should start with an upper-case letter or digit
go-github-com-wtolson-go-taglib @ 0.0.0-0.6e68349inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
go-github-com-rogpeppe-go-internal @ 1.6.1formatting

Look for formatting issues in the source

line 5621 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 2922 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 2923 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 2879 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 2766 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 2671 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 2727 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 2730 is way too long (93 characters)
go-github-com-gorilla-context @ 0.0.0-0.08b5f42formatting

Look for formatting issues in the source

line 1219 is way too long (164 characters)
go-github-com-davecgh-go-spew @ 1.1.1formatting

Look for formatting issues in the source

line 2334 is way too long (129 characters)
guile2.2-email @ 0.2.2description

Validate package descriptions

description should start with an upper-case letter or digit
guile-dbd-sqlite3 @ 2.1.6description

Validate package descriptions

description should start with an upper-case letter or digit
guile-dbi @ 2.1.6formatting

Look for formatting issues in the source

line 1331 is way too long (94 characters)
python-mypy @ 0.782description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-hxt-unicode @ 9.0.2.4description

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

line 1442 is way too long (91 characters)
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
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)
extra-cmake-modules @ 5.70.0formatting

Look for formatting issues in the source

line 112 is way too long (91 characters)
mkbootimg @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
fdroidserver @ 1.1.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 277, column 20
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 385 is way too long (97 characters)
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
git-crypt @ 0.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 147 is way too long (93 characters)
variant-tools @ 3.1.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that shouldn't be inputs at all

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1061 is way too long (92 characters)
fc-host-tools @ 13formatting

Look for formatting issues in the source

line 1207 is way too long (122 characters)
python2-cryptography @ 2.9.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
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
python2-pycrypto @ 2.6.1patch-file-names

Validate file names and availability of patches

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

Validate package descriptions

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 1126 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)
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
libgccjit @ 9.3.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gcc-objc++ @ 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
samblaster @ 0.1.24description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 93, 96
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.1description

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-rgadem @ 2.36.0description

Validate package descriptions

description should start with an upper-case letter or digit
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-mixomics @ 6.12.2description

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-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-iclusterplus @ 1.24.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.4description

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-cardata @ 3.0-4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 45, 56
r-bseqsc @ 1.0-1.fef3f3edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 395
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-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
r-arm @ 1.11-2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 46, 60
python-rpy2 @ 3.3.5description

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'python-cython' 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
python-bbknn @ 1.3.6inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

line 15142 is way too long (92 characters)
salmon @ 0.13.1formatting

Look for formatting issues in the source

line 11710 is way too long (99 characters)
r-unifiedwmwqpcr @ 1.24.0formatting

Look for formatting issues in the source

line 7152 is way too long (92 characters)
r-squarem @ 2020.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1205 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-haplo-stats @ 1.8.5formatting

Look for formatting issues in the source

line 14257 is way too long (103 characters)
r-genomicinteractions @ 1.22.0formatting

Look for formatting issues in the source

line 2146 is way too long (92 characters)
r-gamlss-dist @ 5.1-7formatting

Look for formatting issues in the source

line 12841 is way too long (91 characters)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 15479 is way too long (96 characters)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 15493 is way too long (96 characters)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 15500 is way too long (117 characters)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 15507 is way too long (100 characters)
r-colourpicker @ 1.0formatting

Look for formatting issues in the source

line 12949 is way too long (94 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)
r-abps @ 0.3formatting

Look for formatting issues in the source

line 8313 is way too long (93 characters)
python-rpy2 @ 3.3.5formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 5689 is way too long (104 characters)
phast @ 1.5formatting

Look for formatting issues in the source

tabulation on line 15425, column 30
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)
java-surefire-booter @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3269 is way too long (107 characters)
freebayes @ 1.0.2-1.3ce827dformatting

Look for formatting issues in the source

tabulation on line 15217, column 28
fastahack @ 1.0.0formatting

Look for formatting issues in the source

line 15031 is way too long (91 characters)
dropseq-tools @ 1.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 12289, column 0
rapicorn @ 16.0.0inputs-should-be-native

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

file names of patches should start with the package name
wpa-supplicant-minimal @ 2.9description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
tor @ 0.4.4.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 574
dico @ 2.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
cryptsetup-static @ 2.3.4formatting

Look for formatting issues in the source

line 102 is way too long (93 characters)
sendmail @ 8.15.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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
alot @ 0.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
guile2.2-mailutils @ 3.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-rst.linker @ 1.11description

Validate package descriptions

description should start with an upper-case letter or digit
python2-psutil @ 5.7.2description

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

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

Validate package descriptions

use @code or similar ornament instead of quotes
snakemake @ 5.7.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python2-numpydoc @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
python2-matplotlib @ 2.2.4inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-restructuredtext-lint @ 1.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-numpydoc @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' 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
pelican @ 4.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' 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
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-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-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
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-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
scons @ 3.0.4formatting

Look for formatting issues in the source

line 2158 is way too long (96 characters)
python-numpy @ 1.17.3formatting

Look for formatting issues in the source

line 4328 is way too long (152 characters)
python-matplotlib @ 3.1.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4924 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
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
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-ncurses-with-gpm @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
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
hdf5-parallel-openmpi @ 1.10.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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
lepton-eda @ 1.9.11-20200604inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'libtool' should probably be a native input
qucs-s @ 0.0.21source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
librecad @ 2.1.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
meshlab @ 2020.06formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 245 is way too long (93 characters)
grantleetheme @ 20.04.1patch-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 606 is way too long (116 characters)
abseil-cpp @ 20200225.2formatting

Look for formatting issues in the source

line 607 is way too long (144 characters)
electron-cash @ 4.1.1inputs-should-be-native

Identify inputs that should be native inputs

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
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
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
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
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 2342 is way too long (91 characters)
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)
solfege @ 3.22.2formatting

Look for formatting issues in the source

line 1487 is way too long (92 characters)
rosegarden @ 20.06formatting

Look for formatting issues in the source

line 4388 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
gtklick @ 0.6.4formatting

Look for formatting issues in the source

line 922 is way too long (94 characters)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4862, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4863, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4864, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4865, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4867, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4874, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4875, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4876, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 4877, column 0
drumstick @ 1.1.3formatting

Look for formatting issues in the source

line 2297 is way too long (91 characters)
beets-bandcamp @ 0.1.3formatting

Look for formatting issues in the source

line 3235 is way too long (149 characters)
libvirt-glib @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
qemu-minimal @ 5.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xen @ 4.13.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
virt-manager @ 2.2.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libosinfo @ 1.7.1formatting

Look for formatting issues in the source

line 919 is way too long (106 characters)
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
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-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-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 @ 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-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
java-eclipse-sisu-plexus @ 0.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-powermock-reflect @ 1.7.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

java-apache-ivy-port-to-latest-bouncycastle.patch: file name is too long
java-antlr4-runtime @ 4.8patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
java-testng @ 6.14.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8986 is way too long (110 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 12025 is way too long (91 characters)
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 12383 is way too long (101 characters)
antlr4 @ 4.8formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8295 is way too long (100 characters)
docker @ 19.03.12formatting

Look for formatting issues in the source

line 351 is way too long (95 characters)
docker @ 19.03.12formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 217 is way too long (102 characters)
robin-map @ 0.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 281
sdsl-lite @ 2.1.1formatting

Look for formatting issues in the source

line 234 is way too long (145 characters)
icecat @ 78.3.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 855 is way too long (102 characters)
icecat @ 78.3.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 947 is way too long (139 characters)
icecat @ 78.3.0-guix0-preview1formatting

Look for formatting issues in the source

line 953 is way too long (95 characters)
icecat @ 78.3.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 997 is way too long (94 characters)
icecat @ 78.3.0-guix0-preview1formatting

Look for formatting issues in the source

line 999 is way too long (95 characters)
icecat @ 78.3.0-guix0-preview1formatting

Look for formatting issues in the source

line 1012 is way too long (98 characters)
icecat @ 78.3.0-guix0-preview1formatting

Look for formatting issues in the source

line 1141 is way too long (92 characters)
python2-psycopg2 @ 2.8.6description

Validate package descriptions

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

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-html2text @ 2019.8.11description

Validate package descriptions

description should start with an upper-case letter or digit
pan @ 0.146description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
python-pytest-django @ 3.10.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' 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
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
python2-paste @ 3.0.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-mailman-hyperkitty @ 1.1.0patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3554 is way too long (100 characters)
python-wtforms @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1175 is way too long (91 characters)
python-mailman-hyperkitty @ 1.1.0formatting

Look for formatting issues in the source

line 3072 is way too long (168 characters)
patchwork @ 2.2.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python2-q @ 2.6description

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

Validate package descriptions

description should start with an upper-case letter or digit
python-pyquery @ 1.2.17description

Validate package descriptions

description should start with an upper-case letter or digit
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-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
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-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-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-pytest-black @ 0.3.8inputs-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-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-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-get-version @ 2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-get-version @ 2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python-docusign-esign @ 3.1.0inputs-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
python-legacy-api-wrap @ 1.2inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-get-version @ 2.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
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
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-pep8 @ 1.7.0patch-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-configobj @ 5.0.6patch-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
go-github-com-mitchellh-reflectwalk @ 1.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
sonata @ 1.7b1inputs-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
java-native-access-platform @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-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
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 5722 is way too long (91 characters)
jucipp @ 1.6.1description

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
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
spice-gtk @ 0.37inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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
mkvtoolnix @ 50.0.0formatting

Look for formatting issues in the source

line 903 is way too long (96 characters)
gaupol @ 1.7formatting

Look for formatting issues in the source

line 4343 is way too long (95 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)
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
system-config-printer @ 1.5.12inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' 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
lollypop @ 1.2.32inputs-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
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
keybinder-3.0 @ 0.3.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gnome-tweaks @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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.98.1inputs-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
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
java-openmpi @ 4.0.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
upower @ 0.99.11formatting

Look for formatting issues in the source

line 5106 is way too long (110 characters)
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)
libsoup @ 2.70.0formatting

Look for formatting issues in the source

line 4565 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
glade @ 3.36.0formatting

Look for formatting issues in the source

line 2989 is way too long (91 characters)
gdm @ 3.34.1formatting

Look for formatting issues in the source

line 7914 is way too long (103 characters)
ibus-libhangul @ 1.5.3description

Validate package descriptions

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

Look for formatting issues in the source

line 328 is way too long (93 characters)
sky @ 1.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'swig' should probably be a native input
linux-libre-headers @ 4.9.237patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
crawl-tiles @ 0.25.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
sky @ 1.2formatting

Look for formatting issues in the source

line 9334 is way too long (118 characters)
ri-li @ 2.0.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6740, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 6741, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 6744, column 0
lure-it @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9131 is way too long (93 characters)
linux-libre-arm-omap2plus @ 4.14.199formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 811 is way too long (117 characters)
linux-libre @ 4.9.237formatting

Look for formatting issues in the source

line 811 is way too long (117 characters)
linux-libre @ 4.4.237formatting

Look for formatting issues in the source

line 811 is way too long (117 characters)
linux-libre @ 4.14.199formatting

Look for formatting issues in the source

line 811 is way too long (117 characters)
freeorion @ 0.4.10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2755, column 0
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
einstein @ 2.0formatting

Look for formatting issues in the source

line 4287 is way too long (96 characters)
drascula @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 8106, column 18
btanks @ 0.9.8083formatting

Look for formatting issues in the source

tabulation on line 8107, column 17
rust @ 1.26.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 745 is way too long (91 characters)
mrustc @ 0.9formatting

Look for formatting issues in the source

line 177 is way too long (123 characters)
emacs-gdscript-mode @ 1.2.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
emacs-dhall-mode @ 0.1.3-1.484bcf8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 89
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
texlive-fonts-lm @ 51265description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 93
perftest @ 4.4-0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
mdadm-static @ 4.1description

Validate package descriptions

description should start with an upper-case letter or digit
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
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
ecasound @ 2.9.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471
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
python-conda @ 4.8.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' 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
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
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
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.2patch-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.12patch-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-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-next @ 3.0.2patch-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
boost-with-python3 @ 1.72.0patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

line 3677 is way too long (93 characters)
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1610, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1611, column 0
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
wireless-tools @ 30.pre9formatting

Look for formatting issues in the source

line 3515 is way too long (104 characters)
vamp @ 2.6formatting

Look for formatting issues in the source

line 3158 is way too long (94 characters)
util-linux @ 2.35.1formatting

Look for formatting issues in the source

line 1487 is way too long (91 characters)
perftest @ 4.4-0.4formatting

Look for formatting issues in the source

line 5417 is way too long (98 characters)
linux-pam @ 1.3.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
guile-for-guile-emacs @ 2.1.2-1.15ca784formatting

Look for formatting issues in the source

line 493 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 497
faad2 @ 2.8.8formatting

Look for formatting issues in the source

line 1709 is way too long (95 characters)
crda @ 3.18formatting

Look for formatting issues in the source

line 3622 is way too long (100 characters)
audacity @ 2.4.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
openssh-sans-x @ 8.4p1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ppsspp @ 1.10.3description

Validate package descriptions

use @code or similar ornament instead of quotes
mosquitto @ 1.6.12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 347
quaternion @ 0.0.9.4einputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
vim-full @ 8.2.1770formatting

Look for formatting issues in the source

line 213 is way too long (94 characters)
pypy3 @ 7.3.1formatting

Look for formatting issues in the source

line 805 is way too long (91 characters)
iml @ 1.0.5description

Validate package descriptions

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

Look for formatting issues in the source

line 1402 is way too long (100 characters)
giac @ 1.6.0-23formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1165 is way too long (98 characters)
eigen @ 3.3.7formatting

Look for formatting issues in the source

tabulation on line 1036, column 0
xdg-user-dirs @ 0.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
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
plymouth @ 0.9.4formatting

Look for formatting issues in the source

line 1841 is way too long (91 characters)
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
ecl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
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
sbcl-cl-gobject-introspection @ 0.3-0.7b703e2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
cl-gobject-introspection @ 0.3-0.7b703e2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
sbcl-graph-json @ 0.0.0-0.78bf9ecpatch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
sbcl-graph-dot @ 0.0.0-0.78bf9ecpatch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
cl-graph @ 0.0.0-0.78bf9ecpatch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 14096 is way too long (110 characters)
cl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

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

Validate package descriptions

description should start with an upper-case letter or digit
rust-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-dav1d-sys @ 0.3.2inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 30420 is way too long (114 characters)
rust-packed-struct @ 0.3.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1929 is way too long (111 characters)
ocaml4.07-sexplib @ 0.11.0description

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

line 2095 is way too long (97 characters)
emacs-beancount @ 2.2.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-pygame @ 1.9.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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)
nginx-accept-language-module @ 0.0.0-1.2f69842formatting

Look for formatting issues in the source

line 470 is way too long (92 characters)
love-nuklear @ v2.6-1.fef4e00formatting

Look for formatting issues in the source

trailing white space on line 694
linux-libre-riscv64-generic @ 5.8.12derivation

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

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

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

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'
x86-energy-perf-policy @ 5.8.12patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perf @ 5.8.12patch-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.12patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name