Bug 2036333 - Please branch and build ncdu in epel9
Summary: Please branch and build ncdu in epel9
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: ncdu
Version: epel9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Richard Fearn
QA Contact: Fedora Extras Quality Assurance
: 2070432 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2021-12-31 09:42 UTC by Alessio
Modified: 2022-03-31 10:23 UTC (History)
3 users (show)

Fixed In Version: ncdu-1.16-2.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-01-13 01:44:17 UTC
Type: Bug

Attachments (Terms of Use)

Description Alessio 2021-12-31 09:42:43 UTC
Please branch and build ncdu in epel9.

If you do not wish to maintain <package> in epel9,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package.

Comment 1 Richard Fearn 2021-12-31 14:43:46 UTC
epel9 branch requested: https://pagure.io/releng/fedora-scm-requests/issue/40346

Comment 2 Richard Fearn 2022-01-04 18:40:26 UTC
epel9 build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1872818

Comment 3 Fedora Update System 2022-01-04 18:42:12 UTC
FEDORA-EPEL-2022-896a89052d has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-896a89052d

Comment 4 Fedora Update System 2022-01-05 02:15:45 UTC
FEDORA-EPEL-2022-896a89052d 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-896a89052d

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

Comment 5 Fedora Update System 2022-01-13 01:44:17 UTC
FEDORA-EPEL-2022-896a89052d has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Richard Fearn 2022-03-31 10:23:48 UTC
*** Bug 2070432 has been marked as a duplicate of this bug. ***

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