| Package | Linter | Message | Location | |
|---|---|---|---|---|
| nsis-i686 @ 3.05 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 107 | ||
| connman @ 1.38 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 146 | ||
| java-jblas @ 1.2.4 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| perl-test-file-contents @ 0.23 | 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 | ||
| nsis-x86_64 @ 3.05 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 107 | ||
| cinnamon-desktop @ 3.4.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' 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 | ||
| 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 | ||
| mig @ 1.8 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' 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 | ||
| gramps @ 5.1.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| 389-ds-base @ 1.4.0.21 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| rdmd @ 2.077.1 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| infiniband-diags @ 2.0.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| flatbuffers @ 1.10.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 65 is way too long (115 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 66 is way too long (112 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 80 is way too long (112 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 94 is way too long (92 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 104 is way too long (97 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 108 is way too long (122 characters) | ||
| nsis-i686 @ 3.05 | formatting Look for formatting issues in the source | line 118 is way too long (114 characters) | ||
| jose @ 10 | formatting Look for formatting issues in the source | line 37 is way too long (92 characters) | ||
| ldc @ 0.17.4 | formatting Look for formatting issues in the source | line 137 is way too long (98 characters) | ||
| libdaemon @ 0.14 | formatting Look for formatting issues in the source | line 35 is way too long (147 characters) | ||
| libdaemon @ 0.14 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| pth @ 2.0.7 | formatting Look for formatting issues in the source | trailing white space on line 42 | ||
| ldc @ 1.10.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| sdl-mixer @ 1.2.12 | formatting Look for formatting issues in the source | line 260 is way too long (92 characters) | ||
| axoloti-patcher-next @ 2.0.0 | formatting Look for formatting issues in the source | line 414 is way too long (94 characters) | ||
| axoloti-patcher-next @ 2.0.0 | formatting Look for formatting issues in the source | line 573 is way too long (103 characters) | ||
| mingw-w64-i686-winpthreads @ 7.0.0 | formatting Look for formatting issues in the source | line 90 is way too long (91 characters) | ||
| guile-wm @ 1.0-1.f3c7b3b | formatting Look for formatting issues in the source | line 128 is way too long (92 characters) | ||
| sdl-image @ 1.2.12 | formatting Look for formatting issues in the source | line 223 is way too long (91 characters) | ||
| python2 @ 2.7.17 | formatting Look for formatting issues in the source | line 181 is way too long (99 characters) | ||
| python2 @ 2.7.17 | formatting Look for formatting issues in the source | line 290 is way too long (98 characters) | ||
| mingw-w64-x86_64 @ 7.0.0 | formatting Look for formatting issues in the source | line 90 is way too long (91 characters) | ||
| mingw-w64-i686 @ 7.0.0 | formatting Look for formatting issues in the source | line 90 is way too long (91 characters) | ||
| ncurses @ 6.2 | formatting Look for formatting issues in the source | trailing white space on line 165 | ||
| ncurses @ 6.2 | formatting Look for formatting issues in the source | line 179 is way too long (94 characters) | ||
| axoloti-runtime @ 1.0.12-2 | formatting Look for formatting issues in the source | line 196 is way too long (96 characters) | ||
| libsigsegv @ 2.12 | formatting Look for formatting issues in the source | line 48 is way too long (133 characters) | ||
| sdl-gfx @ 2.0.26 | formatting Look for formatting issues in the source | line 213 is way too long (106 characters) | ||
| hyperledger-iroha @ 1.1.1 | formatting Look for formatting issues in the source | line 169 is way too long (105 characters) | ||
| papi @ 5.5.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| gmp @ 6.2.0 | formatting Look for formatting issues in the source | line 82 is way too long (96 characters) | ||
| mingw-w64-x86_64-winpthreads @ 7.0.0 | formatting Look for formatting issues in the source | line 90 is way too long (91 characters) | ||
| guile-sdl @ 0.5.2 | formatting Look for formatting issues in the source | line 607 is way too long (111 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 65 is way too long (115 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 66 is way too long (112 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 80 is way too long (112 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 94 is way too long (92 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 104 is way too long (97 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 108 is way too long (122 characters) | ||
| nsis-x86_64 @ 3.05 | formatting Look for formatting issues in the source | line 118 is way too long (114 characters) | ||
| ibus-anthy @ 1.5.9 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| perl-test2-plugin-nowarnings @ 0.06 | formatting Look for formatting issues in the source | line 106 is way too long (92 characters) | ||
| perl-devel-globaldestruction @ 0.14 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| vorbis-tools @ 1.4.0 | formatting Look for formatting issues in the source | trailing white space on line 323 | ||
| guile @ 2.0.14 | formatting Look for formatting issues in the source | line 188 is way too long (94 characters) | ||
| guile @ 2.0.14 | formatting Look for formatting issues in the source | line 191 is way too long (93 characters) | ||
| netpbm @ 10.78.3 | formatting Look for formatting issues in the source | line 86 is way too long (127 characters) | ||
| wicd @ 1.7.4 | formatting Look for formatting issues in the source | line 109 is way too long (95 characters) | ||
| dejagnu @ 1.6.2 | formatting Look for formatting issues in the source | line 60 is way too long (91 characters) | ||
| python-libfreenect @ 0.6.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| libfreenect-opencv @ 0.6.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| libfreenect-examples @ 0.6.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| presentty @ 0.2.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| presentty @ 0.2.1 | formatting Look for formatting issues in the source | line 45 is way too long (117 characters) | ||
| arm-trusted-firmware-rk3328 @ 2.3 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| maven-resolver-impl @ 1.3.1 | formatting Look for formatting issues in the source | line 201 is way too long (92 characters) | ||
| maven-resolver-impl @ 1.3.1 | formatting Look for formatting issues in the source | line 210 is way too long (92 characters) | ||
| maven-resolver-impl @ 1.3.1 | formatting Look for formatting issues in the source | line 218 is way too long (95 characters) | ||
| maven-resolver-impl @ 1.3.1 | formatting Look for formatting issues in the source | line 221 is way too long (93 characters) | ||
| maven-resolver-connector-basic @ 1.3.1 | formatting Look for formatting issues in the source | line 165 is way too long (99 characters) | ||
| maven-resolver-transport-wagon @ 1.3.1 | formatting Look for formatting issues in the source | line 255 is way too long (91 characters) | ||
| maven-resolver-transport-wagon @ 1.3.1 | formatting Look for formatting issues in the source | line 270 is way too long (106 characters) | ||
| maven-resolver-transport-wagon @ 1.3.1 | formatting Look for formatting issues in the source | line 284 is way too long (102 characters) | ||
| java-jbzip2 @ 0.9.1 | formatting Look for formatting issues in the source | line 274 is way too long (92 characters) | ||
| maven-shared-utils @ 3.2.1 | formatting Look for formatting issues in the source | line 583 is way too long (109 characters) | ||
| maven-wagon-file @ 3.3.4 | formatting Look for formatting issues in the source | line 738 is way too long (125 characters) | ||
| syncthing-gtk @ 0.9.4.4 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python2-setuptools' should probably not be an input at all | ||
| syncthing @ 1.5.0 | formatting Look for formatting issues in the source | line 109 is way too long (93 characters) | ||
| libextractor @ 1.10 | formatting Look for formatting issues in the source | line 128 is way too long (140 characters) | ||
| lxde-common @ 0.99.2 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| 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 | ||
| bison @ 3.6.3 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| bison @ 3.6.3 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| bison @ 3.5.3 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| bison @ 3.5.3 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| rtl-sdr @ 0.6.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| shogun @ 6.1.3 | inputs-should-be-native Identify inputs that should be native inputs | 'swig' should probably be a native input | ||
| shogun @ 6.1.3 | formatting Look for formatting issues in the source | line 520 is way too long (91 characters) | ||
| libringclient @ 20200710.1.6bd18d2 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| libringclient @ 20200710.1.6bd18d2 | formatting Look for formatting issues in the source | line 502 is way too long (105 characters) | ||
| jami @ 20200710.1.6bd18d2 | formatting Look for formatting issues in the source | line 536 is way too long (92 characters) | ||
| gx-go @ 1.9.0 | formatting Look for formatting issues in the source | line 186 is way too long (91 characters) | ||
| gx-go @ 1.9.0 | formatting Look for formatting issues in the source | line 191 is way too long (91 characters) | ||
| gx-go @ 1.9.0 | formatting Look for formatting issues in the source | line 196 is way too long (91 characters) | ||
| gx-go @ 1.9.0 | formatting Look for formatting issues in the source | line 197 is way too long (99 characters) | ||
| gx-go @ 1.9.0 | formatting Look for formatting issues in the source | line 198 is way too long (91 characters) | ||
| gx @ 0.14.3 | formatting Look for formatting issues in the source | line 126 is way too long (91 characters) | ||
| gx @ 0.14.3 | formatting Look for formatting issues in the source | line 131 is way too long (91 characters) | ||
| gx @ 0.14.3 | formatting Look for formatting issues in the source | line 136 is way too long (91 characters) | ||
| gx @ 0.14.3 | formatting Look for formatting issues in the source | line 137 is way too long (99 characters) | ||
| gx @ 0.14.3 | formatting Look for formatting issues in the source | line 138 is way too long (91 characters) | ||
| gx @ 0.14.3 | formatting Look for formatting issues in the source | line 145 is way too long (91 characters) | ||
| go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1 | formatting Look for formatting issues in the source | line 81 is way too long (93 characters) | ||
| go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1 | formatting Look for formatting issues in the source | line 82 is way too long (91 characters) | ||
| go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1 | formatting Look for formatting issues in the source | line 85 is way too long (93 characters) | ||
| go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1 | formatting Look for formatting issues in the source | line 88 is way too long (93 characters) | ||
| go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1 | formatting Look for formatting issues in the source | line 89 is way too long (101 characters) | ||
| go-github-com-ipfs-go-ipfs-api @ 1.3.1-0.dafc2a1 | formatting Look for formatting issues in the source | line 95 is way too long (93 characters) | ||
| ghc @ 8.6.5 | formatting Look for formatting issues in the source | line 591 is way too long (91 characters) | ||
| wxwidgets-gtk2 @ 3.1.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| wxwidgets-gtk2 @ 3.0.5.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-wxpython @ 4.0.7.post1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| cfitsio @ 3.49 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 197 | ||
| espeak-ng @ 1.50 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| zbar @ 0.23 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| flite @ 2.1 | formatting Look for formatting issues in the source | line 90 is way too long (419 characters) | ||
| help2man @ 1.47.13 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| mate-applets @ 1.24.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 917 | ||
| mate-panel @ 1.24.1 | formatting Look for formatting issues in the source | line 669 is way too long (92 characters) | ||
| mate-menus @ 1.24.1 | formatting Look for formatting issues in the source | line 509 is way too long (91 characters) | ||
| atril @ 1.22.0 | formatting Look for formatting issues in the source | line 744 is way too long (92 characters) | ||
| openfoam @ 4.1 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| openfoam @ 4.1 | formatting Look for formatting issues in the source | line 132 is way too long (109 characters) | ||
| openfoam @ 4.1 | formatting Look for formatting issues in the source | line 146 is way too long (91 characters) | ||
| python-pytools @ 2020.4 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| tuxmath @ 2.0.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| gcompris @ 17.05 | formatting Look for formatting issues in the source | line 135 is way too long (96 characters) | ||
| extra-cmake-modules @ 5.70.0 | formatting Look for formatting issues in the source | line 112 is way too long (91 characters) | ||
| python-xsge @ 2020.09.07 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| fdroidserver @ 1.1.9 | formatting Look for formatting issues in the source | line 940 is way too long (106 characters) | ||
| fastboot @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 700 is way too long (105 characters) | ||
| android-safe-iop @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 435 is way too long (95 characters) | ||
| android-libutils @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 642 is way too long (114 characters) | ||
| android-libcutils @ 7.1.2_r36 | formatting Look for formatting issues in the source | tabulation on line 277, column 20 | ||
| adb @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| adb @ 7.1.2_r36 | formatting Look for formatting issues in the source | line 385 is way too long (97 characters) | ||
| dico @ 2.10 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| cryptsetup-static @ 2.3.4 | formatting Look for formatting issues in the source | line 102 is way too long (93 characters) | ||
| python-pytest-django @ 3.10.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| spice-gtk @ 0.37 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| ibus-libhangul @ 1.5.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| librime @ 1.6.1 | formatting Look for formatting issues in the source | line 328 is way too long (93 characters) | ||
| axoloti-patcher-next @ 2.0.0 | formatting Look for formatting issues in the source | line 560 is way too long (93 characters) | ||
| kget @ 20.04.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 169 | ||
| kget @ 20.04.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| python-fpylll @ 0.5.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-fpylll @ 0.5.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| python-fpylll @ 0.5.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| perl-class-load @ 0.25 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| 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' | ||
| texlive-fonts-lm @ 51265 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 93 | ||
| guile3.0-email @ 0.2.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile3.0-commonmark @ 0.1.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-conda @ 4.8.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| guile3.0-mailutils @ 3.10 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| hackrf @ 2018.01.1-0.43e6f99 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| guile3.0-ncurses @ 3.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| 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 | ||
| 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 | ||
| docker @ 19.03.12 | formatting Look for formatting issues in the source | line 350 is way too long (95 characters) | ||
| docker @ 19.03.12 | formatting Look for formatting issues in the source | line 386 is way too long (93 characters) | ||
| containerd @ 1.2.5 | formatting Look for formatting issues in the source | line 214 is way too long (105 characters) | ||
| r-boot @ 1.3-25 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 125, 142 | ||
| lxqt @ 0.15.0 | inputs-should-be-native Identify inputs that should be native inputs | 'desktop-file-utils' should probably be a native input | ||
| malcontent @ 0.8.0 | formatting Look for formatting issues in the source | line 252 is way too long (91 characters) | ||
| lxqt-session @ 0.15.0 | formatting Look for formatting issues in the source | line 860 is way too long (92 characters) | ||
| lxqt-session @ 0.15.0 | formatting Look for formatting issues in the source | line 867 is way too long (100 characters) | ||
| lxqt-session @ 0.15.0 | formatting Look for formatting issues in the source | line 885 is way too long (98 characters) | ||
| lxqt-connman-applet @ 0.15.0-0.8a6cc14 | formatting Look for formatting issues in the source | tabulation on line 1360, column 0 | ||
| lxqt-connman-applet @ 0.15.0-0.8a6cc14 | formatting Look for formatting issues in the source | tabulation on line 1361, column 0 | ||
| lxqt-connman-applet @ 0.15.0-0.8a6cc14 | formatting Look for formatting issues in the source | tabulation on line 1362, column 0 | ||
| lxqt-connman-applet @ 0.15.0-0.8a6cc14 | formatting Look for formatting issues in the source | tabulation on line 1363, column 0 | ||
| lxqt-connman-applet @ 0.15.0-0.8a6cc14 | formatting Look for formatting issues in the source | tabulation on line 1364, column 0 | ||
| lxqt-connman-applet @ 0.15.0-0.8a6cc14 | formatting Look for formatting issues in the source | tabulation on line 1366, column 0 | ||
| gtk+ @ 2.24.32 | formatting Look for formatting issues in the source | tabulation on line 813, column 0 | ||
| gtk+ @ 2.24.32 | formatting Look for formatting issues in the source | tabulation on line 814, column 0 | ||
| gtk+ @ 2.24.32 | formatting Look for formatting issues in the source | tabulation on line 815, column 0 | ||
| at-spi2-core @ 2.34.0 | formatting Look for formatting issues in the source | line 659 is way too long (97 characters) | ||
| fstrcmp @ 0.7.D001 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 236 | ||
| python @ 3.8.2 | formatting Look for formatting issues in the source | line 480 is way too long (93 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) | ||
| catdoc @ 0.95 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 157 | ||
| ghc-base-unicode-symbols @ 0.2.3 | formatting Look for formatting issues in the source | line 955 is way too long (101 characters) | ||
| python2-langkit @ 0.0.0-0.fe0bc8b | inputs-should-be-native Identify inputs that should be native inputs | 'python2-docutils' should probably be a native input | ||
| mate-polkit @ 1.24.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| xplanet @ 1.3.1 | patch-file-names Validate file names and availability of patches | xplanet-1.3.1-libdisplay_DisplayOutput.cpp.patch: file name is too long | ||
| xplanet @ 1.3.1 | patch-file-names Validate file names and availability of patches | xplanet-1.3.1-xpUtil-Add2017LeapSecond.cpp.patch: file name is too long | ||
| racket-minimal @ 7.9 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-pycrypto @ 2.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2 @ 2.7.17 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| pjproject-jami @ 2.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| perl-parent @ 5.30.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| perl-base @ 5.30.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| owncloud-client @ 2.5.3.11470 | 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 @ 7.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 @ 7.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 @ 7.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 @ 7.0.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libstdc++-doc @ 9.3.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 | ||
| 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 | ||
| libiberty @ 7.5.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libgccjit @ 9.3.0 | 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 | ||
| ijs @ 9.52 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| idutils @ 4.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile3.0-rsvg @ 2.18.1-0.05c6a2f | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile3.0-readline @ 3.0.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile3.0-present @ 0.3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile3.0-mailutils @ 3.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile3.0-gnutls @ 3.6.12 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile3.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 | ||
| guile3.0-fibers @ 1.0.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.2-gdbm-ffi @ 20120209.fa1d5b6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.0-gdbm-ffi @ 20120209.fa1d5b6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile-static-stripped-tarball @ 2.0.14 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile-static-stripped @ 3.0.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile-static-stripped @ 2.0.14 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile-next @ 3.0.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gtk+ @ 2.24.32 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| ghostscript-with-x @ 9.52 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| ghostscript-with-cups @ 9.52 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gccgo @ 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++ @ 9.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.4.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.2.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gcc-objc @ 9.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.4.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.2.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 | ||
| enlightenment-wayland @ 0.24.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-next @ 28.0.50-0.2ea3466 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| boost-with-python3 @ 1.72.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| boost-static @ 1.72.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| boost-python2 @ 1.72.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| bash-static @ 5.0.16 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| bash-minimal @ 5.0.16 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| android-libziparchive @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| android-libutils @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| android-libsparse @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| android-liblog @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| android-libcutils @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| adb @ 7.1.2_r36 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| minizip @ 1.2.11 | formatting Look for formatting issues in the source | line 154 is way too long (115 characters) | ||
| tor @ 0.4.4.6 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 574 | ||
| julia @ 1.5.3 | formatting Look for formatting issues in the source | line 301 is way too long (107 characters) | ||
| julia @ 1.5.3 | formatting Look for formatting issues in the source | line 303 is way too long (106 characters) | ||
| python2-debtcollector @ 1.19.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-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-debtcollector @ 1.19.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-coveralls @ 1.11.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-coverage' should probably be a native input | ||
| python-pytest-vcr @ 1.0.2-1.4d6c7b3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-isort @ 0.3.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-checkdocs @ 1.2.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| tcsh @ 6.22.02 | patch-headers Validate patch headers | tcsh-fix-autotest.patch: patch lacks comment and upstream status | ||
| 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 | ||
| 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.6.5 | 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 | ||
| musl-cross @ 0.1-3.a8a6649 | formatting Look for formatting issues in the source | line 152 is way too long (92 characters) | ||
| python2-pydot @ 1.4.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| ghc-tasty-expected-failure @ 0.11.1.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 185 | ||
| ghc-operational @ 0.2.3.5 | 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.7.0.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-hsyaml @ 0.1.2.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ghc-gtk2hs-buildtools @ 0.13.5.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 95, 367 | ||
| ghc-fsnotify @ 0.3.0.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 81 | ||
| ghc-doclayout @ 0.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| tensorflow @ 1.9.0 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| pandoc @ 2.7.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| openmpi-thread-multiple @ 4.0.5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-openmpi @ 4.0.5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| tensorflow @ 1.9.0 | formatting Look for formatting issues in the source | line 1502 is way too long (92 characters) | ||
| tensorflow @ 1.9.0 | formatting Look for formatting issues in the source | line 1605 is way too long (91 characters) | ||
| tensorflow @ 1.9.0 | formatting Look for formatting issues in the source | line 1692 is way too long (137 characters) | ||
| tensorflow @ 1.9.0 | formatting Look for formatting issues in the source | line 1693 is way too long (131 characters) | ||
| tensorflow @ 1.9.0 | formatting Look for formatting issues in the source | line 1694 is way too long (137 characters) | ||
| python2-fastlmm @ 0.2.21 | formatting Look for formatting issues in the source | line 1132 is way too long (92 characters) | ||
| openmpi @ 4.0.5 | formatting Look for formatting issues in the source | line 264 is way too long (94 characters) | ||
| openmpi @ 4.0.5 | formatting Look for formatting issues in the source | line 266 is way too long (96 characters) | ||
| python-faiss @ 1.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'swig' should probably be a native input | ||
| openssh-sans-x @ 8.4p1 | 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 | ||
| emacs-xwidgets @ 27.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-wide-int @ 27.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 @ 27.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-no-x @ 27.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-minimal @ 27.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| wine64-staging @ 5.13 | inputs-should-be-native Identify inputs that should be native inputs | 'autoconf' should probably be a native input | ||
| wine-staging @ 5.13 | inputs-should-be-native Identify inputs that should be native inputs | 'autoconf' should probably be a native input | ||
| wine64-staging @ 5.13 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| wine-staging @ 5.13 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| gimp-resynthesizer @ 2.0.3 | formatting Look for formatting issues in the source | line 498 is way too long (107 characters) | ||
| python2-cryptography @ 3.1.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-asn1crypto @ 1.4.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-cryptography @ 3.1.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-asn1crypto @ 1.4.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| telepathy-mission-control @ 5.16.5 | inputs-should-be-native Identify inputs that should be native inputs | 'gtk-doc' should probably be a native input | ||
| maven-wagon-provider-api @ 3.3.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs /gnu/store/hyi21wbh8vfs1v3cy162g4rz457yli9r-maven-wagon-provider-api-3.3.4 and /gnu/store/dd25ffafrqxiwi7ly20vn6kkvd3sq9jb-maven-wagon-provider-api-3.3.4 collide | ||
| gtk+ @ 3.24.23 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| xproto @ 7.0.31 | formatting Look for formatting issues in the source | line 4988 is way too long (91 characters) | ||
| xf86-video-intel @ 2.99.917-17.ad5540f | formatting Look for formatting issues in the source | line 3025 is way too long (91 characters) | ||
| localed @ 241 | formatting Look for formatting issues in the source | line 713 is way too long (96 characters) | ||
| python-mypy @ 0.790 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| python-robber @ 1.1.5 | inputs-should-be-native Identify inputs that should be native inputs | 'python-mock' should probably be a native input | ||
| zathura-pdf-poppler @ 0.3.0 | formatting Look for formatting issues in the source | line 561 is way too long (107 characters) | ||
| zathura-djvu @ 0.2.9 | formatting Look for formatting issues in the source | line 475 is way too long (93 characters) | ||
| python2-dukpy @ 0.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-dukpy @ 0.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-arcp @ 0.2.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-sure @ 1.4.11 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-mock' should probably be a native input | ||
| python2-setuptools-scm-git-archive @ 1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-setuptools-scm' should probably be a native input | ||
| python-sure @ 1.4.11 | inputs-should-be-native Identify inputs that should be native inputs | 'python-mock' should probably be a native input | ||
| python-setuptools-scm-git-archive @ 1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-setuptools-scm' should probably be a native input | ||
| ghc-unsafe @ 0.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ghc-th-reify-many @ 0.1.9 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-rio @ 0.1.12.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ghc-regex-tdfa @ 1.2.3.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 139 | ||
| ghc-xdg-basedir @ 0.2.2 | formatting Look for formatting issues in the source | line 15244 is way too long (93 characters) | ||
| ghc-vector @ 0.12.0.3 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| ghc-th-orphans @ 0.13.9 | formatting Look for formatting issues in the source | line 13517 is way too long (92 characters) | ||
| ghc-system-filepath @ 0.4.14 | formatting Look for formatting issues in the source | line 13004 is way too long (250 characters) | ||
| gobject-introspection @ 1.62.0 | inputs-should-be-native Identify inputs that should be native inputs | 'bison' should probably be a native input | ||
| gobject-introspection @ 1.62.0 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| xorg-server-xwayland @ 1.20.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gobject-introspection @ 1.62.0 | patch-file-names Validate file names and availability of patches | gobject-introspection-absolute-shlib-path.patch: file name is too long | ||
| gobject-introspection @ 1.62.0 | patch-headers Validate patch headers | gobject-introspection-girepository.patch: patch lacks comment and upstream status | ||
| c-blosc @ 1.18.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 64 | ||
| google-brotli @ 1.0.9 | formatting Look for formatting issues in the source | line 1915 is way too long (94 characters) | ||
| guile2.2-gnutls @ 3.6.12 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.0-gnutls @ 3.6.12 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| gnutls-dane @ 3.6.15 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 506, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 507, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 508, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 509, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 510, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 511, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 512, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 513, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 514, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 516, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 517, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 518, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 519, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 520, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 522, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 523, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 524, column 0 | ||
| openssl @ 1.0.2u | formatting Look for formatting issues in the source | tabulation on line 525, column 0 | ||
| robin-map @ 0.6.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 281 | ||
| sdsl-lite @ 2.1.1 | formatting Look for formatting issues in the source | line 237 is way too long (145 characters) | ||
| 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.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ghc-hxt-unicode @ 9.0.2.4 | formatting Look for formatting issues in the source | line 1486 is way too long (91 characters) | ||
| rust-winit @ 0.20.0-alpha6 | formatting Look for formatting issues in the source | line 2217 is way too long (114 characters) | ||
| mesa-opencl-icd @ 20.1.9 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mesa-opencl @ 20.1.9 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mesa-headers @ 20.1.9 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| mesa @ 20.1.9 | formatting Look for formatting issues in the source | line 299 is way too long (120 characters) | ||
| libmypaint @ 1.6.1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| mailutils @ 3.10 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| guile2.2-mailutils @ 3.10 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| guile2.2-mailutils @ 3.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| fcitx5-gtk @ 5.0.1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| i3-wm @ 4.18.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| keybinder-3.0 @ 0.3.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| awesome @ 4.3 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| quickswitch-i3 @ 2.2-1.ed692b1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-pypandoc @ 1.5 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-eliot @ 1.12.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 153 | ||
| python2-djvulibre @ 0.8.5 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-cython' should probably be a native input | ||
| python-readme-renderer @ 26.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-pytest-check-links @ 0.3.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-pytest-check-links @ 0.3.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pifpaf @ 2.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-iocapture @ 0.1.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-iocapture @ 0.1.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest-cov' should probably be a native input | ||
| python-docusign-esign @ 3.1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-nose' should probably be a native input | ||
| python-djvulibre @ 0.8.5 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| python-argh @ 0.26.2-1.dcd3253 | inputs-should-be-native Identify inputs that should be native inputs | 'python-mock' should probably be a native input | ||
| python-argh @ 0.26.2-1.dcd3253 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-argh @ 0.26.2-1.dcd3253 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest-cov' should probably be a native input | ||
| python-eliot @ 1.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 | ||
| calibre @ 4.18.0 | formatting Look for formatting issues in the source | line 247 is way too long (93 characters) | ||
| icu4c-build-root @ 66.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-minimal @ 2.7.17 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-next @ 3.9.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-minimal @ 3.8.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-debug @ 3.8.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| pypy3 @ 7.3.1 | formatting Look for formatting issues in the source | line 862 is way too long (91 characters) | ||
| python2-sphinxcontrib-programoutput @ 0.15 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python2-sphinx-rtd-theme @ 0.2.4 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python2-sphinx-repoze-autointerface @ 0.8 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python2-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-sphinxcontrib-svg2pdfconverter @ 1.0.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinxcontrib-programoutput @ 0.15 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinxcontrib-newsfeed @ 0.1.4 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx-rtd-theme @ 0.2.4 | 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-copybutton @ 0.2.6 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx @ 3.2.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-pytest-sanic @ 1.6.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-nbsphinx @ 0.7.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-nbsphinx @ 0.7.1 | 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.22.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-breathe @ 4.22.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-sphinx-copybutton @ 0.2.6 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| maven-surefire-plugin @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide | ||
| maven-surefire-common @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide | ||
| maven-shared-utils @ 3.1.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@16 and apache-parent-pom@18 collide | ||
| maven-shared-utils @ 3.0.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-shared-io @ 3.0.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@39 collide | ||
| maven-shared-incremental @ 1.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-settings-builder @ 3.6.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide | ||
| maven-settings-builder @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide | ||
| maven-resources-plugin @ 3.1.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide | ||
| maven-resolver-provider @ 3.6.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-plugin-api @ 3.6.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide | ||
| maven-plugin-api @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide | ||
| maven-model-builder @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide | ||
| maven-model @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide | ||
| maven-jar-plugin @ 3.2.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@39 and apache-commons-parent-pom@41 collide | ||
| maven-install-plugin @ 3.0.0-M1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide | ||
| maven-filtering @ 3.1.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@39 collide | ||
| maven-file-management @ 3.0.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@48 and apache-commons-parent-pom@39 collide | ||
| maven-enforcer-rules @ 3.0.0-M3 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-artifact@3.6.1 and maven-artifact@3.0 collide | ||
| maven-enforcer-plugin @ 3.0.0-M3 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@18 collide | ||
| maven-enforcer-api @ 3.0.0-M3 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-embedder @ 3.6.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide | ||
| maven-dependency-tree @ 3.0.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-compiler-plugin @ 3.8.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-compat @ 3.6.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide | ||
| maven-compat @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide | ||
| maven-common-artifact-filters @ 3.1.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| maven-artifact-transfer @ 0.12.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide | ||
| maven-artifact @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide | ||
| maven-archiver @ 3.5.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@39 and apache-commons-parent-pom@41 collide | ||
| maven-aether-provider @ 3.0 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide | ||
| java-surefire-extensions-api @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide | ||
| java-surefire-common-junit4 @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide | ||
| java-surefire-common-junit3 @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide | ||
| java-surefire-common-java5 @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@16 and apache-parent-pom@21 collide | ||
| java-surefire-booter @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-commons-parent-pom@50 and apache-commons-parent-pom@39 collide | ||
| java-surefire-api @ 3.0.0-M4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs maven-parent-pom@33 and maven-parent-pom@30 collide | ||
| maven-settings-builder @ 3.6.1 | 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.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-settings @ 3.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.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-repository-metadata @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-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.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-plugin-api @ 3.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.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-model-builder @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-model @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-model @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-enforcer-rules @ 3.0.0-M3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-enforcer-plugin @ 3.0.0-M3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-embedder @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-compat @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-compat @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-builder-support @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-artifact @ 3.6.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-artifact @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-aether-provider @ 3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| maven-wagon-http @ 3.3.4 | formatting Look for formatting issues in the source | line 901 is way too long (105 characters) | ||
| maven-wagon-http @ 3.3.4 | formatting Look for formatting issues in the source | line 906 is way too long (138 characters) | ||
| maven-wagon-http @ 3.3.4 | formatting Look for formatting issues in the source | line 907 is way too long (129 characters) | ||
| maven-surefire-plugin @ 3.0.0-M4 | formatting Look for formatting issues in the source | line 3607 is way too long (113 characters) | ||
| maven-surefire-plugin @ 3.0.0-M4 | formatting Look for formatting issues in the source | line 3608 is way too long (111 characters) | ||
| maven-embedder @ 3.6.1 | formatting Look for formatting issues in the source | line 1638 is way too long (110 characters) | ||
| java-surefire-booter @ 3.0.0-M4 | formatting Look for formatting issues in the source | line 3271 is way too long (107 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 | ||
| python2-pygobject @ 3.34.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python2-pygobject @ 2.28.7 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python-pygobject @ 3.34.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| telepathy-glib @ 0.24.1 | formatting Look for formatting issues in the source | line 876 is way too long (92 characters) | ||
| python2-pygobject @ 3.34.0 | formatting Look for formatting issues in the source | line 803 is way too long (95 characters) | ||
| appstream-glib @ 0.7.18 | formatting Look for formatting issues in the source | line 1037 is way too long (93 characters) | ||
| r-bsgenome-dmelanogaster-ucsc-dm3-masked @ 1.3.99 | formatting Look for formatting issues in the source | line 220 is way too long (95 characters) | ||
| ppsspp @ 1.10.3 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| geda-gaf @ 1.10.0 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| librecad @ 2.1.3 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| chez-srfi @ 1.0 | formatting Look for formatting issues in the source | line 246 is way too long (91 characters) | ||
| kdbusaddons @ 5.70.0 | formatting Look for formatting issues in the source | line 647 is way too long (107 characters) | ||
| emacs-clang-rename @ 9.0.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-clang-format @ 9.0.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| clang-runtime @ 3.9.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| clang-runtime @ 3.9.1 | patch-file-names Validate file names and availability of patches | clang-runtime-3.9-libsanitizer-mode-field.patch: file name is too long | ||
| clang-runtime @ 3.8.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| clang-runtime @ 3.8.1 | patch-file-names Validate file names and availability of patches | clang-runtime-3.8-libsanitizer-mode-field.patch: file name is too long | ||
| clang-runtime @ 3.7.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| clang-runtime @ 3.7.1 | patch-file-names Validate file names and availability of patches | clang-runtime-3.8-libsanitizer-mode-field.patch: file name is too long | ||
| clang-runtime @ 3.5.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| clang-runtime @ 3.5.2 | patch-file-names Validate file names and availability of patches | clang-runtime-3.5-libsanitizer-mode-field.patch: file name is too long | ||
| clang @ 9.0.1 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| clang @ 8.0.0 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| clang @ 7.0.1 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| clang @ 6.0.1 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| clang @ 3.9.1 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| clang @ 3.8.1 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| clang @ 3.7.1 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| clang @ 3.6.2 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| clang @ 3.5.2 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| clang @ 11.0.0 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| clang @ 10.0.0 | formatting Look for formatting issues in the source | line 366 is way too long (91 characters) | ||
| python-reno @ 2.7.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-oslo.log @ 3.36.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-oslo.config @ 5.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' should probably be a native input | ||
| python-openstackdocstheme @ 1.18.1 | 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 | ||
| ucsim @ 0.6-pre67 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| gdb-arm-none-eabi @ 9.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-libmpsse @ 1.4.1 | formatting Look for formatting issues in the source | line 1132 is way too long (96 characters) | ||
| python-libmpsse @ 1.4.1 | formatting Look for formatting issues in the source | line 1099 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 | ||
| unbound @ 1.13.0 | formatting Look for formatting issues in the source | trailing white space on line 683 | ||
| unbound @ 1.13.0 | formatting Look for formatting issues in the source | trailing white space on line 719 | ||
| fc-host-tools @ 14 | formatting Look for formatting issues in the source | line 1223 is way too long (122 characters) | ||
| patchwork @ 3.0.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| emacs-cmake-mode @ 3.19.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| 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 1020 is way too long (100 characters) | ||
| lua-resty-signal @ 0.02 | formatting Look for formatting issues in the source | line 985 is way too long (104 characters) | ||
| lua-resty-signal @ 0.02 | formatting Look for formatting issues in the source | line 986 is way too long (93 characters) | ||
| lua-resty-signal @ 0.02 | formatting Look for formatting issues in the source | line 987 is way too long (123 characters) | ||
| lua-resty-signal @ 0.02 | formatting Look for formatting issues in the source | line 988 is way too long (112 characters) | ||
| lua-resty-shell @ 0.03 | formatting Look for formatting issues in the source | line 1052 is way too long (100 characters) | ||
| lua-resty-shell @ 0.03 | formatting Look for formatting issues in the source | line 1054 is way too long (119 characters) | ||
| lua-resty-shell @ 0.03 | formatting Look for formatting issues in the source | line 1055 is way too long (108 characters) | ||
| lua-resty-lrucache @ 0.10 | formatting Look for formatting issues in the source | line 945 is way too long (100 characters) | ||
| lua-resty-lrucache @ 0.10 | formatting Look for formatting issues in the source | line 947 is way too long (119 characters) | ||
| lua-resty-lrucache @ 0.10 | formatting Look for formatting issues in the source | line 948 is way too long (108 characters) | ||
| lua-resty-core @ 0.1.18 | formatting Look for formatting issues in the source | line 910 is way too long (95 characters) | ||
| wpa-supplicant-minimal @ 2.9 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| wpa-supplicant-gui @ 2.9 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| wpa-supplicant @ 2.9 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| debops @ 1.1.0 | patch-file-names Validate file names and availability of patches | debops-constants-for-external-program-names.patch: file name is too long | ||
| qucs-s @ 0.0.21 | inputs-should-be-native Identify inputs that should be native inputs | 'libtool' should probably be a native input | ||
| qucs @ 0.0.19-0.b4f27d9 | inputs-should-be-native Identify inputs that should be native inputs | 'libtool' should probably be a native input | ||
| lepton-eda @ 1.9.13-20201211 | 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 | ||
| qucs-s @ 0.0.21 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| fritzing @ 0.9.3b | formatting Look for formatting issues in the source | line 669 is way too long (91 characters) | ||
| fritzing @ 0.9.3b | formatting Look for formatting issues in the source | line 670 is way too long (99 characters) | ||
| freehdl @ 0.0.8 | formatting Look for formatting issues in the source | line 1896 is way too long (104 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 | ||
| ir @ 1.3.4 | formatting Look for formatting issues in the source | trailing white space on line 1914 | ||
| faad2 @ 2.8.8 | formatting Look for formatting issues in the source | line 1660 is way too long (95 characters) | ||
| audacity @ 2.4.2 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| python2-html2text @ 2019.8.11 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-html2text @ 2020.1.16 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| electron-cash @ 4.2.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| awscli @ 1.18.203 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-requests @ 2.20.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs python-urllib3@1.24.3 and python-urllib3@1.25.9 collide | ||
| python2-paste @ 3.0.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-wtforms @ 2.1 | formatting Look for formatting issues in the source | line 4020 is way too long (92 characters) | ||
| python2-wtforms @ 2.1 | formatting Look for formatting issues in the source | line 4021 is way too long (100 characters) | ||
| python-wtforms @ 2.1 | formatting Look for formatting issues in the source | line 4020 is way too long (92 characters) | ||
| python-wtforms @ 2.1 | formatting Look for formatting issues in the source | line 4021 is way too long (100 characters) | ||
| python-tornado @ 5.1.1 | formatting Look for formatting issues in the source | line 1614 is way too long (91 characters) | ||
| libsecp256k1 @ 20200615-1.dbd41db | formatting Look for formatting issues in the source | line 1055 is way too long (106 characters) | ||
| sbcl-cl-strings @ 0.0.0-1.c5c5cba | formatting Look for formatting issues in the source | line 1085 is way too long (98 characters) | ||
| ecl-cl-strings @ 0.0.0-1.c5c5cba | formatting Look for formatting issues in the source | line 1085 is way too long (98 characters) | ||
| cl-strings @ 0.0.0-1.c5c5cba | formatting Look for formatting issues in the source | line 1085 is way too long (98 characters) | ||
| xdg-user-dirs @ 0.17 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 116 | ||
| udiskie @ 2.1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| plymouth @ 0.9.4 | formatting Look for formatting issues in the source | line 1927 is way too long (91 characters) | ||
| python2-clf @ 0.5.7 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-nose' should probably be a native input | ||
| python-pytest-httpbin @ 0.2.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-clf @ 0.5.7 | inputs-should-be-native Identify inputs that should be native inputs | 'python-nose' should probably be a native input | ||
| java-eclipse-jetty-xml @ 9.4.6 | 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.6 | 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 @ 9.4.6 | 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.6 | 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.6 | 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.6 | 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.6 | 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.6 | 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.6 | 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 | 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 | ||
| varnish @ 6.5.1 | formatting Look for formatting issues in the source | line 5913 is way too long (91 characters) | ||
| serf @ 1.3.9 | formatting Look for formatting issues in the source | line 1864 is way too long (92 characters) | ||
| nginx-accept-language-module @ 0.0.0-1.2f69842 | formatting Look for formatting issues in the source | line 531 is way too long (92 characters) | ||
| krona-tools @ 2.7 | formatting Look for formatting issues in the source | trailing white space on line 1160 | ||
| xygrib @ 1.2.6.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 256 | ||
| osm-gps-map @ 1.1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| tegola @ 0.7.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| python2-mapnik @ 3.0.16 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| imposm3 @ 0.6.0-alpha.4 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| libgeotiff @ 1.5.1 | patch-file-names Validate file names and availability of patches | libgeotiff-adapt-test-script-for-proj-6.2.patch: file name is too long | ||
| xygrib @ 1.2.6.1 | formatting Look for formatting issues in the source | line 1185 is way too long (95 characters) | ||
| proj.4 @ 4.9.3 | formatting Look for formatting issues in the source | line 534 is way too long (92 characters) | ||
| ublock-origin-chromium @ 1.32.4 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-yapsa @ 1.16.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 93, 96 | ||
| r-rgadem @ 2.38.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-mixomics @ 6.14.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-iclusterplus @ 1.26.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-biosigner @ 1.18.2 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-biocio @ 1.0.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| r-bioassayr @ 1.28.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-unifiedwmwqpcr @ 1.26.0 | formatting Look for formatting issues in the source | line 7431 is way too long (92 characters) | ||
| r-monocle @ 2.18.0 | formatting Look for formatting issues in the source | line 3160 is way too long (101 characters) | ||
| r-lumi @ 2.42.0 | formatting Look for formatting issues in the source | line 3580 is way too long (95 characters) | ||
| r-hsmmsinglecell @ 1.2.0 | formatting Look for formatting issues in the source | line 972 is way too long (95 characters) | ||
| r-genomicinteractions @ 1.24.0 | formatting Look for formatting issues in the source | line 2380 is way too long (92 characters) | ||
| ruby-iruby @ 0.3 | formatting Look for formatting issues in the source | line 505 is way too long (112 characters) | ||
| ruby-asciidoctor-pdf @ 1.5.3-1.d257440 | formatting Look for formatting issues in the source | line 1737 is way too long (99 characters) | ||
| tigervnc-server @ 1.11.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| tigervnc-server @ 1.11.0 | formatting Look for formatting issues in the source | line 178 is way too long (102 characters) | ||
| tigervnc-server @ 1.11.0 | formatting Look for formatting issues in the source | line 181 is way too long (102 characters) | ||
| tigervnc-server @ 1.11.0 | formatting Look for formatting issues in the source | tabulation on line 190, column 0 | ||
| abc @ 0.0-1.5ae4b97 | formatting Look for formatting issues in the source | line 94 is way too long (95 characters) | ||
| libchop @ 0.5.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 248, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 249, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 250, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 251, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 252, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 253, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 254, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 255, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 256, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 259, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 260, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 262, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 263, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 264, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 265, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 266, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 268, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 269, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 270, column 0 | ||
| libarchive @ 3.4.2 | formatting Look for formatting issues in the source | tabulation on line 271, column 0 | ||
| python-pyportmidi @ 217 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| solfege @ 3.22.2 | formatting Look for formatting issues in the source | line 1711 is way too long (92 characters) | ||
| gtklick @ 0.6.4 | formatting Look for formatting issues in the source | line 1146 is way too long (94 characters) | ||
| sooperlooper @ 1.7.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 120 | ||
| python2-discogs-client @ 2.2.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 50 | ||
| python-discogs-client @ 2.2.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 50 | ||
| drumstick @ 2.0.0 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| beets @ 1.4.9 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| vmpk @ 0.8.0 | formatting Look for formatting issues in the source | line 2580 is way too long (91 characters) | ||
| drumstick @ 2.0.0 | formatting Look for formatting issues in the source | line 2533 is way too long (91 characters) | ||
| 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 | ||
| git-crypt @ 0.6.0 | formatting Look for formatting issues in the source | line 781 is way too long (91 characters) | ||
| bazaar @ 2.7.0 | formatting Look for formatting issues in the source | line 152 is way too long (93 characters) | ||
| perl-specio @ 0.38 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 185, 314 | ||
| perl-file-which @ 1.23 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| perl-file-readbackwards @ 1.05 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 47 | ||
| perl-extutils-pkgconfig @ 1.16 | inputs-should-be-native Identify inputs that should be native inputs | 'pkg-config' should probably be a native input | ||
| perl-sys-cpu @ 0.61 | formatting Look for formatting issues in the source | line 9382 is way too long (97 characters) | ||
| python2-pygame @ 1.9.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 123 | ||
| python-pygame @ 1.9.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 123 | ||
| openjpeg-data @ 2020.05.19 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 116 | ||
| libjxr @ 1.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 99 | ||
| 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 | ||
| python2-renpy @ 7.3.5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| aws-checksums @ 0.1.10 | patch-headers Validate patch headers | aws-checksums-cmake-prefix.patch: patch lacks comment and upstream status | ||
| aws-c-event-stream @ 0.1.6 | patch-headers Validate patch headers | aws-c-event-stream-cmake-prefix.patch: patch lacks comment and upstream status | ||
| restinio @ 0.6.1.1 | formatting Look for formatting issues in the source | line 3347 is way too long (105 characters) | ||
| restinio @ 0.6.1.1 | formatting Look for formatting issues in the source | line 3361 is way too long (95 characters) | ||
| restbed @ 4.6-1.6eb385f | formatting Look for formatting issues in the source | line 3322 is way too long (92 characters) | ||
| love-nuklear @ v2.6-1.fef4e00 | formatting Look for formatting issues in the source | trailing white space on line 725 | ||
| libjxr @ 1.1 | formatting Look for formatting issues in the source | line 520 is way too long (95 characters) | ||
| dmraid @ 1.0.0.rc16-3 | formatting Look for formatting issues in the source | line 824 is way too long (91 characters) | ||
| python2-argcomplete @ 1.11.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-argcomplete @ 1.11.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ptpython2 @ 3.0.5 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-xopen @ 0.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-setuptools-scm' should probably be a native input | ||
| python2-m2r @ 0.2.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-docutils' should probably be a native input | ||
| python-xopen @ 0.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-setuptools-scm' should probably be a native input | ||
| python-rst2ansi @ 0.1.5 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-mamba @ 0.11.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-coverage' should probably be a native input | ||
| python-m2r @ 0.2.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python2-packaging @ 20.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-larch @ 1.20151025 | patch-file-names Validate file names and availability of patches | python2-larch-coverage-4.0a6-compatibility.patch: file name is too long | ||
| python2-argcomplete @ 1.11.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| rust @ 1.47.0 | formatting Look for formatting issues in the source | line 1336 is way too long (98 characters) | ||
| rust @ 1.47.0 | formatting Look for formatting issues in the source | line 1342 is way too long (91 characters) | ||
| rust @ 1.26.2 | formatting Look for formatting issues in the source | line 788 is way too long (94 characters) | ||
| rust @ 1.25.0 | formatting Look for formatting issues in the source | line 749 is way too long (91 characters) | ||
| mrustc @ 0.9 | formatting Look for formatting issues in the source | line 178 is way too long (123 characters) | ||
| perl-search-xapian @ 1.2.25.4 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| gaupol @ 1.9 | formatting Look for formatting issues in the source | line 4530 is way too long (95 characters) | ||
| 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.7.0 | 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 | ||
| rav1e @ 0.3.5 | inputs-should-be-native Identify inputs that should be native inputs | 'nasm' 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 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 293, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 295, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 298, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 299, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 308, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 309, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 310, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 311, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 312, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 313, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 314, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 316, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 317, column 0 | ||
| slim @ 1.3.6 | formatting Look for formatting issues in the source | tabulation on line 318, column 0 | ||
| go-github-com-rogpeppe-go-internal @ 1.6.1 | formatting Look for formatting issues in the source | line 6301 is way too long (101 characters) | ||
| go-github-com-multiformats-go-multiaddr-net @ 1.6.3-0.1cb9a0e | formatting Look for formatting issues in the source | line 3477 is way too long (93 characters) | ||
| go-github-com-multiformats-go-multiaddr-net @ 1.6.3-0.1cb9a0e | formatting Look for formatting issues in the source | line 3478 is way too long (93 characters) | ||
| go-github-com-multiformats-go-multiaddr @ 1.3.0-0.fe1c46f | formatting Look for formatting issues in the source | line 3434 is way too long (93 characters) | ||
| go-github-com-mitchellh-go-homedir @ 1.0.0-0.ae18d6b | formatting Look for formatting issues in the source | line 3321 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-libp2p-go-libp2p-peer @ 2.3.8-0.993d742 | formatting Look for formatting issues in the source | line 3226 is way too long (93 characters) | ||
| go-github-com-libp2p-go-libp2p-metrics @ 2.1.6-0.a10ff6e | formatting Look for formatting issues in the source | line 3282 is way too long (93 characters) | ||
| go-github-com-libp2p-go-libp2p-metrics @ 2.1.6-0.a10ff6e | formatting Look for formatting issues in the source | line 3285 is way too long (93 characters) | ||
| go-github-com-gorilla-context @ 0.0.0-0.08b5f42 | formatting Look for formatting issues in the source | line 1675 is way too long (164 characters) | ||
| go-github-com-davecgh-go-spew @ 1.1.1 | formatting Look for formatting issues in the source | line 2889 is way too long (129 characters) | ||
| mosquitto @ 1.6.12 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 347 | ||
| poezio @ 0.13.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| gajim @ 1.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 | ||
| gajim @ 1.2.2 | patch-headers Validate patch headers | gajim-honour-GAJIM_PLUGIN_PATH.patch: patch lacks comment and upstream status | ||
| xwallpaper @ 0.6.5 | 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 | ||
| guile3.0-gi @ 0.3.1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| xftwidth @ 20170402 | formatting Look for formatting issues in the source | tabulation on line 1652, column 0 | ||
| xftwidth @ 20170402 | formatting Look for formatting issues in the source | tabulation on line 1653, column 0 | ||
| xftwidth @ 20170402 | formatting Look for formatting issues in the source | tabulation on line 1655, column 0 | ||
| xftwidth @ 20170402 | formatting Look for formatting issues in the source | tabulation on line 1656, column 0 | ||
| gtkspell3 @ 3.0.10 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| guile2.2-rsvg @ 2.18.1-0.05c6a2f | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.2-present @ 0.3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| qtwebglplugin @ 5.14.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 41 | ||
| qtdatavis3d @ 5.14.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 107, 250 | ||
| qtcharts @ 5.14.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 | ||
| python2-pyqt @ 5.14.2 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| python-pyqt-without-qtwebkit @ 5.14.2 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| python-pyqt @ 5.14.2 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| python2-pyqt @ 5.14.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-pyqt-without-qtwebkit @ 5.14.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-pyqt @ 5.14.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| qtserialport @ 5.14.2 | formatting Look for formatting issues in the source | line 1045 is way too long (115 characters) | ||
| qtsensors @ 5.14.2 | formatting Look for formatting issues in the source | line 894 is way too long (97 characters) | ||
| qtremoteobjects @ 5.14.2 | formatting Look for formatting issues in the source | line 1517 is way too long (94 characters) | ||
| qtmultimedia @ 5.14.2 | formatting Look for formatting issues in the source | line 937 is way too long (96 characters) | ||
| qtbase @ 5.14.2 | formatting Look for formatting issues in the source | line 446 is way too long (96 characters) | ||
| qtbase @ 5.14.2 | formatting Look for formatting issues in the source | line 573 is way too long (97 characters) | ||
| qtbase @ 5.14.2 | formatting Look for formatting issues in the source | line 578 is way too long (94 characters) | ||
| qtbase @ 5.14.2 | formatting Look for formatting issues in the source | line 580 is way too long (94 characters) | ||
| python-pyqt @ 5.14.2 | formatting Look for formatting issues in the source | line 2062 is way too long (105 characters) | ||
| shell-functools @ 0.3.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 121, 206 | ||
| sh-z @ 1.11 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| python2-rst.linker @ 1.11 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-q @ 2.6 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-pyaml @ 18.11.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-psutil @ 5.7.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-editor @ 1.0.4 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-dnspython @ 1.16.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-dbus @ 1.2.16 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-rst.linker @ 1.11 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-q @ 2.6 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-pywinrm @ 0.4.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-pyquery @ 1.2.17 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-pyaml @ 18.11.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-py3status @ 3.21 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-psutil @ 5.7.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-jinja2-time @ 0.2.0 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| python-dnspython @ 2.0.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-dnspython @ 1.16.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| snakemake @ 5.7.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python2-pkgconfig @ 1.3.1 | inputs-should-be-native Identify inputs that should be native inputs | 'pkg-config' should probably be a native input | ||
| python2-numpydoc @ 0.8.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python2-matplotlib @ 2.2.4 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python-restructuredtext-lint @ 1.3.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-pytest-black @ 0.3.8 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pkgconfig @ 1.3.1 | inputs-should-be-native Identify inputs that should be native inputs | 'pkg-config' should probably be a native input | ||
| python-numpydoc @ 0.8.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-moto @ 1.3.16.dev134 | inputs-should-be-native Identify inputs that should be native inputs | 'python-mock' should probably be a native input | ||
| python-matplotlib @ 3.1.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| python-legacy-api-wrap @ 1.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-legacy-api-wrap @ 1.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest-cov' should probably be a native input | ||
| python-jsonrpc-server @ 0.4.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-mock' should probably be a native input | ||
| python-jsonrpc-server @ 0.4.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-jaraco-packaging @ 6.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-jaraco-packaging @ 6.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-setuptools-scm' should probably be a native input | ||
| python-jaraco-packaging @ 6.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-sphinx' should probably be a native input | ||
| python-get-version @ 2.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-get-version @ 2.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest-cov' should probably be a native input | ||
| python-doc8 @ 0.8.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python-case @ 1.5.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-mock' should probably be a native input | ||
| python-case @ 1.5.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-nose' should probably be a native input | ||
| pelican @ 4.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| python2-virtualenv @ 20.2.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python2-setuptools' should probably not be an input at all | ||
| python2-ipython-cluster-helper @ 0.6.4 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python2-setuptools' should probably not be an input at all | ||
| python-virtualenv @ 20.2.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-legacy-api-wrap @ 1.2 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-jaraco-packaging @ 6.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-ipython-cluster-helper @ 0.6.4 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| python-get-version @ 2.1 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-setuptools' should probably not be an input at all | ||
| poetry @ 1.1.4 | inputs-should-not-be-input Identify inputs that shouldn't be inputs at all | 'python-pip' should probably not be an input at all | ||
| python2-waitress @ 1.1.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-pybugz @ 0.6.11 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-pep8 @ 1.7.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-configobj @ 5.0.6 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| scons @ 3.0.4 | formatting Look for formatting issues in the source | line 2300 is way too long (96 characters) | ||
| python-numpy @ 1.17.3 | formatting Look for formatting issues in the source | line 4570 is way too long (152 characters) | ||
| python-matplotlib @ 3.1.2 | formatting Look for formatting issues in the source | line 5126 is way too long (107 characters) | ||
| python-matplotlib @ 3.1.2 | formatting Look for formatting issues in the source | line 5166 is way too long (96 characters) | ||
| python-matplotlib @ 3.1.2 | formatting Look for formatting issues in the source | line 5187 is way too long (105 characters) | ||
| python-ipython-documentation @ 7.9.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| python-boto3 @ 1.16.22 | formatting Look for formatting issues in the source | tabulation on line 11347, column 0 | ||
| python-boto3 @ 1.16.22 | formatting Look for formatting issues in the source | tabulation on line 11348, column 0 | ||
| python-boto3 @ 1.16.22 | formatting Look for formatting issues in the source | tabulation on line 11349, column 0 | ||
| meshlab @ 2020.06 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| libmediaart @ 1.9.4 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| gnome-contacts @ 3.34 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| zeitgeist @ 1.0.3 | formatting Look for formatting issues in the source | tabulation on line 751, column 18 | ||
| zeitgeist @ 1.0.3 | formatting Look for formatting issues in the source | tabulation on line 754, column 18 | ||
| gnome-initial-setup @ 3.32.1 | formatting Look for formatting issues in the source | line 1396 is way too long (91 characters) | ||
| grantleetheme @ 20.04.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| rcm @ 1.3.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 183 | ||
| eid-mw @ 5.0.11 | formatting Look for formatting issues in the source | line 156 is way too long (97 characters) | ||
| eid-mw @ 5.0.11 | 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 | ||
| rust-async-process @ 1.0.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| rust-bitstream-io @ 0.8.5 | formatting Look for formatting issues in the source | line 3719 is way too long (111 characters) | ||
| rust-bitstream-io @ 0.8.5 | formatting Look for formatting issues in the source | line 3721 is way too long (111 characters) | ||
| rust-async-compression @ 0.3.5 | formatting Look for formatting issues in the source | line 1989 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 | ||
| libnfs @ 3.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 | ||
| geany @ 1.37.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| glibc-locales-2.29 @ 2.29 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| glibc-locales @ 2.31 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| glibc-hurd-headers @ 2.31 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| coreutils-minimal @ 8.32 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| binutils-gold @ 2.34 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| glibc @ 2.31 | formatting Look for formatting issues in the source | line 810 is way too long (98 characters) | ||
| bsd-games @ 2.17.0 | patch-headers Validate patch headers | bsd-games-gamescreen.h.patch: patch lacks comment and upstream status | ||
| js-mathjax @ 2.7.2 | formatting Look for formatting issues in the source | line 150 is way too long (91 characters) | ||
| js-filesaver @ 1.3.8 | formatting Look for formatting issues in the source | line 534 is way too long (99 characters) | ||
| abseil-cpp @ 20200225.2 | formatting Look for formatting issues in the source | line 622 is way too long (116 characters) | ||
| abseil-cpp @ 20200225.2 | formatting Look for formatting issues in the source | line 623 is way too long (144 characters) | ||
| php @ 7.4.14 | formatting Look for formatting issues in the source | line 188 is way too long (93 characters) | ||
| php @ 7.4.14 | formatting Look for formatting issues in the source | line 189 is way too long (93 characters) | ||
| php @ 7.4.14 | formatting Look for formatting issues in the source | line 197 is way too long (91 characters) | ||
| php @ 7.4.14 | formatting Look for formatting issues in the source | line 205 is way too long (93 characters) | ||
| php @ 7.4.14 | formatting Look for formatting issues in the source | line 227 is way too long (92 characters) | ||
| php @ 7.4.14 | formatting Look for formatting issues in the source | line 228 is way too long (96 characters) | ||
| php @ 7.4.14 | formatting Look for formatting issues in the source | line 233 is way too long (96 characters) | ||
| php @ 7.4.14 | formatting Look for formatting issues in the source | line 275 is way too long (91 characters) | ||
| php @ 7.4.14 | formatting Look for formatting issues in the source | line 288 is way too long (92 characters) | ||
| gnome-shell-extension-gsconnect @ 33 | 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 @ 38 | inputs-should-be-native Identify inputs that should be native inputs | 'glib:bin' should probably be a native input | ||
| perl-test-object @ 0.08 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| mia @ 2.4.6 | inputs-should-be-native Identify inputs that should be native inputs | 'doxygen' should probably be a native input | ||
| opencv @ 3.4.3 | formatting Look for formatting issues in the source | line 396 is way too long (132 characters) | ||
| rust-funty @ 1.1.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 127 | ||
| rust-libnghttp2-sys @ 0.1.4+1.41.0 | inputs-should-be-native Identify inputs that should be native inputs | 'pkg-config' should probably be a native input | ||
| rust-parking-lot @ 0.11.0 | formatting Look for formatting issues in the source | line 22835 is way too long (102 characters) | ||
| rust-nix @ 0.15.0 | formatting Look for formatting issues in the source | line 20685 is way too long (93 characters) | ||
| rust-gimli @ 0.20.0 | formatting Look for formatting issues in the source | line 13516 is way too long (91 characters) | ||
| rust-rustc-tools-util @ 0.2.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| rust-packed-struct @ 0.3.0 | formatting Look for formatting issues in the source | tabulation on line 41282, column 0 | ||
| rust-packed-struct @ 0.3.0 | formatting Look for formatting issues in the source | tabulation on line 41284, column 0 | ||
| rust-packed-struct @ 0.3.0 | formatting Look for formatting issues in the source | tabulation on line 41285, column 0 | ||
| rust-inflections @ 1.1.1 | formatting Look for formatting issues in the source | line 41410 is way too long (107 characters) | ||
| rust-inflections @ 1.1.1 | formatting Look for formatting issues in the source | line 41412 is way too long (107 characters) | ||
| python-trezor-agent @ 0.13.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-docutils' should probably be a native input | ||
| sorcer @ 1.1.3 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| rosegarden @ 20.12 | formatting Look for formatting issues in the source | line 4669 is way too long (94 characters) | ||
| rosegarden @ 20.12 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5143, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5144, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5145, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5146, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5148, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5155, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5156, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5157, column 0 | ||
| fmit @ 1.2.14 | formatting Look for formatting issues in the source | tabulation on line 5158, column 0 | ||
| icecat @ 78.6.1-guix0-preview1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| icecat @ 78.6.1-guix0-preview1 | formatting Look for formatting issues in the source | line 1003 is way too long (102 characters) | ||
| icecat @ 78.6.1-guix0-preview1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| icecat @ 78.6.1-guix0-preview1 | formatting Look for formatting issues in the source | line 1095 is way too long (139 characters) | ||
| icecat @ 78.6.1-guix0-preview1 | formatting Look for formatting issues in the source | line 1101 is way too long (95 characters) | ||
| icecat @ 78.6.1-guix0-preview1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| icecat @ 78.6.1-guix0-preview1 | formatting Look for formatting issues in the source | line 1145 is way too long (94 characters) | ||
| icecat @ 78.6.1-guix0-preview1 | formatting Look for formatting issues in the source | line 1147 is way too long (95 characters) | ||
| icecat @ 78.6.1-guix0-preview1 | formatting Look for formatting issues in the source | line 1160 is way too long (98 characters) | ||
| icecat @ 78.6.1-guix0-preview1 | formatting Look for formatting issues in the source | line 1289 is way too long (92 characters) | ||
| vim-full @ 8.2.2067 | formatting Look for formatting issues in the source | line 218 is way too long (94 characters) | ||
| zita-resampler @ 1.6.2 | formatting Look for formatting issues in the source | line 3665 is way too long (93 characters) | ||
| vamp @ 2.6 | formatting Look for formatting issues in the source | line 3143 is way too long (94 characters) | ||
| libsigrok @ 0.5.2 | formatting Look for formatting issues in the source | line 211 is way too long (101 characters) | ||
| libsigrok @ 0.5.2 | formatting Look for formatting issues in the source | line 212 is way too long (92 characters) | ||
| omnitux @ 1.2.1 | formatting Look for formatting issues in the source | line 581 is way too long (99 characters) | ||
| childsplay @ 3.4 | formatting Look for formatting issues in the source | line 490 is way too long (92 characters) | ||
| perftest @ 4.4-0.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 99 | ||
| mdadm-static @ 4.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| fakeroot @ 1.25.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 114, 240 | ||
| f2fs-fsck-static @ 1.14.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 91 | ||
| ecryptfs-utils @ 111 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| util-linux-with-udev @ 2.35.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| proot-static @ 5.1.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| wireless-tools @ 30.pre9 | formatting Look for formatting issues in the source | line 3619 is way too long (104 characters) | ||
| util-linux @ 2.35.1 | formatting Look for formatting issues in the source | line 1527 is way too long (91 characters) | ||
| perftest @ 4.4-0.4 | formatting Look for formatting issues in the source | line 5621 is way too long (98 characters) | ||
| linux-pam @ 1.4.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| ipset @ 7.10 | formatting Look for formatting issues in the source | line 7791 is way too long (91 characters) | ||
| crda @ 3.18 | formatting Look for formatting issues in the source | line 3726 is way too long (100 characters) | ||
| hplip-minimal @ 3.20.11 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| steghide @ 0.5.1 | patch-headers Validate patch headers | steghide-fixes.patch: patch lacks comment and upstream status | ||
| guile-zstd @ 0.1.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| guile2.2-readline @ 2.2.7 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile-readline @ 3.0.2 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile2.2-readline @ 2.2.7 | formatting Look for formatting issues in the source | line 384 is way too long (94 characters) | ||
| guile-readline @ 3.0.2 | formatting Look for formatting issues in the source | line 384 is way too long (94 characters) | ||
| guile-for-guile-emacs @ 2.1.2-1.15ca784 | formatting Look for formatting issues in the source | line 496 is way too long (96 characters) | ||
| guile-for-guile-emacs @ 2.1.2-1.15ca784 | formatting Look for formatting issues in the source | trailing white space on line 500 | ||
| libblockdev @ 2.25 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| libreoffice @ 6.4.7.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| aegis @ 4.24 | patch-headers Validate patch headers | aegis-perl-tempdir2.patch: patch lacks comment and upstream status | ||
| ocaml-zarith @ 1.9.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 146 | ||
| ocaml-topkg @ 1.0.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 51 | ||
| ocaml-qcheck @ 0.12 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 52, 156 | ||
| ocaml-down @ 0.0.3 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| ocaml-cmdliner @ 1.0.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 304 | ||
| ocaml-dose3 @ 5.0.1 | patch-headers Validate patch headers | ocaml-dose3-dont-make-printconf.patch: patch lacks comment and upstream status | ||
| ocaml4.07-sedlex @ 2.1 | formatting Look for formatting issues in the source | line 2319 is way too long (97 characters) | ||
| ocaml-dose3 @ 5.0.1 | formatting Look for formatting issues in the source | line 349 is way too long (92 characters) | ||
| icedove @ 78.6.1 | formatting Look for formatting issues in the source | line 1337 is way too long (98 characters) | ||
| icedove @ 78.6.1 | formatting Look for formatting issues in the source | line 1492 is way too long (105 characters) | ||
| icedove @ 78.6.1 | formatting Look for formatting issues in the source | line 1494 is way too long (102 characters) | ||
| sonata @ 1.7.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| iml @ 1.0.5 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 798 | ||
| python2-pygpgme @ 0.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-pygpgme @ 0.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| 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 1409 is way too long (100 characters) | ||
| giac @ 1.6.0-41 | formatting Look for formatting issues in the source | line 364 is way too long (95 characters) | ||
| gap @ 4.11.0 | formatting Look for formatting issues in the source | line 1172 is way too long (98 characters) | ||
| eigen @ 3.3.8 | formatting Look for formatting issues in the source | tabulation on line 1043, column 0 | ||
| u-boot-wandboard @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-vexpress-ca9x4 @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-sifive-fu540 @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-rockpro64-rk3399 @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-rock64-rk3328 @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-qemu-riscv64-smode @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-qemu-riscv64 @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-puma-rk3399 @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-pinebook-pro-rk3399 @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-pinebook @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-pine64-plus @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-pine64-lts @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-novena @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-nintendo-nes-classic-edition @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-mx6cuboxi @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-malta @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-firefly-rk3399 @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-cubietruck @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-cubieboard @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-bananapi-m2-ultra @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-am335x-evm @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-am335x-boneblack @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-a20-olinuxino-micro @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-a20-olinuxino-lime2 @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-a20-olinuxino-lime @ 2020.10 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 49 | ||
| u-boot-qemu-riscv64-smode @ 2020.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| grub-minimal @ 2.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| grub-hybrid @ 2.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| grub-efi @ 2.04 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| u-boot-wandboard @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-vexpress-ca9x4 @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-tools @ 2020.10 | formatting Look for formatting issues in the source | line 538 is way too long (91 characters) | ||
| u-boot-tools @ 2020.10 | formatting Look for formatting issues in the source | line 560 is way too long (97 characters) | ||
| u-boot-sifive-fu540 @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-rockpro64-rk3399 @ 2020.10 | formatting Look for formatting issues in the source | line 904 is way too long (91 characters) | ||
| u-boot-rockpro64-rk3399 @ 2020.10 | formatting Look for formatting issues in the source | line 905 is way too long (102 characters) | ||
| u-boot-qemu-riscv64 @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-pinebook @ 2020.10 | formatting Look for formatting issues in the source | line 760 is way too long (127 characters) | ||
| u-boot-pine64-plus @ 2020.10 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| u-boot-pine64-lts @ 2020.10 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| u-boot-nintendo-nes-classic-edition @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-mx6cuboxi @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-malta @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-cubietruck @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-cubieboard @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-bananapi-m2-ultra @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-am335x-evm @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-am335x-boneblack @ 2020.10 | formatting Look for formatting issues in the source | line 711 is way too long (95 characters) | ||
| u-boot-a20-olinuxino-micro @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-a20-olinuxino-lime2 @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| u-boot-a20-olinuxino-lime @ 2020.10 | formatting Look for formatting issues in the source | line 670 is way too long (93 characters) | ||
| conda @ 4.8.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| texlive-lm @ 51265 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 93 | ||
| texlive-latex-cyrillic @ 51265 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 166 | ||
| texlive-hyphen-occitan @ 51265 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| texlive-hyphen-latin @ 51265 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| texlive-fonts-latex @ 51265 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 78 | ||
| texlive-fonts-iwona @ 0.995b | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 42 | ||
| perl-libxml @ 0.08 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| libxmlplusplus @ 3.2.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| libxmlplusplus @ 2.40.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| java-xpp3 @ 1.1.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 188 | ||
| java-kxml2 @ 2.4.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| config @ 0.0.0-1.c8ddc84 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| libtool @ 2.4.6 | inputs-should-be-native Identify inputs that should be native inputs | 'm4' should probably be a native input | ||
| texlive-latex-hyperref @ 6.84a2 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| python2-libxml2 @ 2.9.10 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-beancount @ 2.2.3 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| xmlrpc-c @ 1.43.08 | formatting Look for formatting issues in the source | line 2263 is way too long (91 characters) | ||
| texlive-ruhyphen @ 51265 | formatting Look for formatting issues in the source | line 2357 is way too long (92 characters) | ||
| texlive-ruhyphen @ 51265 | formatting Look for formatting issues in the source | line 2360 is way too long (93 characters) | ||
| texlive-latex-pgf @ 51265 | formatting Look for formatting issues in the source | line 6708 is way too long (98 characters) | ||
| texlive-latex-l3packages @ 51265 | formatting Look for formatting issues in the source | line 3014 is way too long (91 characters) | ||
| texlive-latex-l3packages @ 51265 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| texlive-latex-base @ 51265 | formatting Look for formatting issues in the source | tabulation on line 2468, column 22 | ||
| texlive-hyph-utf8 @ 51265 | formatting Look for formatting issues in the source | line 2179 is way too long (108 characters) | ||
| texlive-hyph-utf8 @ 51265 | formatting Look for formatting issues in the source | line 2180 is way too long (108 characters) | ||
| texlive-hyph-utf8 @ 51265 | formatting Look for formatting issues in the source | line 2181 is way too long (95 characters) | ||
| texlive-amsfonts @ 51265 | formatting Look for formatting issues in the source | line 1143 is way too long (94 characters) | ||
| texlive-amsfonts @ 51265 | formatting Look for formatting issues in the source | line 1168 is way too long (93 characters) | ||
| texlive-amsfonts @ 51265 | formatting Look for formatting issues in the source | line 1170 is way too long (91 characters) | ||
| pyconfigure @ 0.2.3 | formatting Look for formatting issues in the source | line 603 is way too long (92 characters) | ||
| java-xom @ 127 | formatting Look for formatting issues in the source | trailing white space on line 1913 | ||
| bitcoin-unlimited @ 1.9.0.1 | formatting Look for formatting issues in the source | line 1437 is way too long (91 characters) | ||
| jucipp @ 1.6.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ecasound @ 2.9.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471 | ||
| libvirt-glib @ 3.0.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| qemu-minimal @ 5.1.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| xen @ 4.14.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| virt-manager @ 2.2.1 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| qemu @ 5.1.0 | formatting Look for formatting issues in the source | line 151 is way too long (91 characters) | ||
| qemu @ 5.1.0 | formatting Look for formatting issues in the source | line 155 is way too long (109 characters) | ||
| qemu @ 5.1.0 | formatting Look for formatting issues in the source | line 157 is way too long (103 characters) | ||
| libosinfo @ 1.7.1 | formatting Look for formatting issues in the source | line 943 is way too long (106 characters) | ||
| efitools @ 1.9.2 | formatting Look for formatting issues in the source | line 215 is way too long (113 characters) | ||
| python2-pytest-subtesthack @ 0.1.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 106 | ||
| python2-flexmock @ 0.10.4 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-pytest-subtesthack @ 0.1.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 106 | ||
| python-flexmock @ 0.10.4 | 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 | ||
| python2-testtools @ 2.3.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pbr' should probably be a native input | ||
| python2-testscenarios @ 0.5.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pbr' should probably be a native input | ||
| python2-testresources @ 2.0.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pbr' should probably be a native input | ||
| python2-pytest-xdist @ 2.1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pytest' should probably be a native input | ||
| python2-pytest-warnings @ 0.2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pytest' should probably be a native input | ||
| python2-pytest-subtesthack @ 0.1.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pytest' should probably be a native input | ||
| python2-pytest-mock @ 1.10.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-mock' should probably be a native input | ||
| python2-pytest-mock @ 1.10.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pytest' should probably be a native input | ||
| python2-pytest-cov @ 2.8.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-coverage' should probably be a native input | ||
| python2-pytest-cov @ 2.8.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pytest' should probably be a native input | ||
| python2-pytest-catchlog @ 1.2.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pytest' should probably be a native input | ||
| python2-pytest-capturelog @ 0.7 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pytest' should probably be a native input | ||
| python2-pytest-cache @ 1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pytest' should probably be a native input | ||
| python2-nosexcover @ 1.0.11 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-coverage' should probably be a native input | ||
| python2-nosexcover @ 1.0.11 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-nose' should probably be a native input | ||
| python2-nose2 @ 0.9.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pytest-cov' should probably be a native input | ||
| python2-nose-timer @ 0.7.5 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-nose' should probably be a native input | ||
| python2-fixtures @ 3.0.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-pbr' should probably be a native input | ||
| python2-coverage-test-runner @ 1.15 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-coverage' should probably be a native input | ||
| python2-cov-core @ 1.15.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-coverage' should probably be a native input | ||
| python-testtools @ 2.3.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.9.1 | 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 @ 1.3.4 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' 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-mock @ 1.10.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-forked @ 1.1.3 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest' should probably be a native input | ||
| python-pytest-cov @ 2.8.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-coverage' should probably be a native input | ||
| python-pytest-cov @ 2.8.1 | 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-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-nose2 @ 0.9.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pytest-cov' 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-fixtures @ 3.0.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-pbr' 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 | ||
| python2-unittest2 @ 1.1.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-testtools-bootstrap @ 2.3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-testtools @ 2.3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-pyfakefs @ 3.7.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python-testtools-bootstrap @ 2.3.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| python2-unittest2 @ 1.1.0 | patch-headers Validate patch headers | python-unittest2-remove-argparse.patch: patch lacks comment and upstream status | ||
| python-unittest2 @ 1.1.0 | patch-headers Validate patch headers | python-unittest2-remove-argparse.patch: patch lacks comment and upstream status | ||
| go-github.com-smartystreets-goconvey @ 1.6.3 | formatting Look for formatting issues in the source | line 678 is way too long (91 characters) | ||
| busybox @ 1.32.1 | formatting Look for formatting issues in the source | line 93 is way too long (92 characters) | ||
| emacs-gdscript-mode @ 1.4.0 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 99 | ||
| emacs-dhall-mode @ 0.1.3-1.484bcf8 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 89 | ||
| emacs-sqlite @ 1.0-0.dad42b8 | formatting Look for formatting issues in the source | tabulation on line 4480, column 0 | ||
| emacs-sqlite @ 1.0-0.dad42b8 | formatting Look for formatting issues in the source | tabulation on line 4481, column 0 | ||
| yelp-xsl @ 3.34.2 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 300 | ||
| ruby-rb-inotify @ 0.9.10 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| yelp-tools @ 3.32.2 | inputs-should-be-native Identify inputs that should be native inputs | 'itstool' should probably be a native input | ||
| system-config-printer @ 1.5.15 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| lollypop @ 1.4.6 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| libpeas @ 1.28.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| libgee @ 0.20.3 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| libdazzle @ 3.37.1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| libchamplain @ 0.12.16 | inputs-should-be-native Identify inputs that should be native inputs | 'glib:bin' should probably be a native input | ||
| gnome-tweaks @ 3.34.1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| gnome @ 3.34.2 | inputs-should-be-native Identify inputs that should be native inputs | 'desktop-file-utils' should probably be a native input | ||
| gjs @ 1.58.3 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| gexiv2 @ 0.12.1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| geoclue @ 2.5.7 | inputs-should-be-native Identify inputs that should be native inputs | 'glib:bin' should probably be a native input | ||
| eolie @ 0.9.101 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| d-feet @ 0.3.14 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| cheese @ 3.38.0 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| upower @ 0.99.11 | formatting Look for formatting issues in the source | line 5266 is way too long (110 characters) | ||
| libsoup @ 2.72.0 | formatting Look for formatting issues in the source | line 4722 is way too long (128 characters) | ||
| libsoup @ 2.72.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| librsvg @ 2.50.2 | formatting Look for formatting issues in the source | line 3397 is way too long (104 characters) | ||
| gnome-keyring @ 3.34.0 | formatting Look for formatting issues in the source | line 2456 is way too long (91 characters) | ||
| glade @ 3.36.0 | formatting Look for formatting issues in the source | line 3099 is way too long (91 characters) | ||
| gdm @ 3.34.1 | formatting Look for formatting issues in the source | line 8094 is way too long (103 characters) | ||
| xfce4-clipman-plugin @ 1.6.1 | formatting Look for formatting issues in the source | line 499 is way too long (91 characters) | ||
| tumbler @ 4.16.0 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| straw-viewer @ 0.1.2 | formatting Look for formatting issues in the source | trailing white space on line 1039 | ||
| mkvtoolnix @ 52.0.0 | formatting Look for formatting issues in the source | line 908 is way too long (96 characters) | ||
| diffoscope @ 164 | formatting Look for formatting issues in the source | line 129 is way too long (102 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-plexus-archiver @ 4.2.2 | 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-lmax-disruptor @ 3.3.7 | 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-jansi @ 1.16 | 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-plexus-sec-dispatcher @ 1.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs java-sonatype-spice-parent-pom@15 and java-sonatype-spice-parent-pom@12 collide | ||
| java-plexus-digest @ 1.2 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@3.1 collide | ||
| java-plexus-container-default @ 1.7.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-plexus-component-metadata @ 1.7.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs apache-parent-pom@13 and apache-parent-pom@21 collide | ||
| java-plexus-compiler-manager @ 2.8.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-plexus-compiler-javac @ 2.8.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-plexus-compiler-api @ 2.8.4 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide | ||
| java-plexus-archiver @ 4.2.2 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@6.1 collide | ||
| java-modello-test @ 1.9.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-modello-plugins-xpp3 @ 1.9.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-modello-plugins-xml @ 1.9.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-modello-plugins-java @ 1.9.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-modello-core @ 1.9.1 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@4.0 collide | ||
| java-eclipse-sisu-plexus @ 0.3.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 | ||
| 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-annotations @ 4.7.4 | patch-file-names Validate file names and availability of patches | java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long | ||
| java-tunnelvisionlabs-antlr4-runtime @ 4.7.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 | java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long | ||
| 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-tunnelvisionlabs-antlr4 @ 4.7.4 | patch-file-names Validate file names and availability of patches | java-tunnelvisionlabs-antlr-code-too-large.patch: file name is too long | ||
| java-powermock-reflect @ 1.7.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-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-base @ 8.202 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| java-apache-ivy @ 2.4.0 | patch-file-names Validate file names and availability of patches | java-apache-ivy-port-to-latest-bouncycastle.patch: file name is too long | ||
| java-antlr4-runtime @ 4.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 | ||
| openjdk @ 14.0 | formatting Look for formatting issues in the source | tabulation on line 2384, column 0 | ||
| openjdk @ 14.0 | formatting Look for formatting issues in the source | tabulation on line 2385, column 0 | ||
| openjdk @ 14.0 | formatting Look for formatting issues in the source | tabulation on line 2386, column 0 | ||
| openjdk @ 14.0 | formatting Look for formatting issues in the source | tabulation on line 2387, column 0 | ||
| openjdk @ 14.0 | formatting Look for formatting issues in the source | tabulation on line 2388, column 0 | ||
| openjdk @ 14.0 | formatting Look for formatting issues in the source | tabulation on line 2389, column 0 | ||
| openjdk @ 14.0 | formatting Look for formatting issues in the source | tabulation on line 2390, column 0 | ||
| openjdk @ 14.0 | formatting Look for formatting issues in the source | tabulation on line 2391, column 0 | ||
| openjdk @ 14.0 | formatting Look for formatting issues in the source | tabulation on line 2392, column 0 | ||
| openjdk @ 14.0 | formatting Look for formatting issues in the source | tabulation on line 2397, column 0 | ||
| openjdk @ 14.0 | formatting Look for formatting issues in the source | tabulation on line 2398, column 0 | ||
| openjdk @ 13.0 | formatting Look for formatting issues in the source | tabulation on line 2342, column 0 | ||
| openjdk @ 13.0 | formatting Look for formatting issues in the source | tabulation on line 2343, column 0 | ||
| openjdk @ 13.0 | formatting Look for formatting issues in the source | tabulation on line 2344, column 0 | ||
| openjdk @ 13.0 | formatting Look for formatting issues in the source | tabulation on line 2345, column 0 | ||
| openjdk @ 13.0 | formatting Look for formatting issues in the source | tabulation on line 2346, column 0 | ||
| openjdk @ 13.0 | formatting Look for formatting issues in the source | tabulation on line 2347, column 0 | ||
| openjdk @ 13.0 | formatting Look for formatting issues in the source | tabulation on line 2348, column 0 | ||
| openjdk @ 13.0 | formatting Look for formatting issues in the source | tabulation on line 2349, column 0 | ||
| openjdk @ 13.0 | formatting Look for formatting issues in the source | tabulation on line 2350, column 0 | ||
| openjdk @ 13.0 | formatting Look for formatting issues in the source | tabulation on line 2351, column 0 | ||
| openjdk @ 13.0 | formatting Look for formatting issues in the source | tabulation on line 2352, column 0 | ||
| java-testng @ 6.14.3 | formatting Look for formatting issues in the source | line 10591 is way too long (91 characters) | ||
| java-sisu-build-api @ 0.0.7 | formatting Look for formatting issues in the source | line 4851 is way too long (98 characters) | ||
| java-plexus-sec-dispatcher @ 1.4 | formatting Look for formatting issues in the source | line 4728 is way too long (107 characters) | ||
| java-plexus-compiler-javac @ 2.8.4 | formatting Look for formatting issues in the source | line 4609 is way too long (95 characters) | ||
| java-ops4j-pax-exam-core-spi @ 4.11.0 | formatting Look for formatting issues in the source | line 9552 is way too long (92 characters) | ||
| java-ops4j-pax-exam-core-spi @ 4.11.0 | formatting Look for formatting issues in the source | line 9556 is way too long (98 characters) | ||
| java-ops4j-pax-exam-core-spi @ 4.11.0 | formatting Look for formatting issues in the source | line 9560 is way too long (99 characters) | ||
| java-ops4j-pax-exam-core-spi @ 4.11.0 | formatting Look for formatting issues in the source | line 9561 is way too long (91 characters) | ||
| java-ops4j-pax-exam-core-spi @ 4.11.0 | formatting Look for formatting issues in the source | line 9564 is way too long (100 characters) | ||
| java-ops4j-base-lang @ 1.5.0 | formatting Look for formatting issues in the source | line 9248 is way too long (110 characters) | ||
| java-openjfx-base @ 8.202 | formatting Look for formatting issues in the source | line 2611 is way too long (111 characters) | ||
| java-openjfx-base @ 8.202 | formatting Look for formatting issues in the source | line 2626 is way too long (99 characters) | ||
| java-openchart2 @ 1.4.3 | formatting Look for formatting issues in the source | line 12251 is way too long (92 characters) | ||
| java-native-access @ 4.5.1 | formatting Look for formatting issues in the source | line 12431 is way too long (91 characters) | ||
| java-logback-classic @ 1.2.3 | formatting Look for formatting issues in the source | line 13010 is way too long (102 characters) | ||
| java-joda-time @ 2.9.9 | formatting Look for formatting issues in the source | line 11922 is way too long (92 characters) | ||
| java-jnacl @ 0.1.0-2.094e819 | formatting Look for formatting issues in the source | line 10668 is way too long (93 characters) | ||
| java-jnacl @ 0.1.0-2.094e819 | formatting Look for formatting issues in the source | line 10678 is way too long (92 characters) | ||
| java-jgit @ 4.2.0.201601211800-r | formatting Look for formatting issues in the source | line 13113 is way too long (93 characters) | ||
| java-hawtjni @ 1.15 | formatting Look for formatting issues in the source | line 11578 is way too long (92 characters) | ||
| java-hamcrest-core @ 1.3 | formatting Look for formatting issues in the source | line 3740 is way too long (112 characters) | ||
| java-geronimo-xbean-reflect @ 4.5 | formatting Look for formatting issues in the source | line 11360 is way too long (92 characters) | ||
| java-geronimo-xbean-bundleutils @ 4.5 | formatting Look for formatting issues in the source | line 11475 is way too long (122 characters) | ||
| java-fasterxml-jackson-dataformat-yaml @ 2.9.4 | formatting Look for formatting issues in the source | line 9878 is way too long (104 characters) | ||
| java-fasterxml-jackson-dataformat-xml @ 2.9.4 | formatting Look for formatting issues in the source | line 9993 is way too long (98 characters) | ||
| java-fasterxml-jackson-databind @ 2.9.4 | formatting Look for formatting issues in the source | line 9710 is way too long (96 characters) | ||
| java-fasterxml-jackson-core @ 2.9.4 | formatting Look for formatting issues in the source | line 9659 is way too long (93 characters) | ||
| java-eclipse-text @ 3.6.0 | formatting Look for formatting issues in the source | tabulation on line 7272, column 20 | ||
| java-eclipse-text @ 3.6.0 | formatting Look for formatting issues in the source | tabulation on line 7273, column 20 | ||
| java-eclipse-sisu-plexus @ 0.3.4 | formatting Look for formatting issues in the source | line 12827 is way too long (104 characters) | ||
| java-eclipse-sisu-plexus @ 0.3.4 | formatting Look for formatting issues in the source | line 12834 is way too long (95 characters) | ||
| java-eclipse-jdt-core @ 3.16.0 | formatting Look for formatting issues in the source | line 7332 is way too long (98 characters) | ||
| java-commons-jxpath @ 1.3 | formatting Look for formatting issues in the source | line 6047 is way too long (93 characters) | ||
| java-commons-httpclient @ 3.1 | formatting Look for formatting issues in the source | line 12293 is way too long (91 characters) | ||
| java-commons-exec @ 1.1 | formatting Look for formatting issues in the source | line 5815 is way too long (91 characters) | ||
| java-aqute-bndlib @ 3.5.0 | formatting Look for formatting issues in the source | line 9433 is way too long (91 characters) | ||
| java-apache-ivy @ 2.4.0 | formatting Look for formatting issues in the source | line 12651 is way too long (101 characters) | ||
| icedtea @ 3.7.0 | formatting Look for formatting issues in the source | line 1785 is way too long (109 characters) | ||
| icedtea @ 2.6.13 | formatting Look for formatting issues in the source | line 1275 is way too long (102 characters) | ||
| icedtea @ 2.6.13 | formatting Look for formatting issues in the source | line 1456 is way too long (100 characters) | ||
| antlr4 @ 4.8 | formatting Look for formatting issues in the source | line 8305 is way too long (96 characters) | ||
| antlr4 @ 4.8 | formatting Look for formatting issues in the source | line 8379 is way too long (100 characters) | ||
| sbcl-trivial-gray-streams @ 0.0.0-1.ebd59b1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 75 | ||
| sbcl-quri @ 0.1.0-2.b53231c | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 68 | ||
| sbcl-md5 @ 2.0.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 85 | ||
| sbcl-fare-utils @ 1.0.0.5-1.66e9c6f | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| sbcl-cl-reexport @ 0.1-1.312f366 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| sbcl-cl-cookie @ 0.9.10-1.cea55ae | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| sbcl-circular-streams @ 0.1.0-1.e770bad | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 79 | ||
| ecl-trivial-gray-streams @ 0.0.0-1.ebd59b1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 75 | ||
| ecl-quri @ 0.1.0-2.b53231c | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 68 | ||
| ecl-md5 @ 2.0.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 85 | ||
| ecl-fare-utils @ 1.0.0.5-1.66e9c6f | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ecl-cl-reexport @ 0.1-1.312f366 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ecl-cl-cookie @ 0.9.10-1.cea55ae | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| ecl-circular-streams @ 0.1.0-1.e770bad | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 79 | ||
| cl-trivial-gray-streams @ 0.0.0-1.ebd59b1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 75 | ||
| cl-reexport @ 0.1-1.312f366 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| cl-quri @ 0.1.0-2.b53231c | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 68 | ||
| cl-md5 @ 2.0.4 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 85 | ||
| cl-fare-utils @ 1.0.0.5-1.66e9c6f | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| cl-circular-streams @ 0.1.0-1.e770bad | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 79 | ||
| sbcl-cl-gobject-introspection @ 0.3-0.7b703e2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| ecl-cl-gobject-introspection @ 0.3-0.7b703e2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| cl-gobject-introspection @ 0.3-0.7b703e2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| sbcl-static-dispatch @ 0.3 | formatting Look for formatting issues in the source | line 11946 is way too long (93 characters) | ||
| sbcl-optima @ 1.0-1.373b245 | formatting Look for formatting issues in the source | line 5558 is way too long (91 characters) | ||
| sbcl-net.didierverna.asdf-flv @ 2.1 | formatting Look for formatting issues in the source | line 179 is way too long (96 characters) | ||
| sbcl-caveman @ 2.4.0-1.faa5f7e | formatting Look for formatting issues in the source | line 11596 is way too long (140 characters) | ||
| sbcl-caveman @ 2.4.0-1.faa5f7e | formatting Look for formatting issues in the source | line 11598 is way too long (97 characters) | ||
| sbcl-caveman @ 2.4.0-1.faa5f7e | formatting Look for formatting issues in the source | line 11599 is way too long (110 characters) | ||
| ecl-static-dispatch @ 0.3 | formatting Look for formatting issues in the source | line 11946 is way too long (93 characters) | ||
| ecl-optima @ 1.0-1.373b245 | formatting Look for formatting issues in the source | line 5558 is way too long (91 characters) | ||
| ecl-net.didierverna.asdf-flv @ 2.1 | formatting Look for formatting issues in the source | line 179 is way too long (96 characters) | ||
| ecl-caveman @ 2.4.0-1.faa5f7e | formatting Look for formatting issues in the source | line 11596 is way too long (140 characters) | ||
| ecl-caveman @ 2.4.0-1.faa5f7e | formatting Look for formatting issues in the source | line 11598 is way too long (97 characters) | ||
| ecl-caveman @ 2.4.0-1.faa5f7e | formatting Look for formatting issues in the source | line 11599 is way too long (110 characters) | ||
| cl-static-dispatch @ 0.3 | formatting Look for formatting issues in the source | line 11946 is way too long (93 characters) | ||
| cl-optima @ 1.0-1.373b245 | formatting Look for formatting issues in the source | line 5558 is way too long (91 characters) | ||
| cl-net.didierverna.asdf-flv @ 2.1 | formatting Look for formatting issues in the source | line 179 is way too long (96 characters) | ||
| lpsolve @ 5.5.2.5 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| opencascade-occt @ 7.3.0p3 | inputs-should-be-native Identify inputs that should be native inputs | 'doxygen' should probably be a native input | ||
| octave-cli @ 6.1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'texinfo' should probably be a native input | ||
| octave @ 6.1.0 | inputs-should-be-native Identify inputs that should be native inputs | 'texinfo' should probably be a native input | ||
| arpack-ng @ 3.3.0 | source-unstable-tarball Check for autogenerated tarballs | the source URI should not be an autogenerated tarball | ||
| scotch32 @ 6.1.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| pt-scotch32 @ 6.1.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| pt-scotch @ 6.1.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| netcdf-parallel-openmpi @ 4.7.4 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| 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 | ||
| 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 | ||
| dune-istl-openmpi @ 2.7.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| 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 | ||
| hdf5 @ 1.8.21 | patch-headers Validate patch headers | hdf5-1.8-mpi-deprecations.patch: patch lacks comment and upstream status | ||
| superlu-dist @ 6.4.0 | formatting Look for formatting issues in the source | line 3053 is way too long (92 characters) | ||
| superlu-dist @ 6.4.0 | formatting Look for formatting issues in the source | tabulation on line 3073, column 0 | ||
| superlu-dist @ 6.4.0 | formatting Look for formatting issues in the source | tabulation on line 3074, column 0 | ||
| sundials-openmpi @ 3.1.1 | formatting Look for formatting issues in the source | tabulation on line 5116, column 0 | ||
| slepc-openmpi @ 3.11.1 | formatting Look for formatting issues in the source | tabulation on line 2647, column 0 | ||
| slepc-complex-openmpi @ 3.11.1 | formatting Look for formatting issues in the source | line 2663 is way too long (92 characters) | ||
| scalapack @ 2.0.2 | formatting Look for formatting issues in the source | tabulation on line 909, column 0 | ||
| pt-scotch32 @ 6.1.0 | formatting Look for formatting issues in the source | tabulation on line 3271, column 0 | ||
| pt-scotch @ 6.1.0 | formatting Look for formatting issues in the source | tabulation on line 3249, column 0 | ||
| petsc @ 3.11.2 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| p4est @ 2.0 | formatting Look for formatting issues in the source | tabulation on line 3335, column 0 | ||
| mumps-openmpi @ 5.2.1 | formatting Look for formatting issues in the source | tabulation on line 2892, column 0 | ||
| mumps @ 5.2.1 | formatting Look for formatting issues in the source | line 2806 is way too long (94 characters) | ||
| hypre-openmpi @ 2.15.1 | formatting Look for formatting issues in the source | tabulation on line 4545, column 0 | ||
| hdf-java @ 3.3.2 | formatting Look for formatting issues in the source | line 1299 is way too long (92 characters) | ||
| clapack @ 3.2.1 | formatting Look for formatting issues in the source | line 871 is way too long (91 characters) | ||
| linux-libre-headers @ 4.9.252 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-headers @ 4.4.252 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-headers @ 4.14.216 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm-omap2plus @ 4.14.216 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm-generic @ 4.14.216 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre @ 4.9.252 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre @ 4.4.252 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre @ 4.14.216 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| linux-libre-arm-omap2plus @ 4.14.216 | formatting Look for formatting issues in the source | line 815 is way too long (117 characters) | ||
| linux-libre-arm-generic @ 4.14.216 | formatting Look for formatting issues in the source | line 815 is way too long (117 characters) | ||
| linux-libre @ 4.9.252 | formatting Look for formatting issues in the source | line 815 is way too long (117 characters) | ||
| linux-libre @ 4.4.252 | formatting Look for formatting issues in the source | line 815 is way too long (117 characters) | ||
| linux-libre @ 4.14.216 | formatting Look for formatting issues in the source | line 815 is way too long (117 characters) | ||
| guile3.0-ncurses-with-gpm @ 3.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile2.2-sjson @ 0.2.1 | 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-1.03e9cac | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile-dbd-sqlite3 @ 2.1.6 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| guile2.2-gi @ 0.3.1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| guile-gi @ 0.3.1 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| g-golf @ 0.1.0-839.ef83010 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' should probably be a native input | ||
| guile2.2-fibers @ 1.0.0 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| guile-dbi @ 2.1.6 | formatting Look for formatting issues in the source | line 1437 is way too long (94 characters) | ||
| xpra @ 4.0.6 | formatting Look for formatting issues in the source | tabulation on line 6332, column 0 | ||
| samblaster @ 0.1.24 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 263 | ||
| r-seqlogo @ 1.56.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-rtracklayer @ 1.50.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| r-bseqsc @ 1.0-1.fef3f3e | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 395 | ||
| r-biomart @ 2.46.0 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-twobitreader @ 3.1.6 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-pybedtools @ 0.8.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-plastid @ 0.4.8 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python2-bx-python @ 0.8.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-twobitreader @ 3.1.6 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-pyfit-sne @ 1.0.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-pybedtools @ 0.8.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-plastid @ 0.4.8 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-dnaio @ 0.3 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| python-bx-python @ 0.8.2 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| variant-tools @ 3.1.2 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| rseqc @ 3.0.1 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| python2-pbcore @ 1.2.10 | inputs-should-be-native Identify inputs that should be native inputs | 'python2-cython' should probably be a native input | ||
| python-velocyto @ 0.17.17 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| python-bbknn @ 1.3.6 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| newick-utils @ 1.6-1.da121155 | inputs-should-be-native Identify inputs that should be native inputs | 'flex' should probably be a native input | ||
| newick-utils @ 1.6-1.da121155 | inputs-should-be-native Identify inputs that should be native inputs | 'bison' should probably be a native input | ||
| multiqc @ 1.5 | inputs-should-be-native Identify inputs that should be native inputs | 'python-nose' should probably be a native input | ||
| clipper @ 2.0 | inputs-should-be-native Identify inputs that should be native inputs | 'python-cython' should probably be a native input | ||
| python-pygenometracks @ 3.3 | profile-collisions Report collisions that would occur due to propagated inputs | propagated inputs python-distlib@0.3.1 and python-distlib@0.3.0 collide | ||
| vcflib @ 1.0.2 | formatting Look for formatting issues in the source | line 15103 is way too long (92 characters) | ||
| salmon @ 0.13.1 | formatting Look for formatting issues in the source | line 11653 is way too long (99 characters) | ||
| phast @ 1.5 | formatting Look for formatting issues in the source | tabulation on line 15358, column 30 | ||
| ncbi-vdb @ 2.10.6 | formatting Look for formatting issues in the source | tabulation on line 6082, column 26 | ||
| java-picard @ 2.3.0 | formatting Look for formatting issues in the source | line 4019 is way too long (104 characters) | ||
| java-picard @ 2.10.3 | formatting Look for formatting issues in the source | line 4078 is way too long (104 characters) | ||
| java-picard @ 2.10.3 | formatting Look for formatting issues in the source | line 4108 is way too long (91 characters) | ||
| java-picard @ 1.113 | formatting Look for formatting issues in the source | line 4165 is way too long (96 characters) | ||
| java-picard @ 1.113 | formatting Look for formatting issues in the source | line 4166 is way too long (117 characters) | ||
| fastahack @ 1.0.0 | formatting Look for formatting issues in the source | line 14990 is way too long (91 characters) | ||
| dropseq-tools @ 1.13 | formatting Look for formatting issues in the source | tabulation on line 12220, column 0 | ||
| dropseq-tools @ 1.13 | formatting Look for formatting issues in the source | tabulation on line 12232, column 0 | ||
| discrover @ 1.6.0 | formatting Look for formatting issues in the source | line 2922 is way too long (91 characters) | ||
| blasr-libcpp @ 5.3.3 | formatting Look for formatting issues in the source | line 607 is way too long (95 characters) | ||
| xfce4-volumed-pulse @ 0.2.3 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infractions at 65, 112 | ||
| thunar @ 4.16.2 | inputs-should-be-native Identify inputs that should be native inputs | 'gobject-introspection' 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 | ||
| kconfigwidgets @ 5.70.0 | inputs-should-be-native Identify inputs that should be native inputs | 'qttools' should probably be a native input | ||
| plasma-framework @ 5.70.1 | patch-file-names Validate file names and availability of patches | plasma-framework-fix-KF5PlasmaMacros.cmake.patch: file name is too long | ||
| emacs-erlang @ 23.2.1 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| plasma-framework @ 5.70.1 | formatting Look for formatting issues in the source | line 3396 is way too long (93 characters) | ||
| kpackage @ 5.70.0 | formatting Look for formatting issues in the source | line 1928 is way too long (106 characters) | ||
| kio @ 5.70.1 | formatting Look for formatting issues in the source | line 2767 is way too long (113 characters) | ||
| kimageformats @ 5.70.0 | formatting Look for formatting issues in the source | line 1790 is way too long (103 characters) | ||
| kcmutils @ 5.70.0 | formatting Look for formatting issues in the source | line 2239 is way too long (113 characters) | ||
| elixir @ 1.11.3 | formatting Look for formatting issues in the source | line 76 is way too long (97 characters) | ||
| elixir @ 1.11.3 | formatting Look for formatting issues in the source | line 77 is way too long (99 characters) | ||
| emacs-swiper @ 0.13.1 | description Validate package descriptions | use @code or similar ornament instead of quotes | ||
| emacs-pyvenv @ 1.21 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| emacs-flx @ 0.6.1 | description Validate package descriptions | sentences in description should be followed by two spaces; possible infraction at 220 | ||
| emacs-el-x @ 0.3.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| emacs-cnfonts @ 0.9.1 | description Validate package descriptions | description should start with an upper-case letter or digit | ||
| emacs-undohist-el @ 0-1.d2239a5 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-exwm-no-x-toolkit @ 0.24 | patch-file-names Validate file names and availability of patches | file names of patches should start with the package name | ||
| emacs-org @ 9.4.4 | formatting Look for formatting issues in the source | parentheses feel lonely, move to the previous or next line | ||
| emacs-mit-scheme-doc @ 20140203 | formatting Look for formatting issues in the source | line 5858 is way too long (94 characters) | ||
| emacs-exwm @ 0.24 | formatting Look for formatting issues in the source | line 12330 is way too long (96 characters) | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12674, column 0 | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12675, column 0 | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12678, column 0 | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12679, column 0 | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12691, column 0 | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12692, column 0 | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12693, column 0 | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12694, column 0 | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12695, column 0 | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12696, column 0 | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12697, column 0 | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12698, column 0 | ||
| emacs-ert-runner @ 0.8.0 | formatting Look for formatting issues in the source | tabulation on line 12699, column 0 |