Upgrade gupnp to 1.6.9-1

[kevin-b-lockwood]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Dependent on #10790

Upgrade gupnp to 1.6.9

Change Log

• Basic version bump for gupnp, dependent on gssndp update.
• Exclude manpage if docs are not to be generated.
• Verify license

Does this affect the toolchain?

NO

Test Methodology

• Local build

[kgodara912]

Good for next stage: buddy build pipeline.

[kgodara912]

Buddy build. Package builds fine but installation couldn't be verified.

[kevin-b-lockwood]

@kgodara912 What do I need to do to get this PR moving along?

[kgodara912]

@kevin-b-lockwood, please check the test failures in the pipeline mentioned above. You may also run and check on your local setup as well.

PKGTEST:: scan_pkg_test_logs:: Processing : gupnp-1.6.7-1.azl3.src.rpm.test.log
PKGTEST:: _get_pkg_details:: Package: gupnp  Version: 1.6.7-1.azl3
PKGTEST:: _check_test_status:: time="2025-05-12T17:18:00Z" level=debug msg="====== CHECK START gupnp"
PKGTEST:: _check_test_status:: time="2025-05-12T17:18:01Z" level=debug msg="====== CHECK DONE gupnp. EXIT STATUS 5"
PKGTEST:: _get_test_status:: STATUS => 5
PKGTEST:: _analyze_pkg_test_log:: status: Fail start time: 1747070280.0 end time: 1747070281.0
PKGTEST:: scan_pkg_test_logs:: pkgname: gupnp version: 1.6.7-1.azl3 test status: Fail duration: 1.0

PKGTEST:: <module>:: Some test(s) failed
+ RESULT=1

[kevin-b-lockwood]

@kgodara912 I bumped the version to current upstream (This PR had fallen behind) and checked the build failures, they are only because we're missing part of the testing prerequisites. We've never used these prereqs that I know of, and fedora doesn't appear to consider them either. Failed tests as follows:

I can try to track down appropriate GSettings schemas but I don't know if that's necessary. Please advise.

[sandeepkarambelkar]

Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=921375&view=results

[sandeepkarambelkar]

@kevin-b-lockwood There are test failures in the buddy build. Can you check them?