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
zn-poly @ 0.9.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/sagemath.scm (line: 296, column: 17)
wxwidgets-gtk2 @ 3.1.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/wxwidgets.scm (line: 186, column: 2)
wxwidgets-gtk2 @ 3.0.5.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/wxwidgets.scm (line: 155, column: 2)
robin-map @ 0.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 281
  • gnu/packages/datastructures.scm (line: 365, column: 17)
rcm @ 1.3.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 183
  • gnu/packages/rcm.scm (line: 54, column: 17)
python-wxpython @ 4.0.7.post1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/wxwidgets.scm (line: 246, column: 17)
perl6-grammar-debugger @ 1.0.1-1.0375008description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 203
  • gnu/packages/perl6.scm (line: 253, column: 19)
perl-test-file-contents @ 0.23description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/perl-check.scm (line: 634, column: 5)
kget @ 20.04.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 169
  • gnu/packages/kde-internet.scm (line: 169, column: 17)
java-jblas @ 1.2.4description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/java-maths.scm (line: 86, column: 5)
go-github.com-smartystreets-goconvey @ 1.6.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 33
  • gnu/packages/check.scm (line: 682, column: 5)
ghc-tasty-expected-failure @ 0.11.1.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 185
  • gnu/packages/haskell-check.scm (line: 399, column: 5)
ghc-operational @ 0.2.3.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
  • gnu/packages/haskell-xyz.scm (line: 8961, column: 5)
ghc-llvm-hs-pure @ 9.0.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/haskell-xyz.scm (line: 7388, column: 17)
ghc-llvm-hs @ 9.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/haskell-xyz.scm (line: 7423, column: 17)
ghc-inline-c @ 0.7.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/haskell-xyz.scm (line: 6495, column: 5)
ghc-hxt-unicode @ 9.0.2.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 158
  • gnu/packages/haskell-web.scm (line: 1490, column: 5)
ghc-gtk2hs-buildtools @ 0.13.5.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 95, 367
  • gnu/packages/haskell-xyz.scm (line: 5164, column: 5)
ghc-fsnotify @ 0.3.0.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 81
  • gnu/packages/haskell-xyz.scm (line: 4699, column: 17)
ghc-doclayout @ 0.3description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/haskell-xyz.scm (line: 9221, column: 5)
ghc-aeson-qq @ 0.8.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/haskell-web.scm (line: 1088, column: 5)
fstrcmp @ 0.7.D001description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 236
  • gnu/packages/kodi.scm (line: 265, column: 5)
shogun @ 6.1.3inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
  • gnu/packages/machine-learning.scm (line: 553, column: 5)
python2-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
  • gnu/packages/check.scm (line: 1101, column: 2)
python2-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1101, column: 2)
python2-nose2 @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest-cov' should probably be a native input
  • gnu/packages/check.scm (line: 869, column: 2)
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
  • gnu/packages/ada.scm (line: 152, column: 4)
python-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
  • gnu/packages/check.scm (line: 1101, column: 2)
python-pytest-cov @ 2.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1101, column: 2)
python-nose2 @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
  • gnu/packages/check.scm (line: 869, column: 2)
python-debtcollector @ 1.19.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/openstack.scm (line: 111, column: 2)
presentty @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/presentation.scm (line: 74, column: 5)
openfoam @ 4.1inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
  • gnu/packages/simulation.scm (line: 87, column: 5)
mig @ 1.8inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
  • gnu/packages/hurd.scm (line: 133, column: 12)
lxqt @ 0.15.0inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
  • gnu/packages/lxqt.scm (line: 1377, column: 2)
flex @ 2.6.4inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
  • gnu/packages/flex.scm (line: 47, column: 5)
flex @ 2.6.4inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
  • gnu/packages/flex.scm (line: 47, column: 5)
cinnamon-desktop @ 3.4.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/cinnamon.scm (line: 56, column: 5)
bison @ 3.6.3inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
  • gnu/packages/bison.scm (line: 72, column: 2)
bison @ 3.6.3inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
  • gnu/packages/bison.scm (line: 72, column: 2)
bison @ 3.5.3inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
  • gnu/packages/bison.scm (line: 58, column: 12)
bison @ 3.5.3inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
  • gnu/packages/bison.scm (line: 58, column: 12)
bison @ 3.0.5inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
  • gnu/packages/bison.scm (line: 83, column: 2)
bison @ 3.0.5inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
  • gnu/packages/bison.scm (line: 83, column: 2)
aseba @ 1.6.0-0.3b35de8inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
  • gnu/packages/robotics.scm (line: 107, column: 7)
rdmd @ 2.077.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/dlang.scm (line: 50, column: 12)
infiniband-diags @ 2.0.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/fabric-management.scm (line: 97, column: 5)
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'
  • gnu/packages/hurd.scm (line: 568, column: 4)
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'
  • gnu/packages/hurd.scm (line: 356, column: 2)
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'
  • gnu/packages/hurd.scm (line: 304, column: 2)
python2-unittest2 @ 1.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/check.scm (line: 898, column: 2)
python2-pycrypto @ 2.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python-crypto.scm (line: 337, column: 4)
pandoc @ 2.7.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/haskell-xyz.scm (line: 9315, column: 2)
mkbootimg @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/android.scm (line: 402, column: 2)
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
  • gnu/packages/maven.scm (line: 1205, column: 2)
maven-settings-builder @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 2146, column: 2)
maven-settings @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 1156, column: 2)
maven-settings @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 2133, column: 2)
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
  • gnu/packages/maven.scm (line: 1343, column: 2)
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
  • gnu/packages/maven.scm (line: 1293, column: 2)
maven-repository-metadata @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 2211, column: 2)
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
  • gnu/packages/maven.scm (line: 1378, column: 2)
maven-plugin-api @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 2183, column: 2)
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
  • gnu/packages/maven.scm (line: 1238, column: 2)
maven-model-builder @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 2164, column: 2)
maven-model @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 1077, column: 2)
maven-model @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 2081, column: 2)
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
  • gnu/packages/maven.scm (line: 2699, column: 2)
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
  • gnu/packages/maven.scm (line: 2726, column: 2)
maven-embedder @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 1607, column: 2)
maven-compat @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 1703, column: 2)
maven-compat @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 2359, column: 2)
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
  • gnu/packages/maven.scm (line: 1128, column: 2)
maven-artifact @ 3.6.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 1052, column: 2)
maven-artifact @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 2068, column: 2)
maven-aether-provider @ 3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maven.scm (line: 2224, column: 2)
libmhash @ 0.9.9.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/mcrypt.scm (line: 86, column: 2)
libcanberra-gtk2 @ 0.30patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/libcanberra.scm (line: 108, column: 2)
kodi-wayland @ 18.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/kodi.scm (line: 470, column: 2)
jfsutils-static @ 1.1.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • guix/build-system/gnu.scm (line: 214, column: 2)
idutils @ 4.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/idutils.scm (line: 29, column: 2)
icu4c-build-root @ 66.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/icu4c.scm (line: 134, column: 2)
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
  • gnu/packages/make-bootstrap.scm (line: 816, column: 2)
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
  • gnu/packages/make-bootstrap.scm (line: 755, column: 2)
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
  • gnu/packages/make-bootstrap.scm (line: 755, column: 2)
grub-minimal @ 2.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 253, column: 2)
grub-hybrid @ 2.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 328, column: 2)
grub-efi @ 2.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 284, column: 2)
fastboot @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/android.scm (line: 656, column: 2)
emacs-erlang @ 23.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/erlang.scm (line: 227, column: 2)
bash-static @ 5.0.16patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bash.scm (line: 263, column: 4)
bash-minimal @ 5.0.16patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bash.scm (line: 223, column: 2)
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
  • gnu/packages/android.scm (line: 320, column: 2)
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
  • gnu/packages/android.scm (line: 616, column: 2)
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
  • gnu/packages/android.scm (line: 299, column: 2)
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
  • gnu/packages/android.scm (line: 192, column: 2)
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
  • gnu/packages/android.scm (line: 245, column: 2)
adb @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/android.scm (line: 355, column: 2)
shogun @ 6.1.3formatting

Look for formatting issues in the source

line 521 is way too long (91 characters)
  • gnu/packages/machine-learning.scm (line: 521, column: 0)
sdsl-lite @ 2.1.1formatting

Look for formatting issues in the source

line 237 is way too long (145 characters)
  • gnu/packages/datastructures.scm (line: 237, column: 0)
sdl-mixer @ 1.2.12formatting

Look for formatting issues in the source

line 260 is way too long (92 characters)
  • gnu/packages/sdl.scm (line: 260, column: 0)
sdl-image @ 1.2.12formatting

Look for formatting issues in the source

line 223 is way too long (91 characters)
  • gnu/packages/sdl.scm (line: 223, column: 0)
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

line 213 is way too long (106 characters)
  • gnu/packages/sdl.scm (line: 213, column: 0)
raspi-arm64-chainloader @ 0.1formatting

Look for formatting issues in the source

line 211 is way too long (139 characters)
  • gnu/packages/raspberry-pi.scm (line: 211, column: 0)
raspi-arm64-chainloader @ 0.1formatting

Look for formatting issues in the source

line 224 is way too long (97 characters)
  • gnu/packages/raspberry-pi.scm (line: 224, column: 0)
raspi-arm-chainloader @ 0.1formatting

Look for formatting issues in the source

line 131 is way too long (129 characters)
  • gnu/packages/raspberry-pi.scm (line: 131, column: 0)
raspi-arm-chainloader @ 0.1formatting

Look for formatting issues in the source

line 137 is way too long (102 characters)
  • gnu/packages/raspberry-pi.scm (line: 137, column: 0)
pth @ 2.0.7formatting

Look for formatting issues in the source

trailing white space on line 42
  • gnu/packages/pth.scm (line: 42, column: 0)
presentty @ 0.2.1formatting

Look for formatting issues in the source

line 45 is way too long (117 characters)
  • gnu/packages/presentation.scm (line: 45, column: 0)
perl-test2-plugin-nowarnings @ 0.06formatting

Look for formatting issues in the source

line 106 is way too long (92 characters)
  • gnu/packages/perl-check.scm (line: 106, column: 0)
papi @ 5.5.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/profiling.scm (line: 137, column: 0)
openfoam @ 4.1formatting

Look for formatting issues in the source

line 132 is way too long (109 characters)
  • gnu/packages/simulation.scm (line: 132, column: 0)
openfoam @ 4.1formatting

Look for formatting issues in the source

line 146 is way too long (91 characters)
  • gnu/packages/simulation.scm (line: 146, column: 0)
omnitux @ 1.2.1formatting

Look for formatting issues in the source

line 581 is way too long (99 characters)
  • gnu/packages/education.scm (line: 581, column: 0)
ncurses @ 6.2formatting

Look for formatting issues in the source

trailing white space on line 165
  • gnu/packages/ncurses.scm (line: 165, column: 0)
ncurses @ 6.2formatting

Look for formatting issues in the source

line 179 is way too long (94 characters)
  • gnu/packages/ncurses.scm (line: 179, column: 0)
musl-cross @ 0.1-3.a8a6649formatting

Look for formatting issues in the source

line 152 is way too long (92 characters)
  • gnu/packages/heads.scm (line: 152, column: 0)
mrustc @ 0.9formatting

Look for formatting issues in the source

line 178 is way too long (123 characters)
  • gnu/packages/rust.scm (line: 178, column: 0)
maven-wagon-http @ 3.3.4formatting

Look for formatting issues in the source

line 901 is way too long (105 characters)
  • gnu/packages/maven.scm (line: 901, column: 0)
maven-wagon-http @ 3.3.4formatting

Look for formatting issues in the source

line 906 is way too long (138 characters)
  • gnu/packages/maven.scm (line: 906, column: 0)
maven-wagon-http @ 3.3.4formatting

Look for formatting issues in the source

line 907 is way too long (129 characters)
  • gnu/packages/maven.scm (line: 907, column: 0)
maven-wagon-file @ 3.3.4formatting

Look for formatting issues in the source

line 738 is way too long (125 characters)
  • gnu/packages/maven.scm (line: 738, column: 0)
maven-surefire-plugin @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3607 is way too long (113 characters)
  • gnu/packages/maven.scm (line: 3607, column: 0)
maven-surefire-plugin @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3608 is way too long (111 characters)
  • gnu/packages/maven.scm (line: 3608, column: 0)
maven-shared-utils @ 3.2.1formatting

Look for formatting issues in the source

line 583 is way too long (109 characters)
  • gnu/packages/maven.scm (line: 583, column: 0)
maven-resolver-transport-wagon @ 1.3.1formatting

Look for formatting issues in the source

line 255 is way too long (91 characters)
  • gnu/packages/maven.scm (line: 255, column: 0)
maven-resolver-transport-wagon @ 1.3.1formatting

Look for formatting issues in the source

line 270 is way too long (106 characters)
  • gnu/packages/maven.scm (line: 270, column: 0)
maven-resolver-transport-wagon @ 1.3.1formatting

Look for formatting issues in the source

line 284 is way too long (102 characters)
  • gnu/packages/maven.scm (line: 284, column: 0)
maven-resolver-impl @ 1.3.1formatting

Look for formatting issues in the source

line 201 is way too long (92 characters)
  • gnu/packages/maven.scm (line: 201, column: 0)
maven-resolver-impl @ 1.3.1formatting

Look for formatting issues in the source

line 210 is way too long (92 characters)
  • gnu/packages/maven.scm (line: 210, column: 0)
maven-resolver-impl @ 1.3.1formatting

Look for formatting issues in the source

line 218 is way too long (95 characters)
  • gnu/packages/maven.scm (line: 218, column: 0)
maven-resolver-impl @ 1.3.1formatting

Look for formatting issues in the source

line 221 is way too long (93 characters)
  • gnu/packages/maven.scm (line: 221, column: 0)
maven-resolver-connector-basic @ 1.3.1formatting

Look for formatting issues in the source

line 165 is way too long (99 characters)
  • gnu/packages/maven.scm (line: 165, column: 0)
maven-embedder @ 3.6.1formatting

Look for formatting issues in the source

line 1638 is way too long (110 characters)
  • gnu/packages/maven.scm (line: 1638, column: 0)
lxqt-session @ 0.15.0formatting

Look for formatting issues in the source

line 860 is way too long (92 characters)
  • gnu/packages/lxqt.scm (line: 860, column: 0)
lxqt-session @ 0.15.0formatting

Look for formatting issues in the source

line 867 is way too long (100 characters)
  • gnu/packages/lxqt.scm (line: 867, column: 0)
lxqt-session @ 0.15.0formatting

Look for formatting issues in the source

line 885 is way too long (98 characters)
  • gnu/packages/lxqt.scm (line: 885, column: 0)
lxqt-connman-applet @ 0.15.0-0.8a6cc14formatting

Look for formatting issues in the source

tabulation on line 1360, column 0
  • gnu/packages/lxqt.scm (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
  • gnu/packages/lxqt.scm (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
  • gnu/packages/lxqt.scm (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
  • gnu/packages/lxqt.scm (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
  • gnu/packages/lxqt.scm (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
  • gnu/packages/lxqt.scm (line: 1366, column: 0)
lxde-common @ 0.99.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/lxde.scm (line: 499, column: 0)
libsigsegv @ 2.12formatting

Look for formatting issues in the source

line 48 is way too long (133 characters)
  • gnu/packages/libsigsegv.scm (line: 48, column: 0)
libdaemon @ 0.14formatting

Look for formatting issues in the source

line 35 is way too long (147 characters)
  • gnu/packages/libdaemon.scm (line: 35, column: 0)
libdaemon @ 0.14formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/libdaemon.scm (line: 42, column: 0)
ldc @ 1.10.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/dlang.scm (line: 236, column: 0)
ldc @ 0.17.6formatting

Look for formatting issues in the source

line 130 is way too long (98 characters)
  • gnu/packages/dlang.scm (line: 130, column: 0)
kget @ 20.04.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/kde-internet.scm (line: 166, column: 0)
julia @ 1.5.3formatting

Look for formatting issues in the source

line 301 is way too long (107 characters)
  • gnu/packages/julia.scm (line: 301, column: 0)
julia @ 1.5.3formatting

Look for formatting issues in the source

line 303 is way too long (106 characters)
  • gnu/packages/julia.scm (line: 303, column: 0)
js-mathjax @ 2.7.2formatting

Look for formatting issues in the source

line 150 is way too long (91 characters)
  • gnu/packages/javascript.scm (line: 150, column: 0)
js-filesaver @ 1.3.8formatting

Look for formatting issues in the source

line 534 is way too long (99 characters)
  • gnu/packages/javascript.scm (line: 534, column: 0)
jose @ 10formatting

Look for formatting issues in the source

line 37 is way too long (92 characters)
  • gnu/packages/jose.scm (line: 37, column: 0)
java-surefire-booter @ 3.0.0-M4formatting

Look for formatting issues in the source

line 3271 is way too long (107 characters)
  • gnu/packages/maven.scm (line: 3271, column: 0)
idris @ 1.3.3formatting

Look for formatting issues in the source

line 104 is way too long (93 characters)
  • gnu/packages/idris.scm (line: 104, column: 0)
hyperledger-iroha @ 1.1.1formatting

Look for formatting issues in the source

line 169 is way too long (105 characters)
  • gnu/packages/hyperledger.scm (line: 169, column: 0)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

line 186 is way too long (91 characters)
  • gnu/packages/ipfs.scm (line: 186, column: 0)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

line 191 is way too long (91 characters)
  • gnu/packages/ipfs.scm (line: 191, column: 0)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

line 196 is way too long (91 characters)
  • gnu/packages/ipfs.scm (line: 196, column: 0)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

line 197 is way too long (99 characters)
  • gnu/packages/ipfs.scm (line: 197, column: 0)
gx-go @ 1.9.0formatting

Look for formatting issues in the source

line 198 is way too long (91 characters)
  • gnu/packages/ipfs.scm (line: 198, column: 0)
gx @ 0.14.3formatting

Look for formatting issues in the source

line 126 is way too long (91 characters)
  • gnu/packages/ipfs.scm (line: 126, column: 0)
gx @ 0.14.3formatting

Look for formatting issues in the source

line 131 is way too long (91 characters)
  • gnu/packages/ipfs.scm (line: 131, column: 0)
gx @ 0.14.3formatting

Look for formatting issues in the source

line 136 is way too long (91 characters)
  • gnu/packages/ipfs.scm (line: 136, column: 0)
gx @ 0.14.3formatting

Look for formatting issues in the source

line 137 is way too long (99 characters)
  • gnu/packages/ipfs.scm (line: 137, column: 0)
gx @ 0.14.3formatting

Look for formatting issues in the source

line 138 is way too long (91 characters)
  • gnu/packages/ipfs.scm (line: 138, column: 0)
gx @ 0.14.3formatting

Look for formatting issues in the source

line 145 is way too long (91 characters)
  • gnu/packages/ipfs.scm (line: 145, column: 0)
guile-wm @ 1.0-1.f3c7b3bformatting

Look for formatting issues in the source

line 128 is way too long (92 characters)
  • gnu/packages/guile-wm.scm (line: 128, column: 0)
guile-sdl @ 0.5.2formatting

Look for formatting issues in the source

line 607 is way too long (111 characters)
  • gnu/packages/sdl.scm (line: 607, column: 0)
go-github.com-smartystreets-goconvey @ 1.6.3formatting

Look for formatting issues in the source

line 679 is way too long (91 characters)
  • gnu/packages/check.scm (line: 679, column: 0)
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)
  • gnu/packages/ipfs.scm (line: 81, column: 0)
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)
  • gnu/packages/ipfs.scm (line: 82, column: 0)
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)
  • gnu/packages/ipfs.scm (line: 85, column: 0)
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)
  • gnu/packages/ipfs.scm (line: 88, column: 0)
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)
  • gnu/packages/ipfs.scm (line: 89, column: 0)
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)
  • gnu/packages/ipfs.scm (line: 95, column: 0)
gmp @ 6.2.0formatting

Look for formatting issues in the source

line 82 is way too long (96 characters)
  • gnu/packages/multiprecision.scm (line: 82, column: 0)
ghc-hxt-unicode @ 9.0.2.4formatting

Look for formatting issues in the source

line 1486 is way too long (91 characters)
  • gnu/packages/haskell-web.scm (line: 1486, column: 0)
ghc-base-unicode-symbols @ 0.2.3formatting

Look for formatting issues in the source

line 955 is way too long (101 characters)
  • gnu/packages/haskell-xyz.scm (line: 955, column: 0)
ghc @ 8.6.5formatting

Look for formatting issues in the source

line 591 is way too long (91 characters)
  • gnu/packages/haskell.scm (line: 591, column: 0)
gcompris @ 17.05formatting

Look for formatting issues in the source

line 135 is way too long (96 characters)
  • gnu/packages/education.scm (line: 135, column: 0)
fdroidserver @ 1.1.9formatting

Look for formatting issues in the source

line 940 is way too long (106 characters)
  • gnu/packages/android.scm (line: 940, column: 0)
fastboot @ 7.1.2_r36formatting

Look for formatting issues in the source

line 700 is way too long (105 characters)
  • gnu/packages/android.scm (line: 700, column: 0)
efitools @ 1.9.2formatting

Look for formatting issues in the source

line 215 is way too long (113 characters)
  • gnu/packages/efi.scm (line: 215, column: 0)
childsplay @ 3.4formatting

Look for formatting issues in the source

line 490 is way too long (92 characters)
  • gnu/packages/education.scm (line: 490, column: 0)
android-safe-iop @ 7.1.2_r36formatting

Look for formatting issues in the source

line 435 is way too long (95 characters)
  • gnu/packages/android.scm (line: 435, column: 0)
android-libutils @ 7.1.2_r36formatting

Look for formatting issues in the source

line 642 is way too long (114 characters)
  • gnu/packages/android.scm (line: 642, column: 0)
android-libcutils @ 7.1.2_r36formatting

Look for formatting issues in the source

tabulation on line 277, column 20
  • gnu/packages/android.scm (line: 277, column: 20)
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

line 366 is way too long (91 characters)
  • gnu/packages/android.scm (line: 366, column: 0)
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

line 385 is way too long (97 characters)
  • gnu/packages/android.scm (line: 385, column: 0)
abc @ 0.0-1.5ae4b97formatting

Look for formatting issues in the source

line 95 is way too long (95 characters)
  • gnu/packages/fpga.scm (line: 95, column: 0)
python-openstackdocstheme @ 1.18.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/openstack.scm (line: 206, column: 2)
python-mox3 @ 0.24.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/openstack.scm (line: 176, column: 2)
ijs @ 9.52patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/ghostscript.scm (line: 313, column: 2)
ghostscript-with-x @ 9.52patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/ghostscript.scm (line: 300, column: 2)
ghostscript-with-cups @ 9.52patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/ghostscript.scm (line: 307, column: 2)
mesa @ 20.2.4formatting

Look for formatting issues in the source

line 299 is way too long (120 characters)
  • gnu/packages/gl.scm (line: 299, column: 0)
mingw-w64-x86_64-winpthreads @ 8.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/mingw.scm (line: 46, column: 4)
mingw-w64-x86_64 @ 8.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/mingw.scm (line: 46, column: 4)
mingw-w64-i686-winpthreads @ 8.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/mingw.scm (line: 46, column: 4)
mingw-w64-i686 @ 8.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/mingw.scm (line: 46, column: 4)
connman @ 1.39description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
  • gnu/packages/connman.scm (line: 90, column: 17)
libtomcrypt @ 1.18.2formatting

Look for formatting issues in the source

line 341 is way too long (100 characters)
  • gnu/packages/multiprecision.scm (line: 341, column: 0)
gnome-shell-extension-gsconnect @ 33inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
  • gnu/packages/gnome-xyz.scm (line: 426, column: 5)
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
  • gnu/packages/gnome-xyz.scm (line: 504, column: 2)
xftwidth @ 20170402description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 96, 234
  • gnu/packages/xdisorg.scm (line: 1805, column: 17)
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1780, column 0
  • gnu/packages/xdisorg.scm (line: 1780, column: 0)
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1781, column 0
  • gnu/packages/xdisorg.scm (line: 1781, column: 0)
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1783, column 0
  • gnu/packages/xdisorg.scm (line: 1783, column: 0)
xftwidth @ 20170402formatting

Look for formatting issues in the source

tabulation on line 1784, column 0
  • gnu/packages/xdisorg.scm (line: 1784, column: 0)
python2-cryptography @ 3.3.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-crypto.scm (line: 556, column: 4)
python2-asn1crypto @ 1.4.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-crypto.scm (line: 762, column: 17)
python-cryptography @ 3.3.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-crypto.scm (line: 544, column: 6)
python-asn1crypto @ 1.4.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-crypto.scm (line: 762, column: 17)
python-keyring @ 22.0.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-crypto.scm (line: 370, column: 2)
rust-actix-derive @ 0.5.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/crates-io.scm (line: 310, column: 0)
emacs-cmake-mode @ 3.19.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/cmake.scm (line: 456, column: 2)
cfitsio @ 3.49description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 197
  • gnu/packages/astronomy.scm (line: 91, column: 17)
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
  • gnu/packages/machine-learning.scm (line: 1904, column: 5)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1544 is way too long (92 characters)
  • gnu/packages/machine-learning.scm (line: 1544, column: 0)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1647 is way too long (91 characters)
  • gnu/packages/machine-learning.scm (line: 1647, column: 0)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1734 is way too long (137 characters)
  • gnu/packages/machine-learning.scm (line: 1734, column: 0)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1735 is way too long (131 characters)
  • gnu/packages/machine-learning.scm (line: 1735, column: 0)
tensorflow @ 1.9.0formatting

Look for formatting issues in the source

line 1736 is way too long (137 characters)
  • gnu/packages/machine-learning.scm (line: 1736, column: 0)
python2-fastlmm @ 0.2.21formatting

Look for formatting issues in the source

line 1174 is way too long (92 characters)
  • gnu/packages/machine-learning.scm (line: 1174, column: 0)
patchwork @ 3.0.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/patchutils.scm (line: 370, column: 0)
ghc-th-reify-many @ 0.1.9description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/haskell-xyz.scm (line: 13652, column: 5)
ghc-regex-tdfa @ 1.2.3.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 139
  • gnu/packages/haskell-xyz.scm (line: 11130, column: 5)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 324, column 0
  • gnu/packages/display-managers.scm (line: 324, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 326, column 0
  • gnu/packages/display-managers.scm (line: 326, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 329, column 0
  • gnu/packages/display-managers.scm (line: 329, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 330, column 0
  • gnu/packages/display-managers.scm (line: 330, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 339, column 0
  • gnu/packages/display-managers.scm (line: 339, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 340, column 0
  • gnu/packages/display-managers.scm (line: 340, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 341, column 0
  • gnu/packages/display-managers.scm (line: 341, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 342, column 0
  • gnu/packages/display-managers.scm (line: 342, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 343, column 0
  • gnu/packages/display-managers.scm (line: 343, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 344, column 0
  • gnu/packages/display-managers.scm (line: 344, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 345, column 0
  • gnu/packages/display-managers.scm (line: 345, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 347, column 0
  • gnu/packages/display-managers.scm (line: 347, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 348, column 0
  • gnu/packages/display-managers.scm (line: 348, column: 0)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 349, column 0
  • gnu/packages/display-managers.scm (line: 349, column: 0)
ghc-xdg-basedir @ 0.2.2formatting

Look for formatting issues in the source

line 15284 is way too long (93 characters)
  • gnu/packages/haskell-xyz.scm (line: 15284, column: 0)
ghc-vector @ 0.12.0.3formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/haskell-xyz.scm (line: 14810, column: 0)
ghc-th-orphans @ 0.13.9formatting

Look for formatting issues in the source

line 13533 is way too long (92 characters)
  • gnu/packages/haskell-xyz.scm (line: 13533, column: 0)
ghc-system-filepath @ 0.4.14formatting

Look for formatting issues in the source

line 13020 is way too long (250 characters)
  • gnu/packages/haskell-xyz.scm (line: 13020, column: 0)
nsis-x86_64 @ 3.05description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
  • gnu/packages/installers.scm (line: 132, column: 7)
nsis-i686 @ 3.05description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 107
  • gnu/packages/installers.scm (line: 132, column: 7)
lua5.2-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/lua.scm (line: 703, column: 5)
lua5.1-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/lua.scm (line: 703, column: 5)
lua-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/lua.scm (line: 703, column: 5)
kdelibs4support @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
  • gnu/packages/kde-frameworks.scm (line: 3661, column: 5)
kconfigwidgets @ 5.70.0inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
  • gnu/packages/kde-frameworks.scm (line: 2315, column: 5)
python2 @ 2.7.17patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python.scm (line: 108, column: 2)
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
  • gnu/packages/kde-frameworks.scm (line: 3413, column: 2)
nsis-x86_64 @ 3.05patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/installers.scm (line: 35, column: 4)
nsis-i686 @ 3.05patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/installers.scm (line: 35, column: 4)
ruby-iruby @ 0.3formatting

Look for formatting issues in the source

line 509 is way too long (112 characters)
  • gnu/packages/ruby.scm (line: 509, column: 0)
ruby-asciidoctor-pdf @ 1.5.3-1.d257440formatting

Look for formatting issues in the source

line 1904 is way too long (99 characters)
  • gnu/packages/ruby.scm (line: 1904, column: 0)
python @ 3.8.2formatting

Look for formatting issues in the source

line 483 is way too long (93 characters)
  • gnu/packages/python.scm (line: 483, column: 0)
plasma-framework @ 5.70.1formatting

Look for formatting issues in the source

line 3425 is way too long (93 characters)
  • gnu/packages/kde-frameworks.scm (line: 3425, column: 0)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 65 is way too long (115 characters)
  • gnu/packages/installers.scm (line: 65, column: 0)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 66 is way too long (112 characters)
  • gnu/packages/installers.scm (line: 66, column: 0)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 80 is way too long (112 characters)
  • gnu/packages/installers.scm (line: 80, column: 0)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 94 is way too long (92 characters)
  • gnu/packages/installers.scm (line: 94, column: 0)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 114 is way too long (97 characters)
  • gnu/packages/installers.scm (line: 114, column: 0)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 118 is way too long (122 characters)
  • gnu/packages/installers.scm (line: 118, column: 0)
nsis-x86_64 @ 3.05formatting

Look for formatting issues in the source

line 128 is way too long (114 characters)
  • gnu/packages/installers.scm (line: 128, column: 0)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 65 is way too long (115 characters)
  • gnu/packages/installers.scm (line: 65, column: 0)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 66 is way too long (112 characters)
  • gnu/packages/installers.scm (line: 66, column: 0)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 80 is way too long (112 characters)
  • gnu/packages/installers.scm (line: 80, column: 0)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 94 is way too long (92 characters)
  • gnu/packages/installers.scm (line: 94, column: 0)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 114 is way too long (97 characters)
  • gnu/packages/installers.scm (line: 114, column: 0)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 118 is way too long (122 characters)
  • gnu/packages/installers.scm (line: 118, column: 0)
nsis-i686 @ 3.05formatting

Look for formatting issues in the source

line 128 is way too long (114 characters)
  • gnu/packages/installers.scm (line: 128, column: 0)
mkvtoolnix @ 52.0.0formatting

Look for formatting issues in the source

line 912 is way too long (96 characters)
  • gnu/packages/video.scm (line: 912, column: 0)
lua-tablepool @ 0.01formatting

Look for formatting issues in the source

line 1062 is way too long (100 characters)
  • gnu/packages/lua.scm (line: 1062, column: 0)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

line 1027 is way too long (104 characters)
  • gnu/packages/lua.scm (line: 1027, column: 0)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

line 1028 is way too long (93 characters)
  • gnu/packages/lua.scm (line: 1028, column: 0)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

line 1029 is way too long (123 characters)
  • gnu/packages/lua.scm (line: 1029, column: 0)
lua-resty-signal @ 0.02formatting

Look for formatting issues in the source

line 1030 is way too long (112 characters)
  • gnu/packages/lua.scm (line: 1030, column: 0)
lua-resty-shell @ 0.03formatting

Look for formatting issues in the source

line 1094 is way too long (100 characters)
  • gnu/packages/lua.scm (line: 1094, column: 0)
lua-resty-shell @ 0.03formatting

Look for formatting issues in the source

line 1096 is way too long (119 characters)
  • gnu/packages/lua.scm (line: 1096, column: 0)
lua-resty-shell @ 0.03formatting

Look for formatting issues in the source

line 1097 is way too long (108 characters)
  • gnu/packages/lua.scm (line: 1097, column: 0)
lua-resty-lrucache @ 0.10formatting

Look for formatting issues in the source

line 987 is way too long (100 characters)
  • gnu/packages/lua.scm (line: 987, column: 0)
lua-resty-lrucache @ 0.10formatting

Look for formatting issues in the source

line 989 is way too long (119 characters)
  • gnu/packages/lua.scm (line: 989, column: 0)
lua-resty-lrucache @ 0.10formatting

Look for formatting issues in the source

line 990 is way too long (108 characters)
  • gnu/packages/lua.scm (line: 990, column: 0)
lua-resty-core @ 0.1.18formatting

Look for formatting issues in the source

line 952 is way too long (95 characters)
  • gnu/packages/lua.scm (line: 952, column: 0)
kpackage @ 5.70.0formatting

Look for formatting issues in the source

line 1957 is way too long (106 characters)
  • gnu/packages/kde-frameworks.scm (line: 1957, column: 0)
kio @ 5.70.1formatting

Look for formatting issues in the source

line 2796 is way too long (113 characters)
  • gnu/packages/kde-frameworks.scm (line: 2796, column: 0)
kimageformats @ 5.70.0formatting

Look for formatting issues in the source

line 1819 is way too long (103 characters)
  • gnu/packages/kde-frameworks.scm (line: 1819, column: 0)
kdbusaddons @ 5.70.0formatting

Look for formatting issues in the source

line 649 is way too long (107 characters)
  • gnu/packages/kde-frameworks.scm (line: 649, column: 0)
kcmutils @ 5.70.0formatting

Look for formatting issues in the source

line 2268 is way too long (113 characters)
  • gnu/packages/kde-frameworks.scm (line: 2268, column: 0)
java-jbzip2 @ 0.9.1formatting

Look for formatting issues in the source

line 279 is way too long (92 characters)
  • gnu/packages/java-compression.scm (line: 279, column: 0)
extra-cmake-modules @ 5.70.0formatting

Look for formatting issues in the source

line 114 is way too long (91 characters)
  • gnu/packages/kde-frameworks.scm (line: 114, column: 0)
tesseract-ocr @ 4.1.1-1.97079faformatting

Look for formatting issues in the source

line 121 is way too long (93 characters)
  • gnu/packages/ocr.scm (line: 121, column: 0)
clang-runtime @ 3.9.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/llvm.scm (line: 97, column: 2)
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
  • gnu/packages/llvm.scm (line: 97, column: 2)
clang-runtime @ 3.8.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/llvm.scm (line: 97, column: 2)
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
  • gnu/packages/llvm.scm (line: 97, column: 2)
clang-runtime @ 3.7.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/llvm.scm (line: 97, column: 2)
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
  • gnu/packages/llvm.scm (line: 97, column: 2)
python2 @ 2.7.17formatting

Look for formatting issues in the source

line 183 is way too long (99 characters)
  • gnu/packages/python.scm (line: 183, column: 0)
python2 @ 2.7.17formatting

Look for formatting issues in the source

line 292 is way too long (98 characters)
  • gnu/packages/python.scm (line: 292, column: 0)
clang @ 9.0.1formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
  • gnu/packages/llvm.scm (line: 369, column: 0)
clang @ 8.0.0formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
  • gnu/packages/llvm.scm (line: 369, column: 0)
clang @ 7.0.1formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
  • gnu/packages/llvm.scm (line: 369, column: 0)
clang @ 6.0.1formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
  • gnu/packages/llvm.scm (line: 369, column: 0)
clang @ 3.9.1formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
  • gnu/packages/llvm.scm (line: 369, column: 0)
clang @ 3.8.1formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
  • gnu/packages/llvm.scm (line: 369, column: 0)
clang @ 3.7.1formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
  • gnu/packages/llvm.scm (line: 369, column: 0)
clang @ 3.5.2formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
  • gnu/packages/llvm.scm (line: 369, column: 0)
clang @ 11.0.0formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
  • gnu/packages/llvm.scm (line: 369, column: 0)
clang @ 10.0.0formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
  • gnu/packages/llvm.scm (line: 369, column: 0)
389-ds-base @ 1.4.0.31inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/openldap.scm (line: 355, column: 5)
mumble @ 1.3.4formatting

Look for formatting issues in the source

tabulation on line 544, column 0
  • gnu/packages/telephony.scm (line: 544, column: 0)
mumble @ 1.3.4formatting

Look for formatting issues in the source

tabulation on line 545, column 0
  • gnu/packages/telephony.scm (line: 545, column: 0)
mumble @ 1.3.4formatting

Look for formatting issues in the source

tabulation on line 546, column 0
  • gnu/packages/telephony.scm (line: 546, column: 0)
straw-viewer @ 0.1.3formatting

Look for formatting issues in the source

trailing white space on line 1043
  • gnu/packages/video.scm (line: 1043, column: 0)
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 294, column 18
  • gnu/packages/language.scm (line: 294, column: 18)
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 296, column 18
  • gnu/packages/language.scm (line: 296, column: 18)
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 298, column 18
  • gnu/packages/language.scm (line: 298, column: 18)
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 300, column 18
  • gnu/packages/language.scm (line: 300, column: 18)
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 302, column 18
  • gnu/packages/language.scm (line: 302, column: 18)
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 304, column 18
  • gnu/packages/language.scm (line: 304, column: 18)
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 306, column 18
  • gnu/packages/language.scm (line: 306, column: 18)
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 308, column 18
  • gnu/packages/language.scm (line: 308, column: 18)
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 310, column 18
  • gnu/packages/language.scm (line: 310, column: 18)
rust @ 1.26.2formatting

Look for formatting issues in the source

line 790 is way too long (94 characters)
  • gnu/packages/rust.scm (line: 790, column: 0)
rust @ 1.25.0formatting

Look for formatting issues in the source

line 751 is way too long (91 characters)
  • gnu/packages/rust.scm (line: 751, column: 0)
rust @ 1.47.0formatting

Look for formatting issues in the source

line 1403 is way too long (98 characters)
  • gnu/packages/rust.scm (line: 1403, column: 0)
rust @ 1.47.0formatting

Look for formatting issues in the source

line 1409 is way too long (91 characters)
  • gnu/packages/rust.scm (line: 1409, column: 0)
fcitx5-gtk @ 5.0.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/fcitx5.scm (line: 230, column: 5)
nextcloud-client @ 3.1.3inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
  • gnu/packages/sync.scm (line: 183, column: 5)
owncloud-client @ 2.7.6.3261patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/sync.scm (line: 313, column: 2)
rust-async-compression @ 0.3.7formatting

Look for formatting issues in the source

line 2571 is way too long (92 characters)
  • gnu/packages/crates-io.scm (line: 2571, column: 0)
python-libfreenect @ 0.6.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/openkinect.scm (line: 123, column: 2)
libfreenect-opencv @ 0.6.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/openkinect.scm (line: 105, column: 2)
libfreenect-examples @ 0.6.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/openkinect.scm (line: 88, column: 2)
eid-mw @ 5.0.14formatting

Look for formatting issues in the source

line 156 is way too long (97 characters)
  • gnu/packages/security-token.scm (line: 156, column: 0)
eid-mw @ 5.0.14formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/security-token.scm (line: 163, column: 0)
python-fpylll @ 0.5.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/algebra.scm (line: 232, column: 17)
openjpeg-data @ 2020.05.19description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
  • gnu/packages/image.scm (line: 825, column: 17)
iml @ 1.0.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 798
  • gnu/packages/algebra.scm (line: 1567, column: 5)
ibus-libhangul @ 1.5.3description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/ibus.scm (line: 763, column: 5)
python2-sphinx @ 1.7.7inputs-should-be-native

Identify inputs that should be native inputs

'python2-docutils' should probably be a native input
  • gnu/packages/sphinx.scm (line: 111, column: 4)
python2-pygobject @ 2.28.7inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/glib.scm (line: 775, column: 5)
python-sphinx-copybutton @ 0.2.6inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 174, column: 2)
python-sphinx @ 3.3.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/sphinx.scm (line: 53, column: 2)
python-pygobject @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/glib.scm (line: 819, column: 5)
python-fpylll @ 0.5.2inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
  • gnu/packages/algebra.scm (line: 220, column: 5)
python-fpylll @ 0.5.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/algebra.scm (line: 220, column: 5)
ibus-anthy @ 1.5.9inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/ibus.scm (line: 293, column: 5)
gobject-introspection @ 1.62.0inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
  • gnu/packages/glib.scm (line: 509, column: 5)
gobject-introspection @ 1.62.0inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
  • gnu/packages/glib.scm (line: 509, column: 5)
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
  • gnu/packages/sphinx.scm (line: 174, column: 2)
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
  • gnu/packages/glib.scm (line: 478, column: 2)
symmetrica @ 2.0formatting

Look for formatting issues in the source

line 1393 is way too long (100 characters)
  • gnu/packages/algebra.scm (line: 1393, column: 0)
librime @ 1.6.1formatting

Look for formatting issues in the source

line 334 is way too long (93 characters)
  • gnu/packages/ibus.scm (line: 334, column: 0)
gap @ 4.11.0formatting

Look for formatting issues in the source

line 1156 is way too long (98 characters)
  • gnu/packages/algebra.scm (line: 1156, column: 0)
eigen @ 3.3.8formatting

Look for formatting issues in the source

tabulation on line 1027, column 0
  • gnu/packages/algebra.scm (line: 1027, column: 0)
mate-applets @ 1.24.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 917
  • gnu/packages/mate.scm (line: 575, column: 5)
python2-pygobject @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/glib.scm (line: 837, column: 4)
libtool @ 2.4.6inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
  • gnu/packages/autotools.scm (line: 437, column: 2)
telepathy-glib @ 0.24.1formatting

Look for formatting issues in the source

line 926 is way too long (92 characters)
  • gnu/packages/glib.scm (line: 926, column: 0)
python2-pygobject @ 3.34.0formatting

Look for formatting issues in the source

line 853 is way too long (97 characters)
  • gnu/packages/glib.scm (line: 853, column: 0)
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 606 is way too long (92 characters)
  • gnu/packages/autotools.scm (line: 606, column: 0)
mate-panel @ 1.24.1formatting

Look for formatting issues in the source

line 671 is way too long (92 characters)
  • gnu/packages/mate.scm (line: 671, column: 0)
mate-menus @ 1.24.1formatting

Look for formatting issues in the source

line 511 is way too long (91 characters)
  • gnu/packages/mate.scm (line: 511, column: 0)
elixir @ 1.11.4formatting

Look for formatting issues in the source

line 76 is way too long (97 characters)
  • gnu/packages/elixir.scm (line: 76, column: 0)
elixir @ 1.11.4formatting

Look for formatting issues in the source

line 77 is way too long (99 characters)
  • gnu/packages/elixir.scm (line: 77, column: 0)
rav1e @ 0.3.5inputs-should-be-native

Identify inputs that should be native inputs

'nasm' should probably be a native input
  • gnu/packages/video.scm (line: 4922, column: 5)
gaupol @ 1.9formatting

Look for formatting issues in the source

line 4640 is way too long (95 characters)
  • gnu/packages/video.scm (line: 4640, column: 0)
go-github-com-gorilla-context @ 0.0.0-0.08b5f42formatting

Look for formatting issues in the source

line 1681 is way too long (164 characters)
  • gnu/packages/golang.scm (line: 1681, column: 0)
template-glib @ 3.34.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/glib.scm (line: 1162, column: 5)
emilua @ 0.3.0formatting

Look for formatting issues in the source

line 1154 is way too long (98 characters)
  • gnu/packages/lua.scm (line: 1154, column: 0)
r-bsgenome-dmelanogaster-ucsc-dm3-masked @ 1.3.99formatting

Look for formatting issues in the source

line 224 is way too long (95 characters)
  • gnu/packages/bioconductor.scm (line: 224, column: 0)
mate-polkit @ 1.24.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/mate.scm (line: 1508, column: 5)
atril @ 1.22.0formatting

Look for formatting issues in the source

line 748 is way too long (92 characters)
  • gnu/packages/mate.scm (line: 748, column: 0)
python-tornado @ 5.1.1formatting

Look for formatting issues in the source

line 1665 is way too long (91 characters)
  • gnu/packages/python-web.scm (line: 1665, column: 0)
texlive-lm @ 51265description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 93
  • gnu/packages/tex.scm (line: 883, column: 17)
texlive-fonts-lm @ 51265description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 93
  • guix/packages.scm (line: 464, column: 2)
texlive-fonts-latex @ 51265description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 78
  • gnu/packages/tex.scm (line: 1032, column: 17)
guile3.0-email @ 0.2.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • guix/packages.scm (line: 464, column: 2)
guile3.0-commonmark @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • guix/packages.scm (line: 464, column: 2)
python-conda @ 4.8.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • guix/packages.scm (line: 464, column: 2)
guile3.0-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
  • guix/packages.scm (line: 464, column: 2)
guile3.0-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'automake' should probably be a native input
  • guix/packages.scm (line: 464, column: 2)
guile3.0-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
  • guix/packages.scm (line: 464, column: 2)
guile3.0-mailutils @ 3.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
  • guix/packages.scm (line: 464, column: 2)
guile3.0-gi @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • guix/packages.scm (line: 464, column: 2)
guile3.0-mailutils @ 3.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • guix/packages.scm (line: 464, column: 2)
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
  • guix/packages.scm (line: 464, column: 2)
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
  • guix/packages.scm (line: 464, column: 2)
enlightenment-wayland @ 0.24.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • guix/packages.scm (line: 464, column: 2)
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
  • guix/packages.scm (line: 464, column: 2)
glibc-bootstrap @ 0formatting

Look for formatting issues in the source

line 653 is way too long (100 characters)
  • gnu/packages/bootstrap.scm (line: 653, column: 0)
gcc-bootstrap @ 0formatting

Look for formatting issues in the source

line 749 is way too long (100 characters)
  • gnu/packages/bootstrap.scm (line: 749, column: 0)
help2man @ 1.47.13formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/man.scm (line: 325, column: 0)
cryptsetup-static @ 2.3.5formatting

Look for formatting issues in the source

line 102 is way too long (93 characters)
  • gnu/packages/cryptsetup.scm (line: 102, column: 0)
abseil-cpp @ 20200923.3formatting

Look for formatting issues in the source

line 708 is way too long (116 characters)
  • gnu/packages/cpp.scm (line: 708, column: 0)
abseil-cpp @ 20200923.3formatting

Look for formatting issues in the source

line 709 is way too long (144 characters)
  • gnu/packages/cpp.scm (line: 709, column: 0)
gramps @ 5.1.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/genealogy.scm (line: 57, column: 5)
guile3.0-gnutls @ 3.6.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • guix/packages.scm (line: 464, column: 2)
unbound @ 1.13.1formatting

Look for formatting issues in the source

trailing white space on line 689
  • gnu/packages/dns.scm (line: 689, column: 0)
unbound @ 1.13.1formatting

Look for formatting issues in the source

trailing white space on line 725
  • gnu/packages/dns.scm (line: 725, column: 0)
zbar @ 0.23inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/aidc.scm (line: 193, column: 5)
linphoneqt @ 4.2.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • guix/packages.scm (line: 464, column: 2)
xygrib @ 1.2.6.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 256
  • gnu/packages/geo.scm (line: 1254, column: 5)
osm-gps-map @ 1.1.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/geo.scm (line: 1180, column: 5)
tegola @ 0.7.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/geo.scm (line: 946, column: 12)
python2-mapnik @ 3.0.16source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/geo.scm (line: 645, column: 5)
imposm3 @ 0.6.0-alpha.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/geo.scm (line: 986, column: 6)
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
  • gnu/packages/geo.scm (line: 298, column: 2)
xygrib @ 1.2.6.1formatting

Look for formatting issues in the source

line 1229 is way too long (95 characters)
  • gnu/packages/geo.scm (line: 1229, column: 0)
proj.4 @ 4.9.3formatting

Look for formatting issues in the source

line 561 is way too long (92 characters)
  • gnu/packages/geo.scm (line: 561, column: 0)
flite @ 2.2formatting

Look for formatting issues in the source

line 92 is way too long (419 characters)
  • gnu/packages/speech.scm (line: 92, column: 0)
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
  • gnu/packages/messaging.scm (line: 418, column: 5)
pjproject-jami @ 2.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/jami.scm (line: 122, column: 2)
quaternion @ 0.0.9.4finputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
  • gnu/packages/messaging.scm (line: 2384, column: 5)
docker @ 19.03.15formatting

Look for formatting issues in the source

line 355 is way too long (95 characters)
  • gnu/packages/docker.scm (line: 355, column: 0)
docker @ 19.03.15formatting

Look for formatting issues in the source

line 391 is way too long (93 characters)
  • gnu/packages/docker.scm (line: 391, column: 0)
vim-full @ 8.2.2689formatting

Look for formatting issues in the source

line 224 is way too long (98 characters)
  • gnu/packages/vim.scm (line: 224, column: 0)
go-github-com-songmu-gitconfig @ 0.1.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/golang.scm (line: 6744, column: 17)
go-github-com-muesli-termenv @ 0.7.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/golang.scm (line: 5695, column: 17)
go-github-com-mitchellh-reflectwalk @ 1.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/golang.scm (line: 3383, column: 17)
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
  • gnu/packages/golang.scm (line: 2770, column: 4)
go-github-com-rogpeppe-go-internal @ 1.6.1formatting

Look for formatting issues in the source

line 6328 is way too long (101 characters)
  • gnu/packages/golang.scm (line: 6328, column: 0)
go-github-com-multiformats-go-multiaddr-net @ 1.6.3-0.1cb9a0eformatting

Look for formatting issues in the source

line 3482 is way too long (93 characters)
  • gnu/packages/golang.scm (line: 3482, column: 0)
go-github-com-multiformats-go-multiaddr-net @ 1.6.3-0.1cb9a0eformatting

Look for formatting issues in the source

line 3483 is way too long (93 characters)
  • gnu/packages/golang.scm (line: 3483, column: 0)
go-github-com-multiformats-go-multiaddr @ 1.3.0-0.fe1c46fformatting

Look for formatting issues in the source

line 3439 is way too long (93 characters)
  • gnu/packages/golang.scm (line: 3439, column: 0)
go-github-com-mitchellh-go-homedir @ 1.0.0-0.ae18d6bformatting

Look for formatting issues in the source

line 3326 is way too long (95 characters)
  • gnu/packages/golang.scm (line: 3326, column: 0)
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
  • gnu/packages/golang.scm (line: 4103, column: 0)
go-github-com-libp2p-go-libp2p-peer @ 2.3.8-0.993d742formatting

Look for formatting issues in the source

line 3231 is way too long (93 characters)
  • gnu/packages/golang.scm (line: 3231, column: 0)
go-github-com-libp2p-go-libp2p-metrics @ 2.1.6-0.a10ff6eformatting

Look for formatting issues in the source

line 3287 is way too long (93 characters)
  • gnu/packages/golang.scm (line: 3287, column: 0)
go-github-com-libp2p-go-libp2p-metrics @ 2.1.6-0.a10ff6eformatting

Look for formatting issues in the source

line 3290 is way too long (93 characters)
  • gnu/packages/golang.scm (line: 3290, column: 0)
go-github-com-davecgh-go-spew @ 1.1.1formatting

Look for formatting issues in the source

line 2894 is way too long (129 characters)
  • gnu/packages/golang.scm (line: 2894, column: 0)
chez-srfi @ 1.0formatting

Look for formatting issues in the source

line 289 is way too long (91 characters)
  • gnu/packages/chez.scm (line: 289, column: 0)
libvirt-glib @ 4.0.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/virtualization.scm (line: 1168, column: 5)
qemu-minimal @ 5.2.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/virtualization.scm (line: 396, column: 2)
xen @ 4.14.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/virtualization.scm (line: 1885, column: 0)
python2-pygame @ 1.9.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 123
  • gnu/packages/game-development.scm (line: 1075, column: 17)
python-xsge @ 2020.09.07description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/game-development.scm (line: 442, column: 5)
python-pygame @ 1.9.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 123
  • gnu/packages/game-development.scm (line: 1075, column: 17)
grfcodec @ 6.0.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 100
  • gnu/packages/game-development.scm (line: 241, column: 5)
deutex @ 5.2.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 60
  • gnu/packages/game-development.scm (line: 188, column: 4)
perl-libxml @ 0.08description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/xml.scm (line: 664, column: 5)
libxmlplusplus @ 3.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/xml.scm (line: 317, column: 5)
libxmlplusplus @ 2.40.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/xml.scm (line: 324, column: 2)
python2-libxml2 @ 2.9.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/xml.scm (line: 339, column: 2)
axoloti-runtime @ 1.0.12-2formatting

Look for formatting issues in the source

line 192 is way too long (96 characters)
  • gnu/packages/axoloti.scm (line: 192, column: 0)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

line 410 is way too long (94 characters)
  • gnu/packages/axoloti.scm (line: 410, column: 0)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

line 556 is way too long (93 characters)
  • gnu/packages/axoloti.scm (line: 556, column: 0)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

line 569 is way too long (103 characters)
  • gnu/packages/axoloti.scm (line: 569, column: 0)
rust-winit @ 0.24.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/crates-graphics.scm (line: 2897, column: 5)
rust-winit @ 0.20.0-alpha6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/crates-graphics.scm (line: 2908, column: 2)
rust-winit @ 0.19.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/crates-graphics.scm (line: 2962, column: 2)
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 2925 is way too long (114 characters)
  • gnu/packages/crates-graphics.scm (line: 2925, column: 0)
mosquitto @ 1.6.12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 347
  • gnu/packages/messaging.scm (line: 2681, column: 17)
qtwebglplugin @ 5.15.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 41
  • gnu/packages/qt.scm (line: 1044, column: 17)
qtdatavis3d @ 5.15.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 107, 250
  • gnu/packages/qt.scm (line: 1326, column: 17)
qtcharts @ 5.15.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 244
  • gnu/packages/qt.scm (line: 1302, column: 17)
qwt @ 6.1.5inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
  • gnu/packages/qt.scm (line: 2412, column: 3)
python-pyqt-without-qtwebkit @ 5.15.2inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
  • gnu/packages/qt.scm (line: 2086, column: 2)
python-pyqt @ 5.15.2inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
  • gnu/packages/qt.scm (line: 1912, column: 5)
python-bcj-cffi @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
  • gnu/packages/python-compression.scm (line: 75, column: 2)
python-py7zr @ 0.14.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-compression.scm (line: 130, column: 2)
python-ppmd-cffi @ 0.3.3inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-compression.scm (line: 102, column: 2)
python-multivolumefile @ 0.2.2inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-compression.scm (line: 47, column: 2)
python-bcj-cffi @ 0.5.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-compression.scm (line: 75, column: 2)
python-pyqt-without-qtwebkit @ 5.15.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/qt.scm (line: 2086, column: 2)
python-pyqt @ 5.15.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/qt.scm (line: 1888, column: 2)
qtserialport @ 5.15.2formatting

Look for formatting issues in the source

line 957 is way too long (115 characters)
  • gnu/packages/qt.scm (line: 957, column: 0)
qtsensors @ 5.15.2formatting

Look for formatting issues in the source

line 820 is way too long (97 characters)
  • gnu/packages/qt.scm (line: 820, column: 0)
qtremoteobjects @ 5.15.2formatting

Look for formatting issues in the source

line 1381 is way too long (94 characters)
  • gnu/packages/qt.scm (line: 1381, column: 0)
qtmultimedia @ 5.15.2formatting

Look for formatting issues in the source

line 860 is way too long (96 characters)
  • gnu/packages/qt.scm (line: 860, column: 0)
qtbase @ 5.15.2formatting

Look for formatting issues in the source

line 396 is way too long (96 characters)
  • gnu/packages/qt.scm (line: 396, column: 0)
qtbase @ 5.15.2formatting

Look for formatting issues in the source

line 523 is way too long (97 characters)
  • gnu/packages/qt.scm (line: 523, column: 0)
qtbase @ 5.15.2formatting

Look for formatting issues in the source

line 528 is way too long (94 characters)
  • gnu/packages/qt.scm (line: 528, column: 0)
qtbase @ 5.15.2formatting

Look for formatting issues in the source

line 530 is way too long (94 characters)
  • gnu/packages/qt.scm (line: 530, column: 0)
python-pyqt @ 5.15.2formatting

Look for formatting issues in the source

line 1941 is way too long (105 characters)
  • gnu/packages/qt.scm (line: 1941, column: 0)
calibre @ 5.14.0formatting

Look for formatting issues in the source

line 255 is way too long (92 characters)
  • gnu/packages/ebook.scm (line: 255, column: 0)
calibre @ 5.14.0formatting

Look for formatting issues in the source

line 280 is way too long (93 characters)
  • gnu/packages/ebook.scm (line: 280, column: 0)
jami-qt @ 20210326.1.cfba013formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/jami.scm (line: 594, column: 0)
missfits @ 2.8.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 268
  • gnu/packages/astronomy.scm (line: 690, column: 5)
itcl @ 4.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/tcl.scm (line: 144, column: 5)
tao @ 1.0-beta-10May2006inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
  • gnu/packages/audio.scm (line: 1221, column: 5)
tao @ 1.0-beta-10May2006inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
  • gnu/packages/audio.scm (line: 1221, column: 5)
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
  • gnu/packages/astronomy.scm (line: 703, column: 2)
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
  • gnu/packages/astronomy.scm (line: 703, column: 2)
i3-wm @ 4.18.3description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/wm.scm (line: 343, column: 17)
keybinder-3.0 @ 0.3.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/wm.scm (line: 1133, column: 5)
awesome @ 4.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/wm.scm (line: 950, column: 5)
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
  • gnu/packages/wm.scm (line: 509, column: 4)
notifymuch @ 0.1-1.9d4aaf5inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/mail.scm (line: 1302, column: 7)
geany @ 1.37.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/text-editors.scm (line: 934, column: 0)
python2-pytest-xdist @ 2.1.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1280, column: 2)
python2-pytest-mock @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-mock' should probably be a native input
  • gnu/packages/check.scm (line: 1274, column: 4)
python2-pytest-mock @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1274, column: 4)
python2-cov-core @ 1.15.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
  • gnu/packages/check.scm (line: 1721, column: 2)
python-testtools @ 2.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/check.scm (line: 1440, column: 2)
python-testscenarios @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/check.scm (line: 1492, column: 2)
python-testresources @ 2.0.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/check.scm (line: 1527, column: 2)
python-pytest-xdist @ 2.1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1280, column: 2)
python-pytest-timeout @ 1.3.4inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1331, column: 2)
python-pytest-mock @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1245, column: 2)
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
  • gnu/packages/check.scm (line: 1218, column: 2)
python-pytest-forked @ 1.1.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1361, column: 2)
python-fixtures @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/check.scm (line: 1606, column: 2)
python-cov-core @ 1.15.0inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
  • gnu/packages/check.scm (line: 1721, column: 2)
python-codecov @ 2.0.15inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
  • gnu/packages/check.scm (line: 1746, column: 2)
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
  • gnu/packages/check.scm (line: 1411, column: 2)
python2-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1173 is way too long (96 characters)
  • gnu/packages/embedded.scm (line: 1173, column: 0)
python-libmpsse @ 1.4.1formatting

Look for formatting issues in the source

line 1140 is way too long (94 characters)
  • gnu/packages/embedded.scm (line: 1140, column: 0)
jimtcl @ 0.80formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/embedded.scm (line: 559, column: 0)
fc-host-tools @ 14formatting

Look for formatting issues in the source

line 1264 is way too long (122 characters)
  • gnu/packages/embedded.scm (line: 1264, column: 0)
dsfmt @ 2.2.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maths.scm (line: 395, column: 2)
python2-renpy @ 7.4.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/game-development.scm (line: 1146, column: 2)
r-biomart @ 2.46.3description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioconductor.scm (line: 1786, column: 5)
r-hsmmsinglecell @ 1.2.0formatting

Look for formatting issues in the source

line 1041 is way too long (95 characters)
  • gnu/packages/bioconductor.scm (line: 1041, column: 0)
r-biocparallel @ 1.24.1formatting

Look for formatting issues in the source

line 1836 is way too long (95 characters)
  • gnu/packages/bioconductor.scm (line: 1836, column: 0)
python2-pytest-subtesthack @ 0.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 106
  • gnu/packages/check.scm (line: 1932, column: 17)
python2-flexmock @ 0.10.4description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/check.scm (line: 2594, column: 5)
python-pytest-subtesthack @ 0.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 106
  • gnu/packages/check.scm (line: 1932, column: 17)
python-nbclient @ 0.5.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 62
  • gnu/packages/jupyter.scm (line: 310, column: 5)
python-jupyterlab-widgets @ 1.0.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/jupyter.scm (line: 262, column: 17)
python-flexmock @ 0.10.4description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/check.scm (line: 2594, column: 5)
python2-sphinxcontrib-programoutput @ 0.15inputs-should-be-native

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 302, column: 2)
python2-sphinx-rtd-theme @ 0.2.4inputs-should-be-native

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 584, column: 2)
python2-sphinx-repoze-autointerface @ 0.8inputs-should-be-native

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 465, column: 2)
python2-pytest-warnings @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 2256, column: 2)
python2-pytest-subtesthack @ 0.1.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1919, column: 2)
python2-pytest-catchlog @ 1.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 2284, column: 2)
python2-pytest-capturelog @ 0.7inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 2261, column: 2)
python2-pytest-cache @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1844, column: 2)
python2-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
  • gnu/packages/check.scm (line: 2310, column: 2)
python2-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-nose' should probably be a native input
  • gnu/packages/check.scm (line: 2310, column: 2)
python2-nose-timer @ 0.7.5inputs-should-be-native

Identify inputs that should be native inputs

'python2-nose' should probably be a native input
  • gnu/packages/check.scm (line: 2524, column: 2)
python2-guzzle-sphinx-theme @ 0.7.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 560, column: 2)
python2-coverage-test-runner @ 1.15inputs-should-be-native

Identify inputs that should be native inputs

'python2-coverage' should probably be a native input
  • gnu/packages/check.scm (line: 2135, column: 2)
python-sphinxcontrib-svg2pdfconverter @ 1.0.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 367, column: 2)
python-sphinxcontrib-programoutput @ 0.15inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 302, column: 2)
python-sphinxcontrib-newsfeed @ 0.1.4inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 282, column: 2)
python-sphinxcontrib-github-alt @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/sphinx.scm (line: 220, column: 2)
python-sphinxcontrib-github-alt @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 220, column: 2)
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
  • gnu/packages/sphinx.scm (line: 584, column: 2)
python-sphinx-repoze-autointerface @ 0.8inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 465, column: 2)
python-sphinx-intl @ 2.0.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 629, column: 2)
python-sphinx-autodoc-typehints @ 1.11.1inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
  • gnu/packages/sphinx.scm (line: 697, column: 2)
python-sphinx-autodoc-typehints @ 1.11.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 697, column: 2)
python-sphinx-argparse @ 0.2.5inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 512, column: 2)
python-requests-unixsocket @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/python-web.scm (line: 2527, column: 2)
python-pytest-xprocess @ 0.9.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1898, column: 2)
python-pytest-warnings @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 2232, column: 2)
python-pytest-sugar @ 0.9.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1944, column: 2)
python-pytest-subtesthack @ 0.1.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1919, column: 2)
python-pytest-catchlog @ 1.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 2284, column: 2)
python-pytest-capturelog @ 0.7inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 2261, column: 2)
python-pytest-cache @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 1844, column: 2)
python-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
  • gnu/packages/check.scm (line: 2310, column: 2)
python-nosexcover @ 1.0.11inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
  • gnu/packages/check.scm (line: 2310, column: 2)
python-nose-timer @ 0.7.5inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
  • gnu/packages/check.scm (line: 2524, column: 2)
python-nbsphinx @ 0.7.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/sphinx.scm (line: 724, column: 2)
python-nbsphinx @ 0.7.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 724, column: 2)
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
  • gnu/packages/sphinx.scm (line: 560, column: 2)
python-breathe @ 4.22.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/sphinx.scm (line: 607, column: 2)
python-breathe @ 4.22.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/sphinx.scm (line: 607, column: 2)
awscli @ 1.18.203inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/python-web.scm (line: 2818, column: 2)
python-nbclient @ 0.5.3inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-pip' should probably not be an input at all
  • gnu/packages/jupyter.scm (line: 267, column: 2)
python-nbclient @ 0.5.3inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/jupyter.scm (line: 267, column: 2)
python-jupyterlab-widgets @ 1.0.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/jupyter.scm (line: 246, column: 2)
python-jupyter-packaging @ 0.9.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/jupyter.scm (line: 215, column: 2)
python2-pyfakefs @ 3.7.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/check.scm (line: 2824, column: 2)
python-tempest-lib @ 1.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/openstack.scm (line: 334, column: 2)
python-stevedore @ 3.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/openstack.scm (line: 296, column: 2)
python-reno @ 2.7.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/openstack.scm (line: 557, column: 2)
python-oslo.log @ 3.36.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/openstack.scm (line: 488, column: 2)
python-oslo.config @ 5.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/openstack.scm (line: 381, column: 2)
python-keystoneclient @ 1.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/openstack.scm (line: 698, column: 2)
sooperlooper @ 1.7.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 120
  • gnu/packages/music.scm (line: 3901, column: 5)
python2-discogs-client @ 2.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
  • gnu/packages/music.scm (line: 4514, column: 17)
python-discogs-client @ 2.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
  • gnu/packages/music.scm (line: 4514, column: 17)
python-uqbar @ 0.5.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/graphviz.scm (line: 249, column: 2)
drumstick @ 2.1.1inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
  • gnu/packages/music.scm (line: 2719, column: 5)
beets-next @ 1.4.9-1.04ea754inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/music.scm (line: 3711, column: 7)
beets @ 1.4.9inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/music.scm (line: 3641, column: 5)
sorcer @ 1.1.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/music.scm (line: 5061, column: 12)
python2-pydot @ 1.4.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/graphviz.scm (line: 378, column: 2)
python-pyportmidi @ 217patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/music.scm (line: 2626, column: 2)
vmpk @ 0.8.2formatting

Look for formatting issues in the source

line 2759 is way too long (91 characters)
  • gnu/packages/music.scm (line: 2759, column: 0)
solfege @ 3.22.2formatting

Look for formatting issues in the source

line 1891 is way too long (92 characters)
  • gnu/packages/music.scm (line: 1891, column: 0)
rosegarden @ 20.12formatting

Look for formatting issues in the source

line 4988 is way too long (94 characters)
  • gnu/packages/music.scm (line: 4988, column: 0)
rosegarden @ 20.12formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/music.scm (line: 4989, column: 0)
gtklick @ 0.6.4formatting

Look for formatting issues in the source

line 1275 is way too long (94 characters)
  • gnu/packages/music.scm (line: 1275, column: 0)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5462, column 0
  • gnu/packages/music.scm (line: 5462, column: 0)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5463, column 0
  • gnu/packages/music.scm (line: 5463, column: 0)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5464, column 0
  • gnu/packages/music.scm (line: 5464, column: 0)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5465, column 0
  • gnu/packages/music.scm (line: 5465, column: 0)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5467, column 0
  • gnu/packages/music.scm (line: 5467, column: 0)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5474, column 0
  • gnu/packages/music.scm (line: 5474, column: 0)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5475, column 0
  • gnu/packages/music.scm (line: 5475, column: 0)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5476, column 0
  • gnu/packages/music.scm (line: 5476, column: 0)
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5477, column 0
  • gnu/packages/music.scm (line: 5477, column: 0)
drumstick @ 2.1.1formatting

Look for formatting issues in the source

line 2712 is way too long (91 characters)
  • gnu/packages/music.scm (line: 2712, column: 0)
mesa-opencl-icd @ 20.2.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gl.scm (line: 475, column: 2)
mesa-opencl @ 20.2.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gl.scm (line: 461, column: 2)
mesa-headers @ 20.2.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gl.scm (line: 484, column: 2)
mia @ 2.4.6inputs-should-be-native

Identify inputs that should be native inputs

'doxygen' should probably be a native input
  • gnu/packages/image-processing.scm (line: 142, column: 5)
geda-gaf @ 1.10.0inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
  • gnu/packages/engineering.scm (line: 253, column: 5)
librecad @ 2.2.0-rc2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/engineering.scm (line: 135, column: 12)
vtk @ 9.0.1formatting

Look for formatting issues in the source

line 296 is way too long (93 characters)
  • gnu/packages/image-processing.scm (line: 296, column: 0)
vtk @ 9.0.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/image-processing.scm (line: 301, column: 0)
verilator @ 4.110description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/fpga.scm (line: 545, column: 5)
rust-avif-serialize @ 0.6.5description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/crates-graphics.scm (line: 291, column: 5)
rust-async-process @ 1.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/crates-io.scm (line: 2994, column: 5)
python-pytools @ 2020.4description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/opencl.scm (line: 358, column: 5)
perl-test-object @ 0.08description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/perl-check.scm (line: 1083, column: 5)
perl-search-xapian @ 1.2.25.4description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/search.scm (line: 139, column: 5)
libjxr @ 1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
  • gnu/packages/image.scm (line: 520, column: 17)
hackrf @ 2018.01.1-0.43e6f99description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/radio.scm (line: 847, column: 6)
guile3.0-ncurses @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • guix/packages.scm (line: 464, column: 2)
ghc-unsafe @ 0.0description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/haskell-xyz.scm (line: 14486, column: 17)
ghc-rio @ 0.1.12.0description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/haskell-xyz.scm (line: 11399, column: 17)
ghc-hsyaml @ 0.1.2.0description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/haskell-xyz.scm (line: 6310, column: 17)
espeak-ng @ 1.50description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/speech.scm (line: 211, column: 5)
ecasound @ 2.9.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471
  • gnu/packages/audio.scm (line: 4782, column: 17)
config @ 0.0.0-1.c8ddc84description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/autotools.scm (line: 541, column: 19)
sonata @ 1.7.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/mpd.scm (line: 346, column: 5)
libreoffice @ 6.4.7.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/libreoffice.scm (line: 1109, column: 5)
python-requests @ 2.20.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-urllib3@1.24.3 and python-urllib3@1.26.2 collide
  • gnu/packages/python-web.scm (line: 2510, column: 2)
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
  • gnu/packages/maven.scm (line: 3592, column: 2)
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
  • gnu/packages/maven.scm (line: 3504, column: 2)
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
  • gnu/packages/maven.scm (line: 559, column: 2)
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
  • gnu/packages/maven.scm (line: 2412, column: 2)
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
  • gnu/packages/maven.scm (line: 2396, column: 2)
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
  • gnu/packages/maven.scm (line: 2424, column: 2)
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
  • gnu/packages/maven.scm (line: 2999, column: 2)
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
  • gnu/packages/maven.scm (line: 1205, column: 2)
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
  • gnu/packages/maven.scm (line: 2146, column: 2)
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
  • gnu/packages/maven.scm (line: 2945, column: 2)
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
  • gnu/packages/maven.scm (line: 1343, column: 2)
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
  • gnu/packages/maven.scm (line: 1378, column: 2)
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
  • gnu/packages/maven.scm (line: 2183, column: 2)
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
  • gnu/packages/maven.scm (line: 2164, column: 2)
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
  • gnu/packages/maven.scm (line: 2081, column: 2)
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
  • gnu/packages/maven.scm (line: 3623, column: 2)
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
  • gnu/packages/maven.scm (line: 2811, column: 2)
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
  • gnu/packages/maven.scm (line: 2871, column: 2)
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
  • gnu/packages/maven.scm (line: 2468, column: 2)
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
  • gnu/packages/maven.scm (line: 2699, column: 2)
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
  • gnu/packages/maven.scm (line: 2726, column: 2)
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
  • gnu/packages/maven.scm (line: 2649, column: 2)
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
  • gnu/packages/maven.scm (line: 1607, column: 2)
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
  • gnu/packages/maven.scm (line: 2562, column: 2)
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
  • gnu/packages/maven.scm (line: 3054, column: 2)
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
  • gnu/packages/maven.scm (line: 1703, column: 2)
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
  • gnu/packages/maven.scm (line: 2359, column: 2)
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
  • gnu/packages/maven.scm (line: 2600, column: 2)
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
  • gnu/packages/maven.scm (line: 2755, column: 2)
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
  • gnu/packages/maven.scm (line: 2068, column: 2)
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
  • gnu/packages/maven.scm (line: 2522, column: 2)
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
  • gnu/packages/maven.scm (line: 2224, column: 2)
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
  • gnu/packages/maven.scm (line: 3288, column: 2)
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
  • gnu/packages/maven.scm (line: 3389, column: 2)
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
  • gnu/packages/maven.scm (line: 3366, column: 2)
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
  • gnu/packages/maven.scm (line: 3309, column: 2)
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
  • gnu/packages/maven.scm (line: 3260, column: 2)
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
  • gnu/packages/maven.scm (line: 3194, column: 2)
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
  • gnu/packages/maven.scm (line: 410, column: 2)
perl-parent @ 5.30.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • guix/packages.scm (line: 464, column: 2)
perl-base @ 5.30.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • guix/packages.scm (line: 464, column: 2)
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
  • guix/packages.scm (line: 464, column: 2)
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
  • guix/packages.scm (line: 464, column: 2)
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
  • guix/packages.scm (line: 464, column: 2)
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
  • gnu/packages/base.scm (line: 1211, column: 2)
glibc-locales @ 2.31patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/base.scm (line: 1066, column: 2)
glibc-hurd-headers @ 2.31patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/base.scm (line: 1238, column: 2)
coreutils-minimal @ 8.32patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/base.scm (line: 408, column: 2)
binutils-gold @ 2.34patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/base.scm (line: 600, column: 2)
symmetrica @ 2.0patch-headers

Validate patch headers

symmetrica-bruch.patch: patch lacks comment and upstream status
  • gnu/packages/algebra.scm (line: 1384, column: 12)
steghide @ 0.5.1patch-headers

Validate patch headers

steghide-fixes.patch: patch lacks comment and upstream status
  • gnu/packages/image.scm (line: 1495, column: 12)
sdl-pango @ 0.1.2patch-headers

Validate patch headers

sdl-pango-header-guard.patch: patch lacks comment and upstream status
  • gnu/packages/sdl.scm (line: 335, column: 5)
python2-unittest2 @ 1.1.0patch-headers

Validate patch headers

python-unittest2-remove-argparse.patch: patch lacks comment and upstream status
  • gnu/packages/check.scm (line: 902, column: 5)
python-unittest2 @ 1.1.0patch-headers

Validate patch headers

python-unittest2-remove-argparse.patch: patch lacks comment and upstream status
  • gnu/packages/check.scm (line: 902, column: 5)
nsis-x86_64 @ 3.05patch-headers

Validate patch headers

nsis-env-passthru.patch: patch lacks comment and upstream status
  • gnu/packages/installers.scm (line: 38, column: 14)
nsis-i686 @ 3.05patch-headers

Validate patch headers

nsis-env-passthru.patch: patch lacks comment and upstream status
  • gnu/packages/installers.scm (line: 38, column: 14)
mono @ 4.4.1.0patch-headers

Validate patch headers

mono-mdoc-timestamping.patch: patch lacks comment and upstream status
  • gnu/packages/mono.scm (line: 42, column: 12)
mkbootimg @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 405, column: 12)
mkbootimg @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 405, column: 12)
mkbootimg @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 405, column: 12)
mkbootimg @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 405, column: 12)
lsh @ 2.1patch-headers

Validate patch headers

lsh-fix-x11-forwarding.patch: patch lacks comment and upstream status
  • gnu/packages/ssh.scm (line: 568, column: 12)
libmhash @ 0.9.9.9patch-headers

Validate patch headers

libmhash-hmac-fix-uaf.patch: patch lacks comment and upstream status
  • gnu/packages/mcrypt.scm (line: 90, column: 5)
gobject-introspection @ 1.62.0patch-headers

Validate patch headers

gobject-introspection-girepository.patch: patch lacks comment and upstream status
  • gnu/packages/glib.scm (line: 482, column: 5)
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 659, column: 12)
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 659, column: 12)
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 659, column: 12)
fastboot @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 659, column: 12)
cyrus-sasl @ 2.1.27patch-headers

Validate patch headers

cyrus-sasl-ac-try-run-fix.patch: patch lacks comment and upstream status
  • gnu/packages/cyrus-sasl.scm (line: 37, column: 11)
aws-checksums @ 0.1.11patch-headers

Validate patch headers

aws-checksums-cmake-prefix.patch: patch lacks comment and upstream status
  • gnu/packages/c.scm (line: 574, column: 12)
aws-c-io @ 0.9.2patch-headers

Validate patch headers

aws-c-io-cmake-prefix.patch: patch lacks comment and upstream status
  • gnu/packages/c.scm (line: 634, column: 12)
aws-c-io @ 0.9.2patch-headers

Validate patch headers

aws-c-io-disable-networking-tests.patch: patch lacks comment and upstream status
  • gnu/packages/c.scm (line: 634, column: 12)
aws-c-event-stream @ 0.2.7patch-headers

Validate patch headers

aws-c-event-stream-cmake-prefix.patch: patch lacks comment and upstream status
  • gnu/packages/c.scm (line: 601, column: 12)
aws-c-cal @ 0.4.5patch-headers

Validate patch headers

aws-c-cal-cmake-prefix.patch: patch lacks comment and upstream status
  • gnu/packages/c.scm (line: 665, column: 12)
apr @ 1.6.5patch-headers

Validate patch headers

apr-skip-getservbyname-test.patch: patch lacks comment and upstream status
  • gnu/packages/apr.scm (line: 34, column: 12)
android-libziparchive @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 323, column: 12)
android-libziparchive @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 323, column: 12)
android-libziparchive @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 323, column: 12)
android-libziparchive @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 323, column: 12)
android-libutils @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 619, column: 12)
android-libutils @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 619, column: 12)
android-libutils @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 619, column: 12)
android-libutils @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 619, column: 12)
android-libsparse @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 302, column: 12)
android-libsparse @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 302, column: 12)
android-libsparse @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 302, column: 12)
android-libsparse @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 302, column: 12)
android-liblog @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 195, column: 12)
android-liblog @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 195, column: 12)
android-liblog @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 195, column: 12)
android-liblog @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 195, column: 12)
android-libcutils @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 248, column: 12)
android-libcutils @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 248, column: 12)
android-libcutils @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 248, column: 12)
android-libcutils @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 248, column: 12)
adb @ 7.1.2_r36patch-headers

Validate patch headers

libutils-remove-damaging-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 358, column: 12)
adb @ 7.1.2_r36patch-headers

Validate patch headers

libutils-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 358, column: 12)
adb @ 7.1.2_r36patch-headers

Validate patch headers

adb-add-libraries.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 358, column: 12)
adb @ 7.1.2_r36patch-headers

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
  • gnu/packages/android.scm (line: 358, column: 12)
zita-resampler @ 1.6.2formatting

Look for formatting issues in the source

line 3739 is way too long (93 characters)
  • gnu/packages/audio.scm (line: 3739, column: 0)
zathura-pdf-poppler @ 0.3.0formatting

Look for formatting issues in the source

line 576 is way too long (107 characters)
  • gnu/packages/pdf.scm (line: 576, column: 0)
zathura-djvu @ 0.2.9formatting

Look for formatting issues in the source

line 490 is way too long (93 characters)
  • gnu/packages/pdf.scm (line: 490, column: 0)
wicd @ 1.7.4formatting

Look for formatting issues in the source

line 109 is way too long (95 characters)
  • gnu/packages/wicd.scm (line: 109, column: 0)
virt-manager @ 3.2.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/virtualization.scm (line: 1341, column: 0)
vamp @ 2.6formatting

Look for formatting issues in the source

line 3222 is way too long (94 characters)
  • gnu/packages/audio.scm (line: 3222, column: 0)
opencv @ 3.4.3formatting

Look for formatting issues in the source

line 432 is way too long (132 characters)
  • gnu/packages/image-processing.scm (line: 432, column: 0)
netpbm @ 10.78.3formatting

Look for formatting issues in the source

line 86 is way too long (127 characters)
  • gnu/packages/netpbm.scm (line: 86, column: 0)
libosinfo @ 1.7.1formatting

Look for formatting issues in the source

line 997 is way too long (106 characters)
  • gnu/packages/virtualization.scm (line: 997, column: 0)
libjxr @ 1.1formatting

Look for formatting issues in the source

line 521 is way too long (95 characters)
  • gnu/packages/image.scm (line: 521, column: 0)
guile @ 2.0.14formatting

Look for formatting issues in the source

line 189 is way too long (94 characters)
  • gnu/packages/guile.scm (line: 189, column: 0)
guile @ 2.0.14formatting

Look for formatting issues in the source

line 192 is way too long (93 characters)
  • gnu/packages/guile.scm (line: 192, column: 0)
glibc @ 2.31formatting

Look for formatting issues in the source

line 828 is way too long (98 characters)
  • gnu/packages/base.scm (line: 828, column: 0)
faad2 @ 2.8.8formatting

Look for formatting issues in the source

line 1739 is way too long (95 characters)
  • gnu/packages/audio.scm (line: 1739, column: 0)
dejagnu @ 1.6.2formatting

Look for formatting issues in the source

line 60 is way too long (91 characters)
  • gnu/packages/dejagnu.scm (line: 60, column: 0)
audacity @ 2.4.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/audio.scm (line: 719, column: 0)
python2-paste @ 3.0.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python-web.scm (line: 4160, column: 2)
python2-wtforms @ 2.1formatting

Look for formatting issues in the source

line 4142 is way too long (92 characters)
  • gnu/packages/python-web.scm (line: 4142, column: 0)
python2-wtforms @ 2.1formatting

Look for formatting issues in the source

line 4143 is way too long (100 characters)
  • gnu/packages/python-web.scm (line: 4143, column: 0)
python-wtforms @ 2.1formatting

Look for formatting issues in the source

line 4142 is way too long (92 characters)
  • gnu/packages/python-web.scm (line: 4142, column: 0)
python-wtforms @ 2.1formatting

Look for formatting issues in the source

line 4143 is way too long (100 characters)
  • gnu/packages/python-web.scm (line: 4143, column: 0)
perl-digest-sha @ 6.02description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 82
  • gnu/packages/perl.scm (line: 3853, column: 5)
perl-extutils-pkgconfig @ 1.16inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
  • gnu/packages/perl.scm (line: 4339, column: 2)
tinmop @ 0.6.2formatting

Look for formatting issues in the source

line 902 is way too long (122 characters)
  • gnu/packages/web-browsers.scm (line: 902, column: 0)
perl-file-which @ 1.23description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/perl.scm (line: 4867, column: 5)
jucipp @ 1.6.3description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/text-editors.scm (line: 365, column: 5)
spice-gtk @ 0.37inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/spice.scm (line: 160, column: 6)
openssh-sans-x @ 8.6p1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/ssh.scm (line: 300, column: 2)
icecat @ 78.10.0-guix0-preview1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/gnuzilla.scm (line: 916, column: 0)
tuxmath @ 2.0.3description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/education.scm (line: 934, column: 17)
libsigrok @ 0.5.2formatting

Look for formatting issues in the source

line 216 is way too long (101 characters)
  • gnu/packages/electronics.scm (line: 216, column: 0)
libsigrok @ 0.5.2formatting

Look for formatting issues in the source

line 217 is way too long (92 characters)
  • gnu/packages/electronics.scm (line: 217, column: 0)
flatbuffers @ 1.10.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/serialization.scm (line: 481, column: 6)
xwallpaper @ 0.6.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 72
  • gnu/packages/xdisorg.scm (line: 2345, column: 5)
go-github-com-mesilliac-pulse-simple @ 0.0.0-0.75ac54einputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
  • gnu/packages/golang.scm (line: 6819, column: 4)
mailutils @ 3.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
  • gnu/packages/mail.scm (line: 345, column: 5)
guile2.2-mailutils @ 3.10inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
  • gnu/packages/mail.scm (line: 406, column: 5)
astroid @ 0.15inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/mail.scm (line: 901, column: 5)
guile2.2-mailutils @ 3.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/mail.scm (line: 402, column: 2)
wine64-staging @ 6.6inputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
  • gnu/packages/wine.scm (line: 475, column: 12)
wine-staging @ 6.6inputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
  • gnu/packages/wine.scm (line: 398, column: 12)
wine64-staging @ 6.6formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/wine.scm (line: 514, column: 0)
wine-staging @ 6.6formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/wine.scm (line: 434, column: 0)
shell-functools @ 0.3.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 121, 206
  • gnu/packages/shellutils.scm (line: 390, column: 17)
sh-z @ 1.11description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/shellutils.scm (line: 167, column: 5)
python-orange-canvas-core @ 0.1.19inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/orange.scm (line: 35, column: 2)
python-faiss @ 1.5.0inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
  • gnu/packages/graph.scm (line: 413, column: 5)
tumbler @ 4.16.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/xfce.scm (line: 407, column: 0)
libextractor @ 1.11formatting

Look for formatting issues in the source

line 128 is way too long (140 characters)
  • gnu/packages/gnunet.scm (line: 128, column: 0)
python-pytest-dependency @ 0.5.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/check.scm (line: 2920, column: 2)
sbcl-quri @ 0.3.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 68
  • gnu/packages/lisp-xyz.scm (line: 4467, column: 5)
sbcl-md5 @ 2.0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
  • gnu/packages/lisp-xyz.scm (line: 3959, column: 5)
sbcl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/lisp-xyz.scm (line: 5675, column: 7)
sbcl-cl-reexport @ 0.1-1.312f366description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/lisp-xyz.scm (line: 6041, column: 19)
sbcl-cl-cookie @ 0.9.10-1.cea55aedescription

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/lisp-xyz.scm (line: 6081, column: 19)
sbcl-circular-streams @ 0.1.0-1.e770baddescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 79
  • gnu/packages/lisp-xyz.scm (line: 4884, column: 6)
ecl-quri @ 0.3.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 68
  • gnu/packages/lisp-xyz.scm (line: 4467, column: 5)
ecl-md5 @ 2.0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
  • gnu/packages/lisp-xyz.scm (line: 3967, column: 2)
ecl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/lisp-xyz.scm (line: 5675, column: 7)
ecl-cl-reexport @ 0.1-1.312f366description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/lisp-xyz.scm (line: 6041, column: 19)
ecl-cl-cookie @ 0.9.10-1.cea55aedescription

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/lisp-xyz.scm (line: 6081, column: 19)
ecl-circular-streams @ 0.1.0-1.e770baddescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 79
  • gnu/packages/lisp-xyz.scm (line: 4884, column: 6)
cl-reexport @ 0.1-1.312f366description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/lisp-xyz.scm (line: 6041, column: 19)
cl-quri @ 0.3.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 68
  • gnu/packages/lisp-xyz.scm (line: 4467, column: 5)
cl-md5 @ 2.0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 85
  • gnu/packages/lisp-xyz.scm (line: 3959, column: 5)
cl-fare-utils @ 1.0.0.5-1.66e9c6fdescription

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/lisp-xyz.scm (line: 5675, column: 7)
cl-circular-streams @ 0.1.0-1.e770baddescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 79
  • gnu/packages/lisp-xyz.scm (line: 4884, column: 6)
sbcl-cl-gobject-introspection @ 0.3-1.d0136c8inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/lisp-xyz.scm (line: 7346, column: 7)
ecl-cl-gobject-introspection @ 0.3-1.d0136c8inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/lisp-xyz.scm (line: 7346, column: 7)
cl-gobject-introspection @ 0.3-1.d0136c8inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/lisp-xyz.scm (line: 7346, column: 7)
sbcl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 6344 is way too long (91 characters)
  • gnu/packages/lisp-xyz.scm (line: 6344, column: 0)
ecl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 6344 is way too long (91 characters)
  • gnu/packages/lisp-xyz.scm (line: 6344, column: 0)
cl-optima @ 1.0-1.373b245formatting

Look for formatting issues in the source

line 6344 is way too long (91 characters)
  • gnu/packages/lisp-xyz.scm (line: 6344, column: 0)
ppsspp @ 1.11.3description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/emulators.scm (line: 2330, column: 5)
libmypaint @ 1.6.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gimp.scm (line: 434, column: 5)
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

line 502 is way too long (107 characters)
  • gnu/packages/gimp.scm (line: 502, column: 0)
xorg-server-xwayland @ 1.20.11patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/xorg.scm (line: 5462, column: 2)
gst-transcoder @ 1.18.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • guix/packages.scm (line: 464, column: 2)
xproto @ 7.0.31formatting

Look for formatting issues in the source

line 4982 is way too long (91 characters)
  • gnu/packages/xorg.scm (line: 4982, column: 0)
xpra @ 4.0.6formatting

Look for formatting issues in the source

tabulation on line 6354, column 0
  • gnu/packages/xorg.scm (line: 6354, column: 0)
xf86-video-intel @ 2.99.917-17.ad5540fformatting

Look for formatting issues in the source

line 3026 is way too long (91 characters)
  • gnu/packages/xorg.scm (line: 3026, column: 0)
wpa-supplicant-minimal @ 2.9description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/admin.scm (line: 1825, column: 5)
wpa-supplicant-gui @ 2.9description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/admin.scm (line: 1866, column: 2)
wpa-supplicant @ 2.9description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/admin.scm (line: 1840, column: 2)
wpa-supplicant-minimal @ 2.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/admin.scm (line: 1732, column: 2)
wpa-supplicant-gui @ 2.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/admin.scm (line: 1866, column: 2)
hostapd @ 2.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/admin.scm (line: 1908, column: 2)
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
  • gnu/packages/admin.scm (line: 2478, column: 2)
libstdc++-doc @ 9.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 917, column: 2)
libstdc++-doc @ 5.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 917, column: 2)
libiberty @ 7.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 684, column: 2)
libgccjit @ 9.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 781, column: 2)
gccgo @ 4.9.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc++ @ 9.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc++ @ 8.4.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc++ @ 7.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc++ @ 6.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc++ @ 5.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc++ @ 4.9.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc++ @ 4.8.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc++ @ 10.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc @ 9.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc @ 8.4.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc @ 7.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc @ 6.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc @ 5.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc @ 4.9.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc @ 4.8.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
gcc-objc @ 10.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gcc.scm (line: 719, column: 2)
password-store @ 1.7.3-1.918992cformatting

Look for formatting issues in the source

line 513 is way too long (91 characters)
  • gnu/packages/password-utils.scm (line: 513, column: 0)
ocaml-llvm @ 9.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/llvm.scm (line: 1311, column: 4)
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
  • gnu/packages/llvm.scm (line: 1286, column: 2)
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
  • gnu/packages/llvm.scm (line: 1262, column: 2)
clang-runtime @ 3.5.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/llvm.scm (line: 852, column: 4)
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
  • gnu/packages/llvm.scm (line: 852, column: 4)
clang @ 12.0.0formatting

Look for formatting issues in the source

line 369 is way too long (91 characters)
  • gnu/packages/llvm.scm (line: 369, column: 0)
fcitx-qt5 @ 1.2.6inputs-should-be-native

Identify inputs that should be native inputs

'intltool' should probably be a native input
  • gnu/packages/fcitx.scm (line: 87, column: 5)
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
  • guix/packages.scm (line: 1096, column: 15)
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
  • guix/packages.scm (line: 1096, column: 15)
maven-wagon-provider-api @ 3.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/dg3xsbsvzw4vlzxlvpzxraqayq5h8big-maven-wagon-provider-api-3.3.4 and /gnu/store/z161wf1mmfhkfhazjqvnlhp02rjdx8l5-maven-wagon-provider-api-3.3.4 collide
  • gnu/packages/maven.scm (line: 649, column: 2)
python2-minimal @ 2.7.17patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python.scm (line: 561, column: 2)
python-next @ 3.9.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python.scm (line: 527, column: 2)
python-minimal @ 3.8.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python.scm (line: 574, column: 2)
python-debug @ 3.8.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python.scm (line: 588, column: 2)
guile2.2-gnutls @ 3.6.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/tls.scm (line: 279, column: 2)
guile2.0-gnutls @ 3.6.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/tls.scm (line: 263, column: 2)
gnutls-dane @ 3.6.15patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/tls.scm (line: 273, column: 2)
pypy3 @ 7.3.1formatting

Look for formatting issues in the source

line 865 is way too long (91 characters)
  • gnu/packages/python.scm (line: 865, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 471, column 0
  • gnu/packages/tls.scm (line: 471, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 472, column 0
  • gnu/packages/tls.scm (line: 472, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 473, column 0
  • gnu/packages/tls.scm (line: 473, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 474, column 0
  • gnu/packages/tls.scm (line: 474, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 475, column 0
  • gnu/packages/tls.scm (line: 475, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 476, column 0
  • gnu/packages/tls.scm (line: 476, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 477, column 0
  • gnu/packages/tls.scm (line: 477, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 478, column 0
  • gnu/packages/tls.scm (line: 478, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 479, column 0
  • gnu/packages/tls.scm (line: 479, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 481, column 0
  • gnu/packages/tls.scm (line: 481, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 482, column 0
  • gnu/packages/tls.scm (line: 482, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 483, column 0
  • gnu/packages/tls.scm (line: 483, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 484, column 0
  • gnu/packages/tls.scm (line: 484, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 485, column 0
  • gnu/packages/tls.scm (line: 485, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 487, column 0
  • gnu/packages/tls.scm (line: 487, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 488, column 0
  • gnu/packages/tls.scm (line: 488, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 489, column 0
  • gnu/packages/tls.scm (line: 489, column: 0)
openssl @ 1.0.2uformatting

Look for formatting issues in the source

tabulation on line 490, column 0
  • gnu/packages/tls.scm (line: 490, column: 0)
blasr-libcpp @ 5.3.3formatting

Look for formatting issues in the source

line 647 is way too long (95 characters)
  • gnu/packages/bioinformatics.scm (line: 647, column: 0)
u-boot-wandboard @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-vexpress-ca9x4 @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-sifive-fu540 @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-rockpro64-rk3399 @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 909, column: 4)
u-boot-rock64-rk3328 @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 871, column: 4)
u-boot-qemu-riscv64-smode @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 859, column: 4)
u-boot-qemu-riscv64 @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-puma-rk3399 @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 836, column: 4)
u-boot-pinebook-pro-rk3399 @ 2021.07-rc1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 929, column: 4)
u-boot-pinebook @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 772, column: 4)
u-boot-pine64-plus @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 742, column: 4)
u-boot-pine64-lts @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 742, column: 4)
u-boot-novena @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 811, column: 19)
u-boot-nintendo-nes-classic-edition @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-mx6cuboxi @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-malta @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-firefly-rk3399 @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 889, column: 4)
u-boot-cubietruck @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-cubieboard @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-bananapi-m2-ultra @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-am335x-evm @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-am335x-boneblack @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 718, column: 19)
u-boot-a20-olinuxino-micro @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-a20-olinuxino-lime2 @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-a20-olinuxino-lime @ 2021.04description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot @ 2021.07-rc1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
  • gnu/packages/bootloaders.scm (line: 517, column: 2)
pan @ 0.146description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 71
  • gnu/packages/mail.scm (line: 3862, column: 17)
catdoc @ 0.95description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 157
  • gnu/packages/textutils.scm (line: 610, column: 17)
sendmail @ 8.15.2inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
  • gnu/packages/mail.scm (line: 2882, column: 5)
opencc @ 1.1.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/textutils.scm (line: 1107, column: 2)
gajim @ 1.3.2inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/messaging.scm (line: 1109, column: 5)
u-boot-wandboard @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-vexpress-ca9x4 @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-tools @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 532, column: 2)
u-boot-sifive-fu540 @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-rockpro64-rk3399 @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 909, column: 4)
u-boot-rock64-rk3328 @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 871, column: 4)
u-boot-qemu-riscv64-smode @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 859, column: 4)
u-boot-qemu-riscv64 @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-puma-rk3399 @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 836, column: 4)
u-boot-pinebook-pro-rk3399 @ 2021.07-rc1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 929, column: 4)
u-boot-pinebook @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 772, column: 4)
u-boot-pine64-plus @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 742, column: 4)
u-boot-pine64-lts @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 742, column: 4)
u-boot-novena @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 809, column: 4)
u-boot-nintendo-nes-classic-edition @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-mx6cuboxi @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-malta @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-firefly-rk3399 @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 889, column: 4)
u-boot-cubietruck @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-cubieboard @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-bananapi-m2-ultra @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-am335x-evm @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-am335x-boneblack @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 715, column: 4)
u-boot-a20-olinuxino-micro @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-a20-olinuxino-lime2 @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
u-boot-a20-olinuxino-lime @ 2021.04patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/bootloaders.scm (line: 635, column: 4)
python2-pygpgme @ 0.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gnupg.scm (line: 529, column: 2)
python-pygpgme @ 0.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gnupg.scm (line: 529, column: 2)
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
  • gnu/packages/mail.scm (line: 3439, column: 2)
openmpi-thread-multiple @ 4.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/mpi.scm (line: 359, column: 2)
libchop @ 0.5.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/backup.scm (line: 491, column: 2)
java-openmpi @ 4.1.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/mpi.scm (line: 315, column: 2)
emacs-xwidgets @ 27.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/emacs.scm (line: 382, column: 2)
emacs-wide-int @ 27.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/emacs.scm (line: 441, column: 2)
emacs-no-x-toolkit @ 27.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/emacs.scm (line: 424, column: 2)
emacs-no-x @ 27.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/emacs.scm (line: 401, column: 2)
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
  • gnu/packages/emacs.scm (line: 308, column: 4)
emacs-minimal @ 27.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/emacs.scm (line: 361, column: 2)
gajim @ 1.3.2patch-headers

Validate patch headers

gajim-honour-GAJIM_PLUGIN_PATH.patch: patch lacks comment and upstream status
  • gnu/packages/messaging.scm (line: 1026, column: 5)
u-boot-wandboard @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-vexpress-ca9x4 @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-tools @ 2021.04formatting

Look for formatting issues in the source

line 561 is way too long (91 characters)
  • gnu/packages/bootloaders.scm (line: 561, column: 0)
u-boot-tools @ 2021.04formatting

Look for formatting issues in the source

line 583 is way too long (97 characters)
  • gnu/packages/bootloaders.scm (line: 583, column: 0)
u-boot-sifive-fu540 @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-qemu-riscv64 @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-pinebook @ 2021.04formatting

Look for formatting issues in the source

line 783 is way too long (127 characters)
  • gnu/packages/bootloaders.scm (line: 783, column: 0)
u-boot-pine64-plus @ 2021.04formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/bootloaders.scm (line: 758, column: 0)
u-boot-pine64-lts @ 2021.04formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/bootloaders.scm (line: 758, column: 0)
u-boot-nintendo-nes-classic-edition @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-mx6cuboxi @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-malta @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-cubietruck @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-cubieboard @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-bananapi-m2-ultra @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-am335x-evm @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-am335x-boneblack @ 2021.04formatting

Look for formatting issues in the source

line 734 is way too long (95 characters)
  • gnu/packages/bootloaders.scm (line: 734, column: 0)
u-boot-a20-olinuxino-micro @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-a20-olinuxino-lime2 @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot-a20-olinuxino-lime @ 2021.04formatting

Look for formatting issues in the source

line 693 is way too long (93 characters)
  • gnu/packages/bootloaders.scm (line: 693, column: 0)
u-boot @ 2021.07-rc1formatting

Look for formatting issues in the source

tabulation on line 521, column 0
  • gnu/packages/bootloaders.scm (line: 521, column: 0)
python-mailman-hyperkitty @ 1.1.0formatting

Look for formatting issues in the source

line 3455 is way too long (168 characters)
  • gnu/packages/mail.scm (line: 3455, column: 0)
openmpi @ 4.1.1formatting

Look for formatting issues in the source

line 276 is way too long (94 characters)
  • gnu/packages/mpi.scm (line: 276, column: 0)
openmpi @ 4.1.1formatting

Look for formatting issues in the source

line 278 is way too long (96 characters)
  • gnu/packages/mpi.scm (line: 278, column: 0)
libsecp256k1 @ 20200615-1.dbd41dbformatting

Look for formatting issues in the source

line 1118 is way too long (106 characters)
  • gnu/packages/crypto.scm (line: 1118, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 253, column 0
  • gnu/packages/backup.scm (line: 253, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 254, column 0
  • gnu/packages/backup.scm (line: 254, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 255, column 0
  • gnu/packages/backup.scm (line: 255, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 256, column 0
  • gnu/packages/backup.scm (line: 256, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 257, column 0
  • gnu/packages/backup.scm (line: 257, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 258, column 0
  • gnu/packages/backup.scm (line: 258, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 259, column 0
  • gnu/packages/backup.scm (line: 259, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 260, column 0
  • gnu/packages/backup.scm (line: 260, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 261, column 0
  • gnu/packages/backup.scm (line: 261, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 264, column 0
  • gnu/packages/backup.scm (line: 264, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 265, column 0
  • gnu/packages/backup.scm (line: 265, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 267, column 0
  • gnu/packages/backup.scm (line: 267, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 268, column 0
  • gnu/packages/backup.scm (line: 268, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 269, column 0
  • gnu/packages/backup.scm (line: 269, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 270, column 0
  • gnu/packages/backup.scm (line: 270, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 271, column 0
  • gnu/packages/backup.scm (line: 271, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 273, column 0
  • gnu/packages/backup.scm (line: 273, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 274, column 0
  • gnu/packages/backup.scm (line: 274, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 275, column 0
  • gnu/packages/backup.scm (line: 275, column: 0)
libarchive @ 3.4.2formatting

Look for formatting issues in the source

tabulation on line 276, column 0
  • gnu/packages/backup.scm (line: 276, column: 0)
appstream-glib @ 0.7.18formatting

Look for formatting issues in the source

line 1088 is way too long (93 characters)
  • gnu/packages/glib.scm (line: 1088, column: 0)
laminar @ 1.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/ci.scm (line: 216, column: 5)
laminar @ 1.0formatting

Look for formatting issues in the source

line 239 is way too long (97 characters)
  • gnu/packages/ci.scm (line: 239, column: 0)
laminar @ 1.0formatting

Look for formatting issues in the source

line 241 is way too long (137 characters)
  • gnu/packages/ci.scm (line: 241, column: 0)
perl-specio @ 0.38description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 185, 314
  • gnu/packages/perl.scm (line: 8908, column: 17)
perl-file-readbackwards @ 1.06description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 47
  • gnu/packages/perl.scm (line: 4673, column: 17)
perl-devel-globaldestruction @ 0.14description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/perl.scm (line: 3569, column: 17)
perl-class-load @ 0.25description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/perl.scm (line: 1464, column: 17)
cockatrice @ 2.8.0inputs-should-be-native

Identify inputs that should be native inputs

'qttools' should probably be a native input
  • gnu/packages/games.scm (line: 928, column: 7)
bsd-games @ 2.17.0patch-headers

Validate patch headers

bsd-games-gamescreen.h.patch: patch lacks comment and upstream status
  • gnu/packages/games.scm (line: 640, column: 5)
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 9495 is way too long (97 characters)
  • gnu/packages/perl.scm (line: 9495, column: 0)
rapicorn @ 16.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-cython' should probably be a native input
  • gnu/packages/graphics.scm (line: 1401, column: 5)
ctl @ 1.5.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/graphics.scm (line: 1428, column: 12)
openexr @ 2.5.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/graphics.scm (line: 1082, column: 2)
blender @ 2.92.0formatting

Look for formatting issues in the source

line 541 is way too long (97 characters)
  • gnu/packages/graphics.scm (line: 541, column: 0)
dico @ 2.11inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
  • gnu/packages/dico.scm (line: 70, column: 5)
julia-openspecfun-jll @ 0.5.3+4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 129
  • gnu/packages/julia-xyz.scm (line: 1083, column: 17)
julia-compilersupportlibraries-jll @ 0.4.0+1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 134
  • gnu/packages/julia-xyz.scm (line: 396, column: 17)
julia-chainrulestestutils @ 0.6.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 260
  • gnu/packages/julia-xyz.scm (line: 250, column: 17)
cgit @ 1.2.3inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
  • gnu/packages/version-control.scm (line: 990, column: 5)
cgit @ 1.2.3inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/version-control.scm (line: 990, column: 5)
julia-compilersupportlibraries-jll @ 0.4.0+1formatting

Look for formatting issues in the source

line 368 is way too long (91 characters)
  • gnu/packages/julia-xyz.scm (line: 368, column: 0)
git-crypt @ 0.6.0formatting

Look for formatting issues in the source

line 834 is way too long (91 characters)
  • gnu/packages/version-control.scm (line: 834, column: 0)
bazaar @ 2.7.0formatting

Look for formatting issues in the source

line 161 is way too long (93 characters)
  • gnu/packages/version-control.scm (line: 161, column: 0)
r-wmtsa @ 2.0-3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 105, 128
  • gnu/packages/cran.scm (line: 5982, column: 5)
r-sapa @ 2.0-3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 97, 120
  • gnu/packages/cran.scm (line: 5889, column: 17)
r-r2glmm @ 0.1.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 173, 176
  • gnu/packages/cran.scm (line: 11294, column: 5)
r-palmerpenguins @ 0.1.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 268
  • gnu/packages/cran.scm (line: 2717, column: 5)
r-dplyr @ 1.0.5description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/statistics.scm (line: 1731, column: 5)
r-cmprsk @ 2.2-10description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 242
  • gnu/packages/cran.scm (line: 13618, column: 5)
r-circular @ 0.4-93description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 98, 123
  • gnu/packages/cran.scm (line: 11637, column: 5)
r-bootstrap @ 2019.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 92, 105
  • gnu/packages/cran.scm (line: 13477, column: 5)
r-boot @ 1.3-28description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 125, 142
  • gnu/packages/statistics.scm (line: 431, column: 5)
r-arm @ 1.11-2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 46, 60
  • gnu/packages/cran.scm (line: 11612, column: 5)
r-squarem @ 2021.1formatting

Look for formatting issues in the source

line 4002 is way too long (91 characters)
  • gnu/packages/cran.scm (line: 4002, column: 0)
r-shiny @ 1.6.0formatting

Look for formatting issues in the source

line 1735 is way too long (103 characters)
  • gnu/packages/cran.scm (line: 1735, column: 0)
r-shiny @ 1.6.0formatting

Look for formatting issues in the source

line 1743 is way too long (94 characters)
  • gnu/packages/cran.scm (line: 1743, column: 0)
r-shiny @ 1.6.0formatting

Look for formatting issues in the source

line 1775 is way too long (92 characters)
  • gnu/packages/cran.scm (line: 1775, column: 0)
r-bslib @ 0.2.4formatting

Look for formatting issues in the source

line 1703 is way too long (102 characters)
  • gnu/packages/cran.scm (line: 1703, column: 0)
r-abps @ 0.3formatting

Look for formatting issues in the source

line 9554 is way too long (93 characters)
  • gnu/packages/cran.scm (line: 9554, column: 0)
r-xyz @ 0.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 232, 243, 262
  • gnu/packages/cran.scm (line: 16206, column: 5)
r-topicmodels @ 0.2-12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 151
  • gnu/packages/cran.scm (line: 22295, column: 5)
r-tidyr @ 1.1.3description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/statistics.scm (line: 3798, column: 5)
r-systemfonts @ 1.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/cran.scm (line: 18298, column: 5)
r-rstan @ 2.21.2description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/cran.scm (line: 23298, column: 5)
r-oai @ 0.3.0description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/cran.scm (line: 23737, column: 17)
r-minqa @ 1.2.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 133, 136, 139
  • gnu/packages/statistics.scm (line: 5059, column: 6)
r-iml @ 0.10.0description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/cran.scm (line: 24896, column: 5)
r-iheatmapr @ 0.5.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/cran.scm (line: 23008, column: 5)
r-hapassoc @ 1.2-8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 139
  • gnu/packages/cran.scm (line: 16065, column: 5)
r-fda @ 5.1.9description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 92, 113
  • gnu/packages/cran.scm (line: 20768, column: 5)
r-esc @ 0.5.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 178
  • gnu/packages/statistics.scm (line: 6103, column: 6)
r-dorng @ 1.8.2description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/cran.scm (line: 14039, column: 5)
r-diagram @ 1.6.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 336
  • gnu/packages/cran.scm (line: 21674, column: 5)
r-clusterr @ 1.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 606, 945
  • gnu/packages/cran.scm (line: 25274, column: 5)
r-cardata @ 3.0-4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 45, 56
  • gnu/packages/statistics.scm (line: 5268, column: 5)
r-brms @ 2.15.0description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/cran.scm (line: 24316, column: 5)
r-brms @ 2.15.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 109, 532, 653, 784
  • gnu/packages/cran.scm (line: 24316, column: 5)
python-rpy2 @ 3.3.5description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/statistics.scm (line: 5805, column: 17)
r-haplo-stats @ 1.8.6formatting

Look for formatting issues in the source

line 15797 is way too long (103 characters)
  • gnu/packages/cran.scm (line: 15797, column: 0)
r-gamlss-dist @ 5.3-2formatting

Look for formatting issues in the source

line 14356 is way too long (91 characters)
  • gnu/packages/cran.scm (line: 14356, column: 0)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 17086 is way too long (96 characters)
  • gnu/packages/cran.scm (line: 17086, column: 0)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 17100 is way too long (96 characters)
  • gnu/packages/cran.scm (line: 17100, column: 0)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 17107 is way too long (117 characters)
  • gnu/packages/cran.scm (line: 17107, column: 0)
r-flexdashboard @ 0.5.2formatting

Look for formatting issues in the source

line 17114 is way too long (100 characters)
  • gnu/packages/cran.scm (line: 17114, column: 0)
r-esc @ 0.5.1formatting

Look for formatting issues in the source

line 6104 is way too long (94 characters)
  • gnu/packages/statistics.scm (line: 6104, column: 0)
r-colourpicker @ 1.1.0formatting

Look for formatting issues in the source

line 14465 is way too long (94 characters)
  • gnu/packages/cran.scm (line: 14465, column: 0)
python-rpy2 @ 3.3.5formatting

Look for formatting issues in the source

line 5747 is way too long (104 characters)
  • gnu/packages/statistics.scm (line: 5747, column: 0)
python-rpy2 @ 3.3.5formatting

Look for formatting issues in the source

line 5754 is way too long (104 characters)
  • gnu/packages/statistics.scm (line: 5754, column: 0)
r-yapsa @ 1.16.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 93, 96
  • gnu/packages/bioconductor.scm (line: 5988, column: 5)
r-rgadem @ 2.38.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioconductor.scm (line: 5363, column: 5)
r-mixomics @ 6.14.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioconductor.scm (line: 7596, column: 5)
r-iclusterplus @ 1.26.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioconductor.scm (line: 6553, column: 5)
r-biosigner @ 1.18.2description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/bioconductor.scm (line: 6918, column: 5)
r-biocio @ 1.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/bioconductor.scm (line: 10527, column: 6)
r-bioassayr @ 1.28.3description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioconductor.scm (line: 8927, column: 5)
r-unifiedwmwqpcr @ 1.26.0formatting

Look for formatting issues in the source

line 8429 is way too long (92 characters)
  • gnu/packages/bioconductor.scm (line: 8429, column: 0)
r-monocle @ 2.18.0formatting

Look for formatting issues in the source

line 4130 is way too long (101 characters)
  • gnu/packages/bioconductor.scm (line: 4130, column: 0)
r-lumi @ 2.42.0formatting

Look for formatting issues in the source

line 4550 is way too long (95 characters)
  • gnu/packages/bioconductor.scm (line: 4550, column: 0)
r-genomicinteractions @ 1.24.0formatting

Look for formatting issues in the source

line 3350 is way too long (92 characters)
  • gnu/packages/bioconductor.scm (line: 3350, column: 0)
r-cner @ 1.26.0formatting

Look for formatting issues in the source

line 10134 is way too long (109 characters)
  • gnu/packages/bioconductor.scm (line: 10134, column: 0)
busybox @ 1.33.1formatting

Look for formatting issues in the source

line 93 is way too long (92 characters)
  • gnu/packages/busybox.scm (line: 93, column: 0)
r-survminer @ 0.4.9description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/cran.scm (line: 25631, column: 5)
r-lpme @ 1.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 153
  • gnu/packages/cran.scm (line: 26997, column: 6)
r-fontbitstreamvera @ 0.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 57
  • gnu/packages/cran.scm (line: 27312, column: 5)
r-aws-signature @ 0.6.0description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/cran.scm (line: 27022, column: 5)
r-freetypeharfbuzz @ 0.2.6formatting

Look for formatting issues in the source

tabulation on line 27401, column 0
  • gnu/packages/cran.scm (line: 27401, column: 0)
r-freetypeharfbuzz @ 0.2.6formatting

Look for formatting issues in the source

tabulation on line 27402, column 0
  • gnu/packages/cran.scm (line: 27402, column: 0)
r-freetypeharfbuzz @ 0.2.6formatting

Look for formatting issues in the source

tabulation on line 27403, column 0
  • gnu/packages/cran.scm (line: 27403, column: 0)
r-freetypeharfbuzz @ 0.2.6formatting

Look for formatting issues in the source

tabulation on line 27404, column 0
  • gnu/packages/cran.scm (line: 27404, column: 0)
r-freetypeharfbuzz @ 0.2.6formatting

Look for formatting issues in the source

tabulation on line 27405, column 0
  • gnu/packages/cran.scm (line: 27405, column: 0)
r-freetypeharfbuzz @ 0.2.6formatting

Look for formatting issues in the source

tabulation on line 27406, column 0
  • gnu/packages/cran.scm (line: 27406, column: 0)
r-freetypeharfbuzz @ 0.2.6formatting

Look for formatting issues in the source

tabulation on line 27407, column 0
  • gnu/packages/cran.scm (line: 27407, column: 0)
spiped @ 1.6.1formatting

Look for formatting issues in the source

line 2623 is way too long (94 characters)
  • gnu/packages/networking.scm (line: 2623, column: 0)
restinio @ 0.6.13formatting

Look for formatting issues in the source

line 3435 is way too long (105 characters)
  • gnu/packages/networking.scm (line: 3435, column: 0)
restinio @ 0.6.13formatting

Look for formatting issues in the source

line 3449 is way too long (95 characters)
  • gnu/packages/networking.scm (line: 3449, column: 0)
lepton-eda @ 1.9.14-20210407inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
  • gnu/packages/engineering.scm (line: 304, column: 5)
freehdl @ 0.0.8inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
  • gnu/packages/engineering.scm (line: 2012, column: 5)
freehdl @ 0.0.8inputs-should-be-native

Identify inputs that should be native inputs

'libtool' should probably be a native input
  • gnu/packages/engineering.scm (line: 2012, column: 5)
meshlab @ 2020.06formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/engineering.scm (line: 2710, column: 0)
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

line 680 is way too long (91 characters)
  • gnu/packages/engineering.scm (line: 680, column: 0)
fritzing @ 0.9.3bformatting

Look for formatting issues in the source

line 681 is way too long (99 characters)
  • gnu/packages/engineering.scm (line: 681, column: 0)
freehdl @ 0.0.8formatting

Look for formatting issues in the source

line 1936 is way too long (104 characters)
  • gnu/packages/engineering.scm (line: 1936, column: 0)
texlive-latex-cyrillic @ 51265description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 166
  • gnu/packages/tex.scm (line: 3575, column: 5)
texlive-hyphen-occitan @ 51265description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/tex.scm (line: 2047, column: 17)
texlive-hyphen-latin @ 51265description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/tex.scm (line: 1969, column: 17)
texlive-fonts-iwona @ 0.995bdescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 42
  • gnu/packages/tex.scm (line: 5625, column: 17)
texlive-latex-hyperref @ 6.84a2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/tex.scm (line: 3010, column: 12)
texlive-ruhyphen @ 51265formatting

Look for formatting issues in the source

line 2517 is way too long (92 characters)
  • gnu/packages/tex.scm (line: 2517, column: 0)
texlive-ruhyphen @ 51265formatting

Look for formatting issues in the source

line 2520 is way too long (93 characters)
  • gnu/packages/tex.scm (line: 2520, column: 0)
texlive-latex-pgf @ 51265formatting

Look for formatting issues in the source

line 6909 is way too long (98 characters)
  • gnu/packages/tex.scm (line: 6909, column: 0)
texlive-latex-l3packages @ 51265formatting

Look for formatting issues in the source

line 3178 is way too long (91 characters)
  • gnu/packages/tex.scm (line: 3178, column: 0)
texlive-latex-l3packages @ 51265formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/tex.scm (line: 3196, column: 0)
texlive-latex-base @ 51265formatting

Look for formatting issues in the source

tabulation on line 2628, column 22
  • gnu/packages/tex.scm (line: 2628, column: 22)
texlive-hyph-utf8 @ 51265formatting

Look for formatting issues in the source

line 2339 is way too long (108 characters)
  • gnu/packages/tex.scm (line: 2339, column: 0)
texlive-hyph-utf8 @ 51265formatting

Look for formatting issues in the source

line 2340 is way too long (108 characters)
  • gnu/packages/tex.scm (line: 2340, column: 0)
texlive-hyph-utf8 @ 51265formatting

Look for formatting issues in the source

line 2341 is way too long (95 characters)
  • gnu/packages/tex.scm (line: 2341, column: 0)
texlive-amsfonts @ 51265formatting

Look for formatting issues in the source

line 1302 is way too long (94 characters)
  • gnu/packages/tex.scm (line: 1302, column: 0)
texlive-amsfonts @ 51265formatting

Look for formatting issues in the source

line 1328 is way too long (93 characters)
  • gnu/packages/tex.scm (line: 1328, column: 0)
texlive-amsfonts @ 51265formatting

Look for formatting issues in the source

line 1330 is way too long (91 characters)
  • gnu/packages/tex.scm (line: 1330, column: 0)
python2-pybedtools @ 0.8.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 941, column: 4)
python-pybedtools @ 0.8.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 933, column: 5)
java-xpp3 @ 1.1.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 188
  • gnu/packages/xml.scm (line: 2026, column: 17)
java-mxparser @ 1.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 188, 473
  • gnu/packages/xml.scm (line: 2398, column: 17)
java-kxml2 @ 2.4.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/xml.scm (line: 2229, column: 17)
java-jsch-agentproxy-usocket-nc @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
  • gnu/packages/java.scm (line: 13056, column: 17)
java-jsch-agentproxy-usocket-nc @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/java.scm (line: 13056, column: 17)
java-jsch-agentproxy-usocket-jna @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
  • gnu/packages/java.scm (line: 13024, column: 17)
java-jsch-agentproxy-usocket-jna @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/java.scm (line: 13024, column: 17)
java-jsch-agentproxy-sshagent @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
  • gnu/packages/java.scm (line: 13008, column: 17)
java-jsch-agentproxy-sshagent @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/java.scm (line: 13008, column: 17)
java-jsch-agentproxy-pageant @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
  • gnu/packages/java.scm (line: 13041, column: 17)
java-jsch-agentproxy-pageant @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/java.scm (line: 13041, column: 17)
java-jsch-agentproxy-jsch @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
  • gnu/packages/java.scm (line: 13090, column: 17)
java-jsch-agentproxy-jsch @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/java.scm (line: 13090, column: 17)
java-jsch-agentproxy-core @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/java.scm (line: 12992, column: 17)
java-jsch-agentproxy-connector-factory @ 0.0.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 88
  • gnu/packages/java.scm (line: 13075, column: 17)
java-jsch-agentproxy-connector-factory @ 0.0.8description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/java.scm (line: 13075, column: 17)
opencascade-occt @ 7.3.0p3inputs-should-be-native

Identify inputs that should be native inputs

'doxygen' should probably be a native input
  • gnu/packages/maths.scm (line: 2183, column: 5)
octave-cli @ 6.2.0inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
  • gnu/packages/maths.scm (line: 1968, column: 5)
octave @ 6.2.0inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
  • gnu/packages/maths.scm (line: 2052, column: 5)
java-xmlunit-matchers @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12668, column: 2)
java-xmlunit-legacy @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12654, column: 2)
java-xmlunit @ 2.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12609, column: 12)
java-xerial-core @ 2.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11309, column: 12)
java-stringtemplate @ 4.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 8236, column: 12)
java-stax2-api @ 4.0.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 10251, column: 12)
java-powermock-reflect @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11344, column: 12)
java-powermock-modules-junit4-common @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11418, column: 2)
java-powermock-modules-junit4 @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11435, column: 2)
java-powermock-core @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11379, column: 2)
java-powermock-api-support @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11404, column: 2)
java-powermock-api-easymock @ 1.7.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11466, column: 2)
java-plexus-archiver @ 4.2.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 4389, column: 12)
java-ops4j-pax-tinybundles @ 2.1.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9789, column: 12)
java-ops4j-pax-exam-core-spi @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9870, column: 2)
java-ops4j-pax-exam-core-junit @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9928, column: 2)
java-ops4j-pax-exam-core @ 4.11.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9840, column: 12)
java-ops4j-base-util-property @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9653, column: 2)
java-ops4j-base-util @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9637, column: 2)
java-ops4j-base-store @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9668, column: 2)
java-ops4j-base-spi @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9684, column: 2)
java-ops4j-base-monitors @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9605, column: 2)
java-ops4j-base-lang @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9572, column: 12)
java-ops4j-base-io @ 1.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9618, column: 2)
java-native-access-platform @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12938, column: 2)
java-native-access @ 4.5.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12874, column: 12)
java-mvel2 @ 2.3.1source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11040, column: 12)
java-microemulator-cldc @ 2.0.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9008, column: 12)
java-mail @ 1.6.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11522, column: 12)
java-logback-core @ 1.2.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 13419, column: 12)
java-logback-classic @ 1.2.3source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 13474, column: 2)
java-lmax-disruptor @ 3.3.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11239, column: 12)
java-jsch-agentproxy-usocket-nc @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 13046, column: 2)
java-jsch-agentproxy-usocket-jna @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 13013, column: 2)
java-jsch-agentproxy-sshagent @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12998, column: 2)
java-jsch-agentproxy-pageant @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 13029, column: 2)
java-jsch-agentproxy-jsch @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 13079, column: 2)
java-jsch-agentproxy-core @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12977, column: 12)
java-jsch-agentproxy-connector-factory @ 0.0.8source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 13061, column: 2)
java-joda-time @ 2.9.9source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12273, column: 12)
java-joda-convert @ 1.9.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12242, column: 12)
java-jline @ 2.14.5source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12478, column: 12)
java-jline @ 1.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12447, column: 12)
java-jboss-jms-api-spec @ 2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11496, column: 12)
java-jboss-interceptors-api-spec @ 1.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12153, column: 12)
java-jboss-el-api-spec @ 3.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12102, column: 12)
java-jansi-native @ 1.7source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11988, column: 12)
java-jansi @ 1.16source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12053, column: 12)
java-hawtjni @ 1.15source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11935, column: 12)
java-gson @ 2.8.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 11877, column: 12)
java-fasterxml-jackson-modules-base-mrbean @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 10129, column: 12)
java-fasterxml-jackson-modules-base-jaxb @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 10080, column: 12)
java-fasterxml-jackson-dataformat-yaml @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 10202, column: 12)
java-fasterxml-jackson-databind @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 10035, column: 12)
java-fasterxml-jackson-core @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9972, column: 12)
java-fasterxml-jackson-annotations @ 2.9.4source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9946, column: 12)
java-datanucleus-javax-persistence @ 2.2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9037, column: 12)
java-cdi-api @ 2.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 12205, column: 12)
java-aqute-libg @ 3.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9723, column: 2)
java-aqute-bndlib @ 3.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9763, column: 2)
java-aqute-bnd-annotation @ 3.5.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/java.scm (line: 9702, column: 12)
arpack-ng @ 3.3.0source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/maths.scm (line: 804, column: 5)
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
  • gnu/packages/java.scm (line: 4895, column: 2)
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
  • gnu/packages/java.scm (line: 4862, column: 2)
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
  • gnu/packages/java.scm (line: 4447, column: 2)
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
  • gnu/packages/java.scm (line: 4518, column: 2)
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
  • gnu/packages/java.scm (line: 4748, column: 2)
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
  • gnu/packages/java.scm (line: 4787, column: 2)
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
  • gnu/packages/java.scm (line: 4667, column: 2)
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
  • gnu/packages/java.scm (line: 4386, column: 2)
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
  • gnu/packages/java.scm (line: 5200, column: 2)
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
  • gnu/packages/java.scm (line: 5219, column: 2)
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
  • gnu/packages/java.scm (line: 5168, column: 2)
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
  • gnu/packages/java.scm (line: 5145, column: 2)
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
  • gnu/packages/java.scm (line: 5080, column: 2)
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
  • gnu/packages/java.scm (line: 13257, column: 2)
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
  • gnu/packages/java.scm (line: 8292, column: 2)
scotch32 @ 6.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maths.scm (line: 3231, column: 2)
scotch-shared @ 6.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maths.scm (line: 3278, column: 2)
pt-scotch32 @ 6.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maths.scm (line: 3359, column: 2)
pt-scotch-shared @ 6.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maths.scm (line: 3382, column: 2)
pt-scotch @ 6.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maths.scm (line: 3335, column: 2)
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
  • gnu/packages/maths.scm (line: 1663, column: 2)
mumps-openmpi @ 5.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maths.scm (line: 2926, column: 2)
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
  • gnu/packages/maths.scm (line: 2946, column: 2)
mumps-metis @ 5.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maths.scm (line: 2920, column: 2)
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
  • gnu/packages/java.scm (line: 8858, column: 2)
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
  • gnu/packages/java.scm (line: 8858, column: 2)
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
  • gnu/packages/java.scm (line: 8964, column: 2)
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
  • gnu/packages/java.scm (line: 8964, column: 2)
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
  • gnu/packages/java.scm (line: 8972, column: 2)
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
  • gnu/packages/java.scm (line: 8972, column: 2)
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
  • gnu/packages/java.scm (line: 11341, column: 2)
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
  • gnu/packages/java.scm (line: 11418, column: 2)
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
  • gnu/packages/java.scm (line: 11435, column: 2)
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
  • gnu/packages/java.scm (line: 11379, column: 2)
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
  • gnu/packages/java.scm (line: 11404, column: 2)
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
  • gnu/packages/java.scm (line: 11466, column: 2)
java-openjfx-media @ 8.202patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/java.scm (line: 2838, column: 2)
java-openjfx-graphics @ 8.202patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/java.scm (line: 2730, column: 2)
java-openjfx-controls @ 8.202patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/java.scm (line: 2853, column: 2)
java-openjfx-base @ 8.202patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/java.scm (line: 2698, column: 2)
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
  • gnu/packages/java.scm (line: 13095, column: 2)
java-antlr4-runtime @ 4.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/java.scm (line: 8607, column: 2)
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
  • gnu/packages/maths.scm (line: 1480, column: 2)
hdf4-alt @ 4.2.14patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/maths.scm (line: 1095, column: 2)
grantleetheme @ 20.04.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/kde.scm (line: 121, column: 2)
antlr4 @ 4.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/java.scm (line: 8641, column: 2)
netcdf-parallel-openmpi @ 4.7.4patch-headers

Validate patch headers

netcdf-date-time.patch: patch lacks comment and upstream status
  • gnu/packages/maths.scm (line: 1663, column: 2)
netcdf @ 4.7.4patch-headers

Validate patch headers

netcdf-date-time.patch: patch lacks comment and upstream status
  • gnu/packages/maths.scm (line: 1607, column: 5)
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

line 2416 is way too long (91 characters)
  • gnu/packages/xml.scm (line: 2416, column: 0)
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

line 3099 is way too long (92 characters)
  • gnu/packages/maths.scm (line: 3099, column: 0)
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

tabulation on line 3119, column 0
  • gnu/packages/maths.scm (line: 3119, column: 0)
superlu-dist @ 6.4.0formatting

Look for formatting issues in the source

tabulation on line 3120, column 0
  • gnu/packages/maths.scm (line: 3120, column: 0)
slepc-openmpi @ 3.11.1formatting

Look for formatting issues in the source

tabulation on line 2693, column 0
  • gnu/packages/maths.scm (line: 2693, column: 0)
slepc-complex-openmpi @ 3.11.1formatting

Look for formatting issues in the source

line 2709 is way too long (92 characters)
  • gnu/packages/maths.scm (line: 2709, column: 0)
scalapack @ 2.0.2formatting

Look for formatting issues in the source

tabulation on line 936, column 0
  • gnu/packages/maths.scm (line: 936, column: 0)
pt-scotch32 @ 6.1.0formatting

Look for formatting issues in the source

tabulation on line 3374, column 0
  • gnu/packages/maths.scm (line: 3374, column: 0)
pt-scotch @ 6.1.0formatting

Look for formatting issues in the source

tabulation on line 3352, column 0
  • gnu/packages/maths.scm (line: 3352, column: 0)
petsc @ 3.11.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/maths.scm (line: 2388, column: 0)
p4est @ 2.0formatting

Look for formatting issues in the source

tabulation on line 3463, column 0
  • gnu/packages/maths.scm (line: 3463, column: 0)
mumps-openmpi @ 5.2.1formatting

Look for formatting issues in the source

tabulation on line 2938, column 0
  • gnu/packages/maths.scm (line: 2938, column: 0)
mumps @ 5.2.1formatting

Look for formatting issues in the source

line 2852 is way too long (94 characters)
  • gnu/packages/maths.scm (line: 2852, column: 0)
kuserfeedback @ 1.0.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/kde.scm (line: 1194, column: 0)
java-xom @ 127formatting

Look for formatting issues in the source

trailing white space on line 1969
  • gnu/packages/xml.scm (line: 1969, column: 0)
java-xmlpull-api-v1 @ 1.1.3.4bformatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/xml.scm (line: 2110, column: 0)
java-testng @ 6.14.3formatting

Look for formatting issues in the source

line 10933 is way too long (91 characters)
  • gnu/packages/java.scm (line: 10933, column: 0)
java-sisu-build-api @ 0.0.7formatting

Look for formatting issues in the source

line 5060 is way too long (98 characters)
  • gnu/packages/java.scm (line: 5060, column: 0)
java-plexus-sec-dispatcher @ 1.4formatting

Look for formatting issues in the source

line 4937 is way too long (107 characters)
  • gnu/packages/java.scm (line: 4937, column: 0)
java-plexus-compiler-javac @ 2.8.4formatting

Look for formatting issues in the source

line 4818 is way too long (95 characters)
  • gnu/packages/java.scm (line: 4818, column: 0)
java-ops4j-pax-exam-core-spi @ 4.11.0formatting

Look for formatting issues in the source

line 9894 is way too long (92 characters)
  • gnu/packages/java.scm (line: 9894, column: 0)
java-ops4j-pax-exam-core-spi @ 4.11.0formatting

Look for formatting issues in the source

line 9898 is way too long (98 characters)
  • gnu/packages/java.scm (line: 9898, column: 0)
java-ops4j-pax-exam-core-spi @ 4.11.0formatting

Look for formatting issues in the source

line 9902 is way too long (99 characters)
  • gnu/packages/java.scm (line: 9902, column: 0)
java-ops4j-pax-exam-core-spi @ 4.11.0formatting

Look for formatting issues in the source

line 9903 is way too long (91 characters)
  • gnu/packages/java.scm (line: 9903, column: 0)
java-ops4j-pax-exam-core-spi @ 4.11.0formatting

Look for formatting issues in the source

line 9906 is way too long (100 characters)
  • gnu/packages/java.scm (line: 9906, column: 0)
java-ops4j-base-lang @ 1.5.0formatting

Look for formatting issues in the source

line 9590 is way too long (110 characters)
  • gnu/packages/java.scm (line: 9590, column: 0)
java-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

line 2762 is way too long (99 characters)
  • gnu/packages/java.scm (line: 2762, column: 0)
java-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

line 2773 is way too long (98 characters)
  • gnu/packages/java.scm (line: 2773, column: 0)
java-openjfx-graphics @ 8.202formatting

Look for formatting issues in the source

line 2812 is way too long (96 characters)
  • gnu/packages/java.scm (line: 2812, column: 0)
java-openjfx-base @ 8.202formatting

Look for formatting issues in the source

line 2702 is way too long (111 characters)
  • gnu/packages/java.scm (line: 2702, column: 0)
java-openjfx-base @ 8.202formatting

Look for formatting issues in the source

line 2717 is way too long (99 characters)
  • gnu/packages/java.scm (line: 2717, column: 0)
java-openchart2 @ 1.4.3formatting

Look for formatting issues in the source

line 12722 is way too long (92 characters)
  • gnu/packages/java.scm (line: 12722, column: 0)
java-native-access @ 4.5.1formatting

Look for formatting issues in the source

line 12902 is way too long (91 characters)
  • gnu/packages/java.scm (line: 12902, column: 0)
java-logback-classic @ 1.2.3formatting

Look for formatting issues in the source

line 13481 is way too long (102 characters)
  • gnu/packages/java.scm (line: 13481, column: 0)
java-joda-time @ 2.9.9formatting

Look for formatting issues in the source

line 12295 is way too long (92 characters)
  • gnu/packages/java.scm (line: 12295, column: 0)
java-jnacl @ 0.1.0-2.094e819formatting

Look for formatting issues in the source

line 11010 is way too long (93 characters)
  • gnu/packages/java.scm (line: 11010, column: 0)
java-jnacl @ 0.1.0-2.094e819formatting

Look for formatting issues in the source

line 11020 is way too long (92 characters)
  • gnu/packages/java.scm (line: 11020, column: 0)
java-jgit @ 4.2.0.201601211800-rformatting

Look for formatting issues in the source

line 13584 is way too long (93 characters)
  • gnu/packages/java.scm (line: 13584, column: 0)
java-hawtjni @ 1.15formatting

Look for formatting issues in the source

line 11951 is way too long (92 characters)
  • gnu/packages/java.scm (line: 11951, column: 0)
java-hamcrest-core @ 1.3formatting

Look for formatting issues in the source

line 3949 is way too long (112 characters)
  • gnu/packages/java.scm (line: 3949, column: 0)
java-geronimo-xbean-reflect @ 4.5formatting

Look for formatting issues in the source

line 11702 is way too long (92 characters)
  • gnu/packages/java.scm (line: 11702, column: 0)
java-geronimo-xbean-bundleutils @ 4.5formatting

Look for formatting issues in the source

line 11817 is way too long (122 characters)
  • gnu/packages/java.scm (line: 11817, column: 0)
java-fasterxml-jackson-dataformat-yaml @ 2.9.4formatting

Look for formatting issues in the source

line 10220 is way too long (104 characters)
  • gnu/packages/java.scm (line: 10220, column: 0)
java-fasterxml-jackson-dataformat-xml @ 2.9.4formatting

Look for formatting issues in the source

line 10335 is way too long (98 characters)
  • gnu/packages/java.scm (line: 10335, column: 0)
java-fasterxml-jackson-databind @ 2.9.4formatting

Look for formatting issues in the source

line 10052 is way too long (96 characters)
  • gnu/packages/java.scm (line: 10052, column: 0)
java-fasterxml-jackson-core @ 2.9.4formatting

Look for formatting issues in the source

line 10001 is way too long (93 characters)
  • gnu/packages/java.scm (line: 10001, column: 0)
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

tabulation on line 7481, column 20
  • gnu/packages/java.scm (line: 7481, column: 20)
java-eclipse-text @ 3.6.0formatting

Look for formatting issues in the source

tabulation on line 7482, column 20
  • gnu/packages/java.scm (line: 7482, column: 20)
java-eclipse-sisu-plexus @ 0.3.4formatting

Look for formatting issues in the source

line 13298 is way too long (104 characters)
  • gnu/packages/java.scm (line: 13298, column: 0)
java-eclipse-sisu-plexus @ 0.3.4formatting

Look for formatting issues in the source

line 13305 is way too long (95 characters)
  • gnu/packages/java.scm (line: 13305, column: 0)
java-eclipse-jdt-core @ 3.16.0formatting

Look for formatting issues in the source

line 7541 is way too long (98 characters)
  • gnu/packages/java.scm (line: 7541, column: 0)
java-commons-jxpath @ 1.3formatting

Look for formatting issues in the source

line 6256 is way too long (93 characters)
  • gnu/packages/java.scm (line: 6256, column: 0)
java-commons-httpclient @ 3.1formatting

Look for formatting issues in the source

line 12764 is way too long (91 characters)
  • gnu/packages/java.scm (line: 12764, column: 0)
java-commons-exec @ 1.1formatting

Look for formatting issues in the source

line 6024 is way too long (91 characters)
  • gnu/packages/java.scm (line: 6024, column: 0)
java-aqute-bndlib @ 3.5.0formatting

Look for formatting issues in the source

line 9775 is way too long (91 characters)
  • gnu/packages/java.scm (line: 9775, column: 0)
java-apache-ivy @ 2.4.0formatting

Look for formatting issues in the source

line 13122 is way too long (101 characters)
  • gnu/packages/java.scm (line: 13122, column: 0)
icedtea @ 3.7.0formatting

Look for formatting issues in the source

line 1790 is way too long (109 characters)
  • gnu/packages/java.scm (line: 1790, column: 0)
icedtea @ 2.6.13formatting

Look for formatting issues in the source

line 1277 is way too long (102 characters)
  • gnu/packages/java.scm (line: 1277, column: 0)
icedtea @ 2.6.13formatting

Look for formatting issues in the source

line 1458 is way too long (100 characters)
  • gnu/packages/java.scm (line: 1458, column: 0)
hdf-java @ 3.3.2formatting

Look for formatting issues in the source

line 1344 is way too long (92 characters)
  • gnu/packages/maths.scm (line: 1344, column: 0)
clapack @ 3.2.1formatting

Look for formatting issues in the source

line 898 is way too long (91 characters)
  • gnu/packages/maths.scm (line: 898, column: 0)
antlr4 @ 4.8formatting

Look for formatting issues in the source

line 8647 is way too long (96 characters)
  • gnu/packages/java.scm (line: 8647, column: 0)
antlr4 @ 4.8formatting

Look for formatting issues in the source

line 8721 is way too long (100 characters)
  • gnu/packages/java.scm (line: 8721, column: 0)
ublock-origin-chromium @ 1.35.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/build/chromium-extension.scm (line: 173, column: 4)
python-pytest-django @ 3.10.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/django.scm (line: 319, column: 2)
sbcl-next @ 2-pre-release-7inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • guix/packages.scm (line: 464, column: 2)
nyxt @ 2-pre-release-7inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/web-browsers.scm (line: 666, column: 5)
next @ 2-pre-release-7inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • guix/packages.scm (line: 464, column: 2)
psi-plus @ 1.5.1484formatting

Look for formatting issues in the source

line 2800 is way too long (96 characters)
  • gnu/packages/messaging.scm (line: 2800, column: 0)
php @ 7.4.19formatting

Look for formatting issues in the source

line 192 is way too long (93 characters)
  • gnu/packages/php.scm (line: 192, column: 0)
php @ 7.4.19formatting

Look for formatting issues in the source

line 193 is way too long (93 characters)
  • gnu/packages/php.scm (line: 193, column: 0)
php @ 7.4.19formatting

Look for formatting issues in the source

line 204 is way too long (91 characters)
  • gnu/packages/php.scm (line: 204, column: 0)
php @ 7.4.19formatting

Look for formatting issues in the source

line 212 is way too long (93 characters)
  • gnu/packages/php.scm (line: 212, column: 0)
php @ 7.4.19formatting

Look for formatting issues in the source

line 234 is way too long (92 characters)
  • gnu/packages/php.scm (line: 234, column: 0)
php @ 7.4.19formatting

Look for formatting issues in the source

line 235 is way too long (96 characters)
  • gnu/packages/php.scm (line: 235, column: 0)
php @ 7.4.19formatting

Look for formatting issues in the source

line 240 is way too long (96 characters)
  • gnu/packages/php.scm (line: 240, column: 0)
php @ 7.4.19formatting

Look for formatting issues in the source

line 282 is way too long (91 characters)
  • gnu/packages/php.scm (line: 282, column: 0)
php @ 7.4.19formatting

Look for formatting issues in the source

line 295 is way too long (92 characters)
  • gnu/packages/php.scm (line: 295, column: 0)
lpsolve @ 5.5.2.5description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/maths.scm (line: 4374, column: 5)
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
  • gnu/packages/maths.scm (line: 5843, column: 12)
sundials-openmpi @ 3.1.1formatting

Look for formatting issues in the source

tabulation on line 5292, column 0
  • gnu/packages/maths.scm (line: 5292, column: 0)
hypre-openmpi @ 2.15.1formatting

Look for formatting issues in the source

tabulation on line 4721, column 0
  • gnu/packages/maths.scm (line: 4721, column: 0)
trf @ 4.09.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 387
  • gnu/packages/bioinformatics.scm (line: 2900, column: 17)
repeat-masker @ 4.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 387
  • gnu/packages/bioinformatics.scm (line: 2956, column: 17)
r-demultiplex @ 1.0.2-1.6e2a142description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 7474, column: 7)
python2-twobitreader @ 3.1.6description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 2080, column: 5)
python2-plastid @ 0.4.8description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 2116, column: 5)
python2-bx-python @ 0.8.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 1966, column: 5)
python-twobitreader @ 3.1.6description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 2080, column: 5)
python-plastid @ 0.4.8description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 2116, column: 5)
python-dnaio @ 0.3description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 2468, column: 5)
python-bx-python @ 0.8.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 1966, column: 5)
rseqc @ 3.0.1inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
  • gnu/packages/bioinformatics.scm (line: 5853, column: 5)
python2-pbcore @ 1.2.10inputs-should-be-native

Identify inputs that should be native inputs

'python2-cython' should probably be a native input
  • gnu/packages/bioinformatics.scm (line: 5259, column: 2)
newick-utils @ 1.6-1.da121155inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
  • gnu/packages/bioinformatics.scm (line: 5218, column: 5)
newick-utils @ 1.6-1.da121155inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
  • gnu/packages/bioinformatics.scm (line: 5218, column: 5)
clipper @ 2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
  • gnu/packages/bioinformatics.scm (line: 2266, column: 5)
ncbi-vdb @ 2.10.6formatting

Look for formatting issues in the source

tabulation on line 6228, column 26
  • gnu/packages/bioinformatics.scm (line: 6228, column: 26)
java-picard @ 2.3.0formatting

Look for formatting issues in the source

line 4165 is way too long (104 characters)
  • gnu/packages/bioinformatics.scm (line: 4165, column: 0)
java-picard @ 2.10.3formatting

Look for formatting issues in the source

line 4224 is way too long (104 characters)
  • gnu/packages/bioinformatics.scm (line: 4224, column: 0)
java-picard @ 2.10.3formatting

Look for formatting issues in the source

line 4254 is way too long (91 characters)
  • gnu/packages/bioinformatics.scm (line: 4254, column: 0)
java-picard @ 1.113formatting

Look for formatting issues in the source

line 4311 is way too long (96 characters)
  • gnu/packages/bioinformatics.scm (line: 4311, column: 0)
java-picard @ 1.113formatting

Look for formatting issues in the source

line 4312 is way too long (117 characters)
  • gnu/packages/bioinformatics.scm (line: 4312, column: 0)
discrover @ 1.6.0formatting

Look for formatting issues in the source

line 3062 is way too long (91 characters)
  • gnu/packages/bioinformatics.scm (line: 3062, column: 0)
python-hyperkitty @ 1.3.3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-django@2.2.22 and python-django@3.2.2 collide
  • gnu/packages/mail.scm (line: 3479, column: 2)
tcsh @ 6.22.02patch-headers

Validate patch headers

tcsh-fix-autotest.patch: patch lacks comment and upstream status
  • gnu/packages/shells.scm (line: 395, column: 12)
giac @ 1.7.0-5formatting

Look for formatting issues in the source

line 351 is way too long (95 characters)
  • gnu/packages/algebra.scm (line: 351, column: 0)
rtl-sdr @ 0.6.0description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/radio.scm (line: 161, column: 17)
xfce4-clipman-plugin @ 1.6.2formatting

Look for formatting issues in the source

line 502 is way too long (91 characters)
  • gnu/packages/xfce.scm (line: 502, column: 0)
python-mypy @ 0.790description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/python-check.scm (line: 1307, column: 17)
python-robber @ 1.1.5inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
  • gnu/packages/python-check.scm (line: 1359, column: 2)
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
  • gnu/packages/python-check.scm (line: 565, column: 4)
python-pytest-sanic @ 1.7.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/python-check.scm (line: 1418, column: 2)
python-pytest-isort @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/python-check.scm (line: 710, column: 2)
python-pytest-click @ 1.0.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/python-check.scm (line: 52, column: 2)
python-pytest-checkdocs @ 1.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/python-check.scm (line: 596, column: 2)
python-coveralls @ 1.11.1inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
  • gnu/packages/python-check.scm (line: 98, column: 2)
python-pytest-helpers-namespace @ 2021.3.24inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-check.scm (line: 402, column: 2)
xfce4-volumed-pulse @ 0.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
  • gnu/packages/xfce.scm (line: 1390, column: 5)
ocaml-zarith @ 1.9.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
  • gnu/packages/ocaml.scm (line: 1473, column: 17)
ocaml-topkg @ 1.0.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 51
  • gnu/packages/ocaml.scm (line: 1925, column: 17)
ocaml-qcheck @ 0.12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 52, 156
  • gnu/packages/ocaml.scm (line: 1555, column: 17)
ocaml-down @ 0.0.3description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/ocaml.scm (line: 702, column: 17)
ocaml-cmdliner @ 1.0.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 304
  • gnu/packages/ocaml.scm (line: 2087, column: 17)
gtkspell3 @ 3.0.10inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gtk.scm (line: 1905, column: 5)
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
  • gnu/packages/gtk.scm (line: 1101, column: 2)
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
  • gnu/packages/gtk.scm (line: 1175, column: 2)
gtk+ @ 3.24.24patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gtk.scm (line: 848, column: 2)
gtk+ @ 2.24.32patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gtk.scm (line: 779, column: 2)
gdk-pixbuf+svg @ 2.40.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gtk.scm (line: 625, column: 2)
cairo-xcb @ 1.16.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/gtk.scm (line: 189, column: 2)
ocaml-dose3 @ 5.0.1patch-headers

Validate patch headers

ocaml-dose3-dont-make-printconf.patch: patch lacks comment and upstream status
  • gnu/packages/ocaml.scm (line: 627, column: 12)
volctl @ 0.8.2formatting

Look for formatting issues in the source

line 2397 is way too long (98 characters)
  • gnu/packages/gtk.scm (line: 2397, column: 0)
ocaml4.07-sedlex @ 2.1formatting

Look for formatting issues in the source

line 2599 is way too long (97 characters)
  • gnu/packages/ocaml.scm (line: 2599, column: 0)
ocaml-dose3 @ 5.0.1formatting

Look for formatting issues in the source

line 629 is way too long (92 characters)
  • gnu/packages/ocaml.scm (line: 629, column: 0)
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

tabulation on line 830, column 0
  • gnu/packages/gtk.scm (line: 830, column: 0)
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

tabulation on line 831, column 0
  • gnu/packages/gtk.scm (line: 831, column: 0)
gtk+ @ 2.24.32formatting

Look for formatting issues in the source

tabulation on line 832, column 0
  • gnu/packages/gtk.scm (line: 832, column: 0)
font-canada1500 @ 1.101formatting

Look for formatting issues in the source

line 209 is way too long (91 characters)
  • gnu/packages/fonts.scm (line: 209, column: 0)
at-spi2-core @ 2.34.0formatting

Look for formatting issues in the source

line 676 is way too long (97 characters)
  • gnu/packages/gtk.scm (line: 676, column: 0)
mdadm-static @ 4.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/linux.scm (line: 4710, column: 2)
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
  • gnu/packages/linux.scm (line: 1754, column: 2)
linux-libre-headers @ 4.9.268patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 553, column: 2)
linux-libre-headers @ 4.4.268patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 553, column: 2)
linux-libre-headers @ 4.19.190patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 553, column: 2)
linux-libre-headers @ 4.14.232patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 553, column: 2)
linux-libre-arm-omap2plus @ 4.19.190patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-arm-omap2plus @ 4.14.232patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-arm-generic @ 4.19.190patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-arm-generic @ 4.14.232patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre @ 4.9.268patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre @ 4.4.268patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre @ 4.19.190patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre @ 4.14.232patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
wireless-tools @ 30.pre9formatting

Look for formatting issues in the source

line 3832 is way too long (104 characters)
  • gnu/packages/linux.scm (line: 3832, column: 0)
util-linux @ 2.35.1formatting

Look for formatting issues in the source

line 1634 is way too long (91 characters)
  • gnu/packages/linux.scm (line: 1634, column: 0)
linux-pam @ 1.5.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/linux.scm (line: 1443, column: 0)
linux-libre-arm-omap2plus @ 4.19.190formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre-arm-omap2plus @ 4.14.232formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre-arm-generic @ 4.19.190formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre-arm-generic @ 4.14.232formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre @ 4.9.268formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre @ 4.4.268formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre @ 4.19.190formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre @ 4.14.232formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
crda @ 3.18formatting

Look for formatting issues in the source

line 3939 is way too long (100 characters)
  • gnu/packages/linux.scm (line: 3939, column: 0)
thunar @ 4.16.8inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/xfce.scm (line: 797, column: 5)
sky @ 1.2description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/games.scm (line: 9892, column: 5)
passage @ 4description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/games.scm (line: 12407, column: 5)
mrrescue @ 1.02edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 2
  • gnu/packages/games.scm (line: 5779, column: 5)
chroma @ 1.18description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 33
  • gnu/packages/games.scm (line: 6442, column: 17)
fifengine @ 0.4.2inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
  • gnu/packages/games.scm (line: 3859, column: 5)
crawl-tiles @ 0.26.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/games.scm (line: 6596, column: 2)
tuxpaint @ 0.9.23patch-headers

Validate patch headers

tuxpaint-stamps-path.patch: patch lacks comment and upstream status
  • gnu/packages/games.scm (line: 5381, column: 5)
pinball @ 0.3.1patch-headers

Validate patch headers

pinball-const-fix.patch: patch lacks comment and upstream status
  • gnu/packages/games.scm (line: 4692, column: 5)
pinball @ 0.3.1patch-headers

Validate patch headers

pinball-system-ltdl.patch: patch lacks comment and upstream status
  • gnu/packages/games.scm (line: 4692, column: 5)
gzdoom @ 4.3.2patch-headers

Validate patch headers

gzdoom-find-system-libgme.patch: patch lacks comment and upstream status
  • gnu/packages/games.scm (line: 7421, column: 5)
sky @ 1.2formatting

Look for formatting issues in the source

line 9878 is way too long (118 characters)
  • gnu/packages/games.scm (line: 9878, column: 0)
ri-li @ 2.0.1formatting

Look for formatting issues in the source

line 9974 is way too long (100 characters)
  • gnu/packages/games.scm (line: 9974, column: 0)
queen-it @ 1.0formatting

Look for formatting issues in the source

line 9774 is way too long (184 characters)
  • gnu/packages/games.scm (line: 9774, column: 0)
queen-it @ 1.0formatting

Look for formatting issues in the source

line 9775 is way too long (205 characters)
  • gnu/packages/games.scm (line: 9775, column: 0)
queen-fr @ 1.0formatting

Look for formatting issues in the source

line 9774 is way too long (184 characters)
  • gnu/packages/games.scm (line: 9774, column: 0)
queen-fr @ 1.0formatting

Look for formatting issues in the source

line 9775 is way too long (205 characters)
  • gnu/packages/games.scm (line: 9775, column: 0)
queen-de @ 1.0formatting

Look for formatting issues in the source

line 9774 is way too long (184 characters)
  • gnu/packages/games.scm (line: 9774, column: 0)
queen-de @ 1.0formatting

Look for formatting issues in the source

line 9775 is way too long (205 characters)
  • gnu/packages/games.scm (line: 9775, column: 0)
queen @ 1.1formatting

Look for formatting issues in the source

line 9774 is way too long (184 characters)
  • gnu/packages/games.scm (line: 9774, column: 0)
queen @ 1.1formatting

Look for formatting issues in the source

line 9775 is way too long (205 characters)
  • gnu/packages/games.scm (line: 9775, column: 0)
lure-it @ 1.1formatting

Look for formatting issues in the source

line 9675 is way too long (93 characters)
  • gnu/packages/games.scm (line: 9675, column: 0)
lure-fr @ 1.1formatting

Look for formatting issues in the source

line 9675 is way too long (93 characters)
  • gnu/packages/games.scm (line: 9675, column: 0)
lure-es @ 1.1formatting

Look for formatting issues in the source

line 9675 is way too long (93 characters)
  • gnu/packages/games.scm (line: 9675, column: 0)
lure-de @ 1.1formatting

Look for formatting issues in the source

line 9675 is way too long (93 characters)
  • gnu/packages/games.scm (line: 9675, column: 0)
lure @ 1.1formatting

Look for formatting issues in the source

line 9675 is way too long (93 characters)
  • gnu/packages/games.scm (line: 9675, column: 0)
freeorion @ 0.4.10formatting

Look for formatting issues in the source

line 10059 is way too long (92 characters)
  • gnu/packages/games.scm (line: 10059, column: 0)
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3213, column 0
  • gnu/packages/games.scm (line: 3213, column: 0)
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3214, column 0
  • gnu/packages/games.scm (line: 3214, column: 0)
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3215, column 0
  • gnu/packages/games.scm (line: 3215, column: 0)
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3216, column 0
  • gnu/packages/games.scm (line: 3216, column: 0)
freedink-engine @ 109.6formatting

Look for formatting issues in the source

tabulation on line 3217, column 0
  • gnu/packages/games.scm (line: 3217, column: 0)
einstein @ 2.0formatting

Look for formatting issues in the source

line 4804 is way too long (96 characters)
  • gnu/packages/games.scm (line: 4804, column: 0)
drascula @ 1.0formatting

Look for formatting issues in the source

line 9572 is way too long (93 characters)
  • gnu/packages/games.scm (line: 9572, column: 0)
drascula @ 1.0formatting

Look for formatting issues in the source

line 9576 is way too long (93 characters)
  • gnu/packages/games.scm (line: 9576, column: 0)
btanks @ 0.9.8083formatting

Look for formatting issues in the source

line 8586 is way too long (99 characters)
  • gnu/packages/games.scm (line: 8586, column: 0)
btanks @ 0.9.8083formatting

Look for formatting issues in the source

tabulation on line 8611, column 18
  • gnu/packages/games.scm (line: 8611, column: 18)
btanks @ 0.9.8083formatting

Look for formatting issues in the source

tabulation on line 8612, column 17
  • gnu/packages/games.scm (line: 8612, column: 17)
icedove @ 78.10.1formatting

Look for formatting issues in the source

line 1334 is way too long (98 characters)
  • gnu/packages/gnuzilla.scm (line: 1334, column: 0)
icedove @ 78.10.1formatting

Look for formatting issues in the source

line 1489 is way too long (105 characters)
  • gnu/packages/gnuzilla.scm (line: 1489, column: 0)
icedove @ 78.10.1formatting

Look for formatting issues in the source

line 1491 is way too long (102 characters)
  • gnu/packages/gnuzilla.scm (line: 1491, column: 0)
icecat @ 78.10.0-guix0-preview1formatting

Look for formatting issues in the source

line 997 is way too long (102 characters)
  • gnu/packages/gnuzilla.scm (line: 997, column: 0)
icecat @ 78.10.0-guix0-preview1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/gnuzilla.scm (line: 1022, column: 0)
icecat @ 78.10.0-guix0-preview1formatting

Look for formatting issues in the source

line 1089 is way too long (139 characters)
  • gnu/packages/gnuzilla.scm (line: 1089, column: 0)
icecat @ 78.10.0-guix0-preview1formatting

Look for formatting issues in the source

line 1095 is way too long (95 characters)
  • gnu/packages/gnuzilla.scm (line: 1095, column: 0)
icecat @ 78.10.0-guix0-preview1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/gnuzilla.scm (line: 1101, column: 0)
icecat @ 78.10.0-guix0-preview1formatting

Look for formatting issues in the source

line 1139 is way too long (94 characters)
  • gnu/packages/gnuzilla.scm (line: 1139, column: 0)
icecat @ 78.10.0-guix0-preview1formatting

Look for formatting issues in the source

line 1141 is way too long (95 characters)
  • gnu/packages/gnuzilla.scm (line: 1141, column: 0)
icecat @ 78.10.0-guix0-preview1formatting

Look for formatting issues in the source

line 1154 is way too long (98 characters)
  • gnu/packages/gnuzilla.scm (line: 1154, column: 0)
icecat @ 78.10.0-guix0-preview1formatting

Look for formatting issues in the source

line 1286 is way too long (92 characters)
  • gnu/packages/gnuzilla.scm (line: 1286, column: 0)
yelp-xsl @ 3.34.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 300
  • gnu/packages/gnome.scm (line: 6870, column: 17)
yelp-tools @ 3.32.2inputs-should-be-native

Identify inputs that should be native inputs

'itstool' should probably be a native input
  • gnu/packages/gnome.scm (line: 6937, column: 5)
system-config-printer @ 1.5.15inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 2967, column: 5)
lollypop @ 1.4.6inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 10357, column: 5)
libpeas @ 1.28.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 3100, column: 5)
libmediaart @ 1.9.4inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 1424, column: 5)
libgee @ 0.20.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 6980, column: 5)
libdazzle @ 3.37.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 10754, column: 5)
libchamplain @ 0.12.16inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
  • gnu/packages/gnome.scm (line: 5925, column: 2)
gnome-tweaks @ 3.34.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 9687, column: 5)
gnome-contacts @ 3.34inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 2113, column: 5)
gnome @ 3.34.5inputs-should-be-native

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
  • gnu/packages/gnome.scm (line: 9180, column: 2)
gjs @ 1.58.3inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 7233, column: 5)
gexiv2 @ 0.12.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 7011, column: 5)
geoclue @ 2.5.7inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
  • gnu/packages/gnome.scm (line: 5325, column: 5)
eolie @ 0.9.101inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 6692, column: 5)
d-feet @ 0.3.14inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 6839, column: 5)
cheese @ 3.38.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/gnome.scm (line: 10473, column: 5)
zeitgeist @ 1.0.3formatting

Look for formatting issues in the source

tabulation on line 752, column 18
  • gnu/packages/gnome.scm (line: 752, column: 18)
zeitgeist @ 1.0.3formatting

Look for formatting issues in the source

tabulation on line 755, column 18
  • gnu/packages/gnome.scm (line: 755, column: 18)
upower @ 0.99.11formatting

Look for formatting issues in the source

line 5400 is way too long (110 characters)
  • gnu/packages/gnome.scm (line: 5400, column: 0)
libsoup @ 2.72.0formatting

Look for formatting issues in the source

line 4856 is way too long (128 characters)
  • gnu/packages/gnome.scm (line: 4856, column: 0)
libsoup @ 2.72.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/gnome.scm (line: 4893, column: 0)
librsvg @ 2.50.3formatting

Look for formatting issues in the source

line 3480 is way too long (104 characters)
  • gnu/packages/gnome.scm (line: 3480, column: 0)
gnome-keyring @ 3.34.0formatting

Look for formatting issues in the source

line 2518 is way too long (91 characters)
  • gnu/packages/gnome.scm (line: 2518, column: 0)
gnome-initial-setup @ 3.32.1formatting

Look for formatting issues in the source

line 1459 is way too long (91 characters)
  • gnu/packages/gnome.scm (line: 1459, column: 0)
glade @ 3.36.0formatting

Look for formatting issues in the source

line 3180 is way too long (91 characters)
  • gnu/packages/gnome.scm (line: 3180, column: 0)
gdm @ 3.34.1formatting

Look for formatting issues in the source

line 8240 is way too long (103 characters)
  • gnu/packages/gnome.scm (line: 8240, column: 0)
racket-minimal @ 8.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/racket.scm (line: 67, column: 2)
tor @ 0.4.5.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 574
  • gnu/packages/tor.scm (line: 90, column: 5)
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
  • gnu/packages/lisp-xyz.scm (line: 495, column: 19)
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
  • gnu/packages/lisp-xyz.scm (line: 495, column: 19)
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
  • gnu/packages/lisp-xyz.scm (line: 495, column: 19)
cl-clml @ 0.0.0-0.95505b5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/lisp-xyz.scm (line: 13536, column: 4)
sbcl-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

line 291 is way too long (96 characters)
  • gnu/packages/lisp-xyz.scm (line: 291, column: 0)
sbcl-cl-strings @ 0.0.0-1.c5c5cbaformatting

Look for formatting issues in the source

line 1350 is way too long (98 characters)
  • gnu/packages/lisp-xyz.scm (line: 1350, column: 0)
sbcl-caveman @ 2.4.0-1.faa5f7eformatting

Look for formatting issues in the source

line 12848 is way too long (140 characters)
  • gnu/packages/lisp-xyz.scm (line: 12848, column: 0)
sbcl-caveman @ 2.4.0-1.faa5f7eformatting

Look for formatting issues in the source

line 12850 is way too long (97 characters)
  • gnu/packages/lisp-xyz.scm (line: 12850, column: 0)
sbcl-caveman @ 2.4.0-1.faa5f7eformatting

Look for formatting issues in the source

line 12851 is way too long (110 characters)
  • gnu/packages/lisp-xyz.scm (line: 12851, column: 0)
ecl-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

line 291 is way too long (96 characters)
  • gnu/packages/lisp-xyz.scm (line: 291, column: 0)
ecl-cl-strings @ 0.0.0-1.c5c5cbaformatting

Look for formatting issues in the source

line 1350 is way too long (98 characters)
  • gnu/packages/lisp-xyz.scm (line: 1350, column: 0)
ecl-caveman @ 2.4.0-1.faa5f7eformatting

Look for formatting issues in the source

line 12848 is way too long (140 characters)
  • gnu/packages/lisp-xyz.scm (line: 12848, column: 0)
ecl-caveman @ 2.4.0-1.faa5f7eformatting

Look for formatting issues in the source

line 12850 is way too long (97 characters)
  • gnu/packages/lisp-xyz.scm (line: 12850, column: 0)
ecl-caveman @ 2.4.0-1.faa5f7eformatting

Look for formatting issues in the source

line 12851 is way too long (110 characters)
  • gnu/packages/lisp-xyz.scm (line: 12851, column: 0)
cl-strings @ 0.0.0-1.c5c5cbaformatting

Look for formatting issues in the source

line 1350 is way too long (98 characters)
  • gnu/packages/lisp-xyz.scm (line: 1350, column: 0)
cl-net.didierverna.asdf-flv @ 2.1formatting

Look for formatting issues in the source

line 291 is way too long (96 characters)
  • gnu/packages/lisp-xyz.scm (line: 291, column: 0)
python2-html2text @ 2019.8.11description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-web.scm (line: 710, column: 4)
python-html2text @ 2020.1.16description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-web.scm (line: 703, column: 17)
boost-static @ 1.72.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/boost.scm (line: 216, column: 2)
boost-python2 @ 1.72.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/boost.scm (line: 206, column: 2)
boost-mpi @ 1.72.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/boost.scm (line: 355, column: 2)
ruby-rb-inotify @ 0.9.10description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/ruby.scm (line: 5950, column: 17)
ruby-tzinfo-data @ 1.2021.1formatting

Look for formatting issues in the source

line 5878 is way too long (101 characters)
  • gnu/packages/ruby.scm (line: 5878, column: 0)
ruby-tzinfo-data @ 1.2021.1formatting

Look for formatting issues in the source

line 5879 is way too long (107 characters)
  • gnu/packages/ruby.scm (line: 5879, column: 0)
emacs-vcsh @ 0.4.4description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/emacs-xyz.scm (line: 18093, column: 5)
emacs-trashed @ 2.1.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 178
  • gnu/packages/emacs-xyz.scm (line: 27069, column: 17)
emacs-templatel @ 0.1.4description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/emacs-xyz.scm (line: 10006, column: 5)
emacs-swiper @ 0.13.4description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/emacs-xyz.scm (line: 8158, column: 5)
emacs-pyvenv @ 1.21description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/emacs-xyz.scm (line: 9555, column: 17)
emacs-org-drill-table @ 0.1-0.096387ddescription

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/emacs-xyz.scm (line: 23621, column: 7)
emacs-nhexl-mode @ 1.5description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/emacs-xyz.scm (line: 24032, column: 5)
emacs-ivy-hydra @ 0.13.5description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/emacs-xyz.scm (line: 27891, column: 5)
emacs-gdscript-mode @ 1.4.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
  • gnu/packages/emacs-xyz.scm (line: 3885, column: 5)
emacs-flx @ 0.6.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 220
  • gnu/packages/emacs-xyz.scm (line: 11417, column: 5)
emacs-envrc @ 0.2description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/emacs-xyz.scm (line: 14108, column: 5)
emacs-el-x @ 0.3.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/emacs-xyz.scm (line: 9468, column: 17)
emacs-dhall-mode @ 0.1.3-1.484bcf8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 89
  • gnu/packages/emacs-xyz.scm (line: 2245, column: 7)
emacs-cnfonts @ 0.9.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/emacs-xyz.scm (line: 12644, column: 17)
emacs-telega-contrib @ 0.7.1-1.1d28dc2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/emacs-xyz.scm (line: 25457, column: 2)
emacs-geiser @ 0.13patch-file-names

Validate file names and availability of patches

emacs-geiser-autoload-activate-implementation.patch: file name is too long
  • gnu/packages/emacs-xyz.scm (line: 221, column: 2)
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
  • gnu/packages/emacs-xyz.scm (line: 13021, column: 2)
emacs-sqlite @ 1.0-0.dad42b8formatting

Look for formatting issues in the source

tabulation on line 4883, column 0
  • gnu/packages/emacs-xyz.scm (line: 4883, column: 0)
emacs-sqlite @ 1.0-0.dad42b8formatting

Look for formatting issues in the source

tabulation on line 4884, column 0
  • gnu/packages/emacs-xyz.scm (line: 4884, column: 0)
emacs-powershell @ 0.3-0.d1b3f95formatting

Look for formatting issues in the source

tabulation on line 14740, column 0
  • gnu/packages/emacs-xyz.scm (line: 14740, column: 0)
emacs-powershell @ 0.3-0.d1b3f95formatting

Look for formatting issues in the source

tabulation on line 14741, column 0
  • gnu/packages/emacs-xyz.scm (line: 14741, column: 0)
emacs-org @ 9.4.5formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/emacs-xyz.scm (line: 11271, column: 0)
emacs-mit-scheme-doc @ 20140203formatting

Look for formatting issues in the source

line 6358 is way too long (94 characters)
  • gnu/packages/emacs-xyz.scm (line: 6358, column: 0)
emacs-gtk-look @ 29formatting

Look for formatting issues in the source

line 21118 is way too long (94 characters)
  • gnu/packages/emacs-xyz.scm (line: 21118, column: 0)
emacs-exwm @ 0.24formatting

Look for formatting issues in the source

line 13003 is way too long (96 characters)
  • gnu/packages/emacs-xyz.scm (line: 13003, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13373, column 0
  • gnu/packages/emacs-xyz.scm (line: 13373, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13374, column 0
  • gnu/packages/emacs-xyz.scm (line: 13374, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13377, column 0
  • gnu/packages/emacs-xyz.scm (line: 13377, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13378, column 0
  • gnu/packages/emacs-xyz.scm (line: 13378, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13390, column 0
  • gnu/packages/emacs-xyz.scm (line: 13390, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13391, column 0
  • gnu/packages/emacs-xyz.scm (line: 13391, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13392, column 0
  • gnu/packages/emacs-xyz.scm (line: 13392, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13393, column 0
  • gnu/packages/emacs-xyz.scm (line: 13393, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13394, column 0
  • gnu/packages/emacs-xyz.scm (line: 13394, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13395, column 0
  • gnu/packages/emacs-xyz.scm (line: 13395, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13396, column 0
  • gnu/packages/emacs-xyz.scm (line: 13396, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13397, column 0
  • gnu/packages/emacs-xyz.scm (line: 13397, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13398, column 0
  • gnu/packages/emacs-xyz.scm (line: 13398, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13399, column 0
  • gnu/packages/emacs-xyz.scm (line: 13399, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13400, column 0
  • gnu/packages/emacs-xyz.scm (line: 13400, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13401, column 0
  • gnu/packages/emacs-xyz.scm (line: 13401, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13402, column 0
  • gnu/packages/emacs-xyz.scm (line: 13402, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13403, column 0
  • gnu/packages/emacs-xyz.scm (line: 13403, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13404, column 0
  • gnu/packages/emacs-xyz.scm (line: 13404, column: 0)
emacs-ert-runner @ 0.8.0formatting

Look for formatting issues in the source

tabulation on line 13405, column 0
  • gnu/packages/emacs-xyz.scm (line: 13405, column: 0)
emacs-dash-docs @ 1.4.0-2.dafc8fcformatting

Look for formatting issues in the source

line 23663 is way too long (91 characters)
  • gnu/packages/emacs-xyz.scm (line: 23663, column: 0)
tigervnc-server @ 1.11.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/vnc.scm (line: 214, column: 2)
tigervnc-server @ 1.11.0formatting

Look for formatting issues in the source

line 286 is way too long (102 characters)
  • gnu/packages/vnc.scm (line: 286, column: 0)
tigervnc-server @ 1.11.0formatting

Look for formatting issues in the source

line 289 is way too long (102 characters)
  • gnu/packages/vnc.scm (line: 289, column: 0)
tigervnc-server @ 1.11.0formatting

Look for formatting issues in the source

tabulation on line 298, column 0
  • gnu/packages/vnc.scm (line: 298, column: 0)
v @ 0.1.29name

Validate package names

name should be longer than a single character
  • guix/packages.scm (line: 464, column: 2)
ruby_version @ 1.0.2name

Validate package names

name should use hyphens instead of underscores
  • gnu/packages/ruby.scm (line: 9248, column: 10)
ruby-progress_bar @ 1.1.0name

Validate package names

name should use hyphens instead of underscores
  • gnu/packages/ruby.scm (line: 5477, column: 10)
ruby-data_uri @ 0.1.0name

Validate package names

name should use hyphens instead of underscores
  • gnu/packages/ruby.scm (line: 4835, column: 10)
python-requests_ntlm @ 1.1.0name

Validate package names

name should use hyphens instead of underscores
  • gnu/packages/python-web.scm (line: 2575, column: 10)
perl-crypt-unixcrypt_xs @ 0.11name

Validate package names

name should use hyphens instead of underscores
  • gnu/packages/perl.scm (line: 2265, column: 10)
nsis-x86_64 @ 3.05name

Validate package names

name should use hyphens instead of underscores
  • gnu/packages/installers.scm (line: 36, column: 12)
mingw-w64-x86_64-winpthreads @ 8.0.0name

Validate package names

name should use hyphens instead of underscores
  • gnu/packages/mingw.scm (line: 47, column: 12)
mingw-w64-x86_64 @ 8.0.0name

Validate package names

name should use hyphens instead of underscores
  • gnu/packages/mingw.scm (line: 47, column: 12)
efi_analyzer @ 0.0.0-0.77c9e3aname

Validate package names

name should use hyphens instead of underscores
  • guix/packages.scm (line: 464, column: 2)
python2-psycopg2 @ 2.8.6description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/databases.scm (line: 3256, column: 5)
python2-ccm @ 2.1.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 84
  • gnu/packages/databases.scm (line: 2866, column: 17)
python-psycopg2 @ 2.8.6description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/databases.scm (line: 3256, column: 5)
python-ccm @ 2.1.6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 84
  • gnu/packages/databases.scm (line: 2866, column: 17)
guile-wiredtiger @ 0.7.0description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/databases.scm (line: 2350, column: 5)
sqlcipher @ 3.4.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/databases.scm (line: 2584, column: 5)
linux-libre @ 5.4.118derivation

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'
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre @ 5.10.36derivation

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'
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-headers @ 5.4.118patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 553, column: 2)
linux-libre-headers @ 5.10.36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 553, column: 2)
linux-libre-arm64-generic @ 5.4.118patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-arm64-generic @ 5.10.36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-arm-generic @ 5.4.118patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-arm-generic @ 5.10.36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre @ 5.4.118patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre @ 5.10.36patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-arm64-generic @ 5.4.118formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre-arm64-generic @ 5.10.36formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre-arm-generic @ 5.4.118formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre-arm-generic @ 5.10.36formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre @ 5.4.118formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre @ 5.10.36formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
jfs_fsck-static @ 1.1.15name

Validate package names

name should use hyphens instead of underscores
  • gnu/packages/file-systems.scm (line: 611, column: 10)
perftest @ 4.4-0.4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 99
  • gnu/packages/linux.scm (line: 5820, column: 17)
fakeroot @ 1.25.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 114, 240
  • gnu/packages/linux.scm (line: 7520, column: 17)
f2fs-fsck-static @ 1.14.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 91
  • gnu/packages/linux.scm (line: 5427, column: 17)
ecryptfs-utils @ 111description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/linux.scm (line: 6048, column: 5)
c-blosc @ 1.18.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
  • gnu/packages/compression.scm (line: 2419, column: 5)
proot-static @ 5.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 6816, column: 2)
perftest @ 4.4-0.4formatting

Look for formatting issues in the source

line 5830 is way too long (98 characters)
  • gnu/packages/linux.scm (line: 5830, column: 0)
minizip @ 1.2.11formatting

Look for formatting issues in the source

line 162 is way too long (115 characters)
  • gnu/packages/compression.scm (line: 162, column: 0)
libnfs @ 3.0.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/file-systems.scm (line: 809, column: 0)
google-brotli @ 1.0.9formatting

Look for formatting issues in the source

line 2049 is way too long (94 characters)
  • gnu/packages/compression.scm (line: 2049, column: 0)
glusterfs @ 7.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/file-systems.scm (line: 704, column: 0)
ccache @ 4.3formatting

Look for formatting issues in the source

tabulation on line 59, column 0
  • gnu/packages/ccache.scm (line: 59, column: 0)
guile2.2-sjson @ 0.2.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/guile-xyz.scm (line: 786, column: 2)
guile2.2-email @ 0.2.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/guile-xyz.scm (line: 1286, column: 2)
guile-f-scm @ 0.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/guile-xyz.scm (line: 264, column: 5)
guile-email-latest @ 0.2.2-1.ca0520adescription

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/guile-xyz.scm (line: 1265, column: 4)
guile-dbd-sqlite3 @ 2.1.6description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/guile-xyz.scm (line: 1523, column: 5)
guile2.2-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
  • gnu/packages/guile-xyz.scm (line: 1088, column: 2)
guile2.2-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'automake' should probably be a native input
  • gnu/packages/guile-xyz.scm (line: 1088, column: 2)
guile2.2-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
  • gnu/packages/guile-xyz.scm (line: 1088, column: 2)
guile-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
  • gnu/packages/guile-xyz.scm (line: 1076, column: 7)
guile-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'automake' should probably be a native input
  • gnu/packages/guile-xyz.scm (line: 1076, column: 7)
guile-simple-zmq @ 0.0.0-9.b2ea97einputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
  • gnu/packages/guile-xyz.scm (line: 1076, column: 7)
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
  • gnu/packages/guile-xyz.scm (line: 1999, column: 7)
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
  • gnu/packages/guile-xyz.scm (line: 663, column: 2)
guile-dbi @ 2.1.6formatting

Look for formatting issues in the source

line 1480 is way too long (94 characters)
  • gnu/packages/guile-xyz.scm (line: 1480, column: 0)
linux-libre-riscv64-generic @ 5.11.20derivation

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'
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-bpf @ 5.11.20derivation

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'
  • gnu/packages/linux.scm (line: 1153, column: 4)
linux-libre @ 5.12.3derivation

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'
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre @ 5.11.20derivation

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'
  • gnu/packages/linux.scm (line: 779, column: 2)
x86-energy-perf-policy @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 5912, column: 2)
turbostat @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 5634, column: 2)
tmon @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 5587, column: 2)
perf @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 4204, column: 2)
linux-libre-riscv64-generic @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-mips64el-fuloong2e @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-headers @ 5.12.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 553, column: 2)
linux-libre-headers @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 553, column: 2)
linux-libre-bpf @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 1153, column: 4)
linux-libre-arm64-generic @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-arm-veyron @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • guix/packages.scm (line: 464, column: 2)
linux-libre-arm-omap2plus @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre-arm-generic @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre @ 5.12.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
linux-libre @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 779, column: 2)
freefall @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 5432, column: 2)
cpupower @ 5.11.20patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/linux.scm (line: 5871, column: 2)
linux-libre-riscv64-generic @ 5.11.20formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre-mips64el-fuloong2e @ 5.11.20formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre-arm64-generic @ 5.11.20formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre-arm-omap2plus @ 5.11.20formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre-arm-generic @ 5.11.20formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre @ 5.12.3formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
linux-libre @ 5.11.20formatting

Look for formatting issues in the source

line 869 is way too long (117 characters)
  • gnu/packages/linux.scm (line: 869, column: 0)
libblockdev @ 2.25formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/disk.scm (line: 962, column: 0)
dmraid @ 1.0.0.rc16-3formatting

Look for formatting issues in the source

line 883 is way too long (91 characters)
  • gnu/packages/disk.scm (line: 883, column: 0)
mergerfs @ 2.32.4formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/file-systems.scm (line: 1269, column: 0)
cawbird @ 1.4.1formatting

Look for formatting issues in the source

line 85 is way too long (104 characters)
  • gnu/packages/syndication.scm (line: 85, column: 0)
xdg-user-dirs @ 0.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
  • gnu/packages/freedesktop.scm (line: 1821, column: 17)
python-cchardet @ 2.1.7description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/freedesktop.scm (line: 1974, column: 15)
guile3.0-ncurses-with-gpm @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/guile-xyz.scm (line: 2264, column: 2)
guile2.2-ncurses @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/guile-xyz.scm (line: 2247, column: 2)
guile2.2-commonmark @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/guile-xyz.scm (line: 2630, column: 2)
guile2.0-commonmark @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/guile-xyz.scm (line: 2636, column: 2)
guile-zstd @ 0.1.1description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/guile.scm (line: 937, column: 5)
guile-stis-parser @ 1.2.4.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 117
  • gnu/packages/guile-xyz.scm (line: 2849, column: 5)
guile-ncurses-with-gpm @ 3.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/guile-xyz.scm (line: 2257, column: 2)
udiskie @ 2.1.0inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/freedesktop.scm (line: 1998, column: 5)
telepathy-mission-control @ 5.16.5inputs-should-be-native

Identify inputs that should be native inputs

'gtk-doc' should probably be a native input
  • gnu/packages/freedesktop.scm (line: 1569, column: 5)
python2-clf @ 0.5.7inputs-should-be-native

Identify inputs that should be native inputs

'python2-nose' should probably be a native input
  • gnu/packages/web.scm (line: 6504, column: 7)
python-pytest-httpbin @ 0.2.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/web.scm (line: 6274, column: 2)
python-clf @ 0.5.7inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
  • gnu/packages/web.scm (line: 6504, column: 7)
guile2.2-gi @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/guile-xyz.scm (line: 3084, column: 5)
guile-gi @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/guile-xyz.scm (line: 3070, column: 12)
java-eclipse-jetty-xml @ 9.4.39source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7306, column: 2)
java-eclipse-jetty-xml @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7330, column: 12)
java-eclipse-jetty-webapp @ 9.4.39source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7350, column: 2)
java-eclipse-jetty-webapp @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7380, column: 12)
java-eclipse-jetty-util-ajax @ 9.4.39source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7237, column: 2)
java-eclipse-jetty-util @ 9.4.39source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 6899, column: 12)
java-eclipse-jetty-util @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 6941, column: 12)
java-eclipse-jetty-servlet @ 9.4.39source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7249, column: 2)
java-eclipse-jetty-servlet @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7283, column: 12)
java-eclipse-jetty-server @ 9.4.39source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7134, column: 2)
java-eclipse-jetty-server @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7183, column: 12)
java-eclipse-jetty-security @ 9.4.39source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7195, column: 2)
java-eclipse-jetty-security @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7226, column: 12)
java-eclipse-jetty-jmx @ 9.4.39source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7069, column: 2)
java-eclipse-jetty-jmx @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7096, column: 12)
java-eclipse-jetty-io @ 9.4.39source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 6987, column: 2)
java-eclipse-jetty-io @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7017, column: 12)
java-eclipse-jetty-http @ 9.4.39source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7029, column: 2)
java-eclipse-jetty-http @ 9.2.22source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
  • gnu/packages/web.scm (line: 7062, column: 12)
http-parser @ 2.9.4-1.ec8b5eepatch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/web.scm (line: 6302, column: 4)
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
  • gnu/packages/guile.scm (line: 400, column: 2)
guile-readline @ 3.0.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/guile.scm (line: 400, column: 2)
netsurf @ 3.10patch-headers

Validate patch headers

netsurf-message-timestamp.patch: patch lacks comment and upstream status
  • gnu/packages/web.scm (line: 5630, column: 5)
aegis @ 4.24patch-headers

Validate patch headers

aegis-perl-tempdir2.patch: patch lacks comment and upstream status
  • gnu/packages/version-control.scm (line: 2044, column: 12)
varnish @ 6.5.1formatting

Look for formatting issues in the source

line 6070 is way too long (91 characters)
  • gnu/packages/web.scm (line: 6070, column: 0)
serf @ 1.3.9formatting

Look for formatting issues in the source

line 1971 is way too long (92 characters)
  • gnu/packages/web.scm (line: 1971, column: 0)
plymouth @ 0.9.4formatting

Look for formatting issues in the source

line 2081 is way too long (91 characters)
  • gnu/packages/freedesktop.scm (line: 2081, column: 0)
nginx-accept-language-module @ 0.0.0-1.2f69842formatting

Look for formatting issues in the source

line 616 is way too long (92 characters)
  • gnu/packages/web.scm (line: 616, column: 0)
malcontent @ 0.8.0formatting

Look for formatting issues in the source

line 353 is way too long (91 characters)
  • gnu/packages/freedesktop.scm (line: 353, column: 0)
localed @ 241formatting

Look for formatting issues in the source

line 816 is way too long (96 characters)
  • gnu/packages/freedesktop.scm (line: 816, column: 0)
krona-tools @ 2.8formatting

Look for formatting issues in the source

trailing white space on line 1238
  • gnu/packages/web.scm (line: 1238, column: 0)
guile2.2-readline @ 2.2.7formatting

Look for formatting issues in the source

line 432 is way too long (94 characters)
  • gnu/packages/guile.scm (line: 432, column: 0)
guile-readline @ 3.0.2formatting

Look for formatting issues in the source

line 432 is way too long (94 characters)
  • gnu/packages/guile.scm (line: 432, column: 0)
guile-for-guile-emacs @ 2.1.2-1.15ca784formatting

Look for formatting issues in the source

line 544 is way too long (96 characters)
  • gnu/packages/guile.scm (line: 544, column: 0)
guile-for-guile-emacs @ 2.1.2-1.15ca784formatting

Look for formatting issues in the source

trailing white space on line 548
  • gnu/packages/guile.scm (line: 548, column: 0)
guile-avahi @ 0.4.0-1.6d43cafformatting

Look for formatting issues in the source

line 4337 is way too long (92 characters)
  • gnu/packages/guile-xyz.scm (line: 4337, column: 0)
b4 @ 0.6.2formatting

Look for formatting issues in the source

line 2369 is way too long (93 characters)
  • gnu/packages/version-control.scm (line: 2369, column: 0)
b4 @ 0.6.2formatting

Look for formatting issues in the source

line 2370 is way too long (112 characters)
  • gnu/packages/version-control.scm (line: 2370, column: 0)
samblaster @ 0.1.24description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 263
  • gnu/packages/bioinformatics.scm (line: 14881, column: 17)
rust-unicode-categories @ 0.1.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/crates-io.scm (line: 46785, column: 5)
rust-tungstenite @ 0.11.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 62
  • gnu/packages/crates-io.scm (line: 46194, column: 5)
rust-stringprep @ 0.1.2description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/crates-io.scm (line: 40263, column: 5)
rust-snailquote @ 0.3.0description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/crates-io.scm (line: 39294, column: 5)
rust-rustc-tools-util @ 0.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/crates-io.scm (line: 34852, column: 5)
rust-nu-plugin-query-json @ 0.31.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/shells.scm (line: 1830, column: 17)
rust-juliex @ 0.3.0-alpha.8description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/crates-io.scm (line: 20707, column: 5)
rust-funty @ 1.1.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 127
  • gnu/packages/crates-io.scm (line: 15032, column: 5)
rust-bugreport @ 0.4.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/crates-io.scm (line: 5561, column: 5)
rust-bugreport @ 0.3.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/crates-io.scm (line: 5567, column: 2)
r-seqlogo @ 1.56.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 8205, column: 5)
r-rtracklayer @ 1.50.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 7926, column: 5)
r-bseqsc @ 1.0-1.fef3f3edescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 395
  • gnu/packages/bioinformatics.scm (line: 13268, column: 19)
python-pyfit-sne @ 1.0.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 13746, column: 5)
python-drep @ 3.2.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/bioinformatics.scm (line: 12689, column: 5)
nushell @ 0.31.0description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/shells.scm (line: 1017, column: 5)
kraken2 @ 2.1.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 206
  • gnu/packages/bioinformatics.scm (line: 15257, column: 15)
variant-tools @ 3.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
  • gnu/packages/bioinformatics.scm (line: 8966, column: 5)
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
  • gnu/packages/crates-io.scm (line: 21670, column: 5)
python-velocyto @ 0.17.17inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
  • gnu/packages/bioinformatics.scm (line: 13888, column: 2)
python-drep @ 3.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/bioinformatics.scm (line: 12666, column: 2)
python-bbknn @ 1.3.6inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
  • gnu/packages/bioinformatics.scm (line: 12632, column: 2)
multiqc @ 1.5inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
  • gnu/packages/bioinformatics.scm (line: 8904, column: 2)
ensembl-vep @ 103.1source-file-name

Validate file names of sources

the source file name should contain the package name
  • gnu/packages/bioinformatics.scm (line: 15338, column: 7)
python-pygenometracks @ 3.3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-distlib@0.3.1 and python-distlib@0.3.0 collide
  • gnu/packages/bioinformatics.scm (line: 13073, column: 2)
vcflib @ 1.0.2formatting

Look for formatting issues in the source

line 14751 is way too long (92 characters)
  • gnu/packages/bioinformatics.scm (line: 14751, column: 0)
salmon @ 0.13.1formatting

Look for formatting issues in the source

line 11151 is way too long (99 characters)
  • gnu/packages/bioinformatics.scm (line: 11151, column: 0)
rust-wasmparser @ 0.57.0formatting

Look for formatting issues in the source

line 48575 is way too long (92 characters)
  • gnu/packages/crates-io.scm (line: 48575, column: 0)
rust-packed-struct @ 0.3.0formatting

Look for formatting issues in the source

tabulation on line 50084, column 0
  • gnu/packages/crates-io.scm (line: 50084, column: 0)
rust-packed-struct @ 0.3.0formatting

Look for formatting issues in the source

tabulation on line 50086, column 0
  • gnu/packages/crates-io.scm (line: 50086, column: 0)
rust-packed-struct @ 0.3.0formatting

Look for formatting issues in the source

tabulation on line 50087, column 0
  • gnu/packages/crates-io.scm (line: 50087, column: 0)
rust-nix @ 0.15.0formatting

Look for formatting issues in the source

line 25235 is way too long (93 characters)
  • gnu/packages/crates-io.scm (line: 25235, column: 0)
rust-inflections @ 1.1.1formatting

Look for formatting issues in the source

line 50287 is way too long (107 characters)
  • gnu/packages/crates-io.scm (line: 50287, column: 0)
rust-inflections @ 1.1.1formatting

Look for formatting issues in the source

line 50289 is way too long (107 characters)
  • gnu/packages/crates-io.scm (line: 50289, column: 0)
r-cellchat @ 1.0.0-1.21edd22formatting

Look for formatting issues in the source

line 10082 is way too long (92 characters)
  • gnu/packages/bioinformatics.scm (line: 10082, column: 0)
phast @ 1.5formatting

Look for formatting issues in the source

tabulation on line 15006, column 30
  • gnu/packages/bioinformatics.scm (line: 15006, column: 30)
kraken2 @ 2.1.1formatting

Look for formatting issues in the source

tabulation on line 15226, column 0
  • gnu/packages/bioinformatics.scm (line: 15226, column: 0)
kraken2 @ 2.1.1formatting

Look for formatting issues in the source

tabulation on line 15227, column 0
  • gnu/packages/bioinformatics.scm (line: 15227, column: 0)
kraken2 @ 2.1.1formatting

Look for formatting issues in the source

tabulation on line 15228, column 0
  • gnu/packages/bioinformatics.scm (line: 15228, column: 0)
fastahack @ 1.0.0formatting

Look for formatting issues in the source

line 14638 is way too long (91 characters)
  • gnu/packages/bioinformatics.scm (line: 14638, column: 0)
ensembl-vep @ 103.1formatting

Look for formatting issues in the source

line 15378 is way too long (92 characters)
  • gnu/packages/bioinformatics.scm (line: 15378, column: 0)
ensembl-vep @ 103.1formatting

Look for formatting issues in the source

line 15426 is way too long (100 characters)
  • gnu/packages/bioinformatics.scm (line: 15426, column: 0)
dropseq-tools @ 1.13formatting

Look for formatting issues in the source

tabulation on line 11718, column 0
  • gnu/packages/bioinformatics.scm (line: 11718, column: 0)
dropseq-tools @ 1.13formatting

Look for formatting issues in the source

tabulation on line 11730, column 0
  • gnu/packages/bioinformatics.scm (line: 11730, column: 0)
python2-rst.linker @ 1.11description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 4378, column: 17)
python2-q @ 2.6description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 8834, column: 5)
python2-pyaml @ 18.11.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 15047, column: 5)
python2-editor @ 1.0.4description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 13283, column: 4)
python2-dukpy @ 0.3description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 18886, column: 5)
python2-dnspython @ 1.16.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 14876, column: 2)
python2-dbus @ 1.2.16description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 8280, column: 2)
python2-argcomplete @ 1.11.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 16154, column: 4)
python-uncertainties @ 3.1.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 92
  • gnu/packages/python-xyz.scm (line: 12545, column: 5)
python-rst.linker @ 1.11description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 4378, column: 17)
python-readability @ 0.3.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 140
  • gnu/packages/python-xyz.scm (line: 25520, column: 5)
python-q @ 2.6description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 8834, column: 5)
python-pywinrm @ 0.4.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 6677, column: 5)
python-pyquery @ 1.2.17description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 12888, column: 17)
python-pypandoc @ 1.5description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 24757, column: 17)
python-pyaml @ 18.11.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 15047, column: 5)
python-py3status @ 3.21description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 13953, column: 17)
python-pikepdf @ 2.12.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 6191, column: 5)
python-jinja2-time @ 0.2.0description

Validate package descriptions

use @code or similar ornament instead of quotes
  • gnu/packages/python-xyz.scm (line: 3697, column: 5)
python-eliot @ 1.12.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 153
  • gnu/packages/python-xyz.scm (line: 23878, column: 5)
python-dukpy @ 0.3description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 18886, column: 5)
python-dnspython @ 2.1.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 14870, column: 5)
python-dnspython @ 1.16.0description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 14876, column: 2)
python-argcomplete @ 1.11.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 16143, column: 17)
python-arcp @ 0.2.1description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 18080, column: 5)
ptpython2 @ 3.0.5description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/python-xyz.scm (line: 15220, column: 4)
snakemake @ 5.32.2inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 8601, column: 2)
python2-xopen @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-setuptools-scm' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 16278, column: 4)
python2-sure @ 1.4.11inputs-should-be-native

Identify inputs that should be native inputs

'python2-mock' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 17715, column: 2)
python2-setuptools-scm-git-archive @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-setuptools-scm' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 18922, column: 2)
python2-pkgconfig @ 1.3.1inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 13730, column: 6)
python2-numpydoc @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

'python2-sphinx' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 5381, column: 4)
python2-matplotlib @ 2.2.4inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 5611, column: 4)
python2-m2r @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python2-docutils' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 16760, column: 2)
python2-djvulibre @ 0.8.6inputs-should-be-native

Identify inputs that should be native inputs

'python2-cython' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 24973, column: 5)
python-xopen @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 16253, column: 2)
python-sure @ 1.4.11inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 17715, column: 2)
python-setuptools-scm-git-archive @ 1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 18922, column: 2)
python-rst2ansi @ 0.1.5inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 16481, column: 2)
python-restructuredtext-lint @ 1.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 3889, column: 2)
python-readme-renderer @ 26.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 24363, column: 2)
python-pytest-check-links @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 23546, column: 2)
python-pytest-check-links @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 23546, column: 2)
python-pytest-black @ 0.3.8inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 10189, column: 2)
python-pkgconfig @ 1.3.1inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 13730, column: 6)
python-pifpaf @ 2.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 23504, column: 2)
python-numpydoc @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 5355, column: 2)
python-moto @ 1.3.16.dev134inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 12254, column: 2)
python-matplotlib @ 3.1.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 5510, column: 5)
python-mamba @ 0.11.2inputs-should-be-native

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 17218, column: 2)
python-m2r @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 16760, column: 2)
python-legacy-api-wrap @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 10243, column: 2)
python-legacy-api-wrap @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 10243, column: 2)
python-jsonrpc-server @ 0.4.0inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 4445, column: 2)
python-jsonrpc-server @ 0.4.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 4445, column: 2)
python-jaraco-packaging @ 6.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 7329, column: 2)
python-jaraco-packaging @ 6.1inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 7329, column: 2)
python-jaraco-packaging @ 6.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 7329, column: 2)
python-iocapture @ 0.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 22542, column: 4)
python-iocapture @ 0.1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 22542, column: 4)
python-get-version @ 2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 10214, column: 2)
python-get-version @ 2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 10214, column: 2)
python-docusign-esign @ 3.1.0inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 23408, column: 2)
python-doc8 @ 0.8.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 3921, column: 2)
python-djvulibre @ 0.8.6inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 24973, column: 5)
python-case @ 1.5.3inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 1892, column: 2)
python-case @ 1.5.3inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 1892, column: 2)
python-argh @ 0.26.2-1.dcd3253inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 22582, column: 4)
python-argh @ 0.26.2-1.dcd3253inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 22582, column: 4)
python-argh @ 0.26.2-1.dcd3253inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 22582, column: 4)
python-amply @ 0.1.4inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 8502, column: 2)
pelican @ 4.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/python-xyz.scm (line: 4720, column: 2)
python2-ipython-cluster-helper @ 0.6.4inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python2-setuptools' should probably not be an input at all
  • gnu/packages/python-xyz.scm (line: 7514, column: 2)
python-yamllint @ 1.26.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-xyz.scm (line: 19405, column: 2)
python-virtualenv @ 20.2.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-xyz.scm (line: 3568, column: 2)
python-pikepdf @ 2.12.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-xyz.scm (line: 6184, column: 5)
python-legacy-api-wrap @ 1.2inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-xyz.scm (line: 10243, column: 2)
python-jaraco-packaging @ 6.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-xyz.scm (line: 7329, column: 2)
python-ipython-cluster-helper @ 0.6.4inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-xyz.scm (line: 7514, column: 2)
python-get-version @ 2.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-xyz.scm (line: 10214, column: 2)
python-eliot @ 1.12.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
  • gnu/packages/python-xyz.scm (line: 23832, column: 2)
poetry @ 1.1.5inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-pip' should probably not be an input at all
  • gnu/packages/python-xyz.scm (line: 14683, column: 2)
python2-ipython-cluster-helper @ 0.6.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python2-tornado@5.1.1 and python2-tornado@6.1 collide
  • gnu/packages/python-xyz.scm (line: 7514, column: 2)
python-ipython-cluster-helper @ 0.6.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-tornado@5.1.1 and python-tornado@6.1 collide
  • gnu/packages/python-xyz.scm (line: 7514, column: 2)
python-ipyparallel @ 6.2.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-tornado@6.1 and python-tornado@5.1.1 collide
  • gnu/packages/python-xyz.scm (line: 7464, column: 2)
python2-waitress @ 1.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python-xyz.scm (line: 12788, column: 2)
python2-pybugz @ 0.6.11patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python-xyz.scm (line: 2487, column: 2)
python2-pep8 @ 1.7.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python-xyz.scm (line: 9066, column: 2)
python2-packaging @ 20.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python-xyz.scm (line: 17577, column: 2)
python2-larch @ 1.20151025patch-file-names

Validate file names and availability of patches

python2-larch-coverage-4.0a6-compatibility.patch: file name is too long
  • gnu/packages/python-xyz.scm (line: 16969, column: 2)
python2-configobj @ 5.0.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python-xyz.scm (line: 11543, column: 2)
python2-argcomplete @ 1.11.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python-xyz.scm (line: 16154, column: 4)
python-matplotlib-documentation @ 3.1.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/python-xyz.scm (line: 5653, column: 2)
scons @ 3.0.4formatting

Look for formatting issues in the source

line 2684 is way too long (96 characters)
  • gnu/packages/python-xyz.scm (line: 2684, column: 0)
python2-invoke @ 1.5.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/python-xyz.scm (line: 16711, column: 0)
python-numpy @ 1.17.3formatting

Look for formatting issues in the source

line 4943 is way too long (152 characters)
  • gnu/packages/python-xyz.scm (line: 4943, column: 0)
python-nbconvert @ 6.0.7formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/python-xyz.scm (line: 11045, column: 0)
python-matplotlib @ 3.1.2formatting

Look for formatting issues in the source

line 5506 is way too long (107 characters)
  • gnu/packages/python-xyz.scm (line: 5506, column: 0)
python-matplotlib @ 3.1.2formatting

Look for formatting issues in the source

line 5546 is way too long (96 characters)
  • gnu/packages/python-xyz.scm (line: 5546, column: 0)
python-matplotlib @ 3.1.2formatting

Look for formatting issues in the source

line 5567 is way too long (105 characters)
  • gnu/packages/python-xyz.scm (line: 5567, column: 0)
python-ipython-documentation @ 7.9.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/python-xyz.scm (line: 8018, column: 0)
python-invoke @ 1.5.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/python-xyz.scm (line: 16711, column: 0)
python-imagecodecs @ 2021.3.31formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
  • gnu/packages/python-xyz.scm (line: 6384, column: 0)
python-boto3 @ 1.16.22formatting

Look for formatting issues in the source

tabulation on line 12676, column 0
  • gnu/packages/python-xyz.scm (line: 12676, column: 0)
python-boto3 @ 1.16.22formatting

Look for formatting issues in the source

tabulation on line 12677, column 0
  • gnu/packages/python-xyz.scm (line: 12677, column: 0)
python-boto3 @ 1.16.22formatting

Look for formatting issues in the source

tabulation on line 12678, column 0
  • gnu/packages/python-xyz.scm (line: 12678, column: 0)
ucsim @ 0.6-pre68description

Validate package descriptions

description should start with an upper-case letter or digit
  • gnu/packages/embedded.scm (line: 1502, column: 17)
conda @ 4.8.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
  • gnu/packages/package-management.scm (line: 991, column: 5)
electron-cash @ 4.2.4inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
  • gnu/packages/finance.scm (line: 579, column: 5)
python-trezor-agent @ 0.13.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
  • gnu/packages/finance.scm (line: 831, column: 2)
emacs-beancount @ 2.3.4patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
  • gnu/packages/finance.scm (line: 1617, column: 2)
bitcoin-unlimited @ 1.9.1.1formatting

Look for formatting issues in the source

line 1444 is way too long (91 characters)
  • gnu/packages/finance.scm (line: 1444, column: 0)