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
java-jblas @ 1.2.4description

Validate package descriptions

description should start with an upper-case letter or digit
presentty @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' 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
cinnamon-desktop @ 3.4.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libcanberra-gtk2 @ 0.30patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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)
presentty @ 0.2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 152 is way too long (92 characters)
ghc @ 8.6.5formatting

Look for formatting issues in the source

line 591 is way too long (91 characters)
python-pytest-httpbin @ 0.2.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
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
tesseract-ocr @ 4.1.1-1.97079faformatting

Look for formatting issues in the source

line 121 is way too long (93 characters)
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
python-bcj-cffi @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-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
python-jupyter-packaging @ 0.9.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
wicd @ 1.7.4formatting

Look for formatting issues in the source

line 109 is way too long (95 characters)
netpbm @ 10.78.3formatting

Look for formatting issues in the source

line 86 is way too long (127 characters)
libextractor @ 1.11formatting

Look for formatting issues in the source

line 128 is way too long (140 characters)
dico @ 2.11inputs-should-be-native

Identify inputs that should be native inputs

'm4' 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
axoloti-runtime @ 1.0.12-2formatting

Look for formatting issues in the source

line 197 is way too long (96 characters)
cryptsetup-static @ 2.3.6formatting

Look for formatting issues in the source

line 110 is way too long (93 characters)
flite @ 2.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 104 is way too long (93 characters)
vtk @ 9.0.1formatting

Look for formatting issues in the source

line 299 is way too long (93 characters)
vtk @ 9.0.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
connman @ 1.40description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
python-pyqt @ 5.15.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gtklick @ 0.6.4formatting

Look for formatting issues in the source

line 1298 is way too long (94 characters)
rtl-sdr @ 0.6.0description

Validate package descriptions

use @code or similar ornament instead of quotes
proj.4 @ 4.9.3formatting

Look for formatting issues in the source

line 573 is way too long (92 characters)
r-abps @ 0.3formatting

Look for formatting issues in the source

line 10326 is way too long (93 characters)
gramps @ 5.1.4inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
eigen @ 3.3.8formatting

Look for formatting issues in the source

tabulation on line 1026, column 0
ghc-optparse-applicative @ 0.15.1.0formatting

Look for formatting issues in the source

line 178 is way too long (95 characters)
elm-compiler @ 0.19.0formatting

Look for formatting issues in the source

line 58 is way too long (97 characters)
python-xsge @ 2020.09.07description

Validate package descriptions

description should start with an upper-case letter or digit
cloudflare-cli @ 0.0.0-1.2d986d3formatting

Look for formatting issues in the source

line 122 is way too long (92 characters)
elixir @ 1.12.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 77 is way too long (99 characters)
dejagnu @ 1.6.2formatting

Look for formatting issues in the source

line 60 is way too long (91 characters)
ensembl-vep @ 103.1formatting

Look for formatting issues in the source

line 14942 is way too long (92 characters)
ensembl-vep @ 103.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1289 is way too long (98 characters)
purescript @ 0.14.5formatting

Look for formatting issues in the source

line 121 is way too long (92 characters)
python-tornado @ 5.1.1formatting

Look for formatting issues in the source

line 1731 is way too long (91 characters)
julia-compilersupportlibraries-jll @ 0.4.0+1description

Validate package descriptions

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

Look for formatting issues in the source

line 157 is way too long (91 characters)
ocaml-ounit @ 2.2.4formatting

Look for formatting issues in the source

line 1371 is way too long (97 characters)
cataclysm-dda @ 0.F-3formatting

Look for formatting issues in the source

line 910 is way too long (94 characters)
python-readability @ 0.3.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 140
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
swi-prolog @ 8.3.20tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
lean @ 3.23.0tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
belcard @ 4.4.34tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
wordnet @ 3.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
windowmaker @ 0.95.9wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
syncthing-gtk @ 0.9.4.4-1.c46fbd8wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ronn-ng @ 0.9.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
roffit @ 0.12-1.b59e6c855wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
rednotebook @ 2.22wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
presentty @ 0.2.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
patchutils @ 0.4.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
npiet @ 1.3fwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
nicotine+ @ 2.1.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
keepassxc @ 2.6.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
kdenlive @ 21.08.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
kawa @ 3.1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
icon-naming-utils @ 0.8.90wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gtg @ 0.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gramps @ 5.1.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
execline @ 2.8.1.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
econnman @ 1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cozy @ 1.1.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
calibre @ 5.21.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
artanis @ 0.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ark @ 20.04.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
arcanist @ 0.0.0-2.ceb082ewrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
arandr @ 0.1.10wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python2-ecdsa @ 0.14.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-mpl @ 0.11optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-leather @ 0.3.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-ecdsa @ 0.14.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-agate-sql @ 0.5.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-agate-excel @ 0.2.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-agate-dbf @ 0.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-agate @ 1.6.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
java-iq80-snappy @ 0.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
dico @ 2.11optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
dejagnu @ 1.6.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
date @ 2.4.1-9a0ee254optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
crossguid @ 0.0-2.fef89a4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bcunit @ 3.0.2-0.74021ccoptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bctoolbox @ 4.4.34optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
armips @ 0.11.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
anthy @ 9100hoptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mono @ 4.4.1.0patch-headers

Validate patch headers

mono-mdoc-timestamping.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
cyrus-sasl @ 2.1.27patch-headers

Validate patch headers

cyrus-sasl-ac-try-run-fix.patch: patch lacks comment and upstream status
r-boot @ 1.3-28description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 125, 142
python-priority @ 1.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby_version @ 1.0.2name

Validate package names

name should use hyphens instead of underscores
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
yt-dlp @ 2021.10.22tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ruby-yard-with-tests @ 0.9.25tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ruby-ffi-rzmq @ 2.0.7tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
libicns @ 0.8.1tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ldc @ 1.27.1tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
julia-arrayinterface @ 3.1.19tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ghc-statistics @ 0.15.2.0tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ghc-bsb-http-chunked @ 0.0.0.4tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
extra-cmake-modules @ 5.70.0tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
emacs-sudo-edit @ 0.1.1tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
emacs-elisp-demos @ 2020.02.19tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
emacs-deferred @ 0.5.1tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
emacs-company-lsp @ 2.1.0tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ecl @ 21.2.1tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
ecl @ 16.1.3tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
zn-poly @ 0.9.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
wxwidgets-gtk2 @ 3.1.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
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-latex-l3backend @ 59745description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 124, 199
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-latex @ 59745description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
rust-avif-serialize @ 0.6.5description

Validate package descriptions

use @code or similar ornament instead of quotes
ruby-rb-inotify @ 0.9.10description

Validate package descriptions

description should start with an upper-case letter or digit
rocm-bandwidth-test @ 4.3.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 122
robin-map @ 0.6.3description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 183
r-dplyr @ 1.0.7description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 106
python2-flexmock @ 0.10.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
python-pytest-subtesthack @ 0.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 106
python-libfreenect @ 0.6.2description

Validate package descriptions

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

Validate package descriptions

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

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
openmpi-thread-multiple @ 4.1.1description

Validate package descriptions

description contains leading whitespace
openjpeg-data @ 2020.11.30description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
minetest-basic-trains @ 1.0.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
libdqlite @ 1.9.0description

Validate package descriptions

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

Validate package descriptions

description contains leading whitespace
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
jucipp @ 1.6.3description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
hackrf @ 2021.03.1description

Validate package descriptions

use @code or similar ornament instead of quotes
guile2.2-sjson @ 0.2.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
ghc-llvm-hs-pure @ 9.0.0description

Validate package descriptions

description should start with an upper-case letter or digit
ghc-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-hxt-unicode @ 9.0.2.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 158
ghc-hsyaml @ 0.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-doctest-lib @ 0.1description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ghc-crypto-cipher-tests @ 0.0.11description

Validate package descriptions

description contains leading whitespace
ghc-commonmark @ 0.2.1.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 236
espeak-ng @ 1.50description

Validate package descriptions

description should start with an upper-case letter or digit
config @ 0.0.0-1.c8ddc84description

Validate package descriptions

use @code or similar ornament instead of quotes
yelp-tools @ 3.32.2inputs-should-be-native

Identify inputs that should be native inputs

'itstool' should probably be a native input
thunar @ 4.16.10inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-docutils' should probably be a native input
python2-pytest-xdist @ 2.1.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-warnings @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-subtesthack @ 0.1.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-mock @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-mock' should probably be a native input
python2-pytest-mock @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-catchlog @ 1.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-capturelog @ 0.7inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pytest-cache @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
python2-pygobject @ 3.40.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
python2-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python2-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pytest-cov' should probably be a native input
python2-nose-timer @ 0.7.5inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-docutils' should probably be a native input
python2-coverage-test-runner @ 1.15inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python2-cov-core @ 1.15.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
python-trezor-agent @ 0.14.4inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
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-sphinx @ 4.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' 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.3.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 @ 1.4.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-timeout @ 1.4.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-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-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-dependency @ 0.5.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
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-pytest-csv @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-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-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-pygobject @ 3.40.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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
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-nose2 @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-fixtures @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-coveralls @ 3.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' 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
perl-glib-object-introspection @ 0.049inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'flex' should probably be a native input
mig @ 1.8inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'doxygen' should probably be a native input
mate-polkit @ 1.24.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
ibus-anthy @ 1.5.9inputs-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
gjs @ 1.70.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
fcitx-qt5 @ 1.2.6inputs-should-be-native

Identify inputs that should be native inputs

'intltool' should probably be a native input
docbook2x @ 0.8.8inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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
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-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
zeal @ 0.6.1-1.d3c5521wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
youtube-viewer @ 3.8.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
xorriso @ 1.5.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wgetpaste @ 2.32wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
virt-viewer @ 7.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
vapoursynth @ 53wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
units @ 2.21wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
translate-shell @ 0.9.6.12wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
synfigstudio @ 1.2.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
srt2vtt @ 0.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
spice-gtk @ 0.37wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
sawfish @ 1.12.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
remind @ 3.3.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
redshift @ 1.12wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
rapid-photo-downloader @ 0.9.18wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
raincat @ 1.2.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
quilt @ 0.66wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
piet-toolchain @ 0.0.0-0.f002ff6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
pencil2d @ 0.6.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
papagayo @ 2.0b1-1.e143684b3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ocrodjvu @ 0.12wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
obs @ 27.0.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
meld @ 3.20.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
lxqt-session @ 0.17.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
luakit @ 2.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
kristall @ 0.3-1.204b08awrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
julia @ 1.6.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
jucipp @ 1.6.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
itstool @ 2.0.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
inkscape @ 1.1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ibus-libpinyin @ 1.12.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ibus-libhangul @ 1.5.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ibus-anthy @ 1.5.9wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ibus @ 1.5.24wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
guile2.2-dsv @ 0.5.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
guile-wm @ 1.0-1.f3c7b3bwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
guile-dsv @ 0.5.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gpsd @ 3.23.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gobject-introspection @ 1.66.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

invalid phase clause
gnuradio @ 3.9.2.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnucash @ 4.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnome-shell @ 41.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnome-session @ 40.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gitolite @ 3.6.12wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gitless @ 0.8.8wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gitile @ 0.1.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
git @ 2.34.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
giara @ 0.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ghostwriter @ 2.0.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gedit @ 40.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
foo2zjs @ 20200610.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
fontforge @ 20201107wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
fntsample @ 5.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-wide-int @ 27.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-next-pgtk @ 28.0.50-1.ae18c8ewrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-next @ 28.0.50-0.2ea3466wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs @ 27.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ecl @ 21.2.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ecl @ 16.1.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
dvdstyler @ 3.0.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
didjvu @ 0.9wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
debootstrap @ 1.0.126wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
dblatex @ 0.3.12wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
d-feet @ 0.3.14wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cups-filters @ 1.28.9wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cgit @ 1.2.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cdemu-client @ 3.2.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cawbird @ 1.4.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
catfish @ 4.16.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
caribou @ 0.4.21wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
byobu @ 5.133wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
asunder @ 2.9.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
arcan-sdl @ 0.5.5.2-1.b4dd1fbwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
arcan @ 0.5.5.2-1.b4dd1fbwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
abcde @ 2.9.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
389-ds-base @ 1.4.4.17wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
zsh-autosuggestions @ 0.7.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
xlsx2csv @ 0.7.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
uthash @ 2.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
unshield @ 1.4.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
tng @ 1.8.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
tinyxml @ 2.6.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
syslinux @ 6.04-pre-1.bb41e93optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
stgit @ 1.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
solidity @ 0.7.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
solid @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-yell @ 2.2.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-yard-tomdoc @ 0.7.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-turn @ 0.9.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-thor @ 1.0.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-spectroscope @ 0.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-shoulda-matchers @ 3.1.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-shoulda-matchers @ 2.8.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-shoulda-context @ 1.2.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-shoulda @ 3.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-rubytest @ 0.8.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-rspec-wait @ 0.0.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-rc4 @ 0.1.5optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-rack-test @ 0.8.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-qed @ 2.9.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-protobuf @ 3.10.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-permutation @ 0.1.8optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-pdf-inspector @ 1.3.0-1.00ee4c9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-netrc @ 0.11.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-minitest-pretty-diff @ 0.1-1.11f32e93optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-lemon @ 0.9.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-hydra @ 0.0-0.5abfa37optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-htmlentities @ 4.3.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-hashery @ 2.1.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-ffi-rzmq-core @ 1.0.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-ffi-rzmq @ 2.0.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-debug-inspector @ 0.0.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-cucumber-messages @ 12.2.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-cucumber-html-formatter @ 7.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-cucumber-create-meta @ 1.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-brass @ 1.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-blankslate @ 3.1.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-bio-commandeer @ 0.4.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-awesome-print @ 1.8.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-ansi @ 1.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-ae @ 1.8.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ruby-activesupport @ 6.1.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
robin-map @ 0.6.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
rnp @ 0.13.1-0.203224foptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-unittest2 @ 1.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-pytest-cov @ 2.8.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-hidapi @ 0.7.99.post21optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-freezegun @ 0.3.14optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-coverage-test-runner @ 1.15optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-cffi @ 1.14.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-unittest2 @ 1.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-testscenarios-bootstrap @ 0.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-testscenarios @ 0.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-timeout @ 1.4.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-localserver @ 0.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-lazy-fixture @ 0.6.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-httpserver @ 1.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-cov @ 2.8.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pyhamcrest @ 2.0.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pure-protobuf @ 2.0.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-podcastparser @ 0.6.6optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-mygpoclient @ 1.8optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-meshio @ 4.4.6optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-locust @ 1.4.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-lit @ 12.0.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-libtmux @ 0.10.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-junit-xml @ 1.9-0.4bd08a2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-hidapi @ 0.7.99.post21optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-gitdb @ 4.0.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-freezegun @ 0.3.14optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-fenics-ufl @ 2019.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-fenics-fiat @ 2019.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-fenics-ffc @ 2019.1.0.post0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-fenics-dijitso @ 2019.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-daemux @ 0.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-coverage-test-runner @ 1.15optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-cffi @ 1.14.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
perl6-zef @ 0.6.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
perl6-tap-harness @ 0.0.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ninja @ 1.10.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
networkmanager-qt @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
modemmanager-qt @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
lodepng @ 20200215-1.48e5364optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libksysguard @ 5.19.5optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libcyaml @ 1.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libavif @ 0.9.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
kwindowsystem @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
krunner @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
knotifications @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
kdbusaddons @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
kconfig @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
kauth @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
gnurl @ 7.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
gnuradio @ 3.9.2.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ghc-wai-cors @ 0.2.7optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
genimage @ 14-1.11bb044optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
fullswof-2d @ 1.09.01optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
fenics-dolfin @ 2019.1.0.post0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
fenics @ 2019.1.0.post0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
emacs-ledger-mode @ 4.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
eigen @ 3.3.8optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
dvdisaster @ 0.79.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
docker @ 19.03.15optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
coq-interval @ 4.3.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
coq-flocq @ 3.4.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
coq-coquelicot @ 3.2.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
clitest @ 0.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
cedille @ 1.1.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bcg729 @ 1.1.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
baloo @ 5.70.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
attr @ 2.5.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
rdmd @ 2.077.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
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.68.0 and glibmm@2.64.5 collide
libxml++ @ 3.2.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs libsigc++@2.9.3 and libsigc++@3.0.6 collide
libxml++ @ 2.40.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs libsigc++@2.9.3 and libsigc++@3.0.6 collide
glibmm @ 2.64.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs libsigc++@2.9.3 and libsigc++@3.0.6 collide
u-boot-wandboard @ 2021.10patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-novena @ 2021.10patch-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 @ 2021.10patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-a20-olinuxino-lime @ 2021.10patch-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-unittest2 @ 1.1.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python2-libxml2 @ 2.9.12patch-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
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-packaging-bootstrap @ 20.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
polkit-duktape @ 0.120patch-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
openmpi-thread-multiple @ 4.1.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
mesa-headers @ 21.2.5patch-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
libmhash @ 0.9.9.9patch-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
java-openmpi @ 4.1.1patch-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-gnutls @ 3.7.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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
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
grub-minimal @ 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
gnutls-dane @ 3.7.2patch-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
emacs-xwidgets @ 27.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
emacs-next @ 28.0.50-0.2ea3466patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
coreutils-minimal @ 8.32patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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
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-next @ 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-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
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
tcsh @ 6.22.03patch-headers

Validate patch headers

tcsh-fix-autotest.patch: patch lacks comment and upstream status
t1lib @ 5.1.2patch-headers

Validate patch headers

t1lib-CVE-2010-2642.patch: patch lacks comment and upstream status
steghide @ 0.5.1patch-headers

Validate patch headers

steghide-fixes.patch: patch lacks comment and upstream status
sdl-pango @ 0.1.2patch-headers

Validate patch headers

sdl-pango-header-guard.patch: patch lacks comment and upstream status
ratpoints @ 2.1.3patch-headers

Validate patch headers

ratpoints-sturm_and_rp_private.patch: patch lacks comment and upstream status
python2-unittest2 @ 1.1.0patch-headers

Validate patch headers

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

Validate patch headers

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

Validate patch headers

p7zip-remove-unused-code.patch: patch lacks comment and upstream status
monero @ 0.17.3.0patch-headers

Validate patch headers

monero-use-system-miniupnpc.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
kpackage @ 5.70.0patch-headers

Validate patch headers

kpackage-allow-external-paths.patch: patch lacks comment and upstream status
gobject-introspection @ 1.66.1patch-headers

Validate patch headers

gobject-introspection-girepository.patch: patch lacks comment and upstream status
genimage @ 14-1.11bb044patch-headers

Validate patch headers

genimage-mke2fs-test.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
xfce4-clipman-plugin @ 1.6.2formatting

Look for formatting issues in the source

line 475 is way too long (91 characters)
u-boot-wandboard @ 2021.10formatting

Look for formatting issues in the source

line 726 is way too long (93 characters)
u-boot-tools @ 2021.10formatting

Look for formatting issues in the source

line 605 is way too long (108 characters)
u-boot-tools @ 2021.10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 726 is way too long (93 characters)
u-boot-pinebook @ 2021.10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 726 is way too long (93 characters)
u-boot-malta @ 2021.10formatting

Look for formatting issues in the source

line 726 is way too long (93 characters)
u-boot-cubietruck @ 2021.10formatting

Look for formatting issues in the source

line 726 is way too long (93 characters)
u-boot-cubieboard @ 2021.10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 726 is way too long (93 characters)
tumbler @ 4.16.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
tmux-themepack @ 1.1.0formatting

Look for formatting issues in the source

line 93 is way too long (95 characters)
texlive-stringenc @ 59745formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3605 is way too long (94 characters)
texlive-ruhyphen @ 59745formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2572 is way too long (93 characters)
texlive-mflogo @ 59745formatting

Look for formatting issues in the source

line 1223 is way too long (95 characters)
texlive-latex-l3packages @ 59745formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3453 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 2676, column 22
texlive-hyph-utf8 @ 59745formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2396 is way too long (95 characters)
texlive-amsfonts @ 59745formatting

Look for formatting issues in the source

line 1341 is way too long (94 characters)
texlive-amsfonts @ 59745formatting

Look for formatting issues in the source

line 1366 is way too long (93 characters)
texlive-amsfonts @ 59745formatting

Look for formatting issues in the source

line 1368 is way too long (91 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)
ruby-tzinfo-data @ 1.2021.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 492 is way too long (112 characters)
ruby-asciidoctor-pdf @ 1.6.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 522 is way too long (94 characters)
python2-pygobject @ 3.40.1formatting

Look for formatting issues in the source

line 935 is way too long (97 characters)
python2 @ 2.7.18formatting

Look for formatting issues in the source

line 222 is way too long (99 characters)
python-pyqt @ 5.15.2formatting

Look for formatting issues in the source

line 2094 is way too long (105 characters)
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 632 is way too long (92 characters)
plasma-framework @ 5.70.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
openmpi @ 4.1.1formatting

Look for formatting issues in the source

line 274 is way too long (94 characters)
openmpi @ 4.1.1formatting

Look for formatting issues in the source

line 276 is way too long (96 characters)
openfoam @ 4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 148 is way too long (91 characters)
onionshare @ 2.4formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ncurses @ 6.2.20210619formatting

Look for formatting issues in the source

line 179 is way too long (94 characters)
minizip @ 1.2.11formatting

Look for formatting issues in the source

line 167 is way too long (115 characters)
mesa @ 21.2.5formatting

Look for formatting issues in the source

line 264 is way too long (97 characters)
mesa @ 21.2.5formatting

Look for formatting issues in the source

line 276 is way too long (97 characters)
mesa @ 21.2.5formatting

Look for formatting issues in the source

line 291 is way too long (120 characters)
mesa @ 21.2.5formatting

Look for formatting issues in the source

line 323 is way too long (98 characters)
mbedtls-apache @ 2.26.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 162 is way too long (99 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
libsigsegv @ 2.13formatting

Look for formatting issues in the source

line 48 is way too long (133 characters)
libsigrok @ 0.5.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 209 is way too long (92 characters)
librime @ 1.7.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 522 is way too long (95 characters)
libgit2 @ 1.3.0formatting

Look for formatting issues in the source

line 793 is way too long (96 characters)
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
kpackage @ 5.70.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2174 is way too long (113 characters)
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-libuuid-jll @ 2.36.0+0formatting

Look for formatting issues in the source

line 1219 is way too long (92 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-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 132 is way too long (91 characters)
idris @ 1.3.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 166 is way too long (105 characters)
heimdal @ 7.7.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 126 is way too long (92 characters)
guile-sdl @ 0.5.3formatting

Look for formatting issues in the source

line 609 is way too long (111 characters)
gmp @ 6.2.1formatting

Look for formatting issues in the source

line 83 is way too long (96 characters)
git-crypt @ 0.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 522 is way too long (107 characters)
ghc-xdg-basedir @ 0.2.2formatting

Look for formatting issues in the source

line 14601 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 12929 is way too long (92 characters)
ghc-template-haskell-compat-v0208 @ 0.1.6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1067 is way too long (101 characters)
ghc-persistent-postgresql @ 2.13.2.1formatting

Look for formatting issues in the source

line 15815 is way too long (95 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-language-javascript @ 0.7.1.0formatting

Look for formatting issues in the source

line 1902 is way too long (91 characters)
ghc-indexed-traversable @ 0.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 15695 is way too long (103 characters)
ghc-doctest-exitcode-stdio @ 0.0formatting

Look for formatting issues in the source

line 1128 is way too long (99 characters)
ghc-commonmark-extensions @ 0.2.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 951 is way too long (101 characters)
ghc @ 8.10.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 724 is way too long (92 characters)
gdm @ 40.1formatting

Look for formatting issues in the source

line 8390 is way too long (104 characters)
flashrom @ 1.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 94 is way too long (99 characters)
extra-cmake-modules @ 5.70.0formatting

Look for formatting issues in the source

line 121 is way too long (91 characters)
efitools @ 1.9.2formatting

Look for formatting issues in the source

line 211 is way too long (113 characters)
docker @ 19.03.15formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 382 is way too long (93 characters)
cups-minimal @ 2.3.3op2formatting

Look for formatting issues in the source

tabulation on line 289, column 0
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
cmake @ 3.21.3formatting

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 87 is way too long (104 characters)
bazaar @ 2.7.0formatting

Look for formatting issues in the source

line 170 is way too long (93 characters)
atril @ 1.24.0formatting

Look for formatting issues in the source

line 714 is way too long (92 characters)
c-blosc @ 1.18.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
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
gnome-maps @ 41.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
brotli @ 1.0.9formatting

Look for formatting issues in the source

line 2130 is way too long (94 characters)
python-uqbar @ 0.5.6inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
xdot @ 1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python2-graphviz @ 0.13.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-graphviz @ 0.13.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-pydot @ 1.4.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
nss-certs @ 3.71patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
manuskript @ 0.13.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
blanket @ 0.5.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
quickjs @ 2021-03-27optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
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 229 is way too long (92 characters)
js-mathjax @ 3.2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 651 is way too long (99 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)
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
knotes @ 20.04.1inputs-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
kget @ 20.04.1inputs-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

'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
kaddressbook @ 20.04.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python-pytest-ordering @ 0.6optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
xkbprint @ 1.0.5description

Validate package descriptions

use @code or similar ornament instead of quotes
r-seqlogo @ 1.60.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-biomart @ 2.50.1description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gtk-doc @ 1.33.2inputs-should-be-native

Identify inputs that should be native inputs

'yelp-tools' should probably be a native input
mousepad @ 0.5.8wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
mkfontdir @ 1.0.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gtk-doc @ 1.33.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
c-reduce @ 2.10.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
rgbds @ 0.4.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
c-reduce @ 2.10.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
at-spi2-atk @ 2.38.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
pangomm @ 2.46.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs libsigc++@2.9.3 and libsigc++@3.0.6 collide
gtksourceviewmm @ 3.18.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs glibmm@2.68.0 and glibmm@2.64.5 collide
gtkmm @ 3.24.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs libsigc++@2.9.3 and libsigc++@3.0.6 collide
gtkmm @ 2.24.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs libsigc++@2.9.3 and libsigc++@3.0.6 collide
cairomm @ 1.14.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs libsigc++@2.9.3 and libsigc++@3.0.6 collide
atkmm @ 2.28.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs glibmm@2.64.5 and glibmm@2.68.0 collide
guile2.2-rsvg @ 2.18.1-0.05c6a2fpatch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
cairo-xcb @ 1.16.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xkeyboard-config @ 2.34formatting

Look for formatting issues in the source

line 3987 is way too long (102 characters)
volctl @ 0.8.2formatting

Look for formatting issues in the source

line 2863 is way too long (98 characters)
telepathy-glib @ 0.24.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1336 is way too long (95 characters)
r-drimseq @ 1.22.0formatting

Look for formatting issues in the source

line 1746 is way too long (109 characters)
gtk-doc @ 1.33.2formatting

Look for formatting issues in the source

line 2237 is way too long (92 characters)
gtk+ @ 2.24.33formatting

Look for formatting issues in the source

tabulation on line 910, column 0
gtk+ @ 2.24.33formatting

Look for formatting issues in the source

tabulation on line 911, column 0
gtk+ @ 2.24.33formatting

Look for formatting issues in the source

tabulation on line 912, column 0
cairo @ 1.16.0formatting

Look for formatting issues in the source

tabulation on line 164, column 0
cairo @ 1.16.0formatting

Look for formatting issues in the source

tabulation on line 165, column 0
appstream-glib @ 0.7.18formatting

Look for formatting issues in the source

line 1179 is way too long (93 characters)
pitivi @ 0.999.0-2021.05.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
openshot @ 2.6.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
openshot @ 2.6.1formatting

Look for formatting issues in the source

line 4785 is way too long (94 characters)
openshot @ 2.6.1formatting

Look for formatting issues in the source

line 4786 is way too long (96 characters)
openshot @ 2.6.1formatting

Look for formatting issues in the source

line 4787 is way too long (92 characters)
tor @ 0.4.6.9description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 574
i3-wm @ 4.18.3description

Validate package descriptions

description should start with an upper-case letter or digit
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
keybinder-3.0 @ 0.3.2inputs-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
awesome @ 4.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
impressive @ 0.12.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
flyer-composer @ 1.0rc2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
awesome @ 4.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python2-pypdf2 @ 1.26.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pypdf2 @ 1.26.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-taggit @ 1.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-tagging @ 0.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-statici18n @ 2.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-sortedm2m @ 3.0.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-simple-math-captcha @ 1.0.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-rq @ 2.3.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-redis @ 4.12.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-picklefield @ 3.0.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-override-storage @ 0.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-filter @ 2.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-debug-toolbar @ 3.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-contact-form @ 1.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-auth-ldap @ 2.4.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-appconf @ 1.0.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-django-allauth @ 0.42.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
faiss @ 1.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
awesome @ 4.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
tor-client @ 0.4.6.9patch-file-names

Validate file names and availability of patches

file names of patches should start with 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
zathura-pdf-poppler @ 0.3.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 488 is way too long (93 characters)
tdlib @ 1.7.10tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
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
psi-plus @ 1.5.1484wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
perl-net-psyc @ 1.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
nheko @ 0.8.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
psi-plus @ 1.5.1484formatting

Look for formatting issues in the source

line 2931 is way too long (96 characters)
sonata @ 1.7.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
sonata @ 1.7.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
mpdris2 @ 0.9.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
mcg @ 2.1.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python-mpd2 @ 3.0.4optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mpdris2 @ 0.9.1formatting

Look for formatting issues in the source

line 410 is way too long (96 characters)
trytond-timesheet @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-stock-split @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-stock-package @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-stock-lot-unit @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-stock-location-move @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-sale-promotion @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-sale-extra @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-production-work-timesheet @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-production-work @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-production-split @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-production-outsourcing @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-party-relationship @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-notification-email @ 6.0.1description

Validate package descriptions

description contains typo 'allows to'
trytond-ldap-authentication @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-customs @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-commission-waiting @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-commission @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-analytic-sale @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-analytic-purchase @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-analytic-invoice @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-tax-cash @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-stock-landed-cost @ 6.0.1description

Validate package descriptions

description contains typo 'allows to'
trytond-account-statement @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-payment-sepa @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-payment-clearing @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-invoice-line-standalone @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-invoice-defer @ 6.0.0description

Validate package descriptions

description contains typo 'allows to'
trytond-account-es @ 6.0.2description

Validate package descriptions

description contains typo 'allows to'
trytond-account-deposit @ 6.0.1description

Validate package descriptions

description contains typo 'allows to'
tryton @ 6.0.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
xwallpaper @ 0.7.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 72
xftwidth @ 20170402description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 96, 234
wlsunset @ 0.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
poezio @ 0.13.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
gajim @ 1.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
xkbset @ 0.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gajim @ 1.3.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
tomsfastmath @ 0.13.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libtommath @ 1.2.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libtomcrypt @ 1.18.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
j4-dmenu-desktop @ 2.18optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
gajim @ 1.3.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
clipmenu @ 6.0.1-1.bcbe7b1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
gajim @ 1.3.3patch-headers

Validate patch headers

gajim-honour-GAJIM_PLUGIN_PATH.patch: patch lacks comment and upstream status
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1841, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1842, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1844, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1845, column 0
libtomcrypt @ 1.18.2formatting

Look for formatting issues in the source

line 366 is way too long (100 characters)
vis @ 0.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
adcli @ 0.9.1formatting

Look for formatting issues in the source

line 88 is way too long (95 characters)
lxpanel @ 0.10.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
tomb @ 2.9wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
hash-extender @ 0.0-2.cb8aaeeoptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libsecp256k1 @ 20200615-1.dbd41dbformatting

Look for formatting issues in the source

line 1109 is way too long (103 characters)
trf @ 4.09.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'python-cython' should probably be a native input
ciri-long @ 1.0.2inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
tetoolkit @ 2.0.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ribotaper @ 1.3.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
repeat-masker @ 4.1.2-p1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
edirect @ 13.3.20200128wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ceph @ 16.2.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
bioperl-minimal @ 1.7.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
bamm @ 1.7.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python2-pybedtools @ 0.8.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pybedtools @ 0.8.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pairtools @ 0.3.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
flexbar @ 3.4.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
express-beta-diversity @ 1.0.8optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bowtie @ 2.3.4.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bamm @ 1.7.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
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
python-dendropy @ 4.5.1formatting

Look for formatting issues in the source

line 3094 is way too long (96 characters)
python-dendropy @ 4.5.1formatting

Look for formatting issues in the source

line 3095 is way too long (93 characters)
opencv @ 4.5.4formatting

Look for formatting issues in the source

line 442 is way too long (132 characters)
java-picard @ 2.3.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4584 is way too long (117 characters)
blasr-libcpp @ 5.3.5formatting

Look for formatting issues in the source

line 727 is way too long (95 characters)
perl-search-xapian @ 1.2.25.4description

Validate package descriptions

use @code or similar ornament instead of quotes
recoll @ 1.31.2inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
nyxt @ 2.2.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
swish-e @ 2.4.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
recoll @ 1.31.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
nyxt @ 2.2.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
xapian @ 1.4.18optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libtocc @ 1.0.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
webkitgtk-with-libsoup2 @ 2.34.3patch-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 @ 2.33formatting

Look for formatting issues in the source

line 818 is way too long (98 characters)
coq-stdlib @ 8.14.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
guile-zstd @ 0.1.1description

Validate package descriptions

use @code or similar ornament instead of quotes
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-git @ 0.5.2patch-headers

Validate patch headers

guile-git-adjust-for-libgit2-1.2.0.patch: patch lacks comment and upstream status
guile2.2-readline @ 2.2.7formatting

Look for formatting issues in the source

line 484 is way too long (94 characters)
guile-readline @ 3.0.7formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 205 is way too long (93 characters)
python2-weave @ 0.16.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
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
straw-viewer @ 0.1.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
lightdm @ 1.30.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python-language-server @ 1.3.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-trytond @ 6.0.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-onnx @ 1.9.0patch-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
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
curl-minimal @ 7.79.1patch-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
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 383, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 385, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 388, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 389, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 398, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 399, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 400, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 401, column 0
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 403, 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 406, 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
tkrev @ 9.4.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
src @ 1.18wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
myrepos @ 1.20180726wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
git-when-merged @ 1.2.0-ab6af78wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
git-open @ 2.1.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
git-imerge @ 1.1.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
diff-so-fancy @ 1.4.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
src @ 1.18optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
gita @ 0.12.9-1.e41b504optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
aegis @ 4.24optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
aegis @ 4.24patch-headers

Validate patch headers

aegis-perl-tempdir2.patch: patch lacks comment and upstream status
b4 @ 0.6.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2577 is way too long (112 characters)
sbcl-trivial-gray-streams @ 0.0.0-1.ebd59b1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
sbcl-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 305 is way too long (96 characters)
conda @ 4.10.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-conda-package-handling @ 1.7.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
conda @ 4.10.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
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
singularity @ 2.6.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
pcb @ 4.0.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
kbd @ 2.4.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
bcc @ 0.16.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
util-linux-with-udev @ 2.37.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
bpftrace @ 0.11.4patch-headers

Validate patch headers

bpftrace-disable-bfd-disasm.patch: patch lacks comment and upstream status
linux-pam @ 1.5.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 669 is way too long (99 characters)
java-xpp3 @ 1.1.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 188
java-mxparser @ 1.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 188, 473
java-kxml2 @ 2.4.2description

Validate package descriptions

description should start with an upper-case letter or digit
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
python2-lxml @ 4.6.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-lxml @ 4.6.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
java-testng @ 6.14.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
java-jnacl @ 0.1.0-2.094e819optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
antlr4 @ 4.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
java-xmlunit-matchers @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-xerial-core @ 2.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-stringtemplate @ 4.0.8source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-archiver @ 4.2.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-tinybundles @ 2.1.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core-spi @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core-junit @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-native-access-platform @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-native-access @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-mvel2 @ 2.3.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-microemulator-cldc @ 2.0.4source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-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-plexus-sec-dispatcher @ 1.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide
java-plexus-digest @ 1.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@3.1 collide
java-plexus-container-default @ 1.7.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-component-metadata @ 1.7.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@13 and apache-parent-pom@21 collide
java-plexus-compiler-manager @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-compiler-javac @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-compiler-api @ 2.8.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide
java-plexus-archiver @ 4.2.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@6.1 collide
java-modello-test @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-plugins-xpp3 @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-plugins-xml @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-plugins-java @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-modello-core @ 1.9.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-eclipse-sisu-plexus @ 0.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
antlr3 @ 3.5.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-stringtemplate@3.2.1 and java-stringtemplate@4.0.6 collide
java-tunnelvisionlabs-antlr4-runtime-annotations @ 4.7.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-tunnelvisionlabs-antlr4-runtime @ 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-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-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
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

line 2338 is way too long (91 characters)
java-xom @ 127formatting

Look for formatting issues in the source

trailing white space on line 1890
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-testng @ 6.14.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9335 is way too long (110 characters)
java-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2550 is way too long (99 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

line 12518 is way too long (92 characters)
java-native-access @ 4.5.1formatting

Look for formatting issues in the source

line 12696 is way too long (91 characters)
java-logback-classic @ 1.2.3formatting

Look for formatting issues in the source

line 13264 is way too long (102 characters)
java-joda-time @ 2.9.9formatting

Look for formatting issues in the source

line 12098 is way too long (92 characters)
java-jnacl @ 0.1.0-2.094e819formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10741 is way too long (92 characters)
java-jgit @ 4.2.0.201601211800-rformatting

Look for formatting issues in the source

line 13364 is way too long (93 characters)
java-jansi @ 2.4.0formatting

Look for formatting issues in the source

line 11872 is way too long (94 characters)
java-hawtjni @ 1.15formatting

Look for formatting issues in the source

line 11732 is way too long (92 characters)
java-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9746 is way too long (93 characters)
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 7225, column 20
java-eclipse-sisu-plexus @ 0.3.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 7283 is way too long (98 characters)
java-commons-httpclient @ 3.1formatting

Look for formatting issues in the source

line 12558 is way too long (91 characters)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

line 5829 is way too long (91 characters)
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

line 9520 is way too long (91 characters)
java-apache-ivy @ 2.4.0formatting

Look for formatting issues in the source

line 12907 is way too long (101 characters)
icedtea @ 3.19.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1085 is way too long (100 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)
antlr4 @ 4.8formatting

Look for formatting issues in the source

line 8392 is way too long (96 characters)
antlr4 @ 4.8formatting

Look for formatting issues in the source

line 8466 is way too long (100 characters)
catdoc @ 0.95description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 157
wine64-staging @ 6.6inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'autoconf' should probably be a native input
opencc @ 1.1.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
wine64-staging @ 6.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wine64 @ 6.20wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wine-staging @ 6.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wine @ 6.20wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wine64-staging @ 6.6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
telegram-desktop @ 2.9.3formatting

Look for formatting issues in the source

line 353 is way too long (93 characters)
xygrib @ 1.2.6.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 42
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-nu-plugin-query-json @ 0.42.0description

Validate package descriptions

description should start with an upper-case letter or digit
ppsspp @ 1.11.3-1.69fa207description

Validate package descriptions

use @code or similar ornament instead of quotes
nushell @ 0.42.0description

Validate package descriptions

use @code or similar ornament instead of quotes
kldap @ 20.04.1description

Validate package descriptions

description contains leading whitespace
shogun @ 6.1.3inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
python-pytest-repeat @ 0.9.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-mpl @ 0.11inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-pytest-mockito @ 0.0.4inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-exploratory @ 0.5inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
osm-gps-map @ 1.1.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
nextcloud-client @ 3.2.0inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
libchamplain @ 0.12.20inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' 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.08.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'swig' should probably be a native input
cockatrice @ 2.8.0inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
python-pytest-helpers-namespace @ 2021.3.24inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
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
vnlog @ 1.32wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
vlc @ 3.0.16wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
utox @ 0.18.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
totem @ 3.38.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
signing-party @ 2.11wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
rhythmbox @ 3.4.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
remmina @ 1.4.23wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ranger @ 1.9.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
qtox @ 1.17.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
qgis @ 3.16.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
qgis @ 3.16.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
prosody @ 0.11.10wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
pipe-viewer @ 0.1.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
pinentry-rofi @ 2.0.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
phockup @ 1.7.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
pdfarranger @ 1.8.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
pcsxr @ 1.9.95wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
mypaint @ 2.0.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
itk-snap @ 3.8.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
grass @ 7.8.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gpa @ 0.10.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gammastep @ 2.0.8wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gamine @ 1.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
fzf @ 0.25.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
eog @ 40.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
corsix-th @ 0.65.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cool-retro-term @ 1.1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
biber @ 2.16wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
bcachefs-tools @ 0.1-13.b19d9f9wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
akregator @ 20.04.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
unknown-horizons @ 2019.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
rxcpp @ 4.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ranger @ 1.9.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
qgis @ 3.16.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-stdnum @ 1.17optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python2-pygpgme @ 0.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-stdnum @ 1.17optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-remotedata @ 0.3.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-openfiles @ 0.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-helpers-namespace @ 2021.3.24optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pytest-filter-subpackage @ 0.1.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-pygpgme @ 0.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
python-curtsies @ 0.3.5optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
ppsspp @ 1.11.3-1.69fa207optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mkvtoolnix @ 52.0.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
kitty @ 0.20.3optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
fann @ 2.2.0-1.d71d5478optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
dlib @ 19.20optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bind @ 9.16.24optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
bastet @ 0.43.2optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
autotrace @ 0.40.0-20190624.59optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
asciinema @ 2.1.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
tegola @ 0.7.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
imposm3 @ 0.11.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python2-pygpgme @ 0.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
pinball @ 0.3.20201218patch-headers

Validate patch headers

pinball-system-ltdl.patch: patch lacks comment and upstream status
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
xst @ 0.8.4.1formatting

Look for formatting issues in the source

line 419 is way too long (98 characters)
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
texlive-latex-pgf @ 59745formatting

Look for formatting issues in the source

line 7719 is way too long (98 characters)
superstarfighter @ 0.6.5formatting

Look for formatting issues in the source

line 2564 is way too long (115 characters)
shogun @ 6.1.3formatting

Look for formatting issues in the source

line 675 is way too long (91 characters)
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 2938 is way too long (114 characters)
mkvtoolnix @ 52.0.0formatting

Look for formatting issues in the source

line 961 is way too long (96 characters)
libunibreak @ 5.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
guile-aiscm @ 0.23.1formatting

Look for formatting issues in the source

line 329 is way too long (114 characters)
gnubg @ 1.06.002formatting

Look for formatting issues in the source

line 1839 is way too long (91 characters)
geany @ 1.38formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
freedink-engine @ 109.6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 3306, column 0
einstein @ 2.0formatting

Look for formatting issues in the source

line 4708 is way too long (96 characters)
cc65 @ 2.19formatting

Look for formatting issues in the source

line 2489 is way too long (167 characters)
blender @ 3.0.0formatting

Look for formatting issues in the source

line 447 is way too long (97 characters)
nsis-x86_64 @ 3.05name

Validate package names

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
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-fsnotify @ 0.3.0.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 81
pcc @ 20170109optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
u-boot-sifive-unmatched @ 2021.10patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-firefly-rk3399 @ 2021.10patch-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
nsis-x86_64 @ 3.05patch-headers

Validate patch headers

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

Validate patch headers

nsis-env-passthru.patch: patch lacks comment and upstream status
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 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)
java-commons-jxpath @ 1.3formatting

Look for formatting issues in the source

line 6060 is way too long (93 characters)
rsyslog @ 8.2112.0formatting

Look for formatting issues in the source

trailing white space on line 250
rsyslog @ 8.2112.0formatting

Look for formatting issues in the source

trailing white space on line 262
clementine @ 1.4.0rc1-450-g2725ef99dwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
denemo @ 2.5.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
xtensor-benchmark @ 0.20.10description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 798
opencascade-occt @ 7.3.0p3inputs-should-be-native

Identify inputs that should be native inputs

'doxygen' should probably be a native input
octave-cli @ 6.2.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'texinfo' should probably be a native input
wxmaxima @ 21.05.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
veusz @ 3.3.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gccgo @ 10.3.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
z3 @ 4.8.9optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
pt-scotch32 @ 6.1.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
pt-scotch @ 6.1.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mumps-openmpi @ 5.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mumps-metis-openmpi @ 5.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mumps-metis @ 5.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
mumps @ 5.2.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
maxima @ 5.45.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
hypre @ 2.20.0optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
gappa @ 1.3.5optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
eigen-for-tensorflow-lite @ 3.3.7-1.d10b27foptional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
eigen-for-tensorflow @ 3.3.5-1.fd6845384b86optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
scotch32 @ 6.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
scotch-shared @ 6.1.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
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++ @ 9.4.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 @ 9.4.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
eigen-benchmarks @ 3.3.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
dune-istl-openmpi @ 2.7.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
symmetrica @ 2.0patch-headers

Validate patch headers

symmetrica-bruch.patch: patch lacks comment and upstream status
scotch32 @ 6.1.1patch-headers

Validate patch headers

scotch-integer-declarations.patch: patch lacks comment and upstream status
scotch-shared @ 6.1.1patch-headers

Validate patch headers

scotch-integer-declarations.patch: patch lacks comment and upstream status
scotch @ 6.1.1patch-headers

Validate patch headers

scotch-integer-declarations.patch: patch lacks comment and upstream status
pt-scotch32 @ 6.1.1patch-headers

Validate patch headers

scotch-integer-declarations.patch: patch lacks comment and upstream status
pt-scotch-shared @ 6.1.1patch-headers

Validate patch headers

scotch-integer-declarations.patch: patch lacks comment and upstream status
pt-scotch @ 6.1.1patch-headers

Validate patch headers

scotch-integer-declarations.patch: patch lacks comment and upstream status
libstdc++-doc @ 9.4.0patch-headers

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Look for formatting issues in the source

line 1522 is way too long (100 characters)
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 6284, column 0
slepc-openmpi @ 3.16.1formatting

Look for formatting issues in the source

tabulation on line 3305, column 0
slepc-complex-openmpi @ 3.16.1formatting

Look for formatting issues in the source

line 3321 is way too long (92 characters)
pt-scotch32 @ 6.1.1formatting

Look for formatting issues in the source

tabulation on line 4113, column 0
pt-scotch @ 6.1.1formatting

Look for formatting issues in the source

tabulation on line 4091, column 0
petsc @ 3.16.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
p4est @ 2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 3676, column 0
mumps @ 5.2.1formatting

Look for formatting issues in the source

line 3590 is way too long (94 characters)
hypre-openmpi @ 2.20.0formatting

Look for formatting issues in the source

tabulation on line 5655, column 0
gap @ 4.11.0formatting

Look for formatting issues in the source

line 1259 is way too long (98 characters)
marble-qt @ 21.08.3inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
labplot @ 2.8.2inputs-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
tuxpaint @ 0.9.23wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
tuxpaint @ 0.9.23patch-headers

Validate patch headers

tuxpaint-stamps-path.patch: patch lacks comment and upstream status
akku @ 1.0.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
flatpak @ 1.12.1optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
libxt @ 1.2.1patch-headers

Validate patch headers

libxt-guix-search-paths.patch: patch lacks comment and upstream status
tuxmath @ 2.0.3description

Validate package descriptions

description should start with an upper-case letter or digit
anki @ 2.1.16wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
omnitux @ 1.2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 524 is way too long (92 characters)
go-github-com-mitchellh-reflectwalk @ 1.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
go-github-com-mattn-go-zglob @ 0.0.3description

Validate package descriptions

description contains leading whitespace
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-gitlab-com-ambrevar-golua-unicode @ 0.0.0-0.97ce517optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-github-com-wtolson-go-taglib @ 0.0.0-0.6e68349optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
go-gopkg-in-yaml-v2 @ 2.4.0formatting

Look for formatting issues in the source

line 3912 is way too long (104 characters)
go-github-com-mitchellh-go-homedir @ 1.0.0-0.ae18d6bformatting

Look for formatting issues in the source

line 4855 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 3190 is way too long (164 characters)
go-github-com-davecgh-go-spew @ 1.1.1formatting

Look for formatting issues in the source

line 4425 is way too long (129 characters)
python2-pygame @ 1.9.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 123
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
renpy @ 7.4.10wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python2-renpy @ 7.4.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perl-crypt-unixcrypt_xs @ 0.11name

Validate package names

name should use hyphens instead of underscores
perl-unicode-utf8 @ 0.62tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
wpa-supplicant-minimal @ 2.9description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 47
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
perl-extutils-pkgconfig @ 1.16inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
wpa-supplicant-gui @ 2.9wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
rename @ 1.10wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
perl-sgmls @ 1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
perl-eval-withlexicals @ 1.003006wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
isc-dhcp @ 4.4.2-P1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
clusterssh @ 4.13.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cloud-utils @ 0.32wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wpa-supplicant-minimal @ 2.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
wpa-supplicant-gui @ 2.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
hostapd @ 2.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 9556 is way too long (97 characters)
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
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 342 is way too long (99 characters)
ploticus @ 2.42wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
itcl @ 4.2.2description

Validate package descriptions

description should start with an upper-case letter or digit
moreutils @ 0.67wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
linuxdcpp @ 1.1.0patch-headers

Validate patch headers

linuxdcpp-openssl-1.1.patch: patch lacks comment and upstream status
python-django-q @ 1.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-django@3.2.11 and python-django@2.2.26 collide
r-tidyr @ 1.1.4description

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
emacs-ess @ 18.10.2-0.24da603optional-tests

Make sure tests are only run when requested

the 'check' phase should respect #:tests?
xlispstat @ 3.52.23-0.f1bea60formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 6384 is way too long (94 characters)
r-dt @ 0.20formatting

Look for formatting issues in the source

line 3543 is way too long (92 characters)
r-dt @ 0.20formatting

Look for formatting issues in the source

line 3544 is way too long (91 characters)
r-dt @ 0.20formatting

Look for formatting issues in the source

line 3546 is way too long (98 characters)
r-dt @ 0.20formatting

Look for formatting issues in the source

line 3547 is way too long (94 characters)
r-dt @ 0.20formatting

Look for formatting issues in the source

line 3556 is way too long (93 characters)
r-dt @ 0.20formatting

Look for formatting issues in the source

line 3585 is way too long (93 characters)
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 @ 4