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
nsis-i686 @ 3.05description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
perl6-grammar-debugger @ 1.0.1-1.0375008description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 203
rcm @ 1.3.3description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
cinnamon-desktop @ 3.4.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' 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
aseba @ 1.6.0-0.3b35de8inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 118 is way too long (114 characters)
jose @ 10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 86 is way too long (95 characters)
ldc @ 0.17.4formatting

Look for formatting issues in the source

line 137 is way too long (98 characters)
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 521 is way too long (92 characters)
libdaemon @ 0.14formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
pth @ 2.0.7formatting

Look for formatting issues in the source

trailing white space on line 42
ldc @ 1.10.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 260 is way too long (92 characters)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 573 is way too long (103 characters)
efitools @ 1.9.2formatting

Look for formatting issues in the source

line 176 is way too long (113 characters)
mingw-w64-i686-winpthreads @ 7.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 223 is way too long (91 characters)
python2 @ 2.7.17formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 290 is way too long (98 characters)
mingw-w64-x86_64 @ 7.0.0formatting

Look for formatting issues in the source

line 90 is way too long (91 characters)
mingw-w64-i686 @ 7.0.0formatting

Look for formatting issues in the source

line 90 is way too long (91 characters)
ncurses @ 6.2formatting

Look for formatting issues in the source

trailing white space on line 165
ncurses @ 6.2formatting

Look for formatting issues in the source

line 179 is way too long (94 characters)
axoloti-runtime @ 1.0.12-2formatting

Look for formatting issues in the source

line 196 is way too long (96 characters)
libsigsegv @ 2.12formatting

Look for formatting issues in the source

line 48 is way too long (133 characters)
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

line 213 is way too long (106 characters)
hyperledger-iroha @ 1.1.1formatting

Look for formatting issues in the source

line 169 is way too long (105 characters)
papi @ 5.5.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
gmp @ 6.2.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 90 is way too long (91 characters)
guile-sdl @ 0.5.2formatting

Look for formatting issues in the source

line 607 is way too long (111 characters)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 118 is way too long (114 characters)
ibus-anthy @ 1.5.9inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
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-test2-plugin-nowarnings @ 0.06formatting

Look for formatting issues in the source

line 106 is way too long (92 characters)
perl-search-xapian @ 1.2.25.2description

Validate package descriptions

use @code or similar ornament instead of quotes
vorbis-tools @ 1.4.0formatting

Look for formatting issues in the source

trailing white space on line 323
guile @ 2.0.14formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 191 is way too long (93 characters)
netpbm @ 10.78.3formatting

Look for formatting issues in the source

line 86 is way too long (127 characters)
glibc @ 2.31formatting

Look for formatting issues in the source

line 807 is way too long (98 characters)
wicd @ 1.7.4formatting

Look for formatting issues in the source

line 109 is way too long (95 characters)
dejagnu @ 1.6.2formatting

Look for formatting issues in the source

line 60 is way too long (91 characters)
guile-readline @ 3.0.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 381 is way too long (94 characters)
python-libfreenect @ 0.6.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
busybox @ 1.31.1formatting

Look for formatting issues in the source

trailing white space on line 93
busybox @ 1.31.1formatting

Look for formatting issues in the source

line 95 is way too long (92 characters)
presentty @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
presentty @ 0.2.1formatting

Look for formatting issues in the source

line 45 is way too long (117 characters)
deutex @ 5.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 60
grfcodec @ 6.0.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 100
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 292, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 294, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 297, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 298, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 307, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 308, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 309, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 310, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 311, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 312, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 313, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 315, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 316, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 317, column 0
arm-trusted-firmware-rk3328 @ 2.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
elixir @ 1.10.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 76 is way too long (99 characters)
zn-poly @ 0.9.2description

Validate package descriptions

description should start with an upper-case letter or digit
dmraid @ 1.0.0.rc16-3formatting

Look for formatting issues in the source

line 757 is way too long (91 characters)
maven-resolver-impl @ 1.3.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 284 is way too long (102 characters)
java-jbzip2 @ 0.9.1formatting

Look for formatting issues in the source

line 274 is way too long (92 characters)
maven-embedder @ 3.6.1formatting

Look for formatting issues in the source

line 1636 is way too long (110 characters)
maven-shared-utils @ 3.2.1formatting

Look for formatting issues in the source

line 583 is way too long (109 characters)
maven-wagon-http @ 3.3.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 738 is way too long (125 characters)
tigervnc-server @ 1.10.1-1.920d9c4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 188, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 247, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 248, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 249, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 250, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 251, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 252, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 253, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 254, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 255, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 258, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 259, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 261, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 262, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 263, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 264, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 265, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 267, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 268, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 269, column 0
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 270, column 0
syncthing-gtk @ 0.9.4.4inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python2-setuptools' should probably not be an input at all
syncthing @ 1.5.0formatting

Look for formatting issues in the source

line 109 is way too long (93 characters)
libsigrok @ 0.5.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 211 is way too long (92 characters)
libblockdev @ 2.24formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libextractor @ 1.10formatting

Look for formatting issues in the source

line 128 is way too long (140 characters)
lxde-common @ 0.99.2formatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'm4' should probably be a native input
rtl-sdr @ 0.6.0description

Validate package descriptions

use @code or similar ornament instead of quotes
shogun @ 6.1.3inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
shogun @ 6.1.3formatting

Look for formatting issues in the source

line 520 is way too long (91 characters)
libringclient @ 20200710.1.6bd18d2inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
libringclient @ 20200710.1.6bd18d2formatting

Look for formatting issues in the source

line 502 is way too long (105 characters)
jami @ 20200710.1.6bd18d2formatting

Look for formatting issues in the source

line 536 is way too long (92 characters)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 95 is way too long (93 characters)
ghc @ 8.6.5formatting

Look for formatting issues in the source

line 591 is way too long (91 characters)
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
python-wxpython @ 4.0.7.post1description

Validate package descriptions

description should start with an upper-case letter or digit
cfitsio @ 3.49description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
zbar @ 0.23inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
flite @ 2.1formatting

Look for formatting issues in the source

line 90 is way too long (419 characters)
help2man @ 1.47.13formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
mate-applets @ 1.24.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 917
mate-panel @ 1.24.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 509 is way too long (91 characters)
atril @ 1.22.0formatting

Look for formatting issues in the source

line 744 is way too long (92 characters)
ruby-iruby @ 0.3formatting

Look for formatting issues in the source

line 490 is way too long (112 characters)
openfoam @ 4.1inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
openfoam @ 4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 146 is way too long (91 characters)
chez-srfi @ 1.0formatting

Look for formatting issues in the source

line 245 is way too long (91 characters)
python-pytools @ 2020.4description

Validate package descriptions

use @code or similar ornament instead of quotes
gcompris @ 17.05formatting

Look for formatting issues in the source

line 135 is way too long (96 characters)
texlive-lm @ 51265description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Check for autogenerated tarballs

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2414, column 22
texlive-amsfonts @ 51265formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1142 is way too long (91 characters)
kimageformats @ 5.70.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 704 is way too long (107 characters)
extra-cmake-modules @ 5.70.0formatting

Look for formatting issues in the source

line 112 is way too long (91 characters)
fdroidserver @ 1.1.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 700 is way too long (105 characters)
android-safe-iop @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 277, column 20
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 385 is way too long (97 characters)
xygrib @ 1.2.6.1description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 193 is way too long (95 characters)
maven-surefire-plugin @ 3.0.0-M4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3606 is way too long (111 characters)
java-surefire-booter @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3269 is way too long (107 characters)
dico @ 2.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
cryptsetup-static @ 2.3.4formatting

Look for formatting issues in the source

line 102 is way too long (93 characters)
calibre @ 4.18.0formatting

Look for formatting issues in the source

line 245 is way too long (93 characters)
robin-map @ 0.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 281
sdsl-lite @ 2.1.1formatting

Look for formatting issues in the source

line 234 is way too long (145 characters)
python-pytest-django @ 3.10.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
patchwork @ 2.2.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
jucipp @ 1.6.1description

Validate package descriptions

description should start with an upper-case letter or digit
spice-gtk @ 0.37inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
ibus-libhangul @ 1.5.3description

Validate package descriptions

description should start with an upper-case letter or digit
librime @ 1.6.1formatting

Look for formatting issues in the source

line 328 is way too long (93 characters)
mrustc @ 0.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 497
python-xsge @ 2020.09.07description

Validate package descriptions

description should start with an upper-case letter or digit
mia @ 2.4.6inputs-should-be-native

Identify inputs that should be native inputs

'doxygen' should probably be a native input
opencv @ 3.4.3formatting

Look for formatting issues in the source

line 363 is way too long (132 characters)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

line 560 is way too long (93 characters)
kget @ 20.04.1description

Validate package descriptions

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

Look for formatting issues in the source

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

Look for formatting issues in the source

trailing white space on line 683
unbound @ 1.10.1formatting

Look for formatting issues in the source

trailing white space on line 719
python-fpylll @ 0.5.2description

Validate package descriptions

description should start with an upper-case letter or digit
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
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'
texlive-fonts-lm @ 51265description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
guile3.0-mailutils @ 3.10inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
hackrf @ 2018.01.1-0.43e6f99description

Validate package descriptions

use @code or similar ornament instead of quotes
guile3.0-ncurses @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
maven-surefire-plugin @ 3.0.0-M4profile-collisions

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide
java-sonatype-aether-impl @ 1.7profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-forge-parent-pom@6 and java-sonatype-forge-parent-pom@10 collide
docker @ 19.03.12formatting

Look for formatting issues in the source

line 350 is way too long (95 characters)
docker @ 19.03.12formatting

Look for formatting issues in the source

line 386 is way too long (93 characters)
containerd @ 1.2.5formatting

Look for formatting issues in the source

line 214 is way too long (105 characters)
libreoffice @ 6.4.6.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
r-dplyr @ 1.0.2description

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
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
texlive-latex-pgf @ 51265formatting

Look for formatting issues in the source

line 6537 is way too long (98 characters)
malcontent @ 0.8.0formatting

Look for formatting issues in the source

line 252 is way too long (91 characters)
lxqt-session @ 0.15.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 1366, column 0
gtkspell3 @ 3.0.10inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
librsvg @ 2.50.1formatting

Look for formatting issues in the source

line 3387 is way too long (104 characters)
gnome-initial-setup @ 3.32.1formatting

Look for formatting issues in the source

line 1395 is way too long (91 characters)
fstrcmp @ 0.7.D001description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 236
diffoscope @ 161formatting

Look for formatting issues in the source

line 129 is way too long (102 characters)
python @ 3.8.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 837 is way too long (91 characters)
krona-tools @ 2.7formatting

Look for formatting issues in the source

trailing white space on line 1097
kdelibs4support @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
plasma-framework @ 5.70.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2825 is way too long (113 characters)
kcmutils @ 5.70.0formatting

Look for formatting issues in the source

line 2297 is way too long (113 characters)
guile3.0-ncurses-with-gpm @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-sjson @ 0.2.1description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-email @ 0.2.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
guile2.2-gi @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile-gi @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
guile-dbi @ 2.1.6formatting

Look for formatting issues in the source

line 1372 is way too long (94 characters)
kuserfeedback @ 1.0.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
raspi-arm64-chainloader @ 0.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 137 is way too long (102 characters)
r-yapsa @ 1.14.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-mixomics @ 6.12.2description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-biosigner @ 1.16.0description

Validate package descriptions

use @code or similar ornament instead of quotes
r-bioassayr @ 1.26.0description

Validate package descriptions

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

Look for formatting issues in the source

line 7178 is way too long (92 characters)
r-monocle @ 2.16.0formatting

Look for formatting issues in the source

line 2950 is way too long (101 characters)
r-lumi @ 2.40.0formatting

Look for formatting issues in the source

line 3370 is way too long (95 characters)
r-genomicinteractions @ 1.22.0formatting

Look for formatting issues in the source

line 2172 is way too long (92 characters)
r-tidyr @ 1.1.2description

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-cardata @ 3.0-4description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-squarem @ 2020.5formatting

Look for formatting issues in the source

line 3169 is way too long (91 characters)
r-shiny @ 1.4.0.2formatting

Look for formatting issues in the source

line 1212 is way too long (92 characters)
python-rpy2 @ 3.3.5formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 5702 is way too long (104 characters)
catdoc @ 0.95description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 157
ghc-base-unicode-symbols @ 0.2.3formatting

Look for formatting issues in the source

line 955 is way too long (101 characters)
sonata @ 1.7b1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
mongodb @ 3.4.10source-unstable-tarball

Check for autogenerated tarballs

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

Look for formatting issues in the source

line 771 is way too long (99 characters)
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
ocaml4.07-sexplib @ 0.11.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 304
ocaml4.07-sedlex @ 2.1formatting

Look for formatting issues in the source

line 2267 is way too long (97 characters)
ocaml-dose3 @ 5.0.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1722 is way too long (99 characters)
jimtcl @ 0.80formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
g-golf @ 0.1.0-839.ef83010inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
mkvtoolnix @ 51.0.0formatting

Look for formatting issues in the source

line 906 is way too long (96 characters)
giac @ 1.6.0-31formatting

Look for formatting issues in the source

line 365 is way too long (95 characters)
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.05description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 47
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
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 9346 is way too long (97 characters)
eid-mw @ 5.0.8formatting

Look for formatting issues in the source

line 154 is way too long (97 characters)
eid-mw @ 5.0.8formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ppsspp @ 1.10.3description

Validate package descriptions

use @code or similar ornament instead of quotes
mate-polkit @ 1.24.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
xplanet @ 1.3.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

xplanet-1.3.1-xpUtil-Add2017LeapSecond.cpp.patch: file name is too long
wavemon @ 0.9.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
plasma-framework @ 5.70.1patch-file-names

Validate file names and availability of patches

plasma-framework-fix-KF5PlasmaMacros.cmake.patch: file name is too long
pjproject-jami @ 2.10patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

mongodb-support-unknown-linux-distributions.patch: file name is too long
mkbootimg @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mingw-w64-x86_64-winpthreads @ 7.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 @ 7.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 @ 7.0.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

libgeotiff-adapt-test-script-for-proj-6.2.patch: file name is too long
libgccjit @ 9.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libchop @ 0.5.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libcanberra-gtk2 @ 0.30patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
jfsutils-static @ 1.1.15patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
idutils @ 4.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
icu4c-build-root @ 66.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
guile2.2-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-readline @ 2.2.7patch-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
guile2.2-gnutls @ 3.6.12patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
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.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.6.12patch-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
guile-static-stripped-tarball @ 2.0.14patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gtk+ @ 2.24.32patch-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
gnutls-dane @ 3.6.12patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
enlightenment-wayland @ 0.24.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-erlang @ 21.3.8.13patch-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.5.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.5-libsanitizer-mode-field.patch: file name is too long
boost-with-python3 @ 1.72.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
zeitgeist @ 1.0.3formatting

Look for formatting issues in the source

tabulation on line 750, column 18
zeitgeist @ 1.0.3formatting

Look for formatting issues in the source

tabulation on line 753, column 18
texlive-ruhyphen @ 51265formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2306 is way too long (93 characters)
texlive-hyph-utf8 @ 51265formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2127 is way too long (95 characters)
minizip @ 1.2.11formatting

Look for formatting issues in the source

line 154 is way too long (115 characters)
gnome-keyring @ 3.34.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3088 is way too long (91 characters)
tor @ 0.4.4.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 574
julia @ 1.5.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 475 is way too long (92 characters)
emacs-clang-rename @ 9.0.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

clang-runtime-3.9-libsanitizer-mode-field.patch: file name is too long
clang-runtime @ 3.8.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 369 is way too long (91 characters)
rapicorn @ 16.0.0inputs-should-be-native

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

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

Validate file names and availability of patches

file names of patches should start with the package name
geany @ 1.37formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
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
love-nuklear @ v2.6-1.fef4e00formatting

Look for formatting issues in the source

trailing white space on line 724
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
lua5.2-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
debops @ 1.1.0patch-file-names

Validate file names and availability of patches

debops-constants-for-external-program-names.patch: file name is too long
lua-tablepool @ 0.01formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 909 is way too long (95 characters)
python2-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1129 is way too long (96 characters)
python-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1096 is way too long (94 characters)
fc-host-tools @ 13formatting

Look for formatting issues in the source

line 1220 is way too long (122 characters)
lpsolve @ 5.5.2.5description

Validate package descriptions

description should start with an upper-case letter or digit
opencascade-occt @ 7.3.0p3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'texinfo' should probably be a native input
arpack-ng @ 3.3.0source-unstable-tarball

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
netcdf-parallel-openmpi @ 4.7.4patch-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
hdf5-parallel-openmpi @ 1.10.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
hdf4-alt @ 4.2.14patch-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
dsfmt @ 2.2.3patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 3053, column 0
sundials-openmpi @ 3.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2645 is way too long (92 characters)
scalapack @ 2.0.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 3250, column 0
pt-scotch @ 6.0.6formatting

Look for formatting issues in the source

tabulation on line 3228, column 0
petsc @ 3.11.2formatting

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 3314, column 0
mumps-openmpi @ 5.2.1formatting

Look for formatting issues in the source

tabulation on line 2874, column 0
mumps @ 5.2.1formatting

Look for formatting issues in the source

line 2788 is way too long (94 characters)
hypre-openmpi @ 2.15.1formatting

Look for formatting issues in the source

tabulation on line 4532, column 0
hdf-java @ 3.3.2formatting

Look for formatting issues in the source

line 1281 is way too long (92 characters)
clapack @ 3.2.1formatting

Look for formatting issues in the source

line 855 is way too long (91 characters)
abseil-cpp @ 20200225.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 620 is way too long (144 characters)
libsecp256k1 @ 20191213-1.d644ddaformatting

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'flex' should probably be a native input
gobject-introspection @ 1.62.0patch-file-names

Validate file names and availability of patches

gobject-introspection-absolute-shlib-path.patch: file name is too long
telepathy-glib @ 0.24.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 796 is way too long (95 characters)
appstream-glib @ 0.7.18formatting

Look for formatting issues in the source

line 1030 is way too long (93 characters)
icecat @ 78.5.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 859 is way too long (102 characters)
icecat @ 78.5.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 951 is way too long (139 characters)
icecat @ 78.5.0-guix0-preview1formatting

Look for formatting issues in the source

line 957 is way too long (95 characters)
icecat @ 78.5.0-guix0-preview1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1001 is way too long (94 characters)
icecat @ 78.5.0-guix0-preview1formatting

Look for formatting issues in the source

line 1003 is way too long (95 characters)
icecat @ 78.5.0-guix0-preview1formatting

Look for formatting issues in the source

line 1016 is way too long (98 characters)
icecat @ 78.5.0-guix0-preview1formatting

Look for formatting issues in the source

line 1145 is way too long (92 characters)
mailutils @ 3.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
guile2.2-mailutils @ 3.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
guile2.2-mailutils @ 3.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mrrescue @ 1.02edescription

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'swig' should probably be a native input
crawl-tiles @ 0.25.0patch-file-names

Validate file names and availability of patches

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 2902, column 0
einstein @ 2.0formatting

Look for formatting issues in the source

line 4431 is way too long (96 characters)
restinio @ 0.6.1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 3302 is way too long (92 characters)
icedove @ 78.5.0formatting

Look for formatting issues in the source

line 1193 is way too long (98 characters)
icedove @ 78.5.0formatting

Look for formatting issues in the source

line 1348 is way too long (105 characters)
icedove @ 78.5.0formatting

Look for formatting issues in the source

line 1350 is way too long (102 characters)
perl-libxml @ 0.08description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
libxmlplusplus @ 2.40.1description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 2180 is way too long (91 characters)
java-xom @ 127formatting

Look for formatting issues in the source

trailing white space on line 1830
gajim @ 1.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
ublock-origin-chromium @ 1.31.0description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
python-tempest-lib @ 1.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-reno @ 2.7.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python2-mox3 @ 0.24.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
vim-full @ 8.2.2017formatting

Look for formatting issues in the source

line 228 is way too long (94 characters)
ghc-hxt-unicode @ 9.0.2.4description

Validate package descriptions

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

Validate package descriptions

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

Look for formatting issues in the source

line 1485 is way too long (91 characters)
python-mypy @ 0.782description

Validate package descriptions

use @code or similar ornament instead of quotes
python-robber @ 1.1.5inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-pytest-vcr @ 1.0.2-1.4d6c7b3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
tuxpaint @ 0.9.23patch-headers

Validate patch headers

tuxpaint-stamps-path.patch: patch lacks comment and upstream status
tcsh @ 6.22.02patch-headers

Validate patch headers

tcsh-fix-autotest.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
pinball @ 0.3.1patch-headers

Validate patch headers

pinball-const-fix.patch: patch lacks comment and upstream status
pinball @ 0.3.1patch-headers

Validate patch headers

pinball-system-ltdl.patch: patch lacks comment and upstream status
ocaml-dose3 @ 5.0.1patch-headers

Validate patch headers

ocaml-dose3-dont-make-printconf.patch: patch lacks comment and upstream status
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
netcdf-parallel-openmpi @ 4.7.4patch-headers

Validate patch headers

netcdf-date-time.patch: patch lacks comment and upstream status
netcdf @ 4.7.4patch-headers

Validate patch headers

netcdf-date-time.patch: patch lacks comment and upstream status
mono @ 4.4.1.0patch-headers

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

libmhash-hmac-fix-uaf.patch: patch lacks comment and upstream status
hdf5 @ 1.8.21patch-headers

Validate patch headers

hdf5-1.8-mpi-deprecations.patch: patch lacks comment and upstream status
gobject-introspection @ 1.62.0patch-headers

Validate patch headers

gobject-introspection-girepository.patch: patch lacks comment and upstream status
gajim @ 1.2.2patch-headers

Validate patch headers

gajim-honour-GAJIM_PLUGIN_PATH.patch: patch lacks comment and upstream status
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 505, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 506, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 507, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 508, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 509, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 510, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 511, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 512, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 513, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 515, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 516, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 517, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 518, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 519, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 521, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 522, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 523, column 0
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 524, column 0
quaternion @ 0.0.9.4einputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
musl-cross @ 0.1-3.a8a6649formatting

Look for formatting issues in the source

line 152 is way too long (92 characters)
rust-serde-urlencoded @ 0.6.1description

Validate package descriptions

description should start with an upper-case letter or digit
rust-rustc-tools-util @ 0.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
rust-libnghttp2-sys @ 0.1.4+1.41.0inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 2189 is way too long (114 characters)
rust-parking-lot @ 0.11.0formatting

Look for formatting issues in the source

line 17956 is way too long (102 characters)
rust-packed-struct @ 0.3.0formatting

Look for formatting issues in the source

tabulation on line 33793, column 0
rust-packed-struct @ 0.3.0formatting

Look for formatting issues in the source

tabulation on line 33795, column 0
rust-packed-struct @ 0.3.0formatting

Look for formatting issues in the source

tabulation on line 33796, column 0
rust-nix @ 0.15.0formatting

Look for formatting issues in the source

line 16117 is way too long (93 characters)
rust-inflections @ 1.1.1formatting

Look for formatting issues in the source

line 33894 is way too long (107 characters)
rust-inflections @ 1.1.1formatting

Look for formatting issues in the source

line 33896 is way too long (107 characters)
rust-gimli @ 0.20.0formatting

Look for formatting issues in the source

line 10172 is way too long (91 characters)
rust-bitstream-io @ 0.8.5formatting

Look for formatting issues in the source

line 2238 is way too long (111 characters)
rust-bitstream-io @ 0.8.5formatting

Look for formatting issues in the source

line 2240 is way too long (111 characters)
rust-async-compression @ 0.3.5formatting

Look for formatting issues in the source

line 1195 is way too long (92 characters)
libvirt-glib @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
qemu-minimal @ 5.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
xen @ 4.14.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
virt-manager @ 2.2.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libosinfo @ 1.7.1formatting

Look for formatting issues in the source

line 928 is way too long (106 characters)
python2-pydot @ 1.4.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
iml @ 1.0.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 798
symmetrica @ 2.0patch-headers

Validate patch headers

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

Look for formatting issues in the source

line 1408 is way too long (100 characters)
gap @ 4.11.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 1042, column 0
js-mathjax @ 2.7.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 393 is way too long (99 characters)
bsd-games @ 2.17.0patch-headers

Validate patch headers

bsd-games-gamescreen.h.patch: patch lacks comment and upstream status
r-seqlogo @ 1.54.3description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'python-cython' should probably be a native input
rseqc @ 3.0.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'bison' should probably be a native input
multiqc @ 1.5inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
clipper @ 2.0inputs-should-be-native

Identify inputs that should be native inputs

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4165 is way too long (117 characters)
discrover @ 1.6.0formatting

Look for formatting issues in the source

line 2920 is way too long (91 characters)
blasr-libcpp @ 5.3.3formatting

Look for formatting issues in the source

line 605 is way too long (95 characters)
emacs-swiper @ 0.13.1description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-pyvenv @ 1.21description

Validate package descriptions

description should start with an upper-case letter or digit
emacs-gdscript-mode @ 1.4.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
emacs-flx @ 0.6.1description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
emacs-dhall-mode @ 0.1.3-1.484bcf8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 89
emacs-undohist-el @ 0-1.d2239a5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-sqlite @ 1.0-0.dad42b8formatting

Look for formatting issues in the source

tabulation on line 4350, column 0
emacs-sqlite @ 1.0-0.dad42b8formatting

Look for formatting issues in the source

tabulation on line 4351, column 0
emacs-mit-scheme-doc @ 20140203formatting

Look for formatting issues in the source

line 5733 is way too long (94 characters)
xwallpaper @ 0.6.5description

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
u-boot-wandboard @ 2020.10description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-vexpress-ca9x4 @ 2020.10description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-rock64-rk3328 @ 2020.10description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-qemu-riscv64 @ 2020.10description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-nintendo-nes-classic-edition @ 2020.10description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-bananapi-m2-ultra @ 2020.10description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
u-boot-am335x-evm @ 2020.10description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
lepton-eda @ 1.9.11-20200604inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
u-boot-qemu-riscv64-smode @ 2020.10patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Look for formatting issues in the source

tabulation on line 1646, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1647, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1649, column 0
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1650, column 0
u-boot-wandboard @ 2020.10formatting

Look for formatting issues in the source

line 668 is way too long (93 characters)
u-boot-vexpress-ca9x4 @ 2020.10formatting

Look for formatting issues in the source

line 668 is way too long (93 characters)
u-boot-tools @ 2020.10formatting

Look for formatting issues in the source

line 536 is way too long (91 characters)
u-boot-tools @ 2020.10formatting

Look for formatting issues in the source

line 558 is way too long (97 characters)
u-boot-sifive-fu540 @ 2020.10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 668 is way too long (93 characters)
u-boot-pinebook @ 2020.10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
u-boot-nintendo-nes-classic-edition @ 2020.10formatting

Look for formatting issues in the source

line 668 is way too long (93 characters)
u-boot-mx6cuboxi @ 2020.10formatting

Look for formatting issues in the source

line 668 is way too long (93 characters)
u-boot-malta @ 2020.10formatting

Look for formatting issues in the source

line 668 is way too long (93 characters)
u-boot-cubietruck @ 2020.10formatting

Look for formatting issues in the source

line 668 is way too long (93 characters)
u-boot-cubieboard @ 2020.10formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 668 is way too long (93 characters)
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 631 is way too long (99 characters)
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
linux-libre-arm-veyron @ 5.9.11patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
tuxmath @ 2.0.3description

Validate package descriptions

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

Look for formatting issues in the source

line 578 is way too long (99 characters)
childsplay @ 3.4formatting

Look for formatting issues in the source

line 487 is way too long (92 characters)
zathura-pdf-poppler @ 0.3.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 473 is way too long (93 characters)
ghc-unsafe @ 0.0description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ghc-tasty-expected-failure @ 0.11.1.2description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
ecasound @ 2.9.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471
tao @ 1.0-beta-10May2006inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
tao @ 1.0-beta-10May2006inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'libtool' should probably be a native input
qucs @ 0.0.19-0.b4f27d9inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'libtool' should probably be a native input
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
tensorflow @ 1.9.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
qucs-s @ 0.0.21source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
pandoc @ 2.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
openmpi-thread-multiple @ 4.0.5patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
aegis @ 4.24patch-headers

Validate patch headers

aegis-perl-tempdir2.patch: patch lacks comment and upstream status
zita-resampler @ 1.6.2formatting

Look for formatting issues in the source

line 3719 is way too long (93 characters)
vamp @ 2.6formatting

Look for formatting issues in the source

line 3197 is way too long (94 characters)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1132 is way too long (92 characters)
openmpi @ 4.0.5formatting

Look for formatting issues in the source

line 264 is way too long (94 characters)
openmpi @ 4.0.5formatting

Look for formatting issues in the source

line 266 is way too long (96 characters)
meshlab @ 2020.06formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
git-crypt @ 0.6.0formatting

Look for formatting issues in the source

line 778 is way too long (91 characters)
ghc-xdg-basedir @ 0.2.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 13003 is way too long (250 characters)
freehdl @ 0.0.8formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1722 is way too long (95 characters)
bazaar @ 2.7.0formatting

Look for formatting issues in the source

line 149 is way too long (93 characters)
audacity @ 2.4.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python-faiss @ 1.5.0inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
openssh-sans-x @ 8.4p1patch-file-names

Validate file names and availability of patches

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

Validate patch headers

lsh-fix-x11-forwarding.patch: patch lacks comment and upstream status
php @ 7.4.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 227 is way too long (92 characters)
php @ 7.4.13formatting

Look for formatting issues in the source

line 228 is way too long (96 characters)
php @ 7.4.13formatting

Look for formatting issues in the source

line 233 is way too long (96 characters)
php @ 7.4.13formatting

Look for formatting issues in the source

line 275 is way too long (91 characters)
php @ 7.4.13formatting

Look for formatting issues in the source

line 288 is way too long (92 characters)
sooperlooper @ 1.7.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
sorcer @ 1.1.3source-unstable-tarball

Check for autogenerated tarballs

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

Validate file names and availability of patches

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

Look for formatting issues in the source

line 2555 is way too long (91 characters)
solfege @ 3.22.2formatting

Look for formatting issues in the source

line 1710 is way too long (92 characters)
rosegarden @ 20.06formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
gtklick @ 0.6.4formatting

Look for formatting issues in the source

line 1145 is way too long (94 characters)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5088, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5089, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5090, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5091, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5093, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5100, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5101, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5102, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5103, column 0
drumstick @ 1.1.3formatting

Look for formatting issues in the source

line 2510 is way too long (91 characters)
beets-bandcamp @ 0.1.3formatting

Look for formatting issues in the source

line 3459 is way too long (149 characters)
python2-html2text @ 2019.8.11description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-trezor-agent @ 0.13.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
electron-cash @ 4.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
emacs-beancount @ 2.2.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
pan @ 0.146description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
sendmail @ 8.15.2inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
notifymuch @ 0.1-1.9d4aaf5inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
alot @ 0.9.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
python-hyperkitty @ 1.3.3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-django@2.2.17 and python-django@3.1.3 collide
python-mailman-hyperkitty @ 1.1.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python-mailman-hyperkitty @ 1.1.0formatting

Look for formatting issues in the source

line 3333 is way too long (168 characters)
emacs-xwidgets @ 27.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
xfce4-volumed-pulse @ 0.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
gnome-shell-extension-gsconnect @ 33inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
xfce4-clipman-plugin @ 1.6.1formatting

Look for formatting issues in the source

line 444 is way too long (91 characters)
tumbler @ 0.2.9formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
python-requests @ 2.20.1profile-collisions

Report collisions that would occur due to propagated inputs

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

Look for formatting issues in the source

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
sky @ 1.2description

Validate package descriptions

use @code or similar ornament instead of quotes
nudoku @ 2.1.0source-file-name

Validate file names of sources

the source file name should contain the package name
gzdoom @ 4.3.2patch-headers

Validate patch headers

gzdoom-find-system-libgme.patch: patch lacks comment and upstream status
sky @ 1.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9613 is way too long (100 characters)
queen-it @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9414 is way too long (205 characters)
queen-fr @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9414 is way too long (205 characters)
queen-de @ 1.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9414 is way too long (205 characters)
queen @ 1.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9414 is way too long (205 characters)
lure-it @ 1.1formatting

Look for formatting issues in the source

line 9314 is way too long (93 characters)
lure-fr @ 1.1formatting

Look for formatting issues in the source

line 9314 is way too long (93 characters)
lure-es @ 1.1formatting

Look for formatting issues in the source

line 9314 is way too long (93 characters)
lure-de @ 1.1formatting

Look for formatting issues in the source

line 9314 is way too long (93 characters)
lure @ 1.1formatting

Look for formatting issues in the source

line 9314 is way too long (93 characters)
freeorion @ 0.4.10formatting

Look for formatting issues in the source

line 9698 is way too long (92 characters)
drascula @ 1.0formatting

Look for formatting issues in the source

line 9211 is way too long (93 characters)
drascula @ 1.0formatting

Look for formatting issues in the source

line 9215 is way too long (93 characters)
btanks @ 0.9.8083formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 8256, column 18
btanks @ 0.9.8083formatting

Look for formatting issues in the source

tabulation on line 8257, column 17
emacs-vcsh @ 0.4.4description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-trashed @ 1.9.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 178
emacs-nhexl-mode @ 1.5description

Validate package descriptions

use @code or similar ornament instead of quotes
emacs-hercules @ 0.2.1description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
emacs-exwm-no-x-toolkit @ 0.24patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-telega @ 0.6.28-0.e539967formatting

Look for formatting issues in the source

line 23631 is way too long (99 characters)
emacs-telega @ 0.6.28-0.e539967formatting

Look for formatting issues in the source

tabulation on line 23653, column 0
emacs-telega @ 0.6.28-0.e539967formatting

Look for formatting issues in the source

tabulation on line 23654, column 0
emacs-telega @ 0.6.28-0.e539967formatting

Look for formatting issues in the source

tabulation on line 23657, column 0
emacs-telega @ 0.6.28-0.e539967formatting

Look for formatting issues in the source

tabulation on line 23661, column 0
emacs-powershell @ 0.3-0.d1b3f95formatting

Look for formatting issues in the source

tabulation on line 13527, column 0
emacs-powershell @ 0.3-0.d1b3f95formatting

Look for formatting issues in the source

tabulation on line 13528, column 0
emacs-gtk-look @ 29formatting

Look for formatting issues in the source

line 19610 is way too long (94 characters)
emacs-exwm @ 0.24formatting

Look for formatting issues in the source

line 11923 is way too long (96 characters)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12266, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12267, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12270, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12271, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12283, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12284, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12285, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12286, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12287, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12288, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12289, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12290, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12291, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12292, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12293, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12294, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12295, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12296, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12297, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12298, column 0
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 12299, column 0
emacs-dash-docs @ 1.4.0-1.111fd9bformatting

Look for formatting issues in the source

line 21972 is way too long (91 characters)
libmypaint @ 1.5.1inputs-should-be-native

Identify inputs that should be native inputs

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

Look for formatting issues in the source

line 498 is way too long (107 characters)
xdg-user-dirs @ 0.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
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
samblaster @ 0.1.24description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
r-xyz @ 0.2description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 105, 128
r-topicmodels @ 0.2-11description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 151
r-systemfonts @ 0.3.2description

Validate package descriptions

use @code or similar ornament instead of quotes
r-survminer @ 0.4.8description

Validate package descriptions

use @code or similar ornament instead of quotes
r-sapa @ 2.0-2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 97, 120
r-rstan @ 2.21.2description

Validate package descriptions

use @code or similar ornament instead of quotes
r-r2glmm @ 0.1.2description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-iml @ 0.10.0description

Validate package descriptions

use @code or similar ornament instead of quotes
r-iheatmapr @ 0.5.1description

Validate package descriptions

description should start with an upper-case letter or digit
r-hapassoc @ 1.2-8description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-diagram @ 1.6.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 336
r-cmprsk @ 2.2-10description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 98, 123
r-bseqsc @ 1.0-1.fef3f3edescription

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
r-brms @ 2.14.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 109, 532, 653, 784
r-bootstrap @ 2019.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 92, 105
r-arm @ 1.11-2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 46, 60
qtwebglplugin @ 5.14.2description

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 107, 250
qtcharts @ 5.14.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-psycopg2 @ 2.8.6description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python2-cryptography @ 3.1.1description

Validate package descriptions

description should start with an upper-case letter or digit
python2-ccm @ 2.1.6description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-pytest-subtesthack @ 0.1.1description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
python-psycopg2 @ 2.8.6description

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
python-cryptography @ 3.1.1description

Validate package descriptions

description should start with an upper-case letter or digit
python-ccm @ 2.1.6description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
perftest @ 4.4-0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
openjpeg-data @ 2020.05.19description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
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
i3-wm @ 4.18.3description

Validate package descriptions

description should start with an upper-case letter or digit
guile-wiredtiger @ 0.7.0description

Validate package descriptions

use @code or similar ornament instead of quotes
go-github.com-smartystreets-goconvey @ 1.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 33
go-github-com-muesli-termenv @ 0.7.0description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
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
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
c-blosc @ 1.18.1description

Validate package descriptions

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
python2-testtools @ 2.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
python2-testscenarios @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
python2-testresources @ 2.0.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python2-pytest-xdist @ 1.25.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-httpbin @ 0.2.3inputs-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-pyqt @ 5.14.2inputs-should-be-native

Identify inputs that should be native inputs

'qttools' 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-guzzle-sphinx-theme @ 0.7.11inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python2-pbr' should probably be a native input
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
python2-clf @ 0.5.7inputs-should-be-native

Identify inputs that should be native inputs

'python2-nose' should probably be a native input
python-velocyto @ 0.17.17inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
python-testtools @ 2.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-testscenarios @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-testresources @ 2.0.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-pytest-xprocess @ 0.9.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-xdist @ 1.25.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.3.4inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-lazy-fixture @ 0.6.3inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-forked @ 1.1.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-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-pyqt-without-qtwebkit @ 5.14.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'qttools' should probably be a native input
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-guzzle-sphinx-theme @ 0.7.11inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-cov-core @ 1.15.0inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-codecov @ 2.0.15inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-breathe @ 4.22.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-bbknn @ 1.3.6inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
lollypop @ 1.4.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
keybinder-3.0 @ 0.3.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
go-github-com-wtolson-go-taglib @ 0.0.0-0.6e68349inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
gnome-tweaks @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-docutils' 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
python-sphinx-copybutton @ 0.2.6inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
sqlcipher @ 3.4.2source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-xerial-core @ 2.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-stringtemplate @ 4.0.8source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-plexus-archiver @ 4.2.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-tinybundles @ 2.1.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core-spi @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core-junit @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-ops4j-pax-exam-core @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-native-access-platform @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-native-access @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-mvel2 @ 2.3.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-microemulator-cldc @ 2.0.4source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-joda-time @ 2.9.9source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-joda-convert @ 1.9.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jline @ 2.14.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jline @ 1.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-jms-api-spec @ 2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-interceptors-api-spec @ 1.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jboss-el-api-spec @ 3.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jansi-native @ 1.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-jansi @ 1.16source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-modules-base-mrbean @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-fasterxml-jackson-modules-base-jaxb @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

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

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
java-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
linux-libre-riscv64-generic @ 5.9.11derivation

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
linux-libre-bpf @ 5.9.11derivation

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
linux-libre @ 5.9.11derivation

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
linux-libre @ 5.4.80derivation

Report failure to compile a package to a derivation

failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux'
maven-wagon-provider-api @ 3.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/hyi21wbh8vfs1v3cy162g4rz457yli9r-maven-wagon-provider-api-3.3.4 and /gnu/store/dd25ffafrqxiwi7ly20vn6kkvd3sq9jb-maven-wagon-provider-api-3.3.4 collide
java-plexus-sec-dispatcher @ 1.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide
java-plexus-digest @ 1.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@3.1 collide
java-plexus-container-default @ 1.7.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide
java-plexus-component-metadata @ 1.7.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs 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
xorg-server-xwayland @ 1.20.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
x86-energy-perf-policy @ 5.9.11patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-riscv64-generic @ 5.9.11patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-mips64el-fuloong2e @ 5.9.11patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm64-generic @ 5.9.11patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
linux-libre-arm64-generic @ 5.4.80patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
java-tunnelvisionlabs-antlr4-runtime-annotations @ 4.7.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-tunnelvisionlabs-antlr4-runtime-annotations @ 4.7.4patch-file-names

Validate file names and availability of patches

java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long
java-tunnelvisionlabs-antlr4-runtime @ 4.7.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-tunnelvisionlabs-antlr4-runtime @ 4.7.4patch-file-names

Validate file names and availability of patches

java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long
java-tunnelvisionlabs-antlr4 @ 4.7.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-tunnelvisionlabs-antlr4 @ 4.7.4patch-file-names

Validate file names and availability of patches

java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long
java-powermock-reflect @ 1.7.3patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
java-openjfx-media @ 8.202patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-openjfx-graphics @ 8.202patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-openjfx-base @ 8.202patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-apache-ivy @ 2.4.0patch-file-names

Validate file names and availability of patches

java-apache-ivy-port-to-latest-bouncycastle.patch: file name is too long
java-antlr4-runtime @ 4.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
http-parser @ 2.9.4patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gdb-arm-none-eabi @ 9.2patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
cpupower @ 5.9.11patch-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
steghide @ 0.5.1patch-headers

Validate patch headers

steghide-fixes.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
netsurf @ 3.10patch-headers

Validate patch headers

netsurf-message-timestamp.patch: patch lacks comment and upstream status
xproto @ 7.0.31formatting

Look for formatting issues in the source

line 4988 is way too long (91 characters)
xpra @ 4.0.5formatting

Look for formatting issues in the source

tabulation on line 6320, column 0
xf86-video-intel @ 2.99.917-17.ad5540fformatting

Look for formatting issues in the source

line 3025 is way too long (91 characters)
wireless-tools @ 30.pre9formatting

Look for formatting issues in the source

line 3547 is way too long (104 characters)
vcflib @ 1.0.1formatting

Look for formatting issues in the source

line 15380 is way too long (92 characters)
varnish @ 6.5.1formatting

Look for formatting issues in the source

line 5843 is way too long (91 characters)
util-linux @ 2.35.1formatting

Look for formatting issues in the source

line 1516 is way too long (91 characters)
upower @ 0.99.11formatting

Look for formatting issues in the source

line 5247 is way too long (110 characters)
serf @ 1.3.9formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 137 is way too long (96 characters)
salmon @ 0.13.1formatting

Look for formatting issues in the source

line 11948 is way too long (99 characters)
rust @ 1.26.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 747 is way too long (91 characters)
r-haplo-stats @ 1.8.6formatting

Look for formatting issues in the source

line 14314 is way too long (103 characters)
r-gamlss-dist @ 5.1-7formatting

Look for formatting issues in the source

line 12896 is way too long (91 characters)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 15538 is way too long (96 characters)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 15552 is way too long (96 characters)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 15559 is way too long (117 characters)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 15566 is way too long (100 characters)
r-colourpicker @ 1.1.0formatting

Look for formatting issues in the source

line 13005 is way too long (94 characters)
r-abps @ 0.3formatting

Look for formatting issues in the source

line 8368 is way too long (93 characters)
qtserialport @ 5.14.2formatting

Look for formatting issues in the source

line 1044 is way too long (115 characters)
qtsensors @ 5.14.2formatting

Look for formatting issues in the source

line 893 is way too long (97 characters)
qtremoteobjects @ 5.14.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 579 is way too long (94 characters)
python2-wtforms @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4017 is way too long (100 characters)
python-wtforms @ 2.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 4017 is way too long (100 characters)
python-pyqt @ 5.14.2formatting

Look for formatting issues in the source

line 2061 is way too long (105 characters)
plymouth @ 0.9.4formatting

Look for formatting issues in the source

line 1925 is way too long (91 characters)
phast @ 1.5formatting

Look for formatting issues in the source

tabulation on line 15666, column 30
perftest @ 4.4-0.4formatting

Look for formatting issues in the source

line 5462 is way too long (98 characters)
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2383, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2384, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2385, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2386, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2387, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2388, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2389, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2390, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2391, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2396, column 0
openjdk @ 14.0formatting

Look for formatting issues in the source

tabulation on line 2397, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2341, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2342, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2343, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2344, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2345, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2346, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2347, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2348, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2349, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2350, column 0
openjdk @ 13.0formatting

Look for formatting issues in the source

tabulation on line 2351, column 0
mesa @ 20.1.9formatting

Look for formatting issues in the source

line 297 is way too long (120 characters)
localed @ 241formatting

Look for formatting issues in the source

line 713 is way too long (96 characters)
linux-pam @ 1.4.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
linux-libre-riscv64-generic @ 5.9.11formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre-mips64el-fuloong2e @ 5.9.11formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre-arm64-generic @ 5.9.11formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre-arm64-generic @ 5.4.80formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre @ 5.9.11formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre @ 5.4.80formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre @ 4.9.246formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre @ 4.4.246formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre @ 4.19.160formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
linux-libre @ 4.14.209formatting

Look for formatting issues in the source

line 814 is way too long (117 characters)
libsoup @ 2.70.0formatting

Look for formatting issues in the source

line 4704 is way too long (128 characters)
libsoup @ 2.70.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libjxr @ 1.1formatting

Look for formatting issues in the source

line 515 is way too long (95 characters)
java-testng @ 6.14.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9247 is way too long (110 characters)
java-openjfx-base @ 8.202formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2625 is way too long (99 characters)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

line 12250 is way too long (92 characters)
java-native-access @ 4.5.1formatting

Look for formatting issues in the source

line 12430 is way too long (91 characters)
java-logback-classic @ 1.2.3formatting

Look for formatting issues in the source

line 13009 is way too long (102 characters)
java-joda-time @ 2.9.9formatting

Look for formatting issues in the source

line 11921 is way too long (92 characters)
java-jnacl @ 0.1.0-2.094e819formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 10677 is way too long (92 characters)
java-jgit @ 4.2.0.201601211800-rformatting

Look for formatting issues in the source

line 13112 is way too long (93 characters)
java-hawtjni @ 1.15formatting

Look for formatting issues in the source

line 11577 is way too long (92 characters)
java-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 9658 is way too long (93 characters)
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 7272, column 20
java-eclipse-sisu-plexus @ 0.3.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 6046 is way too long (93 characters)
java-commons-httpclient @ 3.1formatting

Look for formatting issues in the source

line 12292 is way too long (91 characters)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

line 5814 is way too long (91 characters)
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

line 9432 is way too long (91 characters)
java-apache-ivy @ 2.4.0formatting

Look for formatting issues in the source

line 12650 is way too long (101 characters)
ipset @ 7.9formatting

Look for formatting issues in the source

line 7606 is way too long (91 characters)
icedtea @ 3.7.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2966 is way too long (93 characters)
go-github-com-mitchellh-go-homedir @ 1.0.0-0.ae18d6bformatting

Look for formatting issues in the source

line 2853 is way too long (95 characters)
go-github-com-mattn-go-shellwords @ 1.0.5-1.2444a32formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 2758 is way too long (93 characters)
go-github-com-libp2p-go-libp2p-metrics @ 2.1.6-0.a10ff6eformatting

Look for formatting issues in the source

line 2814 is way too long (93 characters)
go-github-com-libp2p-go-libp2p-metrics @ 2.1.6-0.a10ff6eformatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1306 is way too long (164 characters)
go-github-com-davecgh-go-spew @ 1.1.1formatting

Look for formatting issues in the source

line 2421 is way too long (129 characters)
gdm @ 3.34.1formatting

Look for formatting issues in the source

line 8063 is way too long (103 characters)
freebayes @ 1.0.2-1.3ce827dformatting

Look for formatting issues in the source

tabulation on line 15455, column 28
fastahack @ 1.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 137 is way too long (96 characters)
dropseq-tools @ 1.13formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 12527, column 0
crda @ 3.18formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 137 is way too long (96 characters)
antlr4 @ 4.8formatting

Look for formatting issues in the source

line 8304 is way too long (96 characters)
antlr4 @ 4.8formatting

Look for formatting issues in the source

line 8378 is way too long (100 characters)
mosquitto @ 1.6.12description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 68