hibiscus.ppc64le: W: class-path-in-manifest /usr/lib/jameica/plugins/hibiscus/hibiscus.jar
The META-INF/MANIFEST.MF file in the jar contains a hardcoded Class-Path.
These entries do not work with older Java versions and even if they do work,
they are inflexible and usually cause nasty surprises.

hibiscus.ppc64le: W: devel-dependency pcsc-towitoko-devel
Your package has a dependency on a devel package but it's not a devel package
itself.

hibiscus.ppc64le: W: empty-%post
hibiscus.ppc64le: W: empty-%postun
hibiscus.ppc64le: W: no-soname /usr/lib/jameica/plugins/hibiscus/lib/libhbci4java-card-freebsd-64.so
hibiscus.ppc64le: W: no-soname /usr/lib/jameica/plugins/hibiscus/lib/libhbci4java-card-linux-32.so
hibiscus.ppc64le: W: no-soname /usr/lib/jameica/plugins/hibiscus/lib/libhbci4java-card-linux-64.so
hibiscus.ppc64le: W: postin-without-ldconfig /usr/lib/jameica/plugins/hibiscus/lib/libhbci4java-card-freebsd-64.so
hibiscus.ppc64le: W: postin-without-ldconfig /usr/lib/jameica/plugins/hibiscus/lib/libhbci4java-card-linux-32.so
hibiscus.ppc64le: W: postin-without-ldconfig /usr/lib/jameica/plugins/hibiscus/lib/libhbci4java-card-linux-64.so
This package contains a library and its %post scriptlet doesn't call ldconfig.

hibiscus.ppc64le: W: postun-without-ldconfig /usr/lib/jameica/plugins/hibiscus/lib/libhbci4java-card-freebsd-64.so
hibiscus.ppc64le: W: postun-without-ldconfig /usr/lib/jameica/plugins/hibiscus/lib/libhbci4java-card-linux-32.so
hibiscus.ppc64le: W: postun-without-ldconfig /usr/lib/jameica/plugins/hibiscus/lib/libhbci4java-card-linux-64.so
This package contains a library and its %postun doesn't call ldconfig.

hibiscus.ppc64le: W: unstripped-binary-or-object /usr/lib/jameica/plugins/hibiscus/lib/libhbci4java-card-freebsd-64.so
hibiscus.ppc64le: W: unstripped-binary-or-object /usr/lib/jameica/plugins/hibiscus/lib/libhbci4java-card-linux-32.so
hibiscus.ppc64le: W: unstripped-binary-or-object /usr/lib/jameica/plugins/hibiscus/lib/libhbci4java-card-linux-64.so
stripping debug info from binaries happens automatically according to global
project settings. So there's normally no need to manually strip binaries. Left
over unstripped binaries could therefore indicate a bug in the automatic
stripping process.

2 packages and 0 specfiles checked; 0 errors, 16 warnings.