============================ 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: 2

tetrinet-server.spec:65: W: shared-dir-glob-in-files %{_bindir}/*
The %files section contains "%{_bindir}/*", "%{_datadir}/*", "%{_docdir}/*",
"%{_includedir}/*" or "%{_mandir}/*".  These can lead to packagers not
noticing when upstream adds new and possibly conflicting files in these
directories. Therefore, files in these directories should be explicitely
listed like "%{_bindir}/foobar" or "%{_includedir}/foobar.h".

tetrinet-server.spec:51: E: rpm-buildroot-usage %build INCLUDE_DIR=$RPM_BUILD_ROOT%{_includedir} \
tetrinet-server.spec:52: E: rpm-buildroot-usage %build LIB_DIR=$RPM_BUILD_ROOT%{_libdir} \
$RPM_BUILD_ROOT or %{buildroot} must not be touched during %build or %prep
stage, as it will break short circuit builds and will not persist to %install
stage in a normal build, leading to unexpected package build behavior.

tetrinet-server.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.

tetrinet-server.x86_64: W: binary-or-shlib-calls-gethostbyname /usr/bin/tetrinetx
The binary calls gethostbyname. Please port the code to use getaddrinfo.

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

 2 packages and 0 specfiles checked; 2 errors, 3 warnings, 6 filtered, 2 badness; has taken 0.1 s