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
maven-shared-utils @ 3.2.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@16 and apache-parent-pom@18 collide
java-sonatype-aether-impl @ 1.7profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-forge-parent-pom@6 and java-sonatype-forge-parent-pom@10 collide
maven-surefire-plugin @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide
maven-surefire-common @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide
maven-shared-utils @ 3.1.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@16 and apache-parent-pom@18 collide
maven-shared-utils @ 3.0.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-shared-io @ 3.0.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@39 collide
maven-shared-incremental @ 1.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-settings-builder @ 3.6.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide
maven-settings-builder @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide
maven-resources-plugin @ 3.1.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide
maven-resolver-provider @ 3.6.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-plugin-api @ 3.6.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide
maven-plugin-api @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide
maven-model-builder @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide
maven-model @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide
maven-jar-plugin @ 3.2.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@39 and apache-commons-parent-pom@41 collide
maven-install-plugin @ 3.0.0-M1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide
maven-filtering @ 3.1.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@39 collide
maven-file-management @ 3.0.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@39 collide
maven-enforcer-rules @ 3.0.0-M3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide
maven-enforcer-plugin @ 3.0.0-M3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@18 collide
maven-enforcer-api @ 3.0.0-M3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-embedder @ 3.6.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide
maven-dependency-tree @ 3.0.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-compiler-plugin @ 3.8.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-compat @ 3.6.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide
maven-compat @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide
maven-common-artifact-filters @ 3.1.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
maven-artifact-transfer @ 0.12.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide
maven-artifact @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide
maven-archiver @ 3.5.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@39 and apache-commons-parent-pom@41 collide
maven-aether-provider @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide
java-surefire-extensions-api @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide
java-surefire-common-junit4 @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide
java-surefire-common-junit3 @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide
java-surefire-common-java5 @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@16 and apache-parent-pom@21 collide
java-surefire-booter @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide
java-surefire-api @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide
zn-poly @ 0.9.2description

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 121, 206
sh-z @ 1.11description

Validate package descriptions

use @code or similar ornament instead of quotes
robin-map @ 0.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 281
rcm @ 1.3.4description

Validate package descriptions

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

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
perl-test-object @ 0.08description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 185, 314
perl-search-xapian @ 1.2.25.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 47
kget @ 20.04.1description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
go-github.com-smartystreets-goconvey @ 1.6.3description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ghc-inline-c @ 0.7.0.1description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 158
ghc-hsyaml @ 0.1.2.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-gtk2hs-buildtools @ 0.13.5.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ghc-aeson-qq @ 0.8.2description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 236
spice-gtk @ 0.37inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' 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-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python2-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-nose2 @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest-cov' 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-pytest-django @ 3.10.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-nose2 @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' 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
presentty @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
perl-extutils-pkgconfig @ 1.16inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' 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
mig @ 1.8inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
lxqt @ 0.15.0inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' 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.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' 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
bison @ 3.6.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'm4' should probably be a native input
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
aseba @ 1.6.0-0.3b35de8inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
rdmd @ 2.077.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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'
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'
tigervnc-server @ 1.11.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
pandoc @ 2.7.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
maven-enforcer-rules @ 3.0.0-M3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-enforcer-plugin @ 3.0.0-M3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
maven-aether-provider @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libmhash @ 0.9.9.9patch-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
kodi-wayland @ 18.8patch-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
idutils @ 4.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
icu4c-build-root @ 66.1patch-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
guile-static-stripped @ 3.0.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
grub-efi @ 2.04patch-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
emacs-erlang @ 23.2.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
sdl-pango @ 0.1.2patch-headers

Validate patch headers

sdl-pango-header-guard.patch: patch lacks comment and upstream status
python2-unittest2 @ 1.1.0patch-headers

Validate patch headers

python-unittest2-remove-argparse.patch: patch lacks comment and upstream status
python-unittest2 @ 1.1.0patch-headers

Validate patch headers

python-unittest2-remove-argparse.patch: patch lacks comment and upstream status
mono @ 4.4.1.0patch-headers

Validate patch headers

mono-mdoc-timestamping.patch: patch lacks comment and upstream status
mkbootimg @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
mkbootimg @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
mkbootimg @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
mkbootimg @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
libmhash @ 0.9.9.9patch-headers

Validate patch headers

libmhash-hmac-fix-uaf.patch: patch lacks comment and upstream status
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
cyrus-sasl @ 2.1.27patch-headers

Validate patch headers

cyrus-sasl-ac-try-run-fix.patch: patch lacks comment and upstream status
apr @ 1.6.5patch-headers

Validate patch headers

apr-skip-getservbyname-test.patch: patch lacks comment and upstream status
android-libziparchive @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
android-libziparchive @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
android-libziparchive @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
android-libziparchive @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
android-libutils @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
android-libutils @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
android-libutils @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
android-libutils @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
android-libsparse @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
android-libsparse @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
android-libsparse @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
android-libsparse @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
android-liblog @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
android-liblog @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
android-liblog @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
android-liblog @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
android-libcutils @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
android-libcutils @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
android-libcutils @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
android-libcutils @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
adb @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
adb @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
adb @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
adb @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
zeitgeist @ 1.0.3formatting

Look for formatting issues in the source

tabulation on line 751, column 18
zeitgeist @ 1.0.3formatting

Look for formatting issues in the source

tabulation on line 754, column 18
xfce4-clipman-plugin @ 1.6.1formatting

Look for formatting issues in the source

line 499 is way too long (91 characters)
xf86-video-intel @ 2.99.917-17.ad5540fformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 109 is way too long (95 characters)
tumbler @ 4.16.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
tigervnc-server @ 1.11.0formatting

Look for formatting issues in the source

line 178 is way too long (102 characters)
tigervnc-server @ 1.11.0formatting

Look for formatting issues in the source

line 181 is way too long (102 characters)
tigervnc-server @ 1.11.0formatting

Look for formatting issues in the source

tabulation on line 190, column 0
shogun @ 6.1.3formatting

Look for formatting issues in the source

line 521 is way too long (91 characters)
sdsl-lite @ 2.1.1formatting

Look for formatting issues in the source

line 237 is way too long (145 characters)
sdl-mixer @ 1.2.12formatting

Look for formatting issues in the source

line 260 is way too long (92 characters)
sdl-image @ 1.2.12formatting

Look for formatting issues in the source

line 223 is way too long (91 characters)
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

line 213 is way too long (106 characters)
raspi-arm64-chainloader @ 0.1formatting

Look for formatting issues in the source

line 211 is way too long (139 characters)
raspi-arm64-chainloader @ 0.1formatting

Look for formatting issues in the source

line 224 is way too long (97 characters)
raspi-arm-chainloader @ 0.1formatting

Look for formatting issues in the source

line 131 is way too long (129 characters)
raspi-arm-chainloader @ 0.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 42
presentty @ 0.2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 106 is way too long (92 characters)
papi @ 5.5.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
openfoam @ 4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 146 is way too long (91 characters)
omnitux @ 1.2.1formatting

Look for formatting issues in the source

line 581 is way too long (99 characters)
netpbm @ 10.78.3formatting

Look for formatting issues in the source

line 86 is way too long (127 characters)
ncurses @ 6.2formatting

Look for formatting issues in the source

trailing white space on line 165
ncurses @ 6.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 152 is way too long (92 characters)
mrustc @ 0.9formatting

Look for formatting issues in the source

line 178 is way too long (123 characters)
maven-wagon-http @ 3.3.4formatting

Look for formatting issues in the source

line 901 is way too long (105 characters)
maven-wagon-http @ 3.3.4formatting

Look for formatting issues in the source

line 906 is way too long (138 characters)
maven-wagon-http @ 3.3.4formatting

Look for formatting issues in the source

line 907 is way too long (129 characters)
maven-wagon-file @ 3.3.4formatting

Look for formatting issues in the source

line 738 is way too long (125 characters)
maven-surefire-plugin @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3607 is way too long (113 characters)
maven-surefire-plugin @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3608 is way too long (111 characters)
maven-shared-utils @ 3.2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1638 is way too long (110 characters)
lxqt-session @ 0.15.0formatting

Look for formatting issues in the source

line 860 is way too long (92 characters)
lxqt-session @ 0.15.0formatting

Look for formatting issues in the source

line 867 is way too long (100 characters)
lxqt-session @ 0.15.0formatting

Look for formatting issues in the source

line 885 is way too long (98 characters)
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1360, column 0
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1361, column 0
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1362, column 0
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1363, column 0
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1364, column 0
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1366, column 0
lxde-common @ 0.99.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libsigsegv @ 2.12formatting

Look for formatting issues in the source

line 48 is way too long (133 characters)
libextractor @ 1.10formatting

Look for formatting issues in the source

line 128 is way too long (140 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
ldc @ 1.10.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 130 is way too long (98 characters)
kget @ 20.04.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
julia @ 1.5.3formatting

Look for formatting issues in the source

line 301 is way too long (107 characters)
julia @ 1.5.3formatting

Look for formatting issues in the source

line 303 is way too long (106 characters)
js-mathjax @ 2.7.2formatting

Look for formatting issues in the source

line 150 is way too long (91 characters)
js-filesaver @ 1.3.8formatting

Look for formatting issues in the source

line 534 is way too long (99 characters)
jose @ 10formatting

Look for formatting issues in the source

line 37 is way too long (92 characters)
java-surefire-booter @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3271 is way too long (107 characters)
idris @ 1.3.3formatting

Look for formatting issues in the source

line 104 is way too long (93 characters)
icedtea @ 3.7.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1456 is way too long (100 characters)
hyperledger-iroha @ 1.1.1formatting

Look for formatting issues in the source

line 169 is way too long (105 characters)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 128 is way too long (92 characters)
guile-sdl @ 0.5.2formatting

Look for formatting issues in the source

line 607 is way too long (111 characters)
go-github.com-smartystreets-goconvey @ 1.6.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 95 is way too long (93 characters)
gmp @ 6.2.0formatting

Look for formatting issues in the source

line 82 is way too long (96 characters)
ghc-hxt-unicode @ 9.0.2.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 591 is way too long (91 characters)
gcompris @ 17.05formatting

Look for formatting issues in the source

line 135 is way too long (96 characters)
fdroidserver @ 1.1.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 700 is way too long (105 characters)
efitools @ 1.9.2formatting

Look for formatting issues in the source

line 215 is way too long (113 characters)
dejagnu @ 1.6.2formatting

Look for formatting issues in the source

line 60 is way too long (91 characters)
childsplay @ 3.4formatting

Look for formatting issues in the source

line 490 is way too long (92 characters)
android-safe-iop @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 277, column 20
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 385 is way too long (97 characters)
abc @ 0.0-1.5ae4b97formatting

Look for formatting issues in the source

line 95 is way too long (95 characters)
wine64-staging @ 5.13inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
wine-staging @ 5.13formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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-reno @ 2.7.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-oslo.log @ 3.36.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-mox3 @ 0.24.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
fcitx-qt5 @ 1.2.5inputs-should-be-native

Identify inputs that should be native inputs

'intltool' should probably be a native input
emacs-next @ 28.0.50-0.2ea3466patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mia @ 2.4.6inputs-should-be-native

Identify inputs that should be native inputs

'doxygen' should probably be a native input
mesa-opencl-icd @ 20.2.4patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 299 is way too long (120 characters)
mingw-w64-x86_64-winpthreads @ 8.0.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
ublock-origin-chromium @ 1.33.2description

Validate package descriptions

description should start with an upper-case letter or digit
jucipp @ 1.6.2description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
arpack-ng @ 3.3.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
hdf4-alt @ 4.2.14patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

tabulation on line 912, column 0
libjxr @ 1.1formatting

Look for formatting issues in the source

line 521 is way too long (95 characters)
clapack @ 3.2.1formatting

Look for formatting issues in the source

line 874 is way too long (91 characters)
libmediaart @ 1.9.4inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gnome-initial-setup @ 3.32.1formatting

Look for formatting issues in the source

line 1455 is way too long (91 characters)
connman @ 1.39description

Validate package descriptions

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

Look for formatting issues in the source

line 912 is way too long (96 characters)
gnome-shell-extension-gsconnect @ 33inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
gnome-shell-extension-dash-to-panel @ 38inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
libtomcrypt @ 1.18.2formatting

Look for formatting issues in the source

line 341 is way too long (100 characters)
texlive-latex-cyrillic @ 51265description

Validate package descriptions

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

Validate package descriptions

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
texlive-latex-pgf @ 51265formatting

Look for formatting issues in the source

line 6722 is way too long (98 characters)
texlive-latex-l3packages @ 51265formatting

Look for formatting issues in the source

line 3028 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
xftwidth @ 20170402description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 96, 234
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1780, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1781, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1783, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1784, column 0
font-canada1500 @ 1.101formatting

Look for formatting issues in the source

line 208 is way too long (91 characters)
rust-avif-serialize @ 0.6.5description

Validate package descriptions

use @code or similar ornament instead of quotes
tcsh @ 6.22.02patch-headers

Validate patch headers

tcsh-fix-autotest.patch: patch lacks comment and upstream status
catdoc @ 0.95description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 157
opencc @ 1.1.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
rust-actix-derive @ 0.5.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python2-cryptography @ 3.3.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-keyring @ 22.0.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
emacs-cmake-mode @ 3.19.2patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 751 is way too long (91 characters)
cfitsio @ 3.49description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 197
libsigrok @ 0.5.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 216 is way too long (92 characters)
perl-devel-globaldestruction @ 0.14description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
tensorflow @ 1.9.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1174 is way too long (92 characters)
minizip @ 1.2.11formatting

Look for formatting issues in the source

line 161 is way too long (115 characters)
r-minqa @ 1.2.4description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 45, 56
python-rpy2 @ 3.3.5formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 5733 is way too long (104 characters)
python-pytools @ 2020.4description

Validate package descriptions

use @code or similar ornament instead of quotes
mate-applets @ 1.24.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 917
libtool @ 2.4.6inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 606 is way too long (92 characters)
mate-panel @ 1.24.1formatting

Look for formatting issues in the source

line 671 is way too long (92 characters)
mate-menus @ 1.24.1formatting

Look for formatting issues in the source

line 511 is way too long (91 characters)
cockatrice @ 2.8.0inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
patchwork @ 3.0.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
glibc-bootstrap @ 0formatting

Look for formatting issues in the source

line 653 is way too long (100 characters)
gcc-bootstrap @ 0formatting

Look for formatting issues in the source

line 749 is way too long (100 characters)
ghc-unsafe @ 0.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-regex-tdfa @ 1.2.3.2description

Validate package descriptions

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

Look for formatting issues in the source

line 15284 is way too long (93 characters)
ghc-vector @ 0.12.0.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 13533 is way too long (92 characters)
ghc-system-filepath @ 0.4.14formatting

Look for formatting issues in the source

line 13020 is way too long (250 characters)
nsis-x86_64 @ 3.05description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
nsis-x86_64 @ 3.05patch-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
nsis-x86_64 @ 3.05patch-headers

Validate patch headers

nsis-env-passthru.patch: patch lacks comment and upstream status
nsis-i686 @ 3.05patch-headers

Validate patch headers

nsis-env-passthru.patch: patch lacks comment and upstream status
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 114 is way too long (97 characters)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 128 is way too long (114 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 114 is way too long (97 characters)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 128 is way too long (114 characters)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 324, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 326, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 329, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 330, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 339, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 340, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 341, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 342, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 343, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 344, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 345, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 347, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 348, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 349, column 0
python2 @ 2.7.17patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ruby-rb-inotify @ 0.9.10description

Validate package descriptions

description should start with an upper-case letter or digit
ruby-tzinfo-data @ 1.2021.1formatting

Look for formatting issues in the source

line 5851 is way too long (101 characters)
ruby-tzinfo-data @ 1.2021.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1904 is way too long (99 characters)
kdelibs4support @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
plasma-framework @ 5.70.1patch-file-names

Validate file names and availability of patches

plasma-framework-fix-KF5PlasmaMacros.cmake.patch: file name is too long
plasma-framework @ 5.70.1formatting

Look for formatting issues in the source

line 3425 is way too long (93 characters)
kpackage @ 5.70.0formatting

Look for formatting issues in the source

line 1957 is way too long (106 characters)
kio @ 5.70.1formatting

Look for formatting issues in the source

line 2796 is way too long (113 characters)
kimageformats @ 5.70.0formatting

Look for formatting issues in the source

line 1819 is way too long (103 characters)
kdbusaddons @ 5.70.0formatting

Look for formatting issues in the source

line 649 is way too long (107 characters)
kcmutils @ 5.70.0formatting

Look for formatting issues in the source

line 2268 is way too long (113 characters)
extra-cmake-modules @ 5.70.0formatting

Look for formatting issues in the source

line 114 is way too long (91 characters)
lua5.2-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
lua-tablepool @ 0.01formatting

Look for formatting issues in the source

line 1062 is way too long (100 characters)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

line 1027 is way too long (104 characters)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

line 1028 is way too long (93 characters)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

line 1029 is way too long (123 characters)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

line 1030 is way too long (112 characters)
lua-resty-shell @ 0.03formatting

Look for formatting issues in the source

line 1094 is way too long (100 characters)
lua-resty-shell @ 0.03formatting

Look for formatting issues in the source

line 1096 is way too long (119 characters)
lua-resty-shell @ 0.03formatting

Look for formatting issues in the source

line 1097 is way too long (108 characters)
lua-resty-lrucache @ 0.10formatting

Look for formatting issues in the source

line 987 is way too long (100 characters)
lua-resty-lrucache @ 0.10formatting

Look for formatting issues in the source

line 989 is way too long (119 characters)
lua-resty-lrucache @ 0.10formatting

Look for formatting issues in the source

line 990 is way too long (108 characters)
lua-resty-core @ 0.1.18formatting

Look for formatting issues in the source

line 952 is way too long (95 characters)
kuserfeedback @ 1.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 279 is way too long (92 characters)
python2 @ 2.7.17formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 292 is way too long (98 characters)
tesseract-ocr @ 4.1.1-1.97079faformatting

Look for formatting issues in the source

line 121 is way too long (93 characters)
clang-runtime @ 3.9.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.8-libsanitizer-mode-field.patch: file name is too long
clang @ 9.0.1formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
clang @ 8.0.0formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
clang @ 7.0.1formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
clang @ 6.0.1formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
clang @ 3.9.1formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
clang @ 3.8.1formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
clang @ 3.7.1formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
clang @ 3.5.2formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
clang @ 11.0.0formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
clang @ 10.0.0formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
openssh-sans-x @ 8.5p1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libreoffice @ 6.4.7.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
389-ds-base @ 1.4.0.31inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' 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
php @ 7.4.16formatting

Look for formatting issues in the source

line 192 is way too long (93 characters)
php @ 7.4.16formatting

Look for formatting issues in the source

line 193 is way too long (93 characters)
php @ 7.4.16formatting

Look for formatting issues in the source

line 204 is way too long (91 characters)
php @ 7.4.16formatting

Look for formatting issues in the source

line 212 is way too long (93 characters)
php @ 7.4.16formatting

Look for formatting issues in the source

line 234 is way too long (92 characters)
php @ 7.4.16formatting

Look for formatting issues in the source

line 235 is way too long (96 characters)
php @ 7.4.16formatting

Look for formatting issues in the source

line 240 is way too long (96 characters)
php @ 7.4.16formatting

Look for formatting issues in the source

line 282 is way too long (91 characters)
php @ 7.4.16formatting

Look for formatting issues in the source

line 295 is way too long (92 characters)
hplip-minimal @ 3.21.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
verilator @ 4.110description

Validate package descriptions

use @code or similar ornament instead of quotes
scotch32 @ 6.1.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

line 3074 is way too long (92 characters)
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

tabulation on line 3094, column 0
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2913, column 0
mumps @ 5.2.1formatting

Look for formatting issues in the source

line 2827 is way too long (94 characters)
geany @ 1.37.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python-pyportmidi @ 217patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
solfege @ 3.22.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1272 is way too long (94 characters)
cgit @ 1.2.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
aegis @ 4.24patch-headers

Validate patch headers

aegis-perl-tempdir2.patch: patch lacks comment and upstream status
git-crypt @ 0.6.0formatting

Look for formatting issues in the source

line 830 is way too long (91 characters)
mumble @ 1.3.4formatting

Look for formatting issues in the source

tabulation on line 544, column 0
mumble @ 1.3.4formatting

Look for formatting issues in the source

tabulation on line 545, column 0
mumble @ 1.3.4formatting

Look for formatting issues in the source

tabulation on line 546, column 0
xwallpaper @ 0.6.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 72
xorg-server-xwayland @ 1.20.10patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

line 4981 is way too long (91 characters)
straw-viewer @ 0.1.3formatting

Look for formatting issues in the source

trailing white space on line 1043
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 294, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 296, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 298, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 300, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 302, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 304, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 306, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 308, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 310, column 18
rust @ 1.47.0formatting

Look for formatting issues in the source

line 1403 is way too long (98 characters)
rust @ 1.47.0formatting

Look for formatting issues in the source

line 1409 is way too long (91 characters)
ppsspp @ 1.11.3description

Validate package descriptions

use @code or similar ornament instead of quotes
fcitx5-gtk @ 5.0.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile-next @ 3.0.5-0.91547absource-file-name

Validate file names of sources

the source file name should contain the package name
guile2.2-readline @ 2.2.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile-readline @ 3.0.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 420 is way too long (94 characters)
guile-readline @ 3.0.2formatting

Look for formatting issues in the source

line 420 is way too long (94 characters)
guile-for-guile-emacs @ 2.1.2-1.15ca784formatting

Look for formatting issues in the source

line 532 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 536
guile @ 2.0.14formatting

Look for formatting issues in the source

line 189 is way too long (94 characters)
guile @ 2.0.14formatting

Look for formatting issues in the source

line 192 is way too long (93 characters)
r-boot @ 1.3-27description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 125, 142
nextcloud-client @ 3.1.3inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
owncloud-client @ 2.7.6.3261patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
texlive-lm @ 51265description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
texlive-hyphen-latin @ 51265description

Validate package descriptions

use @code or similar ornament instead of quotes
texlive-fonts-lm @ 51265description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 78
guile3.0-ncurses @ 3.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
guile3.0-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
guile3.0-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'automake' should probably be a native input
guile3.0-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
guile3.0-mailutils @ 3.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
guile3.0-gi @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
perl-parent @ 5.30.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
texlive-ruhyphen @ 51265formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2370 is way too long (93 characters)
texlive-latex-base @ 51265formatting

Look for formatting issues in the source

tabulation on line 2478, column 22
texlive-hyph-utf8 @ 51265formatting

Look for formatting issues in the source

line 2189 is way too long (108 characters)
texlive-hyph-utf8 @ 51265formatting

Look for formatting issues in the source

line 2190 is way too long (108 characters)
texlive-hyph-utf8 @ 51265formatting

Look for formatting issues in the source

line 2191 is way too long (95 characters)
texlive-amsfonts @ 51265formatting

Look for formatting issues in the source

line 1153 is way too long (94 characters)
texlive-amsfonts @ 51265formatting

Look for formatting issues in the source

line 1178 is way too long (93 characters)
texlive-amsfonts @ 51265formatting

Look for formatting issues in the source

line 1180 is way too long (91 characters)
conda @ 4.8.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
rust-async-process @ 1.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
rust-async-compression @ 0.3.7formatting

Look for formatting issues in the source

line 2571 is way too long (92 characters)
xdg-user-dirs @ 0.17description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gtk-doc' should probably be a native input
plymouth @ 0.9.4formatting

Look for formatting issues in the source

line 2047 is way too long (91 characters)
malcontent @ 0.8.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 812 is way too long (96 characters)
trf @ 4.09.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 387
repeat-masker @ 4.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 387
discrover @ 1.6.0formatting

Look for formatting issues in the source

line 3005 is way too long (91 characters)
glibc-locales-2.29 @ 2.29patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
glibc-hurd-headers @ 2.31patch-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
binutils-gold @ 2.34patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
glibc @ 2.31formatting

Look for formatting issues in the source

line 828 is way too long (98 characters)
guile-zstd @ 0.1.1description

Validate package descriptions

use @code or similar ornament instead of quotes
python-libfreenect @ 0.6.2description

Validate package descriptions

description should start with an upper-case letter or digit
libfreenect-opencv @ 0.6.2description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
aws-checksums @ 0.1.11patch-headers

Validate patch headers

aws-checksums-cmake-prefix.patch: patch lacks comment and upstream status
aws-c-io @ 0.9.2patch-headers

Validate patch headers

aws-c-io-cmake-prefix.patch: patch lacks comment and upstream status
aws-c-io @ 0.9.2patch-headers

Validate patch headers

aws-c-io-disable-networking-tests.patch: patch lacks comment and upstream status
aws-c-event-stream @ 0.2.7patch-headers

Validate patch headers

aws-c-event-stream-cmake-prefix.patch: patch lacks comment and upstream status
aws-c-cal @ 0.4.5patch-headers

Validate patch headers

aws-c-cal-cmake-prefix.patch: patch lacks comment and upstream status
eid-mw @ 5.0.14formatting

Look for formatting issues in the source

line 156 is way too long (97 characters)
eid-mw @ 5.0.14formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
rust-bugreport @ 0.3.0description

Validate package descriptions

description should start with an upper-case letter or digit
zathura-pdf-poppler @ 0.3.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 490 is way too long (93 characters)
password-store @ 1.7.3-1.918992cformatting

Look for formatting issues in the source

line 514 is way too long (91 characters)
lepton-eda @ 1.9.13-20201211inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
librecad @ 2.2.0-rc2source-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 673 is way too long (91 characters)
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

line 674 is way too long (99 characters)
r-dplyr @ 1.0.5description

Validate package descriptions

description should start with an upper-case letter or digit
python-fpylll @ 0.5.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 798
python2-sphinx @ 1.7.7inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-fpylll @ 0.5.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
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
symmetrica @ 2.0patch-headers

Validate patch headers

symmetrica-bruch.patch: patch lacks comment and upstream status
steghide @ 0.5.1patch-headers

Validate patch headers

steghide-fixes.patch: patch lacks comment and upstream status
symmetrica @ 2.0formatting

Look for formatting issues in the source

line 1393 is way too long (100 characters)
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 506, 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 512, 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
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 517, column 0
gap @ 4.11.0formatting

Look for formatting issues in the source

line 1156 is way too long (98 characters)
eigen @ 3.3.8formatting

Look for formatting issues in the source

tabulation on line 1027, column 0
ibus-libhangul @ 1.5.3description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

line 334 is way too long (93 characters)
xpra @ 4.0.6formatting

Look for formatting issues in the source

tabulation on line 6330, column 0
python2-pygobject @ 2.28.7inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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
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
gobject-introspection @ 1.62.0patch-headers

Validate patch headers

gobject-introspection-girepository.patch: patch lacks comment and upstream status
maven-wagon-provider-api @ 3.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/252jsj57fnckdfif43ajaja1n8wql57i-maven-wagon-provider-api-3.3.4 and /gnu/store/il6pya6qpky9m2cg8jn29m9c4zdhvkvn-maven-wagon-provider-api-3.3.4 collide
rseqc @ 3.0.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

tabulation on line 6171, column 26
java-picard @ 2.3.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4197 is way too long (91 characters)
java-picard @ 1.113formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4255 is way too long (117 characters)
tor @ 0.4.5.7description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 574
template-glib @ 3.34.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
python2-minimal @ 2.7.17patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 853 is way too long (97 characters)
python @ 3.8.2formatting

Look for formatting issues in the source

line 491 is way too long (93 characters)
pypy3 @ 7.3.1formatting

Look for formatting issues in the source

line 881 is way too long (91 characters)
appstream-glib @ 0.7.18formatting

Look for formatting issues in the source

line 1087 is way too long (93 characters)
elixir @ 1.11.4formatting

Look for formatting issues in the source

line 76 is way too long (97 characters)
elixir @ 1.11.4formatting

Look for formatting issues in the source

line 77 is way too long (99 characters)
racket-minimal @ 8.0description

Validate package descriptions

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

Validate file names and availability of patches

file names of patches should start with the package name
go-github-com-mitchellh-reflectwalk @ 1.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
rav1e @ 0.3.5inputs-should-be-native

Identify inputs that should be native inputs

'nasm' should probably be a native input
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
openmpi-thread-multiple @ 4.1.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 1931 is way too long (92 characters)
openmpi @ 4.1.0formatting

Look for formatting issues in the source

line 276 is way too long (94 characters)
openmpi @ 4.1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3483 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 3484 is way too long (93 characters)
go-github-com-multiformats-go-multiaddr @ 1.3.0-0.fe1c46fformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
go-github-com-libp2p-go-libp2p-peer @ 2.3.8-0.993d742formatting

Look for formatting issues in the source

line 3232 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 3288 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 3291 is way too long (93 characters)
go-github-com-davecgh-go-spew @ 1.1.1formatting

Look for formatting issues in the source

line 2895 is way too long (129 characters)
gaupol @ 1.9formatting

Look for formatting issues in the source

line 4640 is way too long (95 characters)
busybox @ 1.33.0formatting

Look for formatting issues in the source

line 94 is way too long (92 characters)
bazaar @ 2.7.0formatting

Look for formatting issues in the source

line 160 is way too long (93 characters)
b4 @ 0.6.2formatting

Look for formatting issues in the source

line 2381 is way too long (93 characters)
b4 @ 0.6.2formatting

Look for formatting issues in the source

line 2382 is way too long (112 characters)
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
util-linux @ 2.35.1formatting

Look for formatting issues in the source

line 1591 is way too long (91 characters)
linux-pam @ 1.5.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
unbound @ 1.13.1formatting

Look for formatting issues in the source

trailing white space on line 689
unbound @ 1.13.1formatting

Look for formatting issues in the source

trailing white space on line 725
emilua @ 0.3.0formatting

Look for formatting issues in the source

line 1154 is way too long (98 characters)
python2-twobitreader @ 3.1.6description

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
python2-plastid @ 0.4.8description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
clipper @ 2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
r-bsgenome-dmelanogaster-ucsc-dm3-masked @ 1.3.99formatting

Look for formatting issues in the source

line 224 is way too long (95 characters)
blasr-libcpp @ 5.3.3formatting

Look for formatting issues in the source

line 611 is way too long (95 characters)
mate-polkit @ 1.24.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
atril @ 1.22.0formatting

Look for formatting issues in the source

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

Validate file names and availability of patches

file names of patches should start with the package name
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 250, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 251, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 252, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 253, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 254, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 255, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 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 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 264, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 265, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 266, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 267, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 268, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 270, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 271, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 272, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 273, column 0
giac @ 1.7.0-1formatting

Look for formatting issues in the source

line 351 is way too long (95 characters)
icecat @ 78.9.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1003 is way too long (102 characters)
icecat @ 78.9.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1095 is way too long (139 characters)
icecat @ 78.9.0-guix0-preview1formatting

Look for formatting issues in the source

line 1101 is way too long (95 characters)
icecat @ 78.9.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1145 is way too long (94 characters)
icecat @ 78.9.0-guix0-preview1formatting

Look for formatting issues in the source

line 1147 is way too long (95 characters)
icecat @ 78.9.0-guix0-preview1formatting

Look for formatting issues in the source

line 1160 is way too long (98 characters)
icecat @ 78.9.0-guix0-preview1formatting

Look for formatting issues in the source

line 1289 is way too long (92 characters)
julia-chainrulestestutils @ 0.6.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 260
electron-cash @ 4.2.4inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
sonata @ 1.7.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-requests @ 2.20.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-urllib3@1.24.3 and python-urllib3@1.26.2 collide
python-tornado @ 5.1.1formatting

Look for formatting issues in the source

line 1665 is way too long (91 characters)
ccache @ 4.2formatting

Look for formatting issues in the source

tabulation on line 59, column 0
r-tidyr @ 1.1.3description

Validate package descriptions

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

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 1228
thunar @ 4.16.6inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libstdc++-doc @ 9.3.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
libiberty @ 7.5.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 1337 is way too long (98 characters)
icedove @ 78.9.0formatting

Look for formatting issues in the source

line 1492 is way too long (105 characters)
icedove @ 78.9.0formatting

Look for formatting issues in the source

line 1494 is way too long (102 characters)
cryptsetup-static @ 2.3.5formatting

Look for formatting issues in the source

line 102 is way too long (93 characters)
perftest @ 4.4-0.4description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
fakeroot @ 1.25.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 114, 240
f2fs-fsck-static @ 1.14.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
proot-static @ 5.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
wireless-tools @ 30.pre9formatting

Look for formatting issues in the source

line 3775 is way too long (104 characters)
perftest @ 4.4-0.4formatting

Look for formatting issues in the source

line 5770 is way too long (98 characters)
libblockdev @ 2.25formatting

Look for formatting issues in the source

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

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 882 is way too long (91 characters)
crda @ 3.18formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

tabulation on line 845, column 0
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

tabulation on line 846, column 0
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

tabulation on line 847, column 0
at-spi2-core @ 2.34.0formatting

Look for formatting issues in the source

line 691 is way too long (97 characters)
abseil-cpp @ 20200923.3formatting

Look for formatting issues in the source

line 708 is way too long (116 characters)
abseil-cpp @ 20200923.3formatting

Look for formatting issues in the source

line 709 is way too long (144 characters)
grantleetheme @ 20.04.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile3.0-ncurses-with-gpm @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-sjson @ 0.2.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
guile2.2-email @ 0.2.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
guile-stis-parser @ 1.2.4.1description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
guile-f-scm @ 0.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
guile-email-latest @ 0.2.2-1.ca0520adescription

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
guile2.2-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
guile2.2-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'automake' should probably be a native input
guile2.2-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
guile2.2-gi @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
guile-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'automake' should probably be a native input
guile-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
guile-gi @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
g-golf @ 0.1.0-839.ef83010inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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
guile-dbi @ 2.1.6formatting

Look for formatting issues in the source

line 1459 is way too long (94 characters)
guile-avahi @ 0.4.0-1.6d43cafformatting

Look for formatting issues in the source

line 4290 is way too long (92 characters)
gramps @ 5.1.3inputs-should-be-native

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
mergerfs @ 2.32.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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
zbar @ 0.23inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
linphoneqt @ 4.2.5patch-file-names

Validate file names and availability of patches

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

Validate package descriptions

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
xygrib @ 1.2.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 561 is way too long (92 characters)
julia-openspecfun-jll @ 0.5.3+4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 129
julia-compilersupportlibraries-jll @ 0.4.0+1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 134
julia-compilersupportlibraries-jll @ 0.4.0+1formatting

Look for formatting issues in the source

line 344 is way too long (91 characters)
crypto++ @ 8.5.0source-file-name

Validate file names of sources

the source file name should contain the package name
libsecp256k1 @ 20200615-1.dbd41dbformatting

Look for formatting issues in the source

line 1116 is way too long (106 characters)
espeak-ng @ 1.50description

Validate package descriptions

description should start with an upper-case letter or digit
flite @ 2.2formatting

Look for formatting issues in the source

line 92 is way too long (419 characters)
qtwebglplugin @ 5.15.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 41
qtdatavis3d @ 5.15.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 107, 250
qtcharts @ 5.15.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 244
python-bcj-cffi @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-py7zr @ 0.14.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-multivolumefile @ 0.2.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-bcj-cffi @ 0.5.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
qtserialport @ 5.15.2formatting

Look for formatting issues in the source

line 957 is way too long (115 characters)
qtsensors @ 5.15.2formatting

Look for formatting issues in the source

line 820 is way too long (97 characters)
qtremoteobjects @ 5.15.2formatting

Look for formatting issues in the source

line 1381 is way too long (94 characters)
qtmultimedia @ 5.15.2formatting

Look for formatting issues in the source

line 860 is way too long (96 characters)
qtbase @ 5.15.2formatting

Look for formatting issues in the source

line 396 is way too long (96 characters)
qtbase @ 5.15.2formatting

Look for formatting issues in the source

line 523 is way too long (97 characters)
qtbase @ 5.15.2formatting

Look for formatting issues in the source

line 528 is way too long (94 characters)
qtbase @ 5.15.2formatting

Look for formatting issues in the source

line 530 is way too long (94 characters)
c-blosc @ 1.18.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
google-brotli @ 1.0.9formatting

Look for formatting issues in the source

line 2024 is way too long (94 characters)
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
meshlab @ 2020.06formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
freehdl @ 0.0.8formatting

Look for formatting issues in the source

line 1929 is way too long (104 characters)
r-demultiplex @ 1.0.2-1.6e2a142description

Validate package descriptions

description should start with an upper-case letter or digit
yelp-xsl @ 3.34.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 300
yelp-tools @ 3.32.2inputs-should-be-native

Identify inputs that should be native inputs

'itstool' should probably be a native input
system-config-printer @ 1.5.15inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
gnome-tweaks @ 3.34.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
gjs @ 1.58.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
eolie @ 0.9.101inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
d-feet @ 0.3.14inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
upower @ 0.99.11formatting

Look for formatting issues in the source

line 5410 is way too long (110 characters)
libsoup @ 2.72.0formatting

Look for formatting issues in the source

line 4867 is way too long (128 characters)
libsoup @ 2.72.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
gnome-keyring @ 3.34.0formatting

Look for formatting issues in the source

line 2514 is way too long (91 characters)
glade @ 3.36.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8249 is way too long (103 characters)
samblaster @ 0.1.24description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-rtracklayer @ 1.50.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-drep @ 3.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
variant-tools @ 3.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-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
python-drep @ 3.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' 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
multiqc @ 1.5inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-pygenometracks @ 3.3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-distlib@0.3.1 and python-distlib@0.3.0 collide
vcflib @ 1.0.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 11029 is way too long (99 characters)
r-cellchat @ 1.0.0-1.21edd22formatting

Look for formatting issues in the source

line 9960 is way too long (92 characters)
phast @ 1.5formatting

Look for formatting issues in the source

tabulation on line 14881, column 30
fastahack @ 1.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 11608, column 0
libmypaint @ 1.6.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

line 503 is way too long (107 characters)
poezio @ 0.13.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
v @ 0.1.29name

Validate package names

name should be longer than a single character
librsvg @ 2.50.3formatting

Look for formatting issues in the source

line 3491 is way too long (104 characters)
java-jsch-agentproxy-usocket-nc @ 0.0.8description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
java-xmlunit-matchers @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-xerial-core @ 2.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-stringtemplate @ 4.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-powermock-reflect @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-archiver @ 4.2.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-tinybundles @ 2.1.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core-spi @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core-junit @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-native-access-platform @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-native-access @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-mvel2 @ 2.3.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-microemulator-cldc @ 2.0.4source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-joda-time @ 2.9.9source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-joda-convert @ 1.9.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jline @ 2.14.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jline @ 1.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-jms-api-spec @ 2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-interceptors-api-spec @ 1.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-el-api-spec @ 3.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jansi-native @ 1.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jansi @ 1.16source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-modules-base-mrbean @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-modules-base-jaxb @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-datanucleus-javax-persistence @ 2.2.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-aqute-libg @ 3.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-aqute-bndlib @ 3.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-aqute-bnd-annotation @ 3.5.0source-unstable-tarball

Check for autogenerated tarballs

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

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide
java-plexus-digest @ 1.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@3.1 collide
java-plexus-container-default @ 1.7.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-component-metadata @ 1.7.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@13 and apache-parent-pom@21 collide
java-plexus-compiler-manager @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-compiler-javac @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-compiler-api @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide
java-plexus-archiver @ 4.2.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@6.1 collide
java-modello-test @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-plugins-xpp3 @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-plugins-xml @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-plugins-java @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-core @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-eclipse-sisu-plexus @ 0.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
antlr3 @ 3.5.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-stringtemplate@3.2.1 and java-stringtemplate@4.0.6 collide
java-tunnelvisionlabs-antlr4-runtime-annotations @ 4.7.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-tunnelvisionlabs-antlr4-runtime-annotations @ 4.7.4patch-file-names

Validate file names and availability of patches

java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long
java-tunnelvisionlabs-antlr4-runtime @ 4.7.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-tunnelvisionlabs-antlr4-runtime @ 4.7.4patch-file-names

Validate file names and availability of patches

java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long
java-tunnelvisionlabs-antlr4 @ 4.7.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-tunnelvisionlabs-antlr4 @ 4.7.4patch-file-names

Validate file names and availability of patches

java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long
java-powermock-reflect @ 1.7.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
java-openjfx-media @ 8.202patch-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-controls @ 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-apache-ivy @ 2.4.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9417 is way too long (110 characters)
java-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

line 2722 is way too long (99 characters)
java-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

line 2733 is way too long (98 characters)
java-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

line 2772 is way too long (96 characters)
java-openjfx-base @ 8.202formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2677 is way too long (99 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 11747 is way too long (92 characters)
java-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 7442, column 20
java-eclipse-sisu-plexus @ 0.3.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7501 is way too long (98 characters)
java-commons-jxpath @ 1.3formatting

Look for formatting issues in the source

line 6216 is way too long (93 characters)
java-commons-httpclient @ 3.1formatting

Look for formatting issues in the source

line 12462 is way too long (91 characters)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 8548 is way too long (100 characters)
pjproject-jami @ 2.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
tuxmath @ 2.0.3description

Validate package descriptions

description should start with an upper-case letter or digit
vtk @ 9.0.1formatting

Look for formatting issues in the source

line 295 is way too long (93 characters)
vtk @ 9.0.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 415 is way too long (132 characters)
docker @ 19.03.15formatting

Look for formatting issues in the source

line 355 is way too long (95 characters)
docker @ 19.03.15formatting

Look for formatting issues in the source

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

Validate package descriptions

description should start with an upper-case letter or digit
rust-juliex @ 0.3.0-alpha.8description

Validate package descriptions

description should start with an upper-case letter or digit
rust-funty @ 1.1.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 127
nushell @ 0.29.0description

Validate package descriptions

use @code or similar ornament instead of quotes
rust-libnghttp2-sys @ 0.1.4+1.41.0inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
rust-nix @ 0.15.0formatting

Look for formatting issues in the source

line 25108 is way too long (93 characters)
vim-full @ 8.2.2689formatting

Look for formatting issues in the source

line 224 is way too long (98 characters)
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 9450 is way too long (97 characters)
sooperlooper @ 1.7.6description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
beets-next @ 1.4.9-1.04ea754inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
sorcer @ 1.1.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
lsh @ 2.1patch-headers

Validate patch headers

lsh-fix-x11-forwarding.patch: patch lacks comment and upstream status
vmpk @ 0.8.2formatting

Look for formatting issues in the source

line 2705 is way too long (91 characters)
rosegarden @ 20.12formatting

Look for formatting issues in the source

line 4934 is way too long (94 characters)
rosegarden @ 20.12formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5408, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5409, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5410, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5411, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5413, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5420, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5421, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5422, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5423, column 0
drumstick @ 2.1.1formatting

Look for formatting issues in the source

line 2658 is way too long (91 characters)
chez-srfi @ 1.0formatting

Look for formatting issues in the source

line 289 is way too long (91 characters)
libvirt-glib @ 4.0.0inputs-should-be-native

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 997 is way too long (106 characters)
rtl-sdr @ 0.6.0description

Validate package descriptions

use @code or similar ornament instead of quotes
python-cchardet @ 2.1.7description

Validate package descriptions

description should start with an upper-case letter or digit
python-ppmd-cffi @ 0.3.3inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
calibre @ 5.14.0formatting

Look for formatting issues in the source

line 255 is way too long (92 characters)
calibre @ 5.14.0formatting

Look for formatting issues in the source

line 280 is way too long (93 characters)
ocaml-zarith @ 1.9.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
ocaml-cmdliner @ 1.0.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 304
ocaml-dose3 @ 5.0.1patch-headers

Validate patch headers

ocaml-dose3-dont-make-printconf.patch: patch lacks comment and upstream status
ocaml4.07-sedlex @ 2.1formatting

Look for formatting issues in the source

line 2600 is way too long (97 characters)
ocaml-dose3 @ 5.0.1formatting

Look for formatting issues in the source

line 630 is way too long (92 characters)
python2-pygame @ 1.9.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 60
r-esc @ 0.5.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 178
python-rpy2 @ 3.3.5description

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
libxmlplusplus @ 3.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
libxmlplusplus @ 2.40.1description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 188
java-mxparser @ 1.2.1description

Validate package descriptions

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

Validate package descriptions

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 2408 is way too long (91 characters)
r-esc @ 0.5.1formatting

Look for formatting issues in the source

line 6083 is way too long (94 characters)
java-xom @ 127formatting

Look for formatting issues in the source

trailing white space on line 1961
java-xmlpull-api-v1 @ 1.1.3.4bformatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
freedink-engine @ 109.6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 3159, column 0
axoloti-runtime @ 1.0.12-2formatting

Look for formatting issues in the source

line 192 is way too long (96 characters)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 556 is way too long (93 characters)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'texinfo' should probably be a native input
netcdf-parallel-openmpi @ 4.7.4patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate patch headers

netcdf-date-time.patch: patch lacks comment and upstream status
netcdf @ 4.7.4patch-headers

Validate patch headers

netcdf-date-time.patch: patch lacks comment and upstream status
hdf-java @ 3.3.2formatting

Look for formatting issues in the source

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

Validate package descriptions

description should start with an upper-case letter or digit
python2-ccm @ 2.1.6description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-ccm @ 2.1.6description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
sqlcipher @ 3.4.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
rust-winit @ 0.24.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
rust-winit @ 0.20.0-alpha6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
rust-winit @ 0.19.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 2925 is way too long (114 characters)
laminar @ 1.0source-unstable-tarball

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
laminar @ 1.0formatting

Look for formatting issues in the source

line 221 is way too long (97 characters)
laminar @ 1.0formatting

Look for formatting issues in the source

line 223 is way too long (137 characters)
boost-static @ 1.72.0patch-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
boost-mpi @ 1.72.0patch-file-names

Validate file names and availability of patches

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
gajim @ 1.3.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
gajim @ 1.3.1patch-headers

Validate patch headers

gajim-honour-GAJIM_PLUGIN_PATH.patch: patch lacks comment and upstream status
qwt @ 6.1.5inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
python-pyqt-without-qtwebkit @ 5.15.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python-pyqt @ 5.15.2formatting

Look for formatting issues in the source

line 1941 is way too long (105 characters)
jami-qt @ 20210326.1.cfba013formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
rust-unicode-categories @ 0.1.1description

Validate package descriptions

description should start with an upper-case letter or digit
rust-tungstenite @ 0.11.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 62
rust-stringprep @ 0.1.2description

Validate package descriptions

use @code or similar ornament instead of quotes
rust-snailquote @ 0.3.0description

Validate package descriptions

use @code or similar ornament instead of quotes
missfits @ 2.8.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 268
itcl @ 4.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
hackrf @ 2018.01.1-0.43e6f99description

Validate package descriptions

use @code or similar ornament instead of quotes
ecasound @ 2.9.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471
config @ 0.0.0-1.c8ddc84description

Validate package descriptions

use @code or similar ornament instead of quotes
tao @ 1.0-beta-10May2006inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
tao @ 1.0-beta-10May2006inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'm4' should probably be a native input
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
bsd-games @ 2.17.0patch-headers

Validate patch headers

bsd-games-gamescreen.h.patch: patch lacks comment and upstream status
zita-resampler @ 1.6.2formatting

Look for formatting issues in the source

line 3739 is way too long (93 characters)
vamp @ 2.6formatting

Look for formatting issues in the source

line 3222 is way too long (94 characters)
rust-wasmparser @ 0.57.0formatting

Look for formatting issues in the source

line 48436 is way too long (92 characters)
rust-packed-struct @ 0.3.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 49922, column 0
rust-inflections @ 1.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 50124 is way too long (107 characters)
faad2 @ 2.8.8formatting

Look for formatting issues in the source

line 1739 is way too long (95 characters)
audacity @ 2.4.2formatting

Look for formatting issues in the source

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

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Validate file names and availability of patches

file names of patches should start with the package name
ocaml-llvm @ 9.0.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.5-libsanitizer-mode-field.patch: file name is too long
linux-libre-riscv64-generic @ 5.11.13derivation

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
linux-libre-bpf @ 5.11.13derivation

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
linux-libre @ 5.4.111derivation

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
linux-libre @ 5.11.13derivation

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
linux-libre @ 5.10.29derivation

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
x86-energy-perf-policy @ 5.11.13patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
turbostat @ 5.11.13patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
tmon @ 5.11.13patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-riscv64-generic @ 5.11.13patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-mips64el-fuloong2e @ 5.11.13patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-bpf @ 5.11.13patch-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.111patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm64-generic @ 5.11.13patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm64-generic @ 5.10.29patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-omap2plus @ 5.11.13patch-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.186patch-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.230patch-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.111patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm-generic @ 5.10.29patch-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.186patch-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.230patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-riscv64-generic @ 5.11.13formatting

Look for formatting issues in the source

line 840 is way too long (117 characters)
linux-libre-mips64el-fuloong2e @ 5.11.13formatting

Look for formatting issues in the source

line 840 is way too long (117 characters)
linux-libre-arm64-generic @ 5.4.111formatting

Look for formatting issues in the source

line 840 is way too long (117 characters)
linux-libre-arm64-generic @ 5.11.13formatting

Look for formatting issues in the source

line 840 is way too long (117 characters)
linux-libre-arm64-generic @ 5.10.29formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 840 is way too long (117 characters)
linux-libre @ 5.4.111formatting

Look for formatting issues in the source

line 840 is way too long (117 characters)
linux-libre @ 5.11.13formatting

Look for formatting issues in the source

line 840 is way too long (117 characters)
linux-libre @ 5.10.29formatting

Look for formatting issues in the source

line 840 is way too long (117 characters)
linux-libre @ 4.9.266formatting

Look for formatting issues in the source

line 840 is way too long (117 characters)
linux-libre @ 4.4.266formatting

Look for formatting issues in the source

line 840 is way too long (117 characters)
linux-libre @ 4.19.186formatting

Look for formatting issues in the source

line 840 is way too long (117 characters)
linux-libre @ 4.14.230formatting

Look for formatting issues in the source

line 840 is way too long (117 characters)
u-boot-wandboard @ 2021.04description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
emacs-vcsh @ 0.4.4description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-trashed @ 2.1.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 178
emacs-templatel @ 0.1.4description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-swiper @ 0.13.4description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-pyvenv @ 1.21description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-org-drill-table @ 0.1-0.096387ddescription

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-nhexl-mode @ 1.5description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-ivy-hydra @ 0.13.5description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-gdscript-mode @ 1.4.0description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 220
emacs-envrc @ 0.2description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-el-x @ 0.3.1description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-dhall-mode @ 0.1.3-1.484bcf8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 89
emacs-cnfonts @ 0.9.1description

Validate package descriptions

description should start with an upper-case letter or digit
u-boot-qemu-riscv64-smode @ 2021.04patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-wandboard @ 2021.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 670 is way too long (93 characters)
u-boot-tools @ 2021.04formatting

Look for formatting issues in the source

line 538 is way too long (91 characters)
u-boot-tools @ 2021.04formatting

Look for formatting issues in the source

line 560 is way too long (97 characters)
u-boot-sifive-fu540 @ 2021.04formatting

Look for formatting issues in the source

line 670 is way too long (93 characters)
u-boot-rockpro64-rk3399 @ 2021.04formatting

Look for formatting issues in the source

line 893 is way too long (91 characters)
u-boot-rockpro64-rk3399 @ 2021.04formatting

Look for formatting issues in the source

line 894 is way too long (102 characters)
u-boot-qemu-riscv64 @ 2021.04formatting

Look for formatting issues in the source

line 670 is way too long (93 characters)
u-boot-pinebook-pro-rk3399 @ 2021.04formatting

Look for formatting issues in the source

line 920 is way too long (91 characters)
u-boot-pinebook-pro-rk3399 @ 2021.04formatting

Look for formatting issues in the source

line 921 is way too long (102 characters)
u-boot-pinebook @ 2021.04formatting

Look for formatting issues in the source

line 760 is way too long (127 characters)
u-boot-pine64-plus @ 2021.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
u-boot-nintendo-nes-classic-edition @ 2021.04formatting

Look for formatting issues in the source

line 670 is way too long (93 characters)
u-boot-mx6cuboxi @ 2021.04formatting

Look for formatting issues in the source

line 670 is way too long (93 characters)
u-boot-malta @ 2021.04formatting

Look for formatting issues in the source

line 670 is way too long (93 characters)
u-boot-cubietruck @ 2021.04formatting

Look for formatting issues in the source

line 670 is way too long (93 characters)
u-boot-cubieboard @ 2021.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 711 is way too long (95 characters)
u-boot-a20-olinuxino-micro @ 2021.04formatting

Look for formatting issues in the source

line 670 is way too long (93 characters)
u-boot-a20-olinuxino-lime2 @ 2021.04formatting

Look for formatting issues in the source

line 670 is way too long (93 characters)
u-boot-a20-olinuxino-lime @ 2021.04formatting

Look for formatting issues in the source

line 670 is way too long (93 characters)
tinmop @ 0.5.9formatting

Look for formatting issues in the source

line 902 is way too long (122 characters)
emacs-telega @ 0.7.1-1.1d28dc2formatting

Look for formatting issues in the source

line 25218 is way too long (99 characters)
emacs-telega @ 0.7.1-1.1d28dc2formatting

Look for formatting issues in the source

tabulation on line 25240, column 0
emacs-telega @ 0.7.1-1.1d28dc2formatting

Look for formatting issues in the source

tabulation on line 25241, column 0
emacs-telega @ 0.7.1-1.1d28dc2formatting

Look for formatting issues in the source

tabulation on line 25244, column 0
emacs-telega @ 0.7.1-1.1d28dc2formatting

Look for formatting issues in the source

tabulation on line 25248, column 0
emacs-sqlite @ 1.0-0.dad42b8formatting

Look for formatting issues in the source

tabulation on line 4770, column 0
emacs-sqlite @ 1.0-0.dad42b8formatting

Look for formatting issues in the source

tabulation on line 4771, column 0
emacs-powershell @ 0.3-0.d1b3f95formatting

Look for formatting issues in the source

tabulation on line 14587, column 0
emacs-powershell @ 0.3-0.d1b3f95formatting

Look for formatting issues in the source

tabulation on line 14588, column 0
emacs-org @ 9.4.5formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
emacs-mit-scheme-doc @ 20140203formatting

Look for formatting issues in the source

line 6193 is way too long (94 characters)
emacs-gtk-look @ 29formatting

Look for formatting issues in the source

line 20952 is way too long (94 characters)
emacs-exwm @ 0.24formatting

Look for formatting issues in the source

line 12849 is way too long (96 characters)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13219, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13220, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13223, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13224, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13236, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13237, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13238, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13239, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13240, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13241, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13242, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13243, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13244, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13245, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13246, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13247, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13248, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13249, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13250, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13251, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13252, column 0
emacs-dash-docs @ 1.4.0-2.dafc8fcformatting

Look for formatting issues in the source

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
sendmail @ 8.15.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'm4' should probably be a native input
guile2.2-mailutils @ 3.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
astroid @ 0.15inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-hyperkitty @ 1.3.3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-django@2.2.20 and python-django@3.1.8 collide
python-mailman-hyperkitty @ 1.1.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 3456 is way too long (168 characters)
python2-pytest-xdist @ 2.1.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-mock @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-mock' should probably be a native input
python2-pytest-mock @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-cov-core @ 1.15.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python-testtools @ 2.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-testscenarios @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-testresources @ 2.0.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-pytest-xdist @ 2.1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-timeout @ 1.3.4inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-mock @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-lazy-fixture @ 0.6.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-forked @ 1.1.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-fixtures @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-cov-core @ 1.15.0inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-codecov @ 2.0.15inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
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
restinio @ 0.6.13formatting

Look for formatting issues in the source

line 3432 is way too long (105 characters)
restinio @ 0.6.13formatting

Look for formatting issues in the source

line 3446 is way too long (95 characters)
ucsim @ 0.6-pre67description

Validate package descriptions

description should start with an upper-case letter or digit
python-mypy @ 0.790description

Validate package descriptions

use @code or similar ornament instead of quotes
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-robber @ 1.1.5inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-pytest-vcr @ 1.0.2-1.4d6c7b3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-sanic @ 1.7.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' 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
python-pytest-checkdocs @ 1.2.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
emacs-beancount @ 2.2.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python2-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1173 is way too long (96 characters)
python-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1140 is way too long (94 characters)
jimtcl @ 0.80formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
fc-host-tools @ 14formatting

Look for formatting issues in the source

line 1264 is way too long (122 characters)
bitcoin-unlimited @ 1.9.1.1formatting

Look for formatting issues in the source

line 1459 is way too long (91 characters)
wpa-supplicant-minimal @ 2.9description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
mosquitto @ 1.6.12description

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-nose' should probably be a native input
java-eclipse-jetty-xml @ 9.4.39source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
wpa-supplicant-minimal @ 2.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
wpa-supplicant-gui @ 2.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
scotch-shared @ 6.1.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
http-parser @ 2.9.4-1.ec8b5eepatch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
hostapd @ 2.9patch-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
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
netsurf @ 3.10patch-headers

Validate patch headers

netsurf-message-timestamp.patch: patch lacks comment and upstream status
varnish @ 6.5.1formatting

Look for formatting issues in the source

line 6030 is way too long (91 characters)
sundials-openmpi @ 3.1.1formatting

Look for formatting issues in the source

tabulation on line 5237, column 0
pt-scotch32 @ 6.1.0formatting

Look for formatting issues in the source

tabulation on line 3349, column 0
pt-scotch @ 6.1.0formatting

Look for formatting issues in the source

tabulation on line 3327, column 0
psi-plus @ 1.5.1482formatting

Look for formatting issues in the source

line 2806 is way too long (96 characters)
p4est @ 2.0formatting

Look for formatting issues in the source

tabulation on line 3438, column 0
hypre-openmpi @ 2.15.1formatting

Look for formatting issues in the source

tabulation on line 4666, column 0
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
sbcl-quri @ 0.3.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-mixomics @ 6.14.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-biosigner @ 1.18.2description

Validate package descriptions

use @code or similar ornament instead of quotes
r-biomart @ 2.46.3description

Validate package descriptions

description should start with an upper-case letter or digit
r-biocio @ 1.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
r-bioassayr @ 1.28.2description

Validate package descriptions

description should start with an upper-case letter or digit
ecl-trivial-gray-streams @ 0.0.0-1.ebd59b1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 75
ecl-quri @ 0.3.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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