Language
Lint warnings where the package name matches the query.
Lint warnings for specific lint checkers.
Lint warnings where the message matches the query.
Fields to return in the response.

Lint warnings

PackageLinterMessageLocation
perl-crypt-unixcrypt_xs @ 0.11name

Validate package names

name should use hyphens instead of underscores
nsis-x86_64 @ 3.05name

Validate package names

name should use hyphens instead of underscores
mingw-w64-x86_64-winpthreads @ 8.0.0name

Validate package names

name should use hyphens instead of underscores
mingw-w64-x86_64 @ 8.0.0name

Validate package names

name should use hyphens instead of underscores
wxwidgets-gtk2 @ 3.1.5description

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
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-ctr @ 0.8.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 77
rust-ctr @ 0.6.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 77
rust-charset @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
rust-bugreport @ 0.4.0description

Validate package descriptions

description should start with an upper-case letter or digit
rust-bugreport @ 0.3.0description

Validate package descriptions

description should start with an upper-case letter or digit
rust-avif-serialize @ 0.6.5description

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
python-wxpython @ 4.0.7.post1description

Validate package descriptions

description should start with an upper-case letter or digit
python-rpy2 @ 3.4.5description

Validate package descriptions

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

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
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-libxml @ 0.08description

Validate package descriptions

description should start with an upper-case letter or digit
perl-digest-sha @ 6.02description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 82
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
node-serialport-parser-ready @ 9.2.4description

Validate package descriptions

use @code or similar ornament instead of quotes
node-nan @ 2.15.0description

Validate package descriptions

use @code or similar ornament instead of quotes
myrddin @ 0.3.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
mate-applets @ 1.24.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 917
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
kget @ 20.04.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 169
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-chainrulestestutils @ 1.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 260
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
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-silver @ 3.2.3description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-tasty-expected-failure @ 0.12.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 185
ghc-quickcheck-classes-base @ 0.6.2.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-quickcheck-classes-base @ 0.6.2.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 109, 318, 450, 544
ghc-operational @ 0.2.4.0description

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.9.1.5description

Validate package descriptions

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

Validate package descriptions

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

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-doctest-lib @ 0.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 35
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
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-stevedore @ 3.2.2inputs-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.utils @ 4.12.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-oslo.serialization @ 4.2.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-orange-canvas-core @ 0.1.24inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' 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
python-debtcollector @ 1.19.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
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
perl-extutils-pkgconfig @ 1.16inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
nextcloud-client @ 3.2.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
libtool @ 2.4.6inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
libreoffice @ 7.1.4.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kget @ 20.04.1inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kaddressbook @ 20.04.1inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
juk @ 20.04.1inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
gramps @ 5.1.4inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' 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
fcitx-qt5 @ 1.2.6inputs-should-be-native

Identify inputs that should be native inputs

'intltool' 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.7.6inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
bison @ 3.7.6inputs-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
autoconf @ 2.71inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
autoconf @ 2.69inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
autoconf @ 2.68inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
autoconf @ 2.64inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
autoconf @ 2.13inputs-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
389-ds-base @ 1.4.4.17inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' 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-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
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
infiniband-diags @ 2.0.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
389-ds-base @ 1.4.4.17source-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'
synfig @ 1.2.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs glibmm@2.70.0 and glibmm@2.64.5 collide
clojure-tools-deps-alpha @ 0.12.1104profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-oss-parent-pom@7 and java-sonatype-oss-parent-pom@9 collide
tigervnc-server @ 1.12.0-0.b484c22patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
sed @ 4.8patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
pjproject-jami @ 2.11-0.e1f389dpatch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
owncloud-client @ 2.9.0.5150patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
nsis-i686 @ 3.05patch-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
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
libmhash @ 0.9.9.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libjami @ 20211223.2.37be4c3patch-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
jami-libclient @ 20211223.2.37be4c3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
jami-gnome @ 20211223.2.37be4c3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with 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-static-stripped-tarball @ 3.0.7patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
ghostscript-with-cups @ 9.54.0patch-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
coreutils-minimal @ 8.32patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
avr-binutils @ 2.37patch-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
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
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
mcrypt @ 2.6.8patch-headers

Validate patch headers

mcrypt-CVE-2012-4426.patch: patch lacks comment and upstream status
linuxdcpp @ 1.1.0patch-headers

Validate patch headers

linuxdcpp-openssl-1.1.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
guile-git @ 0.5.2patch-headers

Validate patch headers

guile-git-adjust-for-libgit2-1.2.0.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.7.0patch-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
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

line 2353 is way too long (91 characters)
tmux-themepack @ 1.1.0formatting

Look for formatting issues in the source

line 93 is way too long (95 characters)
tesseract-ocr @ 4.1.1-1.97079faformatting

Look for formatting issues in the source

line 122 is way too long (93 characters)
telegram-desktop @ 2.9.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 211 is way too long (106 characters)
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 2988 is way too long (114 characters)
ruby-iruby @ 0.3formatting

Look for formatting issues in the source

line 506 is way too long (112 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)
r-bsgenome-dmelanogaster-ucsc-dm3-masked @ 1.3.99formatting

Look for formatting issues in the source

line 275 is way too long (95 characters)
python2 @ 2.7.18formatting

Look for formatting issues in the source

line 222 is way too long (99 characters)
purescript @ 0.14.5formatting

Look for formatting issues in the source

line 121 is way too long (92 characters)
presentty @ 0.2.1formatting

Look for formatting issues in the source

line 45 is way too long (117 characters)
podman @ 3.4.4formatting

Look for formatting issues in the source

line 313 is way too long (99 characters)
podman @ 3.4.4formatting

Look for formatting issues in the source

line 316 is way too long (94 characters)
php @ 7.4.26formatting

Look for formatting issues in the source

line 194 is way too long (93 characters)
php @ 7.4.26formatting

Look for formatting issues in the source

line 195 is way too long (93 characters)
php @ 7.4.26formatting

Look for formatting issues in the source

line 220 is way too long (91 characters)
php @ 7.4.26formatting

Look for formatting issues in the source

line 228 is way too long (93 characters)
php @ 7.4.26formatting

Look for formatting issues in the source

line 250 is way too long (92 characters)
php @ 7.4.26formatting

Look for formatting issues in the source

line 251 is way too long (96 characters)
php @ 7.4.26formatting

Look for formatting issues in the source

line 256 is way too long (96 characters)
php @ 7.4.26formatting

Look for formatting issues in the source

line 298 is way too long (91 characters)
php @ 7.4.26formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 104 is way too long (92 characters)
opam @ 2.1.2formatting

Look for formatting issues in the source

line 880 is way too long (99 characters)
opam @ 2.1.2formatting

Look for formatting issues in the source

line 882 is way too long (99 characters)
opam @ 2.1.2formatting

Look for formatting issues in the source

line 884 is way too long (99 characters)
opam @ 2.1.2formatting

Look for formatting issues in the source

line 886 is way too long (102 characters)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 129 is way too long (114 characters)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 129 is way too long (114 characters)
node-serialport @ 9.2.7formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
netpbm @ 10.78.3formatting

Look for formatting issues in the source

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

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)
mbedtls-apache @ 2.26.0formatting

Look for formatting issues in the source

line 966 is way too long (96 characters)
mate-panel @ 1.24.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 486 is way too long (91 characters)
lxqt-session @ 0.17.1formatting

Look for formatting issues in the source

line 846 is way too long (92 characters)
lxqt-session @ 0.17.1formatting

Look for formatting issues in the source

line 853 is way too long (100 characters)
lxqt-session @ 0.17.1formatting

Look for formatting issues in the source

line 871 is way too long (98 characters)
lxde-common @ 0.99.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libunibreak @ 5.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libtomcrypt @ 1.18.2formatting

Look for formatting issues in the source

line 366 is way too long (100 characters)
libsigsegv @ 2.13formatting

Look for formatting issues in the source

line 48 is way too long (133 characters)
libetc1 @ 7.1.2_r36formatting

Look for formatting issues in the source

tabulation on line 805, column 20
libdaemon @ 0.14formatting

Look for formatting issues in the source

line 38 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
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
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 312, column 18
julia-xorg-xcb-util-renderutil-jll @ 0.3.9+1formatting

Look for formatting issues in the source

line 2428 is way too long (93 characters)
julia-reversediff @ 1.9.0formatting

Look for formatting issues in the source

line 4590 is way too long (103 characters)
julia-libuuid-jll @ 2.36.0+0formatting

Look for formatting issues in the source

line 1219 is way too long (92 characters)
julia-compilersupportlibraries-jll @ 0.4.0+1formatting

Look for formatting issues in the source

line 157 is way too long (91 characters)
julia @ 1.6.3formatting

Look for formatting issues in the source

line 238 is way too long (107 characters)
julia @ 1.6.3formatting

Look for formatting issues in the source

line 240 is way too long (106 characters)
julia @ 1.6.3formatting

Look for formatting issues in the source

line 454 is way too long (101 characters)
julia @ 1.6.3formatting

Look for formatting issues in the source

line 459 is way too long (124 characters)
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
java-jbzip2 @ 0.9.1formatting

Look for formatting issues in the source

line 277 is way too long (92 characters)
irods-client-icommands @ 4.2.8formatting

Look for formatting issues in the source

line 235 is way too long (91 characters)
irods @ 4.2.8formatting

Look for formatting issues in the source

line 104 is way too long (93 characters)
irods @ 4.2.8formatting

Look for formatting issues in the source

line 132 is way too long (91 characters)
hyperledger-iroha @ 1.1.1formatting

Look for formatting issues in the source

line 166 is way too long (105 characters)
guile2.2-readline @ 2.2.7formatting

Look for formatting issues in the source

line 506 is way too long (94 characters)
guile-sdl @ 0.5.3formatting

Look for formatting issues in the source

line 609 is way too long (111 characters)
guile-readline @ 3.0.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 585 is way too long (96 characters)
guile @ 2.0.14formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 208 is way too long (93 characters)
gnome-initial-setup @ 40.4formatting

Look for formatting issues in the source

line 1502 is way too long (91 characters)
gmp @ 6.2.1formatting

Look for formatting issues in the source

line 83 is way too long (96 characters)
glibc @ 2.33formatting

Look for formatting issues in the source

line 810 is way too long (98 characters)
ghc-quickcheck-classes-base @ 0.6.2.0formatting

Look for formatting issues in the source

line 1113 is way too long (101 characters)
ghc-quickcheck-classes @ 0.6.5.0formatting

Look for formatting issues in the source

line 1069 is way too long (91 characters)
ghc-monad-par @ 0.3.5formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ghc-doctest-exitcode-stdio @ 0.0formatting

Look for formatting issues in the source

line 1174 is way too long (99 characters)
ghc-base-unicode-symbols @ 0.2.4.2formatting

Look for formatting issues in the source

line 938 is way too long (93 characters)
ghc-base-unicode-symbols @ 0.2.4.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 865 is way too long (91 characters)
ghc @ 8.10.7formatting

Look for formatting issues in the source

line 992 is way too long (93 characters)
ghc @ 8.10.7formatting

Look for formatting issues in the source

line 998 is way too long (92 characters)
ghc @ 4.08.2formatting

Look for formatting issues in the source

line 330 is way too long (93 characters)
ghc @ 4.08.2formatting

Look for formatting issues in the source

line 331 is way too long (91 characters)
flite @ 2.2formatting

Look for formatting issues in the source

line 93 is way too long (419 characters)
fastboot @ 7.1.2_r36formatting

Look for formatting issues in the source

line 718 is way too long (105 characters)
etc1tool @ 7.1.2_r36formatting

Look for formatting issues in the source

tabulation on line 852, column 20
etc1tool @ 7.1.2_r36formatting

Look for formatting issues in the source

line 880 is way too long (98 characters)
efitools @ 1.9.2formatting

Look for formatting issues in the source

line 211 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)
cryptsetup-static @ 2.3.7formatting

Look for formatting issues in the source

line 110 is way too long (93 characters)
cni-plugins @ 1.0.1formatting

Look for formatting issues in the source

line 249 is way too long (93 characters)
cloudflare-cli @ 0.0.0-1.2d986d3formatting

Look for formatting issues in the source

line 122 is way too long (92 characters)
clojure-tools-deps-alpha @ 0.12.1104formatting

Look for formatting issues in the source

line 500 is way too long (94 characters)
clojure-data-xml @ 0.2.0-alpha6formatting

Look for formatting issues in the source

line 341 is way too long (93 characters)
clojure-data-xml @ 0.2.0-alpha6formatting

Look for formatting issues in the source

line 342 is way too long (91 characters)
axoloti-runtime @ 1.0.12-2formatting

Look for formatting issues in the source

line 197 is way too long (96 characters)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 558 is way too long (93 characters)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

line 571 is way too long (103 characters)
atril @ 1.24.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 460 is way too long (95 characters)
android-platform-frameworks-native-headers @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 305, column 20
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

line 413 is way too long (97 characters)
labplot @ 2.8.2inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kdevelop @ 5.6.1inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kdenlive @ 21.12.3inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
grantleetheme @ 20.04.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-pep-adapter @ 2.1.3inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
ppsspp @ 1.12.3description

Validate package descriptions

use @code or similar ornament instead of quotes
cc65 @ 2.19formatting

Look for formatting issues in the source

line 2490 is way too long (167 characters)
mumble @ 1.4.230formatting

Look for formatting issues in the source

tabulation on line 583, column 0
mumble @ 1.4.230formatting

Look for formatting issues in the source

tabulation on line 584, column 0
mumble @ 1.4.230formatting

Look for formatting issues in the source

tabulation on line 585, column 0
python-doit @ 0.34.0description

Validate package descriptions

description should start with an upper-case letter or digit
python-phpserialize @ 1.3formatting

Look for formatting issues in the source

line 28944 is way too long (92 characters)
python-phpserialize @ 1.3formatting

Look for formatting issues in the source

line 28949 is way too long (97 characters)
steghide @ 0.5.1patch-headers

Validate patch headers

steghide-fixes.patch: patch lacks comment and upstream status
python-joblib @ 1.1.0formatting

Look for formatting issues in the source

line 4149 is way too long (91 characters)
python-joblib @ 1.1.0formatting

Look for formatting issues in the source

line 4150 is way too long (94 characters)
python-pytest-datadir @ 1.3.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-ccm @ 2.1.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 84
xfce4-clipman-plugin @ 1.6.2formatting

Look for formatting issues in the source

line 476 is way too long (91 characters)
tumbler @ 4.16.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ghc-unsafe @ 0.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ghc-template-haskell @ 2.16.0.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 111
ghc-rio @ 0.1.21.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-doclayout @ 0.3.1.1description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-commonmark @ 0.2.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 630
libsecp256k1 @ 20200615-1.dbd41dbformatting

Look for formatting issues in the source

line 1120 is way too long (103 characters)
ghc-xdg-basedir @ 0.2.2formatting

Look for formatting issues in the source

line 14679 is way too long (93 characters)
ghc-vector @ 0.12.3.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 13007 is way too long (92 characters)
ghc-template-haskell-compat-v0208 @ 0.1.6formatting

Look for formatting issues in the source

line 15580 is way too long (111 characters)
ghc-persistent-postgresql @ 2.13.2.1formatting

Look for formatting issues in the source

line 15893 is way too long (95 characters)
ghc-optparse-applicative @ 0.15.1.0formatting

Look for formatting issues in the source

line 8743 is way too long (95 characters)
ghc-indexed-traversable @ 0.1.1formatting

Look for formatting issues in the source

line 14944 is way too long (91 characters)
ghc-hspec-expectations-lifted @ 0.10.0formatting

Look for formatting issues in the source

line 15773 is way too long (103 characters)
ghc-commonmark-extensions @ 0.2.2formatting

Look for formatting issues in the source

line 15355 is way too long (95 characters)
genimage @ 15-1.ec44ae0patch-headers

Validate patch headers

genimage-mke2fs-test.patch: patch lacks comment and upstream status
mumble @ 1.4.230formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
gcompris @ 17.05formatting

Look for formatting issues in the source

line 142 is way too long (96 characters)
libxt @ 1.2.1patch-headers

Validate patch headers

libxt-guix-search-paths.patch: patch lacks comment and upstream status
util-linux-with-udev @ 2.37.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xpra @ 4.3.1formatting

Look for formatting issues in the source

tabulation on line 6384, column 0
unbound @ 1.13.2formatting

Look for formatting issues in the source

trailing white space on line 748
unbound @ 1.13.2formatting

Look for formatting issues in the source

trailing white space on line 784
ghc-hxt-unicode @ 9.0.2.4description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ghc-language-javascript @ 0.7.1.0formatting

Look for formatting issues in the source

line 1932 is way too long (91 characters)
ghc-hxt-unicode @ 9.0.2.4formatting

Look for formatting issues in the source

line 1484 is way too long (91 characters)
verilator @ 4.204description

Validate package descriptions

use @code or similar ornament instead of quotes
abc @ 0.0-1.5ae4b97formatting

Look for formatting issues in the source

line 97 is way too long (95 characters)
config @ 0.0.0-1.c8ddc84description

Validate package descriptions

use @code or similar ornament instead of quotes
libtool @ 2.4.7inputs-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 641 is way too long (92 characters)
mate-polkit @ 1.24.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
rust-funty @ 1.2.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 127
rust-funty @ 1.1.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 127
rust-crates-index-5 @ 0.5.1inputs-should-be-native

Identify inputs that should be native inputs

'cmake' should probably be a native input
rust-crates-index-5 @ 0.5.1formatting

Look for formatting issues in the source

line 13794 is way too long (91 characters)
marble-qt @ 21.12.3inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kuserfeedback @ 1.0.0formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
fcitx5-gtk4 @ 5.0.9inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
fcitx5-gtk @ 5.0.9inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
volctl @ 0.8.2formatting

Look for formatting issues in the source

line 2887 is way too long (98 characters)
xdg-user-dirs @ 0.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
python-cchardet @ 2.1.7description

Validate package descriptions

description should start with an upper-case letter or digit
udiskie @ 2.3.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
plymouth @ 0.9.5formatting

Look for formatting issues in the source

line 2105 is way too long (91 characters)
swaks @ 20201014.0formatting

Look for formatting issues in the source

line 3642 is way too long (106 characters)
xfce4-volumed-pulse @ 0.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
python-pyaml @ 18.11.0description

Validate package descriptions

description should start with an upper-case letter or digit
zeitgeist @ 1.0.4formatting

Look for formatting issues in the source

tabulation on line 771, column 18
zeitgeist @ 1.0.4formatting

Look for formatting issues in the source

tabulation on line 774, column 18
knotes @ 20.04.1inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
python-mutatormath @ 3.0.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 129
python-jupyterlab-widgets @ 1.0.0description

Validate package descriptions

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-docrepr @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-jupyterlab-widgets @ 1.0.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-jupyter-packaging @ 0.12.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
t1lib @ 5.1.2patch-headers

Validate patch headers

t1lib-CVE-2010-2642.patch: patch lacks comment and upstream status
propeller-gcc @ 6.0.0-1.b4f45a472patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
propeller-gcc @ 4.6.1-2.4c46ecbe7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gcc-cross-sans-libc-arm-none-eabi @ 7-2018-q2-update-1.261907patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
zathura-pdf-poppler @ 0.3.0formatting

Look for formatting issues in the source

line 575 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)
python-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1135 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
gcc-cross-sans-libc-arm-none-eabi @ 7-2018-q2-update-1.261907formatting

Look for formatting issues in the source

line 345 is way too long (99 characters)
fdroidserver @ 1.1.9formatting

Look for formatting issues in the source

line 1157 is way too long (106 characters)
idris @ 1.3.4formatting

Look for formatting issues in the source

line 102 is way too long (100 characters)
python-sphinx @ 4.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
jfs_fsck-static @ 1.1.15name

Validate package names

name should use hyphens instead of underscores
libnfs @ 4.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
cawbird @ 1.4.2formatting

Look for formatting issues in the source

line 88 is way too long (104 characters)
qemu-minimal @ 6.2.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ocaml4.07-qcheck @ 0.12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 52, 156
ocaml-zarith @ 1.12description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 52, 156
ocaml-down @ 0.1.0description

Validate package descriptions

use @code or similar ornament instead of quotes
ocaml-ounit @ 2.2.6formatting

Look for formatting issues in the source

line 1427 is way too long (97 characters)
nss-certs @ 3.71patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
chez-scheme-for-racket-bootstrap-bootfiles @ 9.5.7.6description

Validate package descriptions

use @code or similar ornament instead of quotes
ruby-progress_bar @ 1.1.0name

Validate package names

name should use hyphens instead of underscores
ruby-data_uri @ 0.1.0name

Validate package names

name should use hyphens instead of underscores
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 5731 is way too long (101 characters)
ruby-tzinfo-data @ 1.2021.1formatting

Look for formatting issues in the source

line 5732 is way too long (107 characters)
ruby-asciidoctor-pdf @ 1.6.1formatting

Look for formatting issues in the source

line 1852 is way too long (97 characters)
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
infamous-plugins @ 0.3.0formatting

Look for formatting issues in the source

line 1143 is way too long (104 characters)
faad2 @ 2.8.8formatting

Look for formatting issues in the source

line 1874 is way too long (95 characters)
audacity @ 3.1.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
guile2.2-gnutls @ 3.7.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
cmake @ 3.21.4formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libxcrypt @ 4.4.28description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 62
itcl @ 4.2.2description

Validate package descriptions

description should start with an upper-case letter or digit
mescc-tools-static-stripped-tarball @ 1.4.0derivation

Report failure to compile a package to a derivation

failed to create riscv32-linux derivation: could not find bootstrap binary 'tar' for system 'riscv32-linux'
mescc-tools @ 1.4.0derivation

Report failure to compile a package to a derivation

failed to create riscv32-linux derivation: could not find bootstrap binary 'tar' for system 'riscv32-linux'
wine64-staging @ 7.8inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'autoconf' should probably be a native input
cups-minimal @ 2.3.3op2formatting

Look for formatting issues in the source

tabulation on line 290, column 0
cups-minimal @ 2.3.3op2formatting

Look for formatting issues in the source

tabulation on line 291, column 0
cups-minimal @ 2.3.3op2formatting

Look for formatting issues in the source

tabulation on line 292, column 0
cups-minimal @ 2.3.3op2formatting

Look for formatting issues in the source

tabulation on line 293, column 0
rust-juliex @ 0.3.0-alpha.8description

Validate package descriptions

description should start with an upper-case letter or digit
rust-is-debug @ 1.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
js-mathjax @ 3.2.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
js-mathjax @ 3.2.0formatting

Look for formatting issues in the source

line 234 is way too long (92 characters)
js-mathjax @ 3.2.0formatting

Look for formatting issues in the source

line 275 is way too long (92 characters)
js-mathjax @ 2.7.2formatting

Look for formatting issues in the source

line 156 is way too long (91 characters)
plasma-framework @ 5.70.1inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kwallet @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kservice @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kpackage @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kio @ 5.70.1inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kinit @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kdesignerplugin @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kded @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' 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
polkit-duktape @ 0.120patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
kpackage @ 5.70.0patch-headers

Validate patch headers

kpackage-allow-external-paths.patch: patch lacks comment and upstream status
plasma-framework @ 5.70.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 646 is way too long (121 characters)
kcmutils @ 5.70.0formatting

Look for formatting issues in the source

line 2191 is way too long (113 characters)
extra-cmake-modules @ 5.91.0formatting

Look for formatting issues in the source

line 128 is way too long (92 characters)
extra-cmake-modules @ 5.91.0formatting

Look for formatting issues in the source

line 129 is way too long (107 characters)
extra-cmake-modules @ 5.91.0formatting

Look for formatting issues in the source

line 142 is way too long (92 characters)
u-boot-wandboard @ 2022.04patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-sifive-unmatched @ 2022.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-sifive-unleashed @ 2022.04patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-rock64-rk3328 @ 2022.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-qemu-riscv64-smode @ 2022.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-qemu-riscv64 @ 2022.04patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-mx6cuboxi @ 2022.04patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
grub-efi32 @ 2.06patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-wandboard @ 2022.04formatting

Look for formatting issues in the source

line 742 is way too long (93 characters)
u-boot-tools @ 2022.04formatting

Look for formatting issues in the source

line 621 is way too long (108 characters)
u-boot-tools @ 2022.04formatting

Look for formatting issues in the source

line 625 is way too long (97 characters)
u-boot-sifive-unleashed @ 2022.04formatting

Look for formatting issues in the source

line 742 is way too long (93 characters)
u-boot-qemu-riscv64-smode @ 2022.04formatting

Look for formatting issues in the source

line 742 is way too long (93 characters)
u-boot-qemu-riscv64 @ 2022.04formatting

Look for formatting issues in the source

line 742 is way too long (93 characters)
u-boot-pinebook @ 2022.04formatting

Look for formatting issues in the source

line 829 is way too long (127 characters)
u-boot-pine64-plus @ 2022.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 742 is way too long (93 characters)
u-boot-malta @ 2022.04formatting

Look for formatting issues in the source

line 742 is way too long (93 characters)
u-boot-cubietruck @ 2022.04formatting

Look for formatting issues in the source

line 742 is way too long (93 characters)
u-boot-cubieboard @ 2022.04formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 780 is way too long (95 characters)
u-boot-a20-olinuxino-micro @ 2022.04formatting

Look for formatting issues in the source

line 742 is way too long (93 characters)
u-boot-a20-olinuxino-lime2 @ 2022.04formatting

Look for formatting issues in the source

line 742 is way too long (93 characters)
u-boot-a20-olinuxino-lime @ 2022.04formatting

Look for formatting issues in the source

line 742 is way too long (93 characters)
sbcl-trivial-gray-streams @ 2.0-1.2b3823edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 75
ecl-trivial-gray-streams @ 2.0-1.2b3823edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 75
cl-trivial-gray-streams @ 2.0-1.2b3823edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 75
python-libxml2 @ 2.9.12patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libxml2-xpath0 @ 2.9.12patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
sbcl-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 313 is way too long (96 characters)
guile-zstd @ 0.1.1description

Validate package descriptions

use @code or similar ornament instead of quotes
superstarfighter @ 0.6.5formatting

Look for formatting issues in the source

line 2602 is way too long (115 characters)
sane-airscan @ 0.99.27description

Validate package descriptions

use @code or similar ornament instead of quotes
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 1075 is way too long (100 characters)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 965 is way too long (95 characters)
emilua @ 0.3.2formatting

Look for formatting issues in the source

line 1162 is way too long (102 characters)
emacs-xwidgets @ 28.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
espeak-ng @ 1.51description

Validate package descriptions

description should start with an upper-case letter or digit
elm-terezka-intervals @ 2.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
sonata @ 1.7.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-pytest-django @ 4.4.0inputs-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
python-louvain @ 0.16inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
libiberty @ 10.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
gccgo @ 11.3.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
elm-sans-reactor @ 0.19.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
unzip @ 6.0patch-headers

Validate patch headers

unzip-case-insensitive.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-CVE-2018-1000035.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-CVE-2018-18384.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-manpage-fix.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-overflow.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-valgrind.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-x-option.patch: patch lacks comment and upstream status
p7zip @ 16.02patch-headers

Validate patch headers

p7zip-remove-unused-code.patch: patch lacks comment and upstream status
mpdris2 @ 0.9.1formatting

Look for formatting issues in the source

line 427 is way too long (96 characters)
minizip @ 1.2.11formatting

Look for formatting issues in the source

line 168 is way too long (115 characters)
mergerfs @ 2.33.5formatting

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 772 is way too long (100 characters)
gcc-bootstrap @ 0formatting

Look for formatting issues in the source

line 878 is way too long (100 characters)
elm-sans-reactor @ 0.19.1formatting

Look for formatting issues in the source

line 72 is way too long (98 characters)
brotli @ 1.0.9formatting

Look for formatting issues in the source

line 2160 is way too long (94 characters)
adcli @ 0.9.1formatting

Look for formatting issues in the source

line 97 is way too long (95 characters)
xkbprint @ 1.0.5description

Validate package descriptions

use @code or similar ornament instead of quotes
xkeyboard-config @ 2.34formatting

Look for formatting issues in the source

line 3985 is way too long (102 characters)
busybox @ 1.34.1formatting

Look for formatting issues in the source

line 91 is way too long (92 characters)
texlive-lm @ 59745description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 93
texlive-libkpathsea @ 20210325description

Validate package descriptions

description should start with an upper-case letter or digit
texlive-fonts-latex @ 59745description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 78
texlive-mflogo @ 59745formatting

Look for formatting issues in the source

line 1395 is way too long (95 characters)
chez-scheme-bootstrap-bootfiles @ 9.5.8description

Validate package descriptions

use @code or similar ornament instead of quotes
conda @ 4.10.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
laminar @ 1.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
laminar @ 1.1formatting

Look for formatting issues in the source

line 221 is way too long (97 characters)
laminar @ 1.1formatting

Look for formatting issues in the source

line 223 is way too long (137 characters)
nyxt @ 2.2.4inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile-wm @ 1.0-1.f3c7b3bformatting

Look for formatting issues in the source

line 130 is way too long (92 characters)
openexr @ 2.5.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
blender @ 3.0.1formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
bsd-games @ 2.17.0patch-headers

Validate patch headers

bsd-games-bad-ntohl-cast.patch: patch lacks comment and upstream status
bsd-games @ 2.17.0patch-headers

Validate patch headers

bsd-games-gamescreen.h.patch: patch lacks comment and upstream status
bsd-games @ 2.17.0patch-headers

Validate patch headers

bsd-games-null-check.patch: patch lacks comment and upstream status
cataclysm-dda @ 0.F-3formatting

Look for formatting issues in the source

line 915 is way too long (94 characters)
guile-wiredtiger @ 0.7.0description

Validate package descriptions

use @code or similar ornament instead of quotes
zn-poly @ 0.9.2description

Validate package descriptions

description should start with an upper-case letter or digit
ucsim @ 0.7.1description

Validate package descriptions

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

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinxcontrib-svg2pdfconverter @ 1.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinxcontrib-programoutput @ 0.17inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinxcontrib-github-alt @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-sphinxcontrib-github-alt @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-panels @ 0.6.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-sphinx-panels @ 0.6.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-click @ 4.0.3inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-sphinx-click @ 4.0.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
libmypaint @ 1.6.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-pymol @ 2.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
python-openapi-spec-validator @ 0.4.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
gnupg @ 2.2.32mirror-url

Suggest 'mirror://' URLs

URL should be 'mirror://gnupg/gnupg/gnupg-2.2.32.tar.bz2'
python2-minimal @ 2.7.18patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
ratpoints @ 2.1.3patch-headers

Validate patch headers

ratpoints-sturm_and_rp_private.patch: patch lacks comment and upstream status
ocaml-dose3 @ 5.0.1patch-headers

Validate patch headers

ocaml-dose3-dont-make-printconf.patch: patch lacks comment and upstream status
gourmet @ 0.17.4-0.8af29c8patch-headers

Validate patch headers

gourmet-sqlalchemy-compat.patch: patch lacks comment and upstream status
aegis @ 4.24patch-headers

Validate patch headers

aegis-perl-tempdir2.patch: patch lacks comment and upstream status
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 402, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 404, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 407, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 408, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 417, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 418, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 419, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 420, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 421, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 422, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 423, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 425, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 426, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 427, column 0
patchwork @ 3.0.4formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ocaml-dose3 @ 5.0.1formatting

Look for formatting issues in the source

line 655 is way too long (92 characters)
libgit2 @ 1.4.3formatting

Look for formatting issues in the source

line 795 is way too long (96 characters)
java-xom @ 127formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 508 is way too long (107 characters)
fc-host-tools @ 15formatting

Look for formatting issues in the source

line 1225 is way too long (122 characters)
r-dplyr @ 1.0.9description

Validate package descriptions

description should start with an upper-case letter or digit
r-boot @ 1.3-28description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 125, 142
r-hsmmsinglecell @ 1.16.0formatting

Look for formatting issues in the source

line 1422 is way too long (95 characters)
pbuilder @ 0.231formatting

Look for formatting issues in the source

line 499 is way too long (103 characters)
libgccjit @ 9.5.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
gcc-objc++ @ 9.5.0patch-headers

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
gcc-objc @ 9.5.0patch-headers

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
gcc @ 9.5.0patch-headers

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
onionshare @ 2.4formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
cairo-xcb @ 1.16.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
cairo @ 1.16.0formatting

Look for formatting issues in the source

tabulation on line 167, column 0
cairo @ 1.16.0formatting

Look for formatting issues in the source

tabulation on line 168, column 0
glibc-locales-2.32 @ 2.32patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3338, column 0
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3339, column 0
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3340, column 0
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3341, column 0
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3342, column 0
mesa-opencl-icd @ 21.3.8patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 319 is way too long (120 characters)
mesa @ 21.3.8formatting

Look for formatting issues in the source

line 322 is way too long (110 characters)
libextractor @ 1.11formatting

Look for formatting issues in the source

line 133 is way too long (140 characters)
gnubg @ 1.06.002formatting

Look for formatting issues in the source

line 1848 is way too long (91 characters)
perftest @ 4.4-0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
f2fs-fsck-static @ 1.14.0description

Validate package descriptions

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

Look for formatting issues in the source

line 6337 is way too long (98 characters)
mdadm-static @ 4.2description

Validate package descriptions

description should start with an upper-case letter or digit
libaio @ 0.3.112formatting

Look for formatting issues in the source

line 5325 is way too long (110 characters)
crda @ 3.18formatting

Look for formatting issues in the source

line 4308 is way too long (100 characters)
xwallpaper @ 0.7.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 72
wlsunset @ 0.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
telepathy-mission-control @ 5.16.6inputs-should-be-native

Identify inputs that should be native inputs

'gtk-doc' should probably be a native input
malcontent @ 0.8.0formatting

Look for formatting issues in the source

line 366 is way too long (91 characters)
rcm @ 1.3.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 183
papi @ 6.0.0.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
crun @ 1.4.5formatting

Look for formatting issues in the source

line 78 is way too long (98 characters)
minetest-basic-trains @ 1.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
docbook2x @ 0.8.8inputs-should-be-native

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
cscope @ 15.9description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
python-trezor-agent @ 0.14.4inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' 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
electron-cash @ 4.2.10inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
monero @ 0.17.3.2patch-headers

Validate patch headers

monero-use-system-miniupnpc.patch: patch lacks comment and upstream status
openfoam @ 4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 150 is way too long (91 characters)
cdecl @ 2.5formatting

Look for formatting issues in the source

line 994 is way too long (95 characters)
cdecl @ 2.5formatting

Look for formatting issues in the source

line 995 is way too long (97 characters)
cdecl @ 2.5formatting

Look for formatting issues in the source

line 998 is way too long (93 characters)
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 1947, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1948, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1950, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1951, column 0
openmpi-thread-multiple @ 4.1.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
openmpi-c++ @ 4.1.4patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 263 is way too long (94 characters)
openmpi @ 4.1.4formatting

Look for formatting issues in the source

line 265 is way too long (96 characters)
texlive-latex-tocloft @ 59745description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 173
texlive-latex-l3backend @ 59745description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 124, 199
texlive-latex-cyrillic @ 59745description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 42
libchamplain @ 0.12.20inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' 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
colord-minimal @ 1.4.5inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
emacs-next-pgtk @ 29.0.50-1.0a5477bpatch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-next @ 29.0.50-1.0a5477bpatch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
upower @ 0.99.15formatting

Look for formatting issues in the source

line 5362 is way too long (101 characters)
texlive-stringenc @ 59745formatting

Look for formatting issues in the source

line 3797 is way too long (94 characters)
texlive-stringenc @ 59745formatting

Look for formatting issues in the source

line 3799 is way too long (101 characters)
texlive-stringenc @ 59745formatting

Look for formatting issues in the source

line 3800 is way too long (104 characters)
texlive-stringenc @ 59745formatting

Look for formatting issues in the source

line 3802 is way too long (94 characters)
texlive-stmaryrd @ 59745formatting

Look for formatting issues in the source

line 6859 is way too long (98 characters)
texlive-ruhyphen @ 59745formatting

Look for formatting issues in the source

line 2677 is way too long (92 characters)
texlive-ruhyphen @ 59745formatting

Look for formatting issues in the source

line 2680 is way too long (93 characters)
texlive-pgf @ 59745formatting

Look for formatting issues in the source

line 8437 is way too long (98 characters)
texlive-latex-l3packages @ 59745formatting

Look for formatting issues in the source

line 3641 is way too long (93 characters)
texlive-latex-l3packages @ 59745formatting

Look for formatting issues in the source

line 3650 is way too long (91 characters)
texlive-latex-l3packages @ 59745formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2849, column 22
texlive-hyph-utf8 @ 59745formatting

Look for formatting issues in the source

line 2502 is way too long (108 characters)
texlive-hyph-utf8 @ 59745formatting

Look for formatting issues in the source

line 2503 is way too long (108 characters)
texlive-hyph-utf8 @ 59745formatting

Look for formatting issues in the source

line 2504 is way too long (95 characters)
texlive-hyperref @ 59745formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 980 is way too long (96 characters)
mrrescue @ 1.02edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 2
chroma @ 1.20description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 33
fifengine @ 0.4.2inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
irrlicht-for-minetest @ 1.9.0mt5source-file-name

Validate file names of sources

the source file name should contain the package name
crawl-tiles @ 0.28.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
tuxpaint @ 0.9.23patch-headers

Validate patch headers

tuxpaint-stamps-path.patch: patch lacks comment and upstream status
supertux @ 0.6.3patch-headers

Validate patch headers

supertux-unbundle-squirrel.patch: patch lacks comment and upstream status
pinball @ 0.3.20201218patch-headers

Validate patch headers

pinball-system-ltdl.patch: patch lacks comment and upstream status
gzdoom @ 4.3.2patch-headers

Validate patch headers

gzdoom-find-system-libgme.patch: patch lacks comment and upstream status
einstein @ 2.0formatting

Look for formatting issues in the source

line 4817 is way too long (96 characters)
0ad @ 0.0.25b-alphaformatting

Look for formatting issues in the source

line 6739 is way too long (91 characters)
python-distributed @ 2022.05.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-vedo @ 2022.2.0formatting

Look for formatting issues in the source

line 737 is way too long (124 characters)
python-pyvista @ 0.34.0formatting

Look for formatting issues in the source

line 1216 is way too long (122 characters)
rsyslog @ 8.2204.1formatting

Look for formatting issues in the source

trailing white space on line 268
rsyslog @ 8.2204.1formatting

Look for formatting issues in the source

trailing white space on line 280
abseil-cpp @ 20200923.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 998 is way too long (144 characters)
c-blosc @ 1.21.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
efi_analyzer @ 0.0.0-0.77c9e3aname

Validate package names

name should use hyphens instead of underscores
texlive-fonts-lm @ 59745description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 93
curl-minimal @ 7.79.1description

Validate package descriptions

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-abjad @ 3.4inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
keybinder-3.0 @ 0.3.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
g-golf @ 0.1.0-1010.1824633inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python-trytond @ 6.0.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linphoneqt @ 4.2.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libringclient @ 20211223.2.37be4c3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libring @ 20211223.2.37be4c3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
jami-qt @ 20211223.2.37be4c3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.2-git @ 0.5.2patch-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-git @ 0.5.2patch-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
elm-compiler @ 0.19.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
curl-minimal @ 7.79.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
bazaar @ 3.2.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
guile2.2-git @ 0.5.2patch-headers

Validate patch headers

guile-git-adjust-for-libgit2-1.2.0.patch: patch lacks comment and upstream status
guile2.0-git @ 0.5.2patch-headers

Validate patch headers

guile-git-adjust-for-libgit2-1.2.0.patch: patch lacks comment and upstream status
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@52 and apache-commons-parent-pom@39 collide
maven-slf4j-provider @ 3.8.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide
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
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.8.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@8 and plexus-parent-pom@5.1 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.8.5 and maven-artifact@3.0 collide
maven-resolver-provider @ 3.8.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide
maven-plugin-api @ 3.8.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@25 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-plugin-annotations @ 3.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide
maven-model-builder @ 3.8.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@25 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.8.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@25 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.8.5 and maven-artifact@3.0 collide
maven-filtering @ 3.1.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-plexus-utils@3.3.0 and java-plexus-utils@3.2.1 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.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-artifact@3.8.5 and maven-artifact@3.0 collide
maven-enforcer-plugin @ 3.0.0profile-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.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-embedder @ 3.8.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@8 collide
maven-dependency-tree @ 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-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.8.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-parent-pom@35 and maven-parent-pom@33 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.2.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-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.13.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@52 and apache-commons-parent-pom@39 collide
maven-artifact @ 3.8.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@25 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@52 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@52 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@52 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@52 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
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-slf4j-provider @ 3.8.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-settings-builder @ 3.8.5patch-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.8.5patch-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.8.5patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
maven-compat @ 3.8.5patch-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.8.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-artifact @ 3.8.5patch-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
maven-wagon-http @ 3.4.3formatting

Look for formatting issues in the source

line 1059 is way too long (105 characters)
maven-wagon-http @ 3.4.3formatting

Look for formatting issues in the source

line 1064 is way too long (138 characters)
maven-wagon-http @ 3.4.3formatting

Look for formatting issues in the source

line 1065 is way too long (129 characters)
maven-wagon-file @ 3.4.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 278 is way too long (102 characters)
maven-resolver-transport-http @ 1.6.3formatting

Look for formatting issues in the source

line 377 is way too long (94 characters)
maven-resolver-transport-file @ 1.6.3formatting

Look for formatting issues in the source

line 332 is way too long (94 characters)
maven-resolver-impl @ 1.6.3formatting

Look for formatting issues in the source

line 195 is way too long (92 characters)
maven-resolver-impl @ 1.6.3formatting

Look for formatting issues in the source

line 204 is way too long (92 characters)
maven-resolver-impl @ 1.6.3formatting

Look for formatting issues in the source

line 212 is way too long (95 characters)
maven-resolver-impl @ 1.6.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 163 is way too long (99 characters)
maven-model-builder @ 3.0formatting

Look for formatting issues in the source

line 2412 is way too long (127 characters)
maven-embedder @ 3.8.5formatting

Look for formatting issues in the source

line 1846 is way too long (110 characters)
maven-embedder @ 3.8.5formatting

Look for formatting issues in the source

line 1861 is way too long (116 characters)
maven-compat @ 3.8.5formatting

Look for formatting issues in the source

line 2068 is way too long (109 characters)
maven-common-artifact-filters @ 3.2.0formatting

Look for formatting issues in the source

line 2856 is way too long (124 characters)
java-surefire-booter @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3521 is way too long (107 characters)
java-plexus-archiver @ 4.2.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-container-default @ 2.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
java-plexus-component-metadata @ 2.1.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@13 and apache-parent-pom@25 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-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-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

line 2616 is way too long (99 characters)
java-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

line 2627 is way too long (98 characters)
java-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

line 2666 is way too long (96 characters)
java-openjfx-base @ 8.202formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2571 is way too long (99 characters)
java-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

line 3797 is way too long (112 characters)
icedtea @ 3.19.0formatting

Look for formatting issues in the source

line 1418 is way too long (109 characters)
icedtea @ 3.19.0formatting

Look for formatting issues in the source

line 1464 is way too long (99 characters)
icedtea @ 2.6.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1087 is way too long (100 characters)
guile-f-scm @ 0.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
ublock-origin-chromium @ 1.43.0description

Validate package descriptions

description should start with an upper-case letter or digit
java-plexus-sec-dispatcher @ 2.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@8 collide
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 java-plexus-container-default@1.7.1 and java-plexus-container-default@2.1.0 collide
java-plexus-compiler-manager @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-plexus-container-default@2.1.0 and java-plexus-container-default@1.7.1 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-modello-test @ 1.11profile-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.11profile-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.11profile-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.11profile-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.11profile-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-sec-dispatcher @ 2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 5038 is way too long (107 characters)
java-plexus-component-metadata @ 2.1.0formatting

Look for formatting issues in the source

line 4388 is way too long (110 characters)
java-plexus-component-metadata @ 2.1.0formatting

Look for formatting issues in the source

line 4421 is way too long (95 characters)
java-plexus-component-metadata @ 2.1.0formatting

Look for formatting issues in the source

line 4428 is way too long (146 characters)
java-plexus-component-metadata @ 2.1.0formatting

Look for formatting issues in the source

line 4429 is way too long (151 characters)
java-plexus-component-metadata @ 2.1.0formatting

Look for formatting issues in the source

line 4430 is way too long (149 characters)
java-plexus-component-metadata @ 2.1.0formatting

Look for formatting issues in the source

line 4431 is way too long (141 characters)
java-plexus-component-metadata @ 2.1.0formatting

Look for formatting issues in the source

line 4432 is way too long (161 characters)
java-plexus-component-metadata @ 2.1.0formatting

Look for formatting issues in the source

line 4444 is way too long (138 characters)
java-plexus-component-metadata @ 2.1.0formatting

Look for formatting issues in the source

line 4448 is way too long (103 characters)
java-plexus-component-metadata @ 2.1.0formatting

Look for formatting issues in the source

line 4455 is way too long (114 characters)
java-plexus-component-metadata @ 2.1.0formatting

Look for formatting issues in the source

line 4456 is way too long (108 characters)
java-plexus-component-metadata @ 1.7.1formatting

Look for formatting issues in the source

line 4559 is way too long (114 characters)
java-plexus-component-metadata @ 1.7.1formatting

Look for formatting issues in the source

line 4560 is way too long (108 characters)
java-plexus-compiler-javac @ 2.8.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 5130 is way too long (98 characters)
openssh-sans-x @ 8.9p1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
racket @ 8.5formatting

Look for formatting issues in the source

line 651 is way too long (91 characters)
racket @ 8.5formatting

Look for formatting issues in the source

line 771 is way too long (91 characters)
guile2.2-ssh @ 0.15.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
js-mathjax @ 3.1.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
js-mathjax @ 3.1.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 716 is way too long (99 characters)
r-tidyr @ 1.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
r-minqa @ 1.2.4description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 178
r-datasaurus @ 0.1.6description

Validate package descriptions

use @code or similar ornament instead of quotes
r-cardata @ 3.0-5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 45, 56
xlispstat @ 3.52.23-0.f1bea60formatting

Look for formatting issues in the source

tabulation on line 6952, column 0
xlispstat @ 3.52.23-0.f1bea60formatting

Look for formatting issues in the source

tabulation on line 6953, column 0
xlispstat @ 3.52.23-0.f1bea60formatting

Look for formatting issues in the source

tabulation on line 6954, column 0
xlispstat @ 3.52.23-0.f1bea60formatting

Look for formatting issues in the source

tabulation on line 6955, column 0
xlispstat @ 3.52.23-0.f1bea60formatting

Look for formatting issues in the source

tabulation on line 6957, column 0
xlispstat @ 3.52.23-0.f1bea60formatting

Look for formatting issues in the source

tabulation on line 6958, column 0
xlispstat @ 3.52.23-0.f1bea60formatting

Look for formatting issues in the source

tabulation on line 6959, column 0
r-esc @ 0.5.1formatting

Look for formatting issues in the source

line 6578 is way too long (94 characters)
r-dt @ 0.23formatting

Look for formatting issues in the source

line 3601 is way too long (92 characters)
r-dt @ 0.23formatting

Look for formatting issues in the source

line 3602 is way too long (91 characters)
r-dt @ 0.23formatting

Look for formatting issues in the source

line 3604 is way too long (98 characters)
r-dt @ 0.23formatting

Look for formatting issues in the source

line 3605 is way too long (94 characters)
r-dt @ 0.23formatting

Look for formatting issues in the source

line 3614 is way too long (93 characters)
r-dt @ 0.23formatting

Look for formatting issues in the source

line 3643 is way too long (93 characters)
python-fpylll @ 0.5.7description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
autogen @ 5.18.16formatting

Look for formatting issues in the source

line 70 is way too long (113 characters)
dmraid @ 1.0.0.rc16-3formatting

Look for formatting issues in the source

line 942 is way too long (91 characters)
python-warcio @ 1.7.4-0.aa702cbdescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 90
python-warcio @ 1.7.4-0.aa702cbdescription

Validate package descriptions

description should start with an upper-case letter or digit
python-cloudscraper @ 1.2.58formatting

Look for formatting issues in the source

line 6212 is way too long (96 characters)
template-glib @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
perl-glib-object-introspection @ 0.049inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'flex' should probably be a native input
dbus-verbose @ 1.12.20patch-file-names

Validate file names and availability of patches

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

Validate patch headers

gobject-introspection-girepository.patch: patch lacks comment and upstream status
telepathy-glib @ 0.24.2formatting

Look for formatting issues in the source

line 973 is way too long (92 characters)
appstream-glib @ 0.7.18formatting

Look for formatting issues in the source

line 1134 is way too long (93 characters)
flashrom @ 1.2formatting

Look for formatting issues in the source

line 93 is way too long (91 characters)
flashrom @ 1.2formatting

Look for formatting issues in the source

line 95 is way too long (99 characters)
openjpeg-data @ 2020.11.30description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
libjxr @ 1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
libjxr @ 1.1formatting

Look for formatting issues in the source

line 505 is way too long (95 characters)
ruby_version @ 1.0.2name

Validate package names

name should use hyphens instead of underscores
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
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
qtserialport @ 5.15.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 524 is way too long (94 characters)
python-pyqt @ 5.15.2formatting

Look for formatting issues in the source

line 2092 is way too long (105 characters)
system-config-printer @ 1.5.16inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' 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
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
netsurf @ 3.10patch-headers

Validate patch headers

netsurf-message-timestamp.patch: patch lacks comment and upstream status
wslay @ 1.1.1formatting

Look for formatting issues in the source

line 1555 is way too long (101 characters)
varnish @ 7.0.1formatting

Look for formatting issues in the source

line 5916 is way too long (91 characters)
slurm @ 22.05.1formatting

Look for formatting issues in the source

line 255 is way too long (91 characters)
serf @ 1.3.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 624 is way too long (92 characters)
librsvg @ 2.50.7formatting

Look for formatting issues in the source

line 3429 is way too long (104 characters)
libgnome @ 2.32.1formatting

Look for formatting issues in the source

line 3844 is way too long (110 characters)
krona-tools @ 2.8formatting

Look for formatting issues in the source

trailing white space on line 1299
blasr-libcpp @ 5.3.5formatting

Look for formatting issues in the source

line 661 is way too long (95 characters)
llvm @ 14.0.5patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
lsh @ 2.1patch-headers

Validate patch headers

lsh-fix-x11-forwarding.patch: patch lacks comment and upstream status
rust-async-process @ 1.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
python-argopt @ 0.7.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
rust-async-compression @ 0.3.7formatting

Look for formatting issues in the source

line 4311 is way too long (92 characters)
rust-actix-derive @ 0.5.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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
pan @ 0.149description

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
tor @ 0.4.7.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 574
coq-stdlib @ 8.15.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
coq-ide-server @ 8.15.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
coq-ide @ 8.15.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
coq-core @ 8.15.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
maven-wagon-provider-api @ 3.4.3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/d04y4sr3ibjbaapijhac3x35si7ik7kn-maven-wagon-provider-api-3.4.3 and /gnu/store/bi1y5dx0pz68bs87283iq9mqcr1xh4af-maven-wagon-provider-api-3.4.3 collide
java-commons-lang3 @ 3.12.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 7504, column 20
java-eclipse-jdt-core @ 3.16.0formatting

Look for formatting issues in the source

line 7562 is way too long (98 characters)
java-commons-jxpath @ 1.3formatting

Look for formatting issues in the source

line 6341 is way too long (93 characters)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

line 6108 is way too long (91 characters)
ocaml4.07-cmdliner @ 1.0.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 304
ocaml-sedlex @ 2.5formatting

Look for formatting issues in the source

line 2877 is way too long (97 characters)
go-sigs-k8s-io-yaml @ 1.3.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 181
go-github-com-songmu-gitconfig @ 0.1.0description

Validate package descriptions

description should start with an upper-case letter or digit
go-github-com-muesli-termenv @ 0.8.1description

Validate package descriptions

description should start with an upper-case letter or digit
go-github-com-mitchellh-reflectwalk @ 1.0.1description

Validate package descriptions

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

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
go-github-com-mesilliac-pulse-simple @ 0.0.0-0.75ac54einputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
go-gopkg-in-yaml-v2 @ 2.4.0formatting

Look for formatting issues in the source

line 4074 is way too long (104 characters)
go-gopkg-in-djherbis-times-v1 @ 1.5.0formatting

Look for formatting issues in the source

line 9043 is way too long (91 characters)
go-github-com-rogpeppe-go-internal @ 1.6.1formatting

Look for formatting issues in the source

line 8137 is way too long (101 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1007 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1008 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1009 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1010 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1011 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1012 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1013 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1014 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1019 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1020 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1029 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1030 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1032 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1033 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1034 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1035 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1036 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1037 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1039 is way too long (97 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1040 is way too long (97 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1042 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1044 is way too long (92 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1045 is way too long (92 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1046 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1047 is way too long (97 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1057 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1058 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1059 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1060 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1061 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1062 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1063 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1064 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1069 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1070 is way too long (98 characters)
go-github-com-mitchellh-go-homedir @ 1.0.0-0.ae18d6bformatting

Look for formatting issues in the source

line 5017 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-gorilla-context @ 0.0.0-0.08b5f42formatting

Look for formatting issues in the source

line 3314 is way too long (164 characters)
go-github-com-davecgh-go-spew @ 1.1.1formatting

Look for formatting issues in the source

line 4587 is way too long (129 characters)
libvirt-glib @ 4.0.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
virt-manager @ 3.2.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
criu @ 3.17formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
java-commons-text @ 1.9profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@51 collide
libdqlite @ 1.9.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 70
drumstick @ 2.3.1inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
abjad @ 3.4inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
abjad @ 3.4inputs-should-be-native

Identify inputs that should be native inputs

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 2968 is way too long (91 characters)
solfege @ 3.23.5pre2formatting

Look for formatting issues in the source

line 2067 is way too long (94 characters)
drumstick @ 2.3.1formatting

Look for formatting issues in the source

line 2924 is way too long (91 characters)
tuxmath @ 2.0.3description

Validate package descriptions

description should start with an upper-case letter or digit
xtensor-benchmark @ 0.24.0description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 798
eigen-benchmarks @ 3.3.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
symmetrica @ 2.0patch-headers

Validate patch headers

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

Look for formatting issues in the source

line 1520 is way too long (100 characters)
giac @ 1.7.0-51formatting

Look for formatting issues in the source

line 335 is way too long (95 characters)
gap @ 4.11.0formatting

Look for formatting issues in the source

line 1257 is way too long (98 characters)
python-pytest-subtesthack @ 0.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 106
python-pytest-freezegun @ 0.4.2description

Validate package descriptions

description contains typo 'allows to'
python-flexmock @ 0.10.4description

Validate package descriptions

description should start with an upper-case letter or digit
python-testtools @ 2.5.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-xprocess @ 0.18.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-xdist @ 2.5.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-timeout @ 2.0.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-timeout @ 2.0.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-subtesthack @ 0.1.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-randomly @ 3.11.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-random-order @ 1.0.4inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-mypy @ 0.9.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-mock @ 3.6.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-freezegun @ 0.4.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-dependency @ 0.5.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-capturelog @ 0.7inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-cache @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-assume @ 2.4.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-nose-timer @ 0.7.5inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-hypothesis @ 6.43.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-coverage-test-runner @ 1.15inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' 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-django-auth-ldap @ 4.1.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-pip' should probably not be an input at all
python-fixtures-bootstrap @ 3.0.0patch-file-names

Validate file names and availability of patches

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

Validate patch headers

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

Validate package names

name should use hyphens instead of underscores
python-requests-unixsocket @ 0.2.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
awscli @ 1.22.90inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
awscli @ 1.22.90inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-urlgrabber @ 4.1.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-flask-migrate @ 3.1.0source-file-name

Validate file names of sources

the source file name should contain the package name
python-tornado @ 5.1.1formatting

Look for formatting issues in the source

line 2038 is way too long (91 characters)
emacs-erlang @ 25.0.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

file names of patches should start with the package name
lepton-eda @ 1.9.14-20210407inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
geda-gaf @ 1.10.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'libtool' should probably be a native input
prusa-slicer @ 2.4.2formatting

Look for formatting issues in the source

line 3205 is way too long (94 characters)
libigl @ 2.3.0formatting

Look for formatting issues in the source

line 3063 is way too long (91 characters)
libigl @ 2.3.0formatting

Look for formatting issues in the source

line 3064 is way too long (101 characters)
libigl @ 2.3.0formatting

Look for formatting issues in the source

line 3091 is way too long (94 characters)
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2015 is way too long (101 characters)
localed @ 241formatting

Look for formatting issues in the source

line 862 is way too long (96 characters)
sh-z @ 1.11description

Validate package descriptions

use @code or similar ornament instead of quotes
ecryptfs-utils @ 111description

Validate package descriptions

description should start with an upper-case letter or digit
python-sphinx-sitemap @ 2.2.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-sphinx-rtd-theme @ 1.0.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-cloud-sptheme @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-autodoc-typehints @ 1.18.3inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-autobuild @ 2021.3.14inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-argparse @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-pydata-sphinx-theme @ 0.7.2inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-pydata-sphinx-theme @ 0.7.2inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-nbsphinx @ 0.8.8inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-nbsphinx @ 0.8.8inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-breathe @ 4.34.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
jucipp @ 1.7.1description

Validate package descriptions

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
xen @ 4.14.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
xsimd-benchmark @ 8.1.0description

Validate package descriptions

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

Validate package descriptions

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

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
python-pyopenssl @ 21.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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-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-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-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-eclipse-sisu-plexus @ 0.3.5profile-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 @ 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

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
java-powermock-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-antlr4-runtime-cpp @ 4.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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 10994 is way too long (91 characters)
java-ops4j-pax-exam-core-spi @ 4.11.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9680 is way too long (110 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

line 12858 is way too long (92 characters)
java-native-access @ 4.5.1formatting

Look for formatting issues in the source

line 13036 is way too long (91 characters)
java-logback-classic @ 1.2.3formatting

Look for formatting issues in the source

line 13605 is way too long (102 characters)
java-joda-time @ 2.9.9formatting

Look for formatting issues in the source

line 12438 is way too long (92 characters)
java-jnacl @ 0.1.0-2.094e819formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 11081 is way too long (92 characters)
java-jgit @ 4.2.0.201601211800-rformatting

Look for formatting issues in the source

line 13705 is way too long (93 characters)
java-jansi @ 2.4.0formatting

Look for formatting issues in the source

line 12212 is way too long (94 characters)
java-hawtjni @ 1.15formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10091 is way too long (93 characters)
java-eclipse-sisu-plexus @ 0.3.5formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 13429 is way too long (95 characters)
java-commons-httpclient @ 3.1formatting

Look for formatting issues in the source

line 12898 is way too long (91 characters)
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

line 9865 is way too long (91 characters)
java-apache-ivy @ 2.4.0formatting

Look for formatting issues in the source

line 13247 is way too long (101 characters)
antlr4 @ 4.8formatting

Look for formatting issues in the source

line 8737 is way too long (96 characters)
antlr4 @ 4.8formatting

Look for formatting issues in the source

line 8811 is way too long (100 characters)
maven-doxia-core @ 2.0.0-M2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
xblackjack @ 2.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
sky @ 1.2description

Validate package descriptions

use @code or similar ornament instead of quotes
passage @ 4description

Validate package descriptions

use @code or similar ornament instead of quotes
sky @ 1.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10010 is way too long (100 characters)
queen-it @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9818 is way too long (205 characters)
queen-fr @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9818 is way too long (205 characters)
queen @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9720 is way too long (93 characters)
lure-fr @ 1.1formatting

Look for formatting issues in the source

line 9720 is way too long (93 characters)
lure-es @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9720 is way too long (93 characters)
lure @ 1.1formatting

Look for formatting issues in the source

line 9720 is way too long (93 characters)
freeorion @ 0.4.10.2formatting

Look for formatting issues in the source

line 10095 is way too long (92 characters)
drascula @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9623 is way too long (93 characters)
btanks @ 0.9.8083formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 8642, column 18
btanks @ 0.9.8083formatting

Look for formatting issues in the source

tabulation on line 8643, column 17
guile2.2-sjson @ 0.2.2description

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-email-latest @ 0.2.2-2.ea60bb9description

Validate package descriptions

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

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.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile2.2-g-golf @ 0.1.0-1010.1824633inputs-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.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile-g-golf @ 0.1.0-1010.1824633inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile2.2-fibers @ 1.1.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
guile-dbd-postgresql @ 2.1.8formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
guile-dbd-mysql @ 2.1.8formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
guile-avahi @ 0.4.0-1.6d43cafformatting

Look for formatting issues in the source

line 4334 is way too long (92 characters)
gnome-shell-extension-gsconnect @ 48inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
libstdc++-doc @ 9.5.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
cfitsio @ 3.49description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 197
python-flit-scm @ 1.6.2inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' 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
astroid @ 0.16inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile2.2-mailutils @ 3.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-statmake @ 0.5.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 275, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 276, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 277, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 278, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 279, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 280, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 281, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 282, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 283, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 286, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 287, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 289, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 290, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 291, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 292, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 293, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 295, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 296, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 297, column 0
libarchive @ 3.5.1formatting

Look for formatting issues in the source

tabulation on line 298, column 0
i3-wm @ 4.20.1description

Validate package descriptions

description should start with an upper-case letter or digit
keybinder @ 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
i3-gaps @ 4.20.1source-file-name

Validate file names of sources

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

Validate file names and availability of patches

file names of patches should start with the package name
icecat @ 91.11.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 769 is way too long (140 characters)
icecat @ 91.11.0-guix0-preview1formatting

Look for formatting issues in the source

line 775 is way too long (96 characters)
icecat @ 91.11.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 813 is way too long (93 characters)
icecat @ 91.11.0-guix0-preview1formatting

Look for formatting issues in the source

line 815 is way too long (94 characters)
icecat @ 91.11.0-guix0-preview1formatting

Look for formatting issues in the source

line 821 is way too long (99 characters)
libcpuid @ 0.5.1-1.2e61160description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 113
h-client @ 0.0a0-1.e6c78b1inputs-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
tensorflow @ 1.9.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-cmaes @ 0.8.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-keras @ 2.2.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-pyparsing@2.4.7 and python-pyparsing@3.0.6 collide
python-xgboost @ 1.5.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1848 is way too long (96 characters)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1869 is way too long (105 characters)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1871 is way too long (98 characters)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1872 is way too long (99 characters)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1873 is way too long (99 characters)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1874 is way too long (103 characters)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2038 is way too long (137 characters)
shogun @ 6.1.3formatting

Look for formatting issues in the source

line 692 is way too long (91 characters)
guile-aiscm @ 0.23.1formatting

Look for formatting issues in the source

line 330 is way too long (114 characters)
rocm-bandwidth-test @ 5.1.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 122
python-clang @ 13.0.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python-clang @ 10.0.1patch-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
lld @ 14.0.5patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
vim-full @ 9.0.0000formatting

Look for formatting issues in the source

line 219 is way too long (98 characters)
icedove @ 91.11.0formatting

Look for formatting issues in the source

line 1007 is way too long (98 characters)
icedove @ 91.11.0formatting

Look for formatting issues in the source

line 1159 is way too long (105 characters)
icedove @ 91.11.0formatting

Look for formatting issues in the source

line 1161 is way too long (102 characters)
rtl-sdr @ 0.6.0-1.5e73f90description

Validate package descriptions

use @code or similar ornament instead of quotes
hackrf @ 2021.03.1description

Validate package descriptions

use @code or similar ornament instead of quotes
sbcl @ 2.2.6formatting

Look for formatting issues in the source

tabulation on line 547, column 18
r-biomart @ 2.52.0description

Validate package descriptions

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

Look for formatting issues in the source

line 2586 is way too long (109 characters)
r-biocparallel @ 1.30.3formatting

Look for formatting issues in the source

line 3381 is way too long (95 characters)
python-html2text @ 2020.1.16description

Validate package descriptions

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

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-praw @ 7.5.0formatting

Look for formatting issues in the source

line 238 is way too long (93 characters)
python-praw @ 7.5.0formatting

Look for formatting issues in the source

line 239 is way too long (105 characters)
wpa-supplicant-minimal @ 2.10description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
greetd-pam-mount @ 2.18description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 358
linux-pam @ 1.5.1formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
musikcube @ 0.96.10formatting

Look for formatting issues in the source

line 6725 is way too long (99 characters)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5523, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5524, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5525, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5526, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5528, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5535, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5536, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5537, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

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

Validate package descriptions

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

line 393 is way too long (93 characters)
mosquitto @ 1.6.12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 347
quaternion @ 0.0.9.4finputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
python-librecaptcha @ 0.7.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
poezio @ 0.13.2inputs-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.4.5inputs-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.4.5patch-headers

Validate patch headers

gajim-honour-GAJIM_PLUGIN_PATH.patch: patch lacks comment and upstream status
python-librecaptcha @ 0.7.3formatting

Look for formatting issues in the source

line 3391 is way too long (101 characters)
psi-plus @ 1.5.1484formatting

Look for formatting issues in the source

line 2980 is way too long (96 characters)
mtxclient @ 0.7.0formatting

Look for formatting issues in the source

line 2357 is way too long (98 characters)
python-psycopg2 @ 2.9.3description

Validate package descriptions

description should start with an upper-case letter or digit
python-sphinxcontrib-asyncio @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
sqlcipher @ 3.4.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-psycopg @ 3.0.8formatting

Look for formatting issues in the source

tabulation on line 3730, column 0
mariadb @ 10.5.12formatting

Look for formatting issues in the source

trailing white space on line 957
java-xpp3 @ 1.1.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 188
python-fiona @ 1.8.20inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
proj.4 @ 4.9.3formatting

Look for formatting issues in the source

line 607 is way too long (92 characters)
font-bravura @ 1.393description

Validate package descriptions

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

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
python-renpy @ 8.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
warsow-qfusion @ 2.5-1.c4de15dpatch-headers

Validate patch headers

warsow-qfusion-fix-bool-return-type.patch: patch lacks comment and upstream status
godot @ 3.4.2formatting

Look for formatting issues in the source

line 1859 is way too long (92 characters)
godot @ 3.4.2formatting

Look for formatting issues in the source

line 1862 is way too long (97 characters)
font-canada1500 @ 1.101formatting

Look for formatting issues in the source

line 217 is way too long (91 characters)
font-adobe-source-code-pro @ 2.032R-ro-1.052R-it-1.012R-VARformatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
tbb @ 2021.5.0patch-headers

Validate patch headers

tbb-other-arches.patch: patch lacks comment and upstream status
lpsolve @ 5.5.2.5description

Validate package descriptions

description should start with an upper-case letter or dig