Language
Lint warnings where the package name matches the query.
Lint warnings for specific lint checkers.
Lint warnings where the message matches the query.
Fields to return in the response.

Lint warnings

PackageLinterMessageLocation
python-libfreenect @ 0.6.2description

Validate package descriptions

description should start with an upper-case letter or digit
perl6-grammar-debugger @ 1.0.1-1.0375008description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 203
perl-test-object @ 0.08description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-test-file-contents @ 0.23description

Validate package descriptions

description should start with an upper-case letter or digit
myrddin @ 0.3.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
mate-applets @ 1.24.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 917
libfreenect-opencv @ 0.6.2description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
linuxdcpp @ 1.1.0patch-headers

Validate patch headers

linuxdcpp-openssl-1.1.patch: patch lacks comment and upstream status
presentty @ 0.2.1formatting

Look for formatting issues in the source

line 45 is way too long (117 characters)
perl-test2-plugin-nowarnings @ 0.06formatting

Look for formatting issues in the source

line 104 is way too long (92 characters)
musl-cross @ 0.1-3.a8a6649formatting

Look for formatting issues in the source

line 152 is way too long (92 characters)
mate-panel @ 1.24.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 486 is way too long (91 characters)
java-jbzip2 @ 0.9.1formatting

Look for formatting issues in the source

line 277 is way too long (92 characters)
irods-client-icommands @ 4.2.8formatting

Look for formatting issues in the source

line 235 is way too long (91 characters)
irods @ 4.2.8formatting

Look for formatting issues in the source

line 104 is way too long (93 characters)
irods @ 4.2.8formatting

Look for formatting issues in the source

line 132 is way too long (91 characters)
hyperledger-iroha @ 1.1.1formatting

Look for formatting issues in the source

line 166 is way too long (105 characters)
cryptsetup-static @ 2.3.7formatting

Look for formatting issues in the source

line 110 is way too long (93 characters)
atril @ 1.24.0formatting

Look for formatting issues in the source

line 714 is way too long (92 characters)
genimage @ 15-1.ec44ae0patch-headers

Validate patch headers

genimage-mke2fs-test.patch: patch lacks comment and upstream status
perl-libxml @ 0.08description

Validate package descriptions

description should start with an upper-case letter or digit
tmux-themepack @ 1.1.0formatting

Look for formatting issues in the source

line 94 is way too long (95 characters)
js-mathjax @ 3.2.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
js-mathjax @ 3.2.0formatting

Look for formatting issues in the source

line 234 is way too long (92 characters)
js-mathjax @ 3.2.0formatting

Look for formatting issues in the source

line 275 is way too long (92 characters)
js-mathjax @ 2.7.2formatting

Look for formatting issues in the source

line 156 is way too long (91 characters)
guile-zstd @ 0.1.1description

Validate package descriptions

use @code or similar ornament instead of quotes
sane-airscan @ 0.99.27description

Validate package descriptions

use @code or similar ornament instead of quotes
guile-wm @ 1.0-1.f3c7b3bformatting

Look for formatting issues in the source

line 130 is way too long (92 characters)
gourmet @ 0.17.4-0.8af29c8patch-headers

Validate patch headers

gourmet-sqlalchemy-compat.patch: patch lacks comment and upstream status
rcm @ 1.3.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 183
papi @ 6.0.0.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
js-mathjax @ 3.1.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
js-mathjax @ 3.1.2formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 716 is way too long (99 characters)
clang-runtime @ 3.9.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
rocm-bandwidth-test @ 5.1.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 122
vnlog @ 1.32wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
rednotebook @ 2.22wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
presentty @ 0.2.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
piet-toolchain @ 0.0.0-0.f002ff6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
npiet @ 1.3fwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
kawa @ 3.1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
guile-wm @ 1.0-1.f3c7b3bwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gramps @ 5.1.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
byobu @ 5.133wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
arcanist @ 0.0.0-2.ceb082ewrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
arcan-sdl @ 0.5.5.2-1.b4dd1fbwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
arcan @ 0.5.5.2-1.b4dd1fbwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cloud-utils @ 0.33wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
nsis-x86_64 @ 3.08name

Validate package names

name should use hyphens instead of underscores
nsis-x86_64 @ 3.08patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
nsis-i686 @ 3.08patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
nsis-x86_64 @ 3.08patch-headers

Validate patch headers

nsis-env-passthru.patch: patch lacks comment and upstream status
nsis-i686 @ 3.08patch-headers

Validate patch headers

nsis-env-passthru.patch: patch lacks comment and upstream status
nsis-x86_64 @ 3.08formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 114 is way too long (97 characters)
nsis-x86_64 @ 3.08formatting

Look for formatting issues in the source

line 118 is way too long (122 characters)
nsis-x86_64 @ 3.08formatting

Look for formatting issues in the source

line 127 is way too long (92 characters)
nsis-x86_64 @ 3.08formatting

Look for formatting issues in the source

line 128 is way too long (114 characters)
nsis-i686 @ 3.08formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 114 is way too long (97 characters)
nsis-i686 @ 3.08formatting

Look for formatting issues in the source

line 118 is way too long (122 characters)
nsis-i686 @ 3.08formatting

Look for formatting issues in the source

line 127 is way too long (92 characters)
nsis-i686 @ 3.08formatting

Look for formatting issues in the source

line 128 is way too long (114 characters)
mkbootimg @ 7.1.2_r36patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

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

Validate patch headers

libziparchive-add-includes.patch: patch lacks comment and upstream status
libetc1 @ 7.1.2_r36formatting

Look for formatting issues in the source

tabulation on line 808, column 20
fastboot @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 463 is way too long (95 characters)
android-platform-frameworks-native-headers @ 7.1.2_r36formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
android-libutils @ 7.1.2_r36formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

tabulation on line 308, column 20
adb @ 7.1.2_r36formatting

Look for formatting issues in the source

line 416 is way too long (97 characters)
mingw-w64-x86_64-winpthreads @ 10.0.0name

Validate package names

name should use hyphens instead of underscores
mingw-w64-x86_64 @ 10.0.0name

Validate package names

name should use hyphens instead of underscores
mingw-w64-x86_64-winpthreads @ 10.0.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
mingw-w64-x86_64 @ 10.0.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
python-git-review @ 2.1.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python-openstacksdk @ 0.100.0formatting

Look for formatting issues in the source

tabulation on line 1040, column 0
lxde-common @ 0.99.2formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
syncthing-gtk @ 0.9.4.4-1.c46fbd8wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gpsd @ 3.23.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python2-minimal @ 2.7.18patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
windowmaker @ 0.95.9wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gcompris @ 17.05formatting

Look for formatting issues in the source

line 145 is way too long (96 characters)
t1lib @ 5.1.2patch-headers

Validate patch headers

t1lib-CVE-2010-2642.patch: patch lacks comment and upstream status
connman @ 1.41description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 146
econnman @ 1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gpsd @ 3.23.1mirror-url

Suggest 'mirror://' URLs

URL should be 'mirror://savannah/gpsd/gpsd-3.23.1.tar.xz'
rust-minimal-lexical @ 0.2.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 92
elm-sans-reactor @ 0.19.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libgweather4-with-libsoup2 @ 4.1.1description

Validate package descriptions

description should start with an upper-case letter or digit
libgweather4 @ 4.1.1description

Validate package descriptions

description should start with an upper-case letter or digit
cawbird @ 1.4.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cawbird @ 1.4.2formatting

Look for formatting issues in the source

line 94 is way too long (104 characters)
sdl-mixer @ 1.2.12formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 237 is way too long (91 characters)
sdl-gfx @ 2.0.26formatting

Look for formatting issues in the source

line 227 is way too long (106 characters)
libtomcrypt @ 1.18.2formatting

Look for formatting issues in the source

line 383 is way too long (100 characters)
gmp @ 6.2.1formatting

Look for formatting issues in the source

line 88 is way too long (96 characters)
remind @ 3.3.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
khelpcenter @ 22.04.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
sddm @ 0.19.0formatting

Look for formatting issues in the source

line 84 is way too long (98 characters)
ronn-ng @ 0.9.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
roffit @ 0.12-1.b59e6c855wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
etc1tool @ 7.1.2_r36formatting

Look for formatting issues in the source

tabulation on line 855, column 20
etc1tool @ 7.1.2_r36formatting

Look for formatting issues in the source

line 883 is way too long (98 characters)
parlatype @ 3.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
libratbag @ 0.16wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
liferea @ 1.13.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
clojure-algo-generic @ 0.1.3formatting

Look for formatting issues in the source

line 285 is way too long (93 characters)
clojure @ 1.11.1formatting

Look for formatting issues in the source

line 174 is way too long (99 characters)
axoloti-runtime @ 1.0.12-2formatting

Look for formatting issues in the source

line 195 is way too long (96 characters)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 554 is way too long (93 characters)
axoloti-patcher-next @ 2.0.0formatting

Look for formatting issues in the source

line 567 is way too long (103 characters)
ublock-origin-chromium @ 1.45.2description

Validate package descriptions

description should start with an upper-case letter or digit
clojure-tools-deps-alpha @ 0.14.1212profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-oss-parent-pom@7 and java-sonatype-oss-parent-pom@9 collide
clojure-tools-deps-alpha @ 0.14.1212formatting

Look for formatting issues in the source

line 594 is way too long (94 characters)
clojure-data-xml @ 0.2.0-alpha6formatting

Look for formatting issues in the source

line 423 is way too long (93 characters)
clojure-data-xml @ 0.2.0-alpha6formatting

Look for formatting issues in the source

line 424 is way too long (91 characters)
giara @ 1.0.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
moreutils @ 0.67wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
tuxmath @ 2.0.3description

Validate package descriptions

description should start with an upper-case letter or digit
kalendar @ 22.08.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
anki @ 2.1.16wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
akregator @ 22.08.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
wacomtablet @ 3.2.0formatting

Look for formatting issues in the source

line 754 is way too long (144 characters)
libksieve @ 22.08.1formatting

Look for formatting issues in the source

tabulation on line 2166, column 0
kitinerary @ 22.08.1formatting

Look for formatting issues in the source

line 1074 is way too long (219 characters)
kincidenceeditor @ 22.08.1formatting

Look for formatting issues in the source

tabulation on line 473, column 0
kincidenceeditor @ 22.08.1formatting

Look for formatting issues in the source

line 473 is way too long (102 characters)
bluez-qt @ 5.98.0formatting

Look for formatting issues in the source

tabulation on line 355, column 0
akonadi-mime @ 22.08.1formatting

Look for formatting issues in the source

line 273 is way too long (92 characters)
akonadi @ 22.08.1formatting

Look for formatting issues in the source

line 109 is way too long (849 characters)
zn-poly @ 0.9.2description

Validate package descriptions

description should start with an upper-case letter or digit
ratpoints @ 2.1.3patch-headers

Validate patch headers

ratpoints-sturm_and_rp_private.patch: patch lacks comment and upstream status
python-pybcj @ 1.0.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 202
wordnet @ 3.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
slurm @ 22.05.1formatting

Look for formatting issues in the source

line 274 is way too long (91 characters)
artanis @ 0.5.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
mysql @ 5.7.33wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ephemeralpg @ 3.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
espeak-ng @ 1.51description

Validate package descriptions

description should start with an upper-case letter or digit
flite @ 2.2formatting

Look for formatting issues in the source

line 95 is way too long (419 characters)
tbb @ 2021.6.0patch-headers

Validate patch headers

tbb-other-arches.patch: patch lacks comment and upstream status
man-pages-posix @ 2013-aformatting

Look for formatting issues in the source

line 346 is way too long (99 characters)
ceph @ 17.2.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
libtirpc-hurd @ 1.3.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
pencil2d @ 0.6.6wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
papagayo @ 2.0b1-1.e143684b3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
openfoam @ 4.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 160 is way too long (91 characters)
java-xpp3 @ 1.1.4description

Validate package descriptions

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

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
java-xom @ 127formatting

Look for formatting issues in the source

trailing white space on line 235
java-xmlpull-api-v1 @ 1.1.3.4bformatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
minetest-basic-trains @ 1.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
rapid-photo-downloader @ 0.9.18wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
raspi-arm64-chainloader @ 0.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 155 is way too long (102 characters)
nettle @ 2.7.1formatting

Look for formatting issues in the source

line 67 is way too long (92 characters)
dirvish @ 1.2.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
tasksh @ 1.2.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 93
sawfish @ 1.13.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
blanket @ 0.5.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
timewarrior @ 1.4.3formatting

Look for formatting issues in the source

line 194 is way too long (94 characters)
wine64 @ 8.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
julia-compilersupportlibraries-jll @ 0.4.0+1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 134
julia-compilersupportlibraries-jll @ 0.4.0+1formatting

Look for formatting issues in the source

line 201 is way too long (91 characters)
julia @ 1.8.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
chez-scheme-bootstrap-bootfiles @ 9.5.8description

Validate package descriptions

use @code or similar ornament instead of quotes
chez-scheme-bootstrap-bootfiles @ 9.5.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
verilator @ 4.204description

Validate package descriptions

use @code or similar ornament instead of quotes
yosys @ 0.26wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cloudflare-cli @ 0.0.0-1.2d986d3formatting

Look for formatting issues in the source

line 126 is way too long (92 characters)
translate-shell @ 0.9.7.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
tor @ 0.4.7.13description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 574
catfish @ 4.16.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
julia-openspecfun-jll @ 0.5.3+4description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 129
julia-xorg-xcb-util-renderutil-jll @ 0.3.9+1formatting

Look for formatting issues in the source

line 2546 is way too long (93 characters)
julia-libuuid-jll @ 2.36.0+0formatting

Look for formatting issues in the source

line 1299 is way too long (92 characters)
pw @ 2description

Validate package descriptions

use @code or similar ornament instead of quotes
java-jblas @ 1.2.4description

Validate package descriptions

description should start with an upper-case letter or digit
llvm @ 15.0.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
llvm @ 14.0.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
lldb @ 15.0.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
lld @ 15.0.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
lld @ 14.0.6patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libcxx @ 15.0.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
coq-stdlib @ 8.16.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
coq-ide-server @ 8.16.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
coq-ide @ 8.16.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
coq-core @ 8.16.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
libkscreen @ 5.25.5formatting

Look for formatting issues in the source

line 940 is way too long (158 characters)
kpackage @ 5.98.0formatting

Look for formatting issues in the source

line 1936 is way too long (106 characters)
kimageformats @ 5.98.0formatting

Look for formatting issues in the source

line 1809 is way too long (103 characters)
kfilemetadata @ 5.98.0formatting

Look for formatting issues in the source

tabulation on line 1758, column 0
kcontacts @ 5.98.0formatting

Look for formatting issues in the source

line 1647 is way too long (95 characters)
kcmutils @ 5.98.0formatting

Look for formatting issues in the source

line 2212 is way too long (113 characters)
kcmutils @ 5.98.0formatting

Look for formatting issues in the source

line 2213 is way too long (92 characters)
discover @ 5.25.5formatting

Look for formatting issues in the source

line 268 is way too long (94 characters)
discover @ 5.25.5formatting

Look for formatting issues in the source

line 269 is way too long (100 characters)
zuo @ 1.6-racket8.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
racket @ 8.8formatting

Look for formatting issues in the source

line 713 is way too long (91 characters)
racket @ 8.8formatting

Look for formatting issues in the source

line 833 is way too long (91 characters)
virt-manager @ 4.1.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ganeti @ 3.0.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
criu @ 3.17.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
virt-manager @ 4.1.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
ibutils @ 1.5.7-0.2.gbd7e502formatting

Look for formatting issues in the source

line 175 is way too long (158 characters)
itcl @ 4.2.2description

Validate package descriptions

description should start with an upper-case letter or digit
fstrcmp @ 0.7.D001description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 236
libmhash @ 0.9.9.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
sdl-pango @ 0.1.2patch-headers

Validate patch headers

sdl-pango-header-guard.patch: patch lacks comment and upstream status
mcrypt @ 2.6.8patch-headers

Validate patch headers

mcrypt-CVE-2012-4426.patch: patch lacks comment and upstream status
libmhash @ 0.9.9.9patch-headers

Validate patch headers

libmhash-hmac-fix-uaf.patch: patch lacks comment and upstream status
apr @ 1.7.0patch-headers

Validate patch headers

apr-skip-getservbyname-test.patch: patch lacks comment and upstream status
netpbm @ 10.78.3formatting

Look for formatting issues in the source

line 86 is way too long (127 characters)
libdaemon @ 0.14formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
icedtea @ 2.6.13formatting

Look for formatting issues in the source

line 224 is way too long (102 characters)
icedtea @ 2.6.13formatting

Look for formatting issues in the source

line 233 is way too long (93 characters)
ghc-hxt-unicode @ 9.0.2.4description

Validate package descriptions

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

Validate package descriptions

description should start with an upper-case letter or digit
elm-terezka-intervals @ 2.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
raincat @ 1.2.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
shellcheck @ 0.9.0formatting

Look for formatting issues in the source

line 842 is way too long (92 characters)
idris @ 1.3.4formatting

Look for formatting issues in the source

line 102 is way too long (134 characters)
ghc-hxt-unicode @ 9.0.2.4formatting

Look for formatting issues in the source

line 1394 is way too long (91 characters)
elm-sans-reactor @ 0.19.1formatting

Look for formatting issues in the source

line 74 is way too long (114 characters)
darcs @ 2.16.5formatting

Look for formatting issues in the source

line 201 is way too long (120 characters)
darcs @ 2.16.5formatting

Look for formatting issues in the source

line 205 is way too long (92 characters)
pbuilder @ 0.231formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 307 is way too long (95 characters)
cloc @ 1.96.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gimp-resynthesizer @ 2.0.3formatting

Look for formatting issues in the source

line 521 is way too long (107 characters)
grub-hybrid @ 2.06patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
grub-efi32 @ 2.06patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
julia-chainrulestestutils @ 1.5.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 260
sugar @ 0.120formatting

Look for formatting issues in the source

line 108 is way too long (101 characters)
xst @ 0.8.4.1formatting

Look for formatting issues in the source

line 427 is way too long (98 characters)
kbd @ 2.5.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
julia-reversediff @ 1.14.4formatting

Look for formatting issues in the source

line 5384 is way too long (103 characters)
julia-documenter @ 0.27.7formatting

Look for formatting issues in the source

line 1727 is way too long (105 characters)
julia-cstparser @ 3.3.4formatting

Look for formatting issues in the source

line 1343 is way too long (91 characters)
blueman @ 2.3.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs @ 28.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
sugar @ 0.120synopsis

Validate package synopses

synopsis should not start with the package name
smalltalk @ 3.2.91synopsis

Validate package synopses

synopsis should not start with the package name
scroll @ 1.20180421synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
scroll @ 1.20180421synopsis

Validate package synopses

synopsis should not start with the package name
python-inflate64 @ 0.3.1synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
pure @ 0.68synopsis

Validate package synopses

synopsis should not start with the package name
musl-cross @ 0.1-3.a8a6649synopsis

Validate package synopses

synopsis should not start with the package name
motif @ 2.3.8-0.59858b0synopsis

Validate package synopses

synopsis should not start with the package name
most @ 5.1.0synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
julia-xorg-xtrans-jll @ 1.4.0+2synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
julia-xorg-xkbcomp-jll @ 1.4.2+3synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
julia-xorg-libxrender-jll @ 0.9.10+3synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
julia-x265-jll @ 3.0.0+1synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
julia-x264-jll @ 2020.7.14+0synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
julia-libgpg-error-jll @ 1.42.0+0synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
julia-libgcrypt-jll @ 1.8.7+0synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
julia-ffmpeg-jll @ 4.3.1+2synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
julia-commonsubexpressions @ 0.3.0synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
itinerary @ 22.08.1synopsis

Validate package synopses

synopsis should not start with the package name
heads-dev-cpio @ 0.1synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
elixir @ 1.14.0synopsis

Validate package synopses

synopsis should not start with the package name
bind @ 9.16.38synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
android-udev-rules @ 20210501synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
fennel @ 1.3.0tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
python-pytools @ 2021.2.7description

Validate package descriptions

use @code or similar ornament instead of quotes
lua-tablepool @ 0.01formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 974 is way too long (95 characters)
emilua @ 0.3.2formatting

Look for formatting issues in the source

line 1171 is way too long (102 characters)
python-fpylll @ 0.5.7description

Validate package descriptions

description should start with an upper-case letter or digit
eigen-benchmarks @ 3.4.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-pyts @ 0.12.0formatting

Look for formatting issues in the source

line 560 is way too long (91 characters)
chez-scheme-for-racket-bootstrap-bootfiles @ 9.9.9-pre-release.14description

Validate package descriptions

use @code or similar ornament instead of quotes
texinfo @ 7.0.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
nomad @ 0.2.0-alpha-199-g3e7a475wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
shell-functools @ 0.3.0description

Validate package descriptions

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

Validate package descriptions

use @code or similar ornament instead of quotes
ploticus @ 2.42wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
notifymuch @ 0.1-1.9d4aaf5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
licensecheck @ 3.0.37wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
jfs_fsck-static @ 1.1.15name

Validate package names

name should use hyphens instead of underscores
xfstests @ 1.1.0-1.bae1d15wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
bcachefs-tools @ 0.1-16.46a6b92wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
mergerfs @ 2.33.5formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libnfs @ 4.0.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
glusterfs @ 7.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
tryton @ 6.2.7synopsis

Validate package synopses

synopsis should not start with the package name
tryton @ 6.2.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
trytond-account-statement-aeb43 @ 6.2.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-pycountry@22.3.5 and python-pycountry@20.7.3 collide
robin-map @ 0.6.3description

Validate package descriptions

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

Look for formatting issues in the source

line 310 is way too long (145 characters)
xfce4-volumed-pulse @ 0.2.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 65, 112
execline @ 2.9.3.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
unicorn @ 1.0.2-rc4synopsis

Validate package synopses

synopsis should not start with the package name
pcsxr @ 1.9.95wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gnunet-scheme @ 0.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 77
xorriso @ 1.5.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
perl-image-exiftool @ 12.50wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ctl @ 1.5.2source-unstable-tarball

Check for autogenerated tarballs

the source URI should not be an autogenerated tarball
libjami @ 20230323.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libextractor @ 1.11formatting

Look for formatting issues in the source

line 138 is way too long (140 characters)
jami @ 20230323.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
guile-sdl @ 0.6.1formatting

Look for formatting issues in the source

line 637 is way too long (111 characters)
remmina @ 1.4.29wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
tigervnc-server @ 1.12.0-0.b484c22patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
hledger @ 1.27.1formatting

Look for formatting issues in the source

line 286 is way too long (96 characters)
qemu-minimal @ 7.2.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
plasma-nano @ 5.24.3mirror-url

Suggest 'mirror://' URLs

URL should be 'mirror://kde/stable/plasma/5.24.3/plasma-nano-5.24.3.tar.xz'
plasma-mobile @ 5.24.3mirror-url

Suggest 'mirror://' URLs

URL should be 'mirror://kde/stable/plasma/5.24.3/plasma-mobile-5.24.3.tar.xz'
plasma-workspace @ 5.25.5formatting

Look for formatting issues in the source

line 2398 is way too long (140 characters)
plasma-vault @ 5.25.5formatting

Look for formatting issues in the source

tabulation on line 2184, column 0
plasma-integration @ 5.25.5formatting

Look for formatting issues in the source

line 1818 is way too long (238 characters)
kwin @ 5.25.5formatting

Look for formatting issues in the source

line 1273 is way too long (91 characters)
kwin @ 5.25.5formatting

Look for formatting issues in the source

line 1274 is way too long (91 characters)
kwin @ 5.25.5formatting

Look for formatting issues in the source

line 1275 is way too long (97 characters)
kwin @ 5.25.5formatting

Look for formatting issues in the source

line 1276 is way too long (109 characters)
luakit @ 2.3.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
kristall @ 0.3-1.204b08awrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
perl-search-xapian @ 1.2.25.5description

Validate package descriptions

use @code or similar ornament instead of quotes
libxapp @ 2.4.3source-file-name

Validate file names of sources

the source file name should contain the package name
mcomix @ 2.0.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
hydrus-network @ 495formatting

Look for formatting issues in the source

line 1133 is way too long (92 characters)
gnucash @ 5.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1144 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1145 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1146 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1147 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1148 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1149 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1150 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1151 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1156 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1157 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1166 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1167 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1169 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1170 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1171 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1172 is way too long (96 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1173 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1174 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1176 is way too long (97 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1177 is way too long (97 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1179 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1181 is way too long (92 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1182 is way too long (92 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1183 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1184 is way too long (97 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1194 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1195 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1196 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1197 is way too long (94 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1198 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1199 is way too long (93 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1200 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1201 is way too long (95 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1206 is way too long (91 characters)
go-github-com-operatorfoundation-shapeshifter-transports @ 3.0.12formatting

Look for formatting issues in the source

line 1207 is way too long (98 characters)
go @ 1.19.7formatting

Look for formatting issues in the source

line 921 is way too long (91 characters)
openmpi-thread-multiple @ 4.1.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
openmpi-c++ @ 4.1.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
java-openmpi @ 4.1.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
openmpi @ 4.1.5formatting

Look for formatting issues in the source

line 268 is way too long (95 characters)
openmpi @ 4.1.5formatting

Look for formatting issues in the source

line 270 is way too long (97 characters)
swish-e @ 2.4.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
recoll @ 1.34.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
giac @ 1.9.0-45formatting

Look for formatting issues in the source

line 339 is way too long (95 characters)
perl-crypt-unixcrypt_xs @ 0.11name

Validate package names

name should use hyphens instead of underscores
cups @ 2.4.2tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
xtensor-benchmark @ 0.24.0description

Validate package descriptions

description should start with an upper-case letter or digit
qtwebglplugin @ 5.15.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 41
qtdatavis3d @ 5.15.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 107, 250
qtcharts @ 5.15.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 244
perl-specio @ 0.38description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 185, 314
perl-file-which @ 1.23description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-file-readbackwards @ 1.06description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 47
perl-digest-sha @ 6.02description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 82
perl-devel-globaldestruction @ 0.14description

Validate package descriptions

use @code or similar ornament instead of quotes
perl-class-load @ 0.25description

Validate package descriptions

use @code or similar ornament instead of quotes
mdadm-static @ 4.2description

Validate package descriptions

description should start with an upper-case letter or digit
libdqlite @ 1.9.0description

Validate package descriptions

description should start with an upper-case letter or digit
ipxe-qemu @ 1.21.1-1.9e1f7a3description

Validate package descriptions

description should start with an upper-case letter or digit
iml @ 1.0.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 798
config @ 0.0.0-1.c8ddc84description

Validate package descriptions

use @code or similar ornament instead of quotes
qxlsx-qt5 @ 1.4.5synopsis

Validate package synopses

no period allowed at the end of the synopsis
python-grpc-stubs @ 1.24.11synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
pyconfigure @ 0.2.3synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
perl-io-all @ 0.87synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
libical @ 3.0.16synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
hello @ 2.12.1synopsis

Validate package synopses

synopsis should not start with the package name
file @ 5.44synopsis

Validate package synopses

synopsis should not start with the package name
date @ 2.4.1-9a0ee254synopsis

Validate package synopses

synopsis should not start with the package name
cppawk-egawk @ 20220703synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
spice-gtk @ 0.42wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
singularity @ 2.6.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
signing-party @ 2.11wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
pinentry-rofi @ 2.0.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
perl-sgmls @ 1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
perl-eval-withlexicals @ 1.003006wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
parcimonie @ 0.12.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
orange @ 3.32.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
ocrodjvu @ 0.12-0.0dd3364wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gpa @ 0.10.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
foo2zjs @ 20200610.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
dvdstyler @ 3.0.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
didjvu @ 0.9-0.c792d61wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
dblatex @ 0.3.12wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cups-filters @ 1.28.15wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cdemu-client @ 3.2.5wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
calibre @ 5.44.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
asunder @ 2.9.7wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
abcde @ 2.9.3wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
389-ds-base @ 2.2.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python-libxml2 @ 2.9.14mirror-url

Suggest 'mirror://' URLs

URL should be 'mirror://gnome/sources/libxml2/2.9/libxml2-2.9.14.tar.xz'
libxslt @ 1.1.37mirror-url

Suggest 'mirror://' URLs

URL should be 'mirror://gnome/sources/libxslt/1.1/libxslt-1.1.37.tar.xz'
libxml2-xpath0 @ 2.9.14mirror-url

Suggest 'mirror://' URLs

URL should be 'mirror://gnome/sources/libxml2/2.9/libxml2-2.9.14.tar.xz'
libxml2 @ 2.9.14mirror-url

Suggest 'mirror://' URLs

URL should be 'mirror://gnome/sources/libxml2/2.9/libxml2-2.9.14.tar.xz'
wpewebkit @ 2.40.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-wandboard @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-tools @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-sifive-unmatched @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-sifive-unleashed @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-sandbox @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-rpi-arm64-efi @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-rpi-arm64 @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-rpi-4-32b-efi @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-rpi-4-32b @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-rpi-3-32b-efi @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-rpi-3-32b @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-rpi-2-efi @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-rpi-2 @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-rockpro64-rk3399 @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-rock64-rk3328 @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-qemu-riscv64-smode @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-qemu-riscv64 @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-qemu-arm64 @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-qemu-arm @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-puma-rk3399 @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-pinebook-pro-rk3399 @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-pinebook @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-pine64-plus @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-pine64-lts @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-novena @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-nintendo-nes-classic-edition @ 2018.11patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-mx6cuboxi @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-firefly-rk3399 @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-documentation @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-cubietruck @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-cubieboard @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-bananapi-m2-ultra @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-am335x-evm @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-am335x-boneblack @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-a20-olinuxino-micro @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-a20-olinuxino-lime2 @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
u-boot-a20-olinuxino-lime @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
sed @ 4.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-pyqt @ 5.15.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-pygpgme @ 0.3patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-clang @ 13.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-clang @ 12.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-clang @ 11.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-clang @ 10.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
patman @ 2022.10patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ocaml-llvm @ 9.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ocaml-llvm @ 11.1.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
ocaml-llvm @ 10.0.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
llvm-for-mesa @ 15.0.7patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libomp @ 15.0.7patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
emacs-clang-rename @ 13.0.1patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
cairo-xcb @ 1.16.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
boost-mpi @ 1.80.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
bash-with-syslog @ 5.1.16patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
zsh @ 5.8.1patch-headers

Validate patch headers

zsh-egrep-failing-test.patch: patch lacks comment and upstream status
zig @ 0.9.1patch-headers

Validate patch headers

zig-do-not-link-against-librt.patch: patch lacks comment and upstream status
zig @ 0.10.1patch-headers

Validate patch headers

zig-do-not-link-against-librt.patch: patch lacks comment and upstream status
tcsh @ 6.24.01patch-headers

Validate patch headers

tcsh-fix-autotest.patch: patch lacks comment and upstream status
symmetrica @ 2.0patch-headers

Validate patch headers

symmetrica-bruch.patch: patch lacks comment and upstream status
scribus @ 1.5.8patch-headers

Validate patch headers

scribus-1.5.8-poppler-22.09.0.patch: patch lacks comment and upstream status
xmlrpc-c @ 1.43.08formatting

Look for formatting issues in the source

line 1700 is way too long (91 characters)
u-boot-tools @ 2022.10formatting

Look for formatting issues in the source

line 780 is way too long (101 characters)
u-boot-tools @ 2022.10formatting

Look for formatting issues in the source

line 784 is way too long (92 characters)
symmetrica @ 2.0formatting

Look for formatting issues in the source

line 1579 is way too long (100 characters)
qtwebengine @ 6.3.2formatting

Look for formatting issues in the source

line 2822 is way too long (94 characters)
qtwebengine @ 6.3.2formatting

Look for formatting issues in the source

line 2825 is way too long (91 characters)
qtwebengine @ 6.3.2formatting

Look for formatting issues in the source

line 2846 is way too long (96 characters)
qtsensors @ 5.15.8formatting

Look for formatting issues in the source

line 1470 is way too long (97 characters)
qtmultimedia @ 5.15.8formatting

Look for formatting issues in the source

line 1508 is way too long (96 characters)
qtbase @ 6.3.2formatting

Look for formatting issues in the source

line 777 is way too long (97 characters)
qtbase @ 5.15.8formatting

Look for formatting issues in the source

line 484 is way too long (96 characters)
qtbase @ 5.15.8formatting

Look for formatting issues in the source

line 562 is way too long (97 characters)
qtbase @ 5.15.8formatting

Look for formatting issues in the source

line 567 is way too long (94 characters)
qtbase @ 5.15.8formatting

Look for formatting issues in the source

line 569 is way too long (94 characters)
python-pyqt @ 5.15.9formatting

Look for formatting issues in the source

line 3336 is way too long (105 characters)
pyconfigure @ 0.2.3formatting

Look for formatting issues in the source

line 610 is way too long (92 characters)
perl-sys-cpu @ 0.61formatting

Look for formatting issues in the source

line 10167 is way too long (97 characters)
openjdk @ 11.0.17formatting

Look for formatting issues in the source

line 1331 is way too long (91 characters)
minizip @ 1.2.13formatting

Look for formatting issues in the source

line 185 is way too long (115 characters)
libsigsegv @ 2.14formatting

Look for formatting issues in the source

line 48 is way too long (133 characters)
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 275, column 0
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 276, column 0
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 277, column 0
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 278, column 0
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 280, column 0
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 281, column 0
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 282, column 0
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 283, column 0
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 284, column 0
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 286, column 0
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 287, column 0
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 288, column 0
libarchive @ 3.6.1formatting

Look for formatting issues in the source

tabulation on line 289, column 0
julia @ 1.8.3formatting

Look for formatting issues in the source

line 435 is way too long (101 characters)
julia @ 1.8.3formatting

Look for formatting issues in the source

line 440 is way too long (124 characters)
icedtea @ 3.19.0formatting

Look for formatting issues in the source

line 756 is way too long (109 characters)
icedtea @ 3.19.0formatting

Look for formatting issues in the source

line 802 is way too long (99 characters)
icedtea @ 2.6.13formatting

Look for formatting issues in the source

line 425 is way too long (100 characters)
gst-plugins-base @ 1.22.2formatting

Look for formatting issues in the source

line 599 is way too long (91 characters)
gst-plugins-bad @ 1.22.2formatting

Look for formatting issues in the source

line 790 is way too long (91 characters)
glibc @ 2.35formatting

Look for formatting issues in the source

line 893 is way too long (98 characters)
ghc @ 8.6.5formatting

Look for formatting issues in the source

line 1123 is way too long (91 characters)
ghc @ 8.4.4formatting

Look for formatting issues in the source

line 1028 is way too long (92 characters)
ghc @ 8.4.4formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 1134 is way too long (106 characters)
esound @ 0.2.41formatting

Look for formatting issues in the source

line 356 is way too long (102 characters)
dejagnu @ 1.6.3formatting

Look for formatting issues in the source

line 78 is way too long (95 characters)
cups-minimal @ 2.4.2formatting

Look for formatting issues in the source

tabulation on line 291, column 0
cups-minimal @ 2.4.2formatting

Look for formatting issues in the source

tabulation on line 292, column 0
cups-minimal @ 2.4.2formatting

Look for formatting issues in the source

tabulation on line 293, column 0
cups-minimal @ 2.4.2formatting

Look for formatting issues in the source

tabulation on line 294, column 0
crda @ 3.18formatting

Look for formatting issues in the source

line 4618 is way too long (100 characters)
cairo @ 1.16.0formatting

Look for formatting issues in the source

tabulation on line 174, column 0
cairo @ 1.16.0formatting

Look for formatting issues in the source

tabulation on line 175, column 0
bzip2 @ 1.0.8formatting

Look for formatting issues in the source

line 315 is way too long (93 characters)
autogen @ 5.18.16formatting

Look for formatting issues in the source

line 76 is way too long (113 characters)
ghc @ 8.10.7formatting

Look for formatting issues in the source

line 1277 is way too long (98 characters)
lcov @ 1.16wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
c-blosc @ 1.21.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 64
unzip @ 6.0patch-headers

Validate patch headers

unzip-case-insensitive.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-CVE-2018-1000035.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-CVE-2018-18384.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-manpage-fix.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-overflow.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-valgrind.patch: patch lacks comment and upstream status
unzip @ 6.0patch-headers

Validate patch headers

unzip-x-option.patch: patch lacks comment and upstream status
p7zip @ 16.02patch-headers

Validate patch headers

p7zip-remove-unused-code.patch: patch lacks comment and upstream status
brotli @ 1.0.9formatting

Look for formatting issues in the source

line 2197 is way too long (94 characters)
rust-nu-plugin-query-json @ 0.44.0description

Validate package descriptions

description should start with an upper-case letter or digit
nushell @ 0.44.0description

Validate package descriptions

use @code or similar ornament instead of quotes
rust-nu-value-ext @ 0.44.0synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
python-jupyterlab-widgets @ 1.1.4description

Validate package descriptions

description should start with an upper-case letter or digit
ausweisapp2 @ 1.22.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
maven-slf4j-provider @ 3.8.6profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide
maven-shared-utils @ 3.2.1profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@16 and apache-parent-pom@18 collide
maven-settings-builder @ 3.8.6profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@8 and plexus-parent-pom@5.1 collide
maven-settings-builder @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@4.0 and plexus-parent-pom@5.1 collide
maven-resolver-provider @ 3.8.6profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide
maven-plugin-api @ 3.8.6profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide
maven-plugin-annotations @ 3.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide
maven-model-builder @ 3.8.6profile-collisions

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

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

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide
maven-embedder @ 3.8.6profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs plexus-parent-pom@5.1 and plexus-parent-pom@8 collide
maven-compat @ 3.8.6profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs maven-parent-pom@35 and maven-parent-pom@33 collide
maven-artifact @ 3.8.6profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@25 collide
maven-artifact @ 3.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs apache-parent-pom@21 and apache-parent-pom@6 collide
java-sonatype-aether-impl @ 1.7profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs java-sonatype-forge-parent-pom@6 and java-sonatype-forge-parent-pom@10 collide
maven-slf4j-provider @ 3.8.6patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
maven-wagon-http @ 3.4.3formatting

Look for formatting issues in the source

line 1061 is way too long (105 characters)
maven-wagon-http @ 3.4.3formatting

Look for formatting issues in the source

line 1066 is way too long (138 characters)
maven-wagon-http @ 3.4.3formatting

Look for formatting issues in the source

line 1067 is way too long (129 characters)
maven-wagon-file @ 3.4.3formatting

Look for formatting issues in the source

line 901 is way too long (125 characters)
maven-slf4j-provider @ 3.8.6formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 752 is way too long (109 characters)
maven-resolver-transport-wagon @ 1.6.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

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

Look for formatting issues in the source

line 280 is way too long (102 characters)
maven-resolver-transport-http @ 1.6.3formatting

Look for formatting issues in the source

line 379 is way too long (94 characters)
maven-resolver-transport-file @ 1.6.3formatting

Look for formatting issues in the source

line 334 is way too long (94 characters)
maven-resolver-impl @ 1.6.3formatting

Look for formatting issues in the source

line 197 is way too long (92 characters)
maven-resolver-impl @ 1.6.3formatting

Look for formatting issues in the source

line 206 is way too long (92 characters)
maven-resolver-impl @ 1.6.3formatting

Look for formatting issues in the source

line 214 is way too long (95 characters)
maven-resolver-impl @ 1.6.3formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 165 is way too long (99 characters)
maven-embedder @ 3.8.6formatting

Look for formatting issues in the source

line 1870 is way too long (110 characters)
maven-embedder @ 3.8.6formatting

Look for formatting issues in the source

line 1885 is way too long (116 characters)
maven-compat @ 3.8.6formatting

Look for formatting issues in the source

line 2092 is way too long (109 characters)
shunit2 @ 2.1.8synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
ungoogled-chromium @ 112.0.5615.165-1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
flyer-composer @ 1.0rc2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
zathura-pdf-poppler @ 0.3.1formatting

Look for formatting issues in the source

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

Look for formatting issues in the source

line 584 is way too long (93 characters)
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 438, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 440, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 443, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 444, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 453, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 454, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 455, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 456, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 457, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 458, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 459, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 461, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 462, column 0
slim @ 1.3.6formatting

Look for formatting issues in the source

tabulation on line 463, column 0
xfce4-clipman-plugin @ 1.6.3formatting

Look for formatting issues in the source

line 478 is way too long (91 characters)
tumbler @ 4.18.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
p2c @ 2.02synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
p2c @ 2.02synopsis

Validate package synopses

synopsis should not start with the package name
synfigstudio @ 1.4.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
synfig @ 1.4.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs libsigc++@2.9.3 and libsigc++@3.0.6 collide
lxqt-session @ 1.3.0formatting

Look for formatting issues in the source

line 701 is way too long (95 characters)
lxqt-session @ 1.3.0formatting

Look for formatting issues in the source

line 711 is way too long (100 characters)
lxqt-session @ 1.3.0formatting

Look for formatting issues in the source

line 713 is way too long (91 characters)
gtksourceview @ 5.8.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs glib@2.73.3 and glib@2.72.3 collide
mumble @ 1.4.287formatting

Look for formatting issues in the source

tabulation on line 595, column 0
mumble @ 1.4.287formatting

Look for formatting issues in the source

tabulation on line 596, column 0
mumble @ 1.4.287formatting

Look for formatting issues in the source

tabulation on line 597, column 0
mumble @ 1.4.287formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
emacs-protobuf-mode @ 3.21.9patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
pdfarranger @ 1.9.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
impressive @ 0.13.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python-django-q @ 1.3.4profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-django@3.2.18 and python-django@2.2.28 collide
ppsspp @ 1.14.4description

Validate package descriptions

use @code or similar ornament instead of quotes
cc65 @ 2.19formatting

Look for formatting issues in the source

line 2508 is way too long (167 characters)
nss-certs @ 3.88.1patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-atpublic @ 3.1.1synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
swayr @ 0.18.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 86, 128, 244
rust-winit @ 0.28.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
rust-winit @ 0.26.1description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
rust-winit @ 0.24.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
rust-winit @ 0.20.0-alpha6description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
rust-winit @ 0.19.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 49
rust-avif-serialize @ 0.7.7description

Validate package descriptions

use @code or similar ornament instead of quotes
rust-avif-serialize @ 0.6.5description

Validate package descriptions

use @code or similar ornament instead of quotes
rust-async-process @ 1.0.1description

Validate package descriptions

use @code or similar ornament instead of quotes
rust-arr-macro @ 0.1.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 35
rust-x11-clipboard @ 0.7.1synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
rust-x11-clipboard @ 0.5.1synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
rust-asn1-derive @ 0.8.7synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
rust-asn1-derive @ 0.13.0synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
i3status-rust @ 0.20.1synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
bat @ 0.20.0synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
gtk-doc @ 1.33.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gccgo @ 12.3.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gccgo @ 11.3.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
gccgo @ 10.4.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
pangomm @ 2.46.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs libsigc++@3.0.6 and libsigc++@2.9.3 collide
gtksourceviewmm @ 3.18.0profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs glibmm@2.72.1 and glibmm@2.64.5 collide
gtkmm @ 3.24.6profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs libsigc++@3.0.6 and libsigc++@2.9.3 collide
gtkmm @ 2.24.5profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs libsigc++@3.0.6 and libsigc++@2.9.3 collide
cairomm @ 1.14.2profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs libsigc++@2.9.3 and libsigc++@3.0.6 collide
libstdc++-doc @ 9.5.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
libgccjit @ 9.5.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libgccjit @ 12.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libgccjit @ 11.3.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libgccjit @ 10.4.0patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

file names of patches should start with the package name
gtk+ @ 3.24.37patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gtk+ @ 2.24.33patch-file-names

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate file names and availability of patches

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

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
libgccjit @ 9.5.0patch-headers

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
gcc-objc++ @ 9.5.0patch-headers

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
gcc-objc @ 9.5.0patch-headers

Validate patch headers

gcc-9-asan-fix-limits-include.patch: patch lacks comment and upstream status
rust-winit @ 0.20.0-alpha6formatting

Look for formatting issues in the source

line 3597 is way too long (114 characters)
rust-autocompress @ 0.2.2formatting

Look for formatting issues in the source

line 5451 is way too long (110 characters)
rust-async-compression @ 0.3.15formatting

Look for formatting issues in the source

line 4559 is way too long (92 characters)
rust-actix-derive @ 0.5.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
libdbusmenu @ 16.04.0-496formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
gtk-doc @ 1.33.2formatting

Look for formatting issues in the source

line 2207 is way too long (92 characters)
gtk+ @ 2.24.33formatting

Look for formatting issues in the source

tabulation on line 970, column 0
gtk+ @ 2.24.33formatting

Look for formatting issues in the source

tabulation on line 971, column 0
scheme48-prescheme @ 1.9.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
scheme48-prescheme @ 1.9.2formatting

Look for formatting issues in the source

line 492 is way too long (94 characters)
laminar @ 1.2formatting

Look for formatting issues in the source

line 206 is way too long (97 characters)
laminar @ 1.2formatting

Look for formatting issues in the source

line 208 is way too long (137 characters)
python-pyside-2-tools @ 5.15.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
python-pyside-2 @ 5.15.8patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
packagekit-qt5 @ 1.0.2formatting

Look for formatting issues in the source

tabulation on line 4496, column 0
packagekit-qt5 @ 1.0.2formatting

Look for formatting issues in the source

tabulation on line 4497, column 0
packagekit-qt5 @ 1.0.2formatting

Look for formatting issues in the source

tabulation on line 4498, column 0
python-geosketch @ 1.2description

Validate package descriptions

description should start with an upper-case letter or digit
kodi-wayland @ 19.5patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
kodi @ 19.5formatting

Look for formatting issues in the source

line 340 is way too long (96 characters)
book-faif @ 2.0description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 72
nmap @ 7.93wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
dstat @ 0.7.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
abseil-cpp @ 20200923.3formatting

Look for formatting issues in the source

line 1053 is way too long (116 characters)
abseil-cpp @ 20200923.3formatting

Look for formatting issues in the source

line 1054 is way too long (144 characters)
sooperlooper @ 1.7.8description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 120
python-discogs-client @ 2.3.12description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 70
pragha @ 1.3.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
fmit @ 1.2.14wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
demlo @ 3.8-0.fe9ec4cwrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
sfizz @ 1.2.0formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
rosegarden @ 22.12.1formatting

Look for formatting issues in the source

line 5269 is way too long (95 characters)
rosegarden @ 22.12.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5806, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5807, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5808, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5809, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5811, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5818, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5819, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5820, column 0
fmit @ 1.2.14formatting

Look for formatting issues in the source

tabulation on line 5821, column 0
glibc-bootstrap @ 0formatting

Look for formatting issues in the source

line 767 is way too long (100 characters)
gcc-bootstrap @ 0formatting

Look for formatting issues in the source

line 873 is way too long (100 characters)
rust-charset @ 0.1.2description

Validate package descriptions

description should start with an upper-case letter or digit
rust-bugreport @ 0.4.0description

Validate package descriptions

description should start with an upper-case letter or digit
rust-const-sha1 @ 0.2.0synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
rust-clippy-lints @ 0.0.153synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
rust-cargo-lock @ 8.0.3synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
rust-cargo-lock @ 7.0.1synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
bat @ 0.18.3synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
rust-clap @ 3.2.23formatting

Look for formatting issues in the source

line 11638 is way too long (110 characters)
rust-clap @ 3.2.23formatting

Look for formatting issues in the source

line 11639 is way too long (116 characters)
mousepad @ 0.6.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python-resampy @ 0.2.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 129
ecasound @ 2.9.3description

Validate package descriptions

sentences in description should be followed by two spaces; possible infractions at 71, 243, 322, 471
libfreeaptx @ 0.1.1synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
volk @ 3.0.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
solvespace @ 3.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
freehdl @ 0.0.8wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
freecad @ 0.20.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
cura @ 4.13.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
prusa-slicer @ 2.5.2formatting

Look for formatting issues in the source

line 3610 is way too long (94 characters)
libigl @ 2.3.0formatting

Look for formatting issues in the source

line 3464 is way too long (91 characters)
libigl @ 2.3.0formatting

Look for formatting issues in the source

line 3465 is way too long (101 characters)
libigl @ 2.3.0formatting

Look for formatting issues in the source

line 3492 is way too long (94 characters)
inspekt3d @ 0-0.703f52cformatting

Look for formatting issues in the source

line 1028 is way too long (96 characters)
freehdl @ 0.0.8formatting

Look for formatting issues in the source

line 2170 is way too long (101 characters)
remake @ 4.3-1.6synopsis

Validate package synopses

synopsis should not start with the package name
python-rdflib-jsonld @ 0.6.2synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
scanmem @ 0.17wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
c-reduce @ 2.10.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
xen @ 4.14.1synopsis

Validate package synopses

synopsis should not start with the package name
xen @ 4.14.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
criu @ 3.17.1formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
cscope @ 15.9description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 50
cdecl @ 2.5formatting

Look for formatting issues in the source

line 1036 is way too long (95 characters)
cdecl @ 2.5formatting

Look for formatting issues in the source

line 1037 is way too long (97 characters)
cdecl @ 2.5formatting

Look for formatting issues in the source

line 1040 is way too long (93 characters)
qbittorrent-nox @ 4.5.2description

Validate package descriptions

description should start with an upper-case letter or digit
qbittorrent @ 4.5.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-qt-program' is used
python-requests_ntlm @ 1.1.0name

Validate package names

name should use hyphens instead of underscores
python-warcio @ 1.7.4-0.aa702cbdescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 90
python-warcio @ 1.7.4-0.aa702cbdescription

Validate package descriptions

description should start with an upper-case letter or digit
python-html2text @ 2020.1.16description

Validate package descriptions

description should start with an upper-case letter or digit
python-aiostream @ 0.4.5description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 236
httpie @ 3.2.1synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
gunicorn @ 20.1.0wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
python-google-api-client @ 1.12.8profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs python-google-auth@1.35.0 and python-google-auth@2.17.3 collide
python-praw @ 7.6.1formatting

Look for formatting issues in the source

line 255 is way too long (93 characters)
python-praw @ 7.6.1formatting

Look for formatting issues in the source

line 256 is way too long (105 characters)
python-httpcore @ 0.17.0formatting

Look for formatting issues in the source

line 5875 is way too long (95 characters)
python-cloudscraper @ 1.2.60formatting

Look for formatting issues in the source

line 6776 is way too long (96 characters)
xdg-user-dirs @ 0.17description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 116
python-cchardet @ 2.1.7description

Validate package descriptions

description should start with an upper-case letter or digit
udisks @ 2.8.4wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
udiskie @ 2.4.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
perl-file-mimeinfo @ 0.33wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
libinput-minimal @ 1.22.1source-file-name

Validate file names of sources

the source file name should contain the package name
libinput @ 1.22.1source-file-name

Validate file names of sources

the source file name should contain the package name
malcontent @ 0.8.0formatting

Look for formatting issues in the source

line 360 is way too long (91 characters)
localed @ 241formatting

Look for formatting issues in the source

line 945 is way too long (96 characters)
xdot @ 1.1wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
tomb @ 2.9wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-bookmark-plus @ 2022.11.05description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 84
emacs-ac-php @ 2.4.2synopsis

Validate package synopses

synopsis should start with an upper-case letter or digit
emacs-bookmark-plus @ 2022.11.05source-file-name

Validate file names of sources

the source file name should contain the package name
emacs-bookmark-plus @ 2022.11.05formatting

Look for formatting issues in the source

tabulation on line 367, column 0
emacs-bookmark-plus @ 2022.11.05formatting

Look for formatting issues in the source

tabulation on line 368, column 0
emacs-bookmark-plus @ 2022.11.05formatting

Look for formatting issues in the source

tabulation on line 371, column 0
dbus-verbose @ 1.14.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
gobject-introspection @ 1.72.0patch-headers

Validate patch headers

gobject-introspection-girepository.patch: patch lacks comment and upstream status
ode @ 0.16.3tests-true

Check if tests are explicitly enabled

#:tests? must not be explicitly set to #t
python-xsge @ 2020.09.07description

Validate package descriptions

description should start with an upper-case letter or digit
grfcodec @ 6.0.6-0.7ded8ebdescription

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 100
deutex @ 5.2.2description

Validate package descriptions

sentences in description should be followed by two spaces; possible infraction at 60
emacs-xwidgets @ 28.2synopsis

Validate package synopses

synopsis should be less than 80 characters long
emacs-no-x-toolkit @ 28.2synopsis

Validate package synopses

synopsis should be less than 80 characters long
godot @ 3.4.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-wide-int @ 28.2wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-next-tree-sitter @ 29.0.91wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-next-pgtk-xwidgets @ 29.0.91wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-next-pgtk @ 29.0.91wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-next @ 29.0.91wrapper-inputs

Make sure 'wrap-program' can finds its interpreter.

"bash-minimal" should be in 'inputs' when 'wrap-program' is used
emacs-xwidgets @ 28.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-wide-int @ 28.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-no-x-toolkit @ 28.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-no-x @ 28.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-next-tree-sitter @ 29.0.91patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-next-pgtk-xwidgets @ 29.0.91patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-next-pgtk @ 29.0.91patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-next @ 29.0.91patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-motif @ 28.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
emacs-minimal @ 28.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
warsow-qfusion @ 2.5-1.c4de15dpatch-headers

Validate patch headers

warsow-qfusion-fix-bool-return-type.patch: patch lacks comment and upstream status
godot @ 3.4.2formatting

Look for formatting issues in the source

line 1931 is way too long (92 characters)
godot @ 3.4.2formatting

Look for formatting issues in the source

line 1934 is way too long (97 characters)
maven-wagon-provider-api @ 3.4.3profile-collisions

Report collisions that would occur due to propagated inputs

propagated inputs /gnu/store/a4g790ps9566jalb78n7y91qxakshl0i-maven-wagon-provider-api-3.4.3 and /gnu/store/p680086v4msj9mik9909dz3g00vcvygv-maven-wagon-provider-api-3.4.3 collide
node-serialport-parser-ready @ 9.2.4description

Validate package descriptions

use @code or similar ornament instead of quotes
node-nan @ 2.15.0description

Validate package descriptions

use @code or similar ornament instead of quotes
node-serialport @ 9.2.7formatting

Look for formatting issues in the source

parentheses feel lonely, move to the previous or next line
mecab-ipadic @ 2.7.0patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 289, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 291, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 293, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 295, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 297, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 299, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 301, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 303, column 18
libchewing @ 0.5.1formatting

Look for formatting issues in the source

tabulation on line 305, column 18
webkitgtk-with-libsoup2 @ 2.40.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
webkitgtk-next @ 2.40.2patch-file-names

Validate file names and availability of patches

file names of patches should start with the package name
wine64-staging @ 8.0inputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
wine-staging @ 8.0inputs-should-be-native

Identify inputs that should be native inputs

'autoconf' should probably be a native input
udiskie @ 2.4.2inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
u-boot-puma-rk3399 @ 2022.10inputs-should-be-native

Identify inputs that should be native inputs

'bison' should probably be a native input
u-boot-puma-rk3399 @ 2022.10inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
u-boot-puma-rk3399 @ 2022.10inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
u-boot-puma-rk3399 @ 2022.10inputs-should-be-native

Identify inputs that should be native inputs

'swig' should probably be a native input
transmission @ 4.0.3inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
thunar @ 4.18.6inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
telepathy-salut @ 0.8.1-1.90dbe5einputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
telepathy-mission-control @ 5.16.6inputs-should-be-native

Identify inputs that should be native inputs

'gtk-doc' should probably be a native input
telepathy-gabble @ 0.18.4-1.f1c762dinputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
sugar-toolkit-gtk3 @ 0.120inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
sugar-browse-activity @ 207inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
sugar-browse-activity @ 207inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
spice-gtk @ 0.42inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'groff' should probably be a native input
python-uqbar @ 0.5.6inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-stevedore @ 3.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-sphinxcontrib-svg2pdfconverter @ 1.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinxcontrib-programoutput @ 0.17inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinxcontrib-newsfeed @ 0.1.4inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinxcontrib-github-alt @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-sphinxcontrib-github-alt @ 1.2inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-tabs @ 3.4.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-sphinx-tabs @ 3.4.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-sitemap @ 2.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-rtd-theme @ 1.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-sphinx-rtd-theme @ 1.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-repoze-autointerface @ 0.8inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-pytest @ 0.0.5inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-sphinx-pytest @ 0.0.5inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-panels @ 0.6.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-sphinx-panels @ 0.6.0inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-intl @ 2.0.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-copybutton @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-cloud-sptheme @ 1.10.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-click @ 4.0.3inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-sphinx-click @ 4.0.3inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-autodoc-typehints @ 1.18.3inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-autobuild @ 2021.3.14inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx-argparse @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-sphinx @ 5.1.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-sphinx @ 4.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-requests-unixsocket @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-trio @ 0.7.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-tornasync @ 0.6.0.post2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-tornado @ 0.8.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-repeat @ 0.9.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-pydocstyle @ 2.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-mpl @ 0.16.1inputs-should-be-native

Identify inputs that should be native inputs

'python-nose' should probably be a native input
python-pytest-mockito @ 0.0.4inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-exploratory @ 0.5inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-django @ 4.4.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-csv @ 3.0.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-cram @ 0.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-console-scripts @ 1.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-mock' should probably be a native input
python-pytest-console-scripts @ 1.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-click @ 1.0.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-pytest-astropy @ 0.10.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest-cov' should probably be a native input
python-pydata-sphinx-theme @ 0.7.2inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-pydata-sphinx-theme @ 0.7.2inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-pep-adapter @ 2.1.3inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-oslo.utils @ 4.12.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-oslo.serialization @ 4.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-orange-canvas-core @ 0.1.24inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-openstacksdk @ 0.100.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-nbsphinx @ 0.8.8inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-nbsphinx @ 0.8.8inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-myst-parser @ 0.18.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-myst-parser @ 0.18.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-jschema-to-python @ 1.2.3inputs-should-be-native

Identify inputs that should be native inputs

'python-pbr' should probably be a native input
python-hatch-vcs @ 0.3.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-guzzle-sphinx-theme @ 0.7.11inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-fpylll @ 0.5.7inputs-should-be-native

Identify inputs that should be native inputs

'python-cython' should probably be a native input
python-fpylll @ 0.5.7inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
python-flit-scm @ 1.7.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
python-docrepr @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-docrepr @ 0.2.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'python-coverage' should probably be a native input
python-breathe @ 4.35.0inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
python-breathe @ 4.35.0inputs-should-be-native

Identify inputs that should be native inputs

'python-sphinx' should probably be a native input
python-bcj-cffi @ 0.5.0inputs-should-be-native

Identify inputs that should be native inputs

'python-setuptools-scm' should probably be a native input
presentty @ 0.2.1inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
parole @ 4.18.0inputs-should-be-native

Identify inputs that should be native inputs

'glib:bin' should probably be a native input
openfoam @ 4.1inputs-should-be-native

Identify inputs that should be native inputs

'flex' should probably be a native input
mate-polkit @ 1.24.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'desktop-file-utils' should probably be a native input
lua5.2-lgi @ 0.9.2inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
libvirt-glib @ 4.0.0inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'm4' should probably be a native input
libmypaint @ 1.6.1inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
lepton-eda @ 1.9.18-20220529inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
khotkeys @ 5.25.5inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kgamma @ 5.25.5inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kdevelop @ 22.08.1inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
kde-cli-tools @ 5.25.5inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
instead @ 3.3.5inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
gtkspell3 @ 3.0.10inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
gtk-doc @ 1.33.2inputs-should-be-native

Identify inputs that should be native inputs

'yelp-tools' should probably be a native input
gst-vosk @ 0.3.1inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
geda-gaf @ 1.10.2inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
freehdl @ 0.0.8inputs-should-be-native

Identify inputs that should be native inputs

'pkg-config' should probably be a native input
freehdl @ 0.0.8inputs-should-be-native

Identify inputs that should be native inputs

'libtool' should probably be a native input
flex @ 2.6.4inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'm4' should probably be a native input
fcitx5-gtk4 @ 5.0.23inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
fcitx5-gtk @ 5.0.23inputs-should-be-native

Identify inputs that should be native inputs

'gobject-introspection' should probably be a native input
fcitx-qt5 @ 1.2.7inputs-should-be-native

Identify inputs that should be native inputs

'intltool' should probably be a native input
docbook2x @ 0.8.8inputs-should-be-native

Identify inputs that should be native inputs

'texinfo' should probably be a native input
dico @ 2.11inputs-should-be-native

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

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

Identify inputs that should be native inputs

'm4' should probably be a native input
basket @ 2.49-1.e23a8b3inputs-should-be-native

Identify inputs that should be native inputs

'kdoctools' should probably be a native input
awscli @ 1.22.90inputs-should-be-native

Identify inputs that should be native inputs

'groff' should probably be a native input
awscli @ 1.22.90inputs-should-be-native

Identify inputs that should be native inputs

'python-docutils' should probably be a native input
autoconf @ 2.71inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
autoconf @ 2.69inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
autoconf @ 2.68inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
autoconf @ 2.64inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
autoconf @ 2.13inputs-should-be-native

Identify inputs that should be native inputs

'm4' should probably be a native input
389-ds-base @ 2.2.2inputs-should-be-native

Identify inputs that should be native inputs

'python-pytest' should probably be a native input
xonsh @ 0.14.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-urlgrabber @ 4.1.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-scrapy @ 2.7.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-pytest-tornado @ 0.8.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-pytest-helpers-namespace @ 2021.3.24inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-pymol @ 2.5.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-py7zr @ 0.20.2inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-protobuf @ 3.6.1inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-openapi-spec-validator @ 0.4.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-omnipath @ 1.0.6inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-pre-commit' should probably not be an input at all
python-jupyterlab-widgets @ 1.1.4inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-jupyter-packaging @ 0.12.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
python-django-auth-ldap @ 4.1.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-pip' should probably not be an input at all
python-bcj-cffi @ 0.5.0inputs-should-not-be-input

Identify inputs that shouldn't be inputs at all

'python-setuptools' should probably not be an input at all
zn-poly @ 0.9.2input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python2'
zile-on-guile @ 2.6.2-0.fd09781input-labels

Identify input labels that do not match package names

label 'gpg' does not match package name 'gnupg'
zile-on-guile @ 2.6.2-0.fd09781input-labels

Identify input labels that do not match package names

label 'boehm-gc' does not match package name 'libgc'
zile-on-guile @ 2.6.2-0.fd09781input-labels

Identify input labels that do not match package names

label 'gee' does not match package name 'libgee'
zile @ 2.6.2input-labels

Identify input labels that do not match package names

label 'boehm-gc' does not match package name 'libgc'
zile @ 2.6.2input-labels

Identify input labels that do not match package names

label 'gee' does not match package name 'libgee'
zig @ 0.10.1input-labels

Identify input labels that do not match package names

label 'zstd' does not match package name 'zstd:lib'
zbar @ 0.23.90input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
zbar @ 0.23.90input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
zbar @ 0.23.90input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
zathura @ 0.5.2input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
yasm @ 1.3.0input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
xyce-serial @ 6.8input-labels

Identify input labels that do not match package names

label 'fortran' does not match package name 'gfortran'
xyce-serial @ 6.8input-labels

Identify input labels that do not match package names

label 'trilinos' does not match package name 'trilinos-serial-xyce'
xyce-parallel @ 6.8input-labels

Identify input labels that do not match package names

label 'fortran' does not match package name 'gfortran'
xyce-parallel @ 6.8input-labels

Identify input labels that do not match package names

label 'trilinos' does not match package name 'trilinos-parallel-xyce'
xyce-parallel @ 6.8input-labels

Identify input labels that do not match package names

label 'mpi' does not match package name 'openmpi'
xst @ 0.8.4.1input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
xsane @ 0.999input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
xmlsec-nss @ 1.2.37input-labels

Identify input labels that do not match package names

label 'nss' does not match package name 'nss:bin'
xfstests @ 1.1.0-1.bae1d15input-labels

Identify input labels that do not match package names

label 'libuuid' does not match package name 'util-linux:lib'
xfig @ 3.2.8binput-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
xfdashboard @ 1.0.0input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
xfconf @ 4.18.1input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
xfce4-statusnotifier-plugin @ 0.2.3input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
xfce4-notifyd @ 0.8.2input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
xeus @ 2.4.1input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
xen @ 4.14.1input-labels

Identify input labels that do not match package names

label 'cmake' does not match package name 'cmake-minimal'
xen @ 4.14.1input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
xen @ 4.14.1input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python2'
xen @ 4.14.1input-labels

Identify input labels that do not match package names

label 'cross-gcc' does not match package name 'gcc-cross-i686-linux-gnu'
xen @ 4.14.1input-labels

Identify input labels that do not match package names

label 'cross-libc' does not match package name 'glibc-cross-i686-linux-gnu'
xen @ 4.14.1input-labels

Identify input labels that do not match package names

label 'cross-libc-static' does not match package name 'glibc-cross-i686-linux-gnu:static'
xen @ 4.14.1input-labels

Identify input labels that do not match package names

label 'iproute' does not match package name 'iproute2'
xen @ 4.14.1input-labels

Identify input labels that do not match package names

label 'qemu' does not match package name 'qemu-minimal'
xen @ 4.14.1input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
xdg-user-dirs @ 0.17input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
xdg-user-dirs @ 0.17input-labels

Identify input labels that do not match package names

label 'xsltproc' does not match package name 'libxslt'
xarcan @ 0.5.4-1.8e6ee02input-labels

Identify input labels that do not match package names

label 'libkbfile' does not match package name 'libxkbfile'
xarcan @ 0.5.4-1.8e6ee02input-labels

Identify input labels that do not match package names

label 'libxfont2' does not match package name 'libxfont'
xapian @ 1.4.19input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
wv @ 1.2.9input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
wpewebkit @ 2.40.0input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
windowmaker @ 0.95.9input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
windowmaker @ 0.95.9input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
webkitgtk-with-libsoup2 @ 2.40.2input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
webkitgtk-with-libsoup2 @ 2.40.2input-labels

Identify input labels that do not match package names

label 'libsoup' does not match package name 'libsoup-minimal'
webkitgtk-next @ 2.40.2input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
webkitgtk-next @ 2.40.2input-labels

Identify input labels that do not match package names

label 'gtk+' does not match package name 'gtk'
webkitgtk @ 2.40.2input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
warsow-qfusion @ 2.5-1.c4de15dinput-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
warsow-qfusion @ 2.5-1.c4de15dinput-labels

Identify input labels that do not match package names

label 'qtdeclarative-5' does not match package name 'qtdeclarative'
warsow-qfusion @ 2.5-1.c4de15dinput-labels

Identify input labels that do not match package names

label 'uuid.h' does not match package name 'util-linux:lib'
w3m @ 0.5.3+git20230121input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
volk @ 3.0.0input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
vlang @ 0.2.4input-labels

Identify input labels that do not match package names

label 'git' does not match package name 'git-minimal'
vkd3d @ 1.2input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
virt-viewer @ 11.0input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
virt-manager @ 4.1.0input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
virt-manager @ 4.1.0input-labels

Identify input labels that do not match package names

label 'gtk+' does not match package name 'gtk+:bin'
virt-manager @ 4.1.0input-labels

Identify input labels that do not match package names

label 'rst2man' does not match package name 'python-docutils'
vimb @ 3.6.0input-labels

Identify input labels that do not match package names

label 'webkitgtk' does not match package name 'webkitgtk-with-libsoup2'
viewnior @ 1.8input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
vice @ 3.6input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
verilator @ 4.204input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
vboot-utils @ R63-10032.Binput-labels

Identify input labels that do not match package names

label 'python@2' does not match package name 'python2'
vboot-utils @ R63-10032.Binput-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
valgrind @ 3.20.0input-labels

Identify input labels that do not match package names

label 'glibc' does not match package name 'glibc:debug'
unicorn @ 1.0.2-rc4input-labels

Identify input labels that do not match package names

label 'hexdump-for-tests' does not match package name 'util-linux'
ungoogled-chromium-wayland @ 112.0.5615.165-1input-labels

Identify input labels that do not match package names

label 'bash' does not match package name 'bash-minimal'
ungoogled-chromium-wayland @ 112.0.5615.165-1input-labels

Identify input labels that do not match package names

label 'glibc-locales' does not match package name 'glibc-utf8-locales'
uncrustify @ 0.75.1input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
ugrep @ 3.11.2input-labels

Identify input labels that do not match package names

label 'zstd' does not match package name 'zstd:lib'
udisks @ 2.8.4input-labels

Identify input labels that do not match package names

label 'xsltproc' does not match package name 'libxslt'
udiskie @ 2.4.2input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
u-boot-wandboard @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-ts7970-q-2g-1000mhz-c @ 2015.04_3-0.0880916input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-tools @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-sifive-unmatched @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-sifive-unleashed @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-sandbox @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-rpi-arm64-efi @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-rpi-arm64 @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-rpi-4-32b-efi @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-rpi-4-32b @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-rpi-3-32b-efi @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-rpi-3-32b @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-rpi-2-efi @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-rpi-2 @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-rockpro64-rk3399 @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-rock64-rk3328 @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-qemu-riscv64-smode @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-qemu-riscv64 @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-qemu-arm64 @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-qemu-arm @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-puma-rk3399 @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-puma-rk3399 @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-pinebook-pro-rk3399 @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-pinebook @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-pine64-plus @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-pine64-lts @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-novena @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-nintendo-nes-classic-edition @ 2018.11input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python2'
u-boot-nintendo-nes-classic-edition @ 2018.11input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-mx6cuboxi @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-firefly-rk3399 @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-documentation @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-cubietruck @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-cubieboard @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-bananapi-m2-ultra @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-am335x-evm @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-am335x-boneblack @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-a20-olinuxino-micro @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-a20-olinuxino-lime2 @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
u-boot-a20-olinuxino-lime @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
tz @ 0.6.1input-labels

Identify input labels that do not match package names

label 'github.com/charmbracelet/bubbletea' does not match package name 'go-github-com-charmbracelet-bubbletea'
tz @ 0.6.1input-labels

Identify input labels that do not match package names

label 'github.com/muesli/termenv' does not match package name 'go-github-com-muesli-termenv'
tuxmath @ 2.0.3input-labels

Identify input labels that do not match package names

label 'sdl' does not match package name 'sdl-union'
turbovnc @ 3.0.1input-labels

Identify input labels that do not match package names

label 'openjdk' does not match package name 'openjdk:jdk'
tumbler @ 4.18.1input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
tsukundere @ 0.4.3input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
tsukundere @ 0.4.3input-labels

Identify input labels that do not match package names

label 'guile-sdl2' does not match package name 'guile3.0-sdl2'
tryton @ 6.2.7input-labels

Identify input labels that do not match package names

label 'glib-compile-schemas' does not match package name 'glib:bin'
transmission @ 4.0.3input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
translate-shell @ 0.9.7.1input-labels

Identify input labels that do not match package names

label 'emacs' does not match package name 'emacs-minimal'
transfig @ 3.2.5einput-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
tractor @ 4.1.1input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
tor-client @ 0.4.7.13input-labels

Identify input labels that do not match package names

label 'zstd' does not match package name 'zstd:lib'
tor @ 0.4.7.13input-labels

Identify input labels that do not match package names

label 'zstd' does not match package name 'zstd:lib'
tomb @ 2.9input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
tk @ 8.6.12input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
timewarrior @ 1.4.3input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
tilda @ 1.5.4input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
tigervnc-server @ 1.12.0-0.b484c22input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
tigervnc-server @ 1.12.0-0.b484c22input-labels

Identify input labels that do not match package names

label 'udev' does not match package name 'eudev'
tigervnc-server @ 1.12.0-0.b484c22input-labels

Identify input labels that do not match package names

label 'libxfont2' does not match package name 'libxfont'
tgcli @ 0.3.1input-labels

Identify input labels that do not match package names

label 'coveralls' does not match package name 'python-coveralls'
tgcli @ 0.3.1input-labels

Identify input labels that do not match package names

label 'pytest' does not match package name 'python-pytest'
tgcli @ 0.3.1input-labels

Identify input labels that do not match package names

label 'pytest-click' does not match package name 'python-pytest-click'
tgcli @ 0.3.1input-labels

Identify input labels that do not match package names

label 'pytest-cov' does not match package name 'python-pytest-cov'
tgcli @ 0.3.1input-labels

Identify input labels that do not match package names

label 'mkdocs' does not match package name 'python-mkdocs'
tgcli @ 0.3.1input-labels

Identify input labels that do not match package names

label 'mkdocs-material' does not match package name 'python-mkdocs-material'
tgcli @ 0.3.1input-labels

Identify input labels that do not match package names

label 'requests-mock' does not match package name 'python-requests-mock'
tgcli @ 0.3.1input-labels

Identify input labels that do not match package names

label 'click' does not match package name 'python-click'
tgcli @ 0.3.1input-labels

Identify input labels that do not match package names

label 'colorful' does not match package name 'python-colorful'
tgcli @ 0.3.1input-labels

Identify input labels that do not match package names

label 'requests' does not match package name 'python-requests'
tgcli @ 0.3.1input-labels

Identify input labels that do not match package names

label 'yaspin' does not match package name 'python-yaspin'
tesseract-engine @ 20200615-2411input-labels

Identify input labels that do not match package names

label 'sdl2-union' does not match package name 'sdl-union'
tesseract-engine @ 20200615-2411input-labels

Identify input labels that do not match package names

label 'libgl' does not match package name 'mesa'
termite @ 15input-labels

Identify input labels that do not match package names

label 'vte' does not match package name 'vte-ng'
telepathy-salut @ 0.8.1-1.90dbe5einput-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
telepathy-salut @ 0.8.1-1.90dbe5einput-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
telepathy-mission-control @ 5.16.6input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
telepathy-logger @ 0.8.2input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python2'
telepathy-logger @ 0.8.2input-labels

Identify input labels that do not match package names

label 'xsltproc' does not match package name 'libxslt'
telepathy-gabble @ 0.18.4-1.f1c762dinput-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
telegram-desktop @ 4.8.1input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
telegram-desktop @ 4.8.1input-labels

Identify input labels that do not match package names

label 'gtk+' does not match package name 'gtk+:bin'
taskwarrior @ 2.6.2input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
task-spooler @ 1.0.1input-labels

Identify input labels that do not match package names

label 'bash' does not match package name 'bash-minimal'
tabbed @ 0.6input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
t4k-common @ 0.1.1input-labels

Identify input labels that do not match package names

label 'font-andika' does not match package name 'font-sil-andika'
t4k-common @ 0.1.1input-labels

Identify input labels that do not match package names

label 'sdl' does not match package name 'sdl-union'
syslinux @ 6.04-pre-1.bb41e93input-labels

Identify input labels that do not match package names

label 'python-2' does not match package name 'python2'
syslinux @ 6.04-pre-1.bb41e93input-labels

Identify input labels that do not match package names

label 'libuuid' does not match package name 'util-linux:lib'
sysbench @ 1.0.20input-labels

Identify input labels that do not match package names

label 'mariadb' does not match package name 'mariadb:dev'
synergy @ 1.11.1input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
sxmo-st @ 0.8.4.1input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
swig @ 4.0.2input-labels

Identify input labels that do not match package names

label 'pcre' does not match package name 'pcre:bin'
swi-prolog @ 8.5.20input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
swi-prolog @ 8.5.20input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
surf @ 2.1input-labels

Identify input labels that do not match package names

label 'webkitgtk' does not match package name 'webkitgtk-with-libsoup2'
sugar-toolkit-gtk3 @ 0.120input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
sugar-browse-activity @ 207input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
sugar @ 0.120input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
st @ 0.8.5input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
sssd @ 2.8.1input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
sssd @ 2.8.1input-labels

Identify input labels that do not match package names

label 'bind' does not match package name 'bind:utils'
squirrel @ 3.1input-labels

Identify input labels that do not match package names

label 'cmake' does not match package name 'cmake-minimal'
spread-sheet-widget @ 0.7input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
splix @ 2.0.0-315.76268c4input-labels

Identify input labels that do not match package names

label 'cups' does not match package name 'cups-minimal'
spice-gtk @ 0.42input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
spandsp @ 0.0.6input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
snapraid @ 12.0input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
slurm @ 22.05.1input-labels

Identify input labels that do not match package names

label 'hwloc' does not match package name 'hwloc:lib'
slurm @ 21.08.8input-labels

Identify input labels that do not match package names

label 'hwloc' does not match package name 'hwloc:lib'
slurm @ 20.11.9input-labels

Identify input labels that do not match package names

label 'hwloc' does not match package name 'hwloc:lib'
slurm @ 20.02.6-1input-labels

Identify input labels that do not match package names

label 'hwloc' does not match package name 'hwloc:lib'
slurm @ 19.05.8input-labels

Identify input labels that do not match package names

label 'hwloc' does not match package name 'hwloc:lib'
slurm @ 18.08.9input-labels

Identify input labels that do not match package names

label 'hwloc' does not match package name 'hwloc:lib'
slstatus @ 0-0.84a2f11input-labels

Identify input labels that do not match package names

label 'x11' does not match package name 'libx11'
slim @ 1.3.6input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
slim @ 1.3.6input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
singular @ 4.2.1input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python2'
sigrok-firmware-fx2lafw @ 0.1.7input-labels

Identify input labels that do not match package names

label 'awk' does not match package name 'gawk'
signing-party @ 2.11input-labels

Identify input labels that do not match package names

label 'autoconf' does not match package name 'autoconf-wrapper'
sfml @ 2.5.1input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
sequoia @ 1.6.0input-labels

Identify input labels that do not match package names

label 'libsequoia' does not match package name 'libsequoia:python'
sdl2-image @ 2.6.2input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
sdl-pango @ 0.1.2input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
sdl-mixer @ 1.2.12input-labels

Identify input labels that do not match package names

label 'libflac' does not match package name 'flac'
sdl-image @ 1.2.12input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
sdcv @ 0.5.3input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
scorep-openmpi @ 3.1input-labels

Identify input labels that do not match package names

label 'mpi' does not match package name 'openmpi'
scorep-openmpi @ 3.1input-labels

Identify input labels that do not match package names

label 'cubelib' does not match package name 'cube:lib'
scanbd @ 1.5.1input-labels

Identify input labels that do not match package names

label 'udev' does not match package name 'eudev'
sbcl-stefil @ 0.1-0.0398548input-labels

Identify input labels that do not match package names

label 'alexandria' does not match package name 'sbcl-alexandria'
sbcl-stefil @ 0.1-0.0398548input-labels

Identify input labels that do not match package names

label 'iterate' does not match package name 'sbcl-iterate'
sbcl-stefil @ 0.1-0.0398548input-labels

Identify input labels that do not match package names

label 'metabang-bind' does not match package name 'sbcl-metabang-bind'
sbcl-stefil @ 0.1-0.0398548input-labels

Identify input labels that do not match package names

label 'swank' does not match package name 'sbcl-slime-swank'
sane-backends-minimal @ 1.0.32input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
sane-backends-minimal @ 1.0.32input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
sane-backends @ 1.0.32input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
sane-backends @ 1.0.32input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
sane-backends @ 1.0.32input-labels

Identify input labels that do not match package names

label 'hplip' does not match package name 'hplip-minimal'
sane-backends @ 1.0.32input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
rust @ 1.67.1input-labels

Identify input labels that do not match package names

label 'cmake' does not match package name 'cmake-minimal'
rust @ 1.67.1input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
rust @ 1.67.1input-labels

Identify input labels that do not match package names

label 'rustc-bootstrap' does not match package name 'rust'
rust @ 1.67.1input-labels

Identify input labels that do not match package names

label 'cargo-bootstrap' does not match package name 'rust:cargo'
rust @ 1.67.1input-labels

Identify input labels that do not match package names

label 'libcurl' does not match package name 'curl'
rsyslog @ 8.2204.1input-labels

Identify input labels that do not match package names

label 'mariadb' does not match package name 'mariadb:dev'
rsyslog @ 8.2204.1input-labels

Identify input labels that do not match package names

label 'mariadb' does not match package name 'mariadb:lib'
rsyslog @ 8.2204.1input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
rsync @ 3.2.7input-labels

Identify input labels that do not match package names

label 'zstd' does not match package name 'zstd:lib'
roffit @ 0.12-1.b59e6c855input-labels

Identify input labels that do not match package names

label 'html-tree' does not match package name 'perl-html-tree'
roct-thunk-interface @ 5.1.3input-labels

Identify input labels that do not match package names

label 'gcc' does not match package name 'gcc:lib'
rocr-runtime @ 5.1.3input-labels

Identify input labels that do not match package names

label 'llvm' does not match package name 'llvm-for-rocm'
rocm-device-libs @ 5.1.3input-labels

Identify input labels that do not match package names

label 'llvm' does not match package name 'llvm-for-rocm'
rocm-comgr @ 5.1.3input-labels

Identify input labels that do not match package names

label 'llvm' does not match package name 'llvm-for-rocm'
robocut @ 1.0.11input-labels

Identify input labels that do not match package names

label 'qmake' does not match package name 'qtbase'
robocut @ 1.0.11input-labels

Identify input labels that do not match package names

label 'qt' does not match package name 'qtbase'
robocut @ 1.0.11input-labels

Identify input labels that do not match package names

label 'qtsvg-5' does not match package name 'qtsvg'
ristretto @ 0.13.1input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
retroarch @ 1.15.0input-labels

Identify input labels that do not match package names

label 'sdl' does not match package name 'sdl2'
retroarch @ 1.15.0input-labels

Identify input labels that do not match package names

label 'udev' does not match package name 'eudev'
reprotest @ 0.7.23input-labels

Identify input labels that do not match package names

label 'python-magic ' does not match package name 'python-magic'
reprotest @ 0.7.23input-labels

Identify input labels that do not match package names

label 'python-pytest ' does not match package name 'python-pytest'
renpy @ 8.1.0input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python:tk'
remmina @ 1.4.29input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
remmina @ 1.4.29input-labels

Identify input labels that do not match package names

label 'gtk+' does not match package name 'gtk+:bin'
rasqal @ 0.9.33input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
raspi-arm64-chainloader @ 0.1input-labels

Identify input labels that do not match package names

label 'locales' does not match package name 'glibc-utf8-locales'
raspi-arm-chainloader @ 0.1input-labels

Identify input labels that do not match package names

label 'binutils' does not match package name 'binutils-cross-arm-none-eabi'
raspi-arm-chainloader @ 0.1input-labels

Identify input labels that do not match package names

label 'gcc' does not match package name 'gcc-cross-sans-libc-arm-none-eabi'
rapid-photo-downloader @ 0.9.18input-labels

Identify input labels that do not match package names

label 'usdisks' does not match package name 'udisks'
qtbase @ 6.3.2input-labels

Identify input labels that do not match package names

label 'mariadb' does not match package name 'mariadb:dev'
qtbase @ 5.15.8input-labels

Identify input labels that do not match package names

label 'mariadb' does not match package name 'mariadb:dev'
qt-creator @ 9.0.0input-labels

Identify input labels that do not match package names

label 'zstd' does not match package name 'zstd:lib'
qiv @ 2.3.3input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
qemu-minimal @ 7.2.1input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
qemu-minimal @ 7.2.1input-labels

Identify input labels that do not match package names

label 'zstd' does not match package name 'zstd:lib'
qemu @ 7.2.1input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
qemu @ 7.2.1input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:static'
qemu @ 7.2.1input-labels

Identify input labels that do not match package names

label 'pcre' does not match package name 'pcre:static'
qemu @ 7.2.1input-labels

Identify input labels that do not match package names

label 'zlib' does not match package name 'zlib:static'
qemu @ 7.2.1input-labels

Identify input labels that do not match package names

label 'zstd' does not match package name 'zstd:lib'
qbittorrent-nox @ 4.5.2input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
qbittorrent @ 4.5.2input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
qbittorrent @ 4.5.2input-labels

Identify input labels that do not match package names

label 'qtsvg-5' does not match package name 'qtsvg'
python-zope-exceptions @ 4.6input-labels

Identify input labels that do not match package names

label 'python-zope-testrunner' does not match package name 'python-zope-testrunner-bootstrap'
python-zope-copy @ 4.2input-labels

Identify input labels that do not match package names

label 'python-zope-component' does not match package name 'python-zope-component-bootstrap'
python-zope-copy @ 4.2input-labels

Identify input labels that do not match package names

label 'python-zope-location' does not match package name 'python-zope-location-bootstrap'
python-zope-component @ 4.6.2input-labels

Identify input labels that do not match package names

label 'python-zope-configuration' does not match package name 'python-zope-configuration-bootstrap'
python-zope-component @ 4.6.2input-labels

Identify input labels that do not match package names

label 'python-zope-location' does not match package name 'python-zope-location-bootstrap'
python-zope-component @ 4.6.2input-labels

Identify input labels that do not match package names

label 'python-zope-proxy' does not match package name 'python-zope-proxy-bootstrap'
python-zope-component @ 4.6.2input-labels

Identify input labels that do not match package names

label 'python-zope-security' does not match package name 'python-zope-security-bootstrap'
python-venusian @ 3.0.0input-labels

Identify input labels that do not match package names

label 'python-runner' does not match package name 'python-pytest-runner'
python-sip @ 4.19.25input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
python-reno @ 2.7.0input-labels

Identify input labels that do not match package names

label 'git' does not match package name 'git-minimal'
python-pyxel @ 1.4.3input-labels

Identify input labels that do not match package names

label 'sdl2' does not match package name 'sdl-union'
python-pyqtwebengine @ 5.15.9input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
python-pyqtwebengine @ 5.15.9input-labels

Identify input labels that do not match package names

label 'qtsvg-5' does not match package name 'qtsvg'
python-pyqtwebengine @ 5.15.9input-labels

Identify input labels that do not match package names

label 'qtdeclarative-5' does not match package name 'qtdeclarative'
python-pyqtwebengine @ 5.15.9input-labels

Identify input labels that do not match package names

label 'qtwebchannel-5' does not match package name 'qtwebchannel'
python-pyqtwebengine @ 5.15.9input-labels

Identify input labels that do not match package names

label 'qtwebengine-5' does not match package name 'qtwebengine'
python-pyqt @ 5.15.9input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
python-pyqt @ 5.15.9input-labels

Identify input labels that do not match package names

label 'qtdeclarative-5' does not match package name 'qtdeclarative'
python-pyqt @ 5.15.9input-labels

Identify input labels that do not match package names

label 'qtmultimedia-5' does not match package name 'qtmultimedia'
python-pyqt @ 5.15.9input-labels

Identify input labels that do not match package names

label 'qtsvg-5' does not match package name 'qtsvg'
python-pyqt @ 5.15.9input-labels

Identify input labels that do not match package names

label 'qttools-5' does not match package name 'qttools'
python-pyqt @ 5.15.9input-labels

Identify input labels that do not match package names

label 'qtwebchannel-5' does not match package name 'qtwebchannel'
python-pyqt @ 5.15.9input-labels

Identify input labels that do not match package names

label 'qtwebsockets-5' does not match package name 'qtwebsockets'
python-pypa-build @ 0.7.0input-labels

Identify input labels that do not match package names

label 'python-packaging' does not match package name 'python-packaging-bootstrap'
python-pypa-build @ 0.7.0input-labels

Identify input labels that do not match package names

label 'python-pep517' does not match package name 'python-pep517-bootstrap'
python-pep-adapter @ 2.1.3input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
python-leather @ 0.3.4input-labels

Identify input labels that do not match package names

label 'python-csselect' does not match package name 'python-cssselect'
python-flit-core @ 3.8.0input-labels

Identify input labels that do not match package names

label 'python-toml' does not match package name 'python-tomli'
python-django-statici18n @ 2.1.0input-labels

Identify input labels that do not match package names

label 'django-appconf' does not match package name 'python-django-appconf'
python-django-picklefield @ 3.0.1input-labels

Identify input labels that do not match package names

label 'python-django@2.2' does not match package name 'python-django'
python-clang @ 13.0.1input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
python-clang @ 12.0.1input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
python-clang @ 11.1.0input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
python-clang @ 10.0.1input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
python-cffi-documentation @ 1.15.1input-labels

Identify input labels that do not match package names

label 'sphinx-build' does not match package name 'python-sphinx'
python-agate @ 1.7.1input-labels

Identify input labels that do not match package names

label 'locales' does not match package name 'python-agate-locales'
python-agate @ 1.7.1input-labels

Identify input labels that do not match package names

label 'python-csselect' does not match package name 'python-cssselect'
pulseaudio @ 16.1input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
proof-general @ 4.4-1.1b1083einput-labels

Identify input labels that do not match package names

label 'emacs' does not match package name 'emacs-minimal'
presage @ 0.9.1input-labels

Identify input labels that do not match package names

label 'dot' does not match package name 'graphviz'
presage @ 0.9.1input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
praat @ 6.1.30input-labels

Identify input labels that do not match package names

label 'gtk' does not match package name 'gtk+'
praat @ 6.1.30input-labels

Identify input labels that do not match package names

label 'publesaudio' does not match package name 'pulseaudio'
ppsspp @ 1.14.4input-labels

Identify input labels that do not match package names

label 'zstd' does not match package name 'zstd:lib'
power-profiles-daemon @ 0.12input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
postgresql @ 15.1input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
postgresql @ 14.6input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
postgresql @ 13.9input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
postgresql @ 11.18input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
postgresql @ 10.23input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
poppler-qt5 @ 22.09.0input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
poppler @ 22.09.0input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
polkit @ 121input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
pocl @ 3.1input-labels

Identify input labels that do not match package names

label 'hwloc' does not match package name 'hwloc:lib'
pluma @ 1.24.1input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
plocate @ 1.1.18input-labels

Identify input labels that do not match package names

label 'zstd' does not match package name 'zstd:lib'
plantuml @ 1.2022.7input-labels

Identify input labels that do not match package names

label 'jre' does not match package name 'icedtea'
pinentry-tty @ 1.2.1input-labels

Identify input labels that do not match package names

label 'libsecret' does not match package name 'libsecret:out'
pinentry-qt @ 1.2.1input-labels

Identify input labels that do not match package names

label 'libsecret' does not match package name 'libsecret:out'
pinentry-gtk2 @ 1.2.1input-labels

Identify input labels that do not match package names

label 'libsecret' does not match package name 'libsecret:out'
pinentry-gnome3 @ 1.2.1input-labels

Identify input labels that do not match package names

label 'libsecret' does not match package name 'libsecret:out'
pinentry-emacs @ 1.2.1input-labels

Identify input labels that do not match package names

label 'libsecret' does not match package name 'libsecret:out'
pinentry-efl @ 1.2.1input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
pinentry-efl @ 1.2.1input-labels

Identify input labels that do not match package names

label 'libsecret' does not match package name 'libsecret:out'
pinentry @ 1.2.1input-labels

Identify input labels that do not match package names

label 'libsecret' does not match package name 'libsecret:out'
perl-tk @ 804.036input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
perl-file-which @ 1.23input-labels

Identify input labels that do not match package names

label 'test-script' does not match package name 'perl-test-script'
perl-alien-sdl @ 1.446input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
perl-alien-sdl @ 1.446input-labels

Identify input labels that do not match package names

label 'sdl' does not match package name 'sdl-union'
pep-engine @ 2.1.34input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
pdfpc @ 4.5.0input-labels

Identify input labels that do not match package names

label 'webkitgtk' does not match package name 'webkitgtk-with-libsoup2'
pdf2djvu @ 0.9.19input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
pcsxr @ 1.9.95input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
patman @ 2022.10input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
parole @ 4.18.0input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
papirus-icon-theme @ 20230104input-labels

Identify input labels that do not match package names

label 'gtk+' does not match package name 'gtk+:bin'
papi @ 6.0.0.1input-labels

Identify input labels that do not match package names

label 'lm-sensors' does not match package name 'lm-sensors:lib'
papi @ 6.0.0.1input-labels

Identify input labels that do not match package names

label 'infiniband-diags' does not match package name 'infiniband-diags:lib'
pango @ 1.90.0input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
pango @ 1.50.10input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
pango @ 1.42.4input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
packagekit @ 1.2.5input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
pacemaker @ 2.1.4input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
orage @ 4.18.0input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
openscad @ 2021.01input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
openscad @ 2021.01input-labels

Identify input labels that do not match package names

label 'ps' does not match package name 'procps'
openscad @ 2021.01input-labels

Identify input labels that do not match package names

label 'xvfb' does not match package name 'xorg-server'
openscad @ 2021.01input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
openscad @ 2021.01input-labels

Identify input labels that do not match package names

label 'qtmultimedia-5' does not match package name 'qtmultimedia'
openni2 @ 2.2.0input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
openni2 @ 2.2.0input-labels

Identify input labels that do not match package names

label 'freeglut3' does not match package name 'freeglut'
openni2 @ 2.2.0input-labels

Identify input labels that do not match package names

label 'libudev' does not match package name 'eudev'
openmpi-thread-multiple @ 4.1.5input-labels

Identify input labels that do not match package names

label 'hwloc' does not match package name 'hwloc:lib'
openmpi-c++ @ 4.1.5input-labels

Identify input labels that do not match package names

label 'hwloc' does not match package name 'hwloc:lib'
openmpi @ 4.1.5input-labels

Identify input labels that do not match package names

label 'hwloc' does not match package name 'hwloc:lib'
openjdk @ 9.181input-labels

Identify input labels that do not match package names

label 'icedtea-8' does not match package name 'icedtea'
openjdk @ 9.181input-labels

Identify input labels that do not match package names

label 'icedtea-8:jdk' does not match package name 'icedtea:jdk'
openjdk @ 9.181input-labels

Identify input labels that do not match package names

label 'make@4.2' does not match package name 'make'
openjdk @ 9.181input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
openjdk @ 9.181input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
openjdk @ 16.0.2input-labels

Identify input labels that do not match package names

label 'openjdk' does not match package name 'openjdk:jdk'
openjdk @ 15.0.9input-labels

Identify input labels that do not match package names

label 'openjdk' does not match package name 'openjdk:jdk'
openjdk @ 14.0.2input-labels

Identify input labels that do not match package names

label 'openjdk' does not match package name 'openjdk:jdk'
openjdk @ 13.0.13input-labels

Identify input labels that do not match package names

label 'openjdk' does not match package name 'openjdk:jdk'
openjdk @ 12.33input-labels

Identify input labels that do not match package names

label 'openjdk' does not match package name 'openjdk:jdk'
openjdk @ 11.0.17input-labels

Identify input labels that do not match package names

label 'openjdk' does not match package name 'openjdk:jdk'
openjdk @ 10.46input-labels

Identify input labels that do not match package names

label 'openjdk9' does not match package name 'openjdk'
openjdk @ 10.46input-labels

Identify input labels that do not match package names

label 'openjdk9:jdk' does not match package name 'openjdk:jdk'
openjdk @ 10.46input-labels

Identify input labels that do not match package names

label 'make@4.2' does not match package name 'make'
openjdk @ 10.46input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
openjdk @ 10.46input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
openfoam @ 4.1input-labels

Identify input labels that do not match package names

label 'scotch' does not match package name 'pt-scotch32'
openctm @ 1.0.3.603input-labels

Identify input labels that do not match package names

label 'glut' does not match package name 'freeglut'
openctm @ 1.0.3.603input-labels

Identify input labels that do not match package names

label 'gtk' does not match package name 'gtk+'
opencog @ 0.1.4-1.ceac905input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-minimal'
opencog @ 0.1.4-1.ceac905input-labels

Identify input labels that do not match package names

label 'libuuid' does not match package name 'util-linux:lib'
opencl-clhpp @ 2023.02.06input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
omega @ 1.4.19input-labels

Identify input labels that do not match package names

label 'pcre' does not match package name 'pcre:bin'
ola @ 0.10.8input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
obconf @ 2.0.4input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
obconf @ 2.0.4input-labels

Identify input labels that do not match package names

label 'gtk+-2' does not match package name 'gtk+'
ntk @ 1.3.1000input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
ntk @ 1.3.1000input-labels

Identify input labels that do not match package names

label 'waf' does not match package name 'python-waf'
nsis-x86_64 @ 3.08input-labels

Identify input labels that do not match package names

label 'xgcc' does not match package name 'gcc-cross-x86_64-w64-mingw32'
nsis-x86_64 @ 3.08input-labels

Identify input labels that do not match package names

label 'xbinutils' does not match package name 'binutils-cross-x86_64-w64-mingw32'
nsis-x86_64 @ 3.08input-labels

Identify input labels that do not match package names

label 'mingw-w64' does not match package name 'mingw-w64-x86_64'
nsis-i686 @ 3.08input-labels

Identify input labels that do not match package names

label 'xgcc' does not match package name 'gcc-cross-i686-w64-mingw32'
nsis-i686 @ 3.08input-labels

Identify input labels that do not match package names

label 'xbinutils' does not match package name 'binutils-cross-i686-w64-mingw32'
nsis-i686 @ 3.08input-labels

Identify input labels that do not match package names

label 'mingw-w64' does not match package name 'mingw-w64-i686'
nomacs @ 3.16.224input-labels

Identify input labels that do not match package names

label 'qtlinguist' does not match package name 'qttools'
nomacs @ 3.16.224input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
nomacs @ 3.16.224input-labels

Identify input labels that do not match package names

label 'qtsvg-5' does not match package name 'qtsvg'
node @ 18.16.0input-labels

Identify input labels that do not match package names

label 'nghttp2' does not match package name 'nghttp2:lib'
node @ 18.16.0input-labels

Identify input labels that do not match package names

label 'nghttp2' does not match package name 'nghttp2:lib'
node @ 10.24.1input-labels

Identify input labels that do not match package names

label 'nghttp2' does not match package name 'nghttp2:lib'
node @ 10.24.1input-labels

Identify input labels that do not match package names

label 'nghttp2' does not match package name 'nghttp2:lib'
nimf @ 1.2input-labels

Identify input labels that do not match package names

label 'gtk+' does not match package name 'gtk+:bin'
nilfs-utils @ 2.2.9input-labels

Identify input labels that do not match package names

label 'util-linux' does not match package name 'util-linux:lib'
newsboat @ 2.31input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
newsboat @ 2.31input-labels

Identify input labels that do not match package names

label 'asciidoctor' does not match package name 'ruby-asciidoctor'
newsboat @ 2.13input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
netpbm @ 10.78.3input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
netpbm @ 10.78.3input-labels

Identify input labels that do not match package names

label 'libjpeg' does not match package name 'libjpeg-turbo'
nestopia-ue @ 1.51.1input-labels

Identify input labels that do not match package names

label 'fontconfig' does not match package name 'fontconfig-minimal'
nemo @ 5.6.5input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
nemo @ 5.6.5input-labels

Identify input labels that do not match package names

label 'gtk+' does not match package name 'gtk+:bin'
neko @ 2.3.0input-labels

Identify input labels that do not match package names

label 'mariadb' does not match package name 'mariadb:dev'
neko @ 2.3.0input-labels

Identify input labels that do not match package names

label 'mariadb' does not match package name 'mariadb:lib'
nagios @ 4.4.6input-labels

Identify input labels that do not match package names

label 'libpng-apng' does not match package name 'libpng'
musl-cross @ 0.1-3.a8a6649input-labels

Identify input labels that do not match package names

label 'config.sub' does not match package name 'automake'
mswebrtc @ 1.1.1-0.946ca70input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python-wrapper'
msamr @ 1.1.3-0.5ab5c09input-labels

Identify input labels that do not match package names

label 'opencoreamr' does not match package name 'opencore-amr'
msamr @ 1.1.3-0.5ab5c09input-labels

Identify input labels that do not match package names

label 'voamrwbenc' does not match package name 'vo-amrwbenc'
mrg @ 0.1.4input-labels

Identify input labels that do not match package names

label 'alsa' does not match package name 'alsa-lib'
mrg @ 0.1.4input-labels

Identify input labels that do not match package names

label 'x11' does not match package name 'libx11'
mpg321 @ 0.3.2input-labels

Identify input labels that do not match package names

label 'libao' does not match package name 'ao'
mpc123 @ 0.2.4input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
mpc123 @ 0.2.4input-labels

Identify input labels that do not match package names

label 'libao' does not match package name 'ao'
mpb @ 1.8.0input-labels

Identify input labels that do not match package names

label 'fortran' does not match package name 'gfortran'
mpb @ 1.8.0input-labels

Identify input labels that do not match package names

label 'libctl' does not match package name 'guile-libctl'
mozjs @ 91.13.0input-labels

Identify input labels that do not match package names

label 'rust' does not match package name 'rust:cargo'
mozjs @ 78.15.0input-labels

Identify input labels that do not match package names

label 'rust' does not match package name 'rust:cargo'
mozjs @ 102.2.0input-labels

Identify input labels that do not match package names

label 'rust' does not match package name 'rust:cargo'
mousepad @ 0.6.1input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
mold @ 1.10.1input-labels

Identify input labels that do not match package names

label 'zstd' does not match package name 'zstd:lib'
modem-manager @ 1.18.12input-labels

Identify input labels that do not match package names

label 'glib' does not match package name 'glib:bin'
mit-scheme @ 11.2input-labels

Identify input labels that do not match package names

label 'texlive' does not match package name 'texlive-updmap.cfg'
miniupnpc @ 2.1.20191224input-labels

Identify input labels that do not match package names

label 'python' does not match package name 'python2'
minidjvu @ 0.8input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
minicom @ 2.8input-labels

Identify input labels that do not match package names

label 'gettext' does not match package name 'gettext-minimal'
mingw-w64-x86_64-winpthreads @ 10.0.0input-labels

Identify input labels that do not match package names

label 'xgcc-core' does not match package name 'gcc-cross-sans-libc-x86_64-w64-mingw32'
mingw-w64-x86_64-winpthreads @ 10.0.0input-labels

Identify input labels that do not match package names

label 'xbinutils' does not match package name 'binutils-cross-x86_64-w64-mingw32'
mingw-w64-x86_64-winpthreads @ 10.0.0input-labels

Identify input labels that do not match package names

label 'xlibc' does not match package name 'mingw-w64-x86_64'
mingw-w64-x86_64 @ 10.0.0input-labels

Identify input labels that do not match package names

label 'xgcc-core' does not match package name 'gcc-cross-sans-libc-x86_64-w64-mingw32'
mingw-w64-x86_64 @ 10.0.0input-labels

Iden