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
perl-test-file-contents @ 0.23description

Validate package descriptions

description should start with an upper-case letter or digit
zn-poly @ 0.9.1description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
guile-stis-parser @ 0-1.6e85d37description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 117
cfitsio @ 3.47description

Validate package descriptions

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
java-iq80-snappy @ 0.4source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-snappy @ 1.0.3-rc3source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
spacefm @ 1.0.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ruby-spring @ 1.7.2source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
gourmet @ 0.17.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-snappy @ 1.1.7.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
gnumach @ 1.8derivation

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

Report failure to compile a package to a derivation

failed to create i686-gnu derivation: could not find bootstrap binary 'tar' for system 'i686-gnu'
gcc-objc @ 8.3.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
python2-mox3 @ 0.24.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gnumach-headers @ 1.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mrustc @ 0.8.0patch-file-names

Validate file names and availability of patches

mrustc-0.8.0-fix-variable-length-integer-receiving.patch: file name is too long
idutils @ 4.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
emacs-erlang @ 21.0.5patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
texlive-bin @ 20180414patch-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 @ 5.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
bazaar @ 2.7.0formatting

Look for formatting issues in the source

line 137 is way too long (93 characters)
lxde-common @ 0.99.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
java-jbzip2 @ 0.9.1formatting

Look for formatting issues in the source

line 264 is way too long (92 characters)
abc @ 0.0-1-5ae4b975cformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
gnumach-headers @ 1.8formatting

Look for formatting issues in the source

line 74 is way too long (93 characters)
ldc @ 0.17.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 48 is way too long (133 characters)
ocaml-dose3 @ 5.0.1formatting

Look for formatting issues in the source

line 355 is way too long (92 characters)
mrustc @ 0.8.0formatting

Look for formatting issues in the source

line 105 is way too long (95 characters)
dejagnu @ 1.6.1formatting

Look for formatting issues in the source

line 60 is way too long (91 characters)
plotutils @ 2.6formatting

Look for formatting issues in the source

trailing white space on line 79
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 450 is way too long (92 characters)
docbook-xml @ 4.5formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 64
go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 104 is way too long (92 characters)
jose @ 10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 176 is way too long (113 characters)
racket @ 7.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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
opencv @ 3.4.3formatting

Look for formatting issues in the source

line 282 is way too long (132 characters)
pth @ 2.0.7formatting

Look for formatting issues in the source

trailing white space on line 42
guile-wm @ 1.0-1.f3c7b3bformatting

Look for formatting issues in the source

line 126 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
busybox @ 1.29.3formatting

Look for formatting issues in the source

trailing white space on line 82
busybox @ 1.29.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 109 is way too long (95 characters)
python2-keystoneclient @ 1.8.1formatting

Look for formatting issues in the source

line 801 is way too long (102 characters)
texlive-bin @ 20180414formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 207, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 208, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 209, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 213, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 214, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 216, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 313, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 315, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 316, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 317, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 321, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 322, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 324, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 325, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 326, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 327, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 328, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 329, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 330, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 331, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 374, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 376, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 377, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 378, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 379, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 380, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 381, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 382, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 383, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 384, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 385, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 386, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 387, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 389, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 390, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 391, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 392, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 393, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 394, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 430, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 431, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 432, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 436, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 437, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 438, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 456, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 461, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 462, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 467, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 468, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 469, column 0
netpbm @ 10.78.3formatting

Look for formatting issues in the source

line 86 is way too long (127 characters)
editorconfig-core-c @ 0.12.3formatting

Look for formatting issues in the source

line 385 is way too long (97 characters)
catdoc @ 0.95description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 157
java-rsyntaxtextarea @ 2.6.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
containerd @ 1.2.5formatting

Look for formatting issues in the source

line 213 is way too long (102 characters)
wgetpaste @ 2.29formatting

Look for formatting issues in the source

line 99 is way too long (113 characters)
iml @ 1.0.5description

Validate package descriptions

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

Look for formatting issues in the source

trailing white space on line 1156
symmetrica @ 2.0formatting

Look for formatting issues in the source

line 1362 is way too long (100 characters)
eigen @ 3.3.5formatting

Look for formatting issues in the source

tabulation on line 941, column 0
lightgbm @ 2.0.12source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
vowpal-wabbit @ 8.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 514 is way too long (91 characters)
hypre-openmpi @ 2.15.1formatting

Look for formatting issues in the source

tabulation on line 3946, column 0
sh-z @ 1.11description

Validate package descriptions

use @code or similar ornament instead of quotes
guile2.0-commonmark @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
lua5.2-sec @ 0.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
lua-lgi @ 0.9.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
lua5.1-filesystem @ 1.6.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
lua-filesystem @ 1.6.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
lua5.1-sec @ 0.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
lua5.1-socket @ 3.0-rc1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
lua5.2-filesystem @ 1.6.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
lua5.2-socket @ 3.0-rc1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
tesseract-ocr @ 3.04.01source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
mkbootimg @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 422 is way too long (95 characters)
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 372 is way too long (97 characters)
mate-applets @ 1.22.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 78
texlive-lm @ 49435description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 93
gpsbabel @ 1.5.4inputs-should-be-native

Identify inputs that should be native inputs

'qttools' 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
ceph @ 13.2.6inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python2-pip' should probably not be an input at all
texlive-latex-hyperref @ 6.84a2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
icu4c @ 64.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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
python-cffi-documentation @ 1.11.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
oath-toolkit @ 2.6.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
perl-base @ 5.30.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
livestreamer @ 0.14.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
eudev-with-hwdb @ 3.2.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perl-parent @ 5.30.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
kiki-the-nano-bot @ 1.0.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
librime @ 1.5.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 94
calibre @ 3.42.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
aspell @ 0.60.6.1formatting

Look for formatting issues in the source

line 75 is way too long (101 characters)
atril @ 1.22.0formatting

Look for formatting issues in the source

line 771 is way too long (92 characters)
mate-panel @ 1.22.0formatting

Look for formatting issues in the source

line 696 is way too long (92 characters)
texlive-latex-l3packages @ 49435formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
mate-menus @ 1.22.0formatting

Look for formatting issues in the source

line 533 is way too long (91 characters)
glibc @ 2.29formatting

Look for formatting issues in the source

line 690 is way too long (98 characters)
ncurses @ 6.1-20190609formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 178 is way too long (94 characters)
librecad @ 2.1.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
glibc-locales-2.27 @ 2.28patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
dmraid @ 1.0.0.rc16-3formatting

Look for formatting issues in the source

line 677 is way too long (91 characters)
nanovg-for-extempore @ 0.7.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
stlink @ 1.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
xproto @ 7.0.31formatting

Look for formatting issues in the source

line 4768 is way too long (91 characters)
perl-class-load @ 0.25description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-devel-globaldestruction @ 0.14description

Validate package descriptions

use @code or similar ornament instead of quotes
gnutls-dane @ 3.6.9patch-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
guile2.0-gnutls @ 3.6.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xfce4-volumed-pulse @ 0.2.3description

Validate package descriptions

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
axoloti-runtime @ 1.0.12formatting

Look for formatting issues in the source

line 195 is way too long (96 characters)
lpsolve @ 5.5.2.5description

Validate package descriptions

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

Validate file names and availability of patches

file names of patches should start with the package name
rust @ 1.25.0formatting

Look for formatting issues in the source

line 696 is way too long (91 characters)
rust @ 1.26.2formatting

Look for formatting issues in the source

line 732 is way too long (94 characters)
python2-conda @ 4.3.16source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-conda @ 4.3.16source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
conda @ 4.3.16source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-anaconda-client @ 1.6.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-anaconda-client @ 1.6.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
conda @ 4.3.16formatting

Look for formatting issues in the source

line 717 is way too long (94 characters)
kodi-wayland @ 18.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-plexus-component-metadata @ 1.7.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
maven-builder-support @ 3.6.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
maven-wagon-file @ 3.1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1215 is way too long (118 characters)
perl-libxml @ 0.08description

Validate package descriptions

description should start with an upper-case letter or digit
ponymix @ 5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
pulsemixer @ 1.4.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
mesa-headers @ 19.2.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 293 is way too long (100 characters)
magit @ 2.90.1-2.c761d28patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
infiniband-diags @ 2.0.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
connman @ 1.37description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
syncthing @ 1.2.2formatting

Look for formatting issues in the source

line 96 is way too long (93 characters)
go-github-com-golang-protobuf-proto @ 1.3.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
nototools @ 20170925source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
rust @ 1.30.1formatting

Look for formatting issues in the source

tabulation on line 899, column 0
rust @ 1.31.1formatting

Look for formatting issues in the source

tabulation on line 927, column 0
rust @ 1.31.1formatting

Look for formatting issues in the source

tabulation on line 928, column 0
rust @ 1.31.1formatting

Look for formatting issues in the source

tabulation on line 929, column 0
rust @ 1.31.1formatting

Look for formatting issues in the source

tabulation on line 930, column 0
arm-trusted-firmware-rk3328 @ 2.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
arm-trusted-firmware-sun50i-a64 @ 2.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.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
mkvtoolnix @ 37.0.0formatting

Look for formatting issues in the source

line 408 is way too long (96 characters)
fstrcmp @ 0.7.D001description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 236
itk-snap @ 3.8.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
mgba @ 0.7.3inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
mingw-w64-i686 @ 6.0.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
mingw-w64-i686 @ 6.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 87 is way too long (91 characters)
mingw-w64-x86_64-winpthreads @ 6.0.0formatting

Look for formatting issues in the source

line 87 is way too long (91 characters)
mingw-w64-x86_64 @ 6.0.0formatting

Look for formatting issues in the source

line 87 is way too long (91 characters)
zathura-pdf-poppler @ 0.2.9formatting

Look for formatting issues in the source

line 472 is way too long (107 characters)
zathura-djvu @ 0.2.8formatting

Look for formatting issues in the source

line 392 is way too long (93 characters)
enlightenment-wayland @ 0.23.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
enlightenment @ 0.23.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 347 is way too long (99 characters)
libblockdev @ 2.23formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ruby-iruby @ 0.3formatting

Look for formatting issues in the source

line 414 is way too long (112 characters)
patchwork @ 2.1.4formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
dunst @ 1.4.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
go-github-com-gorilla-context @ 0.0.0-0.08b5f42formatting

Look for formatting issues in the source

line 1075 is way too long (164 characters)
nsis-i686 @ 3.04description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
nsis-i686 @ 3.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
nsis-x86_64 @ 3.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
nsis-i686 @ 3.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 118 is way too long (114 characters)
nsis-x86_64 @ 3.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 118 is way too long (114 characters)
glibc-locales-2.28 @ 2.28patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
libxdg-basedir @ 1.2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
localed @ 241formatting

Look for formatting issues in the source

line 450 is way too long (96 characters)
geany @ 1.36formatting

Look for formatting issues in the source

line 539 is way too long (125 characters)
libsigrok @ 0.5.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 212 is way too long (92 characters)
libchop @ 0.5.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gnome-tweak-tool @ 3.32.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
cgit @ 1.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
vlc @ 3.0.8formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1216 is way too long (107 characters)
cryptsetup-static @ 2.2.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 842 is way too long (100 characters)
bash @ 5.0.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
docker @ 18.09.5formatting

Look for formatting issues in the source

line 347 is way too long (95 characters)
docker @ 18.09.5formatting

Look for formatting issues in the source

line 383 is way too long (93 characters)
perl6-grammar-debugger @ 1.0.1-1.0375008description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 203
python-wxpython @ 4.0.7.post1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
nginx-accept-language-module @ 0.0.0-1.2f69842formatting

Look for formatting issues in the source

line 506 is way too long (92 characters)
ghc-hxt-unicode @ 9.0.2.4description

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

line 1251 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
guile-static-stripped-tarball @ 2.2.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 842 is way too long (94 characters)
gimp-resynthesizer @ 2.0.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 364, column 0
python-fpylll @ 0.4.1description

Validate package descriptions

description should start with an upper-case letter or digit
java-jblas @ 1.2.4description

Validate package descriptions

description should start with an upper-case letter or digit
xdg-user-dirs @ 0.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
tigervnc-server @ 1.9.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
go-github-com-mitchellh-go-homedir @ 1.0.0-0.ae18d6bformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2333 is way too long (93 characters)
udisks @ 2.7.7formatting

Look for formatting issues in the source

line 818 is way too long (97 characters)
go-github-com-libp2p-go-libp2p-metrics @ 2.1.6-0.a10ff6eformatting

Look for formatting issues in the source

line 2256 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 2259 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 2376 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 2377 is way too long (93 characters)
tigervnc-server @ 1.9.0formatting

Look for formatting issues in the source

line 177 is way too long (102 characters)
tigervnc-server @ 1.9.0formatting

Look for formatting issues in the source

line 180 is way too long (99 characters)
tigervnc-server @ 1.9.0formatting

Look for formatting issues in the source

tabulation on line 189, column 0
go-github-com-libp2p-go-libp2p-peer @ 2.3.8-0.993d742formatting

Look for formatting issues in the source

line 2200 is way too long (93 characters)
go-github-com-davecgh-go-spew @ 0.0.0-0.d8f796aformatting

Look for formatting issues in the source

line 1885 is way too long (129 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
kplotting @ 5.63.0inputs-should-be-native

Identify inputs that should be native inputs

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

Look for formatting issues in the source

line 1951 is way too long (106 characters)
kdbusaddons @ 5.63.0formatting

Look for formatting issues in the source

line 641 is way too long (107 characters)
extra-cmake-modules @ 5.63.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1814 is way too long (103 characters)
unbound @ 1.9.4formatting

Look for formatting issues in the source

trailing white space on line 471
unbound @ 1.9.4formatting

Look for formatting issues in the source

trailing white space on line 507
dungeon-crawl-stone-soup @ 0.24.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
dungeon-crawl-stone-soup-tiles @ 0.24.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
texlive-hyphen-latin @ 49435description

Validate package descriptions

use @code or similar ornament instead of quotes
texlive-fonts-iwona @ 0.995bdescription

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
texlive-latex-pgf @ 49435formatting

Look for formatting issues in the source

line 6608 is way too long (98 characters)
texlive-hyph-utf8 @ 49435formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2270 is way too long (95 characters)
texlive-ruhyphen @ 49435formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1139 is way too long (91 characters)
texlive-hyphen-ethiopic @ 49435formatting

Look for formatting issues in the source

line 1574 is way too long (91 characters)
lyx @ 2.3.3formatting

Look for formatting issues in the source

line 6259 is way too long (101 characters)
espeak-ng @ 1.49.2description

Validate package descriptions

description should start with an upper-case letter or digit
ppp @ 2.4.7patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
hplip-minimal @ 3.19.11patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

line 576 is way too long (97 characters)
xftwidth @ 20170402description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 96, 234
xcalib @ 0.10patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

tabulation on line 1422, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1423, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1425, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1426, column 0
elixir @ 1.9.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 76 is way too long (99 characters)
ghc-tasty-expected-failure @ 0.11.1.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 185
ghc-base-unicode-symbols @ 0.2.3formatting

Look for formatting issues in the source

line 899 is way too long (101 characters)
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.5.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
clang @ 3.7.1formatting

Look for formatting issues in the source

line 230 is way too long (95 characters)
clang @ 3.5.2formatting

Look for formatting issues in the source

line 230 is way too long (95 characters)
clang @ 3.6.2formatting

Look for formatting issues in the source

line 230 is way too long (95 characters)
clang @ 6.0.1formatting

Look for formatting issues in the source

line 230 is way too long (95 characters)
clang @ 3.9.1formatting

Look for formatting issues in the source

line 230 is way too long (95 characters)
clang @ 7.0.1formatting

Look for formatting issues in the source

line 230 is way too long (95 characters)
clang @ 8.0.0formatting

Look for formatting issues in the source

line 230 is way too long (95 characters)
clang @ 3.8.1formatting

Look for formatting issues in the source

line 230 is way too long (95 characters)
ghc-regex-tdfa @ 1.2.3.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 139
ghc-th-reify-many @ 0.1.9description

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-rio @ 0.1.12.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-unsafe @ 0.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-operational @ 0.2.3.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
ghc-inline-c @ 0.7.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-fsnotify @ 0.3.0.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 81
ghc-xdg-basedir @ 0.2.2formatting

Look for formatting issues in the source

line 12906 is way too long (93 characters)
ghc-system-filepath @ 0.4.14formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 11455 is way too long (92 characters)
font-adobe-source-serif-pro @ 2.007R-ro-1.007R-itsource-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
font-adobe-source-code-pro @ 2.030R-ro-1.050R-itsource-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
font-adobe-source-sans-pro @ 2.040R-ro-1.090R-itsource-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-next @ 3.8.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 396 is way too long (92 characters)
python2 @ 2.7.16formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 257 is way too long (98 characters)
emacs-clang-rename @ 8.0.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
clang @ 9.0.0formatting

Look for formatting issues in the source

line 230 is way too long (95 characters)
python-llvmlite @ 0.27.1formatting

Look for formatting issues in the source

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

Validate package descriptions

description should start with an upper-case letter or digit
perl-specio @ 0.38description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 185, 314
httrack @ 3.49.2description

Validate package descriptions

use @code or similar ornament instead of quotes
cadaver @ 0.23.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 48
guile-ncurses-with-gpm @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
ocaml-zarith @ 1.9.1description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
ruby-rb-inotify @ 0.9.10description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
sooperlooper @ 1.7.3description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
python-pybedtools @ 0.8.0description

Validate package descriptions

description should start with an upper-case letter or digit
ocaml-cmdliner @ 1.0.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 304
qtcharts @ 5.12.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 244
ruby-mimemagic @ 0.3.3description

Validate package descriptions

description should start with an upper-case letter or digit
mtr @ 0.93description

Validate package descriptions

description should start with an upper-case letter or digit
ocaml-topkg @ 1.0.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 51
shell-functools @ 0.3.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 121, 206
python2-pybedtools @ 0.8.0description

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

Validate package descriptions

description should start with an upper-case letter or digit
qtwebglplugin @ 5.12.6description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-discogs-client @ 2.2.1description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
ruby-haml @ 5.0.4description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
xygrib @ 1.2.6.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 256
ocaml-sexplib @ 0.11.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
qtdatavis3d @ 5.12.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 107, 250
perl-file-readbackwards @ 1.05description

Validate package descriptions

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

Identify inputs that should be native inputs

'nasm' should probably be a native input
synthv1 @ 0.9.11inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
quaternion @ 0.0.9.4cinputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
vmpk @ 0.7.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
alsa-modular-synth @ 2.1.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' 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
flatbuffers @ 1.10.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
qtox @ 1.16.3source-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-security @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ocaml-lwt @ 4.1.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
nzbget @ 21.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-webapp @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
jimtcl @ 0.77source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
font-mathjax @ 2.7.2source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
spin2cpp @ 3.6.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
argon2 @ 20171227source-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-servlet @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
js-mathjax @ 2.7.2source-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
libsignal-protocol-c @ 2.3.2source-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
nethogs @ 0.8.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
rhash @ 1.3.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
pass-git-helper @ 0.3.1source-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
java-eclipse-jetty-security @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ruby-ae @ 1.8.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-xml @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
hidapi @ 0.8.0-rc1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
pass-rotate @ 0.1source-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
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-http @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ocaml-piqi @ 0.7.7source-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
ruby-ttfunk @ 1.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
tidy-html @ 5.6.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ruby-yard @ 0.9.16source-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
ruby-tzinfo-data @ 1.2017.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ruby-multi-json @ 1.13.1source-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-jmx @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
librdkafka @ 0.9.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsoup @ 1.10.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ruby-oj @ 3.6.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
graphene @ 1.6.0source-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
gumbo-parser @ 0.10.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
sorcer @ 1.1.3source-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
ruby-ansi @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ocaml-ocplib-endian @ 1.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ruby-guard @ 2.13.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ocaml-ctypes @ 0.14.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ruby-rack @ 2.0.6source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-jmx @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
openspin @ 1.00.78source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-perf-helper @ 4.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ruby-puma @ 3.9.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-test-helper @ 4.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
fastboot @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-pyportmidi @ 217patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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
emacs-haskell-mode @ 16.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
mes-rb5 @ 0.21patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
quickswitch-i3 @ 2.2-1.ed692b1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2554 is way too long (95 characters)
giac @ 1.5.0-75formatting

Look for formatting issues in the source

line 354 is way too long (102 characters)
libnfs @ 3.0.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 8188 is way too long (97 characters)
glusterfs @ 7.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
serf @ 1.3.9formatting

Look for formatting issues in the source

line 1514 is way too long (92 characters)
ocamlify @ 0.0.1formatting

Look for formatting issues in the source

line 2162 is way too long (98 characters)
qtbase @ 5.12.6formatting

Look for formatting issues in the source

line 536 is way too long (99 characters)
qtbase @ 5.12.6formatting

Look for formatting issues in the source

line 538 is way too long (105 characters)
qtbase @ 5.12.6formatting

Look for formatting issues in the source

line 541 is way too long (117 characters)
qtbase @ 5.12.6formatting

Look for formatting issues in the source

line 544 is way too long (97 characters)
qtbase @ 5.12.6formatting

Look for formatting issues in the source

line 549 is way too long (94 characters)
qtbase @ 5.12.6formatting

Look for formatting issues in the source

line 551 is way too long (94 characters)
vmpk @ 0.7.2formatting

Look for formatting issues in the source

line 2112 is way too long (91 characters)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 231, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 233, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 236, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 237, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 246, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 247, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 248, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 249, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 250, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 251, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 252, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 254, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 255, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 256, column 0
guile-readline @ 2.2.6formatting

Look for formatting issues in the source

line 343 is way too long (94 characters)
telepathy-glib @ 0.24.1formatting

Look for formatting issues in the source

line 831 is way too long (92 characters)
php @ 7.4.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 243 is way too long (91 characters)
php @ 7.4.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2067 is way too long (91 characters)
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 1675
powertabeditor @ 2.0.0-alpha10formatting

Look for formatting issues in the source

line 1306 is way too long (94 characters)
android-libutils @ 7.1.2_r36formatting

Look for formatting issues in the source

line 618 is way too long (114 characters)
python-pygobject @ 3.28.3formatting

Look for formatting issues in the source

line 701 is way too long (95 characters)
emacs-magit @ 2.90.1-2.c761d28formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 371 is way too long (95 characters)
qtsensors @ 5.12.6formatting

Look for formatting issues in the source

line 844 is way too long (97 characters)
qtmultimedia @ 5.12.6formatting

Look for formatting issues in the source

line 887 is way too long (96 characters)
icecat @ 68.3.0-guix0-preview1formatting

Look for formatting issues in the source

line 851 is way too long (102 characters)
icecat @ 68.3.0-guix0-preview1formatting

Look for formatting issues in the source

trailing white space on line 854
icecat @ 68.3.0-guix0-preview1formatting

Look for formatting issues in the source

trailing white space on line 860
icecat @ 68.3.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 939 is way too long (139 characters)
icecat @ 68.3.0-guix0-preview1formatting

Look for formatting issues in the source

line 944 is way too long (95 characters)
icecat @ 68.3.0-guix0-preview1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
qutebrowser @ 0.11.0formatting

Look for formatting issues in the source

trailing white space on line 324
kcmutils @ 5.63.0formatting

Look for formatting issues in the source

line 2258 is way too long (113 characters)
sdl-image @ 1.2.12formatting

Look for formatting issues in the source

line 217 is way too long (91 characters)
varnish @ 6.3.1formatting

Look for formatting issues in the source

line 5306 is way too long (91 characters)
minizip @ 1.2.11formatting

Look for formatting issues in the source

line 142 is way too long (115 characters)
stumpwm-with-slynk @ 19.11formatting

Look for formatting issues in the source

line 1592 is way too long (94 characters)
js-filesaver @ 1.3.8formatting

Look for formatting issues in the source

line 404 is way too long (99 characters)
ocaml-sedlex @ 2.1formatting

Look for formatting issues in the source

line 1992 is way too long (97 characters)
appstream-glib @ 0.7.16formatting

Look for formatting issues in the source

line 943 is way too long (93 characters)
guile-dbi @ 2.1.6formatting

Look for formatting issues in the source

line 1124 is way too long (94 characters)
krona-tools @ 2.7formatting

Look for formatting issues in the source

trailing white space on line 885
childsplay @ 3.4formatting

Look for formatting issues in the source

line 466 is way too long (92 characters)
python-libmpsse @ 1.4formatting

Look for formatting issues in the source

line 924 is way too long (94 characters)
scalapack @ 2.0.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 522 is way too long (111 characters)
qtserialport @ 5.12.5formatting

Look for formatting issues in the source

line 987 is way too long (115 characters)
python2-wtforms @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 816 is way too long (91 characters)
audacity @ 2.3.2formatting

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 254 is way too long (92 characters)
python-wtforms @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2848 is way too long (100 characters)
proj.4 @ 4.9.3formatting

Look for formatting issues in the source

line 350 is way too long (92 characters)
blasr-libcpp @ 5.3.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2515 is way too long (92 characters)
zita-resampler @ 1.3.0formatting

Look for formatting issues in the source

line 3048 is way too long (93 characters)
rosegarden @ 18.12formatting

Look for formatting issues in the source

line 4059 is way too long (93 characters)
rosegarden @ 18.12formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
hdf4 @ 4.2.14formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
tuxguitar @ 1.5.2formatting

Look for formatting issues in the source

line 1761 is way too long (92 characters)
tuxguitar @ 1.5.2formatting

Look for formatting issues in the source

line 1769 is way too long (92 characters)
gcompris @ 17.05formatting

Look for formatting issues in the source

line 120 is way too long (96 characters)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 196 is way too long (91 characters)
upx @ 3.94formatting

Look for formatting issues in the source

line 1949 is way too long (104 characters)
upx @ 3.94formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libjxr @ 1.1formatting

Look for formatting issues in the source

line 483 is way too long (95 characters)
kio @ 5.63.0formatting

Look for formatting issues in the source

line 2805 is way too long (113 characters)
xygrib @ 1.2.6.1formatting

Look for formatting issues in the source

line 977 is way too long (95 characters)
vorbis-tools @ 1.4.0formatting

Look for formatting issues in the source

trailing white space on line 316
gx @ 0.14.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 135 is way too long (99 characters)
gx @ 0.14.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2932 is way too long (91 characters)
python2-libmpsse @ 1.4formatting

Look for formatting issues in the source

line 957 is way too long (96 characters)
solfege @ 3.22.2formatting

Look for formatting issues in the source

line 1208 is way too long (92 characters)
coq-gappa @ 1.3.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1048 is way too long (122 characters)
vamp @ 2.6formatting

Look for formatting issues in the source

line 2550 is way too long (94 characters)
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

line 207 is way too long (106 characters)
sdsl-lite @ 2.1.1formatting

Look for formatting issues in the source

line 224 is way too long (145 characters)
mumps-metis @ 5.2.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
pt-scotch @ 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
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
scotch32 @ 6.0.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mumps @ 5.2.1formatting

Look for formatting issues in the source

line 2283 is way too long (94 characters)
slepc-complex-openmpi @ 3.11.1formatting

Look for formatting issues in the source

line 2170 is way too long (92 characters)
dune-grid @ 2.6.0formatting

Look for formatting issues in the source

line 4665 is way too long (91 characters)
pt-scotch @ 6.0.6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2756, column 0
petsc @ 3.11.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2398 is way too long (100 characters)
mumps-openmpi @ 5.2.1formatting

Look for formatting issues in the source

tabulation on line 2369, column 0
p4est @ 2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1017 is way too long (92 characters)
superlu-dist @ 6.1.0formatting

Look for formatting issues in the source

line 2539 is way too long (92 characters)
superlu-dist @ 6.1.0formatting

Look for formatting issues in the source

tabulation on line 2559, column 0
superlu-dist @ 6.1.0formatting

Look for formatting issues in the source

tabulation on line 2560, column 0
dune-istl @ 2.6.0formatting

Look for formatting issues in the source

tabulation on line 4735, column 0
dune-istl @ 2.6.0formatting

Look for formatting issues in the source

tabulation on line 4736, column 0
dune-istl @ 2.6.0formatting

Look for formatting issues in the source

tabulation on line 4737, column 0
dune-istl @ 2.6.0formatting

Look for formatting issues in the source

tabulation on line 4738, column 0
dune-istl @ 2.6.0formatting

Look for formatting issues in the source

tabulation on line 4739, column 0
dune-istl @ 2.6.0formatting

Look for formatting issues in the source

tabulation on line 4740, column 0
guile-next @ 2.9.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
r-shiny @ 1.4.0formatting

Look for formatting issues in the source

line 808 is way too long (92 characters)
ecasound @ 2.9.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471
u-boot-mx6cuboxi @ 2019.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-mx6cuboxi @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-am335x-evm @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-tools @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-nintendo-nes-classic-edition @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-pine64-lts @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-a20-olinuxino-lime2 @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-am335x-boneblack @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-a20-olinuxino-lime @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-malta @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-vexpress-ca9x4 @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-novena @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-a20-olinuxino-micro @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-bananapi-m2-ultra @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-cubieboard @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-pinebook @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-wandboard @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-pine64-plus @ 2019.04patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-cubietruck @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-puma-rk3399 @ 2019.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-mx6cuboxi @ 2019.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 609 is way too long (93 characters)
u-boot-pine64-lts @ 2019.04formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
u-boot-a20-olinuxino-lime2 @ 2019.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 650 is way too long (95 characters)
u-boot-a20-olinuxino-lime @ 2019.04formatting

Look for formatting issues in the source

line 609 is way too long (93 characters)
u-boot-malta @ 2019.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 609 is way too long (93 characters)
josm @ 15553formatting

Look for formatting issues in the source

tabulation on line 1098, column 0
josm @ 15553formatting

Look for formatting issues in the source

line 1138 is way too long (91 characters)
u-boot-a20-olinuxino-micro @ 2019.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 609 is way too long (93 characters)
u-boot-cubieboard @ 2019.04formatting

Look for formatting issues in the source

line 609 is way too long (93 characters)
u-boot-pinebook @ 2019.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 609 is way too long (93 characters)
u-boot-pine64-plus @ 2019.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 609 is way too long (93 characters)
icedtea @ 2.6.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1336 is way too long (100 characters)
emacs-el-x @ 0.3.1description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-cnfonts @ 0.9.1description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-nhexl-mode @ 1.4description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-hercules @ 0.2.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 2
emacs-flx @ 0.6.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 220
warzone2100 @ 3.2.3description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 33, 259
fifengine @ 0.4.2description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-discover-my-major @ 1.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
crawl-tiles @ 0.24.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-undohist-el @ 0-1.d2239a5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
einstein @ 2.0formatting

Look for formatting issues in the source

line 3114 is way too long (96 characters)
ri-li @ 2.0.1formatting

Look for formatting issues in the source

line 7699 is way too long (100 characters)
python-sphinxcontrib-svg2pdfconverter @ 0.1.0formatting

Look for formatting issues in the source

line 345 is way too long (99 characters)
python-sphinxcontrib-svg2pdfconverter @ 0.1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4226 is way too long (94 characters)
qemu @ 4.1.1formatting

Look for formatting issues in the source

line 122 is way too long (97 characters)
freeorion @ 0.4.8formatting

Look for formatting issues in the source

line 7792 is way too long (92 characters)
emacs-exwm @ 0.23formatting

Look for formatting issues in the source

line 9545 is way too long (96 characters)
libvirt @ 5.8.0formatting

Look for formatting issues in the source

tabulation on line 456, column 0
libvirt @ 5.8.0formatting

Look for formatting issues in the source

tabulation on line 457, column 0
emacs-gtk-look @ 29formatting

Look for formatting issues in the source

line 16723 is way too long (94 characters)
btanks @ 0.9.8083formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6669, column 18
btanks @ 0.9.8083formatting

Look for formatting issues in the source

tabulation on line 6670, column 17
drascula @ 1.0formatting

Look for formatting issues in the source

line 7594 is way too long (93 characters)
diffoscope @ 133formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 335 is way too long (106 characters)
xen @ 4.11.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
emacs-dash-docs @ 1.4.0-1.111fd9bformatting

Look for formatting issues in the source

line 18731 is way too long (91 characters)
qemu-minimal @ 4.1.1formatting

Look for formatting issues in the source

line 265 is way too long (103 characters)
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5471, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5472, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5475, column 0
virt-manager @ 2.2.1formatting

Look for formatting issues in the source

tabulation on line 624, column 0
virt-manager @ 2.2.1formatting

Look for formatting issues in the source

tabulation on line 625, column 0
python-apispec @ 0.25.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
python2-gevent @ 1.3.7description

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

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-dukpy @ 0.3description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python2-dbus @ 1.2.14description

Validate package descriptions

description should start with an upper-case letter or digit
python-gevent @ 1.3.7description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-q @ 2.6description

Validate package descriptions

description should start with an upper-case letter or digit
python2-q @ 2.6description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ptpython2 @ 0.34description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python2-pyaml @ 18.11.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-pyaml @ 18.11.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-jinja2-time @ 0.2.0description

Validate package descriptions

use @code or similar ornament instead of quotes
python2-editor @ 0.5description

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
python-psutil @ 5.6.5description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
python2-pkgconfig @ 1.3.1inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
python-jaraco-packaging @ 6.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-urwidtrees @ 1.0.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-docopt @ 0.6.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-urwidtrees @ 1.0.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-unicodecsv @ 0.14.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-docopt @ 0.6.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-numpy @ 1.8.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-jsonpatch @ 0.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-whatever @ 0.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-jsonpatch @ 1.16source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-whatever @ 0.6source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-mwclient @ 0.8.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-mwclient @ 0.8.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-jsonpatch @ 1.16source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-jsonpatch @ 0.4source-unstable-tarball

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python-seaborn @ 0.9.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python2-hy @ 0.13.0formatting

Look for formatting issues in the source

tabulation on line 8527, column 0
python2-hy @ 0.13.0formatting

Look for formatting issues in the source

tabulation on line 8528, column 0
python2-hy @ 0.13.0formatting

Look for formatting issues in the source

tabulation on line 8529, column 0
python-numpy @ 1.17.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3964 is way too long (105 characters)
scons @ 3.0.4formatting

Look for formatting issues in the source

line 1550 is way too long (96 characters)
python-seaborn @ 0.9.0formatting

Look for formatting issues in the source

line 6037 is way too long (99 characters)
python-ipython-documentation @ 7.9.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python-binwalk @ 2.1.1-0.64201acformatting

Look for formatting issues in the source

line 11152 is way too long (106 characters)
python2-seaborn @ 0.9.0formatting

Look for formatting issues in the source

line 6037 is way too long (99 characters)
python-hy @ 0.13.0formatting

Look for formatting issues in the source

tabulation on line 8527, column 0
python-hy @ 0.13.0formatting

Look for formatting issues in the source

tabulation on line 8528, column 0
python-hy @ 0.13.0formatting

Look for formatting issues in the source

tabulation on line 8529, column 0
libsecp256k1 @ 20191213-1.d644ddaformatting

Look for formatting issues in the source

line 906 is way too long (106 characters)
electron-cash @ 4.0.12formatting

Look for formatting issues in the source

line 472 is way too long (122 characters)
deutex @ 5.2.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
love-nuklear @ v2.6-1.fef4e00formatting

Look for formatting issues in the source

trailing white space on line 669
python2-asn1crypto @ 0.24.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python2-axolotl @ 0.1.39source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-axolotl @ 0.1.39source-unstable-tarball

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
r-iclusterplus @ 1.22.0description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-mixomics @ 6.10.6description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-genomicinteractions @ 1.20.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 190 is way too long (95 characters)
r-unifiedwmwqpcr @ 1.22.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2582 is way too long (101 characters)
r-hsmmsinglecell @ 1.2.0formatting

Look for formatting issues in the source

line 841 is way too long (95 characters)
r-lumi @ 2.38.0formatting

Look for formatting issues in the source

line 2992 is way too long (95 characters)
python2-lmdb @ 0.95description

Validate package descriptions

description should start with an upper-case letter or digit
python2-ccm @ 2.1.6description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
python2-psycopg2 @ 2.7.7description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 84
darktable @ 2.6.3inputs-should-be-native

Identify inputs that should be native inputs

'intltool' should probably be a native input
darktable @ 2.6.3inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
sparql-query @ 1.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-apsw @ 3.20.1-r1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-apsw @ 3.20.1-r1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
sqlcipher @ 3.4.2source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
mariadb @ 10.1.41formatting

Look for formatting issues in the source

line 798 is way too long (92 characters)
mariadb @ 10.1.41formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 590 is way too long (99 characters)
python-cloudpickle @ 0.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 15816 is way too long (97 characters)
bind @ 9.14.9description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 253
unionfs-fuse @ 2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
unionfs-fuse-static @ 2.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
wireless-tools @ 30.pre9formatting

Look for formatting issues in the source

line 2815 is way too long (104 characters)
util-linux @ 2.34formatting

Look for formatting issues in the source

line 1124 is way too long (91 characters)
linux-pam @ 1.3.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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-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-fasterxml-jackson-core @ 2.9.4description

Validate package descriptions

description should not be empty
java-native-access-platform @ 4.5.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
java-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-javaewah @ 1.1.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 310
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-sshagent @ 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-hamcrest-all @ 1.3source-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-plexus-sec-dispatcher @ 1.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jcommander @ 1.71source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-container-default @ 1.7.1source-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-fest-util @ 1.2.5source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-spi @ 1.5.0source-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-powermock-core @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-lz4 @ 1.4.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-bsh @ 2.0b6source-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-modello-test @ 1.9.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-tinybundles @ 2.1.1source-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-jsch-agentproxy-core @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-modello-core @ 1.9.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-dataformat-xml @ 2.9.4source-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-plexus-io @ 3.0.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-assertj @ 3.8.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
antlr3 @ 3.5.2source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fest-assert @ 2.0M10source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-modello-plugins-xpp3 @ 1.9.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-sisu-build-api @ 0.0.7source-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-powermock-api-support @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-objenesis @ 2.5.1source-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-mvel2 @ 2.3.1source-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-jsch-agentproxy-pageant @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-classworlds @ 2.5.2source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-hdrhistogram @ 2.1.9source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-modello-plugins-xml @ 1.9.1source-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-ops4j-base-lang @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-interpolation @ 1.23source-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-jmock @ 2.8.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-guice @ 4.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-compiler-api @ 2.8.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-bouncycastle @ 1.60source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-easymock @ 3.4source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-powermock-modules-junit4-common @ 1.7.3source-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-javax-inject @ tck-1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-compiler-javac @ 2.8.4source-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-plexus-cipher @ 1.7source-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-guice-servlet @ 4.1source-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-logback-classic @ 1.2.3source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-component-annotations @ 1.7.1source-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-plexus-utils @ 3.2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fest-test @ 2.1.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-junit @ 4.12source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-stax2-api @ 4.0.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-woodstox-core @ 5.0.3source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-modello-plugins-java @ 1.9.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-javassist @ 3.21.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-javaewah @ 1.1.6source-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-hamcrest-core @ 1.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-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-gson @ 2.8.2source-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-xerial-core @ 2.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-powermock-core @ 1.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-powermock-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-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-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-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-geronimo-xbean-bundleutils @ 4.5formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2408 is way too long (99 characters)
java-jgit @ 4.2.0.201601211800-rformatting

Look for formatting issues in the source

line 11478 is way too long (93 characters)
java-joda-time @ 2.9.9formatting

Look for formatting issues in the source

line 10297 is way too long (92 characters)
icedtea @ 3.7.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8225 is way too long (100 characters)
java-commons-httpclient @ 3.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8648 is way too long (98 characters)
java-native-access @ 4.5.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8368 is way too long (96 characters)
java-commons-jxpath @ 1.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 6395 is way too long (98 characters)
java-testng @ 6.14.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7884 is way too long (110 characters)
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6336, column 20
java-eclipse-sisu-plexus @ 0.3.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 11190 is way too long (95 characters)
java-logback-classic @ 1.2.3formatting

Look for formatting issues in the source

line 11346 is way too long (102 characters)
java-apache-ivy @ 2.4.0formatting

Look for formatting issues in the source

line 11026 is way too long (101 characters)
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

line 8083 is way too long (91 characters)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

line 4924 is way too long (91 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

line 10626 is way too long (92 characters)
java-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

line 3441 is way too long (112 characters)
hurd @ 0.9derivation

Report failure to compile a package to a derivation

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

Report failure to compile a package to a derivation

failed to create i586-gnu derivation: could not find bootstrap binary 'tar' for system 'i586-gnu'
libringclient @ 20191101.3.67671e7formatting

Look for formatting issues in the source

line 875 is way too long (105 characters)
pjproject @ 2.9formatting

Look for formatting issues in the source

line 651 is way too long (103 characters)
jami @ 20191101.3.67671e7formatting

Look for formatting issues in the source

line 920 is way too long (92 characters)
pjproject-jami @ 2.9formatting

Look for formatting issues in the source

line 773 is way too long (103 characters)
wpa-supplicant-gui @ 2.9description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
mdadm-static @ 4.1description

Validate package descriptions

description should start with an upper-case letter or digit
perftest @ 4.4-0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
pflask @ 0.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
crda @ 3.18formatting

Look for formatting issues in the source

line 2909 is way too long (105 characters)
perftest @ 4.4-0.4formatting

Look for formatting issues in the source

line 4462 is way too long (98 characters)
wine @ 4.0.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
dxvk @ 1.5formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python2-flexmock @ 0.10.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 106
python2-pyfakefs @ 3.5.8patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 497 is way too long (91 characters)
r-systemfonts @ 0.1.1description

Validate package descriptions

use @code or similar ornament instead of quotes
r-cardata @ 3.0-3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 45, 56
r-cmprsk @ 2.2-9description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 242
r-wmtsa @ 2.0-3description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 139
r-bootstrap @ 2019.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 92, 105
python-rpy2 @ 3.0.4-1.19868a8description

Validate package descriptions

description should start with an upper-case letter or digit
r-tidyr @ 1.0.0description

Validate package descriptions

description should start with an upper-case letter or digit
r-arm @ 1.10-1description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 336
r-circular @ 0.4-93description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-boot @ 1.3-24description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 173, 176
freehdl @ 0.0.8inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
capstone @ 3.0.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-capstone @ 3.0.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
emacs-ess @ 17.11source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-capstone @ 3.0.5source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
r-colourpicker @ 1.0formatting

Look for formatting issues in the source

line 12199 is way too long (94 characters)
r-squarem @ 2017.10-1formatting

Look for formatting issues in the source

line 2650 is way too long (97 characters)
r-squarem @ 2017.10-1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 611 is way too long (99 characters)
r-flexdashboard @ 0.5.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 12093 is way too long (91 characters)
emacs-ess @ 17.11formatting

Look for formatting issues in the source

line 5855 is way too long (106 characters)
kicad-symbols @ 5.1.4formatting

Look for formatting issues in the source

line 948 is way too long (324 characters)
r-abps @ 0.3formatting

Look for formatting issues in the source

line 7577 is way too long (93 characters)
r-haplo-stats @ 1.7.9formatting

Look for formatting issues in the source

line 13436 is way too long (103 characters)
openmpi-thread-multiple @ 4.0.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 242 is way too long (94 characters)
openmpi @ 4.0.2formatting

Look for formatting issues in the source

line 244 is way too long (96 characters)
linux-libre-arm-omap2plus @ 5.4.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-generic @ 4.19.91patch-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.160patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 751 is way too long (117 characters)
linux-libre @ 5.4.6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 751 is way too long (117 characters)
linux-libre @ 4.14.160formatting

Look for formatting issues in the source

line 751 is way too long (117 characters)
linux-libre @ 4.19.91formatting

Look for formatting issues in the source

line 751 is way too long (117 characters)
linux-libre-arm-veyron @ 5.4.6formatting

Look for formatting issues in the source

line 751 is way too long (117 characters)
linux-libre @ 4.9.207formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 751 is way too long (117 characters)
linux-libre @ 4.4.207formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 751 is way too long (117 characters)
kdelibs4support @ 5.63.0inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
pan @ 0.145description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
alot @ 0.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
cl-quri @ 0.1.0-1.76b7510description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 68
sbcl-cl-cookie @ 0.9.10-1.cea55aedescription

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
cl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
cl-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.0483adedescription

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ecl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
cl-md5 @ 2.0.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
sbcl-graph-json @ 0.0.0-0.78bf9ecpatch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2334 is way too long (130 characters)
cl-portable-threads @ 2.3-1.c0e61a1formatting

Look for formatting issues in the source

line 2905 is way too long (94 characters)
cl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 5606 is way too long (91 characters)
sbcl-fare-quasiquote @ 20171130formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 843 is way too long (98 characters)
sbcl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 5606 is way too long (91 characters)
cl-fare-quasiquote @ 20171130formatting

Look for formatting issues in the source

line 5637 is way too long (97 characters)
cl-dbus @ 20190408-1.24b452dformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2024 is way too long (96 characters)
sbcl-trivia.trivial @ 0.0.0-1.902e0c6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2580 is way too long (91 characters)
network-manager @ 1.18.4patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gnome-keyring @ 3.28.2formatting

Look for formatting issues in the source

line 845 is way too long (91 characters)
libsoup @ 2.68.3formatting

Look for formatting issues in the source

line 3072 is way too long (128 characters)
libsoup @ 2.68.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
network-manager @ 1.18.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 6320 is way too long (103 characters)
glade @ 3.22.1formatting

Look for formatting issues in the source

line 1373 is way too long (91 characters)
ecryptfs-utils @ 111description

Validate package descriptions

description should start with an upper-case letter or digit
fakeroot @ 1.24description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 114, 240
jmtpfs @ 0.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
tlp @ 1.2.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
procenv @ 0.51source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
proot-static @ 5.1.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
r-seqlogo @ 1.52.0description

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
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
samblaster @ 0.1.24description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 263
python2-bx-python @ 0.8.2description

Validate package descriptions

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

Validate package descriptions

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

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
r-bseqsc @ 1.0-1.fef3f3edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 395
python-dnaio @ 0.3description

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-cython' should probably be a native input
kdevelop-pg-qt @ 2.2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
emacs-next @ 27.0.50-0.36abf68patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
grantleetheme @ 19.08.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
fastahack @ 0.0.0-1.c68cebbformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3676 is way too long (104 characters)
pigx-scrnaseq @ 0.0.8formatting

Look for formatting issues in the source

tabulation on line 12772, column 0
pigx-scrnaseq @ 0.0.8formatting

Look for formatting issues in the source

tabulation on line 12773, column 0
pigx-scrnaseq @ 0.0.8formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 12473, column 0
ncbi-vdb @ 2.9.6formatting

Look for formatting issues in the source

tabulation on line 5643, column 26
java-forester @ 1.005formatting

Look for formatting issues in the source

line 12175 is way too long (92 characters)
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4569, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4570, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4571, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4572, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4574, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4581, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4582, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4583, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4584, column 0
java-picard @ 1.113formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3823 is way too long (117 characters)
icecat @ 68.3.0-guix0-preview1formatting

Look for formatting issues in the source

line 983 is way too long (98 characters)
gaupol @ 1.6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3765 is way too long (91 characters)
r-rhdf5lib @ 1.8.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10527 is way too long (104 characters)
discrover @ 1.6.0formatting

Look for formatting issues in the source

line 2674 is way too long (91 characters)
salmon @ 0.13.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 15209, column 28