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-pinebook @ 2020.01description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
python2-twobitreader @ 3.1.6description

Validate package descriptions

description should start with an upper-case letter or digit
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
wxwidgets-gtk2 @ 3.0.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
python-bx-python @ 0.8.2description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 157
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
python-twobitreader @ 3.1.6description

Validate package descriptions

description should start with an upper-case letter or digit
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
nsis-x86_64 @ 3.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ruby-haml @ 5.0.4description

Validate package descriptions

description should start with an upper-case letter or digit
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
espeak-ng @ 1.49.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
python-fpylll @ 0.4.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
u-boot-a20-olinuxino-lime2 @ 2020.01description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
mpfi @ 1.5.3description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
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
nsis-i686 @ 3.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
u-boot-puma-rk3399 @ 2020.01description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
python2-bx-python @ 0.8.2description

Validate package descriptions

description should start with an upper-case letter or digit
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
clipper @ 1.2.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' 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
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
template-glib @ 3.32.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'desktop-file-utils' 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
gerbv @ 2.7.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
kicad @ 5.1.5inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' 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
pcb-rnd @ 1.1.3inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
man-db @ 2.9.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
c-reduce @ 2.10.0inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
a2ps @ 4.14inputs-should-be-native

Identify inputs that should be native inputs

'groff' 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
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
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
gpsbabel @ 1.5.4inputs-should-be-native

Identify inputs that should be native inputs

'qttools' 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
gcc-objc @ 4.8.5patch-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
gcc-objc++ @ 6.5.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
gcc-objc @ 4.9.4patch-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
gcc-objc++ @ 4.9.4patch-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
gcc-objc++ @ 5.5.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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
mingw-w64-i686 @ 6.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libstdc++-doc @ 5.5.0patch-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
java-openmpi @ 4.0.2patch-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
clang-runtime @ 3.9.1patch-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
gcc-objc++ @ 4.8.5patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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
libstdc++-doc @ 9.2.0patch-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
gcc-objc @ 8.3.0patch-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
nsis-x86_64 @ 3.04patch-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
python-next @ 3.8.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
kodi-wayland @ 18.4patch-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
fastboot @ 7.1.2_r36patch-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
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
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
mingw-w64-i686-winpthreads @ 6.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
bash-minimal @ 5.0.7patch-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
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
openmpi-thread-multiple @ 4.0.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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
clang-runtime @ 3.5.2patch-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
gcc-objc++ @ 7.4.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
mkbootimg @ 7.1.2_r36patch-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
emacs-minimal @ 26.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
emacs-erlang @ 21.0.5patch-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
nsis-i686 @ 3.04patch-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
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
gcc-objc @ 5.5.0patch-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
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
gcc-objc @ 6.5.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
blasr-libcpp @ 5.3.3formatting

Look for formatting issues in the source

line 581 is way too long (95 characters)
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)
gx @ 0.14.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2449 is way too long (93 characters)
libjxr @ 1.1formatting

Look for formatting issues in the source

line 483 is way too long (95 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)
mingw-w64-i686 @ 6.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 104 is way too long (92 characters)
gap @ 4.10.2formatting

Look for formatting issues in the source

trailing white space on line 1156
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)
clang @ 8.0.0formatting

Look for formatting issues in the source

line 231 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)
r-shiny @ 1.4.0formatting

Look for formatting issues in the source

line 809 is way too long (92 characters)
clang @ 3.5.2formatting

Look for formatting issues in the source

line 231 is way too long (95 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)
powertabeditor @ 2.0.0-alpha10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2933 is way too long (91 characters)
nsis-x86_64 @ 3.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 118 is way too long (114 characters)
glibc @ 2.29formatting

Look for formatting issues in the source

line 690 is way too long (98 characters)
minizip @ 1.2.11formatting

Look for formatting issues in the source

line 142 is way too long (115 characters)
openmpi @ 4.0.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 244 is way too long (96 characters)
android-libutils @ 7.1.2_r36formatting

Look for formatting issues in the source

line 618 is way too long (114 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)
eigen @ 3.3.5formatting

Look for formatting issues in the source

tabulation on line 941, column 0
cl-strings @ 0.0.0-1.c5c5cbaformatting

Look for formatting issues in the source

line 1104 is way too long (98 characters)
clang @ 6.0.1formatting

Look for formatting issues in the source

line 231 is way too long (95 characters)
python-pygobject @ 3.28.3formatting

Look for formatting issues in the source

line 701 is way too long (95 characters)
fastboot @ 7.1.2_r36formatting

Look for formatting issues in the source

line 676 is way too long (105 characters)
maven-shared-utils @ 3.2.1formatting

Look for formatting issues in the source

line 357 is way too long (109 characters)
clang @ 3.7.1formatting

Look for formatting issues in the source

line 231 is way too long (95 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)
mingw-w64-i686-winpthreads @ 6.0.0formatting

Look for formatting issues in the source

line 87 is way too long (91 characters)
clang @ 9.0.0formatting

Look for formatting issues in the source

line 231 is way too long (95 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)
clang @ 7.0.1formatting

Look for formatting issues in the source

line 231 is way too long (95 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)
symmetrica @ 2.0formatting

Look for formatting issues in the source

line 1362 is way too long (100 characters)
xproto @ 7.0.31formatting

Look for formatting issues in the source

line 4769 is way too long (91 characters)
maven-embedder @ 3.6.1formatting

Look for formatting issues in the source

line 1271 is way too long (110 characters)
java-jbzip2 @ 0.9.1formatting

Look for formatting issues in the source

line 264 is way too long (92 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
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 611 is way too long (99 characters)
clang @ 3.8.1formatting

Look for formatting issues in the source

line 231 is way too long (95 characters)
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)
sbcl-cl-strings @ 0.0.0-1.c5c5cbaformatting

Look for formatting issues in the source

line 1104 is way too long (98 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)
python-llvmlite @ 0.30.0formatting

Look for formatting issues in the source

line 727 is way too long (92 characters)
clang @ 3.6.2formatting

Look for formatting issues in the source

line 231 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)
php @ 7.4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 595 is way too long (93 characters)
mingw-w64-x86_64 @ 6.0.0formatting

Look for formatting issues in the source

line 87 is way too long (91 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
nsis-i686 @ 3.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 118 is way too long (114 characters)
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)
clang @ 3.9.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 372 is way too long (97 characters)
libdaemon @ 0.14formatting

Look for formatting issues in the source

line 35 is way too long (147 characters)
android-safe-iop @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1104 is way too long (98 characters)
u-boot-cubietruck @ 2020.01formatting

Look for formatting issues in the source

line 595 is way too long (93 characters)
appstream-glib @ 0.7.16formatting

Look for formatting issues in the source

line 944 is way too long (93 characters)
solfege @ 3.22.2formatting

Look for formatting issues in the source

line 1208 is way too long (92 characters)
texlive-bin @ 20180414formatting

Look for formatting issues in the source

line 270 is way too long (91 characters)
python-asn1crypto @ 0.24.0description

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
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-pycrypto @ 2.6.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
alsa-modular-synth @ 2.1.2inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
go-github.com-smartystreets-goconvey @ 1.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 33
telegram-purple @ 1.4.2inputs-should-be-native

Identify inputs that should be native inputs

'gettext' should probably be a native input
go-github.com-smartystreets-goconvey @ 1.6.3formatting

Look for formatting issues in the source

line 510 is way too long (91 characters)
xygrib @ 1.2.6.1description

Validate package descriptions

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
xygrib @ 1.2.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 387 is way too long (92 characters)
josm @ 15553formatting

Look for formatting issues in the source

tabulation on line 1144, column 0
josm @ 15553formatting

Look for formatting issues in the source

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

Validate package descriptions

description should start with an upper-case letter or digit
java-kxml2 @ 2.4.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-xpp3 @ 1.1.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 188
python2-mox3 @ 0.24.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

line 2024 is way too long (91 characters)
python2-keystoneclient @ 1.8.1formatting

Look for formatting issues in the source

line 802 is way too long (102 characters)
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
guile-next @ 3.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
plotutils @ 2.6formatting

Look for formatting issues in the source

trailing white space on line 81
python-discogs-client @ 2.2.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
vmpk @ 0.7.2inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
python-pyportmidi @ 217patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
vmpk @ 0.7.2formatting

Look for formatting issues in the source

line 2140 is way too long (91 characters)
drumstick @ 1.1.3formatting

Look for formatting issues in the source

line 2095 is way too long (91 characters)
sbcl-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-md5 @ 2.0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
cl-quri @ 0.1.0-1.76b7510description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 68
java-javaewah @ 1.1.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 310
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-fasterxml-jackson-core @ 2.9.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
java-native-access-platform @ 4.5.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
java-jsch-agentproxy-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-powermock-modules-junit4-common @ 1.7.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 9119 is way too long (91 characters)
java-native-access @ 4.5.1formatting

Look for formatting issues in the source

line 10804 is way too long (91 characters)
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6335, column 20
java-commons-httpclient @ 3.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3440 is way too long (112 characters)
java-jgit @ 4.2.0.201601211800-rformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8367 is way too long (96 characters)
java-joda-time @ 2.9.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8319 is way too long (93 characters)
java-logback-classic @ 1.2.3formatting

Look for formatting issues in the source

line 11345 is way too long (102 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

line 10625 is way too long (92 characters)
java-commons-jxpath @ 1.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8647 is way too long (98 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)
java-openjfx-base @ 8.202formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2407 is way too long (99 characters)
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

line 8082 is way too long (91 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)
java-apache-ivy @ 2.4.0formatting

Look for formatting issues in the source

line 11025 is way too long (101 characters)
java-jnacl @ 0.1.0-2.094e819formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9881 is way too long (92 characters)
java-hawtjni @ 1.15formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9934 is way too long (122 characters)
icedtea @ 3.7.0formatting

Look for formatting issues in the source

line 1662 is way too long (109 characters)
akonadi @ 19.08.3patch-file-names

Validate file names and availability of patches

akonadi-Revert-Make-installation-properly-relocatabl.patch: file name is too long
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
gnome-contacts @ 3.32.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gcr @ 3.28.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
glade @ 3.22.1formatting

Look for formatting issues in the source

line 1988 is way too long (91 characters)
gnome-keyring @ 3.28.2formatting

Look for formatting issues in the source

line 1447 is way too long (91 characters)
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
jami @ 20191101.3.67671e7inputs-should-be-native

Identify inputs that should be native inputs

'gettext' should probably be a native input
xorg-server @ 1.20.7patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python-testtools-bootstrap @ 2.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-unittest2 @ 1.1.0patch-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
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
java-picard @ 1.113formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3825 is way too long (117 characters)
pjproject-jami @ 2.9formatting

Look for formatting issues in the source

line 786 is way too long (103 characters)
libringclient @ 20191101.3.67671e7formatting

Look for formatting issues in the source

line 888 is way too long (105 characters)
discrover @ 1.6.0formatting

Look for formatting issues in the source

line 2675 is way too long (91 characters)
java-picard @ 2.10.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3767 is way too long (91 characters)
java-picard @ 2.3.0formatting

Look for formatting issues in the source

line 3678 is way too long (104 characters)
pjproject @ 2.9formatting

Look for formatting issues in the source

line 664 is way too long (103 characters)
jami @ 20191101.3.67671e7formatting

Look for formatting issues in the source

line 933 is way too long (92 characters)
grantleetheme @ 19.08.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile-dbd-sqlite3 @ 2.1.6description

Validate package descriptions

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

Look for formatting issues in the source

line 1251 is way too long (94 characters)
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)
go-github-com-davecgh-go-spew @ 0.0.0-0.d8f796aformatting

Look for formatting issues in the source

line 1880 is way too long (129 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
bind @ 9.14.10description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 253
libdazzle @ 3.33.90inputs-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
lollypop @ 1.2.7inputs-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
mongodb @ 3.4.10formatting

Look for formatting issues in the source

line 592 is way too long (99 characters)
mariadb @ 10.1.43formatting

Look for formatting issues in the source

line 800 is way too long (92 characters)
mariadb @ 10.1.43formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
graphene @ 1.6.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile3.0-readline @ 3.0.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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-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
gtk+ @ 3.24.13patch-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)
guile3.0-readline @ 3.0.0formatting

Look for formatting issues in the source

line 351 is way too long (94 characters)
guile-readline @ 2.2.6formatting

Look for formatting issues in the source

line 351 is way too long (94 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)
guile-ncurses-with-gpm @ 3.0description

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
guile2.0-commonmark @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
wine64-staging @ 5.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Validate file names and availability of patches

file names of patches should start with the package name
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
tensorflow @ 1.9.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python2-fastlmm @ 0.2.21formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1582 is way too long (137 characters)
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
ocaml-qcheck @ 0.12description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 51
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
r-systemfonts @ 0.1.1description

Validate package descriptions

use @code or similar ornament instead of quotes
r-bootstrap @ 2019.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 92, 105
r-circular @ 0.4-93description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 92, 113
r-cmprsk @ 2.2-9description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 232, 243, 262
r-r2glmm @ 0.1.2description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-arm @ 1.10-1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 46, 60
r-haplo-stats @ 1.7.9formatting

Look for formatting issues in the source

line 13433 is way too long (103 characters)
r-flexdashboard @ 0.5.1.1formatting

Look for formatting issues in the source

line 14667 is way too long (96 characters)
r-flexdashboard @ 0.5.1.1formatting

Look for formatting issues in the source

line 14681 is way too long (96 characters)
r-flexdashboard @ 0.5.1.1formatting

Look for formatting issues in the source

line 14688 is way too long (117 characters)
r-flexdashboard @ 0.5.1.1formatting

Look for formatting issues in the source

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
zita-resampler @ 1.3.0formatting

Look for formatting issues in the source

line 3129 is way too long (93 characters)
ocaml4.07-sedlex @ 2.1formatting

Look for formatting issues in the source

line 2080 is way too long (97 characters)
vamp @ 2.6formatting

Look for formatting issues in the source

line 2626 is way too long (94 characters)
ocamlify @ 0.0.1formatting

Look for formatting issues in the source

line 2250 is way too long (98 characters)
ghc-hxt-unicode @ 9.0.2.4description

Validate package descriptions

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

Validate package descriptions

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

Validate file names and availability of patches

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
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
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-rockpro64-rk3399 @ 2020.01description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 79
u-boot-rock64-rk3328 @ 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
sdl-pango @ 0.1.2patch-file-names

Validate file names and availability of patches

sdl-pango-fix-explicit-SDLPango_CopyFTBitmapToSurface.patch: file name is too long
cl-portable-threads @ 2.3-1.c0e61a1formatting

Look for formatting issues in the source

line 3168 is way too long (94 characters)
sdl-mixer @ 1.2.12formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2597 is way too long (130 characters)
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2843 is way too long (91 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)
ecl-portable-threads @ 2.3-1.c0e61a1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2597 is way too long (130 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)
python2-html2text @ 2019.8.11description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
awscli @ 1.14.41inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
python2-paste @ 3.0.6patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2859 is way too long (100 characters)
gparted @ 1.1.0inputs-should-be-native

Identify inputs that should be native inputs

'yelp-tools' should probably be a native input
libblockdev @ 2.23inputs-should-be-native

Identify inputs that should be native inputs

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

Look for formatting issues in the source

line 680 is way too long (91 characters)
ibus-libhangul @ 1.5.3description

Validate package descriptions

description should start with an upper-case letter or digit
gst-transcoder @ 1.12.2inputs-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
ibus-anthy @ 1.5.9inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gettext' should probably be a native input
gaupol @ 1.7formatting

Look for formatting issues in the source

line 3689 is way too long (95 characters)
librime @ 1.5.3formatting

Look for formatting issues in the source

line 327 is way too long (93 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
cl-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2288 is way too long (96 characters)
libsoup @ 2.68.3formatting

Look for formatting issues in the source

line 3690 is way too long (128 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)
tuxmath @ 2.0.3description

Validate package descriptions

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1226 is way too long (107 characters)
mkvtoolnix @ 37.0.0formatting

Look for formatting issues in the source

line 418 is way too long (96 characters)
python-psutil @ 5.6.5description

Validate package descriptions

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

Validate package descriptions

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

Validate file names and availability of patches

file names of patches should start with the package name
scons @ 3.0.4formatting

Look for formatting issues in the source

line 1554 is way too long (96 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
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-unsafe @ 0.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-fsnotify @ 0.3.0.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 81
ghc-regex-tdfa @ 1.2.3.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 139
ghc-operational @ 0.2.3.5description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-inline-c @ 0.7.0.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ghc-llvm-hs-pure @ 9.0.0description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-llvm-hs @ 9.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-system-filepath @ 0.4.14formatting

Look for formatting issues in the source

line 11326 is way too long (250 characters)
ghc-xdg-basedir @ 0.2.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 903 is way too long (101 characters)
i3-wm @ 4.17.1description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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
perl-class-load @ 0.25description

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-devel-globaldestruction @ 0.14description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
perl-file-readbackwards @ 1.05description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 47
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 8237 is way too long (97 characters)
fish @ 3.0.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

'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
bazaar @ 2.7.0formatting

Look for formatting issues in the source

line 140 is way too long (93 characters)
git-crypt @ 0.6.0formatting

Look for formatting issues in the source

line 623 is way too long (91 characters)
vim-full @ 8.2.0236formatting

Look for formatting issues in the source

line 193 is way too long (94 characters)
qtcharts @ 5.12.7description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 244
python-psycopg2 @ 2.7.7description

Validate package descriptions

description should start with an upper-case letter or digit
python2-psycopg2 @ 2.7.7description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
kget @ 19.08.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 169
qtdatavis3d @ 5.12.7description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 107, 250
apache-arrow @ 0.10.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 84
python2-pyqt @ 5.12.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
python-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
python2-pyqt @ 5.12.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libical @ 3.0.7patch-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
python-pyqt @ 5.12.3patch-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)
qtsensors @ 5.12.7formatting

Look for formatting issues in the source

line 870 is way too long (97 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)
qtserialport @ 5.12.7formatting

Look for formatting issues in the source

line 1013 is way too long (115 characters)
rust @ 1.26.2formatting

Look for formatting issues in the source

line 745 is way too long (94 characters)
qtmultimedia @ 5.12.7formatting

Look for formatting issues in the source

line 913 is way too long (96 characters)
libical @ 3.0.7formatting

Look for formatting issues in the source

line 68 is way too long (93 characters)
qtbase @ 5.12.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1969 is way too long (105 characters)
lpsolve @ 5.5.2.5description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
eolie @ 0.9.63inputs-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
qtoctave @ 5.2.0inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' 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
geoclue @ 2.5.5inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' 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
gnome-tweaks @ 3.32.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'texinfo' should probably be a native input
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-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
libgee @ 0.20.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
opencascade-occt @ 7.3.0p3inputs-should-be-native

Identify inputs that should be native inputs

'doxygen' should probably be a native input
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
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
network-manager @ 1.18.4patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

tabulation on line 2148, column 0
dune-grid @ 2.6.0formatting

Look for formatting issues in the source

line 4658 is way too long (91 characters)
hdf-java @ 3.3.2formatting

Look for formatting issues in the source

line 1010 is way too long (92 characters)
network-manager @ 1.18.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 6485 is way too long (117 characters)
mumps @ 5.2.1formatting

Look for formatting issues in the source

line 2277 is way too long (94 characters)
pt-scotch @ 6.0.6formatting

Look for formatting issues in the source

tabulation on line 2727, column 0
upower @ 0.99.11formatting

Look for formatting issues in the source

line 4178 is way too long (110 characters)
mumps-openmpi @ 5.2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2553, column 0
scalapack @ 2.0.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2749, column 0
p4est @ 2.0formatting

Look for formatting issues in the source

tabulation on line 2813, column 0
gdm @ 3.32.0formatting

Look for formatting issues in the source

line 6938 is way too long (103 characters)
hypre-openmpi @ 2.15.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2392 is way too long (100 characters)
sundials-openmpi @ 3.1.1formatting

Look for formatting issues in the source

tabulation on line 4447, column 0
gdb @ 9.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'swig' should probably be a native input
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
icecat @ 68.5.0-guix0-preview1formatting

Look for formatting issues in the source

line 854 is way too long (102 characters)
icecat @ 68.5.0-guix0-preview1formatting

Look for formatting issues in the source

trailing white space on line 857
icecat @ 68.5.0-guix0-preview1formatting

Look for formatting issues in the source

trailing white space on line 863
icecat @ 68.5.0-guix0-preview1formatting

Look for formatting issues in the source

line 946 is way too long (139 characters)
icecat @ 68.5.0-guix0-preview1formatting

Look for formatting issues in the source

line 951 is way too long (95 characters)
icecat @ 68.5.0-guix0-preview1formatting

Look for formatting issues in the source

line 995 is way too long (94 characters)
icecat @ 68.5.0-guix0-preview1formatting

Look for formatting issues in the source

line 997 is way too long (95 characters)
icecat @ 68.5.0-guix0-preview1formatting

Look for formatting issues in the source

line 1010 is way too long (98 characters)
containerd @ 1.2.5formatting

Look for formatting issues in the source

line 215 is way too long (102 characters)
docker @ 19.03.5formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 382 is way too long (93 characters)
quaternion @ 0.0.9.4cinputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4606, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4607, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4608, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4609, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4611, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4618, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4619, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4620, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4621, column 0
rosegarden @ 18.12formatting

Look for formatting issues in the source

line 4096 is way too long (93 characters)
r-rtracklayer @ 1.46.0description

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-seqlogo @ 1.52.0description

Validate package descriptions

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

Identify inputs that should be native inputs

'python2-cython' should probably be a native input
mesa-opencl @ 19.3.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
ncbi-vdb @ 2.9.6formatting

Look for formatting issues in the source

tabulation on line 5656, column 26
mesa @ 19.3.2formatting

Look for formatting issues in the source

line 295 is way too long (100 characters)
syncthing @ 1.3.4formatting

Look for formatting issues in the source

line 96 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 2249 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 2252 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 2369 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 2370 is way too long (93 characters)
go-github-com-mitchellh-go-homedir @ 1.0.0-0.ae18d6bformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2326 is way too long (93 characters)
go-github-com-libp2p-go-libp2p-peer @ 2.3.8-0.993d742formatting

Look for formatting issues in the source

line 2193 is way too long (93 characters)
java-plexus-compiler-javac @ 2.8.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-bouncycastle @ 1.60source-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
ocaml4.07-piqi @ 0.7.7source-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-plexus-cipher @ 1.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
kdevelop-pg-qt @ 2.2.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-component-annotations @ 1.7.1source-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-jboss-interceptors-api-spec @ 1.2source-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
nanovg-for-extempore @ 0.7.1source-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-ops4j-base-store @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jsch-agentproxy-core @ 0.0.8source-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
java-jline @ 2.14.5source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-guice @ 4.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-modules-base-jaxb @ 2.9.4source-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-xmlunit-matchers @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-javassist @ 3.21.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-powermock-api-support @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-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
tegola @ 0.7.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-fasterxml-jackson-databind @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jmock @ 1.2.0source-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-ops4j-pax-exam-core-spi @ 4.11.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-reflect @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
alot @ 0.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
qtox @ 1.16.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fest-assert @ 2.0M10source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-aqute-libg @ 3.5.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
java-hamcrest-all @ 1.3source-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-connector-factory @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-iq80-snappy @ 0.4source-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-fasterxml-jackson-dataformat-yaml @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-sisu-build-api @ 0.0.7source-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
mongodb @ 3.4.10source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
sparql-query @ 1.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
nototools @ 20170925source-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-plexus-compiler-api @ 2.8.4source-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-modello-plugins-xpp3 @ 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-ops4j-base-lang @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-classworlds @ 2.5.2source-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-woodstox-core @ 5.0.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
sorcer @ 1.1.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-xmlunit @ 2.5.1source-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
python2-mapnik @ 3.0.16source-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-core @ 1.7.3source-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
java-jboss-el-api-spec @ 3.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
sqlcipher @ 3.4.2source-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-plexus-interpolation @ 1.23source-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
sonata @ 1.7b1source-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
antlr3 @ 3.5.2source-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
texlive-latex-hyperref @ 6.84a2source-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-ops4j-base-util-property @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-rsyntaxtextarea @ 2.6.1source-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
vowpal-wabbit @ 8.5.0source-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-junit @ 4.12source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-xerial-core @ 2.1source-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-jsch-agentproxy-usocket-jna @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-sec-dispatcher @ 1.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-gson @ 2.8.2source-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
librecad @ 2.1.3source-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
java-javaewah @ 1.1.6source-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-jboss-jms-api-spec @ 2.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-container-default @ 1.7.1source-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-guice-servlet @ 4.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-hdrhistogram @ 2.1.9source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-annotations @ 2.9.4source-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
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-joda-time @ 2.9.9source-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-fest-test @ 2.1.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-fest-util @ 1.2.5source-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-joda-convert @ 1.9.2source-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-ops4j-pax-exam-core-junit @ 4.11.0source-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
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'
diffoscope @ 136formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
audacity @ 2.3.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
patchwork @ 2.1.5formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
rosegarden @ 18.12formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
kget @ 19.08.3formatting

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
wine64 @ 5.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libsoup @ 2.68.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libblockdev @ 2.23formatting

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
go-github-com-mattn-go-shellwords @ 1.0.5-1.2444a32formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
petsc @ 3.11.2formatting

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
wine-staging @ 5.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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
arm-trusted-firmware-rk3328 @ 2.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ghc-vector @ 0.12.0.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
wine @ 5.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
mtr @ 0.93description

Validate package descriptions

description should start with an upper-case letter or digit
iwd @ 0.21inputs-should-be-native

Identify inputs that should be native inputs

'libtool' should probably be a native input
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
nethogs @ 0.8.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
restinio @ 0.6.0.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2525 is way too long (92 characters)
emacs-hercules @ 0.2.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 220
emacs-el-x @ 0.3.1description

Validate package descriptions

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
emacs-undohist-el @ 0-1.d2239a5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-haskell-mode @ 16.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mrustc @ 0.9formatting

Look for formatting issues in the source

line 149 is way too long (123 characters)
emacs-exwm @ 0.23formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4290 is way too long (94 characters)
nginx-accept-language-module @ 0.0.0-1.2f69842formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 934
emacs-gtk-look @ 29formatting

Look for formatting issues in the source

line 16831 is way too long (94 characters)
emacs-dash-docs @ 1.4.0-1.111fd9bformatting

Look for formatting issues in the source

line 19100 is way too long (91 characters)
python-q @ 2.6description

Validate package descriptions

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

Validate package descriptions

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

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-apispec @ 0.25.3description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-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-dbus @ 1.2.14description

Validate package descriptions

description should start with an upper-case letter or digit
python-py3status @ 3.21description

Validate package descriptions

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

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

Validate package descriptions

use @code or similar ornament instead of quotes
python-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
ptpython2 @ 0.34description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
python-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
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-file @ 5.33patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python2-pep8 @ 1.7.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
python-numpy @ 1.17.3formatting

Look for formatting issues in the source

line 3452 is way too long (152 characters)
python2-cloudpickle @ 0.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 8590, column 0
python-cloudpickle @ 0.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 15915 is way too long (97 characters)
python-binwalk @ 2.1.1-0.64201acformatting

Look for formatting issues in the source

line 11220 is way too long (106 characters)
python-hy @ 0.17.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python2-seaborn @ 0.9.0formatting

Look for formatting issues in the source

line 6099 is way too long (99 characters)
python-seaborn @ 0.9.0formatting

Look for formatting issues in the source

line 6099 is way too long (99 characters)
python-matplotlib @ 3.1.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4021 is way too long (105 characters)
sbcl-cl-reexport @ 0.1-1.312f366description

Validate package descriptions

description should start with an upper-case letter or digit
cl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
sbcl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

description should start with an upper-case letter or digit
ecl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
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
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 @ 0.0.19-0.b4f27d9inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre @ 4.9.214patch-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.171patch-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-graph-dot @ 0.0.0-0.78bf9ecpatch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-omap2plus @ 4.14.171patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre @ 4.4.214formatting

Look for formatting issues in the source

line 754 is way too long (117 characters)
linux-libre @ 4.14.171formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 6109 is way too long (104 characters)
linux-libre @ 4.9.214formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 754 is way too long (117 characters)
abc @ 0.0-1-5ae4b975cformatting

Look for formatting issues in the source

line 83 is way too long (95 characters)
cl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
cl-dbus @ 20190408-1.24b452dformatting

Look for formatting issues in the source

line 6337 is way too long (104 characters)
linux-libre-arm-omap2plus @ 4.14.171formatting

Look for formatting issues in the source

line 754 is way too long (117 characters)
mgba @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
xdg-user-dirs @ 0.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
telepathy-mission-control @ 5.16.5inputs-should-be-native

Identify inputs that should be native inputs

'gtk-doc' should probably be a native input
udiskie @ 2.0.4inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
udisks @ 2.7.7formatting

Look for formatting issues in the source

line 858 is way too long (97 characters)
localed @ 241formatting

Look for formatting issues in the source

line 490 is way too long (96 characters)
elixir @ 1.10.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 76 is way too long (99 characters)
cadaver @ 0.23.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 48
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
fasm @ 1.73.22description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
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
wpa-supplicant @ 2.9description

Validate package descriptions

description should start with an upper-case letter or digit
httrack @ 3.49.2description

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
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
wpa-supplicant-minimal @ 2.9description

Validate package descriptions

description should start with an upper-case letter or digit
rapicorn @ 16.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-cython' should probably be a native input
sudo @ 1.8.31inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
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-perf-helper @ 4.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-security @ 9.2.22source-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-xml @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-http @ 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-http @ 9.4.6source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-eclipse-jetty-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-test-helper @ 4.2source-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
ctl @ 1.5.2source-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-util @ 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
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
openexr @ 2.4.1patch-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)
unbound @ 1.9.6formatting

Look for formatting issues in the source

trailing white space on line 466
unbound @ 1.9.6formatting

Look for formatting issues in the source

trailing white space on line 502
serf @ 1.3.9formatting

Look for formatting issues in the source

line 1598 is way too long (92 characters)
varnish @ 6.3.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 5173, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5174, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5175, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5176, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5177, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5183, column 0
netsurf @ 3.9formatting

Look for formatting issues in the source

tabulation on line 5184, column 0
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

line 4923 is way too long (91 characters)
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 449 is way too long (92 characters)
libreoffice @ 6.4.0.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
zathura-djvu @ 0.2.8formatting

Look for formatting issues in the source

line 399 is way too long (93 characters)
zathura-pdf-poppler @ 0.2.9formatting

Look for formatting issues in the source

line 479 is way too long (107 characters)
python2-pygame @ 1.9.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 123
fifengine @ 0.4.2description

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
chroma @ 1.17description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
warzone2100 @ 3.2.3description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
nethack @ 3.6.5inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
nethack @ 3.6.5inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'swig' should probably be a native input
openmw @ 0.45.0source-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
crawl-tiles @ 0.24.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
lure-it @ 1.1formatting

Look for formatting issues in the source

line 7858 is way too long (93 characters)
einstein @ 2.0formatting

Look for formatting issues in the source

line 3289 is way too long (96 characters)
qemu-minimal @ 4.2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 5563, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5564, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 5567, column 0
drascula @ 1.0formatting

Look for formatting issues in the source

line 7757 is way too long (93 characters)
queen-de @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7958 is way too long (205 characters)
btanks @ 0.9.8083formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6832, column 18
btanks @ 0.9.8083formatting

Look for formatting issues in the source

tabulation on line 6833, column 17
qemu @ 4.2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 702
freeorion @ 0.4.9formatting

Look for formatting issues in the source

line 8242 is way too long (92 characters)
xen @ 4.11.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
lure-es @ 1.1formatting

Look for formatting issues in the source

line 7858 is way too long (93 characters)
sky @ 1.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8157 is way too long (100 characters)
lure-fr @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7958 is way too long (205 characters)
queen-it @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7958 is way too long (205 characters)
lure-de @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 357 is way too long (106 characters)
xftwidth @ 20170402description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 96, 234
mrrescue @ 1.02edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 2
xcalib @ 0.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
racket-minimal @ 7.6patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

tabulation on line 1476, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1477, 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 1480, column 0
rust-rustc-tools-util @ 0.2.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-diagram @ 1.6.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 336
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
python-rpy2 @ 3.0.4-1.19868a8description

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-bseqsc @ 1.0-1.fef3f3edescription

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-yapsa @ 1.12.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-tidyr @ 1.0.2description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 45, 56
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
rhash @ 1.3.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
r-unifiedwmwqpcr @ 1.22.0formatting

Look for formatting issues in the source

line 6615 is way too long (92 characters)
r-genomicinteractions @ 1.20.0formatting

Look for formatting issues in the source

line 1941 is way too long (92 characters)
libsecp256k1 @ 20191213-1.d644ddaformatting

Look for formatting issues in the source

line 921 is way too long (106 characters)
r-squarem @ 2020.1formatting

Look for formatting issues in the source

line 2650 is way too long (91 characters)
r-hsmmsinglecell @ 1.2.0formatting

Look for formatting issues in the source

line 912 is way too long (95 characters)
r-colourpicker @ 1.0formatting

Look for formatting issues in the source

line 12185 is way too long (94 characters)
salmon @ 0.13.1formatting

Look for formatting issues in the source

line 11892 is way too long (99 characters)
r-rhdf5lib @ 1.8.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10541 is way too long (104 characters)
emacs-ess @ 17.11formatting

Look for formatting issues in the source

line 5785 is way too long (106 characters)
freebayes @ 1.0.2-1.3ce827dformatting

Look for formatting issues in the source

tabulation on line 15249, column 28
pigx-scrnaseq @ 0.0.8formatting

Look for formatting issues in the source

tabulation on line 12786, column 0
pigx-scrnaseq @ 0.0.8formatting

Look for formatting issues in the source

tabulation on line 12787, column 0
pigx-scrnaseq @ 0.0.8formatting

Look for formatting issues in the source

tabulation on line 12788, column 0
r-gamlss-dist @ 5.1-6formatting

Look for formatting issues in the source

line 12079 is way too long (91 characters)
r-lumi @ 2.38.0formatting

Look for formatting issues in the source

line 3065 is way too long (95 characters)
r-abps @ 0.3formatting

Look for formatting issues in the source

line 7571 is way too long (93 characters)
r-monocle @ 2.14.0formatting

Look for formatting issues in the source

line 2655 is way too long (101 characters)
dropseq-tools @ 1.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 12487, column 0
java-forester @ 1.005formatting

Look for formatting issues in the source

line 12189 is way too long (92 characters)
linux-libre @ 5.4.21derivation

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

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
linux-libre-headers @ 5.4.21patch-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.105patch-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.21patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre @ 5.4.21patch-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.21patch-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.21patch-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.105patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 754 is way too long (117 characters)
linux-libre @ 5.4.21formatting

Look for formatting issues in the source

line 754 is way too long (117 characters)
linux-libre-arm-veyron @ 5.4.21formatting

Look for formatting issues in the source

line 754 is way too long (117 characters)
linux-libre-riscv64-generic @ 5.4.21formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 754 is way too long (117 characters)
linux-libre @ 4.19.105formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 754 is way too long (117 characters)
perftest @ 4.4-0.4description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 114, 240
ecryptfs-utils @ 111description

Validate package descriptions

description should start with an upper-case letter or digit
mdadm-static @ 4.1description

Validate package descriptions

description should start with an upper-case letter or digit
procenv @ 0.51inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
ell @ 0.23inputs-should-be-native

Identify inputs that should be native inputs

'libtool' 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
procenv @ 0.51source-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
unionfs-fuse-static @ 2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
jmtpfs @ 0.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
unionfs-fuse @ 2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
ddate @ 0.2.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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
x86-energy-perf-policy @ 5.4.21patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perf @ 5.4.21patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
cpupower @ 5.4.21patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
freefall @ 5.4.21patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
proot-static @ 5.1.0patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
wireless-tools @ 30.pre9formatting

Look for formatting issues in the source

line 2989 is way too long (104 characters)
util-linux @ 2.34formatting

Look for formatting issues in the source

line 1199 is way too long (91 characters)
crda @ 3.18formatting

Look for formatting issues in the source

line 3083 is way too long (105 characters)