============================ rpmlint session starts ============================
rpmlint: 2.7.0
configuration:
    /opt/testing/lib64/python3.13/rpmlint/configdefaults.toml
    /opt/testing/share/rpmlint/cron-whitelist.toml
    /opt/testing/share/rpmlint/dbus-services.toml
    /opt/testing/share/rpmlint/device-files-whitelist.toml
    /opt/testing/share/rpmlint/licenses.toml
    /opt/testing/share/rpmlint/opensuse.toml
    /opt/testing/share/rpmlint/pam-modules.toml
    /opt/testing/share/rpmlint/permissions-whitelist.toml
    /opt/testing/share/rpmlint/pie-executables.toml
    /opt/testing/share/rpmlint/polkit-rules-whitelist.toml
    /opt/testing/share/rpmlint/scoring.toml
    /opt/testing/share/rpmlint/security.toml
    /opt/testing/share/rpmlint/sudoers-whitelist.toml
    /opt/testing/share/rpmlint/sysctl-whitelist.toml
    /opt/testing/share/rpmlint/systemd-tmpfiles.toml
    /opt/testing/share/rpmlint/users-groups.toml
    /opt/testing/share/rpmlint/world-writable-whitelist.toml
    /opt/testing/share/rpmlint/zypper-plugins.toml
    /etc/xdg/rpmlint/scoring-strict.override.toml
checks: 41, packages: 12

PackageKit.x86_64: W: zero-perms-ghost Suggestion: "%ghost %attr(0755,root,root) /var/cache/PackageKit"
PackageKit.x86_64: W: zero-perms-ghost Suggestion: "%ghost %attr(-,-,-) /var/lib/PackageKit/transactions.db"
Your package contains a file with no permissions. This is usually an error
because the file won't be accessible by any user. You should check the file
permissions and ensure that are correct or fix it using "%attr" macro in
%files section.
http://ftp.rpm.org/max-rpm/s1-rpm-anywhere-specifying-file-attributes.html

PackageKit.x86_64: W: tmpfile-not-in-filelist /var/lib/PackageKit/
Please add the specified file to your %files section as %ghost so users can
easily query who created the file, it gets uninstalled on package removal and
finally other rpmlint checks see it.

PackageKit.x86_64: W: post-without-tmpfile-creation /usr/lib/tmpfiles.d/PackageKit.conf
Please use the %tmpfiles_create macro in %post for each of your tmpfiles.d
files if you expect this file or directory to be available after package
installation (and before reboot).

PackageKit.x86_64: W: obsolete-not-provided PackageKit-browser-plugin
PackageKit.x86_64: W: obsolete-not-provided PackageKit-doc
PackageKit.x86_64: W: obsolete-not-provided PackageKit-gtk-module
PackageKit.x86_64: W: obsolete-not-provided ruck
If a package is obsoleted by a compatible replacement, the obsoleted package
should also be provided in order to not cause unnecessary dependency breakage.
If the obsoleting package is not a compatible replacement for the old one,
leave out the Provides.

PackageKit.x86_64: E: non-executable-script /usr/share/PackageKit/packagekit-background.sh 644 /bin/bash
PackageKit.x86_64: E: non-executable-script /usr/share/PackageKit/pk-upgrade-distro.sh 644 /bin/sh
This text file contains a shebang or is located in a path dedicated for
executables, but lacks the executable bits and cannot thus be executed. If the
file is meant to be an executable script, add the executable bits, otherwise
remove the shebang or move the file elsewhere.

PackageKit-branding-upstream.noarch: W: non-conffile-in-etc /etc/PackageKit/Vendor.conf
A non-executable file in your package is being installed in /etc, but is not a
configuration file. All non-executable files in /etc should be configuration
files. Mark the file as %config in the spec file.

PackageKit.spec: W: no-%check-section
The spec file does not contain an %check section. Please check if the package
has a testsuite and what it takes to enable the testsuite as part of the
package build. If it is not possible to run it in the build environment
(OBS/koji) or no testsuite exists, then please ignore this warning. You should
not insert an empty %check section.

PackageKit-devel.x86_64: E: env-script-interpreter (Badness: 9) /usr/share/PackageKit/helpers/test_spawn/search-name.sh /usr/bin/env bash
This script uses 'env' as an interpreter. For the rpm runtime dependency
detection to work, the shebang #!/usr/bin/env <interpreter>  needs to be
patched into #!/usr/bin/<interpreter>  otherwise the package dependency
generator merely adds a dependency on /usr/bin/env rather than the actual
interpreter /usr/bin/<interpreter>.  Alternatively, if the file should not be
executed, then ensure that it is not marked as executable or don't install it
in a path that is reserved for executables.

Check time report (>1% & >0.1s):
    Check                            Duration (in s)   Fraction (in %)  Checked files
    ExtractRpm                                   0.5              40.4               
    BinariesCheck                                0.2              16.2               
    BashismsCheck                                0.1              11.3               
    SignatureCheck                               0.1               9.5               
    TOTAL                                        1.2             100.0               

 12 packages and 0 specfiles checked; 3 errors, 10 warnings, 74 filtered, 11 badness; has taken 1.2 s