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
ruby-rb-inotify @ 0.9.10description

Validate package descriptions

description should start with an upper-case letter or digit
u-boot-wandboard @ 2020.01description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
u-boot-vexpress-ca9x4 @ 2020.01description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 121, 206
mate-applets @ 1.22.0description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
u-boot-am335x-evm @ 2020.01description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
u-boot-nintendo-nes-classic-edition @ 2020.01description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
u-boot-pine64-plus @ 2020.01description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
xfce4-volumed-pulse @ 0.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
flex @ 2.6.4inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
itk-snap @ 3.8.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
cinnamon-desktop @ 3.4.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
xfce4-places-plugin @ 1.8.1inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
privoxy @ 3.0.28inputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
privoxy @ 3.0.28inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
bison @ 3.0.5inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
ristretto @ 0.10.0inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
gobject-introspection @ 1.60.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'flex' should probably be a native input
dico @ 2.9inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
mate-polkit @ 1.22.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
rubber @ 1.1inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
flex @ 2.6.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libkate @ 0.4.1inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
jami-client-gnome @ 20191101.3.67671e7inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gnome-tweak-tool @ 3.32.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
ijs @ 9.27patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
sdsl-lite @ 2.1.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
enlightenment-wayland @ 0.23.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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
python2-cffi @ 1.11.5patch-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
avr-binutils @ 2.32patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
icu4c @ 64.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
texlive-hyphen-ethiopic @ 49435formatting

Look for formatting issues in the source

line 1574 is way too long (91 characters)
u-boot-wandboard @ 2020.01formatting

Look for formatting issues in the source

line 595 is way too long (93 characters)
texlive-latex-pgf @ 49435formatting

Look for formatting issues in the source

line 6608 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)
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)
u-boot-mx6cuboxi @ 2020.01formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 224 is way too long (145 characters)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 573 is way too long (103 characters)
u-boot-cubieboard @ 2020.01formatting

Look for formatting issues in the source

line 595 is way too long (93 characters)
netpbm @ 10.78.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 196 is way too long (96 characters)
libsigrok @ 0.5.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 212 is way too long (92 characters)
vorbis-tools @ 1.4.0formatting

Look for formatting issues in the source

trailing white space on line 322
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)
maven-core @ 3.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1215 is way too long (118 characters)
cryptsetup-static @ 2.2.2formatting

Look for formatting issues in the source

line 102 is way too long (93 characters)
atril @ 1.22.0formatting

Look for formatting issues in the source

line 770 is way too long (92 characters)
busybox @ 1.29.3formatting

Look for formatting issues in the source

trailing white space on line 82
busybox @ 1.29.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 190 is way too long (95 characters)
wgetpaste @ 2.29formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 595 is way too long (93 characters)
wicd @ 1.7.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 595 is way too long (93 characters)
mate-panel @ 1.22.0formatting

Look for formatting issues in the source

line 695 is way too long (92 characters)
gtklick @ 0.6.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 595 is way too long (93 characters)
ruby-iruby @ 0.3formatting

Look for formatting issues in the source

line 414 is way too long (112 characters)
maven-resolver-impl @ 1.3.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 232 is way too long (93 characters)
jose @ 10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 595 is way too long (93 characters)
glibc @ 2.29formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 357 is way too long (109 characters)
u-boot-tools @ 2020.01formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 485 is way too long (97 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)
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 207, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 208, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 209, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 213, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 214, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 216, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 313, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 315, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 316, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 317, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 321, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 322, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 324, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 325, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 326, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 327, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 328, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 329, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 330, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 331, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 374, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 376, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 377, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 378, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 379, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 380, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 381, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 382, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 383, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 384, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 385, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 386, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 387, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 389, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 390, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 391, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 392, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 393, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 394, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 430, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 431, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 432, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 436, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 437, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 438, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 456, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 461, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 462, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 467, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

tabulation on line 468, column 0
julia @ 1.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 831 is way too long (92 characters)
maven-wagon-file @ 3.1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 633 is way too long (129 characters)
maven-embedder @ 3.6.1formatting

Look for formatting issues in the source

line 1271 is way too long (110 characters)
opencv @ 3.4.3formatting

Look for formatting issues in the source

line 282 is way too long (132 characters)
texlive-latex-l3packages @ 49435formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 297 is way too long (102 characters)
pth @ 2.0.7formatting

Look for formatting issues in the source

trailing white space on line 42
ldc @ 0.17.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 595 is way too long (93 characters)
libsigsegv @ 2.12formatting

Look for formatting issues in the source

line 48 is way too long (133 characters)
mate-menus @ 1.22.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 636 is way too long (95 characters)
lyx @ 2.3.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 595 is way too long (93 characters)
openfoam @ 4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 144 is way too long (91 characters)
python @ 3.7.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 231, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 233, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 236, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 237, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 246, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 247, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 248, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 249, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 250, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 251, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 252, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 254, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 255, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 256, column 0
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)
libdaemon @ 0.14formatting

Look for formatting issues in the source

line 35 is way too long (147 characters)
u-boot-cubietruck @ 2020.01formatting

Look for formatting issues in the source

line 595 is way too long (93 characters)
texlive-bin @ 20180414formatting

Look for formatting issues in the source

line 270 is way too long (91 characters)
python2-cryptography @ 2.7description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python2-axolotl @ 0.1.39patch-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.3description

Validate package descriptions

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

Look for formatting issues in the source

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

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

trailing white space on line 1675
rcm @ 1.3.3description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'swig' should probably be a native input
r-abps @ 0.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1335 is way too long (100 characters)
electron-cash @ 4.0.12formatting

Look for formatting issues in the source

line 480 is way too long (122 characters)
conda @ 4.3.16formatting

Look for formatting issues in the source

line 747 is way too long (94 characters)
icedtea @ 3.7.0formatting

Look for formatting issues in the source

line 1662 is way too long (109 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
gramps @ 5.1.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
r-shiny @ 1.4.0formatting

Look for formatting issues in the source

line 810 is way too long (92 characters)
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
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
grantleetheme @ 19.08.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
go-github-com-gorilla-context @ 0.0.0-0.08b5f42formatting

Look for formatting issues in the source

line 1072 is way too long (164 characters)
tigervnc-server @ 1.10.1patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 195, column 0
gtkspell3 @ 3.0.9inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gtk+ @ 2.24.32patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 577 is way too long (97 characters)
python2-libmpsse @ 1.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1176 is way too long (122 characters)
kiconthemes @ 5.63.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
kdewebkit @ 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
kconfigwidgets @ 5.63.0inputs-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
kplotting @ 5.63.0inputs-should-be-native

Identify inputs that should be native inputs

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 107 is way too long (91 characters)
kdbusaddons @ 5.63.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2196 is way too long (113 characters)
kimageformats @ 5.63.0formatting

Look for formatting issues in the source

line 1752 is way too long (103 characters)
kpackage @ 5.63.0formatting

Look for formatting issues in the source

line 1889 is way too long (106 characters)
owncloud-client @ 2.5.3.11470patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

line 517 is way too long (91 characters)
mailutils @ 3.8inputs-should-be-native

Identify inputs that should be native inputs

'dejagnu' should probably be a native input
mailutils @ 3.8inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
guile3.0-mailutils @ 3.8inputs-should-be-native

Identify inputs that should be native inputs

'dejagnu' should probably be a native input
guile3.0-mailutils @ 3.8inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
ocaml-dose3 @ 5.0.1formatting

Look for formatting issues in the source

line 362 is way too long (92 characters)
python-pytest-subtesthack @ 0.1.1description

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
ghc-hxt-unicode @ 9.0.2.4formatting

Look for formatting issues in the source

line 1252 is way too long (91 characters)
zbar @ 0.23inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
u-boot-qemu-riscv64 @ 2020.01description

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 595 is way too long (93 characters)
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 347 is way too long (107 characters)
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 355, column 0
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 365, column 0
sdl-mixer @ 1.2.12formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1107 is way too long (98 characters)
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

line 214 is way too long (106 characters)
guile-sdl @ 0.5.2formatting

Look for formatting issues in the source

line 610 is way too long (111 characters)
sdl-image @ 1.2.12formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

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

Validate package descriptions

description should start with an upper-case letter or digit
ibus-anthy @ 1.5.9inputs-should-be-native

Identify inputs that should be native inputs

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

Look for formatting issues in the source

line 327 is way too long (93 characters)
gcompris @ 17.05formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 569 is way too long (99 characters)
python-flexmock @ 0.10.4description

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-pyfakefs @ 3.7.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-xsge @ 2018.02.26description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 100
lua-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
ghc-base-unicode-symbols @ 0.2.3formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
awesome @ 4.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
quickswitch-i3 @ 2.2-1.ed692b1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
fish @ 3.0.2inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
libical @ 3.0.7patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

tabulation on line 912, column 0
rust @ 1.31.1formatting

Look for formatting issues in the source

tabulation on line 940, column 0
rust @ 1.31.1formatting

Look for formatting issues in the source

tabulation on line 941, column 0
rust @ 1.31.1formatting

Look for formatting issues in the source

tabulation on line 942, column 0
rust @ 1.31.1formatting

Look for formatting issues in the source

tabulation on line 943, column 0
stumpwm-with-slynk @ 19.11formatting

Look for formatting issues in the source

line 1643 is way too long (94 characters)
dejagnu @ 1.6.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 745 is way too long (94 characters)
libical @ 3.0.7formatting

Look for formatting issues in the source

line 68 is way too long (93 characters)
python-pytools @ 2020.1description

Validate package descriptions

use @code or similar ornament instead of quotes
qtoctave @ 5.2.0inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
editorconfig-core-c @ 0.12.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 755 is way too long (125 characters)
spacefm @ 1.0.6inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
libchop @ 0.5.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
syncthing @ 1.3.4formatting

Look for formatting issues in the source

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-component-metadata @ 1.7.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
python2-mapnik @ 3.0.16source-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
tesseract-ocr @ 3.04.01source-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
texlive-latex-hyperref @ 6.84a2source-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
rdmd @ 2.077.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Report failure to compile a package to a derivation

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

Report failure to compile a package to a derivation

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

Report failure to compile a package to a derivation

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

Report failure to compile a package to a derivation

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
lxde-common @ 0.99.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
help2man @ 1.47.10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
mrustc @ 0.9formatting

Look for formatting issues in the source

line 149 is way too long (123 characters)
tumbler @ 0.2.8formatting

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 414 is way too long (96 characters)
vlc @ 3.0.8formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1222 is way too long (107 characters)
guile3.0-present @ 0.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
efitools @ 1.9.2formatting

Look for formatting issues in the source

line 175 is way too long (113 characters)
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 449 is way too long (92 characters)
connman @ 1.38description

Validate package descriptions

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

Validate file names and availability of patches

file names of patches should start with the package name
r-wmtsa @ 2.0-3description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 97, 120
rhash @ 1.3.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
libsecp256k1 @ 20191213-1.d644ddaformatting

Look for formatting issues in the source

line 921 is way too long (106 characters)
php @ 7.4.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 83 is way too long (95 characters)
python2-pycrypto @ 2.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
containerd @ 1.2.5formatting

Look for formatting issues in the source

line 215 is way too long (102 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)
proj.4 @ 4.9.3formatting

Look for formatting issues in the source

line 387 is way too long (92 characters)
bind @ 9.16.0description

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
java-rsyntaxtextarea @ 2.6.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
telegram-purple @ 1.4.2inputs-should-be-native

Identify inputs that should be native inputs

'gettext' 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
mongodb @ 3.4.10source-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
qtox @ 1.16.3source-unstable-tarball

Check for autogenerated tarballs

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

Look for formatting issues in the source

line 593 is way too long (99 characters)
diffoscope @ 137formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
sky @ 1.2description

Validate package descriptions

use @code or similar ornament instead of quotes
lure-fr @ 1.1formatting

Look for formatting issues in the source

line 7861 is way too long (93 characters)
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5566, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5567, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5570, column 0
ri-li @ 2.0.1formatting

Look for formatting issues in the source

line 8160 is way too long (100 characters)
btanks @ 0.9.8083formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6835, column 18
btanks @ 0.9.8083formatting

Look for formatting issues in the source

tabulation on line 6836, column 17
lure-es @ 1.1formatting

Look for formatting issues in the source

line 7861 is way too long (93 characters)
queen @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7961 is way too long (205 characters)
lure-it @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7760 is way too long (93 characters)
queen-fr @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8064 is way too long (118 characters)
freeorion @ 0.4.9formatting

Look for formatting issues in the source

line 8245 is way too long (92 characters)
queen-it @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7861 is way too long (93 characters)
android-libziparchive @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 373 is way too long (97 characters)
python-fpylll @ 0.4.1description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
libblockdev @ 2.23inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gparted @ 1.1.0inputs-should-be-native

Identify inputs that should be native inputs

'yelp-tools' should probably be a native input
asciidoc @ 8.6.10source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
dmraid @ 1.0.0.rc16-3formatting

Look for formatting issues in the source

line 682 is way too long (91 characters)
libblockdev @ 2.23formatting

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 486 is way too long (95 characters)
nginx-accept-language-module @ 0.0.0-1.2f69842formatting

Look for formatting issues in the source

line 513 is way too long (92 characters)
espeak-ng @ 1.50description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 123
python-faiss @ 1.5.0inputs-should-be-native

Identify inputs that should be native inputs

'swig' 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
synthv1 @ 0.9.12inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
openmw @ 0.45.0source-unstable-tarball

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 704
drumstick @ 1.1.3formatting

Look for formatting issues in the source

line 2090 is way too long (91 characters)
solfege @ 3.22.2formatting

Look for formatting issues in the source

line 1203 is way too long (92 characters)
vmpk @ 0.7.2formatting

Look for formatting issues in the source

line 2135 is way too long (91 characters)
qtdatavis3d @ 5.12.7description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 107, 250
python2-ccm @ 2.1.6description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
qtwebglplugin @ 5.12.7description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 244
python2-lmdb @ 0.95description

Validate package descriptions

description should start with an upper-case letter or digit
gdb @ 9.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
gdb-arm-none-eabi @ 9.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
sparql-query @ 1.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
sqlcipher @ 3.4.2source-unstable-tarball

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
xf86-video-intel @ 2.99.917-15.f66d395formatting

Look for formatting issues in the source

line 2934 is way too long (91 characters)
mariadb @ 10.1.44formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 803 is way too long (91 characters)
qtserialport @ 5.12.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1968 is way too long (105 characters)
xproto @ 7.0.31formatting

Look for formatting issues in the source

line 4771 is way too long (91 characters)
qtbase @ 5.12.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 577 is way too long (94 characters)
r-genomicinteractions @ 1.20.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 936 is way too long (95 characters)
r-monocle @ 2.14.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3113 is way too long (95 characters)
python-html2text @ 2019.8.11description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
clang-runtime @ 3.9.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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
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-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-string-match @ 0-1.5048480formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 132 is way too long (96 characters)
clang-runtime @ 3.5.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 764 is way too long (92 characters)
u-boot-firefly-rk3399 @ 2020.01description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
pcb-rnd @ 1.1.3inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
lepton-eda @ 1.9.9-20191003inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
gerbv @ 2.7.0inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
geda-gaf @ 1.10.0inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
pcb @ 4.0.2inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
qucs @ 0.0.19-0.b4f27d9inputs-should-be-native

Identify inputs that should be native inputs

'libtool' should probably be a native input
qucs-s @ 0.0.21inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 613 is way too long (99 characters)
emacs-xwidgets @ 26.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
emacs-next @ 27.0.50-0.36abf68patch-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
gnome-shell-extension-gsconnect @ 28inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
serf @ 1.3.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 997
ecl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 68
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
sbcl-quri @ 0.1.0-1.76b7510description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 68
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-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-portable-threads @ 2.3-1.c0e61a1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3184 is way too long (94 characters)
cl-sqlite @ 0.2-1.c738e66formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2859 is way too long (91 characters)
pan @ 0.146description

Validate package descriptions

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
aegisub @ 3.2.2inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
gst-transcoder @ 1.12.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
alot @ 0.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
gaupol @ 1.7formatting

Look for formatting issues in the source

line 3685 is way too long (95 characters)
r-rgadem @ 2.34.1description

Validate package descriptions

description should start with an upper-case letter or digit
r-squarem @ 2020.2formatting

Look for formatting issues in the source

line 2651 is way too long (91 characters)
elixir @ 1.10.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Identify inputs that should be native inputs

'doxygen' should probably be a native input
scotch32 @ 6.0.6inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
scotch32 @ 6.0.6inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
pt-scotch @ 6.0.6inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
pt-scotch @ 6.0.6inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'texinfo' should probably be a native input
pt-scotch32 @ 6.0.6inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
pt-scotch32 @ 6.0.6inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
scotch @ 6.0.6inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
scotch @ 6.0.6inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
mumps-metis @ 5.2.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
scalapack @ 2.0.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2439 is way too long (100 characters)
hdf4 @ 4.2.14formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
pt-scotch @ 6.0.6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1057 is way too long (92 characters)
slepc-complex-openmpi @ 3.11.1formatting

Look for formatting issues in the source

line 2211 is way too long (92 characters)
petsc @ 3.11.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
mumps @ 5.2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2600, column 0
p4est @ 2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2796, column 0
rust-rustc-tools-util @ 0.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
rust-winit @ 0.20.0-alpha6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 20853 is way too long (114 characters)
emacs-erlang @ 21.3.8.13patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ddate @ 0.2.2source-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
unionfs-fuse @ 2.0source-unstable-tarball

Check for autogenerated tarballs

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

Validate file names and availability of patches

file names of patches should start with the package name
util-linux @ 2.34formatting

Look for formatting issues in the source

line 1182 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
wine64 @ 5.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
wine-staging @ 5.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'autoconf' should probably be a native input
wine-staging @ 5.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
vim-full @ 8.2.0343formatting

Look for formatting issues in the source

line 197 is way too long (94 characters)
abseil-cpp @ 20200225formatting

Look for formatting issues in the source

line 463 is way too long (116 characters)
abseil-cpp @ 20200225formatting

Look for formatting issues in the source

line 464 is way too long (144 characters)
gpsbabel @ 1.5.4inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
zathura-pdf-poppler @ 0.3.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 399 is way too long (93 characters)
python2-pygobject @ 2.28.7inputs-should-be-native

Identify inputs that should be native inputs

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

Validate file names and availability of patches

file names of patches should start with the package name
i3-wm @ 4.18description

Validate package descriptions

description should start with an upper-case letter or digit
template-glib @ 3.32.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
ibus @ 1.5.22inputs-should-be-native

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 143 is way too long (115 characters)
guile-ncurses-with-gpm @ 3.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
guile3.0-email @ 0.2.2description

Validate package descriptions

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

Validate package descriptions

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

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
guile-dbi @ 2.1.6formatting

Look for formatting issues in the source

line 1240 is way too long (94 characters)
java-jgit @ 4.2.0.201601211800-rformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2413 is way too long (99 characters)
unbound @ 1.10.0formatting

Look for formatting issues in the source

trailing white space on line 466
unbound @ 1.10.0formatting

Look for formatting issues in the source

trailing white space on line 502
a2ps @ 4.14inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
tuxmath @ 2.0.3description

Validate package descriptions

description should start with an upper-case letter or digit
lpsolve @ 5.5.2.5description

Validate package descriptions

description should start with an upper-case letter or digit
hypre-openmpi @ 2.15.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 4524, column 0
perl-class-load @ 0.25description

Validate package descriptions

use @code or similar ornament instead of quotes
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
giac @ 1.5.0-87formatting

Look for formatting issues in the source

line 356 is way too long (95 characters)
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1478, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1479, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1481, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1482, column 0
sbcl-cl-cookie @ 0.9.10-1.cea55aedescription

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
cl-gobject-introspection @ 0.3-0.7b703e2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
sbcl-trivia.trivial @ 0.0.0-1.574901aformatting

Look for formatting issues in the source

line 6142 is way too long (104 characters)
sbcl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 5916 is way too long (91 characters)
cl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 5916 is way too long (91 characters)
librecad @ 2.1.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
xfce4-clipman-plugin @ 1.4.4formatting

Look for formatting issues in the source

line 392 is way too long (91 characters)
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
next @ 1.5.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 588 is way too long (106 characters)
r-tidyr @ 1.0.2description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-cardata @ 3.0-3description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 133, 136, 139
nototools @ 20170925source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
qemu-minimal @ 4.2.0patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 133 is way too long (97 characters)
xen @ 4.11.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 358 is way too long (106 characters)
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-yapsa @ 1.12.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 93, 96
plotutils @ 2.6formatting

Look for formatting issues in the source

trailing white space on line 81
guile-next @ 3.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perl-file-which @ 1.23description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
perl-specio @ 0.38description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 47
man-db @ 2.9.1inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 8329 is way too long (97 characters)
java-eclipse-jetty-servlet @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
pflask @ 0.2source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-server @ 9.4.6source-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 3122 is way too long (105 characters)
wireless-tools @ 30.pre9formatting

Look for formatting issues in the source

line 3028 is way too long (104 characters)
varnish @ 6.3.2formatting

Look for formatting issues in the source

line 5551 is way too long (91 characters)
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5240, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5241, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5242, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5243, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5244, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5250, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5251, column 0
c-reduce @ 2.10.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gtk-doc' should probably be a native input
localed @ 241formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 898 is way too long (97 characters)
jami @ 20191101.3.67671e7inputs-should-be-native

Identify inputs that should be native inputs

'gettext' should probably be a native input
jami @ 20191101.3.67671e7formatting

Look for formatting issues in the source

line 940 is way too long (92 characters)
libringclient @ 20191101.3.67671e7formatting

Look for formatting issues in the source

line 895 is way too long (105 characters)
pjproject-jami @ 2.9formatting

Look for formatting issues in the source

line 793 is way too long (103 characters)
pjproject @ 2.9formatting

Look for formatting issues in the source

line 671 is way too long (103 characters)
icecat @ 68.6.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 244 is way too long (96 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 1157
blasr-libcpp @ 5.3.3formatting

Look for formatting issues in the source

line 583 is way too long (95 characters)
eigen @ 3.3.5formatting

Look for formatting issues in the source

tabulation on line 942, column 0
symmetrica @ 2.0formatting

Look for formatting issues in the source

line 1363 is way too long (100 characters)
graphene @ 1.6.0inputs-should-be-native

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
gx @ 0.14.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 143 is way too long (91 characters)
xdg-user-dirs @ 0.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
docker @ 19.03.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 382 is way too long (93 characters)
python2-twobitreader @ 3.1.6description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
xygrib @ 1.2.6.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 256
wpa-supplicant-minimal @ 2.9description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
nsis-i686 @ 3.05description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
wpa-supplicant-gui @ 2.9description

Validate package descriptions

description should start with an upper-case letter or digit
nsis-x86_64 @ 3.05description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
wpa-supplicant @ 2.9description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
gnome-contacts @ 3.32.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
deja-dup @ 34.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
system-config-printer @ 1.5.12inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
geoclue @ 2.5.5inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
libmediaart @ 1.9.4inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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
nsis-i686 @ 3.05patch-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
nsis-x86_64 @ 3.05patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
josm @ 15937formatting

Look for formatting issues in the source

tabulation on line 1153, column 0
josm @ 15937formatting

Look for formatting issues in the source

line 1193 is way too long (91 characters)
xygrib @ 1.2.6.1formatting

Look for formatting issues in the source

line 1031 is way too long (95 characters)
gnome-keyring @ 3.28.2formatting

Look for formatting issues in the source

line 1477 is way too long (91 characters)
glade @ 3.22.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4232 is way too long (110 characters)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 118 is way too long (114 characters)
discrover @ 1.6.0formatting

Look for formatting issues in the source

line 2686 is way too long (91 characters)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 118 is way too long (114 characters)
libsoup @ 2.68.4formatting

Look for formatting issues in the source

line 3744 is way too long (128 characters)
libsoup @ 2.68.4formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
cgit @ 1.2.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
git-crypt @ 0.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 141 is way too long (93 characters)
udiskie @ 2.1.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile-readline @ 2.2.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 350 is way too long (94 characters)
guile3.0-readline @ 3.0.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 168 is way too long (105 characters)
r-rstan @ 2.19.3description

Validate package descriptions

use @code or similar ornament instead of quotes
r-cmprsk @ 2.2-9description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 242
r-bioassayr @ 1.24.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 173, 176
r-diagram @ 1.6.4description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-rpy2 @ 3.0.4-1.19868a8description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-rtracklayer @ 1.46.0description

Validate package descriptions

description should start with an upper-case letter or digit
r-iheatmapr @ 0.4.12description

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
r-mixomics @ 6.10.8description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
samblaster @ 0.1.24description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 92, 105
r-arm @ 1.10-1description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 139
r-xyz @ 0.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 232, 243, 262
rseqc @ 3.0.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'swig' should probably be a native input
emacs-ess @ 17.11source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
r-gamlss-dist @ 5.1-6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 12532, column 0
r-rhdf5lib @ 1.8.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10601 is way too long (104 characters)
r-colourpicker @ 1.0formatting

Look for formatting issues in the source

line 12189 is way too long (94 characters)
emacs-ess @ 17.11formatting

Look for formatting issues in the source

line 5791 is way too long (106 characters)
r-unifiedwmwqpcr @ 1.22.0formatting

Look for formatting issues in the source

line 6665 is way too long (92 characters)
ncbi-vdb @ 2.9.6formatting

Look for formatting issues in the source

tabulation on line 5685, column 26
java-picard @ 1.113formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3839 is way too long (117 characters)
r-haplo-stats @ 1.7.9formatting

Look for formatting issues in the source

line 13437 is way too long (103 characters)
freebayes @ 1.0.2-1.3ce827dformatting

Look for formatting issues in the source

tabulation on line 15295, column 28
java-picard @ 2.10.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3781 is way too long (91 characters)
salmon @ 0.13.1formatting

Look for formatting issues in the source

line 11953 is way too long (99 characters)
java-picard @ 2.3.0formatting

Look for formatting issues in the source

line 3692 is way too long (104 characters)
r-flexdashboard @ 0.5.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 14700 is way too long (100 characters)
ghc-llvm-hs @ 9.0.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 139
ghc-gtk2hs-buildtools @ 0.13.5.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

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-inline-c @ 0.7.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-xdg-basedir @ 0.2.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 11327 is way too long (250 characters)
mingw-w64-x86_64-winpthreads @ 7.0.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 87 is way too long (91 characters)
mrrescue @ 1.02edescription

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'swig' should probably be a native input
nethack @ 3.6.6inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
nethack @ 3.6.6inputs-should-be-native

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 3293 is way too long (96 characters)
linux-libre @ 5.4.25derivation

Report failure to compile a package to a derivation

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

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
linux-libre-arm-generic @ 5.4.25patch-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.25patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 757 is way too long (117 characters)
linux-libre-arm-veyron @ 5.4.25formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2351 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 2274 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 2277 is way too long (93 characters)
linux-libre @ 4.9.216formatting

Look for formatting issues in the source

line 757 is way too long (117 characters)
go-github-com-mitchellh-go-homedir @ 1.0.0-0.ae18d6bformatting

Look for formatting issues in the source

line 2313 is way too long (95 characters)
linux-libre-arm-omap2plus @ 5.4.25formatting

Look for formatting issues in the source

line 757 is way too long (117 characters)
go-github-com-libp2p-go-libp2p-peer @ 2.3.8-0.993d742formatting

Look for formatting issues in the source

line 2218 is way too long (93 characters)
linux-libre @ 5.4.25formatting

Look for formatting issues in the source

line 757 is way too long (117 characters)
linux-libre-riscv64-generic @ 5.4.25formatting

Look for formatting issues in the source

line 757 is way too long (117 characters)
linux-libre @ 4.14.173formatting

Look for formatting issues in the source

line 757 is way too long (117 characters)
go-github-com-multiformats-go-multiaddr-net @ 1.6.3-0.1cb9a0eformatting

Look for formatting issues in the source

line 2394 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 2395 is way too long (93 characters)
go-github-com-mattn-go-shellwords @ 1.0.5-1.2444a32formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
go-github-com-davecgh-go-spew @ 0.0.0-0.d8f796aformatting

Look for formatting issues in the source

line 1905 is way too long (129 characters)
linux-libre-arm-omap2plus @ 4.14.173formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 757 is way too long (117 characters)
linux-libre @ 4.4.216formatting

Look for formatting issues in the source

line 757 is way too long (117 characters)
catdoc @ 0.95description

Validate package descriptions

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

Look for formatting issues in the source

line 275 is way too long (92 characters)
tegola @ 0.7.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
perf @ 5.4.25patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
iwd @ 0.21inputs-should-be-native

Identify inputs that should be native inputs

'libtool' should probably be a native input
nethogs @ 0.8.5source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
pidentd @ 3.0.19source-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
restbed @ 4.6-1.6eb385fformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

file names of patches should start with the package name
sudo @ 1.8.31p1inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
libreoffice @ 6.4.1.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-psycopg2 @ 2.8.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
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
vowpal-wabbit @ 8.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
lightgbm @ 2.0.12source-unstable-tarball

Check for autogenerated tarballs

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

Validate file names and availability of patches

file names of patches should start with the package name
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
mesa-opencl-icd @ 19.3.4patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 296 is way too long (100 characters)
python2-dbus @ 1.2.14description

Validate package descriptions

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

Validate package descriptions

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

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

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

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-virtualenv @ 20.0.10inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python2-setuptools' should probably not be an input at all
python-jaraco-packaging @ 6.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-virtualenv @ 20.0.10inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python2-pybugz @ 0.6.11patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 3792 is way too long (152 characters)
scons @ 3.0.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4357 is way too long (105 characters)
python-ipython-documentation @ 7.9.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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
mdadm-static @ 4.1description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-pyvenv @ 1.21description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-flx @ 0.6.1description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 137
emacs-nhexl-mode @ 1.4description

Validate package descriptions

use @code or similar ornament instead of quotes
ecasound @ 2.9.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471
gnome-tweaks @ 3.32.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
eolie @ 0.9.98.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
lollypop @ 1.2.7inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
cheese @ 3.32.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gexiv2 @ 0.12.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
terminator @ 1.91inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
emacs-discover-my-major @ 1.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
emacs-haskell-mode @ 16.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
emacs-mit-scheme-doc @ 20140203formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 387 is way too long (95 characters)
emacs-gtk-look @ 29formatting

Look for formatting issues in the source

line 16958 is way too long (94 characters)
audacity @ 2.3.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
gdm @ 3.32.0formatting

Look for formatting issues in the source

line 6991 is way too long (103 characters)
emacs-dash-docs @ 1.4.0-1.111fd9bformatting

Look for formatting issues in the source

line 19229 is way too long (91 characters)
zita-resampler @ 1.3.0formatting

Look for formatting issues in the source

line 3131 is way too long (93 characters)
network-manager @ 1.18.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 6538 is way too long (117 characters)
vamp @ 2.6formatting

Look for formatting issues in the source

line 2628 is way too long (94 characters)
emacs-exwm @ 0.23formatting

Look for formatting issues in the source

line 9747 is way too long (96 characters)
java-kxml2 @ 2.4.2description

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-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-xpp3 @ 1.1.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 188
java-fasterxml-jackson-core @ 2.9.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
java-native-access-platform @ 4.5.1description

Validate package descriptions

description should start with an upper-case letter or digit
java-hamcrest-all @ 1.3source-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-woodstox-core @ 5.0.3source-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-javaewah @ 1.1.6source-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-ops4j-base-util-property @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-modules-base-jaxb @ 2.9.4source-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-api @ 2.8.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-guice @ 4.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jmock-junit4 @ 2.8.2source-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-ops4j-base-monitors @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-modello-plugins-xpp3 @ 1.9.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-plexus-utils @ 3.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-plexus-archiver @ 4.1.0source-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-fasterxml-jackson-dataformat-xml @ 2.9.4source-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-ops4j-base-io @ 1.5.0source-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-xmlunit-legacy @ 2.5.1source-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-stringtemplate @ 4.0.8source-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-ops4j-base-lang @ 1.5.0source-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-objenesis @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-microemulator-cldc @ 2.0.4source-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-plexus-cipher @ 1.7source-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-modello-plugins-java @ 1.9.1source-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-joda-time @ 2.9.9source-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-plexus-interpolation @ 1.23source-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-fest-util @ 1.2.5source-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-plexus-classworlds @ 2.5.2source-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-fasterxml-jackson-core @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-annotations @ 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-datanucleus-javax-persistence @ 2.2.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-sisu-build-api @ 0.0.7source-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-logback-core @ 1.2.3source-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-powermock-modules-junit4-common @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-container-default @ 1.7.1source-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-powermock-modules-junit4 @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-interceptors-api-spec @ 1.2source-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-api-easymock @ 1.7.3source-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-jline @ 2.14.5source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-core @ 0.0.8source-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-fest-assert @ 2.0M10source-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-aqute-libg @ 3.5.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-native-access @ 4.5.1source-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-fasterxml-jackson-modules-base-mrbean @ 2.9.4source-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-jsch-agentproxy-connector-factory @ 0.0.8source-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-jsch-agentproxy-pageant @ 0.0.8source-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-ops4j-pax-exam-core @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jansi-native @ 1.7source-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-jcommander @ 1.71source-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-modello-core @ 1.9.1source-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-native-access-platform @ 4.5.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-modules-junit4-common @ 1.7.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
java-commons-httpclient @ 3.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8682 is way too long (98 characters)
java-testng @ 6.14.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7918 is way too long (110 characters)
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8259 is way too long (100 characters)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

line 4958 is way too long (91 characters)
java-joda-time @ 2.9.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4005 is way too long (107 characters)
java-logback-classic @ 1.2.3formatting

Look for formatting issues in the source

line 11380 is way too long (102 characters)
java-hawtjni @ 1.15formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 11060 is way too long (101 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6370, column 20
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

line 8117 is way too long (91 characters)
java-commons-jxpath @ 1.3formatting

Look for formatting issues in the source

line 5208 is way too long (93 characters)
java-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

line 3475 is way too long (112 characters)
fakeroot @ 1.24description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 114, 240
perftest @ 4.4-0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
ecryptfs-utils @ 111description

Validate package descriptions

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

Identify inputs that should be native inputs

'libtool' should probably be a native input
procenv @ 0.51inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
nftables @ 0.9.3inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
nftables @ 0.9.3inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
jmtpfs @ 0.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
procenv @ 0.51source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
proot-static @ 5.1.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
freefall @ 5.4.25patch-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.25patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

line 4741 is way too long (98 characters)
python2-dukpy @ 0.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-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
python2-argcomplete @ 1.10.3description

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
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-editor @ 1.0.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-py3status @ 3.21description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
wxwidgets-gtk2 @ 3.1.0description

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-legacy-api-wrap @ 1.2inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

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

Identify inputs that shouldn't be inputs at all

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
libgccjit @ 9.3.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python2-waitress @ 1.1.0patch-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.110patch-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
python-file @ 5.33patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-headers @ 4.19.110patch-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.110patch-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
gccgo @ 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
python2-configobj @ 5.0.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre @ 4.19.110formatting

Look for formatting issues in the source

line 757 is way too long (117 characters)
python-wtforms @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2851 is way too long (100 characters)
linux-libre-arm-omap2plus @ 4.19.110formatting

Look for formatting issues in the source

line 757 is way too long (117 characters)
python-hy @ 0.17.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 9087, column 0
python2-wtforms @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 825 is way too long (91 characters)
linux-libre-arm-generic @ 4.19.110formatting

Look for formatting issues in the source

line 757 is way too long (117 characters)
python2-hy @ 0.17.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 9087, column 0
python-cloudpickle @ 0.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 16575 is way too long (97 characters)
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4624, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4625, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4626, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4627, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4629, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4636, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4637, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4638, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4639, column 0
rosegarden @ 18.12formatting

Look for formatting issues in the source

line 4150 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
ocaml4.07-sexplib @ 0.11.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ocaml4.07-sedlex @ 2.1formatting

Look for formatting issues in the source

line 2073 is way too long (97 characters)
ocamlify @ 0.0.1formatting

Look for formatting issues in the source

line 2243 is way too long (98 characters)