Please Branch and build gupnp-igd in epel10.
Will you be able to branch and build gupnp-igd in epel10?
(In reply to Mike Link from comment #1) > Will you be able to branch and build gupnp-igd in epel10? gupnp-igd is waiting for gupnp (bug #2325216). gupnp is waiting for gssdp (bug #2325219). You need to prod the maintainer of those packages first.
With gupnp now available, gupnp-igd is buildable for both epel10 and epel10.0 branches. Successful scratch builds: epel10.0: https://koji.fedoraproject.org/koji/taskinfo?taskID=134338775 epel10: https://koji.fedoraproject.org/koji/taskinfo?taskID=134338738
I can do the builds if given permission. Adding need-info from kalev (package admin) due to lack of response from main package admin.
Sure, I just added you. Thanks!
FEDORA-EPEL-2025-721297734c (gupnp-igd-1.6.0-1.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-721297734c
FEDORA-EPEL-2025-5b7ba2a445 (gupnp-igd-1.6.0-1.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-5b7ba2a445
FEDORA-EPEL-2025-5b7ba2a445 has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-5b7ba2a445 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-721297734c has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-721297734c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-5b7ba2a445 (gupnp-igd-1.6.0-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-721297734c (gupnp-igd-1.6.0-1.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report.