Bug 2322613 - Branch and build libnice in epel10
Summary: Branch and build libnice in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: libnice
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Sekletar
QA Contact:
URL:
Whiteboard:
Depends On: 2325213
Blocks: EPEL10Tracker
TreeView+ depends on / blocked
 
Reported: 2024-10-29 23:41 UTC by Mattias Ellert
Modified: 2025-07-10 16:27 UTC (History)
7 users (show)

Fixed In Version: libnice-0.1.22-7.el10_1 libnice-0.1.22-7.el10_0
Clone Of:
Environment:
Last Closed: 2025-07-10 14:53:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mattias Ellert 2024-10-29 23:41:08 UTC
Please branch and build libnice in epel10.

Comment 1 Jonathan Wright 2024-11-11 14:40:44 UTC
No matching package to install: 'gupnp-igd-devel >= 0.1.2'

Comment 2 Mattias Ellert 2025-07-03 20:07:07 UTC
All dependencies now available in both epel10 and epel10.0 branches.

Successful scratch builds:

epel10.0: https://koji.fedoraproject.org/koji/taskinfo?taskID=134586224
epel10:   https://koji.fedoraproject.org/koji/taskinfo?taskID=134585909

Comment 3 Stefan Becker 2025-07-04 16:06:12 UTC
FYI: login to pagure seems still to be broken after data center move,....

...hence I can't login to renew my pagure token, ...

...hence I can't request branch "epel10".

This will have to wait until all infra problems are solved.

Comment 4 Stefan Becker 2025-07-04 16:18:43 UTC
(In reply to Stefan Becker from comment #3)
> FYI: login to pagure seems still to be broken after data center move,....

Seems it automagically fixed itself suddenly: https://pagure.io/releng/fedora-scm-requests/issue/77139

"epel10" branch rebased to rawhide and pushed,

Build task: https://koji.fedoraproject.org/koji/taskinfo?taskID=134597002

I have no clue how to handle "epel10.0".

Comment 5 Fedora Update System 2025-07-04 16:32:59 UTC
FEDORA-EPEL-2025-f6401017ab (libnice-0.1.22-7.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f6401017ab

Comment 6 Mattias Ellert 2025-07-04 16:40:08 UTC
(In reply to Stefan Becker from comment #4)
> I have no clue how to handle "epel10.0".

fedpkg request-branch epel10.0

and then the same as for any other new branch.

Comment 7 Fedora Update System 2025-07-04 17:07:06 UTC
FEDORA-EPEL-2025-a90a927f58 (libnice-0.1.22-7.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a90a927f58

Comment 8 Fedora Update System 2025-07-05 01:11:41 UTC
FEDORA-EPEL-2025-f6401017ab 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-f6401017ab

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2025-07-05 01:52:11 UTC
FEDORA-EPEL-2025-a90a927f58 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-a90a927f58

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2025-07-10 14:53:36 UTC
FEDORA-EPEL-2025-f6401017ab (libnice-0.1.22-7.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.

Comment 11 Fedora Update System 2025-07-10 16:27:16 UTC
FEDORA-EPEL-2025-a90a927f58 (libnice-0.1.22-7.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.


Note You need to log in before you can comment on or make changes to this bug.