Bug 2052640 - Branch and build gupnp-igd for epel9
Summary: Branch and build gupnp-igd for epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gupnp-igd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Davide Cavalca
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2052638
Blocks: EPELPackagersSIG 2033520 2044092 2101042
TreeView+ depends on / blocked
 
Reported: 2022-02-09 17:05 UTC by Davide Cavalca
Modified: 2022-11-19 03:11 UTC (History)
5 users (show)

Fixed In Version: gupnp-igd-1.2.0-6.el9
Clone Of:
Environment:
Last Closed: 2022-11-19 03:11:20 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Davide Cavalca 2022-02-09 17:05:09 UTC
Comment 1 Fedora Admin user for bugzilla script actions 2022-02-10 00:06:14 UTC 
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Comment 2 Mattias Ellert 2022-11-18 10:49:25 UTC 
The title of this bugzilla issue also asks for a build in EPEL8. This is not necessary since the package exists in RHEL 8 and derivatives:

================================================================================
 Package               Architecture Version              Repository        Size
================================================================================
Installing:
 gupnp-igd             x86_64       0.2.5-4.el8          appstream         36 k
 gupnp-igd-devel       x86_64       0.2.5-4.el8          powertools        28 k

A build for EPEL 9 is needed though.
Comment 3 Fedora Update System 2022-11-18 15:09:13 UTC 
FEDORA-EPEL-2022-ed712a5b26 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-ed712a5b26
Comment 4 Fedora Update System 2022-11-19 03:11:20 UTC 
FEDORA-EPEL-2022-ed712a5b26 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.