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
wxwidgets-gtk2 @ 3.1.0description

Validate package descriptions

description should start with an upper-case letter or digit
u-boot-qemu-riscv64 @ 2020.04description

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
python2-pygame @ 1.9.4description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
ocaml-zarith @ 1.9.1description

Validate package descriptions

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

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
python-libfreenect @ 0.6.1description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 121, 206
cl-md5 @ 2.0.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
ghc-tasty-expected-failure @ 0.11.1.2description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
guile3.0-email @ 0.2.2description

Validate package descriptions

description should start with an upper-case letter or digit
c-blosc @ 1.18.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
u-boot-nintendo-nes-classic-edition @ 2020.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
guile2.2-email @ 0.2.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
u-boot-vexpress-ca9x4 @ 2020.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
connman @ 1.38description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
python2-psutil @ 5.7.0description

Validate package descriptions

description should start with an upper-case letter or digit
java-xpp3 @ 1.1.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
ghc-fsnotify @ 0.3.0.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
guile-stis-parser @ 0-1.6e85d37description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 117
zn-poly @ 0.9.2description

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
rcm @ 1.3.3description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-psutil @ 5.7.0description

Validate package descriptions

description should start with an upper-case letter or digit
iml @ 1.0.5description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-boot @ 1.3-25description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 125, 142
texlive-fonts-lm @ 51265description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
wxwidgets-gtk2 @ 3.0.5.1description

Validate package descriptions

description should start with an upper-case letter or digit
u-boot-firefly-rk3399 @ 2020.04description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
jucipp @ 1.6.0description

Validate package descriptions

description should start with an upper-case letter or digit
perl6-grammar-debugger @ 1.0.1-1.0375008description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 78
python-pytools @ 2020.1description

Validate package descriptions

use @code or similar ornament instead of quotes
fstrcmp @ 0.7.D001description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 236
libfreenect-opencv @ 0.6.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
guile3.0-commonmark @ 0.1.2description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
u-boot-malta @ 2020.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
ghc-gtk2hs-buildtools @ 0.13.5.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 95, 367
u-boot-novena @ 2020.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
guile2.2-commonmark @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
ocaml4.07-sexplib @ 0.11.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 42
xdg-user-dirs @ 0.17description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 60
ocaml-topkg @ 1.0.0description

Validate package descriptions

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

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-mx6cuboxi @ 2020.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 166
ruby-rb-inotify @ 0.9.10description

Validate package descriptions

description should start with an upper-case letter or digit
u-boot-bananapi-m2-ultra @ 2020.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
hackrf @ 2018.01.1-0.43e6f99description

Validate package descriptions

use @code or similar ornament instead of quotes
u-boot-a20-olinuxino-lime2 @ 2020.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 75
java-kxml2 @ 2.4.2description

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
u-boot-am335x-evm @ 2020.04description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 93
lpsolve @ 5.5.2.5description

Validate package descriptions

description should start with an upper-case letter or digit
ocaml-qcheck @ 0.12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 52, 156
python-fpylll @ 0.4.1description

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
python-xsge @ 2018.02.26description

Validate package descriptions

description should start with an upper-case letter or digit
xfce4-volumed-pulse @ 0.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
ghc-doclayout @ 0.3description

Validate package descriptions

description should start with an upper-case letter or digit
u-boot-rock64-rk3328 @ 2020.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 68
guile2.0-commonmark @ 0.1.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
rtl-sdr @ 0.6.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
sbcl-circular-streams @ 0.1.0-1.e770baddescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 79
python-sphinxcontrib-programoutput @ 0.15inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' 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
guile3.0-gi @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gnome-shell-extension-gsconnect @ 33inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
guile-gi @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
g-golf @ 1-683.4a4edf2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libringclient @ 20200401.1.6f090deinputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'flex' should probably be a native input
lua-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-pytest-vcr @ 1.0.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python2-sphinx @ 1.7.7inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-pytest-django @ 3.1.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
zbar @ 0.23inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
python-pytest-isort @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python2-pytest-django @ 3.1.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-mox3 @ 0.24.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
wine64-staging @ 5.8inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
opencascade-occt @ 7.3.0p3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
electron-cash @ 4.0.15inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
lxqt @ 0.14.1inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
telepathy-mission-control @ 5.16.5inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' 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
python-sphinx @ 2.3.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
libmypaint @ 1.5.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' 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
gnome-contacts @ 3.34inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'flex' should probably be a native input
slurp @ 1.2.0inputs-should-be-native

Identify inputs that should be native inputs

'scdoc' should probably be a native input
python-coveralls @ 1.11.1inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
guile3.0-mailutils @ 3.9inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
python-fpylll @ 0.4.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'texinfo' 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
python-tempest-lib @ 1.0.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' 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
python-case @ 1.5.3inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-case @ 1.5.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
wine-staging @ 5.8inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
udiskie @ 2.1.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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
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
xaos @ 4.0source-file-name

Validate file names of sources

the source file name should contain the package name
python-libfreenect @ 0.6.1source-file-name

Validate file names of sources

the source file name should contain the package name
libfreenect-opencv @ 0.6.1source-file-name

Validate file names of sources

the source file name should contain the package name
libfreenect-examples @ 0.6.1source-file-name

Validate file names of sources

the source file name should contain the package name
libfreenect @ 0.6.1source-file-name

Validate file names of sources

the source file name should contain the package name
fntsample @ 5.3source-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
cl-md5 @ 2.0.4source-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
nototools @ 20170925source-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
ocaml4.07-piqi @ 0.7.7source-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
lightgbm @ 2.0.12source-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
flatbuffers @ 1.10.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.9-libsanitizer-mode-field.patch: file name is too long
ijs @ 9.52patch-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
emacs-clang-rename @ 9.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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
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
boost-python2 @ 1.72.0patch-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
idutils @ 4.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

python2-pygobject-2-gi-info-type-error-domain.patch: file name is too long
adb @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-next @ 27.0.91-0.c36c5a3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
nsis-i686 @ 3.05patch-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
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
guile2.2-fibers @ 1.0.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.8-libsanitizer-mode-field.patch: file name is too long
u-boot-qemu-riscv64-smode @ 2020.04patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

libgeotiff-adapt-test-script-for-proj-6.2.patch: file name is too long
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
emacs-clang-format @ 9.0.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

xplanet-1.3.1-xpUtil-Add2017LeapSecond.cpp.patch: file name is too long
mumps-openmpi @ 5.2.1patch-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
python-pygpgme @ 0.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
guile2.2-gdbm-ffi @ 20120209.fa1d5b6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-libxml2 @ 2.9.10patch-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
libcanberra-gtk2 @ 0.30patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

gobject-introspection-absolute-shlib-path.patch: file name is too long
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
dune-istl-openmpi @ 2.7.0patch-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
bash-minimal @ 5.0.16patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
fastboot @ 7.1.2_r36patch-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
openmpi-thread-multiple @ 4.0.3patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

tabulation on line 2959, column 0
u-boot-qemu-riscv64 @ 2020.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 133 is way too long (96 characters)
gnunet @ 0.12.2formatting

Look for formatting issues in the source

line 297 is way too long (92 characters)
u-boot-cubieboard @ 2020.04formatting

Look for formatting issues in the source

line 639 is way too long (93 characters)
u-boot-tools @ 2020.04formatting

Look for formatting issues in the source

line 507 is way too long (91 characters)
u-boot-tools @ 2020.04formatting

Look for formatting issues in the source

line 529 is way too long (97 characters)
pth @ 2.0.7formatting

Look for formatting issues in the source

trailing white space on line 42
plymouth @ 0.9.4formatting

Look for formatting issues in the source

line 1731 is way too long (91 characters)
telepathy-glib @ 0.24.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3323 is way too long (94 characters)
symmetrica @ 2.0formatting

Look for formatting issues in the source

line 1377 is way too long (100 characters)
pt-scotch @ 6.0.6formatting

Look for formatting issues in the source

tabulation on line 2937, column 0
libsigsegv @ 2.12formatting

Look for formatting issues in the source

line 48 is way too long (133 characters)
editorconfig-core-c @ 0.12.3formatting

Look for formatting issues in the source

line 684 is way too long (97 characters)
lxqt-session @ 0.14.1formatting

Look for formatting issues in the source

line 852 is way too long (100 characters)
jami @ 20200401.1.6f090deformatting

Look for formatting issues in the source

line 573 is way too long (92 characters)
rust @ 1.25.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
proj.4 @ 4.9.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 151 is way too long (92 characters)
unbound @ 1.10.1formatting

Look for formatting issues in the source

trailing white space on line 471
unbound @ 1.10.1formatting

Look for formatting issues in the source

trailing white space on line 507
gmp @ 6.2.0formatting

Look for formatting issues in the source

line 82 is way too long (96 characters)
u-boot-sifive-fu540 @ 2020.04formatting

Look for formatting issues in the source

line 639 is way too long (93 characters)
libringclient @ 20200401.1.6f090deformatting

Look for formatting issues in the source

line 539 is way too long (105 characters)
r-hsmmsinglecell @ 1.2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1145 is way too long (98 characters)
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 373 is way too long (97 characters)
superlu-dist @ 6.2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2762, column 0
openmpi @ 4.0.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 252 is way too long (96 characters)
emacs-next @ 27.0.91-0.c36c5a3formatting

Look for formatting issues in the source

line 326 is way too long (134 characters)
u-boot-wandboard @ 2020.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 144 is way too long (91 characters)
libdaemon @ 0.14formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
pypy3 @ 7.3.1formatting

Look for formatting issues in the source

line 789 is way too long (91 characters)
u-boot-nintendo-nes-classic-edition @ 2020.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 133 is way too long (96 characters)
u-boot-vexpress-ca9x4 @ 2020.04formatting

Look for formatting issues in the source

line 639 is way too long (93 characters)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 99 is way too long (113 characters)
python2-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1116 is way too long (96 characters)
libnfs @ 3.0.0formatting

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
js-mathjax @ 2.7.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3323 is way too long (94 characters)
python2 @ 2.7.17formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 290 is way too long (98 characters)
hyperledger-iroha @ 1.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 196 is way too long (96 characters)
mergerfs @ 2.29.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
josm @ 15937formatting

Look for formatting issues in the source

tabulation on line 1180, column 0
josm @ 15937formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1172 is way too long (92 characters)
fc-host-tools @ 11formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 510 is way too long (92 characters)
xygrib @ 1.2.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2333 is way too long (96 characters)
slepc-complex-openmpi @ 3.11.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 37 is way too long (92 characters)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 497, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 498, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 499, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 500, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 501, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 502, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 503, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 504, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 505, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 507, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 508, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 509, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 510, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 511, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 513, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 514, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 515, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 516, column 0
next @ 1.5.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 651 is way too long (106 characters)
bazaar @ 2.7.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 778 is way too long (94 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)
sdsl-lite @ 2.1.1formatting

Look for formatting issues in the source

line 226 is way too long (145 characters)
petsc @ 3.11.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 639 is way too long (93 characters)
cryptsetup-static @ 2.2.2formatting

Look for formatting issues in the source

line 102 is way too long (93 characters)
giac @ 1.5.0-87formatting

Look for formatting issues in the source

line 359 is way too long (95 characters)
xproto @ 7.0.31formatting

Look for formatting issues in the source

line 4989 is way too long (91 characters)
shogun @ 6.1.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 626 is way too long (91 characters)
u-boot-pine64-lts @ 2020.04formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
js-filesaver @ 1.3.8formatting

Look for formatting issues in the source

line 392 is way too long (99 characters)
hypre-openmpi @ 2.15.1formatting

Look for formatting issues in the source

tabulation on line 4231, column 0
localed @ 241formatting

Look for formatting issues in the source

line 533 is way too long (96 characters)
python-llvmlite @ 0.30.0formatting

Look for formatting issues in the source

line 943 is way too long (92 characters)
appstream-glib @ 0.7.17formatting

Look for formatting issues in the source

line 961 is way too long (93 characters)
texlive-ruhyphen @ 51265formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 704
slepc-openmpi @ 3.11.1formatting

Look for formatting issues in the source

tabulation on line 2357, column 0
java-xom @ 127formatting

Look for formatting issues in the source

trailing white space on line 1667
git-crypt @ 0.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 118 is way too long (114 characters)
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)
ecl-cl-strings @ 0.0.0-1.c5c5cbaformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2655 is way too long (130 characters)
glusterfs @ 7.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
solfege @ 3.22.2formatting

Look for formatting issues in the source

line 1231 is way too long (92 characters)
wine64-staging @ 5.8formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 223 is way too long (91 characters)
mumps @ 5.2.1formatting

Look for formatting issues in the source

line 2486 is way too long (94 characters)
ruby-asciimath @ 1.0.4formatting

Look for formatting issues in the source

line 2601 is way too long (100 characters)
python @ 3.8.2formatting

Look for formatting issues in the source

line 437 is way too long (93 characters)
u-boot-malta @ 2020.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3025 is way too long (91 characters)
mumps-openmpi @ 5.2.1formatting

Look for formatting issues in the source

tabulation on line 2572, column 0
mrustc @ 0.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 128 is way too long (92 characters)
u-boot-cubietruck @ 2020.04formatting

Look for formatting issues in the source

line 639 is way too long (93 characters)
eigen @ 3.3.7formatting

Look for formatting issues in the source

tabulation on line 982, column 0
android-safe-iop @ 7.1.2_r36formatting

Look for formatting issues in the source

line 423 is way too long (95 characters)
xfce4-clipman-plugin @ 1.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2655 is way too long (130 characters)
gtklick @ 0.6.4formatting

Look for formatting issues in the source

line 849 is way too long (94 characters)
ocaml-dose3 @ 5.0.1formatting

Look for formatting issues in the source

line 362 is way too long (92 characters)
julia @ 1.4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 311 is way too long (106 characters)
u-boot-am335x-boneblack @ 2020.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2333 is way too long (96 characters)
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 521 is way too long (92 characters)
electron-cash @ 4.0.15formatting

Look for formatting issues in the source

line 528 is way too long (116 characters)
ocamlify @ 0.0.1formatting

Look for formatting issues in the source

line 2251 is way too long (98 characters)
u-boot-mx6cuboxi @ 2020.04formatting

Look for formatting issues in the source

line 639 is way too long (93 characters)
pjproject @ 2.10formatting

Look for formatting issues in the source

line 789 is way too long (103 characters)
wine64 @ 5.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 98 is way too long (93 characters)
papi @ 5.5.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 729 is way too long (127 characters)
scalapack @ 2.0.2formatting

Look for formatting issues in the source

tabulation on line 788, column 0
u-boot-bananapi-m2-ultra @ 2020.04formatting

Look for formatting issues in the source

line 639 is way too long (93 characters)
mingw-w64-x86_64-winpthreads @ 7.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 639 is way too long (93 characters)
p4est @ 2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 607 is way too long (111 characters)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1613 is way too long (137 characters)
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 337, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 338, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 339, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 340, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 341, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 342, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 343, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 344, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 345, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 346, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 347, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 348, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 349, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 350, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 351, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 352, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 353, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 354, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 355, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 366, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 367, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 379, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 380, column 0
openssl @ 1.1.1fformatting

Look for formatting issues in the source

tabulation on line 381, column 0
ncurses @ 6.2formatting

Look for formatting issues in the source

trailing white space on line 165
ncurses @ 6.2formatting

Look for formatting issues in the source

line 179 is way too long (94 characters)
arm-trusted-firmware-rk3328 @ 2.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
tumbler @ 0.2.8formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
pjproject-jami @ 2.10formatting

Look for formatting issues in the source

line 186 is way too long (103 characters)
u-boot-am335x-evm @ 2020.04formatting

Look for formatting issues in the source

line 639 is way too long (93 characters)
docker @ 19.03.11formatting

Look for formatting issues in the source

line 345 is way too long (95 characters)
docker @ 19.03.11formatting

Look for formatting issues in the source

line 381 is way too long (93 characters)
python2-fastlmm @ 0.2.21formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 133 is way too long (96 characters)
elixir @ 1.10.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 76 is way too long (99 characters)
guile-dbi @ 2.1.6formatting

Look for formatting issues in the source

line 1293 is way too long (94 characters)
ldc @ 1.10.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 367 is way too long (107 characters)
ruby-iruby @ 0.3formatting

Look for formatting issues in the source

line 477 is way too long (112 characters)
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

line 213 is way too long (106 characters)
u-boot-a20-olinuxino-lime @ 2020.04formatting

Look for formatting issues in the source

line 639 is way too long (93 characters)
powertabeditor @ 2.0.0-alpha10formatting

Look for formatting issues in the source

line 1329 is way too long (94 characters)
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1145 is way too long (98 characters)
gap @ 4.10.2formatting

Look for formatting issues in the source

trailing white space on line 1197
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 258, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 260, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 263, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 264, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 273, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 274, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 275, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 276, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 277, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 278, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 279, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 281, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 282, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 283, column 0
patchwork @ 2.1.5formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
tigervnc-server @ 1.10.1-1.920d9c4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 187, column 0
mingw-w64-i686-winpthreads @ 7.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 214 is way too long (102 characters)
sundials-openmpi @ 3.1.1formatting

Look for formatting issues in the source

tabulation on line 4750, column 0
efitools @ 1.9.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2081 is way too long (97 characters)
wine-staging @ 5.8formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 260 is way too long (92 characters)
help2man @ 1.47.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 630 is way too long (114 characters)
vim-full @ 8.2.0411formatting

Look for formatting issues in the source

line 197 is way too long (94 characters)
java-jbzip2 @ 0.9.1formatting

Look for formatting issues in the source

line 275 is way too long (92 characters)
abseil-cpp @ 20200225.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 478 is way too long (144 characters)
python-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1083 is way too long (94 characters)
fastboot @ 7.1.2_r36formatting

Look for formatting issues in the source

line 688 is way too long (105 characters)
geany @ 1.36formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python2-pygobject @ 3.34.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3323 is way too long (94 characters)
qtdatavis3d @ 5.14.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 107, 250
python-cryptography @ 2.9.2description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
qtcharts @ 5.14.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 41
xwallpaper @ 0.6.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 72
python2-cryptography @ 2.9.2description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
xftwidth @ 20170402description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 96, 234
kconfigwidgets @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
ibus-anthy @ 1.5.9inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-clf @ 0.5.7inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
kdelibs4support @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
python2-pytest-httpbin @ 0.2.3inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python-pytest-httpbin @ 0.2.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
python2-clf @ 0.5.7inputs-should-be-native

Identify inputs that should be native inputs

'python2-nose' should probably be a native input
java-eclipse-jetty-server @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
grantleetheme @ 20.04.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
khal @ 0.10.1formatting

Look for formatting issues in the source

line 180 is way too long (113 characters)
serf @ 1.3.9formatting

Look for formatting issues in the source

line 1660 is way too long (92 characters)
qtremoteobjects @ 5.14.2formatting

Look for formatting issues in the source

line 1484 is way too long (94 characters)
kcmutils @ 5.70.0formatting

Look for formatting issues in the source

line 2237 is way too long (113 characters)
python-pyqt @ 5.14.2formatting

Look for formatting issues in the source

line 1999 is way too long (105 characters)
librime @ 1.5.3formatting

Look for formatting issues in the source

line 328 is way too long (93 characters)
extra-cmake-modules @ 5.70.0formatting

Look for formatting issues in the source

line 110 is way too long (91 characters)
qtsensors @ 5.14.2formatting

Look for formatting issues in the source

line 875 is way too long (97 characters)
kpackage @ 5.70.0formatting

Look for formatting issues in the source

line 1926 is way too long (106 characters)
qtserialport @ 5.14.2formatting

Look for formatting issues in the source

line 1026 is way too long (115 characters)
kdbusaddons @ 5.70.0formatting

Look for formatting issues in the source

line 645 is way too long (107 characters)
kget @ 20.04.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
qtbase @ 5.14.2formatting

Look for formatting issues in the source

line 440 is way too long (96 characters)
qtbase @ 5.14.2formatting

Look for formatting issues in the source

line 564 is way too long (97 characters)
qtbase @ 5.14.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 918 is way too long (96 characters)
kimageformats @ 5.70.0formatting

Look for formatting issues in the source

line 1789 is way too long (103 characters)
krona-tools @ 2.7formatting

Look for formatting issues in the source

trailing white space on line 1007
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1565, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1566, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1568, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1569, column 0
kio @ 5.70.1formatting

Look for formatting issues in the source

line 2765 is way too long (113 characters)
varnish @ 6.4.0formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

'flex' should probably be a native input
hurd @ 0.9-1.91a5167derivation

Report failure to compile a package to a derivation

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

Report failure to compile a package to a derivation

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

Report failure to compile a package to a derivation

failed to create i686-gnu derivation: could not find bootstrap binary 'tar' for system 'i686-gnu'
openssh-sans-x @ 8.3p1patch-file-names

Validate file names and availability of patches

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
python2-rst.linker @ 1.11description

Validate package descriptions

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-jsonrpc-server @ 0.3.4inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-jsonrpc-server @ 0.3.4inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-doc8 @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
pelican @ 4.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-virtualenv @ 20.0.10inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python2-virtualenv @ 20.0.10inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python2-setuptools' should probably not be an input at all
python2-pybugz @ 0.6.11patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

python-robotframework-honor-source-date-epoch.patch: file name is too long
python-wtforms @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2984 is way too long (100 characters)
scons @ 3.0.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4721 is way too long (105 characters)
python-numpy @ 1.17.3formatting

Look for formatting issues in the source

line 4156 is way too long (152 characters)
python-tornado @ 5.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2984 is way too long (100 characters)
python2-pyqt @ 5.14.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
calibre @ 4.18.0formatting

Look for formatting issues in the source

line 239 is way too long (93 characters)
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
sqlcipher @ 3.4.2source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 587 is way too long (99 characters)
python2-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
python-discogs-client @ 2.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
sorcer @ 1.1.3source-unstable-tarball

Check for autogenerated tarballs

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

Validate file names and availability of patches

file names of patches should start with the package name
beets-bandcamp @ 0.1.3formatting

Look for formatting issues in the source

line 3049 is way too long (149 characters)
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4661, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4662, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4663, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4664, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4666, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4673, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4674, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4675, column 0
fmit @ 1.2.13formatting

Look for formatting issues in the source

tabulation on line 4676, column 0
drumstick @ 1.1.3formatting

Look for formatting issues in the source

line 2124 is way too long (91 characters)
rosegarden @ 20.06formatting

Look for formatting issues in the source

line 4187 is way too long (94 characters)
rosegarden @ 20.06formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
i3-wm @ 4.18.1description

Validate package descriptions

description should start with an upper-case letter or digit
awesome @ 4.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
sbcl-stumpwm-kbd-layouts @ 0.0.1-2.920f8fcsource-file-name

Validate file names of sources

the source file name should contain the package name
stumpish @ 0.0.1-2.920f8fcsource-file-name

Validate file names of sources

the source file name should contain the package name
sbcl-stumpwm-stumptray @ 0.0.1-2.920f8fcsource-file-name

Validate file names of sources

the source file name should contain the package name
sbcl-stumpwm-globalwindows @ 0.0.1-2.920f8fcsource-file-name

Validate file names of sources

the source file name should contain the package name
sbcl-stumpwm-swm-gaps @ 0.0.1-2.920f8fcsource-file-name

Validate file names of sources

the source file name should contain the package name
sbcl-stumpwm-net @ 0.0.1-2.920f8fcsource-file-name

Validate file names of sources

the source file name should contain the package name
sbcl-stumpwm-ttf-fonts @ 0.0.1-2.920f8fcsource-file-name

Validate file names of sources

the source file name should contain the package name
sbcl-stumpwm-wifi @ 0.0.1-2.920f8fcsource-file-name

Validate file names of sources

the source file name should contain the package name
sbcl-stumpwm-pass @ 0.0.1-2.920f8fcsource-file-name

Validate file names of sources

the source file name should contain the package name
quickswitch-i3 @ 2.2-1.ed692b1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
stumpwm-with-slynk @ 19.11formatting

Look for formatting issues in the source

line 1648 is way too long (94 characters)
asciidoc @ 8.6.10source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
grfcodec @ 6.0.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 100
texlive-latex-pgf @ 51265formatting

Look for formatting issues in the source

line 6468 is way too long (98 characters)
maven-model @ 3.6.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 177 is way too long (99 characters)
maven-embedder @ 3.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 298 is way too long (102 characters)
maven-core @ 3.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1216 is way too long (118 characters)
maven-wagon-http @ 3.1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 634 is way too long (129 characters)
maven-shared-utils @ 3.2.1formatting

Look for formatting issues in the source

line 358 is way too long (109 characters)
php @ 7.4.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 285 is way too long (92 characters)
r-dplyr @ 1.0.0description

Validate package descriptions

description should start with an upper-case letter or digit
tuxmath @ 2.0.3description

Validate package descriptions

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

Look for formatting issues in the source

line 579 is way too long (99 characters)
gcompris @ 17.05formatting

Look for formatting issues in the source

line 134 is way too long (96 characters)
childsplay @ 3.4formatting

Look for formatting issues in the source

line 488 is way too long (92 characters)
mesa-headers @ 20.0.7patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 304 is way too long (120 characters)
r-biosigner @ 1.16.0description

Validate package descriptions

use @code or similar ornament instead of quotes
r-yapsa @ 1.14.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-rgadem @ 2.36.0description

Validate package descriptions

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

Look for formatting issues in the source

line 2140 is way too long (92 characters)
r-lumi @ 2.40.0formatting

Look for formatting issues in the source

line 3338 is way too long (95 characters)
r-monocle @ 2.16.0formatting

Look for formatting issues in the source

line 2918 is way too long (101 characters)
ecasound @ 2.9.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471
wpa-supplicant-gui @ 2.9description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
debops @ 1.1.0patch-file-names

Validate file names and availability of patches

debops-constants-for-external-program-names.patch: file name is too long
perl-test-file-contents @ 0.23description

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

line 106 is way too long (92 characters)
busybox @ 1.31.1formatting

Look for formatting issues in the source

trailing white space on line 92
busybox @ 1.31.1formatting

Look for formatting issues in the source

line 94 is way too long (92 characters)
f2fs-fsck-static @ 1.13.0description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
ecryptfs-utils @ 111description

Validate package descriptions

description should start with an upper-case letter or digit
ddate @ 0.2.2source-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
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 5250 is way too long (98 characters)
crda @ 3.18formatting

Look for formatting issues in the source

line 3466 is way too long (100 characters)
python-requests @ 2.20.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-urllib3@1.24.3 and python-urllib3@1.25.9 collide
python2-pytest-httpbin @ 0.2.3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and /gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
python-hacking @ 1.1.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-pep8@1.7.0 and python-pep8@1.5.7 collide
python2-hacking @ 1.1.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python2-pyflakes@2.1.1 and python2-pyflakes@1.2.3 collide
python2-pytest-django @ 3.1.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and /gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
python-q @ 2.6description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-pywinrm @ 0.4.1description

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-legacy-api-wrap @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-legacy-api-wrap @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python-jaraco-packaging @ 6.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-jaraco-packaging @ 6.1inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-jaraco-packaging @ 6.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-pytest-black @ 0.3.8inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-legacy-api-wrap @ 1.2inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-ipython-cluster-helper @ 0.6.4inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python2-ipython-cluster-helper @ 0.6.4inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python2-setuptools' should probably not be an input at all
python-jaraco-packaging @ 6.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

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

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python2-pep8 @ 1.7.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python-ipython-documentation @ 7.9.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ghc-hxt-unicode @ 9.0.2.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-aeson-qq @ 0.8.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
ghc-system-filepath @ 0.4.14formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 14356 is way too long (93 characters)
ghc-hxt-unicode @ 9.0.2.4formatting

Look for formatting issues in the source

line 1423 is way too long (91 characters)
go-github-com-gorilla-context @ 0.0.0-0.08b5f42formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 12721 is way too long (92 characters)
go-github-com-multiformats-go-multiaddr-net @ 1.6.3-0.1cb9a0eformatting

Look for formatting issues in the source

line 2804 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 2805 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 2701 is way too long (95 characters)
go-github-com-mattn-go-shellwords @ 1.0.5-1.2444a32formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
go-github-com-davecgh-go-spew @ 1.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2606 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 2662 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 2665 is way too long (93 characters)
openmw @ 0.46.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
gexiv2 @ 0.12.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libdazzle @ 3.34.1inputs-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
conda @ 4.3.16formatting

Look for formatting issues in the source

line 831 is way too long (94 characters)
mate-applets @ 1.24.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 917
mate-polkit @ 1.24.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
mate-menus @ 1.24.0formatting

Look for formatting issues in the source

line 526 is way too long (91 characters)
mate-panel @ 1.24.0formatting

Look for formatting issues in the source

line 689 is way too long (92 characters)
atril @ 1.22.0formatting

Look for formatting issues in the source

line 764 is way too long (92 characters)
python-botocore @ 1.15.26inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python2-botocore @ 1.15.26inputs-should-be-native

Identify inputs that should be native inputs

'python2-docutils' should probably be a native input
python2-configobj @ 5.0.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
quaternion @ 0.0.9.4einputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
gnome-shell-extension-dash-to-panel @ 37inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
template-glib @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gx @ 0.14.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 144 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 80 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 81 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 84 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 (93 characters)
go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 197 is way too long (91 characters)
restinio @ 0.6.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2812 is way too long (92 characters)
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-extutils-pkgconfig @ 1.16inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
hplip-minimal @ 3.20.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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
guile2.2-mailutils @ 3.9inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
mailutils @ 3.9inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
sendmail @ 8.15.2inputs-should-be-native

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
bind @ 9.16.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 253
perl-specio @ 0.38description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 185, 314
rapicorn @ 16.0.0inputs-should-be-native

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

file names of patches should start with the package name
icedove @ 68.9.0formatting

Look for formatting issues in the source

line 1175 is way too long (98 characters)
icedove @ 68.9.0formatting

Look for formatting issues in the source

line 1243 is way too long (93 characters)
icedove @ 68.9.0formatting

Look for formatting issues in the source

line 1336 is way too long (105 characters)
icedove @ 68.9.0formatting

Look for formatting issues in the source

line 1338 is way too long (102 characters)
cl-reexport @ 0.1-1.312f366description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
sbcl-graph-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
cl-graph @ 0.0.0-0.78bf9ecpatch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 6034 is way too long (91 characters)
oil @ 0.8.pre6formatting

Look for formatting issues in the source

line 805 is way too long (95 characters)
qucs @ 0.0.19-0.b4f27d9inputs-should-be-native

Identify inputs that should be native inputs

'libtool' should probably be a native input
lepton-eda @ 1.9.9-20191003inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'm4' should probably be a native input
librecad @ 2.1.3source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1710 is way too long (104 characters)
meshlab @ 2020.06formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
diffoscope @ 148formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
espeak-ng @ 1.50description

Validate package descriptions

description should start with an upper-case letter or digit
guile3.0-ncurses @ 3.0description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 157
python-psycopg2 @ 2.8.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
guile-wiredtiger @ 0.7.0description

Validate package descriptions

use @code or similar ornament instead of quotes
libjxr @ 1.1description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
guile3.0-ncurses-with-gpm @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
perl-class-load @ 0.25description

Validate package descriptions

use @code or similar ornament instead of quotes
fakeroot @ 1.24description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 114, 240
python2-psycopg2 @ 2.8.4description

Validate package descriptions

description should start with an upper-case letter or digit
perl-devel-globaldestruction @ 0.14description

Validate package descriptions

use @code or similar ornament instead of quotes
mdadm-static @ 4.1description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-ncurses @ 3.0description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libchamplain @ 0.12.16inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
libreoffice @ 6.4.4.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
eolie @ 0.9.98.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
yelp-tools @ 3.32.2inputs-should-be-native

Identify inputs that should be native inputs

'itstool' 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
lollypop @ 1.2.32inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
gjs @ 1.58.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
libpeas @ 1.24.1inputs-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
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-security @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
procenv @ 0.51source-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-jmx @ 9.4.6source-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-eclipse-jetty-xml @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
libsignal-protocol-c @ 2.3.2source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
gcc-objc++ @ 7.5.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

audiofile-division-by-zero-BlockCodec-runPull.patch: file name is too long
guile3.0-readline @ 3.0.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libgccjit @ 9.3.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
util-linux-with-udev @ 2.35.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
http-parser @ 2.9.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile-next @ 3.0.2patch-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
guile2.2-rsvg @ 2.18.1-0.05c6a2fpatch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
perl-base @ 5.30.2patch-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
coreutils-minimal @ 8.32patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
libchop @ 0.5.2patch-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
perl-parent @ 5.30.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
glibc-hurd-headers @ 2.31patch-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
libiberty @ 7.5.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 4258 is way too long (110 characters)
linux-pam @ 1.3.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
netpbm @ 10.78.3formatting

Look for formatting issues in the source

line 86 is way too long (127 characters)
wireless-tools @ 30.pre9formatting

Look for formatting issues in the source

line 3359 is way too long (104 characters)
mariadb @ 10.1.45formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7049 is way too long (103 characters)
libosinfo @ 1.7.1formatting

Look for formatting issues in the source

line 395 is way too long (106 characters)
vorbis-tools @ 1.4.0formatting

Look for formatting issues in the source

trailing white space on line 323
gnome-keyring @ 3.34.0formatting

Look for formatting issues in the source

line 1638 is way too long (91 characters)
dejagnu @ 1.6.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2743 is way too long (94 characters)
glade @ 3.36.0formatting

Look for formatting issues in the source

line 2182 is way too long (91 characters)
texlive-amsfonts @ 51265formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1140 is way too long (91 characters)
glibc @ 2.31formatting

Look for formatting issues in the source

line 807 is way too long (98 characters)
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 746, column 0
libsoup @ 2.70.0formatting

Look for formatting issues in the source

line 3757 is way too long (128 characters)
libsoup @ 2.70.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 489 is way too long (95 characters)
util-linux @ 2.35.1formatting

Look for formatting issues in the source

line 1363 is way too long (91 characters)
at-spi2-core @ 2.34.0formatting

Look for formatting issues in the source

line 590 is way too long (97 characters)
texlive-latex-base @ 51265formatting

Look for formatting issues in the source

tabulation on line 2412, column 22
icecat @ 68.9.0-guix0-preview1formatting

Look for formatting issues in the source

line 868 is way too long (102 characters)
icecat @ 68.9.0-guix0-preview1formatting

Look for formatting issues in the source

trailing white space on line 871
icecat @ 68.9.0-guix0-preview1formatting

Look for formatting issues in the source

trailing white space on line 877
icecat @ 68.9.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 961 is way too long (139 characters)
icecat @ 68.9.0-guix0-preview1formatting

Look for formatting issues in the source

line 966 is way too long (95 characters)
icecat @ 68.9.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1010 is way too long (94 characters)
icecat @ 68.9.0-guix0-preview1formatting

Look for formatting issues in the source

line 1012 is way too long (95 characters)
icecat @ 68.9.0-guix0-preview1formatting

Look for formatting issues in the source

line 1025 is way too long (98 characters)
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 9299 is way too long (97 characters)
qemu @ 5.0.0formatting

Look for formatting issues in the source

line 131 is way too long (97 characters)
xen @ 4.13.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 551 is way too long (107 characters)
audacity @ 2.3.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
opencv @ 3.4.3formatting

Look for formatting issues in the source

line 283 is way too long (132 characters)
zita-resampler @ 1.3.0formatting

Look for formatting issues in the source

line 3246 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)
minizip @ 1.2.11formatting

Look for formatting issues in the source

line 153 is way too long (115 characters)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 241, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 242, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 243, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 244, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 245, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 246, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 247, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 248, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 249, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 252, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 253, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 255, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 256, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 257, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 258, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 259, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 261, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 262, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 263, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 264, column 0
zathura-djvu @ 0.2.9formatting

Look for formatting issues in the source

line 471 is way too long (93 characters)
guile @ 2.0.14formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 191 is way too long (93 characters)
python-plastid @ 0.4.8description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
clipper @ 1.2.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'swig' should probably be a native input
blasr-libcpp @ 5.3.3formatting

Look for formatting issues in the source

line 575 is way too long (95 characters)
discrover @ 1.6.0formatting

Look for formatting issues in the source

line 2758 is way too long (91 characters)
go-github.com-smartystreets-goconvey @ 1.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 33
python2-nose2 @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest-cov' should probably be a native input
python-nose2 @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python2-nose2 @ 0.9.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and /gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
python2-pytest @ 4.6.9profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and /gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
python2-pytest-cov @ 2.8.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and /gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
python2-unittest2 @ 1.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
go-github.com-smartystreets-goconvey @ 1.6.3formatting

Look for formatting issues in the source

line 515 is way too long (91 characters)
emacs-pyvenv @ 1.21description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-flx @ 0.6.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 220
emacs-dhall-mode @ 0.1.3-0.ef4d33ddescription

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 178
emacs-cnfonts @ 0.9.1description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-vcsh @ 0.4.4description

Validate package descriptions

use @code or similar ornament instead of quotes
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-gtk-look @ 29formatting

Look for formatting issues in the source

line 18009 is way too long (94 characters)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10951, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10952, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10955, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10956, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10968, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10969, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10970, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10971, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10972, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10973, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10974, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10975, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10976, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10977, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10978, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10979, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10980, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10981, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10982, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10983, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 10984, column 0
emacs-exwm @ 0.24formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4991 is way too long (94 characters)
mkvtoolnix @ 37.0.0formatting

Look for formatting issues in the source

line 427 is way too long (96 characters)
guile2.2-readline @ 2.2.7patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 381 is way too long (94 characters)
guile-for-guile-emacs @ 2.1.2-1.15ca784formatting

Look for formatting issues in the source

line 491 is way too long (96 characters)
guile-for-guile-emacs @ 2.1.2-1.15ca784formatting

Look for formatting issues in the source

trailing white space on line 495
guile-readline @ 3.0.2formatting

Look for formatting issues in the source

line 381 is way too long (94 characters)
linux-libre-arm-generic @ 4.14.185patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 756 is way too long (117 characters)
linux-libre @ 4.14.185formatting

Look for formatting issues in the source

line 756 is way too long (117 characters)
linux-libre @ 4.4.228formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 756 is way too long (117 characters)
linux-libre @ 4.9.228formatting

Look for formatting issues in the source

line 756 is way too long (117 characters)
bison @ 3.6.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'm4' should probably be a native input
vmpk @ 0.7.2formatting

Look for formatting issues in the source

line 2169 is way too long (91 characters)
r-tidyr @ 1.1.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

line 7144 is way too long (92 characters)
r-brms @ 2.13.0description

Validate package descriptions

use @code or similar ornament instead of quotes
r-brms @ 2.13.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 109, 532, 653, 784
r-xyz @ 0.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 242
r-arm @ 1.11-1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 46, 60
r-rstan @ 2.19.3description

Validate package descriptions

use @code or similar ornament instead of quotes
r-diagram @ 1.6.4description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
python-rpy2 @ 3.0.4-1.19868a8description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-oai @ 0.3.0description

Validate package descriptions

use @code or similar ornament instead of quotes
r-circular @ 0.4-93description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 97, 120
r-systemfonts @ 0.2.3description

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-wmtsa @ 2.0-3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 105, 128
r-r2glmm @ 0.1.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 173, 176
r-topicmodels @ 0.2-11description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 151
r-shiny @ 1.4.0.2formatting

Look for formatting issues in the source

line 1108 is way too long (92 characters)
r-flexdashboard @ 0.5.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 15258 is way too long (100 characters)
r-haplo-stats @ 1.7.9formatting

Look for formatting issues in the source

line 13984 is way too long (103 characters)
r-squarem @ 2020.3formatting

Look for formatting issues in the source

line 2993 is way too long (91 characters)
r-abps @ 0.3formatting

Look for formatting issues in the source

line 8091 is way too long (93 characters)
r-gamlss-dist @ 5.1-6formatting

Look for formatting issues in the source

line 12612 is way too long (91 characters)
r-colourpicker @ 1.0formatting

Look for formatting issues in the source

line 12718 is way too long (94 characters)
rust-rustc-hash @ 1.1.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
rust-dav1d-sys @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
rust-colored @ 1.9.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 27275 is way too long (114 characters)
rust-gimli @ 0.20.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1675 is way too long (111 characters)
rust-ctor @ 0.1.13formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python-pyfit-sne @ 1.0.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-biomart @ 2.44.1description

Validate package descriptions

description should start with an upper-case letter or digit
samblaster @ 0.1.24description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
imp @ 2.6.2inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
variant-tools @ 3.1.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-cython' should probably be a native input
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
python2-pbcore @ 1.2.10inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-cython' should probably be a native input
rseqc @ 3.0.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-nose' should probably be a native input
miniasm @ 0.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
r-rhdf5lib @ 1.10.0formatting

Look for formatting issues in the source

line 10879 is way too long (102 characters)
r-rhdf5lib @ 1.10.0formatting

Look for formatting issues in the source

line 10880 is way too long (104 characters)
salmon @ 0.13.1formatting

Look for formatting issues in the source

line 12235 is way too long (99 characters)
dropseq-tools @ 1.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4003 is way too long (117 characters)
java-picard @ 2.10.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3856 is way too long (104 characters)
freebayes @ 1.0.2-1.3ce827dformatting

Look for formatting issues in the source

tabulation on line 15692, column 28
icu4c-build-root @ 66.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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
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
python2-pytest-xdist @ 1.25.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and /gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
python2-pytest-catchlog @ 1.2.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and /gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
python2-pytest-capturelog @ 0.7profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and /gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
python2-pytest-cache @ 1.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and /gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
python2-pytest-warnings @ 0.2.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and /gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
python2-pytest-subtesthack @ 0.1.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and /gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
python2-pytest-mock @ 1.10.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and /gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
python2-pyfakefs @ 3.7.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
mrrescue @ 1.02edescription

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 76
sky @ 1.2description

Validate package descriptions

use @code or similar ornament instead of quotes
fifengine @ 0.4.2inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
crawl-tiles @ 0.25.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
drascula @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8621 is way too long (205 characters)
einstein @ 2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8820 is way too long (100 characters)
queen-fr @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 7505, column 18
btanks @ 0.9.8083formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8521 is way too long (93 characters)
freeorion @ 0.4.9formatting

Look for formatting issues in the source

line 8905 is way too long (92 characters)
lure-de @ 1.1formatting

Look for formatting issues in the source

line 8521 is way too long (93 characters)
warzone2100 @ 3.2.3formatting

Look for formatting issues in the source

line 4194 is way too long (107 characters)
sky @ 1.2formatting

Look for formatting issues in the source

line 8724 is way too long (118 characters)
lure @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6140, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

tabulation on line 6141, column 0
nudoku @ 1.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8521 is way too long (93 characters)
queen-it @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8621 is way too long (205 characters)
python2-editor @ 1.0.4description

Validate package descriptions

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

Validate package descriptions

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

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
python-pyaml @ 18.11.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

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
ptpython2 @ 0.34description

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-gevent @ 20.5.0description

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
python-argcomplete @ 1.11.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-eliot @ 1.12.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 153
python2-apispec @ 0.25.3description

Validate package descriptions

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

Validate package descriptions

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

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

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
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
gst-transcoder @ 1.12.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' 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
python2-xopen @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-setuptools-scm' should probably be a native input
python2-pkgconfig @ 1.3.1inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
python-iocapture @ 0.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-iocapture @ 0.1.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-pifpaf @ 2.4.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-docusign-esign @ 3.1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-setuptools-scm-git-archive @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-m2r @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-pytest-check-links @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-pytest-check-links @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-rst2ansi @ 0.1.5inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-xopen @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-argh @ 0.26.2-1.dcd3253inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-argh @ 0.26.2-1.dcd3253inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-argh @ 0.26.2-1.dcd3253inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'nasm' should probably be a native input
python2-sure @ 1.4.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-mock' should probably be a native input
python2-setuptools-scm-git-archive @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-setuptools-scm' should probably be a native input
python2-m2r @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-docutils' should probably be a native input
python-eliot @ 1.12.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
java-picocli @ 4.3.2source-file-name

Validate file names of sources

the source file name should contain the package name
java-lmax-disruptor @ 3.3.7source-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-ops4j-pax-exam-core @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-spi @ 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-native-access-platform @ 4.5.1source-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-stax2-api @ 4.0.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-logback-classic @ 1.2.3source-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-jsch-agentproxy-usocket-nc @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-datanucleus-javax-persistence @ 2.2.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-ops4j-base-monitors @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-modules-base-jaxb @ 2.9.4source-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-javax-inject @ tck-1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-core @ 2.9.4source-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-logback-core @ 1.2.3source-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-aqute-bnd-annotation @ 3.5.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-assertj @ 3.8.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-io @ 1.5.0source-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-fasterxml-jackson-modules-base-mrbean @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-native-access @ 4.5.1source-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-jsch-agentproxy-sshagent @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-dataformat-yaml @ 2.9.4source-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-jline @ 1.0source-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-jboss-interceptors-api-spec @ 1.2source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-base-util @ 1.5.0source-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-mail @ 1.6.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-woodstox-core @ 5.0.3source-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-jsch-agentproxy-jsch @ 0.0.8source-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-joda-time @ 2.9.9source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
antlr3 @ 3.5.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-stringtemplate@3.2.1 and java-stringtemplate@4.0.6 collide
antlr3 @ 3.3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs antlr3@3.1 and antlr3@3.3 collide
python2-jedi @ 0.17.0patch-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
python2-packaging @ 20.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

python2-larch-coverage-4.0a6-compatibility.patch: file name is too long
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-apache-ivy @ 2.4.0patch-file-names

Validate file names and availability of patches

java-apache-ivy-port-to-latest-bouncycastle.patch: file name is too long
java-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-openjfx-media @ 8.202patch-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
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-openjfx-graphics @ 8.202patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

tabulation on line 2264, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2265, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2266, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2267, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2268, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2269, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2270, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2271, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2272, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2273, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2274, column 0
java-testng @ 6.14.3formatting

Look for formatting issues in the source

line 9294 is way too long (91 characters)
java-commons-jxpath @ 1.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8816 is way too long (98 characters)
gaupol @ 1.7formatting

Look for formatting issues in the source

line 3800 is way too long (95 characters)
java-jgit @ 4.2.0.201601211800-rformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 11528 is way too long (102 characters)
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8488 is way too long (93 characters)
java-commons-httpclient @ 3.1formatting

Look for formatting issues in the source

line 10850 is way too long (91 characters)
java-hawtjni @ 1.15formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 6560 is way too long (98 characters)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 11372 is way too long (95 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4127 is way too long (107 characters)
java-native-access @ 4.5.1formatting

Look for formatting issues in the source

line 10987 is way too long (91 characters)
java-jnacl @ 0.1.0-2.094e819formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8704 is way too long (104 characters)
icedtea @ 3.7.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8393 is way too long (100 characters)
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6501, column 20
icedtea @ 2.6.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10116 is way too long (122 characters)
java-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

line 3584 is way too long (112 characters)
java-openjfx-base @ 8.202formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2548 is way too long (99 characters)
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2306, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2307, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2308, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2309, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2310, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2311, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2312, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2313, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2314, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2319, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2320, column 0
java-joda-time @ 2.9.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4247 is way too long (98 characters)
linux-libre @ 5.4.48derivation

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

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
linux-libre-arm-generic @ 5.4.48patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
freefall @ 5.4.48patch-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.48patch-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.129patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm64-generic @ 5.7.5patch-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.48patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm64-generic @ 5.4.48patch-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.48formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 756 is way too long (117 characters)