Bug 2035375 - Please build zint for EPEL 9
Summary: Please build zint for EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: zint
Version: epel9
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Martin Gieseking
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-23 19:32 UTC by Robert Scheck
Modified: 2022-01-26 17:59 UTC (History)
2 users (show)

Fixed In Version: zint-2.10.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-26 17:59:05 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Robert Scheck 2021-12-23 19:32:37 UTC 
Description of problem:
Please build zint for EPEL 9. It's at least a build-time dependency of the glabels package.

Version-Release number of selected component (if applicable):
zint-2.10.0-1.fc36

Actual results:
No zint in EPEL 9.

Expected results:
zint-2.10.0-1.el9 or better ;-)

Additional info:
Please let me know if you are not interested in maintaining the package on EPEL 9 branch.
Comment 1 Martin Gieseking 2022-01-17 12:52:04 UTC 
Sorry for the late reply. I've requested an epel9 branch for zint and will build it afterwards.
Comment 2 Fedora Update System 2022-01-18 17:40:42 UTC 
FEDORA-EPEL-2022-8d41e3322d has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8d41e3322d
Comment 3 Fedora Update System 2022-01-19 02:55:49 UTC 
FEDORA-EPEL-2022-8d41e3322d has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8d41e3322d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2022-01-26 17:59:05 UTC 
FEDORA-EPEL-2022-8d41e3322d 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.