| Package | Linter | Message | Location | |
|---|---|---|---|---|
| zn-poly @ 0.9.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| wxwidgets-gtk2 @ 3.1.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| wxwidgets-gtk2 @ 3.0.5.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| robin-map @ 0.6.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 281 | ||
| rcm @ 1.3.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 183 | ||
| python-wxpython @ 4.0.7.post1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| perl6-grammar-debugger @ 1.0.1-1.0375008 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 203 | ||
| perl-test-file-contents @ 0.23 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| kget @ 20.04.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 169 | ||
| java-jblas @ 1.2.4 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-langkit @ 0.0.0-0.fe0bc8b | inputs-should-be-native Identify inputs that should be native inputs | 'python2-docutils' should probably be a native input | ||
| python-debtcollector @ 1.19.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| presentty @ 0.2.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| flex @ 2.6.4 | inputs-should-be-native Identify inputs that should be native inputs | 'bison' should probably be a native input | ||
| flex @ 2.6.4 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| cinnamon-desktop @ 3.4.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| bison @ 3.6.3 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| bison @ 3.6.3 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| bison @ 3.5.3 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| bison @ 3.5.3 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| bison @ 3.0.5 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| bison @ 3.0.5 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| aseba @ 1.6.0-0.3b35de8 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| rdmd @ 2.077.1 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| infiniband-diags @ 2.0.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| mkbootimg @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-settings-builder @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-settings @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-resolver-provider @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-repository-metadata @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-plugin-api @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-model-builder @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-model @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-builder-support @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-artifact @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libmhash @ 0.9.9.9 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libcanberra-gtk2 @ 0.30 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| jfsutils-static @ 1.1.15 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| idutils @ 4.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| fastboot @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| bash-static @ 5.0.16 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| bash-minimal @ 5.0.16 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| android-libziparchive @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| android-libutils @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| android-libsparse @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| android-liblog @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| android-libcutils @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| adb @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| sdsl-lite @ 2.1.1 | formatting Look for formatting issues in the source | line 237 is way too long (145 characters) | ||
| raspi-arm64-chainloader @ 0.1 | formatting Look for formatting issues in the source | line 211 is way too long (139 characters) | ||
| raspi-arm64-chainloader @ 0.1 | formatting Look for formatting issues in the source | line 224 is way too long (97 characters) | ||
| raspi-arm-chainloader @ 0.1 | formatting Look for formatting issues in the source | line 131 is way too long (129 characters) | ||
| raspi-arm-chainloader @ 0.1 | formatting Look for formatting issues in the source | line 137 is way too long (102 characters) | ||
| pth @ 2.0.7 | formatting Look for formatting issues in the source | trailing white space on line 42 | ||
| presentty @ 0.2.1 | formatting Look for formatting issues in the source | line 45 is way too long (117 characters) | ||
| perl-test2-plugin-nowarnings @ 0.06 | formatting Look for formatting issues in the source | line 106 is way too long (92 characters) | ||
| papi @ 5.5.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| ncurses @ 6.2 | formatting Look for formatting issues in the source | trailing white space on line 165 | ||
| ncurses @ 6.2 | formatting Look for formatting issues in the source | line 179 is way too long (94 characters) | ||
| musl-cross @ 0.1-3.a8a6649 | formatting Look for formatting issues in the source | line 152 is way too long (92 characters) | ||
| mrustc @ 0.9 | formatting Look for formatting issues in the source | line 178 is way too long (123 characters) | ||
| maven-wagon-http @ 3.3.4 | formatting Look for formatting issues in the source | line 901 is way too long (105 characters) | ||
| maven-wagon-http @ 3.3.4 | formatting Look for formatting issues in the source | line 906 is way too long (138 characters) | ||
| maven-wagon-http @ 3.3.4 | formatting Look for formatting issues in the source | line 907 is way too long (129 characters) | ||
| maven-wagon-file @ 3.3.4 | formatting Look for formatting issues in the source | line 738 is way too long (125 characters) | ||
| maven-shared-utils @ 3.2.1 | formatting Look for formatting issues in the source | line 583 is way too long (109 characters) | ||
| maven-resolver-transport-wagon @ 1.3.1 | formatting Look for formatting issues in the source | line 255 is way too long (91 characters) | ||
| maven-resolver-transport-wagon @ 1.3.1 | formatting Look for formatting issues in the source | line 270 is way too long (106 characters) | ||
| maven-resolver-transport-wagon @ 1.3.1 | formatting Look for formatting issues in the source | line 284 is way too long (102 characters) | ||
| maven-resolver-impl @ 1.3.1 | formatting Look for formatting issues in the source | line 201 is way too long (92 characters) | ||
| maven-resolver-impl @ 1.3.1 | formatting Look for formatting issues in the source | line 210 is way too long (92 characters) | ||
| maven-resolver-impl @ 1.3.1 | formatting Look for formatting issues in the source | line 218 is way too long (95 characters) | ||
| maven-resolver-impl @ 1.3.1 | formatting Look for formatting issues in the source | line 221 is way too long (93 characters) | ||
| maven-resolver-connector-basic @ 1.3.1 | formatting Look for formatting issues in the source | line 165 is way too long (99 characters) | ||
| lxde-common @ 0.99.2 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| libsigsegv @ 2.12 | formatting Look for formatting issues in the source | line 48 is way too long (133 characters) | ||
| libdaemon @ 0.14 | formatting Look for formatting issues in the source | line 35 is way too long (147 characters) | ||
| libdaemon @ 0.14 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| ldc @ 1.10.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| ldc @ 0.17.6 | formatting Look for formatting issues in the source | line 130 is way too long (98 characters) | ||
| kget @ 20.04.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| js-mathjax @ 2.7.2 | formatting Look for formatting issues in the source | line 150 is way too long (91 characters) | ||
| hyperledger-iroha @ 1.1.1 | formatting Look for formatting issues in the source | line 169 is way too long (105 characters) | ||
| gx-go @ 1.9.0 | formatting Look for formatting issues in the source | line 186 is way too long (91 characters) | ||
| gx-go @ 1.9.0 | formatting Look for formatting issues in the source | line 191 is way too long (91 characters) | ||
| gx-go @ 1.9.0 | formatting Look for formatting issues in the source | line 196 is way too long (91 characters) | ||
| gx-go @ 1.9.0 | formatting Look for formatting issues in the source | line 197 is way too long (99 characters) | ||
| gx-go @ 1.9.0 | formatting Look for formatting issues in the source | line 198 is way too long (91 characters) | ||
| gx @ 0.14.3 | formatting Look for formatting issues in the source | line 126 is way too long (91 characters) | ||
| gx @ 0.14.3 | formatting Look for formatting issues in the source | line 131 is way too long (91 characters) | ||
| gx @ 0.14.3 | formatting Look for formatting issues in the source | line 136 is way too long (91 characters) | ||
| gx @ 0.14.3 | formatting Look for formatting issues in the source | line 137 is way too long (99 characters) | ||
| gx @ 0.14.3 | formatting Look for formatting issues in the source | line 138 is way too long (91 characters) | ||
| gx @ 0.14.3 | formatting Look for formatting issues in the source | line 145 is way too long (91 characters) | ||
| guile-wm @ 1.0-1.f3c7b3b | formatting Look for formatting issues in the source | line 128 is way too long (92 characters) | ||
| go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1 | formatting Look for formatting issues in the source | line 81 is way too long (93 characters) | ||
| go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1 | formatting Look for formatting issues in the source | line 82 is way too long (91 characters) | ||
| go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1 | formatting Look for formatting issues in the source | line 85 is way too long (93 characters) | ||
| go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1 | formatting Look for formatting issues in the source | line 88 is way too long (93 characters) | ||
| go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1 | formatting Look for formatting issues in the source | line 89 is way too long (101 characters) | ||
| go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1 | formatting Look for formatting issues in the source | line 95 is way too long (93 characters) | ||
| fdroidserver @ 1.1.9 | formatting Look for formatting issues in the source | line 940 is way too long (106 characters) | ||
| efitools @ 1.9.2 | formatting Look for formatting issues in the source | line 215 is way too long (113 characters) | ||
| android-safe-iop @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 435 is way too long (95 characters) | ||
| android-libutils @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 642 is way too long (114 characters) | ||
| android-libcutils @ 7.1.2_r36 | formatting Look for formatting issues in the source | tabulation on line 277, column 20 | ||
| adb @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| adb @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 385 is way too long (97 characters) | ||
| abc @ 0.0-1.5ae4b97 | formatting Look for formatting issues in the source | line 95 is way too long (95 characters) | ||
| python-openstackdocstheme @ 1.18.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-mox3 @ 0.24.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 297, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 299, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 301, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 303, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 305, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 307, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 309, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 311, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 313, column 18 | ||
| python2-minimal @ 2.7.17 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-minimal @ 3.8.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-debug @ 3.8.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| ijs @ 9.52 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| ghostscript-with-x @ 9.52 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| ghostscript-with-cups @ 9.52 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mesa @ 20.2.4 | formatting Look for formatting issues in the source | line 299 is way too long (120 characters) | ||
| mingw-w64-x86_64-winpthreads @ 8.0.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mingw-w64-x86_64 @ 8.0.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mingw-w64-i686-winpthreads @ 8.0.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mingw-w64-i686 @ 8.0.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| sbcl-circular-streams @ 0.1.0-1.e770bad | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 79 | ||
| ecl-circular-streams @ 0.1.0-1.e770bad | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 79 | ||
| cl-circular-streams @ 0.1.0-1.e770bad | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 79 | ||
| nsis-x86_64 @ 3.05 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| nsis-i686 @ 3.05 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| sbcl-fare-utils @ 1.0.0.5-1.66e9c6f | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ecl-fare-utils @ 1.0.0.5-1.66e9c6f | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| cl-fare-utils @ 1.0.0.5-1.66e9c6f | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| tesseract-ocr @ 4.1.1-1.97079fa | formatting Look for formatting issues in the source | line 121 is way too long (93 characters) | ||
| rust @ 1.26.2 | formatting Look for formatting issues in the source | line 790 is way too long (94 characters) | ||
| rust @ 1.25.0 | formatting Look for formatting issues in the source | line 751 is way too long (91 characters) | ||
| rust @ 1.47.0 | formatting Look for formatting issues in the source | line 1403 is way too long (98 characters) | ||
| rust @ 1.47.0 | formatting Look for formatting issues in the source | line 1409 is way too long (91 characters) | ||
| nextcloud-client @ 3.1.3 | inputs-should-be-native Identify inputs that should be native inputs | 'desktop-file-utils' should probably be a native input | ||
| python-libfreenect @ 0.6.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| libfreenect-opencv @ 0.6.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| libfreenect-examples @ 0.6.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-pygobject @ 2.28.7 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python-pygobject @ 3.34.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| gobject-introspection @ 1.62.0 | inputs-should-be-native Identify inputs that should be native inputs | 'bison' should probably be a native input | ||
| gobject-introspection @ 1.62.0 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| gobject-introspection @ 1.62.0 | patch-file-names Validate file names and availability of patches | gobject-introspection-absolute-shlib-path.patch: file name is too long | ||
| mate-applets @ 1.24.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 917 | ||
| python2-pygobject @ 3.34.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| gexiv2 @ 0.12.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python2-pygobject @ 3.34.0 | formatting Look for formatting issues in the source | line 853 is way too long (97 characters) | ||
| mate-panel @ 1.24.1 | formatting Look for formatting issues in the source | line 671 is way too long (92 characters) | ||
| mate-menus @ 1.24.1 | formatting Look for formatting issues in the source | line 511 is way too long (91 characters) | ||
| mate-polkit @ 1.24.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| atril @ 1.22.0 | formatting Look for formatting issues in the source | line 748 is way too long (92 characters) | ||
| glibc-bootstrap @ 0 | formatting Look for formatting issues in the source | line 653 is way too long (100 characters) | ||
| gcc-bootstrap @ 0 | formatting Look for formatting issues in the source | line 749 is way too long (100 characters) | ||
| zbar @ 0.23 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| docker @ 19.03.15 | formatting Look for formatting issues in the source | line 355 is way too long (95 characters) | ||
| docker @ 19.03.15 | formatting Look for formatting issues in the source | line 391 is way too long (93 characters) | ||
| chez-srfi @ 1.0 | formatting Look for formatting issues in the source | line 289 is way too long (91 characters) | ||
| python-bcj-cffi @ 0.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-setuptools-scm' should probably be a native input | ||
| python-py7zr @ 0.14.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-ppmd-cffi @ 0.3.3 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-multivolumefile @ 0.2.2 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-bcj-cffi @ 0.5.0 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| itcl @ 4.2.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-tempest-lib @ 1.0.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-stevedore @ 3.2.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-reno @ 2.7.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-oslo.log @ 3.36.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-oslo.config @ 5.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-keystoneclient @ 1.8.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| mesa-opencl-icd @ 20.2.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mesa-opencl @ 20.2.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| perl-test-object @ 0.08 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| maven-shared-utils @ 3.2.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@16 and apache-parent-pom@18 collide | ||
| maven-settings-builder @ 3.6.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide | ||
| maven-resolver-provider @ 3.6.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-plugin-api @ 3.6.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide | ||
| java-sonatype-aether-impl @ 1.7 | profile-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 | ||
| wicd @ 1.7.4 | formatting Look for formatting issues in the source | line 109 is way too long (95 characters) | ||
| netpbm @ 10.78.3 | formatting Look for formatting issues in the source | line 86 is way too long (127 characters) | ||
| guile @ 2.0.14 | formatting Look for formatting issues in the source | line 189 is way too long (94 characters) | ||
| guile @ 2.0.14 | formatting Look for formatting issues in the source | line 192 is way too long (93 characters) | ||
| spice-gtk @ 0.37 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| libsigrok @ 0.5.2 | formatting Look for formatting issues in the source | line 216 is way too long (101 characters) | ||
| libsigrok @ 0.5.2 | formatting Look for formatting issues in the source | line 217 is way too long (92 characters) | ||
| python-orange-canvas-core @ 0.1.19 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| libextractor @ 1.11 | formatting Look for formatting issues in the source | line 128 is way too long (140 characters) | ||
| clang-runtime @ 3.5.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| clang-runtime @ 3.5.2 | patch-file-names Validate file names and availability of patches | clang-runtime-3.5-libsanitizer-mode-field.patch: file name is too long | ||
| fcitx-qt5 @ 1.2.6 | inputs-should-be-native Identify inputs that should be native inputs | 'intltool' should probably be a native input | ||
| openmpi @ 4.1.1 | formatting Look for formatting issues in the source | line 276 is way too long (94 characters) | ||
| openmpi @ 4.1.1 | formatting Look for formatting issues in the source | line 278 is way too long (96 characters) | ||
| laminar @ 1.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| laminar @ 1.0 | formatting Look for formatting issues in the source | line 239 is way too long (97 characters) | ||
| laminar @ 1.0 | formatting Look for formatting issues in the source | line 241 is way too long (137 characters) | ||
| blender @ 2.92.0 | formatting Look for formatting issues in the source | line 541 is way too long (97 characters) | ||
| dico @ 2.11 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| busybox @ 1.33.1 | formatting Look for formatting issues in the source | line 93 is way too long (92 characters) | ||
| grantleetheme @ 20.04.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.2-readline @ 2.2.7 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile-readline @ 3.0.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.2-readline @ 2.2.7 | formatting Look for formatting issues in the source | line 432 is way too long (94 characters) | ||
| guile-readline @ 3.0.2 | formatting Look for formatting issues in the source | line 432 is way too long (94 characters) | ||
| mig @ 1.8 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| netdde @ 2.6.32.65-1.4a1016f | derivation Report failure to compile a package to a derivation | failed to create i686-gnu derivation: could not find bootstrap binary 'tar' for system 'i686-gnu' | ||
| hurd @ 0.9-1.91a5167 | derivation Report failure to compile a package to a derivation | failed to create i686-gnu derivation: could not find bootstrap binary 'tar' for system 'i686-gnu' | ||
| gnumach @ 1.8-1.097f9cf | derivation 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' | ||
| python-pytest-click @ 1.0.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| gcompris @ 17.05 | formatting Look for formatting issues in the source | line 136 is way too long (96 characters) | ||
| axoloti-runtime @ 1.0.12-2 | formatting Look for formatting issues in the source | line 197 is way too long (96 characters) | ||
| axoloti-patcher-next @ 2.0.0 | formatting Look for formatting issues in the source | line 415 is way too long (94 characters) | ||
| axoloti-patcher-next @ 2.0.0 | formatting Look for formatting issues in the source | line 561 is way too long (93 characters) | ||
| axoloti-patcher-next @ 2.0.0 | formatting Look for formatting issues in the source | line 574 is way too long (103 characters) | ||
| cryptsetup-static @ 2.3.6 | formatting Look for formatting issues in the source | line 110 is way too long (93 characters) | ||
| python-pep-adapter @ 2.1.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-setuptools-scm' should probably be a native input | ||
| icu4c-build-root @ 66.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| nsis-x86_64 @ 3.05 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 107 | ||
| nsis-i686 @ 3.05 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 107 | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 66 is way too long (115 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 67 is way too long (112 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 81 is way too long (112 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 95 is way too long (92 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 115 is way too long (97 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 119 is way too long (122 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 129 is way too long (114 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 66 is way too long (115 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 67 is way too long (112 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 81 is way too long (112 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 95 is way too long (92 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 115 is way too long (97 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 119 is way too long (122 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 129 is way too long (114 characters) | ||
| rust-avif-serialize @ 0.6.5 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| pjproject-jami @ 2.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| espeak-ng @ 1.50 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| flite @ 2.2 | formatting Look for formatting issues in the source | line 93 is way too long (419 characters) | ||
| boost-python2 @ 1.72.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| irods-client-icommands @ 4.2.8 | formatting Look for formatting issues in the source | line 238 is way too long (91 characters) | ||
| irods @ 4.2.8 | formatting Look for formatting issues in the source | line 104 is way too long (93 characters) | ||
| irods @ 4.2.8 | formatting Look for formatting issues in the source | line 135 is way too long (91 characters) | ||
| font-canada1500 @ 1.101 | formatting Look for formatting issues in the source | line 187 is way too long (91 characters) | ||
| restinio @ 0.6.13 | formatting Look for formatting issues in the source | line 3375 is way too long (105 characters) | ||
| restinio @ 0.6.13 | formatting Look for formatting issues in the source | line 3389 is way too long (95 characters) | ||
| maven-surefire-plugin @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide | ||
| maven-surefire-common @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide | ||
| maven-shared-utils @ 3.1.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@16 and apache-parent-pom@18 collide | ||
| maven-shared-utils @ 3.0.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-shared-io @ 3.0.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@39 collide | ||
| maven-shared-incremental @ 1.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-settings-builder @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide | ||
| maven-resources-plugin @ 3.1.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide | ||
| maven-plugin-api @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide | ||
| maven-model-builder @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide | ||
| maven-model @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide | ||
| maven-jar-plugin @ 3.2.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@39 and apache-commons-parent-pom@41 collide | ||
| maven-install-plugin @ 3.0.0-M1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide | ||
| maven-filtering @ 3.1.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@39 collide | ||
| maven-file-management @ 3.0.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@39 collide | ||
| maven-enforcer-rules @ 3.0.0-M3 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide | ||
| maven-enforcer-plugin @ 3.0.0-M3 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@18 collide | ||
| maven-enforcer-api @ 3.0.0-M3 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-embedder @ 3.6.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide | ||
| maven-dependency-tree @ 3.0.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-compiler-plugin @ 3.8.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-compat @ 3.6.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide | ||
| maven-compat @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide | ||
| maven-common-artifact-filters @ 3.1.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-artifact-transfer @ 0.12.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide | ||
| maven-artifact @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide | ||
| maven-archiver @ 3.5.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@39 and apache-commons-parent-pom@41 collide | ||
| maven-aether-provider @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide | ||
| java-surefire-extensions-api @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide | ||
| java-surefire-common-junit4 @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide | ||
| java-surefire-common-junit3 @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide | ||
| java-surefire-common-java5 @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@16 and apache-parent-pom@21 collide | ||
| java-surefire-booter @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide | ||
| java-surefire-api @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide | ||
| maven-settings-builder @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-settings @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-repository-metadata @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-plugin-api @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-model-builder @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-model @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-enforcer-rules @ 3.0.0-M3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-enforcer-plugin @ 3.0.0-M3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-embedder @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-compat @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-compat @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-artifact @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-aether-provider @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-surefire-plugin @ 3.0.0-M4 | formatting Look for formatting issues in the source | line 3633 is way too long (113 characters) | ||
| maven-surefire-plugin @ 3.0.0-M4 | formatting Look for formatting issues in the source | line 3634 is way too long (111 characters) | ||
| maven-embedder @ 3.6.1 | formatting Look for formatting issues in the source | line 1661 is way too long (110 characters) | ||
| java-surefire-booter @ 3.0.0-M4 | formatting Look for formatting issues in the source | line 3303 is way too long (107 characters) | ||
| icedtea @ 3.7.0 | formatting Look for formatting issues in the source | line 1792 is way too long (109 characters) | ||
| icedtea @ 2.6.13 | formatting Look for formatting issues in the source | line 1279 is way too long (102 characters) | ||
| icedtea @ 2.6.13 | formatting Look for formatting issues in the source | line 1460 is way too long (100 characters) | ||
| python-fpylll @ 0.5.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-fpylll @ 0.5.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| python-fpylll @ 0.5.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| connman @ 1.40 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 146 | ||
| libstdc++-doc @ 9.4.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libstdc++-doc @ 5.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libiberty @ 7.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libgccjit @ 9.4.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gccgo @ 4.9.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gccgo @ 10.3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc++ @ 9.4.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc++ @ 8.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc++ @ 7.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc++ @ 6.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc++ @ 5.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc++ @ 4.9.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc++ @ 4.8.5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc++ @ 10.3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc @ 9.4.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc @ 8.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc @ 7.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc @ 6.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc @ 5.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc @ 4.9.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc @ 4.8.5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc @ 10.3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libreoffice @ 7.1.4.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python-faiss @ 1.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'swig' should probably be a native input | ||
| perl-file-which @ 1.23 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| perl-file-readbackwards @ 1.06 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 47 | ||
| perl-digest-sha @ 6.02 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 82 | ||
| perl-devel-globaldestruction @ 0.14 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| perl-class-load @ 0.25 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| perl-glib-object-introspection @ 0.049 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| perl-extutils-pkgconfig @ 1.16 | inputs-should-be-native Identify inputs that should be native inputs | 'pkg-config' should probably be a native input | ||
| cairo-xcb @ 1.16.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| telepathy-glib @ 0.24.1 | formatting Look for formatting issues in the source | line 952 is way too long (92 characters) | ||
| guile-static-stripped-tarball @ 3.0.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile-static-stripped @ 3.0.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-sphinxcontrib-programoutput @ 0.15 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-sphinx' should probably be a native input | ||
| python2-sphinx-repoze-autointerface @ 0.8 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-sphinx' should probably be a native input | ||
| python2-sphinx @ 1.7.7 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-docutils' should probably be a native input | ||
| python-sphinxcontrib-svg2pdfconverter @ 1.0.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinxcontrib-programoutput @ 0.15 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinxcontrib-newsfeed @ 0.1.4 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinxcontrib-github-alt @ 1.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-sphinxcontrib-github-alt @ 1.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx-repoze-autointerface @ 0.8 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx-copybutton @ 0.2.6 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx @ 3.3.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-sphinx-copybutton @ 0.2.6 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| nettle @ 3.5.1 | patch-file-names Validate file names and availability of patches | nettle-3.5-check-_pkcs1_sec_decrypt-msg-len.patch: file name is too long | ||
| cups-minimal @ 2.3.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-jbzip2 @ 0.9.1 | formatting Look for formatting issues in the source | line 280 is way too long (92 characters) | ||
| rust-winit @ 0.24.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| rust-winit @ 0.20.0-alpha6 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| rust-winit @ 0.19.5 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| rust-winit @ 0.20.0-alpha6 | formatting Look for formatting issues in the source | line 2914 is way too long (114 characters) | ||
| guile-stis-parser @ 1.2.4.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 117 | ||
| texlive-lm @ 51265 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 93 | ||
| texlive-libkpathsea @ 20190410 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| texlive-latex-cyrillic @ 51265 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 166 | ||
| texlive-hyphen-occitan @ 51265 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| texlive-hyphen-latin @ 51265 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| texlive-fonts-latex @ 51265 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 78 | ||
| texlive-latex-hyperref @ 6.84a2 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| texlive-libkpathsea @ 20190410 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| texlive-ruhyphen @ 51265 | formatting Look for formatting issues in the source | line 2553 is way too long (92 characters) | ||
| texlive-ruhyphen @ 51265 | formatting Look for formatting issues in the source | line 2556 is way too long (93 characters) | ||
| texlive-latex-base @ 51265 | formatting Look for formatting issues in the source | tabulation on line 2664, column 22 | ||
| texlive-hyph-utf8 @ 51265 | formatting Look for formatting issues in the source | line 2375 is way too long (108 characters) | ||
| texlive-hyph-utf8 @ 51265 | formatting Look for formatting issues in the source | line 2376 is way too long (108 characters) | ||
| texlive-hyph-utf8 @ 51265 | formatting Look for formatting issues in the source | line 2377 is way too long (95 characters) | ||
| texlive-amsfonts @ 51265 | formatting Look for formatting issues in the source | line 1338 is way too long (94 characters) | ||
| texlive-amsfonts @ 51265 | formatting Look for formatting issues in the source | line 1364 is way too long (93 characters) | ||
| texlive-amsfonts @ 51265 | formatting Look for formatting issues in the source | line 1366 is way too long (91 characters) | ||
| jucipp @ 1.6.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| openfoam @ 4.1 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| openfoam @ 4.1 | formatting Look for formatting issues in the source | line 135 is way too long (109 characters) | ||
| openfoam @ 4.1 | formatting Look for formatting issues in the source | line 149 is way too long (91 characters) | ||
| tmux-themepack @ 1.1.0 | formatting Look for formatting issues in the source | line 94 is way too long (95 characters) | ||
| xkbprint @ 1.0.5 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| zathura-pdf-poppler @ 0.3.0 | formatting Look for formatting issues in the source | line 577 is way too long (107 characters) | ||
| zathura-djvu @ 0.2.9 | formatting Look for formatting issues in the source | line 491 is way too long (93 characters) | ||
| catdoc @ 0.95 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 157 | ||
| opencc @ 1.1.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| emacs-cmake-mode @ 3.21.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| grub-minimal @ 2.06 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| grub-hybrid @ 2.06 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| grub-efi @ 2.06 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| netcdf-parallel-openmpi @ 4.7.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| hdf5-parallel-openmpi @ 1.10.7 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| hdf4-alt @ 4.2.14 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| dsfmt @ 2.2.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| scalapack @ 2.0.2 | formatting Look for formatting issues in the source | tabulation on line 983, column 0 | ||
| nomad-optimizer @ 4.1.0 | formatting Look for formatting issues in the source | line 1918 is way too long (92 characters) | ||
| hdf-java @ 3.3.2 | formatting Look for formatting issues in the source | line 1393 is way too long (92 characters) | ||
| clapack @ 3.2.1 | formatting Look for formatting issues in the source | line 945 is way too long (91 characters) | ||
| btanks @ 0.9.8083 | formatting Look for formatting issues in the source | line 8649 is way too long (99 characters) | ||
| btanks @ 0.9.8083 | formatting Look for formatting issues in the source | tabulation on line 8674, column 18 | ||
| btanks @ 0.9.8083 | formatting Look for formatting issues in the source | tabulation on line 8675, column 17 | ||
| ruby-iruby @ 0.3 | formatting Look for formatting issues in the source | line 501 is way too long (112 characters) | ||
| omnitux @ 1.2.1 | formatting Look for formatting issues in the source | line 620 is way too long (99 characters) | ||
| childsplay @ 3.4 | formatting Look for formatting issues in the source | line 529 is way too long (92 characters) | ||
| emacs-geiser-racket @ 0.16 | formatting Look for formatting issues in the source | tabulation on line 400, column 0 | ||
| template-glib @ 3.34.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| appstream-glib @ 0.7.18 | formatting Look for formatting issues in the source | line 1118 is way too long (93 characters) | ||
| python-pytools @ 2021.2.7 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| kdelibs4support @ 5.70.0 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| kconfigwidgets @ 5.70.0 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| plasma-framework @ 5.70.1 | patch-file-names Validate file names and availability of patches | plasma-framework-fix-KF5PlasmaMacros.cmake.patch: file name is too long | ||
| plasma-framework @ 5.70.1 | formatting Look for formatting issues in the source | line 3431 is way too long (93 characters) | ||
| kpackage @ 5.70.0 | formatting Look for formatting issues in the source | line 1963 is way too long (106 characters) | ||
| kio @ 5.70.1 | formatting Look for formatting issues in the source | line 2802 is way too long (113 characters) | ||
| kimageformats @ 5.70.0 | formatting Look for formatting issues in the source | line 1825 is way too long (103 characters) | ||
| kdbusaddons @ 5.70.0 | formatting Look for formatting issues in the source | line 655 is way too long (107 characters) | ||
| kcmutils @ 5.70.0 | formatting Look for formatting issues in the source | line 2274 is way too long (113 characters) | ||
| extra-cmake-modules @ 5.70.0 | formatting Look for formatting issues in the source | line 120 is way too long (91 characters) | ||
| wine64-staging @ 6.6 | inputs-should-be-native Identify inputs that should be native inputs | 'autoconf' should probably be a native input | ||
| wine-staging @ 6.6 | inputs-should-be-native Identify inputs that should be native inputs | 'autoconf' should probably be a native input | ||
| wine64-staging @ 6.6 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| wine-staging @ 6.6 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| python-nbclient @ 0.5.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 62 | ||
| python-jupyterlab-widgets @ 1.0.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-voila @ 0.2.10 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-nbclient @ 0.5.3 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-pip' should probably not be an input at all | ||
| python-nbclient @ 0.5.3 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-jupyterlab-widgets @ 1.0.0 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-jupyter-packaging @ 0.9.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| qtwebglplugin @ 5.15.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 41 | ||
| qtdatavis3d @ 5.15.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 107, 250 | ||
| qtcharts @ 5.15.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 244 | ||
| qwt @ 6.1.5 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| python-pyqt-without-qtwebkit @ 5.15.2 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| python-pyqt @ 5.15.2 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| python-pyqt-without-qtwebkit @ 5.15.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-pyqt @ 5.15.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| qtserialport @ 5.15.2 | formatting Look for formatting issues in the source | line 1101 is way too long (115 characters) | ||
| qtsensors @ 5.15.2 | formatting Look for formatting issues in the source | line 964 is way too long (97 characters) | ||
| qtremoteobjects @ 5.15.2 | formatting Look for formatting issues in the source | line 1525 is way too long (94 characters) | ||
| qtmultimedia @ 5.15.2 | formatting Look for formatting issues in the source | line 1004 is way too long (96 characters) | ||
| qtbase @ 5.15.2 | formatting Look for formatting issues in the source | line 444 is way too long (96 characters) | ||
| qtbase @ 5.15.2 | formatting Look for formatting issues in the source | line 522 is way too long (97 characters) | ||
| qtbase @ 5.15.2 | formatting Look for formatting issues in the source | line 527 is way too long (94 characters) | ||
| qtbase @ 5.15.2 | formatting Look for formatting issues in the source | line 529 is way too long (94 characters) | ||
| python-pyqt @ 5.15.2 | formatting Look for formatting issues in the source | line 2151 is way too long (105 characters) | ||
| verilator @ 4.204 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| xorg-server-xwayland @ 1.20.11 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| xproto @ 7.0.31 | formatting Look for formatting issues in the source | line 5009 is way too long (91 characters) | ||
| xdg-user-dirs @ 0.17 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 116 | ||
| python-cchardet @ 2.1.7 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| telepathy-mission-control @ 5.16.5 | inputs-should-be-native Identify inputs that should be native inputs | 'gtk-doc' should probably be a native input | ||
| malcontent @ 0.8.0 | formatting Look for formatting issues in the source | line 357 is way too long (91 characters) | ||
| localed @ 241 | formatting Look for formatting issues in the source | line 820 is way too long (96 characters) | ||
| help2man @ 1.47.13 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| rocm-bandwidth-test @ 4.3.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 122 | ||
| clang-runtime @ 3.9.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| clang-runtime @ 3.9.1 | patch-file-names Validate file names and availability of patches | clang-runtime-3.9-libsanitizer-mode-field.patch: file name is too long | ||
| clang-runtime @ 3.8.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| clang-runtime @ 3.8.1 | patch-file-names Validate file names and availability of patches | clang-runtime-3.8-libsanitizer-mode-field.patch: file name is too long | ||
| clang-runtime @ 3.7.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| clang-runtime @ 3.7.1 | patch-file-names Validate file names and availability of patches | clang-runtime-3.8-libsanitizer-mode-field.patch: file name is too long | ||
| clang @ 9.0.1 | formatting Look for formatting issues in the source | line 370 is way too long (91 characters) | ||
| clang @ 8.0.0 | formatting Look for formatting issues in the source | line 370 is way too long (91 characters) | ||
| clang @ 7.1.0 | formatting Look for formatting issues in the source | line 370 is way too long (91 characters) | ||
| clang @ 6.0.1 | formatting Look for formatting issues in the source | line 370 is way too long (91 characters) | ||
| clang @ 3.9.1 | formatting Look for formatting issues in the source | line 370 is way too long (91 characters) | ||
| clang @ 3.8.1 | formatting Look for formatting issues in the source | line 370 is way too long (91 characters) | ||
| clang @ 3.7.1 | formatting Look for formatting issues in the source | line 370 is way too long (91 characters) | ||
| clang @ 3.5.2 | formatting Look for formatting issues in the source | line 370 is way too long (91 characters) | ||
| clang @ 11.0.0 | formatting Look for formatting issues in the source | line 370 is way too long (91 characters) | ||
| clang @ 10.0.0 | formatting Look for formatting issues in the source | line 370 is way too long (91 characters) | ||
| perl-libxml @ 0.08 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| java-xpp3 @ 1.1.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 188 | ||
| java-mxparser @ 1.2.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 188, 473 | ||
| java-kxml2 @ 2.4.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-libxml2 @ 2.9.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| xmlrpc-c @ 1.43.08 | formatting Look for formatting issues in the source | line 2376 is way too long (91 characters) | ||
| java-xom @ 127 | formatting Look for formatting issues in the source | trailing white space on line 1927 | ||
| java-xmlpull-api-v1 @ 1.1.3.4b | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| xfce4-clipman-plugin @ 1.6.2 | formatting Look for formatting issues in the source | line 504 is way too long (91 characters) | ||
| tumbler @ 4.16.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| patchwork @ 3.0.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| ghc @ 8.6.5 | formatting Look for formatting issues in the source | line 593 is way too long (91 characters) | ||
| rtl-sdr @ 0.6.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| libmediaart @ 1.9.5 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python-pymol @ 2.5.0 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| emacs-erlang @ 24.0.5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| zeitgeist @ 1.0.3 | formatting Look for formatting issues in the source | tabulation on line 757, column 18 | ||
| zeitgeist @ 1.0.3 | formatting Look for formatting issues in the source | tabulation on line 760, column 18 | ||
| js-filesaver @ 1.3.8 | formatting Look for formatting issues in the source | line 533 is way too long (99 characters) | ||
| gnome-initial-setup @ 3.32.1 | formatting Look for formatting issues in the source | line 1474 is way too long (91 characters) | ||
| clang @ 12.0.1 | formatting Look for formatting issues in the source | line 370 is way too long (91 characters) | ||
| python2 @ 2.7.17 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-next @ 3.9.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mesa-headers @ 20.2.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2 @ 2.7.17 | formatting Look for formatting issues in the source | line 181 is way too long (99 characters) | ||
| python2 @ 2.7.17 | formatting Look for formatting issues in the source | line 290 is way too long (98 characters) | ||
| python @ 3.8.2 | formatting Look for formatting issues in the source | line 481 is way too long (93 characters) | ||
| thunar @ 4.16.10 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python-coveralls @ 3.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-coverage' should probably be a native input | ||
| texlive-latex-l3packages @ 51265 | formatting Look for formatting issues in the source | line 3214 is way too long (91 characters) | ||
| texlive-latex-l3packages @ 51265 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| python2-cryptography @ 3.3.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-asn1crypto @ 1.4.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-cryptography @ 3.3.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-asn1crypto @ 1.4.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-keyring @ 22.0.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python2-pycrypto @ 2.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| hackrf @ 2021.03.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| gtk+ @ 3.24.24 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gtk+ @ 2.24.32 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gdk-pixbuf+svg @ 2.40.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gtk+ @ 2.24.32 | formatting Look for formatting issues in the source | tabulation on line 844, column 0 | ||
| gtk+ @ 2.24.32 | formatting Look for formatting issues in the source | tabulation on line 845, column 0 | ||
| gtk+ @ 2.24.32 | formatting Look for formatting issues in the source | tabulation on line 846, column 0 | ||
| at-spi2-core @ 2.34.0 | formatting Look for formatting issues in the source | line 690 is way too long (97 characters) | ||
| xpra @ 4.2.2 | formatting Look for formatting issues in the source | tabulation on line 6379, column 0 | ||
| gramps @ 5.1.4 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| cawbird @ 1.4.2 | formatting Look for formatting issues in the source | line 86 is way too long (104 characters) | ||
| lxqt @ 17.0 | inputs-should-be-native Identify inputs that should be native inputs | 'desktop-file-utils' should probably be a native input | ||
| lxqt-session @ 0.17.1 | formatting Look for formatting issues in the source | line 871 is way too long (92 characters) | ||
| lxqt-session @ 0.17.1 | formatting Look for formatting issues in the source | line 878 is way too long (100 characters) | ||
| lxqt-session @ 0.17.1 | formatting Look for formatting issues in the source | line 896 is way too long (98 characters) | ||
| xfce4-volumed-pulse @ 0.2.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 65, 112 | ||
| config @ 0.0.0-1.c8ddc84 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| libtool @ 2.4.6 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| pyconfigure @ 0.2.3 | formatting Look for formatting issues in the source | line 631 is way too long (92 characters) | ||
| adcli @ 0.9.1 | formatting Look for formatting issues in the source | line 87 is way too long (95 characters) | ||
| tuxmath @ 2.0.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ruby-rb-inotify @ 0.9.10 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-th-reify-many @ 0.1.10 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-tasty-expected-failure @ 0.12.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 185 | ||
| ghc-doctest-lib @ 0.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 35 | ||
| ruby-tzinfo-data @ 1.2021.1 | formatting Look for formatting issues in the source | line 5862 is way too long (101 characters) | ||
| ruby-tzinfo-data @ 1.2021.1 | formatting Look for formatting issues in the source | line 5863 is way too long (107 characters) | ||
| ruby-asciidoctor-pdf @ 1.5.3-1.d257440 | formatting Look for formatting issues in the source | line 1888 is way too long (99 characters) | ||
| idris @ 1.3.3 | formatting Look for formatting issues in the source | line 105 is way too long (100 characters) | ||
| ghc-th-orphans @ 0.13.12 | formatting Look for formatting issues in the source | line 13466 is way too long (92 characters) | ||
| ghc-optparse-applicative @ 0.15.1.0 | formatting Look for formatting issues in the source | line 178 is way too long (95 characters) | ||
| ghc-doctest-exitcode-stdio @ 0.0 | formatting Look for formatting issues in the source | line 1168 is way too long (99 characters) | ||
| elm-compiler @ 0.19.0 | formatting Look for formatting issues in the source | line 58 is way too long (97 characters) | ||
| ppsspp @ 1.11.3-1.69fa207 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| mrrescue @ 1.02e | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 2 | ||
| fifengine @ 0.4.2 | inputs-should-be-native Identify inputs that should be native inputs | 'swig' should probably be a native input | ||
| freedink-engine @ 109.6 | formatting Look for formatting issues in the source | tabulation on line 3339, column 0 | ||
| freedink-engine @ 109.6 | formatting Look for formatting issues in the source | tabulation on line 3340, column 0 | ||
| freedink-engine @ 109.6 | formatting Look for formatting issues in the source | tabulation on line 3341, column 0 | ||
| freedink-engine @ 109.6 | formatting Look for formatting issues in the source | tabulation on line 3342, column 0 | ||
| freedink-engine @ 109.6 | formatting Look for formatting issues in the source | tabulation on line 3343, column 0 | ||
| cc65 @ 2.19 | formatting Look for formatting issues in the source | line 2546 is way too long (167 characters) | ||
| ghc @ 8.10.7 | formatting Look for formatting issues in the source | line 719 is way too long (93 characters) | ||
| ghc-template-haskell @ 2.16.0.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 111 | ||
| ghc-template-haskell-compat-v0208 @ 0.1.6 | formatting Look for formatting issues in the source | line 16143 is way too long (111 characters) | ||
| ghc-indexed-traversable @ 0.1.1 | formatting Look for formatting issues in the source | line 15483 is way too long (91 characters) | ||
| geany @ 1.38 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| libmypaint @ 1.6.1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| gimp-resynthesizer @ 2.0.3 | formatting Look for formatting issues in the source | line 526 is way too long (107 characters) | ||
| owncloud-client @ 2.9.0.5150 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libdqlite @ 1.9.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| openjpeg-data @ 2020.05.19 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 116 | ||
| libjxr @ 1.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 99 | ||
| libjxr @ 1.1 | formatting Look for formatting issues in the source | line 525 is way too long (95 characters) | ||
| cloudflare-cli @ 0.0.0-1.2d986d3 | formatting Look for formatting issues in the source | line 122 is way too long (92 characters) | ||
| libvirt-glib @ 4.0.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| virt-manager @ 3.2.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| libosinfo @ 1.7.1 | formatting Look for formatting issues in the source | line 1046 is way too long (106 characters) | ||
| dmraid @ 1.0.0.rc16-3 | formatting Look for formatting issues in the source | line 887 is way too long (91 characters) | ||
| elixir @ 1.12.3 | formatting Look for formatting issues in the source | line 76 is way too long (97 characters) | ||
| elixir @ 1.12.3 | formatting Look for formatting issues in the source | line 77 is way too long (99 characters) | ||
| minetest-basic-trains @ 1.0.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| gtklick @ 0.6.4 | formatting Look for formatting issues in the source | line 1304 is way too long (94 characters) | ||
| system-config-printer @ 1.5.15 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| libpeas @ 1.28.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| gnome-contacts @ 3.34 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| librsvg @ 2.50.3 | formatting Look for formatting issues in the source | line 3504 is way too long (104 characters) | ||
| gnome-keyring @ 3.34.0 | formatting Look for formatting issues in the source | line 2541 is way too long (91 characters) | ||
| glade @ 3.36.0 | formatting Look for formatting issues in the source | line 3204 is way too long (91 characters) | ||
| dejagnu @ 1.6.2 | formatting Look for formatting issues in the source | line 60 is way too long (91 characters) | ||
| docbook2x @ 0.8.8 | inputs-should-be-native Identify inputs that should be native inputs | 'texinfo' should probably be a native input | ||
| xen @ 4.14.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| python-pytest-csv @ 3.0.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| mia @ 2.4.6 | inputs-should-be-native Identify inputs that should be native inputs | 'doxygen' should probably be a native input | ||
| vtk @ 9.0.1 | formatting Look for formatting issues in the source | line 301 is way too long (93 characters) | ||
| vtk @ 9.0.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| opencv @ 3.4.3 | formatting Look for formatting issues in the source | line 515 is way too long (132 characters) | ||
| trytond-timesheet @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-stock-split @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-stock-package @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-stock-lot-unit @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-stock-location-move @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-sale-promotion @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-sale-extra @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-production-work-timesheet @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-production-work @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-production-split @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-production-outsourcing @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-party-relationship @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-notification-email @ 6.0.1 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-ldap-authentication @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-customs @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-commission-waiting @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-commission @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-analytic-sale @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-analytic-purchase @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-analytic-invoice @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-account-tax-cash @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-account-stock-landed-cost @ 6.0.1 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-account-statement @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-account-payment-sepa @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-account-payment-clearing @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-account-invoice-line-standalone @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-account-invoice-defer @ 6.0.0 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-account-es @ 6.0.2 | description Validate package descriptions | description contains typo 'allows to' | ||
| trytond-account-deposit @ 6.0.1 | description Validate package descriptions | description contains typo 'allows to' | ||
| udiskie @ 2.3.3 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| guile2.2-gnutls @ 3.6.15 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.0-gnutls @ 3.6.15 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gnutls-dane @ 3.6.15 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.2-gnutls @ 3.6.16 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.0-gnutls @ 3.6.16 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gnutls-dane @ 3.6.16 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| plymouth @ 0.9.5 | formatting Look for formatting issues in the source | line 2099 is way too long (91 characters) | ||
| libportal @ 0.4 | formatting Look for formatting issues in the source | line 2265 is way too long (93 characters) | ||
| openexr @ 2.5.7 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-paste @ 3.0.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| tor @ 0.4.6.8 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 574 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 327, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 329, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 332, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 333, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 342, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 343, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 344, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 345, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 346, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 347, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 348, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 350, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 351, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 352, column 0 | ||
| texlive-fonts-lm @ 51265 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 93 | ||
| iml @ 1.0.5 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 798 | ||
| python-onnx @ 1.9.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| perl-parent @ 5.30.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| perl-base @ 5.30.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linphoneqt @ 4.2.5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.2-gdbm-ffi @ 20120209.fa1d5b6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.0-gdbm-ffi @ 20120209.fa1d5b6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| symmetrica @ 2.0 | formatting Look for formatting issues in the source | line 1490 is way too long (100 characters) | ||
| libtomcrypt @ 1.18.2 | formatting Look for formatting issues in the source | line 365 is way too long (100 characters) | ||
| gmp @ 6.2.0 | formatting Look for formatting issues in the source | line 83 is way too long (96 characters) | ||
| gap @ 4.11.0 | formatting Look for formatting issues in the source | line 1212 is way too long (98 characters) | ||
| eigen @ 3.3.8 | formatting Look for formatting issues in the source | tabulation on line 1056, column 0 | ||
| perl-search-xapian @ 1.2.25.4 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| recoll @ 1.31.2 | inputs-should-be-native Identify inputs that should be native inputs | 'groff' should probably be a native input | ||
| libsecp256k1 @ 20200615-1.dbd41db | formatting Look for formatting issues in the source | line 1110 is way too long (103 characters) | ||
| qemu-minimal @ 6.1.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| yelp-xsl @ 3.34.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 300 | ||
| yelp-tools @ 3.32.2 | inputs-should-be-native Identify inputs that should be native inputs | 'itstool' should probably be a native input | ||
| libgee @ 0.20.3 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| libchamplain @ 0.12.16 | inputs-should-be-native Identify inputs that should be native inputs | 'glib:bin' should probably be a native input | ||
| gnome-tweaks @ 3.34.1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| gnome @ 3.34.5 | inputs-should-be-native Identify inputs that should be native inputs | 'desktop-file-utils' should probably be a native input | ||
| gjs @ 1.58.3 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| geoclue @ 2.5.7 | inputs-should-be-native Identify inputs that should be native inputs | 'glib:bin' should probably be a native input | ||
| eolie @ 0.9.101 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| d-feet @ 0.3.14 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| tigervnc-server @ 1.11.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| upower @ 0.99.12 | formatting Look for formatting issues in the source | line 5366 is way too long (103 characters) | ||
| tigervnc-server @ 1.11.0 | formatting Look for formatting issues in the source | line 284 is way too long (102 characters) | ||
| tigervnc-server @ 1.11.0 | formatting Look for formatting issues in the source | line 287 is way too long (102 characters) | ||
| tigervnc-server @ 1.11.0 | formatting Look for formatting issues in the source | tabulation on line 296, column 0 | ||
| libsoup @ 2.72.0 | formatting Look for formatting issues in the source | line 4817 is way too long (128 characters) | ||
| libsoup @ 2.72.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| gdm @ 3.34.1 | formatting Look for formatting issues in the source | line 8231 is way too long (103 characters) | ||
| vim-full @ 8.2.3487 | formatting Look for formatting issues in the source | line 234 is way too long (98 characters) | ||
| ghc-tasty-silver @ 3.2.3 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ghc-operational @ 0.2.4.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 71 | ||
| ghc-llvm-hs-pure @ 9.0.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-llvm-hs @ 9.0.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-inline-c @ 0.9.1.5 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-hxt-unicode @ 9.0.2.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 158 | ||
| ghc-hsyaml @ 0.2.1.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ghc-gtk2hs-buildtools @ 0.13.8.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 95, 367 | ||
| ghc-fsnotify @ 0.3.0.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 81 | ||
| ghc-doclayout @ 0.3.1.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-aeson-qq @ 0.8.4 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-monad-par @ 0.3.5 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| ghc-language-javascript @ 0.7.1.0 | formatting Look for formatting issues in the source | line 1961 is way too long (91 characters) | ||
| ghc-hxt-unicode @ 9.0.2.4 | formatting Look for formatting issues in the source | line 1506 is way too long (91 characters) | ||
| ghc-base-unicode-symbols @ 0.2.4.2 | formatting Look for formatting issues in the source | line 967 is way too long (93 characters) | ||
| ghc-base-unicode-symbols @ 0.2.4.2 | formatting Look for formatting issues in the source | line 981 is way too long (101 characters) | ||
| astroid @ 0.16 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| purescript @ 0.14.5 | formatting Look for formatting issues in the source | line 99 is way too long (100 characters) | ||
| purescript @ 0.14.5 | formatting Look for formatting issues in the source | trailing white space on line 105 | ||
| purescript @ 0.14.5 | formatting Look for formatting issues in the source | line 121 is way too long (92 characters) | ||
| ghc-unsafe @ 0.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ghc-rio @ 0.1.21.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ghc-regex-tdfa @ 1.3.1.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 139 | ||
| ghc-mysql @ 0.2.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ghc-commonmark @ 0.2.1.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 630 | ||
| libblockdev @ 2.26 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| ghc-xdg-basedir @ 0.2.2 | formatting Look for formatting issues in the source | line 15204 is way too long (93 characters) | ||
| ghc-vector @ 0.12.3.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| ghc-persistent-postgresql @ 2.13.2.1 | formatting Look for formatting issues in the source | line 16465 is way too long (95 characters) | ||
| ghc-hspec-expectations-lifted @ 0.10.0 | formatting Look for formatting issues in the source | line 16343 is way too long (103 characters) | ||
| ghc-commonmark-extensions @ 0.2.2 | formatting Look for formatting issues in the source | line 15906 is way too long (95 characters) | ||
| rapicorn @ 16.0.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-cython' should probably be a native input | ||
| ctl @ 1.5.2 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| cockatrice @ 2.8.0 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| zita-resampler @ 1.6.2 | formatting Look for formatting issues in the source | line 3977 is way too long (93 characters) | ||
| vamp @ 2.6 | formatting Look for formatting issues in the source | line 3435 is way too long (94 characters) | ||
| crawl-tiles @ 0.27.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| rust-nu-plugin-query-json @ 0.36.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| nushell @ 0.36.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| guile-zstd @ 0.1.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ecasound @ 2.9.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471 | ||
| gtkspell3 @ 3.0.10 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| conda @ 4.10.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python2-pygpgme @ 0.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-pygpgme @ 0.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.2-rsvg @ 2.18.1-0.05c6a2f | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.2-present @ 0.3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| boost-static @ 1.72.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| boost-mpi @ 1.72.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| volctl @ 0.8.2 | formatting Look for formatting issues in the source | line 2468 is way too long (98 characters) | ||
| spiped @ 1.6.1 | formatting Look for formatting issues in the source | line 2663 is way too long (94 characters) | ||
| mbedtls-apache @ 2.26.0 | formatting Look for formatting issues in the source | line 996 is way too long (96 characters) | ||
| guile-for-guile-emacs @ 2.1.2-1.15ca784 | formatting Look for formatting issues in the source | line 511 is way too long (96 characters) | ||
| guile-for-guile-emacs @ 2.1.2-1.15ca784 | formatting Look for formatting issues in the source | trailing white space on line 515 | ||
| fcitx5-gtk @ 5.0.9 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| glibc-locales-2.29 @ 2.29 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| glibc-locales @ 2.31 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| glibc-hurd-headers @ 2.31 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| coreutils-minimal @ 8.32 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| binutils-gold @ 2.34 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| glibc @ 2.31 | formatting Look for formatting issues in the source | line 844 is way too long (98 characters) | ||
| fstrcmp @ 0.7.D001 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 236 | ||
| lua5.2-lgi @ 0.9.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| lua5.1-lgi @ 0.9.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| lua-lgi @ 0.9.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| kodi-wayland @ 18.8 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| lua-tablepool @ 0.01 | formatting Look for formatting issues in the source | line 1063 is way too long (100 characters) | ||
| lua-resty-signal @ 0.02 | formatting Look for formatting issues in the source | line 1028 is way too long (104 characters) | ||
| lua-resty-signal @ 0.02 | formatting Look for formatting issues in the source | line 1029 is way too long (93 characters) | ||
| lua-resty-signal @ 0.02 | formatting Look for formatting issues in the source | line 1030 is way too long (123 characters) | ||
| lua-resty-signal @ 0.02 | formatting Look for formatting issues in the source | line 1031 is way too long (112 characters) | ||
| lua-resty-shell @ 0.03 | formatting Look for formatting issues in the source | line 1095 is way too long (100 characters) | ||
| lua-resty-shell @ 0.03 | formatting Look for formatting issues in the source | line 1097 is way too long (119 characters) | ||
| lua-resty-shell @ 0.03 | formatting Look for formatting issues in the source | line 1098 is way too long (108 characters) | ||
| lua-resty-lrucache @ 0.10 | formatting Look for formatting issues in the source | line 988 is way too long (100 characters) | ||
| lua-resty-lrucache @ 0.10 | formatting Look for formatting issues in the source | line 990 is way too long (119 characters) | ||
| lua-resty-lrucache @ 0.10 | formatting Look for formatting issues in the source | line 991 is way too long (108 characters) | ||
| lua-resty-core @ 0.1.18 | formatting Look for formatting issues in the source | line 953 is way too long (95 characters) | ||
| emilua @ 0.3.2 | formatting Look for formatting issues in the source | line 1152 is way too long (98 characters) | ||
| libchop @ 0.5.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 262, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 263, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 264, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 265, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 266, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 267, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 268, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 269, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 270, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 273, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 274, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 276, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 277, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 278, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 279, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 280, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 282, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 283, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 284, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 285, column 0 | ||
| ghc-quickcheck-classes-base @ 0.6.2.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ghc-quickcheck-classes-base @ 0.6.2.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 109, 318, 450, 544 | ||
| sonata @ 1.7.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| ghc-quickcheck-classes-base @ 0.6.2.0 | formatting Look for formatting issues in the source | line 1107 is way too long (101 characters) | ||
| xwallpaper @ 0.7.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 72 | ||
| xftwidth @ 20170402 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 96, 234 | ||
| wlsunset @ 0.2.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| xftwidth @ 20170402 | formatting Look for formatting issues in the source | tabulation on line 1902, column 0 | ||
| xftwidth @ 20170402 | formatting Look for formatting issues in the source | tabulation on line 1903, column 0 | ||
| xftwidth @ 20170402 | formatting Look for formatting issues in the source | tabulation on line 1905, column 0 | ||
| xftwidth @ 20170402 | formatting Look for formatting issues in the source | tabulation on line 1906, column 0 | ||
| sooperlooper @ 1.7.6 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 120 | ||
| python2-discogs-client @ 2.3.12 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 70 | ||
| python-discogs-client @ 2.3.12 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 70 | ||
| drumstick @ 2.3.1 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| sorcer @ 1.1.3 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| python-pyportmidi @ 217 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| vmpk @ 0.8.4 | formatting Look for formatting issues in the source | line 3063 is way too long (91 characters) | ||
| solfege @ 3.22.2 | formatting Look for formatting issues in the source | line 2084 is way too long (92 characters) | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5738, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5739, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5740, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5741, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5743, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5750, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5751, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5752, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5753, column 0 | ||
| drumstick @ 2.3.1 | formatting Look for formatting issues in the source | line 3016 is way too long (91 characters) | ||
| texlive-fonts-iwona @ 0.995b | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 42 | ||
| python-distributed @ 2021.09.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| texlive-latex-pgf @ 51265 | formatting Look for formatting issues in the source | line 6993 is way too long (98 characters) | ||
| texlive-context @ 51265 | formatting Look for formatting issues in the source | trailing white space on line 7360 | ||
| python-distributed @ 2021.09.1 | formatting Look for formatting issues in the source | line 951 is way too long (104 characters) | ||
| python-clang @ 12.0.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-clang @ 11.0.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-clang @ 10.0.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| ocaml-llvm @ 9.0.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-clang-rename @ 9.0.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-clang-format @ 9.0.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| julia-openspecfun-jll @ 0.5.3+4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 129 | ||
| julia-compilersupportlibraries-jll @ 0.4.0+1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 134 | ||
| julia-xorg-xcb-util-renderutil-jll @ 0.3.9+1 | formatting Look for formatting issues in the source | line 2469 is way too long (93 characters) | ||
| julia-libuuid-jll @ 2.36.0+0 | formatting Look for formatting issues in the source | line 1235 is way too long (92 characters) | ||
| julia-compilersupportlibraries-jll @ 0.4.0+1 | formatting Look for formatting issues in the source | line 157 is way too long (91 characters) | ||
| abseil-cpp @ 20200923.3 | formatting Look for formatting issues in the source | line 787 is way too long (116 characters) | ||
| abseil-cpp @ 20200923.3 | formatting Look for formatting issues in the source | line 788 is way too long (144 characters) | ||
| julia @ 1.6.3 | formatting Look for formatting issues in the source | line 376 is way too long (107 characters) | ||
| julia @ 1.6.3 | formatting Look for formatting issues in the source | line 378 is way too long (106 characters) | ||
| julia @ 1.6.3 | formatting Look for formatting issues in the source | line 575 is way too long (101 characters) | ||
| julia @ 1.6.3 | formatting Look for formatting issues in the source | line 580 is way too long (124 characters) | ||
| font-adobe-source-code-pro @ 2.032R-ro-1.052R-it-1.012R-VAR | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| perl-specio @ 0.38 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 185, 314 | ||
| cgit @ 1.2.3 | inputs-should-be-native Identify inputs that should be native inputs | 'groff' should probably be a native input | ||
| cgit @ 1.2.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| perl-sys-cpu @ 0.61 | formatting Look for formatting issues in the source | line 9754 is way too long (97 characters) | ||
| git-crypt @ 0.6.0 | formatting Look for formatting issues in the source | line 886 is way too long (91 characters) | ||
| bazaar @ 2.7.0 | formatting Look for formatting issues in the source | line 169 is way too long (93 characters) | ||
| b4 @ 0.6.2 | formatting Look for formatting issues in the source | line 2583 is way too long (93 characters) | ||
| b4 @ 0.6.2 | formatting Look for formatting issues in the source | line 2584 is way too long (112 characters) | ||
| xygrib @ 1.2.6.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 256 | ||
| osm-gps-map @ 1.1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python-fiona @ 1.8.20 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| tegola @ 0.7.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| imposm3 @ 0.6.0-alpha.4 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| libgeotiff @ 1.5.1 | patch-file-names Validate file names and availability of patches | libgeotiff-adapt-test-script-for-proj-6.2.patch: file name is too long | ||
| xygrib @ 1.2.6.1 | formatting Look for formatting issues in the source | line 1404 is way too long (95 characters) | ||
| rust-actix-derive @ 0.5.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| proj.4 @ 4.9.3 | formatting Look for formatting issues in the source | line 583 is way too long (92 characters) | ||
| nyxt @ 2.2.3 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python2-ccm @ 2.1.6 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 84 | ||
| python-psycopg2 @ 2.9.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-ccm @ 2.1.6 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 84 | ||
| guile-wiredtiger @ 0.7.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| sqlcipher @ 3.4.2 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| ibus-libhangul @ 1.5.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ibus-anthy @ 1.5.9 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| librime @ 1.7.3 | formatting Look for formatting issues in the source | line 337 is way too long (93 characters) | ||
| ocaml4.07-qcheck @ 0.12 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 52, 156 | ||
| ocaml-zarith @ 1.12 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 146 | ||
| ocaml-topkg @ 1.0.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 51 | ||
| ocaml-qcheck @ 0.18 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 52, 156 | ||
| ocaml-down @ 0.0.3 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ocaml-cmdliner @ 1.0.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 304 | ||
| ocaml-sedlex @ 2.4 | formatting Look for formatting issues in the source | line 2776 is way too long (97 characters) | ||
| ocaml-ounit @ 2.2.4 | formatting Look for formatting issues in the source | line 1373 is way too long (97 characters) | ||
| ocaml-dose3 @ 5.0.1 | formatting Look for formatting issues in the source | line 634 is way too long (92 characters) | ||
| 389-ds-base @ 1.4.0.31 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| ucsim @ 0.6-pre68 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| emacs-gdscript-mode @ 1.4.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 99 | ||
| emacs-dhall-mode @ 0.1.3-1.484bcf8 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 89 | ||
| maven-wagon-provider-api @ 3.3.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs /gnu/store/6aw23zz5wvvh1pl09xak61ls2xp7ihyy-maven-wagon-provider-api-3.3.4 and /gnu/store/m9z8ym70yaw1ypig4m9yh8nrls1016ck-maven-wagon-provider-api-3.3.4 collide | ||
| python2-libmpsse @ 1.4.1 | formatting Look for formatting issues in the source | line 1175 is way too long (96 characters) | ||
| python-libmpsse @ 1.4.1 | formatting Look for formatting issues in the source | line 1142 is way too long (94 characters) | ||
| jimtcl @ 0.80 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| fc-host-tools @ 15 | formatting Look for formatting issues in the source | line 1262 is way too long (122 characters) | ||
| lpsolve @ 5.5.2.5 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| opencascade-occt @ 7.3.0p3 | inputs-should-be-native Identify inputs that should be native inputs | 'doxygen' should probably be a native input | ||
| octave-cli @ 6.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'texinfo' should probably be a native input | ||
| octave @ 6.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'texinfo' should probably be a native input | ||
| scotch32 @ 6.1.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| scotch-shared @ 6.1.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| pt-scotch32 @ 6.1.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| pt-scotch-shared @ 6.1.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| pt-scotch @ 6.1.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mumps-openmpi @ 5.2.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mumps-metis-openmpi @ 5.2.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mumps-metis @ 5.2.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| dune-istl-openmpi @ 2.7.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| superlu-dist @ 6.4.0 | formatting Look for formatting issues in the source | line 3704 is way too long (92 characters) | ||
| superlu-dist @ 6.4.0 | formatting Look for formatting issues in the source | tabulation on line 3724, column 0 | ||
| superlu-dist @ 6.4.0 | formatting Look for formatting issues in the source | tabulation on line 3725, column 0 | ||
| sundials-openmpi @ 3.1.1 | formatting Look for formatting issues in the source | tabulation on line 6158, column 0 | ||
| slepc-openmpi @ 3.11.1 | formatting Look for formatting issues in the source | tabulation on line 3168, column 0 | ||
| slepc-complex-openmpi @ 3.11.1 | formatting Look for formatting issues in the source | line 3184 is way too long (92 characters) | ||
| pt-scotch32 @ 6.1.1 | formatting Look for formatting issues in the source | tabulation on line 3985, column 0 | ||
| pt-scotch @ 6.1.1 | formatting Look for formatting issues in the source | tabulation on line 3963, column 0 | ||
| petsc @ 3.11.2 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| p4est @ 2.0 | formatting Look for formatting issues in the source | tabulation on line 4074, column 0 | ||
| mumps-openmpi @ 5.2.1 | formatting Look for formatting issues in the source | tabulation on line 3543, column 0 | ||
| mumps @ 5.2.1 | formatting Look for formatting issues in the source | line 3457 is way too long (94 characters) | ||
| hypre-openmpi @ 2.15.1 | formatting Look for formatting issues in the source | tabulation on line 5528, column 0 | ||
| linux-libre-headers @ 4.9.291 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-headers @ 4.4.293 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-headers @ 4.14.256 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm-omap2plus @ 4.14.256 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm-generic @ 4.14.256 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre @ 4.9.291 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre @ 4.4.293 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre @ 4.14.256 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm-omap2plus @ 4.14.256 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre-arm-generic @ 4.14.256 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre @ 4.9.291 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre @ 4.4.293 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre @ 4.14.256 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| mergerfs @ 2.32.6 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| libnfs @ 4.0.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| glusterfs @ 7.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| emacs-templatel @ 0.1.6 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| emacs-swiper @ 0.13.4 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| emacs-pyvenv @ 1.21 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| emacs-epithet @ 0.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 118 | ||
| emacs-el-x @ 0.3.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| emacs-sqlite @ 1.0-0.dad42b8 | formatting Look for formatting issues in the source | tabulation on line 5448, column 0 | ||
| emacs-sqlite @ 1.0-0.dad42b8 | formatting Look for formatting issues in the source | tabulation on line 5449, column 0 | ||
| emacs-mit-scheme-doc @ 20140203 | formatting Look for formatting issues in the source | line 7010 is way too long (94 characters) | ||
| u-boot-wandboard @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-tools @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-sifive-unmatched @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-sifive-unleashed @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-rockpro64-rk3399 @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-rock64-rk3328 @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-qemu-riscv64-smode @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-qemu-riscv64 @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-puma-rk3399 @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-pinebook-pro-rk3399 @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-pinebook @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-pine64-plus @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-pine64-lts @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-novena @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-nintendo-nes-classic-edition @ 2018.11 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-mx6cuboxi @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-malta @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-firefly-rk3399 @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-cubietruck @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-cubieboard @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-bananapi-m2-ultra @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-am335x-evm @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-am335x-boneblack @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-a20-olinuxino-micro @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-a20-olinuxino-lime2 @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-a20-olinuxino-lime @ 2021.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-wandboard @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| u-boot-tools @ 2021.10 | formatting Look for formatting issues in the source | line 601 is way too long (108 characters) | ||
| u-boot-tools @ 2021.10 | formatting Look for formatting issues in the source | line 605 is way too long (97 characters) | ||
| u-boot-sifive-unmatched @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| u-boot-sifive-unleashed @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| u-boot-qemu-riscv64 @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| u-boot-pinebook @ 2021.10 | formatting Look for formatting issues in the source | line 809 is way too long (127 characters) | ||
| u-boot-pine64-plus @ 2021.10 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| u-boot-pine64-lts @ 2021.10 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| u-boot-mx6cuboxi @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| u-boot-malta @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| u-boot-cubietruck @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| u-boot-cubieboard @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| u-boot-bananapi-m2-ultra @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| u-boot-am335x-evm @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| u-boot-am335x-boneblack @ 2021.10 | formatting Look for formatting issues in the source | line 760 is way too long (95 characters) | ||
| u-boot-a20-olinuxino-micro @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| u-boot-a20-olinuxino-lime2 @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| u-boot-a20-olinuxino-lime @ 2021.10 | formatting Look for formatting issues in the source | line 722 is way too long (93 characters) | ||
| linux-pam @ 1.5.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| cscope @ 15.9 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 50 | ||
| cataclysm-dda @ 0.F-3 | formatting Look for formatting issues in the source | line 910 is way too long (94 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 192 is way too long (93 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 193 is way too long (93 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 204 is way too long (91 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 212 is way too long (93 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 234 is way too long (92 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 235 is way too long (96 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 240 is way too long (96 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 282 is way too long (91 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 295 is way too long (92 characters) | ||
| tao @ 1.0-beta-10May2006 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| tao @ 1.0-beta-10May2006 | inputs-should-be-native Identify inputs that should be native inputs | 'bison' should probably be a native input | ||
| audio-to-midi @ 2020.7 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| infamous-plugins @ 0.3.0 | formatting Look for formatting issues in the source | line 1093 is way too long (104 characters) | ||
| faad2 @ 2.8.8 | formatting Look for formatting issues in the source | line 1825 is way too long (95 characters) | ||
| audacity @ 2.4.2 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| calibre @ 5.21.0 | formatting Look for formatting issues in the source | line 260 is way too long (92 characters) | ||
| calibre @ 5.21.0 | formatting Look for formatting issues in the source | line 285 is way too long (93 characters) | ||
| perftest @ 4.4-0.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 99 | ||
| mdadm-static @ 4.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| f2fs-fsck-static @ 1.14.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 91 | ||
| ecryptfs-utils @ 111 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| util-linux-with-udev @ 2.35.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| wireless-tools @ 30.pre9 | formatting Look for formatting issues in the source | line 4041 is way too long (104 characters) | ||
| util-linux @ 2.35.1 | formatting Look for formatting issues in the source | line 1834 is way too long (91 characters) | ||
| toybox @ 0.8.5 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| perftest @ 4.4-0.4 | formatting Look for formatting issues in the source | line 6081 is way too long (98 characters) | ||
| crda @ 3.18 | formatting Look for formatting issues in the source | line 4148 is way too long (100 characters) | ||
| coq-stdlib @ 8.14.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| coq-ide-server @ 8.14.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| coq-ide @ 8.14.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| coq-core @ 8.14.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-html2text @ 2019.8.11 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-html2text @ 2020.1.16 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-requests-unixsocket @ 0.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-requests @ 2.20.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs python-urllib3@1.24.3 and python-urllib3@1.26.2 collide | ||
| python-tornado @ 5.1.1 | formatting Look for formatting issues in the source | line 1733 is way too long (91 characters) | ||
| r-rtracklayer @ 1.54.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-biomart @ 2.50.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-hsmmsinglecell @ 1.2.0 | formatting Look for formatting issues in the source | line 1300 is way too long (95 characters) | ||
| r-bsgenome-dmelanogaster-ucsc-dm3-masked @ 1.3.99 | formatting Look for formatting issues in the source | line 277 is way too long (95 characters) | ||
| r-biocparallel @ 1.28.1 | formatting Look for formatting issues in the source | line 2362 is way too long (95 characters) | ||
| python-jinja2-time @ 0.2.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| python-cligj @ 0.7.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| julia-chainrulestestutils @ 1.2.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 260 | ||
| python-case @ 1.5.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-mock' should probably be a native input | ||
| python-case @ 1.5.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-nose' should probably be a native input | ||
| python-virtualenv @ 20.2.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-argopt @ 0.7.0 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python2-pybugz @ 0.6.11 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| scons @ 3.0.4 | formatting Look for formatting issues in the source | line 3053 is way too long (96 characters) | ||
| r-yapsa @ 1.19.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 93, 96 | ||
| r-seqlogo @ 1.60.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-rgadem @ 2.42.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-iclusterplus @ 1.30.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-biosigner @ 1.22.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| python2-rst.linker @ 1.11 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-pygame @ 1.9.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 123 | ||
| python-xsge @ 2020.09.07 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-rst.linker @ 1.11 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-pywinrm @ 0.4.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-pygame @ 1.9.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 123 | ||
| python-pikepdf @ 2.16.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| grfcodec @ 6.0.6 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 100 | ||
| deutex @ 5.2.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 60 | ||
| c-blosc @ 1.18.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 64 | ||
| shogun @ 6.1.3 | inputs-should-be-native Identify inputs that should be native inputs | 'swig' should probably be a native input | ||
| python2-numpydoc @ 0.9.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-sphinx' should probably be a native input | ||
| python2-matplotlib @ 2.2.4 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python-restructuredtext-lint @ 1.3.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-numpydoc @ 1.1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-matplotlib @ 3.1.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python-hmmlearn @ 0.2.6 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| python-hmmlearn @ 0.2.6 | inputs-should-be-native Identify inputs that should be native inputs | 'python-setuptools-scm' should probably be a native input | ||
| python-doc8 @ 0.8.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| pelican @ 4.7.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| tensorflow @ 1.9.0 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-pikepdf @ 2.16.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-cmaes @ 0.8.2 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| linux-libre-riscv64-generic @ 5.15.6 | derivation Report failure to compile a package to a derivation | failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux' | ||
| linux-libre-bpf @ 5.15.6 | derivation Report failure to compile a package to a derivation | failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux' | ||
| linux-libre @ 5.4.163 | derivation Report failure to compile a package to a derivation | failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux' | ||
| linux-libre @ 5.15.6 | derivation Report failure to compile a package to a derivation | failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux' | ||
| linux-libre @ 5.10.83 | derivation Report failure to compile a package to a derivation | failed to create riscv64-linux derivation: could not find bootstrap binary 'tar' for system 'riscv64-linux' | ||
| x86-energy-perf-policy @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| usbip-utils @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| turbostat @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| tmon @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-renpy @ 7.4.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-xgboost @ 1.4.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-matplotlib-documentation @ 3.1.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| perf @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-riscv64-generic @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-mips64el-fuloong2e @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-headers @ 5.4.163 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-headers @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-headers @ 5.10.83 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-headers @ 4.19.219 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-bpf @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm64-generic @ 5.4.163 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm64-generic @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm64-generic @ 5.10.83 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm-omap2plus @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm-omap2plus @ 4.19.219 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm-generic @ 5.4.163 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm-generic @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm-generic @ 5.10.83 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm-generic @ 4.19.219 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre @ 5.4.163 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre @ 5.10.83 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre @ 4.19.219 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| freefall @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| cpupower @ 5.15.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| pzstd @ 1.4.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| tensorflow @ 1.9.0 | formatting Look for formatting issues in the source | line 1763 is way too long (92 characters) | ||
| tensorflow @ 1.9.0 | formatting Look for formatting issues in the source | line 1866 is way too long (91 characters) | ||
| tensorflow @ 1.9.0 | formatting Look for formatting issues in the source | line 1953 is way too long (137 characters) | ||
| tensorflow @ 1.9.0 | formatting Look for formatting issues in the source | line 1954 is way too long (131 characters) | ||
| tensorflow @ 1.9.0 | formatting Look for formatting issues in the source | line 1955 is way too long (137 characters) | ||
| shogun @ 6.1.3 | formatting Look for formatting issues in the source | line 531 is way too long (91 characters) | ||
| r-monocle @ 2.22.0 | formatting Look for formatting issues in the source | line 6692 is way too long (101 characters) | ||
| r-lumi @ 2.46.0 | formatting Look for formatting issues in the source | line 7155 is way too long (95 characters) | ||
| r-genomicinteractions @ 1.28.0 | formatting Look for formatting issues in the source | line 5711 is way too long (92 characters) | ||
| python2-fastlmm @ 0.2.21 | formatting Look for formatting issues in the source | line 1342 is way too long (92 characters) | ||
| python-pytorch @ 1.10.0 | formatting Look for formatting issues in the source | line 2857 is way too long (94 characters) | ||
| python-numpy @ 1.17.3 | formatting Look for formatting issues in the source | line 5413 is way too long (152 characters) | ||
| python-matplotlib @ 3.1.2 | formatting Look for formatting issues in the source | line 6288 is way too long (107 characters) | ||
| python-matplotlib @ 3.1.2 | formatting Look for formatting issues in the source | line 6328 is way too long (96 characters) | ||
| python-imagecodecs @ 2021.3.31 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| openshot @ 2.6.1 | formatting Look for formatting issues in the source | line 4867 is way too long (94 characters) | ||
| openshot @ 2.6.1 | formatting Look for formatting issues in the source | line 4868 is way too long (96 characters) | ||
| openshot @ 2.6.1 | formatting Look for formatting issues in the source | line 4869 is way too long (92 characters) | ||
| mkvtoolnix @ 52.0.0 | formatting Look for formatting issues in the source | line 973 is way too long (96 characters) | ||
| minizip @ 1.2.11 | formatting Look for formatting issues in the source | line 166 is way too long (115 characters) | ||
| linux-libre-riscv64-generic @ 5.15.6 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre-mips64el-fuloong2e @ 5.15.6 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre-arm64-generic @ 5.4.163 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre-arm64-generic @ 5.15.6 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre-arm64-generic @ 5.10.83 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre-arm-omap2plus @ 5.15.6 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre-arm-omap2plus @ 4.19.219 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre-arm-generic @ 5.4.163 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre-arm-generic @ 5.15.6 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre-arm-generic @ 5.10.83 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre-arm-generic @ 4.19.219 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre @ 5.4.163 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre @ 5.15.6 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre @ 5.10.83 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| linux-libre @ 4.19.219 | formatting Look for formatting issues in the source | line 856 is way too long (117 characters) | ||
| gaupol @ 1.9 | formatting Look for formatting issues in the source | line 5034 is way too long (95 characters) | ||
| brotli @ 1.0.9 | formatting Look for formatting issues in the source | line 2190 is way too long (94 characters) | ||
| r-bseqsc @ 1.0-1.fef3f3e | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 395 | ||
| python-pyfit-sne @ 1.0.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-drep @ 3.2.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| i3-wm @ 4.18.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-int-interval-map @ 0.0.0.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 268 | ||
| python-velocyto @ 0.17.17 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| python-drep @ 3.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-bbknn @ 1.3.6 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| keybinder-3.0 @ 0.3.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| awesome @ 4.3 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| quickswitch-i3 @ 2.2-1.ed692b1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| openmpi-thread-multiple @ 4.1.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| openmpi-c++ @ 4.1.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-openmpi @ 4.1.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-scanpy @ 1.8.1 | formatting Look for formatting issues in the source | line 12015 is way too long (98 characters) | ||
| kuserfeedback @ 1.0.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| python2-q @ 2.6 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-dbus @ 1.2.16 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-q @ 2.6 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| snakemake @ 5.32.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-pytest-black @ 0.3.8 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-legacy-api-wrap @ 1.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-legacy-api-wrap @ 1.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest-cov' should probably be a native input | ||
| python-jaraco-packaging @ 6.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-jaraco-packaging @ 6.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-setuptools-scm' should probably be a native input | ||
| python-jaraco-packaging @ 6.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-get-version @ 2.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-get-version @ 2.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest-cov' should probably be a native input | ||
| python-amply @ 0.1.4 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-legacy-api-wrap @ 1.2 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-jaraco-packaging @ 6.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-ipython-cluster-helper @ 0.6.4 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-get-version @ 2.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-ipython-cluster-helper @ 0.6.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs python-tornado@5.1.1 and python-tornado@6.1 collide | ||
| python-ipyparallel @ 6.2.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs python-tornado@6.1 and python-tornado@5.1.1 collide | ||
| python2-pep8 @ 1.7.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-execnet @ 1.9.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-configobj @ 5.0.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-nbconvert @ 6.0.7 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| python-ipython-documentation @ 7.20.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| java-plexus-archiver @ 4.2.2 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-plexus-sec-dispatcher @ 1.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide | ||
| java-plexus-digest @ 1.2 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@3.1 collide | ||
| java-plexus-container-default @ 1.7.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-plexus-component-metadata @ 1.7.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@13 and apache-parent-pom@21 collide | ||
| java-plexus-compiler-manager @ 2.8.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-plexus-compiler-javac @ 2.8.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-plexus-compiler-api @ 2.8.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide | ||
| java-plexus-archiver @ 4.2.2 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@6.1 collide | ||
| java-modello-test @ 1.9.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-modello-plugins-xpp3 @ 1.9.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-modello-plugins-xml @ 1.9.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-modello-plugins-java @ 1.9.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-modello-core @ 1.9.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-openjfx-media @ 8.202 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-openjfx-graphics @ 8.202 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-openjfx-controls @ 8.202 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-openjfx-base @ 8.202 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-sisu-build-api @ 0.0.7 | formatting Look for formatting issues in the source | line 5152 is way too long (98 characters) | ||
| java-plexus-sec-dispatcher @ 1.4 | formatting Look for formatting issues in the source | line 5029 is way too long (107 characters) | ||
| java-plexus-compiler-javac @ 2.8.4 | formatting Look for formatting issues in the source | line 4910 is way too long (95 characters) | ||
| java-openjfx-graphics @ 8.202 | formatting Look for formatting issues in the source | line 2861 is way too long (99 characters) | ||
| java-openjfx-graphics @ 8.202 | formatting Look for formatting issues in the source | line 2872 is way too long (98 characters) | ||
| java-openjfx-graphics @ 8.202 | formatting Look for formatting issues in the source | line 2911 is way too long (96 characters) | ||
| java-openjfx-base @ 8.202 | formatting Look for formatting issues in the source | line 2801 is way too long (111 characters) | ||
| java-openjfx-base @ 8.202 | formatting Look for formatting issues in the source | line 2816 is way too long (99 characters) | ||
| java-hamcrest-core @ 1.3 | formatting Look for formatting issues in the source | line 4041 is way too long (112 characters) | ||
| java-eclipse-text @ 3.6.0 | formatting Look for formatting issues in the source | tabulation on line 7573, column 20 | ||
| java-eclipse-text @ 3.6.0 | formatting Look for formatting issues in the source | tabulation on line 7574, column 20 | ||
| java-eclipse-jdt-core @ 3.16.0 | formatting Look for formatting issues in the source | line 7633 is way too long (98 characters) | ||
| java-commons-jxpath @ 1.3 | formatting Look for formatting issues in the source | line 6377 is way too long (93 characters) | ||
| java-commons-exec @ 1.1 | formatting Look for formatting issues in the source | line 6145 is way too long (91 characters) | ||
| r-mixomics @ 6.18.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-biocio @ 1.4.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-bioassayr @ 1.32.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-unifiedwmwqpcr @ 1.30.0 | formatting Look for formatting issues in the source | line 11240 is way too long (92 characters) | ||
| r-gdsfmt @ 1.30.0 | formatting Look for formatting issues in the source | tabulation on line 10796, column 17 | ||
| r-cner @ 1.30.0 | formatting Look for formatting issues in the source | line 12944 is way too long (109 characters) | ||
| emacs-flx @ 0.6.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 220 | ||
| emacs-cnfonts @ 0.9.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| lepton-eda @ 1.9.14-20210407 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| geda-gaf @ 1.10.0 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| freehdl @ 0.0.8 | inputs-should-be-native Identify inputs that should be native inputs | 'pkg-config' should probably be a native input | ||
| freehdl @ 0.0.8 | inputs-should-be-native Identify inputs that should be native inputs | 'libtool' should probably be a native input | ||
| emacs-xwidgets @ 27.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-wide-int @ 27.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-no-x-toolkit @ 27.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-no-x @ 27.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-next @ 28.0.50-0.2ea3466 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-minimal @ 27.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| meshlab @ 2020.06 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| fritzing @ 0.9.3b | formatting Look for formatting issues in the source | line 674 is way too long (91 characters) | ||
| fritzing @ 0.9.3b | formatting Look for formatting issues in the source | line 675 is way too long (99 characters) | ||
| freehdl @ 0.0.8 | formatting Look for formatting issues in the source | line 1975 is way too long (101 characters) | ||
| r-xyz @ 0.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 232, 243, 262 | ||
| r-wmtsa @ 2.0-3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 105, 128 | ||
| r-topicmodels @ 0.2-12 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 151 | ||
| r-systemfonts @ 1.0.3 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-survminer @ 0.4.9 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-sapa @ 2.0-3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 97, 120 | ||
| r-rstan @ 2.21.2 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-reldist @ 1.6-6 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 250 | ||
| r-r2glmm @ 0.1.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 173, 176 | ||
| r-palmerpenguins @ 0.1.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 268 | ||
| r-oai @ 0.3.2 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-lpme @ 1.1.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 153 | ||
| r-iml @ 0.10.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-iheatmapr @ 0.5.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-hapassoc @ 1.2-8 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 139 | ||
| r-fontbitstreamvera @ 0.1.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 57 | ||
| r-fda @ 5.5.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 92, 113 | ||
| r-dorng @ 1.8.2 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-diagram @ 1.6.5 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 336 | ||
| r-cmprsk @ 2.2-10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 242 | ||
| r-clusterr @ 1.2.5 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 606, 945 | ||
| r-circular @ 0.4-93 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 98, 123 | ||
| r-brms @ 2.16.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-brms @ 2.16.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 109, 532, 653, 784 | ||
| r-bootstrap @ 2019.6 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 92, 105 | ||
| r-aws-signature @ 0.6.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-astsa @ 1.14 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 132, 149 | ||
| r-arm @ 1.12-2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 46, 60 | ||
| r-zra @ 0.2 | formatting Look for formatting issues in the source | line 31333 is way too long (92 characters) | ||
| r-squarem @ 2021.1 | formatting Look for formatting issues in the source | line 4476 is way too long (91 characters) | ||
| r-shiny @ 1.7.1 | formatting Look for formatting issues in the source | line 2141 is way too long (103 characters) | ||
| r-shiny @ 1.7.1 | formatting Look for formatting issues in the source | line 2149 is way too long (94 characters) | ||
| r-shiny @ 1.7.1 | formatting Look for formatting issues in the source | line 2181 is way too long (92 characters) | ||
| r-haplo-stats @ 1.8.7 | formatting Look for formatting issues in the source | line 17047 is way too long (103 characters) | ||
| r-gamlss-dist @ 6.0-1 | formatting Look for formatting issues in the source | line 15544 is way too long (91 characters) | ||
| r-freetypeharfbuzz @ 0.2.6 | formatting Look for formatting issues in the source | tabulation on line 29402, column 0 | ||
| r-freetypeharfbuzz @ 0.2.6 | formatting Look for formatting issues in the source | tabulation on line 29403, column 0 | ||
| r-freetypeharfbuzz @ 0.2.6 | formatting Look for formatting issues in the source | tabulation on line 29404, column 0 | ||
| r-freetypeharfbuzz @ 0.2.6 | formatting Look for formatting issues in the source | tabulation on line 29405, column 0 | ||
| r-freetypeharfbuzz @ 0.2.6 | formatting Look for formatting issues in the source | tabulation on line 29406, column 0 | ||
| r-freetypeharfbuzz @ 0.2.6 | formatting Look for formatting issues in the source | tabulation on line 29407, column 0 | ||
| r-freetypeharfbuzz @ 0.2.6 | formatting Look for formatting issues in the source | tabulation on line 29408, column 0 | ||
| r-flexdashboard @ 0.5.2 | formatting Look for formatting issues in the source | line 18414 is way too long (96 characters) | ||
| r-flexdashboard @ 0.5.2 | formatting Look for formatting issues in the source | line 18428 is way too long (96 characters) | ||
| r-flexdashboard @ 0.5.2 | formatting Look for formatting issues in the source | line 18435 is way too long (117 characters) | ||
| r-flexdashboard @ 0.5.2 | formatting Look for formatting issues in the source | line 18442 is way too long (100 characters) | ||
| r-colourpicker @ 1.1.1 | formatting Look for formatting issues in the source | line 15643 is way too long (94 characters) | ||
| r-bslib @ 0.3.1 | formatting Look for formatting issues in the source | line 2102 is way too long (102 characters) | ||
| r-bslib @ 0.3.1 | formatting Look for formatting issues in the source | line 2109 is way too long (102 characters) | ||
| r-abps @ 0.3 | formatting Look for formatting issues in the source | line 10549 is way too long (93 characters) | ||
| xfce4-screensaver @ 4.16.0 | description Validate package descriptions | description contains trailing whitespace | ||
| tracker @ 2.3.5 | description Validate package descriptions | description contains trailing whitespace | ||
| texlive-unicode-data @ 51265 | description Validate package descriptions | description contains trailing whitespace | ||
| texlive-sectsty @ 51265 | description Validate package descriptions | description contains trailing whitespace | ||
| texlive-generic-unicode-data @ 51265 | description Validate package descriptions | description contains trailing whitespace | ||
| texlive-fonts-charter @ 51265 | description Validate package descriptions | description contains trailing whitespace | ||
| texlive-charter @ 51265 | description Validate package descriptions | description contains trailing whitespace | ||
| ruby-ox @ 2.6.0 | description Validate package descriptions | description contains trailing whitespace | ||
| r-labelled @ 2.9.0 | description Validate package descriptions | description contains trailing whitespace | ||
| quazip @ 1.2 | description Validate package descriptions | description contains trailing whitespace | ||
| quazip @ 0.9.1 | description Validate package descriptions | description contains trailing whitespace | ||
| python2-babel @ 2.9.0 | description Validate package descriptions | description contains trailing whitespace | ||
| python-plotly @ 4.14.3 | description Validate package descriptions | description contains trailing whitespace | ||
| python-plotly @ 2.4.1 | description Validate package descriptions | description contains trailing whitespace | ||
| python-myhdl @ 0.11 | description Validate package descriptions | description contains trailing whitespace | ||
| python-babel @ 2.9.0 | description Validate package descriptions | description contains trailing whitespace | ||
| openmpi-thread-multiple @ 4.1.1 | description Validate package descriptions | description contains leading whitespace | ||
| leafpad @ 0.8.18.1 | description Validate package descriptions | description contains trailing whitespace | ||
| kontactinterface @ 20.04.1 | description Validate package descriptions | description contains leading whitespace | ||
| kldap @ 20.04.1 | description Validate package descriptions | description contains leading whitespace | ||
| kldap @ 20.04.1 | description Validate package descriptions | description contains trailing whitespace | ||
| keyutils @ 1.6.1 | description Validate package descriptions | description contains trailing whitespace | ||
| js-commander @ 6.2.1 | description Validate package descriptions | description contains trailing whitespace | ||
| guile-f-scm @ 0.2.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-yesod-form @ 1.7.0 | description Validate package descriptions | description contains trailing whitespace | ||
| ghc-vector-builder @ 0.3.8.2 | description Validate package descriptions | description contains trailing whitespace | ||
| ghc-genvalidity-hspec @ 0.7.0.4 | description Validate package descriptions | description contains trailing whitespace | ||
| ghc-crypto-cipher-tests @ 0.0.11 | description Validate package descriptions | description contains leading whitespace | ||
| frrouting @ 7.5.1 | description Validate package descriptions | description contains trailing whitespace | ||
| emacs-sly-quicklisp @ 0.0.0-1.01ebe39 | description Validate package descriptions | description contains trailing whitespace | ||
| emacs-highlight-symbol @ 1.3-1.7a789c7 | description Validate package descriptions | description contains trailing whitespace | ||
| dirvish @ 1.2.1 | description Validate package descriptions | description contains trailing whitespace | ||
| buildapp @ 1.5.6 | description Validate package descriptions | description contains trailing whitespace | ||
| bindfs @ 1.15.1 | description Validate package descriptions | description contains trailing whitespace | ||
| python-pytest-django @ 4.4.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| poezio @ 0.13.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| phonesim @ 1.21 | source-file-name Validate file names of sources | the source file name should contain the package name | ||
| mumble @ 1.3.4 | formatting Look for formatting issues in the source | tabulation on line 578, column 0 | ||
| mumble @ 1.3.4 | formatting Look for formatting issues in the source | tabulation on line 579, column 0 | ||
| mumble @ 1.3.4 | formatting Look for formatting issues in the source | tabulation on line 580, column 0 | ||
| prusa-slicer @ 2.3.3 | formatting Look for formatting issues in the source | line 3107 is way too long (94 characters) | ||
| libigl @ 2.3.0 | formatting Look for formatting issues in the source | line 2965 is way too long (91 characters) | ||
| libigl @ 2.3.0 | formatting Look for formatting issues in the source | line 2966 is way too long (101 characters) | ||
| libigl @ 2.3.0 | formatting Look for formatting issues in the source | line 2993 is way too long (94 characters) | ||
| openssh-sans-x @ 8.8p1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| giac @ 1.7.0-43 | formatting Look for formatting issues in the source | line 353 is way too long (95 characters) | ||
| python2-clf @ 0.5.7 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-nose' should probably be a native input | ||
| python-pytest-httpbin @ 0.2.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-clf @ 0.5.7 | inputs-should-be-native Identify inputs that should be native inputs | 'python-nose' should probably be a native input | ||
| java-eclipse-jetty-xml @ 9.4.39 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-xml @ 9.2.22 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-webapp @ 9.4.39 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-webapp @ 9.2.22 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-util-ajax @ 9.4.39 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-util @ 9.4.39 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-util @ 9.2.22 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-servlet @ 9.4.39 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-servlet @ 9.2.22 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-server @ 9.4.39 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-server @ 9.2.22 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-security @ 9.4.39 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-security @ 9.2.22 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-jmx @ 9.4.39 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-jmx @ 9.2.22 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-io @ 9.4.39 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-io @ 9.2.22 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-http @ 9.4.39 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-jetty-http @ 9.2.22 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| http-parser @ 2.9.4-1.ec8b5ee | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| varnish @ 7.0.1 | formatting Look for formatting issues in the source | line 6081 is way too long (91 characters) | ||
| serf @ 1.3.9 | formatting Look for formatting issues in the source | line 2011 is way too long (92 characters) | ||
| nginx-accept-language-module @ 0.0.0-1.2f69842 | formatting Look for formatting issues in the source | line 625 is way too long (92 characters) | ||
| krona-tools @ 2.8 | formatting Look for formatting issues in the source | trailing white space on line 1305 | ||
| icecat @ 91.4.0-guix0-preview1 | formatting Look for formatting issues in the source | line 1025 is way too long (102 characters) | ||
| icecat @ 91.4.0-guix0-preview1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| icecat @ 91.4.0-guix0-preview1 | formatting Look for formatting issues in the source | line 1105 is way too long (139 characters) | ||
| icecat @ 91.4.0-guix0-preview1 | formatting Look for formatting issues in the source | line 1111 is way too long (95 characters) | ||
| icecat @ 91.4.0-guix0-preview1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| icecat @ 91.4.0-guix0-preview1 | formatting Look for formatting issues in the source | line 1153 is way too long (92 characters) | ||
| icecat @ 91.4.0-guix0-preview1 | formatting Look for formatting issues in the source | line 1155 is way too long (93 characters) | ||
| icecat @ 91.4.0-guix0-preview1 | formatting Look for formatting issues in the source | line 1162 is way too long (98 characters) | ||
| xfs_repair-static @ 5.14.0 | name Validate package names | name should use hyphens instead of underscores | ||
| ruby_version @ 1.0.2 | name Validate package names | name should use hyphens instead of underscores | ||
| ruby-progress_bar @ 1.1.0 | name Validate package names | name should use hyphens instead of underscores | ||
| ruby-data_uri @ 0.1.0 | name Validate package names | name should use hyphens instead of underscores | ||
| perl-crypt-unixcrypt_xs @ 0.11 | name Validate package names | name should use hyphens instead of underscores | ||
| nsis-x86_64 @ 3.05 | name Validate package names | name should use hyphens instead of underscores | ||
| mingw-w64-x86_64-winpthreads @ 8.0.0 | name Validate package names | name should use hyphens instead of underscores | ||
| mingw-w64-x86_64 @ 8.0.0 | name Validate package names | name should use hyphens instead of underscores | ||
| jfs_fsck-static @ 1.1.15 | name Validate package names | name should use hyphens instead of underscores | ||
| efi_analyzer @ 0.0.0-0.77c9e3a | name Validate package names | name should use hyphens instead of underscores | ||
| yt-dlp @ 2021.10.22 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| swi-prolog @ 8.3.20 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| ruby-yard-with-tests @ 0.9.25 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| ruby-ffi-rzmq @ 2.0.7 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| ruby-byebug @ 11.1.3 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| python2-promise @ 0.4.2 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| python2-empy @ 3.3.3 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| proot-static @ 5.2.0-alpha-0.a70023a | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| proot @ 5.2.0-alpha-0.a70023a | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| pjproject-jami @ 2.10 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| pjproject @ 2.11 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| perl-unicode-utf8 @ 0.62 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| libicns @ 0.8.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| lean @ 3.23.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| lablgtk @ 3.1.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| inkscape @ 1.1.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| ghc-statistics @ 0.15.2.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| ghc-bsb-http-chunked @ 0.0.0.4 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| fennel @ 1.0.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| extra-cmake-modules @ 5.70.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-yasnippet @ 0.14.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-xmlgen @ 0.5 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-wucuo @ 0.2.9 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-use-package @ 2.4.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-undo-fu-session @ 0.2-0.56cdd35 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-sudo-edit @ 0.1.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-string-inflection @ 1.0.16 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-skeletor @ 1.6.1-1.47c5b76 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-shx @ 1.5.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-s @ 1.12.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-rspec @ 1.11-1.66ea7cc | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-relative-buffers @ 0.0.1-0.9762fe2 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-realgud @ 1.5.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-rainbow-delimiters @ 2.1.5 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-pyvenv @ 1.21 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-perspective @ 2.17 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-org-pomodoro @ 2.1.0-1.aa07c11 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-org @ 9.5.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-nodejs-repl @ 0.2.4 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-monky @ 0.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-mocker @ 0.5.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-memoize @ 1.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-magit @ 3.3.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-lua-mode @ 20210802 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-lispy @ 0.27.0-2.38a7df4 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-julia-mode @ 0.4 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-js2-mode @ 20201220 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-hydra @ 0.15.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-ht @ 2.3 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-git-link @ 0.8.3 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-fringe-helper @ 1.0.1-1.ef4a9c0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-find-file-in-project @ 6.1.2 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-explain-pause-mode @ 0.1-0.2356c8c | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-evil-owl @ 0.0.1-3.24c5f43 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-evil-lion @ 0.0.2-1.6b03593 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-evil-expat @ 0.0.1-1.f4fcd0a | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-evil-exchange @ 0.41-1.4769153 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-elpy @ 1.35.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-elisp-demos @ 2020.02.19 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-elfeed-org @ 0.1-1.77b6bbf | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-elfeed @ 3.4.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-deferred @ 0.5.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-dash @ 2.19.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-company-lsp @ 2.1.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-clojure-mode @ 5.13.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-avy @ 0.5.0 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| emacs-ample-regexps @ 0.1-2.153969c | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| ecl @ 21.2.1 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| ecl @ 16.1.3 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| belcard @ 4.4.34 | tests-true Check if tests are explicitly enabled | #:tests? must not be explicitly set to #t | ||
| zeal @ 0.6.1-1.d3c5521 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| youtube-viewer @ 3.8.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| xorriso @ 1.5.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| xkbset @ 0.6 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| xfstests @ 1.1.0-1.bae1d15 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| xdg-utils @ 1.1.3 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| wxmaxima @ 21.05.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| wordnet @ 3.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| wine64-staging @ 6.6 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| wine64 @ 6.16 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| wine-staging @ 6.6 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| wine @ 6.16 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| windowmaker @ 0.95.9 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| wgetpaste @ 2.32 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| volk @ 2.4.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| vlc @ 3.0.16 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| vis @ 0.7 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| virt-viewer @ 7.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| virt-manager @ 3.2.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| veusz @ 3.3.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| vapoursynth @ 53 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| units @ 2.21 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| udisks @ 2.8.4 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| udiskie @ 2.3.3 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| tryton @ 6.0.5 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| translate-shell @ 0.9.6.12 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| totem @ 3.38.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| tomb @ 2.9 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| system-config-printer @ 1.5.15 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| synfigstudio @ 1.2.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| syncthing-gtk @ 0.9.4.4-1.c46fbd8 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| swish-e @ 2.4.7 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| sushi @ 3.32.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| strawberry @ 0.9.3 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| straw-viewer @ 0.1.7 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| srt2vtt @ 0.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| src @ 1.18 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| sqitch @ 1.1.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| spice-gtk @ 0.37 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| sonata @ 1.7.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| solfege @ 3.22.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| singularity @ 2.6.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| signing-party @ 2.11 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| shroud @ 0.1.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| shotcut @ 21.10.31 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| scanmem @ 0.17 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| sawfish @ 1.12.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| rust @ 1.20.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| ronn-ng @ 0.9.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| roffit @ 0.12-1.b59e6c855 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| rhythmbox @ 3.4.4 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| renpy @ 7.4.10 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| remmina @ 1.4.21 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| remind @ 3.3.7 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| redshift @ 1.12 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| rednotebook @ 2.22 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| recoll @ 1.31.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| rapid-photo-downloader @ 0.9.18 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| ranger @ 1.9.3 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| raincat @ 1.2.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| qutebrowser @ 2.3.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| quilt @ 0.66 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| qtpass @ 1.3.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used | ||
| qmapshack @ 1.15.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| qgis @ 3.16.3 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used | ||
| qgis @ 3.16.3 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| qbittorrent @ 4.2.5 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used | ||
| python-sqlparse @ 0.4.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| python-git-review @ 2.1.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| public-inbox @ 1.6.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| protonvpn-cli @ 2.2.6 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| presentty @ 0.2.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| pragha @ 1.3.4 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| po4a @ 0.63 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| ploticus @ 2.42 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| pitivi @ 0.999.0-2021.05.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| pipe-viewer @ 0.1.7 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| pinentry-rofi @ 2.0.3 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| piet-toolchain @ 0.0.0-0.f002ff6 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| phockup @ 1.7.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| perl-sgmls @ 1.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| perl-image-exiftool @ 12.16 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| perl-file-mimeinfo @ 0.29 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| perl-eval-withlexicals @ 1.003006 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| pencil2d @ 0.6.6 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| pcsxr @ 1.9.95 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| pcb @ 4.0.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| patchutils @ 0.4.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| password-store @ 1.7.4 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| parcimonie @ 0.11.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| parallel @ 20211122 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| papagayo @ 2.0b1-1.e143684b3 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| orca @ 3.34.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| orange @ 3.28.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| openshot @ 2.6.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used | ||
| opendht @ 2.3.0-1.6c58d4f | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| openconnect-sso @ 0.7.3 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| ocrodjvu @ 0.12 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| obs @ 27.0.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| nyxt @ 2.2.3 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| npiet @ 1.3f | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| nicotine+ @ 2.1.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| mysql @ 5.7.33 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| myrepos @ 1.20180726 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| mypaint @ 2.0.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| mpdris2 @ 0.9.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| mousepad @ 0.5.7 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| mosh @ 1.3.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| moreutils @ 0.66 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| mkfontdir @ 1.0.7 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| meld @ 3.20.4 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| mcg @ 2.1.2 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| maxima @ 5.45.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| manuskript @ 0.12.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| lxqt-session @ 0.17.1 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| lxpanel @ 0.10.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| luakit @ 2.3 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| lightdm @ 1.30.0 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| liferea @ 1.13.4 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| licensecheck @ 3.0.37 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| lcov @ 1.15 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| krona-tools @ 2.8 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| krita @ 4.4.8 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||
| kristall @ 0.3-1.204b08a | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used | ||
| kicad @ 5.1.10 | wrapper-inputs Make sure 'wrap-program' can finds its interpreter. | "bash-minimal" should be in 'inputs' when 'wrap-program' is used | ||