Bug 2374176 - Please branch and build pangomm for EPEL 10
Summary: Please branch and build pangomm for EPEL 10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pangomm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2374177
Blocks: 2315461
TreeView+ depends on / blocked
 
Reported: 2025-06-21 19:16 UTC by wojnilowicz
Modified: 2025-08-11 17:14 UTC (History)
3 users (show)

Fixed In Version: pangomm-2.46.4-3.el10_1
Clone Of:
Environment:
Last Closed: 2025-08-11 17:14:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description wojnilowicz 2025-06-21 19:16:08 UTC
Could you please branch and build pangomm for EPEL 10 ?
It is needed to build another package.

Comment 1 wojnilowicz 2025-07-11 03:54:45 UTC
Will you be able to branch and build pangomm in epel10?
I would be happy to be a co-maintainer if you do not wish
to build it on epel10 (FAS: wojnilowicz).

Comment 2 Nils Philippsen 2025-07-14 10:44:59 UTC
Hi! Sorry that I didn’t pick up on this earlier.

There are some dependencies still missing which need to be in place before this can be built (not sure this is exhaustive):

- cairomm (#2374177)
- glibmm2.4 (no ticket)

I’ll request the epel10 branch and add you as a co-maintainer to the package.

Comment 3 Nils Philippsen 2025-07-14 10:47:06 UTC
The branch was created: https://pagure.io/releng/fedora-scm-requests/issue/77258

Comment 4 Nils Philippsen 2025-07-14 11:00:20 UTC
I’ve fast-forwarded the epel10 branch to rawhide and made you co-maintainer. NB, I like to keep the Fedora and EPEL branches in sync (pointing to the same tip, fast-forwardable) where it makes sense (same upstream version), and cater for possible differences in the spec file.

Once the dependencies are sorted, we can build the package.

Comment 5 wojnilowicz 2025-07-15 17:29:40 UTC
(In reply to Nils Philippsen from comment #2)
> Hi! Sorry that I didn’t pick up on this earlier.
> 
> There are some dependencies still missing which need to be in place before
> this can be built (not sure this is exhaustive):
> 
> - cairomm (#2374177)
> - glibmm2.4 (no ticket)
> 
> I’ll request the epel10 branch and add you as a co-maintainer to the package.

No problem. No ticket for glibmm2.4, because I'm its co-maintainer. Thanks for your interest.

Comment 6 Fedora Update System 2025-07-23 17:55:15 UTC
FEDORA-EPEL-2025-23fb3915a3 (glibmm2.4-2.66.8-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-23fb3915a3

Comment 7 Fedora Update System 2025-07-24 01:27:10 UTC
FEDORA-EPEL-2025-23fb3915a3 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-23fb3915a3

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

Comment 8 Fedora Update System 2025-08-01 01:40:22 UTC
FEDORA-EPEL-2025-23fb3915a3 (glibmm2.4-2.66.8-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.

Comment 9 Fedora Update System 2025-08-01 15:20:37 UTC
FEDORA-EPEL-2025-6832c43650 (pangomm-2.46.4-3.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-6832c43650

Comment 10 Fedora Update System 2025-08-03 01:41:00 UTC
FEDORA-EPEL-2025-6832c43650 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-6832c43650

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

Comment 11 Fedora Update System 2025-08-11 17:14:34 UTC
FEDORA-EPEL-2025-6832c43650 (pangomm-2.46.4-3.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.


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