============================ rpmlint session starts ============================
rpmlint: 2.6.1
configuration:
    /opt/testing/lib/python3.11/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: 3

npkg.noarch: E: script-without-shebang /usr/share/npkg/scripts/npkg-mgmt-json-statistics.rb
This text file has executable bits set or is located in a path dedicated for
executables, but lacks a shebang and cannot thus be executed. If the file is
meant to be an executable script, add the shebang, otherwise remove the
executable bits or move the file elsewhere.

nodejs-packaging.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.

nodejs-packaging.noarch: E: env-script-interpreter (Badness: 9) /usr/lib/rpm/nodejs-check.rb /usr/bin/env ruby
nodejs-packaging.noarch: E: env-script-interpreter (Badness: 9) /usr/lib/rpm/nodejs-fixdep.rb /usr/bin/env ruby
nodejs-packaging.noarch: E: env-script-interpreter (Badness: 9) /usr/lib/rpm/nodejs-symlink-deps.rb /usr/bin/env ruby
nodejs-packaging.noarch: E: env-script-interpreter (Badness: 9) /usr/lib/rpm/nodejs.prov /usr/bin/env ruby
nodejs-packaging.noarch: E: env-script-interpreter (Badness: 9) /usr/lib/rpm/nodejs.rb /usr/bin/env ruby
npkg.noarch: E: env-script-interpreter (Badness: 9) /usr/share/npkg/npkg /usr/bin/env ruby
npkg.noarch: E: env-script-interpreter (Badness: 9) /usr/share/npkg/scripts/npkg-mgmt-json2pkgtxt.rb /usr/bin/env ruby
npkg.noarch: E: env-script-interpreter (Badness: 9) /usr/share/npkg/scripts/npkg-mgmt-merge.rb /usr/bin/env ruby
npkg.noarch: E: env-script-interpreter (Badness: 9) /usr/share/npkg/scripts/npkg-mgmt-pkg-batchrm.rb /usr/bin/env ruby
npkg.noarch: E: env-script-interpreter (Badness: 9) /usr/share/npkg/scripts/npkg-test-random-pick.rb /usr/bin/env ruby
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.

nodejs-packaging.noarch: E: devel-dependency nodejs-devel
Your package has a dependency on a devel package but it's not a devel package
itself.

Check time report (>1% & >0.1s):
    Check                            Duration (in s)   Fraction (in %)  Checked files
    TOTAL                                        0.1             100.0               

 3 packages and 0 specfiles checked; 12 errors, 1 warnings, 9 filtered, 92 badness; has taken 0.1 s