| Package | Linter | Message | Location | |
|---|---|---|---|---|
| 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 | ||
| wxwidgets-gtk2 @ 3.1.5 | 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 | ||
| python-wxpython @ 4.0.7.post1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-libfreenect @ 0.6.2 | 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-object @ 0.08 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| perl-test-file-contents @ 0.23 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| perl-libxml @ 0.08 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| node-serialport-parser-ready @ 9.2.4 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| node-nan @ 2.15.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| myrddin @ 0.3.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 116 | ||
| mate-applets @ 1.24.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 917 | ||
| 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 | ||
| kget @ 20.04.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 169 | ||
| 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 | ||
| java-jblas @ 1.2.4 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-tasty-silver @ 3.2.3 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| 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-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 | ||
| 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-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-doctest-lib @ 0.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 35 | ||
| fstrcmp @ 0.7.D001 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 236 | ||
| spice-gtk @ 0.37 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| 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-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 | ||
| python-oslo.utils @ 4.12.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-oslo.serialization @ 4.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-oslo.log @ 4.6.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-orange-canvas-core @ 0.1.24 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| 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 | ||
| python-keystoneclient @ 1.8.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' 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 | ||
| 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 | ||
| nextcloud-client @ 3.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'desktop-file-utils' should probably be a native input | ||
| lxqt @ 17.0 | inputs-should-be-native Identify inputs that should be native inputs | 'desktop-file-utils' should probably be a native input | ||
| libtool @ 2.4.6 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| libreoffice @ 7.1.4.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| kget @ 20.04.1 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| kaddressbook @ 20.04.1 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| gramps @ 5.1.4 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' 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 | ||
| fcitx-qt5 @ 1.2.6 | inputs-should-be-native Identify inputs that should be native inputs | 'intltool' 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.7.6 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| bison @ 3.7.6 | 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 | ||
| autoconf @ 2.71 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| autoconf @ 2.69 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| autoconf @ 2.68 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| autoconf @ 2.64 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| autoconf @ 2.13 | 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 | ||
| 389-ds-base @ 1.4.4.17 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' 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 | ||
| infiniband-diags @ 2.0.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| 389-ds-base @ 1.4.4.17 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| synfig @ 1.2.2 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs glibmm@2.70.0 and glibmm@2.64.5 collide | ||
| tigervnc-server @ 1.12.0-0.b484c22 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2 @ 2.7.18 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| pjproject-jami @ 2.11-0.e1f389d | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| 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 | ||
| 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 | ||
| 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 | ||
| 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 | ||
| 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 | ||
| libjami @ 20211223.2.37be4c3 | 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 | ||
| kodi-wayland @ 18.8 | 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 | ||
| jami-libclient @ 20211223.2.37be4c3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| jami-gnome @ 20211223.2.37be4c3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| ijs @ 9.54.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile-static-stripped-tarball @ 3.0.7 | 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.7 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| ghostscript-with-x @ 9.54.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| ghostscript-with-cups @ 9.54.0 | 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 | ||
| binutils-static-stripped-tarball @ 2.37 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| bash-with-syslog @ 5.1.8 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| bash-static @ 5.1.8 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| bash-minimal @ 5.1.8 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| avr-binutils @ 2.37 | 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 | ||
| sdl-pango @ 0.1.2 | patch-headers Validate patch headers | sdl-pango-header-guard.patch: patch lacks comment and upstream status | ||
| nsis-x86_64 @ 3.05 | patch-headers Validate patch headers | nsis-env-passthru.patch: patch lacks comment and upstream status | ||
| nsis-i686 @ 3.05 | patch-headers Validate patch headers | nsis-env-passthru.patch: patch lacks comment and upstream status | ||
| mono @ 4.4.1.0 | patch-headers Validate patch headers | mono-mdoc-timestamping.patch: patch lacks comment and upstream status | ||
| mkbootimg @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-remove-damaging-includes.patch: patch lacks comment and upstream status | ||
| mkbootimg @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-add-includes.patch: patch lacks comment and upstream status | ||
| mkbootimg @ 7.1.2_r36 | patch-headers Validate patch headers | adb-add-libraries.patch: patch lacks comment and upstream status | ||
| mkbootimg @ 7.1.2_r36 | patch-headers Validate patch headers | libziparchive-add-includes.patch: patch lacks comment and upstream status | ||
| mcrypt @ 2.6.8 | patch-headers Validate patch headers | mcrypt-CVE-2012-4426.patch: patch lacks comment and upstream status | ||
| linuxdcpp @ 1.1.0 | patch-headers Validate patch headers | linuxdcpp-openssl-1.1.patch: patch lacks comment and upstream status | ||
| libmhash @ 0.9.9.9 | patch-headers Validate patch headers | libmhash-hmac-fix-uaf.patch: patch lacks comment and upstream status | ||
| fastboot @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-remove-damaging-includes.patch: patch lacks comment and upstream status | ||
| fastboot @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-add-includes.patch: patch lacks comment and upstream status | ||
| fastboot @ 7.1.2_r36 | patch-headers Validate patch headers | adb-add-libraries.patch: patch lacks comment and upstream status | ||
| fastboot @ 7.1.2_r36 | patch-headers Validate patch headers | libziparchive-add-includes.patch: patch lacks comment and upstream status | ||
| cyrus-sasl @ 2.1.27 | patch-headers Validate patch headers | cyrus-sasl-ac-try-run-fix.patch: patch lacks comment and upstream status | ||
| apr @ 1.7.0 | patch-headers Validate patch headers | apr-skip-getservbyname-test.patch: patch lacks comment and upstream status | ||
| android-libziparchive @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-remove-damaging-includes.patch: patch lacks comment and upstream status | ||
| android-libziparchive @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-add-includes.patch: patch lacks comment and upstream status | ||
| android-libziparchive @ 7.1.2_r36 | patch-headers Validate patch headers | adb-add-libraries.patch: patch lacks comment and upstream status | ||
| android-libziparchive @ 7.1.2_r36 | patch-headers Validate patch headers | libziparchive-add-includes.patch: patch lacks comment and upstream status | ||
| android-libutils @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-remove-damaging-includes.patch: patch lacks comment and upstream status | ||
| android-libutils @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-add-includes.patch: patch lacks comment and upstream status | ||
| android-libutils @ 7.1.2_r36 | patch-headers Validate patch headers | adb-add-libraries.patch: patch lacks comment and upstream status | ||
| android-libutils @ 7.1.2_r36 | patch-headers Validate patch headers | libziparchive-add-includes.patch: patch lacks comment and upstream status | ||
| android-libsparse @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-remove-damaging-includes.patch: patch lacks comment and upstream status | ||
| android-libsparse @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-add-includes.patch: patch lacks comment and upstream status | ||
| android-libsparse @ 7.1.2_r36 | patch-headers Validate patch headers | adb-add-libraries.patch: patch lacks comment and upstream status | ||
| android-libsparse @ 7.1.2_r36 | patch-headers Validate patch headers | libziparchive-add-includes.patch: patch lacks comment and upstream status | ||
| android-liblog @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-remove-damaging-includes.patch: patch lacks comment and upstream status | ||
| android-liblog @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-add-includes.patch: patch lacks comment and upstream status | ||
| android-liblog @ 7.1.2_r36 | patch-headers Validate patch headers | adb-add-libraries.patch: patch lacks comment and upstream status | ||
| android-liblog @ 7.1.2_r36 | patch-headers Validate patch headers | libziparchive-add-includes.patch: patch lacks comment and upstream status | ||
| android-libcutils @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-remove-damaging-includes.patch: patch lacks comment and upstream status | ||
| android-libcutils @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-add-includes.patch: patch lacks comment and upstream status | ||
| android-libcutils @ 7.1.2_r36 | patch-headers Validate patch headers | adb-add-libraries.patch: patch lacks comment and upstream status | ||
| android-libcutils @ 7.1.2_r36 | patch-headers Validate patch headers | libziparchive-add-includes.patch: patch lacks comment and upstream status | ||
| adb @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-remove-damaging-includes.patch: patch lacks comment and upstream status | ||
| adb @ 7.1.2_r36 | patch-headers Validate patch headers | libutils-add-includes.patch: patch lacks comment and upstream status | ||
| adb @ 7.1.2_r36 | patch-headers Validate patch headers | adb-add-libraries.patch: patch lacks comment and upstream status | ||
| adb @ 7.1.2_r36 | patch-headers Validate patch headers | libziparchive-add-includes.patch: patch lacks comment and upstream status | ||
| tmux-themepack @ 1.1.0 | formatting Look for formatting issues in the source | line 93 is way too long (95 characters) | ||
| sdsl-lite @ 2.1.1 | formatting Look for formatting issues in the source | line 234 is way too long (145 characters) | ||
| sdl-mixer @ 1.2.12 | formatting Look for formatting issues in the source | line 258 is way too long (92 characters) | ||
| sdl-image @ 1.2.12 | formatting Look for formatting issues in the source | line 221 is way too long (91 characters) | ||
| sdl-gfx @ 2.0.26 | formatting Look for formatting issues in the source | line 211 is way too long (106 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) | ||
| r-bsgenome-dmelanogaster-ucsc-dm3-masked @ 1.3.99 | formatting Look for formatting issues in the source | line 275 is way too long (95 characters) | ||
| python2 @ 2.7.18 | formatting Look for formatting issues in the source | line 222 is way too long (99 characters) | ||
| purescript @ 0.14.5 | formatting Look for formatting issues in the source | line 121 is way too long (92 characters) | ||
| presentty @ 0.2.1 | formatting Look for formatting issues in the source | line 45 is way too long (117 characters) | ||
| podman @ 3.4.4 | formatting Look for formatting issues in the source | line 313 is way too long (99 characters) | ||
| podman @ 3.4.4 | formatting Look for formatting issues in the source | line 316 is way too long (94 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 194 is way too long (93 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 195 is way too long (93 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 220 is way too long (91 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 228 is way too long (93 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 250 is way too long (92 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 251 is way too long (96 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 256 is way too long (96 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 298 is way too long (91 characters) | ||
| php @ 7.4.26 | formatting Look for formatting issues in the source | line 311 is way too long (92 characters) | ||
| perl-test2-plugin-nowarnings @ 0.06 | formatting Look for formatting issues in the source | line 104 is way too long (92 characters) | ||
| opam @ 2.1.2 | formatting Look for formatting issues in the source | line 880 is way too long (99 characters) | ||
| opam @ 2.1.2 | formatting Look for formatting issues in the source | line 882 is way too long (99 characters) | ||
| opam @ 2.1.2 | formatting Look for formatting issues in the source | line 884 is way too long (99 characters) | ||
| opam @ 2.1.2 | formatting Look for formatting issues in the source | line 886 is way too long (102 characters) | ||
| 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) | ||
| node-serialport @ 9.2.7 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| netpbm @ 10.78.3 | formatting Look for formatting issues in the source | line 86 is way too long (127 characters) | ||
| ncurses @ 6.2.20210619 | 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) | ||
| mbedtls-apache @ 2.26.0 | formatting Look for formatting issues in the source | line 966 is way too long (96 characters) | ||
| mate-panel @ 1.24.1 | formatting Look for formatting issues in the source | line 641 is way too long (92 characters) | ||
| mate-menus @ 1.24.1 | formatting Look for formatting issues in the source | line 486 is way too long (91 characters) | ||
| lxqt-session @ 0.17.1 | formatting Look for formatting issues in the source | line 846 is way too long (92 characters) | ||
| lxqt-session @ 0.17.1 | formatting Look for formatting issues in the source | line 853 is way too long (100 characters) | ||
| lxqt-session @ 0.17.1 | formatting Look for formatting issues in the source | line 871 is way too long (98 characters) | ||
| lxde-common @ 0.99.2 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| libunibreak @ 5.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| libtomcrypt @ 1.18.2 | formatting Look for formatting issues in the source | line 366 is way too long (100 characters) | ||
| libsigsegv @ 2.13 | formatting Look for formatting issues in the source | line 48 is way too long (133 characters) | ||
| libetc1 @ 7.1.2_r36 | formatting Look for formatting issues in the source | tabulation on line 805, column 20 | ||
| libdaemon @ 0.14 | formatting Look for formatting issues in the source | line 38 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 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 296, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 298, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 300, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 302, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 304, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 306, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 308, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 310, column 18 | ||
| libchewing @ 0.5.1 | formatting Look for formatting issues in the source | tabulation on line 312, column 18 | ||
| julia-xorg-xcb-util-renderutil-jll @ 0.3.9+1 | formatting Look for formatting issues in the source | line 2428 is way too long (93 characters) | ||
| julia-libuuid-jll @ 2.36.0+0 | formatting Look for formatting issues in the source | line 1219 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) | ||
| julia @ 1.6.3 | formatting Look for formatting issues in the source | line 238 is way too long (107 characters) | ||
| julia @ 1.6.3 | formatting Look for formatting issues in the source | line 240 is way too long (106 characters) | ||
| julia @ 1.6.3 | formatting Look for formatting issues in the source | line 454 is way too long (101 characters) | ||
| julia @ 1.6.3 | formatting Look for formatting issues in the source | line 459 is way too long (124 characters) | ||
| java-jbzip2 @ 0.9.1 | formatting Look for formatting issues in the source | line 277 is way too long (92 characters) | ||
| irods-client-icommands @ 4.2.8 | formatting Look for formatting issues in the source | line 235 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 132 is way too long (91 characters) | ||
| hyperledger-iroha @ 1.1.1 | formatting Look for formatting issues in the source | line 166 is way too long (105 characters) | ||
| guile-sdl @ 0.5.3 | formatting Look for formatting issues in the source | line 609 is way too long (111 characters) | ||
| guile @ 2.0.14 | formatting Look for formatting issues in the source | line 205 is way too long (94 characters) | ||
| guile @ 2.0.14 | formatting Look for formatting issues in the source | line 208 is way too long (93 characters) | ||
| gmp @ 6.2.1 | formatting Look for formatting issues in the source | line 83 is way too long (96 characters) | ||
| ghc-quickcheck-classes-base @ 0.6.2.0 | formatting Look for formatting issues in the source | line 1113 is way too long (101 characters) | ||
| ghc-quickcheck-classes @ 0.6.5.0 | formatting Look for formatting issues in the source | line 1069 is way too long (91 characters) | ||
| 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-doctest-exitcode-stdio @ 0.0 | formatting Look for formatting issues in the source | line 1174 is way too long (99 characters) | ||
| ghc-base-unicode-symbols @ 0.2.4.2 | formatting Look for formatting issues in the source | line 938 is way too long (93 characters) | ||
| ghc-base-unicode-symbols @ 0.2.4.2 | formatting Look for formatting issues in the source | line 952 is way too long (101 characters) | ||
| flite @ 2.2 | formatting Look for formatting issues in the source | line 93 is way too long (419 characters) | ||
| fastboot @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 718 is way too long (105 characters) | ||
| etc1tool @ 7.1.2_r36 | formatting Look for formatting issues in the source | tabulation on line 852, column 20 | ||
| etc1tool @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 880 is way too long (98 characters) | ||
| efitools @ 1.9.2 | formatting Look for formatting issues in the source | line 211 is way too long (113 characters) | ||
| dejagnu @ 1.6.2 | formatting Look for formatting issues in the source | line 60 is way too long (91 characters) | ||
| cryptsetup-static @ 2.3.7 | formatting Look for formatting issues in the source | line 110 is way too long (93 characters) | ||
| cni-plugins @ 1.0.1 | formatting Look for formatting issues in the source | line 249 is way too long (93 characters) | ||
| cloudflare-cli @ 0.0.0-1.2d986d3 | formatting Look for formatting issues in the source | line 122 is way too long (92 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 412 is way too long (94 characters) | ||
| axoloti-patcher-next @ 2.0.0 | formatting Look for formatting issues in the source | line 558 is way too long (93 characters) | ||
| axoloti-patcher-next @ 2.0.0 | formatting Look for formatting issues in the source | line 571 is way too long (103 characters) | ||
| atril @ 1.24.0 | formatting Look for formatting issues in the source | line 714 is way too long (92 characters) | ||
| android-safe-iop @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 460 is way too long (95 characters) | ||
| android-platform-frameworks-native-headers @ 7.1.2_r36 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| android-libutils @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 660 is way too long (114 characters) | ||
| android-libcutils @ 7.1.2_r36 | formatting Look for formatting issues in the source | tabulation on line 305, column 20 | ||
| adb @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 413 is way too long (97 characters) | ||
| perl-crypt-unixcrypt_xs @ 0.11 | name Validate package names | name should use hyphens instead of underscores | ||
| shell-functools @ 0.3.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 121, 206 | ||
| 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-ctr @ 0.8.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 77 | ||
| rust-ctr @ 0.6.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 77 | ||
| rust-charset @ 0.1.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| rust-bugreport @ 0.4.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| rust-bugreport @ 0.3.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| rust-avif-serialize @ 0.6.5 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| python-rpy2 @ 3.4.5 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-pytools @ 2021.2.7 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ppsspp @ 1.12.3 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| 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 | ||
| julia-chainrulestestutils @ 1.2.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 260 | ||
| 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 | ||
| go-github.com-smartystreets-goconvey @ 1.6.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 33 | ||
| perl-extutils-pkgconfig @ 1.16 | inputs-should-be-native Identify inputs that should be native inputs | 'pkg-config' should probably be a native input | ||
| mig @ 1.8 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| libmediaart @ 1.9.5 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| labplot @ 2.8.2 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| kmix @ 20.04.1 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| kdevelop @ 5.6.1 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| kdenlive @ 21.12.3 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| juk @ 20.04.1 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| gnome-contacts @ 40.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' 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' | ||
| clojure-tools-deps-alpha @ 0.12.1104 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs java-sonatype-oss-parent-pom@7 and java-sonatype-oss-parent-pom@9 collide | ||
| sed @ 4.8 | 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 | ||
| grantleetheme @ 20.04.1 | 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.37 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile-git @ 0.5.2 | patch-headers Validate patch headers | guile-git-adjust-for-libgit2-1.2.0.patch: patch lacks comment and upstream status | ||
| xmlrpc-c @ 1.43.08 | formatting Look for formatting issues in the source | line 2353 is way too long (91 characters) | ||
| tesseract-ocr @ 4.1.1-1.97079fa | formatting Look for formatting issues in the source | line 122 is way too long (93 characters) | ||
| telegram-desktop @ 2.9.3 | formatting Look for formatting issues in the source | line 352 is way too long (93 characters) | ||
| rust-winit @ 0.20.0-alpha6 | formatting Look for formatting issues in the source | line 2988 is way too long (114 characters) | ||
| ruby-iruby @ 0.3 | formatting Look for formatting issues in the source | line 506 is way too long (112 characters) | ||
| mumble @ 1.4.230 | formatting Look for formatting issues in the source | tabulation on line 583, column 0 | ||
| mumble @ 1.4.230 | formatting Look for formatting issues in the source | tabulation on line 584, column 0 | ||
| mumble @ 1.4.230 | formatting Look for formatting issues in the source | tabulation on line 585, column 0 | ||
| 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 | ||
| guile2.2-readline @ 2.2.7 | formatting Look for formatting issues in the source | line 506 is way too long (94 characters) | ||
| guile-readline @ 3.0.7 | formatting Look for formatting issues in the source | line 506 is way too long (94 characters) | ||
| guile-for-guile-emacs @ 2.1.2-1.15ca784 | formatting Look for formatting issues in the source | line 585 is way too long (96 characters) | ||
| gnome-initial-setup @ 40.4 | formatting Look for formatting issues in the source | line 1502 is way too long (91 characters) | ||
| glibc @ 2.33 | formatting Look for formatting issues in the source | line 810 is way too long (98 characters) | ||
| ghc @ 8.6.5 | formatting Look for formatting issues in the source | line 865 is way too long (91 characters) | ||
| ghc @ 8.10.7 | formatting Look for formatting issues in the source | line 992 is way too long (93 characters) | ||
| ghc @ 8.10.7 | formatting Look for formatting issues in the source | line 998 is way too long (92 characters) | ||
| ghc @ 4.08.2 | formatting Look for formatting issues in the source | line 330 is way too long (93 characters) | ||
| ghc @ 4.08.2 | formatting Look for formatting issues in the source | line 331 is way too long (91 characters) | ||
| clojure-tools-deps-alpha @ 0.12.1104 | formatting Look for formatting issues in the source | line 500 is way too long (94 characters) | ||
| clojure-data-xml @ 0.2.0-alpha6 | formatting Look for formatting issues in the source | line 341 is way too long (93 characters) | ||
| clojure-data-xml @ 0.2.0-alpha6 | formatting Look for formatting issues in the source | line 342 is way too long (91 characters) | ||
| cc65 @ 2.19 | formatting Look for formatting issues in the source | line 2490 is way too long (167 characters) | ||
| python-joblib @ 1.1.0 | formatting Look for formatting issues in the source | line 4149 is way too long (91 characters) | ||
| python-joblib @ 1.1.0 | formatting Look for formatting issues in the source | line 4150 is way too long (94 characters) | ||
| python-djvulibre @ 0.8.6 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| python-ccm @ 2.1.6 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 84 | ||
| ghc-unsafe @ 0.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ghc-th-reify-many @ 0.1.10 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| 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-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-doclayout @ 0.3.1.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-commonmark @ 0.2.1.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 630 | ||
| ghc-xdg-basedir @ 0.2.2 | formatting Look for formatting issues in the source | line 14679 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-th-orphans @ 0.13.12 | formatting Look for formatting issues in the source | line 13007 is way too long (92 characters) | ||
| ghc-template-haskell-compat-v0208 @ 0.1.6 | formatting Look for formatting issues in the source | line 15580 is way too long (111 characters) | ||
| ghc-persistent-postgresql @ 2.13.2.1 | formatting Look for formatting issues in the source | line 15893 is way too long (95 characters) | ||
| ghc-optparse-applicative @ 0.15.1.0 | formatting Look for formatting issues in the source | line 8743 is way too long (95 characters) | ||
| ghc-indexed-traversable @ 0.1.1 | formatting Look for formatting issues in the source | line 14944 is way too long (91 characters) | ||
| ghc-hspec-expectations-lifted @ 0.10.0 | formatting Look for formatting issues in the source | line 15773 is way too long (103 characters) | ||
| ghc-commonmark-extensions @ 0.2.2 | formatting Look for formatting issues in the source | line 15355 is way too long (95 characters) | ||
| libsecp256k1 @ 20200615-1.dbd41db | formatting Look for formatting issues in the source | line 1120 is way too long (103 characters) | ||
| mumble @ 1.4.230 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| gcompris @ 17.05 | formatting Look for formatting issues in the source | line 142 is way too long (96 characters) | ||
| util-linux-with-udev @ 2.37.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| unbound @ 1.13.2 | formatting Look for formatting issues in the source | trailing white space on line 748 | ||
| unbound @ 1.13.2 | formatting Look for formatting issues in the source | trailing white space on line 784 | ||
| 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-aeson-qq @ 0.8.4 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-language-javascript @ 0.7.1.0 | formatting Look for formatting issues in the source | line 1932 is way too long (91 characters) | ||
| ghc-hxt-unicode @ 9.0.2.4 | formatting Look for formatting issues in the source | line 1484 is way too long (91 characters) | ||
| verilator @ 4.204 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| abc @ 0.0-1.5ae4b97 | formatting Look for formatting issues in the source | line 97 is way too long (95 characters) | ||
| config @ 0.0.0-1.c8ddc84 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| libtool @ 2.4.7 | 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 641 is way too long (92 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 | ||
| rust-funty @ 1.2.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 127 | ||
| rust-funty @ 1.1.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 127 | ||
| rust-crates-index-5 @ 0.5.1 | inputs-should-be-native Identify inputs that should be native inputs | 'cmake' should probably be a native input | ||
| rust-crates-index-5 @ 0.5.1 | formatting Look for formatting issues in the source | line 13794 is way too long (91 characters) | ||
| marble-qt @ 21.12.3 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| kuserfeedback @ 1.0.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| thunar @ 4.16.10 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| parole @ 4.16.0 | inputs-should-be-native Identify inputs that should be native inputs | 'glib:bin' should probably be a native input | ||
| fcitx5-gtk4 @ 5.0.9 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| fcitx5-gtk @ 5.0.9 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| xfce4-clipman-plugin @ 1.6.2 | formatting Look for formatting issues in the source | line 476 is way too long (91 characters) | ||
| volctl @ 0.8.2 | formatting Look for formatting issues in the source | line 2887 is way too long (98 characters) | ||
| tumbler @ 4.16.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| 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-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 | ||
| 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 | ||
| genimage @ 15-1.ec44ae0 | patch-headers Validate patch headers | genimage-mke2fs-test.patch: patch lacks comment and upstream status | ||
| python-amply @ 0.1.4 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| 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 | ||
| udiskie @ 2.3.3 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| plymouth @ 0.9.5 | formatting Look for formatting issues in the source | line 2105 is way too long (91 characters) | ||
| swaks @ 20201014.0 | formatting Look for formatting issues in the source | line 3642 is way too long (106 characters) | ||
| jfs_fsck-static @ 1.1.15 | name Validate package names | name should use hyphens instead of underscores | ||
| 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 | ||
| xfce4-volumed-pulse @ 0.2.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 65, 112 | ||
| zeitgeist @ 1.0.4 | formatting Look for formatting issues in the source | tabulation on line 771, column 18 | ||
| zeitgeist @ 1.0.4 | formatting Look for formatting issues in the source | tabulation on line 774, column 18 | ||
| knotes @ 20.04.1 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| idris @ 1.3.4 | formatting Look for formatting issues in the source | line 102 is way too long (100 characters) | ||
| python-xsge @ 2020.09.07 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| nss-certs @ 3.71 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| cawbird @ 1.4.2 | formatting Look for formatting issues in the source | line 88 is way too long (104 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-qcheck @ 0.18.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 52, 156 | ||
| ocaml-down @ 0.1.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ocaml-ounit @ 2.2.6 | formatting Look for formatting issues in the source | line 1427 is way too long (97 characters) | ||
| nginx-accept-language-module @ 0.0.0-1.2f69842 | formatting Look for formatting issues in the source | line 624 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 | ||
| infamous-plugins @ 0.3.0 | formatting Look for formatting issues in the source | line 1143 is way too long (104 characters) | ||
| faad2 @ 2.8.8 | formatting Look for formatting issues in the source | line 1874 is way too long (95 characters) | ||
| audacity @ 3.1.3 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| libxcrypt @ 4.4.28 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 62 | ||
| itcl @ 4.2.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| mescc-tools-static-stripped-tarball @ 1.4.0 | derivation Report failure to compile a package to a derivation | failed to create riscv32-linux derivation: could not find bootstrap binary 'tar' for system 'riscv32-linux' | ||
| mescc-tools @ 1.4.0 | derivation Report failure to compile a package to a derivation | failed to create riscv32-linux derivation: could not find bootstrap binary 'tar' for system 'riscv32-linux' | ||
| cups-minimal @ 2.3.3op2 | formatting Look for formatting issues in the source | tabulation on line 290, column 0 | ||
| cups-minimal @ 2.3.3op2 | formatting Look for formatting issues in the source | tabulation on line 291, column 0 | ||
| cups-minimal @ 2.3.3op2 | formatting Look for formatting issues in the source | tabulation on line 292, column 0 | ||
| cups-minimal @ 2.3.3op2 | formatting Look for formatting issues in the source | tabulation on line 293, column 0 | ||
| 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 | ||
| ruby-rb-inotify @ 0.9.10 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ruby-tzinfo-data @ 1.2021.1 | formatting Look for formatting issues in the source | line 5731 is way too long (101 characters) | ||
| ruby-tzinfo-data @ 1.2021.1 | formatting Look for formatting issues in the source | line 5732 is way too long (107 characters) | ||
| ruby-asciidoctor-pdf @ 1.6.1 | formatting Look for formatting issues in the source | line 1852 is way too long (97 characters) | ||
| rust-juliex @ 0.3.0-alpha.8 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| rust-is-debug @ 1.0.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| js-mathjax @ 3.2.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| js-mathjax @ 3.2.0 | formatting Look for formatting issues in the source | line 234 is way too long (92 characters) | ||
| js-mathjax @ 3.2.0 | formatting Look for formatting issues in the source | line 275 is way too long (92 characters) | ||
| js-mathjax @ 2.7.2 | formatting Look for formatting issues in the source | line 156 is way too long (91 characters) | ||
| chez-scheme-for-racket-bootstrap-bootfiles @ 9.5.7.6 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| python-mutatormath @ 3.0.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 129 | ||
| python-jupyterlab-widgets @ 1.0.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-sphinx @ 4.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-docrepr @ 0.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-docrepr @ 0.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| 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.12.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 | ||
| propeller-gcc @ 6.0.0-1.b4f45a472 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| propeller-gcc @ 4.6.1-2.4c46ecbe7 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-cross-sans-libc-arm-none-eabi @ 7-2018-q2-update-1.261907 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| t1lib @ 5.1.2 | patch-headers Validate patch headers | t1lib-CVE-2010-2642.patch: patch lacks comment and upstream status | ||
| zathura-pdf-poppler @ 0.3.0 | formatting Look for formatting issues in the source | line 575 is way too long (107 characters) | ||
| zathura-djvu @ 0.2.9 | formatting Look for formatting issues in the source | line 490 is way too long (93 characters) | ||
| python-libmpsse @ 1.4.1 | formatting Look for formatting issues in the source | line 1135 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 | ||
| gcc-cross-sans-libc-arm-none-eabi @ 7-2018-q2-update-1.261907 | formatting Look for formatting issues in the source | line 345 is way too long (99 characters) | ||
| fdroidserver @ 1.1.9 | formatting Look for formatting issues in the source | line 1157 is way too long (106 characters) | ||
| guile2.2-gnutls @ 3.7.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.0-gnutls @ 3.7.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gnutls-dane @ 3.7.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-cmake-mode @ 3.21.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| cmake @ 3.21.4 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| emacs-wide-int @ 28.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-libxml2 @ 2.9.12 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libxml2-xpath0 @ 2.9.12 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| sbcl-trivial-gray-streams @ 2.0-1.2b3823e | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 75 | ||
| ecl-trivial-gray-streams @ 2.0-1.2b3823e | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 75 | ||
| cl-trivial-gray-streams @ 2.0-1.2b3823e | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 75 | ||
| sbcl-net.didierverna.asdf-flv @ 2.1 | formatting Look for formatting issues in the source | line 313 is way too long (96 characters) | ||
| ecl-net.didierverna.asdf-flv @ 2.1 | formatting Look for formatting issues in the source | line 313 is way too long (96 characters) | ||
| cl-net.didierverna.asdf-flv @ 2.1 | formatting Look for formatting issues in the source | line 313 is way too long (96 characters) | ||
| guile-zstd @ 0.1.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| superstarfighter @ 0.6.5 | formatting Look for formatting issues in the source | line 2602 is way too long (115 characters) | ||
| sane-airscan @ 0.99.27 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| 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 | ||
| lua-tablepool @ 0.01 | formatting Look for formatting issues in the source | line 1075 is way too long (100 characters) | ||
| lua-resty-signal @ 0.02 | formatting Look for formatting issues in the source | line 1040 is way too long (104 characters) | ||
| lua-resty-signal @ 0.02 | formatting Look for formatting issues in the source | line 1041 is way too long (93 characters) | ||
| lua-resty-signal @ 0.02 | formatting Look for formatting issues in the source | line 1042 is way too long (123 characters) | ||
| lua-resty-signal @ 0.02 | formatting Look for formatting issues in the source | line 1043 is way too long (112 characters) | ||
| lua-resty-shell @ 0.03 | formatting Look for formatting issues in the source | line 1107 is way too long (100 characters) | ||
| lua-resty-shell @ 0.03 | formatting Look for formatting issues in the source | line 1109 is way too long (119 characters) | ||
| lua-resty-shell @ 0.03 | formatting Look for formatting issues in the source | line 1110 is way too long (108 characters) | ||
| lua-resty-lrucache @ 0.10 | formatting Look for formatting issues in the source | line 1000 is way too long (100 characters) | ||
| lua-resty-lrucache @ 0.10 | formatting Look for formatting issues in the source | line 1002 is way too long (119 characters) | ||
| lua-resty-lrucache @ 0.10 | formatting Look for formatting issues in the source | line 1003 is way too long (108 characters) | ||
| lua-resty-core @ 0.1.18 | formatting Look for formatting issues in the source | line 965 is way too long (95 characters) | ||
| emilua @ 0.3.2 | formatting Look for formatting issues in the source | line 1162 is way too long (102 characters) | ||
| mergerfs @ 2.33.5 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| sonata @ 1.7.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| mpdris2 @ 0.9.1 | formatting Look for formatting issues in the source | line 427 is way too long (96 characters) | ||
| wine64-staging @ 7.8 | inputs-should-be-native Identify inputs that should be native inputs | 'autoconf' should probably be a native input | ||
| wine-staging @ 7.8 | inputs-should-be-native Identify inputs that should be native inputs | 'autoconf' should probably be a native input | ||
| elm-terezka-intervals @ 2.0.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| elm-sans-reactor @ 0.19.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| unzip @ 6.0 | patch-headers Validate patch headers | unzip-case-insensitive.patch: patch lacks comment and upstream status | ||
| unzip @ 6.0 | patch-headers Validate patch headers | unzip-CVE-2018-1000035.patch: patch lacks comment and upstream status | ||
| unzip @ 6.0 | patch-headers Validate patch headers | unzip-CVE-2018-18384.patch: patch lacks comment and upstream status | ||
| unzip @ 6.0 | patch-headers Validate patch headers | unzip-manpage-fix.patch: patch lacks comment and upstream status | ||
| unzip @ 6.0 | patch-headers Validate patch headers | unzip-overflow.patch: patch lacks comment and upstream status | ||
| unzip @ 6.0 | patch-headers Validate patch headers | unzip-valgrind.patch: patch lacks comment and upstream status | ||
| unzip @ 6.0 | patch-headers Validate patch headers | unzip-x-option.patch: patch lacks comment and upstream status | ||
| p7zip @ 16.02 | patch-headers Validate patch headers | p7zip-remove-unused-code.patch: patch lacks comment and upstream status | ||
| minizip @ 1.2.11 | formatting Look for formatting issues in the source | line 168 is way too long (115 characters) | ||
| elm-sans-reactor @ 0.19.1 | formatting Look for formatting issues in the source | line 72 is way too long (98 characters) | ||
| brotli @ 1.0.9 | formatting Look for formatting issues in the source | line 2160 is way too long (94 characters) | ||
| 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 | ||
| python-faiss @ 1.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'swig' should probably be a native input | ||
| python-louvain @ 0.16 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| glibc-bootstrap @ 0 | formatting Look for formatting issues in the source | line 772 is way too long (100 characters) | ||
| gcc-bootstrap @ 0 | formatting Look for formatting issues in the source | line 878 is way too long (100 characters) | ||
| espeak-ng @ 1.51 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| libiberty @ 10.3.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 @ 11.3.0 | 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++ @ 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 @ 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 | ||
| busybox @ 1.34.1 | formatting Look for formatting issues in the source | line 91 is way too long (92 characters) | ||
| adcli @ 0.9.1 | formatting Look for formatting issues in the source | line 97 is way too long (95 characters) | ||
| chez-scheme-bootstrap-bootfiles @ 9.5.8 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| conda @ 4.10.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| laminar @ 1.1 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| laminar @ 1.1 | formatting Look for formatting issues in the source | line 221 is way too long (97 characters) | ||
| laminar @ 1.1 | formatting Look for formatting issues in the source | line 223 is way too long (137 characters) | ||
| guile-wm @ 1.0-1.f3c7b3b | formatting Look for formatting issues in the source | line 130 is way too long (92 characters) | ||
| r-dplyr @ 1.0.9 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-boot @ 1.3-28 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 125, 142 | ||
| r-hsmmsinglecell @ 1.16.0 | formatting Look for formatting issues in the source | line 1422 is way too long (95 characters) | ||
| pbuilder @ 0.231 | formatting Look for formatting issues in the source | line 499 is way too long (103 characters) | ||
| guile-wiredtiger @ 0.7.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| libgccjit @ 9.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc++ @ 9.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc @ 9.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libgccjit @ 9.5.0 | patch-headers Validate patch headers | gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status | ||
| gcc-objc++ @ 9.5.0 | patch-headers Validate patch headers | gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status | ||
| gcc-objc @ 9.5.0 | patch-headers Validate patch headers | gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status | ||
| gcc @ 9.5.0 | patch-headers Validate patch headers | gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status | ||
| onionshare @ 2.4 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| zn-poly @ 0.9.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ucsim @ 0.7.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-uqbar @ 0.5.6 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinxcontrib-svg2pdfconverter @ 1.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinxcontrib-programoutput @ 0.17 | 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-panels @ 0.6.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-sphinx-panels @ 0.6.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx-copybutton @ 0.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx-click @ 4.0.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-sphinx-click @ 4.0.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| 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 | ||
| libmypaint @ 1.6.1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| dico @ 2.11 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| 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 | ||
| 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 | ||
| python-openapi-spec-validator @ 0.4.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 | ||
| gnupg @ 2.2.32 | mirror-url Suggest 'mirror://' URLs | URL should be 'mirror://gnupg/gnupg/gnupg-2.2.32.tar.bz2' | ||
| python2-minimal @ 2.7.18 | 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 | ||
| python-minimal @ 3.9.9 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| ratpoints @ 2.1.3 | patch-headers Validate patch headers | ratpoints-sturm_and_rp_private.patch: patch lacks comment and upstream status | ||
| ocaml-dose3 @ 5.0.1 | patch-headers Validate patch headers | ocaml-dose3-dont-make-printconf.patch: patch lacks comment and upstream status | ||
| gourmet @ 0.17.4-0.8af29c8 | patch-headers Validate patch headers | gourmet-sqlalchemy-compat.patch: patch lacks comment and upstream status | ||
| aegis @ 4.24 | patch-headers Validate patch headers | aegis-perl-tempdir2.patch: patch lacks comment and upstream status | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 402, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 404, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 407, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 408, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 417, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 418, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 419, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 420, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 421, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 422, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 423, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 425, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 426, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 427, column 0 | ||
| patchwork @ 3.0.4 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| ocaml-dose3 @ 5.0.1 | formatting Look for formatting issues in the source | line 655 is way too long (92 characters) | ||
| libgit2 @ 1.4.3 | formatting Look for formatting issues in the source | line 795 is way too long (96 characters) | ||
| java-xom @ 127 | formatting Look for formatting issues in the source | trailing white space on line 1902 | ||
| git-crypt @ 0.6.0 | formatting Look for formatting issues in the source | line 924 is way too long (91 characters) | ||
| gimp-resynthesizer @ 2.0.3 | formatting Look for formatting issues in the source | line 508 is way too long (107 characters) | ||
| fc-host-tools @ 15 | formatting Look for formatting issues in the source | line 1225 is way too long (122 characters) | ||
| cairo @ 1.16.0 | formatting Look for formatting issues in the source | tabulation on line 167, column 0 | ||
| cairo @ 1.16.0 | formatting Look for formatting issues in the source | tabulation on line 168, column 0 | ||
| glibc-locales-2.32 @ 2.32 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| glibc-locales-2.31 @ 2.31 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| glibc-locales-2.30 @ 2.30 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| 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.33 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| glibc-hurd-headers @ 2.33 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| freedink-engine @ 109.6 | formatting Look for formatting issues in the source | tabulation on line 3338, column 0 | ||
| 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 | ||
| libextractor @ 1.11 | formatting Look for formatting issues in the source | line 133 is way too long (140 characters) | ||
| cockatrice @ 2.8.0 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| bsd-games @ 2.17.0 | patch-headers Validate patch headers | bsd-games-bad-ntohl-cast.patch: patch lacks comment and upstream status | ||
| bsd-games @ 2.17.0 | patch-headers Validate patch headers | bsd-games-gamescreen.h.patch: patch lacks comment and upstream status | ||
| bsd-games @ 2.17.0 | patch-headers Validate patch headers | bsd-games-null-check.patch: patch lacks comment and upstream status | ||
| gnubg @ 1.06.002 | formatting Look for formatting issues in the source | line 1848 is way too long (91 characters) | ||
| cataclysm-dda @ 0.F-3 | formatting Look for formatting issues in the source | line 915 is way too long (94 characters) | ||
| texlive-lm @ 59745 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 93 | ||
| texlive-libkpathsea @ 20210325 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| texlive-fonts-latex @ 59745 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 78 | ||
| texlive-mflogo @ 59745 | formatting Look for formatting issues in the source | line 1395 is way too long (95 characters) | ||
| rcm @ 1.3.5 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 183 | ||
| papi @ 6.0.0.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| crun @ 1.4.5 | formatting Look for formatting issues in the source | line 78 is way too long (98 characters) | ||
| minetest-basic-trains @ 1.0.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| cscope @ 15.9 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 50 | ||
| python-trezor-agent @ 0.14.4 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| openfoam @ 4.1 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| electron-cash @ 4.2.10 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| monero @ 0.17.3.2 | patch-headers Validate patch headers | monero-use-system-miniupnpc.patch: patch lacks comment and upstream status | ||
| openfoam @ 4.1 | formatting Look for formatting issues in the source | line 136 is way too long (109 characters) | ||
| openfoam @ 4.1 | formatting Look for formatting issues in the source | line 150 is way too long (91 characters) | ||
| cdecl @ 2.5 | formatting Look for formatting issues in the source | line 994 is way too long (95 characters) | ||
| cdecl @ 2.5 | formatting Look for formatting issues in the source | line 995 is way too long (97 characters) | ||
| cdecl @ 2.5 | formatting Look for formatting issues in the source | line 998 is way too long (93 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 1947, column 0 | ||
| xftwidth @ 20170402 | formatting Look for formatting issues in the source | tabulation on line 1948, column 0 | ||
| xftwidth @ 20170402 | formatting Look for formatting issues in the source | tabulation on line 1950, column 0 | ||
| xftwidth @ 20170402 | formatting Look for formatting issues in the source | tabulation on line 1951, column 0 | ||
| openmpi-thread-multiple @ 4.1.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| openmpi-c++ @ 4.1.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-openmpi @ 4.1.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| openmpi @ 4.1.4 | formatting Look for formatting issues in the source | line 263 is way too long (94 characters) | ||
| openmpi @ 4.1.4 | formatting Look for formatting issues in the source | line 265 is way too long (96 characters) | ||
| mrrescue @ 1.02e | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 2 | ||
| chroma @ 1.20 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 33 | ||
| fifengine @ 0.4.2 | inputs-should-be-native Identify inputs that should be native inputs | 'swig' should probably be a native input | ||
| irrlicht-for-minetest @ 1.9.0mt5 | source-file-name Validate file names of sources | the source file name should contain the package name | ||
| crawl-tiles @ 0.28.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| tuxpaint @ 0.9.23 | patch-headers Validate patch headers | tuxpaint-stamps-path.patch: patch lacks comment and upstream status | ||
| supertux @ 0.6.3 | patch-headers Validate patch headers | supertux-unbundle-squirrel.patch: patch lacks comment and upstream status | ||
| pinball @ 0.3.20201218 | patch-headers Validate patch headers | pinball-system-ltdl.patch: patch lacks comment and upstream status | ||
| gzdoom @ 4.3.2 | patch-headers Validate patch headers | gzdoom-find-system-libgme.patch: patch lacks comment and upstream status | ||
| einstein @ 2.0 | formatting Look for formatting issues in the source | line 4817 is way too long (96 characters) | ||
| 0ad @ 0.0.25b-alpha | formatting Look for formatting issues in the source | line 6739 is way too long (91 characters) | ||
| python-distributed @ 2022.05.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-vedo @ 2022.2.0 | formatting Look for formatting issues in the source | line 737 is way too long (124 characters) | ||
| python-pyvista @ 0.34.0 | formatting Look for formatting issues in the source | line 1216 is way too long (122 characters) | ||
| rsyslog @ 8.2204.1 | formatting Look for formatting issues in the source | trailing white space on line 268 | ||
| rsyslog @ 8.2204.1 | formatting Look for formatting issues in the source | trailing white space on line 280 | ||
| abseil-cpp @ 20200923.3 | formatting Look for formatting issues in the source | line 997 is way too long (116 characters) | ||
| abseil-cpp @ 20200923.3 | formatting Look for formatting issues in the source | line 998 is way too long (144 characters) | ||
| c-blosc @ 1.21.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 64 | ||
| efi_analyzer @ 0.0.0-0.77c9e3a | name Validate package names | name should use hyphens instead of underscores | ||
| texlive-fonts-lm @ 59745 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 93 | ||
| curl-minimal @ 7.79.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-abjad @ 3.4 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-abjad @ 3.4 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest-cov' 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 | ||
| g-golf @ 0.1.0-1010.1824633 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python-trytond @ 6.0.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| perl-parent @ 5.34.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| perl-base @ 5.34.0 | 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 | ||
| libringclient @ 20211223.2.37be4c3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libring @ 20211223.2.37be4c3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| jami-qt @ 20211223.2.37be4c3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.2-git @ 0.5.2 | 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-git @ 0.5.2 | 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 | ||
| elm-compiler @ 0.19.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| curl-minimal @ 7.79.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| bazaar @ 3.2.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.2-git @ 0.5.2 | patch-headers Validate patch headers | guile-git-adjust-for-libgit2-1.2.0.patch: patch lacks comment and upstream status | ||
| guile2.0-git @ 0.5.2 | patch-headers Validate patch headers | guile-git-adjust-for-libgit2-1.2.0.patch: patch lacks comment and upstream status | ||
| ublock-origin-chromium @ 1.43.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| texlive-latex-tocloft @ 59745 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 173 | ||
| texlive-latex-l3backend @ 59745 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 124, 199 | ||
| texlive-latex-cyrillic @ 59745 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 166 | ||
| texlive-hyphen-occitan @ 59745 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| texlive-hyphen-latin @ 59745 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| texlive-fonts-iwona @ 0.995b | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 42 | ||
| r-tidyr @ 1.2.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-minqa @ 1.2.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 133, 136, 139 | ||
| r-esc @ 0.5.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 178 | ||
| r-datasaurus @ 0.1.6 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-cardata @ 3.0-5 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 45, 56 | ||
| python-fpylll @ 0.5.7 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| perftest @ 4.4-0.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 99 | ||
| f2fs-fsck-static @ 1.14.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 91 | ||
| python-fpylll @ 0.5.7 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| python-fpylll @ 0.5.7 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| plasma-framework @ 5.70.1 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| nyxt @ 2.2.4 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| libchamplain @ 0.12.20 | inputs-should-be-native Identify inputs that should be native inputs | 'glib:bin' should probably be a native input | ||
| kwallet @ 5.70.0 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| kservice @ 5.70.0 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| kpackage @ 5.70.0 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| kio @ 5.70.1 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| kinit @ 5.70.0 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| kdesignerplugin @ 5.70.0 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| kdelibs4support @ 5.70.0 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| kdelibs4support @ 5.70.0 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' should probably be a native input | ||
| kded @ 5.70.0 | inputs-should-be-native Identify inputs that should be native inputs | 'kdoctools' 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 | ||
| geoclue @ 2.5.7 | inputs-should-be-native Identify inputs that should be native inputs | 'glib:bin' should probably be a native input | ||
| docbook2x @ 0.8.8 | inputs-should-be-native Identify inputs that should be native inputs | 'texinfo' should probably be a native input | ||
| colord-minimal @ 1.4.5 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| colord @ 1.4.5 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| qemu-minimal @ 6.2.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| polkit-duktape @ 0.120 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| openssh-sans-x @ 8.9p1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mesa-opencl-icd @ 21.3.8 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mesa-opencl @ 21.3.8 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mesa-headers @ 21.3.8 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| js-mathjax @ 3.1.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-xwidgets @ 28.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-no-x-toolkit @ 28.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-no-x @ 28.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-next-pgtk @ 29.0.50-1.0a5477b | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-next @ 29.0.50-1.0a5477b | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-minimal @ 28.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| kpackage @ 5.70.0 | patch-headers Validate patch headers | kpackage-allow-external-paths.patch: patch lacks comment and upstream status | ||
| xlispstat @ 3.52.23-0.f1bea60 | formatting Look for formatting issues in the source | tabulation on line 6952, column 0 | ||
| xlispstat @ 3.52.23-0.f1bea60 | formatting Look for formatting issues in the source | tabulation on line 6953, column 0 | ||
| xlispstat @ 3.52.23-0.f1bea60 | formatting Look for formatting issues in the source | tabulation on line 6954, column 0 | ||
| xlispstat @ 3.52.23-0.f1bea60 | formatting Look for formatting issues in the source | tabulation on line 6955, column 0 | ||
| xlispstat @ 3.52.23-0.f1bea60 | formatting Look for formatting issues in the source | tabulation on line 6957, column 0 | ||
| xlispstat @ 3.52.23-0.f1bea60 | formatting Look for formatting issues in the source | tabulation on line 6958, column 0 | ||
| xlispstat @ 3.52.23-0.f1bea60 | formatting Look for formatting issues in the source | tabulation on line 6959, column 0 | ||
| upower @ 0.99.15 | formatting Look for formatting issues in the source | line 5362 is way too long (101 characters) | ||
| texlive-stringenc @ 59745 | formatting Look for formatting issues in the source | line 3797 is way too long (94 characters) | ||
| texlive-stringenc @ 59745 | formatting Look for formatting issues in the source | line 3799 is way too long (101 characters) | ||
| texlive-stringenc @ 59745 | formatting Look for formatting issues in the source | line 3800 is way too long (104 characters) | ||
| texlive-stringenc @ 59745 | formatting Look for formatting issues in the source | line 3802 is way too long (94 characters) | ||
| texlive-stmaryrd @ 59745 | formatting Look for formatting issues in the source | line 6859 is way too long (98 characters) | ||
| texlive-ruhyphen @ 59745 | formatting Look for formatting issues in the source | line 2677 is way too long (92 characters) | ||
| texlive-ruhyphen @ 59745 | formatting Look for formatting issues in the source | line 2680 is way too long (93 characters) | ||
| texlive-pgf @ 59745 | formatting Look for formatting issues in the source | line 8437 is way too long (98 characters) | ||
| texlive-latex-l3packages @ 59745 | formatting Look for formatting issues in the source | line 3641 is way too long (93 characters) | ||
| texlive-latex-l3packages @ 59745 | formatting Look for formatting issues in the source | line 3650 is way too long (91 characters) | ||
| texlive-latex-l3packages @ 59745 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| texlive-latex-base @ 59745 | formatting Look for formatting issues in the source | tabulation on line 2849, column 22 | ||
| texlive-hyph-utf8 @ 59745 | formatting Look for formatting issues in the source | line 2502 is way too long (108 characters) | ||
| texlive-hyph-utf8 @ 59745 | formatting Look for formatting issues in the source | line 2503 is way too long (108 characters) | ||
| texlive-hyph-utf8 @ 59745 | formatting Look for formatting issues in the source | line 2504 is way too long (95 characters) | ||
| texlive-hyperref @ 59745 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| racket @ 8.5 | formatting Look for formatting issues in the source | line 651 is way too long (91 characters) | ||
| racket @ 8.5 | formatting Look for formatting issues in the source | line 771 is way too long (91 characters) | ||
| r-esc @ 0.5.1 | formatting Look for formatting issues in the source | line 6578 is way too long (94 characters) | ||
| r-dt @ 0.23 | formatting Look for formatting issues in the source | line 3601 is way too long (92 characters) | ||
| r-dt @ 0.23 | formatting Look for formatting issues in the source | line 3602 is way too long (91 characters) | ||
| r-dt @ 0.23 | formatting Look for formatting issues in the source | line 3604 is way too long (98 characters) | ||
| r-dt @ 0.23 | formatting Look for formatting issues in the source | line 3605 is way too long (94 characters) | ||
| r-dt @ 0.23 | formatting Look for formatting issues in the source | line 3614 is way too long (93 characters) | ||
| r-dt @ 0.23 | formatting Look for formatting issues in the source | line 3643 is way too long (93 characters) | ||
| plasma-framework @ 5.70.1 | formatting Look for formatting issues in the source | line 3306 is way too long (93 characters) | ||
| perftest @ 4.4-0.4 | formatting Look for formatting issues in the source | line 6337 is way too long (98 characters) | ||
| mkvtoolnix @ 52.0.0 | formatting Look for formatting issues in the source | line 980 is way too long (96 characters) | ||
| mesa @ 21.3.8 | formatting Look for formatting issues in the source | line 319 is way too long (120 characters) | ||
| mesa @ 21.3.8 | formatting Look for formatting issues in the source | line 322 is way too long (110 characters) | ||
| kpackage @ 5.70.0 | formatting Look for formatting issues in the source | line 1891 is way too long (106 characters) | ||
| kio @ 5.70.1 | formatting Look for formatting issues in the source | line 2695 is way too long (113 characters) | ||
| kimageformats @ 5.70.0 | formatting Look for formatting issues in the source | line 1759 is way too long (103 characters) | ||
| kdbusaddons @ 5.70.0 | formatting Look for formatting issues in the source | line 646 is way too long (121 characters) | ||
| kcmutils @ 5.70.0 | formatting Look for formatting issues in the source | line 2191 is way too long (113 characters) | ||
| js-mathjax @ 3.1.2 | formatting Look for formatting issues in the source | line 354 is way too long (94 characters) | ||
| js-filesaver @ 1.3.8 | formatting Look for formatting issues in the source | line 716 is way too long (99 characters) | ||
| guile2.2-ssh @ 0.15.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| extra-cmake-modules @ 5.91.0 | formatting Look for formatting issues in the source | line 128 is way too long (92 characters) | ||
| extra-cmake-modules @ 5.91.0 | formatting Look for formatting issues in the source | line 129 is way too long (107 characters) | ||
| extra-cmake-modules @ 5.91.0 | formatting Look for formatting issues in the source | line 142 is way too long (92 characters) | ||
| 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 @ 2.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@8 collide | ||
| java-plexus-sec-dispatcher @ 1.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 @ 2.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 | ||
| 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 @ 2.1.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@13 and apache-parent-pom@25 collide | ||
| java-plexus-component-metadata @ 1.7.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs java-plexus-container-default@1.7.1 and java-plexus-container-default@2.1.0 collide | ||
| java-plexus-compiler-manager @ 2.8.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs java-plexus-container-default@2.1.0 and java-plexus-container-default@1.7.1 collide | ||
| java-plexus-compiler-javac @ 2.8.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.11 | 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.11 | 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.11 | 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.11 | 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.11 | 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-plexus-sec-dispatcher @ 2.0 | formatting Look for formatting issues in the source | line 4978 is way too long (92 characters) | ||
| java-plexus-sec-dispatcher @ 1.4 | formatting Look for formatting issues in the source | line 5038 is way too long (107 characters) | ||
| java-plexus-component-metadata @ 2.1.0 | formatting Look for formatting issues in the source | line 4388 is way too long (110 characters) | ||
| java-plexus-component-metadata @ 2.1.0 | formatting Look for formatting issues in the source | line 4421 is way too long (95 characters) | ||
| java-plexus-component-metadata @ 2.1.0 | formatting Look for formatting issues in the source | line 4428 is way too long (146 characters) | ||
| java-plexus-component-metadata @ 2.1.0 | formatting Look for formatting issues in the source | line 4429 is way too long (151 characters) | ||
| java-plexus-component-metadata @ 2.1.0 | formatting Look for formatting issues in the source | line 4430 is way too long (149 characters) | ||
| java-plexus-component-metadata @ 2.1.0 | formatting Look for formatting issues in the source | line 4431 is way too long (141 characters) | ||
| java-plexus-component-metadata @ 2.1.0 | formatting Look for formatting issues in the source | line 4432 is way too long (161 characters) | ||
| java-plexus-component-metadata @ 2.1.0 | formatting Look for formatting issues in the source | line 4444 is way too long (138 characters) | ||
| java-plexus-component-metadata @ 2.1.0 | formatting Look for formatting issues in the source | line 4448 is way too long (103 characters) | ||
| java-plexus-component-metadata @ 2.1.0 | formatting Look for formatting issues in the source | line 4455 is way too long (114 characters) | ||
| java-plexus-component-metadata @ 2.1.0 | formatting Look for formatting issues in the source | line 4456 is way too long (108 characters) | ||
| java-plexus-component-metadata @ 1.7.1 | formatting Look for formatting issues in the source | line 4559 is way too long (114 characters) | ||
| java-plexus-component-metadata @ 1.7.1 | formatting Look for formatting issues in the source | line 4560 is way too long (108 characters) | ||
| java-plexus-compiler-javac @ 2.8.4 | formatting Look for formatting issues in the source | line 4868 is way too long (95 characters) | ||
| java-plexus-build-api @ 0.0.7 | formatting Look for formatting issues in the source | line 5130 is way too long (98 characters) | ||
| java-openjfx-graphics @ 8.202 | formatting Look for formatting issues in the source | line 2616 is way too long (99 characters) | ||
| java-openjfx-graphics @ 8.202 | formatting Look for formatting issues in the source | line 2627 is way too long (98 characters) | ||
| java-openjfx-graphics @ 8.202 | formatting Look for formatting issues in the source | line 2666 is way too long (96 characters) | ||
| java-openjfx-base @ 8.202 | formatting Look for formatting issues in the source | line 2556 is way too long (111 characters) | ||
| java-openjfx-base @ 8.202 | formatting Look for formatting issues in the source | line 2571 is way too long (99 characters) | ||
| java-hamcrest-core @ 1.3 | formatting Look for formatting issues in the source | line 3797 is way too long (112 characters) | ||
| icedtea @ 3.19.0 | formatting Look for formatting issues in the source | line 1418 is way too long (109 characters) | ||
| icedtea @ 3.19.0 | formatting Look for formatting issues in the source | line 1464 is way too long (99 characters) | ||
| icedtea @ 2.6.13 | formatting Look for formatting issues in the source | line 894 is way too long (102 characters) | ||
| icedtea @ 2.6.13 | formatting Look for formatting issues in the source | line 903 is way too long (93 characters) | ||
| icedtea @ 2.6.13 | formatting Look for formatting issues in the source | line 1087 is way too long (100 characters) | ||
| autogen @ 5.18.16 | formatting Look for formatting issues in the source | line 70 is way too long (113 characters) | ||
| dmraid @ 1.0.0.rc16-3 | formatting Look for formatting issues in the source | line 942 is way too long (91 characters) | ||
| python-warcio @ 1.7.4-0.aa702cb | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 90 | ||
| python-warcio @ 1.7.4-0.aa702cb | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-cloudscraper @ 1.2.58 | formatting Look for formatting issues in the source | line 6212 is way too long (96 characters) | ||
| template-glib @ 3.34.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python-pygobject @ 3.40.1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| 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 | ||
| gobject-introspection @ 1.66.1 | inputs-should-be-native Identify inputs that should be native inputs | 'bison' should probably be a native input | ||
| gobject-introspection @ 1.66.1 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| dbus-verbose @ 1.12.20 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gobject-introspection @ 1.66.1 | patch-headers Validate patch headers | gobject-introspection-girepository.patch: patch lacks comment and upstream status | ||
| telepathy-glib @ 0.24.2 | formatting Look for formatting issues in the source | line 973 is way too long (92 characters) | ||
| appstream-glib @ 0.7.18 | formatting Look for formatting issues in the source | line 1134 is way too long (93 characters) | ||
| ruby_version @ 1.0.2 | name Validate package names | name should use hyphens instead of underscores | ||
| 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 @ 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 | 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 1079 is way too long (115 characters) | ||
| qtsensors @ 5.15.2 | formatting Look for formatting issues in the source | line 950 is way too long (97 characters) | ||
| qtremoteobjects @ 5.15.2 | formatting Look for formatting issues in the source | line 1476 is way too long (94 characters) | ||
| qtmultimedia @ 5.15.2 | formatting Look for formatting issues in the source | line 989 is way too long (96 characters) | ||
| qtbase @ 5.15.2 | formatting Look for formatting issues in the source | line 439 is way too long (96 characters) | ||
| qtbase @ 5.15.2 | formatting Look for formatting issues in the source | line 517 is way too long (97 characters) | ||
| qtbase @ 5.15.2 | formatting Look for formatting issues in the source | line 522 is way too long (94 characters) | ||
| qtbase @ 5.15.2 | formatting Look for formatting issues in the source | line 524 is way too long (94 characters) | ||
| python-pyqt @ 5.15.2 | formatting Look for formatting issues in the source | line 2092 is way too long (105 characters) | ||
| system-config-printer @ 1.5.16 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' 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 | ||
| libpeas @ 1.30.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' 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 | ||
| netsurf @ 3.10 | patch-headers Validate patch headers | netsurf-message-timestamp.patch: patch lacks comment and upstream status | ||
| wslay @ 1.1.1 | formatting Look for formatting issues in the source | line 1555 is way too long (101 characters) | ||
| varnish @ 7.0.1 | formatting Look for formatting issues in the source | line 5916 is way too long (91 characters) | ||
| serf @ 1.3.9 | formatting Look for formatting issues in the source | line 1999 is way too long (92 characters) | ||
| librsvg @ 2.50.7 | formatting Look for formatting issues in the source | line 3429 is way too long (104 characters) | ||
| libgnome @ 2.32.1 | formatting Look for formatting issues in the source | line 3844 is way too long (110 characters) | ||
| krona-tools @ 2.8 | formatting Look for formatting issues in the source | trailing white space on line 1299 | ||
| blasr-libcpp @ 5.3.5 | formatting Look for formatting issues in the source | line 661 is way too long (95 characters) | ||
| 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.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.7.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| lsh @ 2.1 | patch-headers Validate patch headers | lsh-fix-x11-forwarding.patch: patch lacks comment and upstream status | ||
| rust-async-process @ 1.0.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| rust-async-compression @ 0.3.7 | formatting Look for formatting issues in the source | line 4311 is way too long (92 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 | ||
| 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 | ||
| flashrom @ 1.2 | formatting Look for formatting issues in the source | line 93 is way too long (91 characters) | ||
| flashrom @ 1.2 | formatting Look for formatting issues in the source | line 95 is way too long (99 characters) | ||
| python-pygame @ 1.9.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 123 | ||
| 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 | ||
| pan @ 0.149 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 71 | ||
| sendmail @ 8.15.2 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| tor @ 0.4.7.8 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 574 | ||
| guile-f-scm @ 0.2.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| coq-stdlib @ 8.15.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| coq-ide-server @ 8.15.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| coq-ide @ 8.15.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| coq-core @ 8.15.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-commons-lang3 @ 3.12.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-eclipse-text @ 3.6.0 | formatting Look for formatting issues in the source | tabulation on line 7503, column 20 | ||
| java-eclipse-text @ 3.6.0 | formatting Look for formatting issues in the source | tabulation on line 7504, column 20 | ||
| java-eclipse-jdt-core @ 3.16.0 | formatting Look for formatting issues in the source | line 7562 is way too long (98 characters) | ||
| java-commons-jxpath @ 1.3 | formatting Look for formatting issues in the source | line 6341 is way too long (93 characters) | ||
| java-commons-exec @ 1.1 | formatting Look for formatting issues in the source | line 6108 is way too long (91 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 | ||
| maven-wagon-provider-api @ 3.4.3 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs /gnu/store/d04y4sr3ibjbaapijhac3x35si7ik7kn-maven-wagon-provider-api-3.4.3 and /gnu/store/bi1y5dx0pz68bs87283iq9mqcr1xh4af-maven-wagon-provider-api-3.4.3 collide | ||
| 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@52 and apache-commons-parent-pom@39 collide | ||
| maven-slf4j-provider @ 3.8.5 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide | ||
| maven-shared-utils @ 3.2.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-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.8.5 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@8 and plexus-parent-pom@5.1 collide | ||
| maven-settings-builder @ 3.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.8.5 and maven-artifact@3.0 collide | ||
| maven-resolver-provider @ 3.8.5 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide | ||
| maven-plugin-api @ 3.8.5 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide | ||
| maven-plugin-api @ 3.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-plugin-annotations @ 3.5 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide | ||
| maven-model-builder @ 3.8.5 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide | ||
| maven-model-builder @ 3.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.8.5 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide | ||
| maven-model @ 3.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.8.5 and maven-artifact@3.0 collide | ||
| maven-filtering @ 3.1.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs java-plexus-utils@3.3.0 and java-plexus-utils@3.2.1 collide | ||
| maven-file-management @ 3.0.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 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-artifact@3.8.5 and maven-artifact@3.0 collide | ||
| maven-enforcer-plugin @ 3.0.0 | 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 | 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.8.5 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@8 collide | ||
| maven-dependency-tree @ 3.1.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-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.8.5 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-parent-pom@35 and maven-parent-pom@33 collide | ||
| maven-compat @ 3.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.2.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-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.13.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@52 and apache-commons-parent-pom@39 collide | ||
| maven-artifact @ 3.8.5 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide | ||
| maven-artifact @ 3.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@52 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@52 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@52 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@52 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 | ||
| 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 | ||
| maven-slf4j-provider @ 3.8.5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-settings-builder @ 3.8.5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| 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.8.5 | 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-resolver-provider @ 3.8.5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-repository-metadata @ 3.8.5 | 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.8.5 | 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.8.5 | 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.8.5 | 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-embedder @ 3.8.5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-compat @ 3.8.5 | 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-builder-support @ 3.8.5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-artifact @ 3.8.5 | 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 | ||
| virt-manager @ 3.2.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| maven-wagon-http @ 3.4.3 | formatting Look for formatting issues in the source | line 1059 is way too long (105 characters) | ||
| maven-wagon-http @ 3.4.3 | formatting Look for formatting issues in the source | line 1064 is way too long (138 characters) | ||
| maven-wagon-http @ 3.4.3 | formatting Look for formatting issues in the source | line 1065 is way too long (129 characters) | ||
| maven-wagon-file @ 3.4.3 | formatting Look for formatting issues in the source | line 899 is way too long (125 characters) | ||
| maven-surefire-plugin @ 3.0.0-M4 | formatting Look for formatting issues in the source | line 3833 is way too long (113 characters) | ||
| maven-surefire-plugin @ 3.0.0-M4 | formatting Look for formatting issues in the source | line 3834 is way too long (111 characters) | ||
| maven-shared-utils @ 3.2.1 | formatting Look for formatting issues in the source | line 750 is way too long (109 characters) | ||
| maven-resolver-transport-wagon @ 1.6.3 | formatting Look for formatting issues in the source | line 249 is way too long (91 characters) | ||
| maven-resolver-transport-wagon @ 1.6.3 | formatting Look for formatting issues in the source | line 264 is way too long (106 characters) | ||
| maven-resolver-transport-wagon @ 1.6.3 | formatting Look for formatting issues in the source | line 278 is way too long (102 characters) | ||
| maven-resolver-transport-http @ 1.6.3 | formatting Look for formatting issues in the source | line 377 is way too long (94 characters) | ||
| maven-resolver-transport-file @ 1.6.3 | formatting Look for formatting issues in the source | line 332 is way too long (94 characters) | ||
| maven-resolver-impl @ 1.6.3 | formatting Look for formatting issues in the source | line 195 is way too long (92 characters) | ||
| maven-resolver-impl @ 1.6.3 | formatting Look for formatting issues in the source | line 204 is way too long (92 characters) | ||
| maven-resolver-impl @ 1.6.3 | formatting Look for formatting issues in the source | line 212 is way too long (95 characters) | ||
| maven-resolver-impl @ 1.6.3 | formatting Look for formatting issues in the source | line 215 is way too long (93 characters) | ||
| maven-resolver-connector-basic @ 1.6.3 | formatting Look for formatting issues in the source | line 163 is way too long (99 characters) | ||
| maven-model-builder @ 3.0 | formatting Look for formatting issues in the source | line 2412 is way too long (127 characters) | ||
| maven-embedder @ 3.8.5 | formatting Look for formatting issues in the source | line 1846 is way too long (110 characters) | ||
| maven-embedder @ 3.8.5 | formatting Look for formatting issues in the source | line 1861 is way too long (116 characters) | ||
| maven-compat @ 3.8.5 | formatting Look for formatting issues in the source | line 2068 is way too long (109 characters) | ||
| maven-common-artifact-filters @ 3.2.0 | formatting Look for formatting issues in the source | line 2856 is way too long (124 characters) | ||
| java-surefire-booter @ 3.0.0-M4 | formatting Look for formatting issues in the source | line 3521 is way too long (107 characters) | ||
| criu @ 3.17 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| libdqlite @ 1.9.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| tuxmath @ 2.0.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| xtensor-benchmark @ 0.24.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| iml @ 1.0.5 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 798 | ||
| eigen-benchmarks @ 3.3.8 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| symmetrica @ 2.0 | patch-headers Validate patch headers | symmetrica-bruch.patch: patch lacks comment and upstream status | ||
| symmetrica @ 2.0 | formatting Look for formatting issues in the source | line 1520 is way too long (100 characters) | ||
| giac @ 1.7.0-51 | formatting Look for formatting issues in the source | line 335 is way too long (95 characters) | ||
| gap @ 4.11.0 | formatting Look for formatting issues in the source | line 1257 is way too long (98 characters) | ||
| python-pytest-subtesthack @ 0.1.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 106 | ||
| python-pytest-freezegun @ 0.4.2 | description Validate package descriptions | description contains typo 'allows to' | ||
| python-flexmock @ 0.10.4 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-testtools @ 2.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-testscenarios @ 0.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-testresources @ 2.0.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-pytest-xprocess @ 0.18.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-xdist @ 2.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-xdist @ 2.1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-warnings @ 0.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-timeout @ 2.0.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-timeout @ 2.0.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest-cov' should probably be a native input | ||
| python-pytest-sugar @ 0.9.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-subtesthack @ 0.1.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-randomly @ 3.11.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-random-order @ 1.0.4 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-mypy @ 0.9.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-mock @ 3.6.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-lazy-fixture @ 0.6.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-freezegun @ 0.4.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-dependency @ 0.5.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-datadir @ 1.3.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-cov @ 3.0.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-coverage' should probably be a native input | ||
| python-pytest-cov @ 3.0.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-catchlog @ 1.2.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-capturelog @ 0.7 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-cache @ 1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-assume @ 2.4.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-nosexcover @ 1.0.11 | inputs-should-be-native Identify inputs that should be native inputs | 'python-coverage' should probably be a native input | ||
| python-nosexcover @ 1.0.11 | inputs-should-be-native Identify inputs that should be native inputs | 'python-nose' should probably be a native input | ||
| python-nose-timer @ 0.7.5 | inputs-should-be-native Identify inputs that should be native inputs | 'python-nose' should probably be a native input | ||
| python-hypothesis @ 6.43.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-fixtures @ 3.0.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-coverage-test-runner @ 1.15 | inputs-should-be-native Identify inputs that should be native inputs | 'python-coverage' should probably be a native input | ||
| python-cov-core @ 1.15.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-coverage' should probably be a native input | ||
| python-codecov @ 2.0.15 | inputs-should-be-native Identify inputs that should be native inputs | 'python-coverage' should probably be a native input | ||
| python-django-auth-ldap @ 4.1.0 | 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-fixtures-bootstrap @ 3.0.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-unittest2 @ 1.1.0 | patch-headers Validate patch headers | python-unittest2-remove-argparse.patch: patch lacks comment and upstream status | ||
| python-requests_ntlm @ 1.1.0 | name Validate package names | name should use hyphens instead of underscores | ||
| 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 | ||
| presentty @ 0.2.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| awscli @ 1.22.90 | inputs-should-be-native Identify inputs that should be native inputs | 'groff' should probably be a native input | ||
| awscli @ 1.22.90 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-urlgrabber @ 4.1.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-flask-migrate @ 3.1.0 | source-file-name Validate file names of sources | the source file name should contain the package name | ||
| python-tornado @ 5.1.1 | formatting Look for formatting issues in the source | line 2038 is way too long (91 characters) | ||
| 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.2 | 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 | ||
| prusa-slicer @ 2.4.2 | formatting Look for formatting issues in the source | line 3205 is way too long (94 characters) | ||
| libigl @ 2.3.0 | formatting Look for formatting issues in the source | line 3063 is way too long (91 characters) | ||
| libigl @ 2.3.0 | formatting Look for formatting issues in the source | line 3064 is way too long (101 characters) | ||
| libigl @ 2.3.0 | formatting Look for formatting issues in the source | line 3091 is way too long (94 characters) | ||
| fritzing @ 0.9.3b | formatting Look for formatting issues in the source | line 686 is way too long (91 characters) | ||
| fritzing @ 0.9.3b | formatting Look for formatting issues in the source | line 687 is way too long (99 characters) | ||
| freehdl @ 0.0.8 | formatting Look for formatting issues in the source | line 2015 is way too long (101 characters) | ||
| emacs-erlang @ 25.0.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| telepathy-mission-control @ 5.16.6 | 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 366 is way too long (91 characters) | ||
| localed @ 241 | formatting Look for formatting issues in the source | line 862 is way too long (96 characters) | ||
| openjpeg-data @ 2020.11.30 | 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 505 is way too long (95 characters) | ||
| python-sphinx-sitemap @ 2.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx-rtd-theme @ 1.0.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-sphinx-rtd-theme @ 1.0.0 | 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-intl @ 2.0.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx-cloud-sptheme @ 1.10.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx-autodoc-typehints @ 1.18.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx-autobuild @ 2021.3.14 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx-argparse @ 0.3.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-pydata-sphinx-theme @ 0.7.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-pydata-sphinx-theme @ 0.7.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-nbsphinx @ 0.8.8 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-nbsphinx @ 0.8.8 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-guzzle-sphinx-theme @ 0.7.11 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-breathe @ 4.34.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-breathe @ 4.34.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| sh-z @ 1.11 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| xen @ 4.14.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| u-boot-wandboard @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-tools @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-sifive-unmatched @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-sifive-unleashed @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-rockpro64-rk3399 @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-rock64-rk3328 @ 2022.04 | 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 @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-qemu-riscv64 @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-puma-rk3399 @ 2022.04 | 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 @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-pinebook @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-pine64-plus @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-pine64-lts @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-novena @ 2022.04 | 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 @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-malta @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-firefly-rk3399 @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-cubietruck @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-cubieboard @ 2022.04 | 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 @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-am335x-evm @ 2022.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-am335x-boneblack @ 2022.04 | 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 @ 2022.04 | 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 @ 2022.04 | 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 @ 2022.04 | 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-efi32 @ 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 | ||
| u-boot-wandboard @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| u-boot-tools @ 2022.04 | formatting Look for formatting issues in the source | line 621 is way too long (108 characters) | ||
| u-boot-tools @ 2022.04 | formatting Look for formatting issues in the source | line 625 is way too long (97 characters) | ||
| u-boot-sifive-unleashed @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| u-boot-qemu-riscv64-smode @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| u-boot-qemu-riscv64 @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| u-boot-pinebook @ 2022.04 | formatting Look for formatting issues in the source | line 829 is way too long (127 characters) | ||
| u-boot-pine64-plus @ 2022.04 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| u-boot-pine64-lts @ 2022.04 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| u-boot-mx6cuboxi @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| u-boot-malta @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| u-boot-cubietruck @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| u-boot-cubieboard @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| u-boot-bananapi-m2-ultra @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| u-boot-am335x-evm @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| u-boot-am335x-boneblack @ 2022.04 | formatting Look for formatting issues in the source | line 780 is way too long (95 characters) | ||
| u-boot-a20-olinuxino-micro @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| u-boot-a20-olinuxino-lime2 @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| u-boot-a20-olinuxino-lime @ 2022.04 | formatting Look for formatting issues in the source | line 742 is way too long (93 characters) | ||
| ctl @ 1.5.2 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| openexr @ 2.5.7 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| blender @ 3.0.1 | formatting Look for formatting issues in the source | line 459 is way too long (97 characters) | ||
| java-jsch-agentproxy-usocket-nc @ 0.0.8 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 88 | ||
| java-jsch-agentproxy-usocket-nc @ 0.0.8 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| java-jsch-agentproxy-usocket-jna @ 0.0.8 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 88 | ||
| java-jsch-agentproxy-usocket-jna @ 0.0.8 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| java-jsch-agentproxy-sshagent @ 0.0.8 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 88 | ||
| java-jsch-agentproxy-sshagent @ 0.0.8 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| java-jsch-agentproxy-pageant @ 0.0.8 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 88 | ||
| java-jsch-agentproxy-pageant @ 0.0.8 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| java-jsch-agentproxy-jsch @ 0.0.8 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 88 | ||
| java-jsch-agentproxy-jsch @ 0.0.8 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| java-jsch-agentproxy-core @ 0.0.8 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| java-jsch-agentproxy-connector-factory @ 0.0.8 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 88 | ||
| java-jsch-agentproxy-connector-factory @ 0.0.8 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| java-xmlunit-matchers @ 2.5.1 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-xmlunit-legacy @ 2.5.1 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-xmlunit @ 2.5.1 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-xerial-core @ 2.1 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-stringtemplate @ 4.0.8 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-stax2-api @ 4.0.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-powermock-reflect @ 1.7.3 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-powermock-modules-junit4-common @ 1.7.3 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-powermock-modules-junit4 @ 1.7.3 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-powermock-core @ 1.7.3 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-powermock-api-support @ 1.7.3 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-powermock-api-easymock @ 1.7.3 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-ops4j-pax-tinybundles @ 2.1.1 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-ops4j-pax-exam-core-spi @ 4.11.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-ops4j-pax-exam-core-junit @ 4.11.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-ops4j-pax-exam-core @ 4.11.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-ops4j-base-util-property @ 1.5.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-ops4j-base-util @ 1.5.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-ops4j-base-store @ 1.5.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-ops4j-base-spi @ 1.5.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-ops4j-base-monitors @ 1.5.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-ops4j-base-lang @ 1.5.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-ops4j-base-io @ 1.5.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-native-access-platform @ 4.5.1 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-native-access @ 4.5.1 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-mvel2 @ 2.3.1 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-microemulator-cldc @ 2.0.4 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-mail @ 1.6.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-logback-core @ 1.2.3 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-logback-classic @ 1.2.3 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jsch-agentproxy-usocket-nc @ 0.0.8 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jsch-agentproxy-usocket-jna @ 0.0.8 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jsch-agentproxy-sshagent @ 0.0.8 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jsch-agentproxy-pageant @ 0.0.8 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jsch-agentproxy-jsch @ 0.0.8 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jsch-agentproxy-core @ 0.0.8 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jsch-agentproxy-connector-factory @ 0.0.8 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-joda-time @ 2.9.9 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-joda-convert @ 1.9.2 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jline @ 2.14.5 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jline @ 1.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jboss-jms-api-spec @ 2.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jboss-interceptors-api-spec @ 1.2 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jboss-el-api-spec @ 3.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-jansi-native @ 1.7 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-hawtjni @ 1.15 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-gson @ 2.8.2 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-fasterxml-jackson-modules-base-mrbean @ 2.9.4 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-fasterxml-jackson-modules-base-jaxb @ 2.9.4 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-fasterxml-jackson-dataformat-yaml @ 2.9.4 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-fasterxml-jackson-databind @ 2.9.4 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-fasterxml-jackson-core @ 2.9.4 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-fasterxml-jackson-annotations @ 2.9.4 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-datanucleus-javax-persistence @ 2.2.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-cdi-api @ 2.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-aqute-libg @ 3.5.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-aqute-bndlib @ 3.5.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-aqute-bnd-annotation @ 3.5.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| java-eclipse-sisu-plexus @ 0.3.5 | 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-commons-text @ 1.9 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@51 collide | ||
| antlr3 @ 3.5.2 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs java-stringtemplate@3.2.1 and java-stringtemplate@4.0.6 collide | ||
| java-tunnelvisionlabs-antlr4-runtime-annotations @ 4.7.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-tunnelvisionlabs-antlr4-runtime @ 4.7.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-tunnelvisionlabs-antlr4 @ 4.7.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-powermock-reflect @ 1.7.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-powermock-modules-junit4-common @ 1.7.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-powermock-modules-junit4 @ 1.7.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-powermock-core @ 1.7.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-powermock-api-support @ 1.7.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-powermock-api-easymock @ 1.7.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-antlr4-runtime-cpp @ 4.8 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-antlr4-runtime @ 4.8 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| antlr4 @ 4.8 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-testng @ 6.14.3 | formatting Look for formatting issues in the source | line 10994 is way too long (91 characters) | ||
| java-ops4j-pax-exam-core-spi @ 4.11.0 | formatting Look for formatting issues in the source | line 9984 is way too long (92 characters) | ||
| java-ops4j-pax-exam-core-spi @ 4.11.0 | formatting Look for formatting issues in the source | line 9988 is way too long (98 characters) | ||
| java-ops4j-pax-exam-core-spi @ 4.11.0 | formatting Look for formatting issues in the source | line 9992 is way too long (99 characters) | ||
| java-ops4j-pax-exam-core-spi @ 4.11.0 | formatting Look for formatting issues in the source | line 9993 is way too long (91 characters) | ||
| java-ops4j-pax-exam-core-spi @ 4.11.0 | formatting Look for formatting issues in the source | line 9996 is way too long (100 characters) | ||
| java-ops4j-base-lang @ 1.5.0 | formatting Look for formatting issues in the source | line 9680 is way too long (110 characters) | ||
| java-openchart2 @ 1.4.3 | formatting Look for formatting issues in the source | line 12858 is way too long (92 characters) | ||
| java-native-access @ 4.5.1 | formatting Look for formatting issues in the source | line 13036 is way too long (91 characters) | ||
| java-logback-classic @ 1.2.3 | formatting Look for formatting issues in the source | line 13605 is way too long (102 characters) | ||
| java-joda-time @ 2.9.9 | formatting Look for formatting issues in the source | line 12438 is way too long (92 characters) | ||
| java-jnacl @ 0.1.0-2.094e819 | formatting Look for formatting issues in the source | line 11071 is way too long (93 characters) | ||
| java-jnacl @ 0.1.0-2.094e819 | formatting Look for formatting issues in the source | line 11081 is way too long (92 characters) | ||
| java-jgit @ 4.2.0.201601211800-r | formatting Look for formatting issues in the source | line 13705 is way too long (93 characters) | ||
| java-jansi @ 2.4.0 | formatting Look for formatting issues in the source | line 12212 is way too long (94 characters) | ||
| java-hawtjni @ 1.15 | formatting Look for formatting issues in the source | line 12072 is way too long (92 characters) | ||
| java-geronimo-xbean-reflect @ 4.5 | formatting Look for formatting issues in the source | line 11825 is way too long (92 characters) | ||
| java-geronimo-xbean-bundleutils @ 4.5 | formatting Look for formatting issues in the source | line 11940 is way too long (122 characters) | ||
| java-fasterxml-jackson-dataformat-yaml @ 2.9.4 | formatting Look for formatting issues in the source | line 10305 is way too long (104 characters) | ||
| java-fasterxml-jackson-dataformat-xml @ 2.9.4 | formatting Look for formatting issues in the source | line 10418 is way too long (98 characters) | ||
| java-fasterxml-jackson-databind @ 2.9.4 | formatting Look for formatting issues in the source | line 10142 is way too long (96 characters) | ||
| java-fasterxml-jackson-core @ 2.9.4 | formatting Look for formatting issues in the source | line 10091 is way too long (93 characters) | ||
| java-eclipse-sisu-plexus @ 0.3.5 | formatting Look for formatting issues in the source | line 13422 is way too long (104 characters) | ||
| java-eclipse-sisu-plexus @ 0.3.5 | formatting Look for formatting issues in the source | line 13429 is way too long (95 characters) | ||
| java-commons-httpclient @ 3.1 | formatting Look for formatting issues in the source | line 12898 is way too long (91 characters) | ||
| java-aqute-bndlib @ 3.5.0 | formatting Look for formatting issues in the source | line 9865 is way too long (91 characters) | ||
| java-apache-ivy @ 2.4.0 | formatting Look for formatting issues in the source | line 13247 is way too long (101 characters) | ||
| antlr4 @ 4.8 | formatting Look for formatting issues in the source | line 8737 is way too long (96 characters) | ||
| antlr4 @ 4.8 | formatting Look for formatting issues in the source | line 8811 is way too long (100 characters) | ||
| maven-doxia-core @ 2.0.0-M2 | 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 | ||
| xsimd-benchmark @ 8.1.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| jucipp @ 1.7.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile2.2-sjson @ 0.2.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile2.2-ncurses @ 3.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile2.2-email @ 0.2.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile2.2-commonmark @ 0.1.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile2.0-commonmark @ 0.1.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile-stis-parser @ 1.2.4.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 117 | ||
| guile-ncurses-with-gpm @ 3.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile-email-latest @ 0.2.2-2.ea60bb9 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile-dbd-sqlite3 @ 2.1.8 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile2.2-simple-zmq @ 0.0.0-9.b2ea97e | inputs-should-be-native Identify inputs that should be native inputs | 'autoconf' should probably be a native input | ||
| guile2.2-simple-zmq @ 0.0.0-9.b2ea97e | inputs-should-be-native Identify inputs that should be native inputs | 'automake' should probably be a native input | ||
| guile2.2-simple-zmq @ 0.0.0-9.b2ea97e | inputs-should-be-native Identify inputs that should be native inputs | 'pkg-config' should probably be a native input | ||
| guile2.2-gi @ 0.3.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| guile2.2-g-golf @ 0.1.0-1010.1824633 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| guile-simple-zmq @ 0.0.0-9.b2ea97e | inputs-should-be-native Identify inputs that should be native inputs | 'autoconf' should probably be a native input | ||
| guile-simple-zmq @ 0.0.0-9.b2ea97e | inputs-should-be-native Identify inputs that should be native inputs | 'automake' should probably be a native input | ||
| guile-simple-zmq @ 0.0.0-9.b2ea97e | inputs-should-be-native Identify inputs that should be native inputs | 'pkg-config' should probably be a native input | ||
| guile-gi @ 0.3.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| guile-g-golf @ 0.1.0-1010.1824633 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| guile2.2-fibers @ 1.1.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.2-email @ 0.2.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile-dbd-postgresql @ 2.1.8 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| guile-dbd-mysql @ 2.1.8 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| guile-avahi @ 0.4.0-1.6d43caf | formatting Look for formatting issues in the source | line 4334 is way too long (92 characters) | ||
| geany @ 1.38 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| gnome-shell-extension-gsconnect @ 48 | inputs-should-be-native Identify inputs that should be native inputs | 'glib:bin' should probably be a native input | ||
| gnome-shell-extension-dash-to-panel @ 45 | inputs-should-be-native Identify inputs that should be native inputs | 'glib:bin' should probably be a native input | ||
| libstdc++-doc @ 9.5.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 | ||
| gcc-objc++ @ 12.1.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc++ @ 11.3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc @ 12.1.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc @ 11.3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libstdc++-doc @ 9.5.0 | patch-headers Validate patch headers | gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status | ||
| python-cryptography @ 36.0.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-cryptography @ 3.4.8 | 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 | ||
| python-pyopenssl @ 21.0.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| cfitsio @ 3.49 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 197 | ||
| python-flit-scm @ 1.6.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-setuptools-scm' should probably be a native input | ||
| notifymuch @ 0.1-1.9d4aaf5 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| astroid @ 0.16 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| guile2.2-mailutils @ 3.15 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-statmake @ 0.5.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 275, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 276, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 277, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 278, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 279, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 280, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 281, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 282, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 283, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 286, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 287, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 289, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 290, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 291, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 292, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 293, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 295, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 296, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 297, column 0 | ||
| libarchive @ 3.5.1 | formatting Look for formatting issues in the source | tabulation on line 298, column 0 | ||
| i3-wm @ 4.20.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| keybinder @ 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 | ||
| i3-gaps @ 4.20.1 | source-file-name Validate file names of sources | the source file name should contain the package name | ||
| 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 | ||
| libcpuid @ 0.5.1-1.2e61160 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 113 | ||
| h-client @ 0.0a0-1.e6c78b1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| rocm-bandwidth-test @ 5.1.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 122 | ||
| vim-full @ 9.0.0000 | formatting Look for formatting issues in the source | line 219 is way too long (98 characters) | ||
| ocaml4.07-cmdliner @ 1.0.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 304 | ||
| ocaml-topkg @ 1.0.5 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 51 | ||
| ocaml-cmdliner @ 1.1.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 304 | ||
| ocaml-sedlex @ 2.5 | formatting Look for formatting issues in the source | line 2877 is way too long (97 characters) | ||
| icecat @ 91.11.0-guix0-preview1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| icecat @ 91.11.0-guix0-preview1 | formatting Look for formatting issues in the source | line 769 is way too long (140 characters) | ||
| icecat @ 91.11.0-guix0-preview1 | formatting Look for formatting issues in the source | line 775 is way too long (96 characters) | ||
| icecat @ 91.11.0-guix0-preview1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| icecat @ 91.11.0-guix0-preview1 | formatting Look for formatting issues in the source | line 813 is way too long (93 characters) | ||
| icecat @ 91.11.0-guix0-preview1 | formatting Look for formatting issues in the source | line 815 is way too long (94 characters) | ||
| icecat @ 91.11.0-guix0-preview1 | formatting Look for formatting issues in the source | line 821 is way too long (99 characters) | ||
| xblackjack @ 2.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 146 | ||
| sooperlooper @ 1.7.6 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 120 | ||
| sky @ 1.2 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| python-discogs-client @ 2.3.12 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 70 | ||
| passage @ 4 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| drumstick @ 2.3.1 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| abjad @ 3.4 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| abjad @ 3.4 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest-cov' should probably be a native input | ||
| 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 2968 is way too long (91 characters) | ||
| solfege @ 3.23.5pre2 | formatting Look for formatting issues in the source | line 2067 is way too long (94 characters) | ||
| sky @ 1.2 | formatting Look for formatting issues in the source | line 9919 is way too long (118 characters) | ||
| ri-li @ 2.0.1 | formatting Look for formatting issues in the source | line 10010 is way too long (100 characters) | ||
| queen-it @ 1.0 | formatting Look for formatting issues in the source | line 9817 is way too long (184 characters) | ||
| queen-it @ 1.0 | formatting Look for formatting issues in the source | line 9818 is way too long (205 characters) | ||
| queen-fr @ 1.0 | formatting Look for formatting issues in the source | line 9817 is way too long (184 characters) | ||
| queen-fr @ 1.0 | formatting Look for formatting issues in the source | line 9818 is way too long (205 characters) | ||
| queen-de @ 1.0 | formatting Look for formatting issues in the source | line 9817 is way too long (184 characters) | ||
| queen-de @ 1.0 | formatting Look for formatting issues in the source | line 9818 is way too long (205 characters) | ||
| queen @ 1.1 | formatting Look for formatting issues in the source | line 9817 is way too long (184 characters) | ||
| queen @ 1.1 | formatting Look for formatting issues in the source | line 9818 is way too long (205 characters) | ||
| lure-it @ 1.1 | formatting Look for formatting issues in the source | line 9720 is way too long (93 characters) | ||
| lure-fr @ 1.1 | formatting Look for formatting issues in the source | line 9720 is way too long (93 characters) | ||
| lure-es @ 1.1 | formatting Look for formatting issues in the source | line 9720 is way too long (93 characters) | ||
| lure-de @ 1.1 | formatting Look for formatting issues in the source | line 9720 is way too long (93 characters) | ||
| lure @ 1.1 | formatting Look for formatting issues in the source | line 9720 is way too long (93 characters) | ||
| icedove @ 91.11.0 | formatting Look for formatting issues in the source | line 1007 is way too long (98 characters) | ||
| icedove @ 91.11.0 | formatting Look for formatting issues in the source | line 1159 is way too long (105 characters) | ||
| icedove @ 91.11.0 | formatting Look for formatting issues in the source | line 1161 is way too long (102 characters) | ||
| freeorion @ 0.4.10.2 | formatting Look for formatting issues in the source | line 10095 is way too long (92 characters) | ||
| drumstick @ 2.3.1 | formatting Look for formatting issues in the source | line 2924 is way too long (91 characters) | ||
| drascula @ 1.0 | formatting Look for formatting issues in the source | line 9619 is way too long (93 characters) | ||
| drascula @ 1.0 | formatting Look for formatting issues in the source | line 9623 is way too long (93 characters) | ||
| btanks @ 0.9.8083 | formatting Look for formatting issues in the source | line 8618 is way too long (99 characters) | ||
| btanks @ 0.9.8083 | formatting Look for formatting issues in the source | tabulation on line 8642, column 18 | ||
| btanks @ 0.9.8083 | formatting Look for formatting issues in the source | tabulation on line 8643, column 17 | ||
| rtl-sdr @ 0.6.0-1.5e73f90 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| hackrf @ 2021.03.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| sbcl @ 2.2.6 | formatting Look for formatting issues in the source | tabulation on line 547, column 18 | ||
| r-biomart @ 2.52.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-drimseq @ 1.24.0 | formatting Look for formatting issues in the source | line 2586 is way too long (109 characters) | ||
| r-biocparallel @ 1.30.3 | formatting Look for formatting issues in the source | line 3381 is way too long (95 characters) | ||
| python-html2text @ 2020.1.16 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-scrapy @ 2.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-praw @ 7.5.0 | formatting Look for formatting issues in the source | line 238 is way too long (93 characters) | ||
| python-praw @ 7.5.0 | formatting Look for formatting issues in the source | line 239 is way too long (105 characters) | ||
| wpa-supplicant-minimal @ 2.10 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| wpa-supplicant-gui @ 2.10 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| wpa-supplicant @ 2.10 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| greetd-pam-mount @ 2.18 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 358 | ||
| mdadm-static @ 4.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ecryptfs-utils @ 111 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| linux-pam @ 1.5.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| libaio @ 0.3.112 | formatting Look for formatting issues in the source | line 5325 is way too long (110 characters) | ||
| crda @ 3.18 | formatting Look for formatting issues in the source | line 4308 is way too long (100 characters) | ||
| quodlibet @ 4.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| musikcube @ 0.96.10 | formatting Look for formatting issues in the source | line 6725 is way too long (99 characters) | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5523, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5524, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5525, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5526, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5528, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5535, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5536, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5537, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5538, column 0 | ||
| ibus-libhangul @ 1.5.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ibus-anthy @ 1.5.14 | 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 393 is way too long (93 characters) | ||
| mosquitto @ 1.6.12 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 347 | ||
| quaternion @ 0.0.9.4f | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| python-librecaptcha @ 0.7.3 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| poezio @ 0.13.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 | ||
| gajim @ 1.4.5 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| gajim @ 1.4.5 | patch-headers Validate patch headers | gajim-honour-GAJIM_PLUGIN_PATH.patch: patch lacks comment and upstream status | ||
| python-librecaptcha @ 0.7.3 | formatting Look for formatting issues in the source | line 3391 is way too long (101 characters) | ||
| psi-plus @ 1.5.1484 | formatting Look for formatting issues in the source | line 2980 is way too long (96 characters) | ||
| mtxclient @ 0.7.0 | formatting Look for formatting issues in the source | line 2357 is way too long (98 characters) | ||
| python-psycopg2 @ 2.9.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| go-sigs-k8s-io-yaml @ 1.3.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 181 | ||
| go-github-com-songmu-gitconfig @ 0.1.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| go-github-com-muesli-termenv @ 0.8.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| go-github-com-mitchellh-reflectwalk @ 1.0.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-sphinxcontrib-asyncio @ 0.3.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| go-github-com-wtolson-go-taglib @ 0.0.0-0.6e68349 | inputs-should-be-native Identify inputs that should be native inputs | 'pkg-config' should probably be a native input | ||
| go-github-com-mesilliac-pulse-simple @ 0.0.0-0.75ac54e | inputs-should-be-native Identify inputs that should be native inputs | 'pkg-config' should probably be a native input | ||
| sqlcipher @ 3.4.2 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| python-psycopg @ 3.0.8 | formatting Look for formatting issues in the source | tabulation on line 3730, column 0 | ||
| mariadb @ 10.5.12 | formatting Look for formatting issues in the source | trailing white space on line 957 | ||
| go-gopkg-in-yaml-v2 @ 2.4.0 | formatting Look for formatting issues in the source | line 4074 is way too long (104 characters) | ||
| go-gopkg-in-djherbis-times-v1 @ 1.5.0 | formatting Look for formatting issues in the source | line 9043 is way too long (91 characters) | ||
| go-github-com-rogpeppe-go-internal @ 1.6.1 | formatting Look for formatting issues in the source | line 8137 is way too long (101 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1007 is way too long (94 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1008 is way too long (94 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1009 is way too long (94 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1010 is way too long (94 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1011 is way too long (93 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1012 is way too long (93 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1013 is way too long (95 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1014 is way too long (95 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1019 is way too long (91 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1020 is way too long (95 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1029 is way too long (91 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1030 is way too long (91 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1032 is way too long (96 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1033 is way too long (96 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1034 is way too long (96 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1035 is way too long (96 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1036 is way too long (95 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1037 is way too long (95 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1039 is way too long (97 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1040 is way too long (97 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1042 is way too long (94 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1044 is way too long (92 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1045 is way too long (92 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1046 is way too long (93 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1047 is way too long (97 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1057 is way too long (94 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1058 is way too long (94 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1059 is way too long (94 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1060 is way too long (94 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1061 is way too long (93 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1062 is way too long (93 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1063 is way too long (95 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1064 is way too long (95 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1069 is way too long (91 characters) | ||
| go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12 | formatting Look for formatting issues in the source | line 1070 is way too long (98 characters) | ||
| go-github-com-mitchellh-go-homedir @ 1.0.0-0.ae18d6b | formatting Look for formatting issues in the source | line 5017 is way too long (95 characters) | ||
| go-github-com-mattn-go-shellwords @ 1.0.5-1.2444a32 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| go-github-com-gorilla-context @ 0.0.0-0.08b5f42 | formatting Look for formatting issues in the source | line 3314 is way too long (164 characters) | ||
| go-github-com-davecgh-go-spew @ 1.1.1 | formatting Look for formatting issues in the source | line 4587 is way too long (129 characters) | ||
| java-xpp3 @ 1.1.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 188 | ||
| 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 | ||
| proj.4 @ 4.9.3 | formatting Look for formatting issues in the source | line 607 is way too long (92 characters) | ||
| font-bravura @ 1.393 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| instead @ 3.3.5 | inputs-should-be-native Identify inputs that should be native inputs | 'pkg-config' should probably be a native input | ||
| python-renpy @ 8.0.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| warsow-qfusion @ 2.5-1.c4de15d | patch-headers Validate patch headers | warsow-qfusion-fix-bool-return-type.patch: patch lacks comment and upstream status | ||
| godot @ 3.4.2 | formatting Look for formatting issues in the source | line 1859 is way too long (92 characters) | ||
| godot @ 3.4.2 | formatting Look for formatting issues in the source | line 1862 is way too long (97 characters) | ||
| font-canada1500 @ 1.101 | formatting Look for formatting issues in the source | line 217 is way too long (91 characters) | ||
| font-adobe-source-code-pro @ 2.032R-ro-1.052R-it-1.012R-VAR | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| tbb @ 2021.5.0 | patch-headers Validate patch headers | tbb-other-arches.patch: patch lacks comment and upstream status | ||
| lpsolve @ 5.5.2.5 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| opencascade-occt @ 7.6.0 | inputs-should-be-native Identify inputs that should be native inputs | 'doxygen' should probably be a native input | ||
| octave-cli @ 7.1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'texinfo' should probably be a native input | ||
| octave @ 7.1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'texinfo' should probably be a native input | ||
| 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 | ||
| 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 | ||
| mcrl2-minimal @ 202206.0 | 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 | ||
| netcdf-parallel-openmpi @ 4.7.4 | patch-headers Validate patch headers | netcdf-date-time.patch: patch lacks comment and upstream status | ||
| netcdf @ 4.7.4 | patch-headers Validate patch headers | netcdf-date-time.patch: patch lacks comment and upstream status | ||
| superlu-dist @ 6.4.0 | formatting Look for formatting issues in the source | line 4007 is way too long (92 characters) | ||
| superlu-dist @ 6.4.0 | formatting Look for formatting issues in the source | tabulation on line 4027, column 0 | ||
| superlu-dist @ 6.4.0 | formatting Look for formatting issues in the source | tabulation on line 4028, column 0 | ||
| slepc-openmpi @ 3.16.1 | formatting Look for formatting issues in the source | tabulation on line 3473, column 0 | ||
| slepc-complex-openmpi @ 3.16.1 | formatting Look for formatting issues in the source | line 3489 is way too long (92 characters) | ||
| scalapack @ 2.1.0 | formatting Look for formatting issues in the source | tabulation on line 1016, column 0 | ||
| petsc @ 3.16.1 | 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 4207, column 0 | ||
| nomad-optimizer @ 4.2.0 | formatting Look for formatting issues in the source | line 2112 is way too long (105 characters) | ||
| nomad-optimizer @ 4.2.0 | formatting Look for formatting issues in the source | line 2115 is way too long (102 characters) | ||
| nomad-optimizer @ 4.2.0 | formatting Look for formatting issues in the source | line 2144 is way too long (92 characters) | ||
| nlopt @ 2.7.1 | formatting Look for formatting issues in the source | line 1981 is way too long (91 characters) | ||
| mumps-openmpi @ 5.2.1 | formatting Look for formatting issues in the source | tabulation on line 3846, column 0 | ||
| mumps @ 5.2.1 | formatting Look for formatting issues in the source | line 3758 is way too long (94 characters) | ||
| hypre-openmpi @ 2.20.0 | formatting Look for formatting issues in the source | tabulation on line 5664, column 0 | ||
| hdf-java @ 3.3.2 | formatting Look for formatting issues in the source | line 1518 is way too long (97 characters) | ||
| clapack @ 3.2.1 | formatting Look for formatting issues in the source | line 979 is way too long (91 characters) | ||
| r-yapsa @ 1.22.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 93, 96 | ||
| r-wmtsa @ 2.0-3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 105, 128 | ||
| r-seqlogo @ 1.62.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-sapa @ 2.0-3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 97, 120 | ||
| r-rtracklayer @ 1.56.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-rgadem @ 2.44.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-palmerpenguins @ 0.1.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 268 | ||
| r-mixomics @ 6.20.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-iclusterplus @ 1.32.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-biosigner @ 1.24.2 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-biocio @ 1.6.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-bioassayr @ 1.34.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-astsa @ 1.15 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 132, 149 | ||
| r-unifiedwmwqpcr @ 1.32.0 | formatting Look for formatting issues in the source | line 12525 is way too long (92 characters) | ||
| r-squarem @ 2021.1 | formatting Look for formatting issues in the source | line 5175 is way too long (91 characters) | ||
| r-shiny @ 1.7.1 | formatting Look for formatting issues in the source | line 2652 is way too long (103 characters) | ||
| r-shiny @ 1.7.1 | formatting Look for formatting issues in the source | line 2660 is way too long (94 characters) | ||
| r-shiny @ 1.7.1 | formatting Look for formatting issues in the source | line 2692 is way too long (96 characters) | ||
| r-monocle @ 2.24.1 | formatting Look for formatting issues in the source | line 7980 is way too long (101 characters) | ||
| r-lumi @ 2.48.0 | formatting Look for formatting issues in the source | line 8468 is way too long (95 characters) | ||
| r-leaflet @ 2.1.1 | formatting Look for formatting issues in the source | line 7130 is way too long (97 characters) | ||
| r-leaflet @ 2.1.1 | formatting Look for formatting issues in the source | line 7132 is way too long (99 characters) | ||
| r-leaflet @ 2.1.1 | formatting Look for formatting issues in the source | line 7133 is way too long (102 characters) | ||
| r-leaflet @ 2.1.1 | formatting Look for formatting issues in the source | line 7164 is way too long (97 characters) |