Bug 2368725 - Git-annex on EPEL
Summary: Git-annex on EPEL
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: git-annex
Version: epel9
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1972432
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-27 10:57 UTC by Jens Petersen
Modified: 2025-05-27 10:58 UTC (History)
6 users (show)

Fixed In Version:
Clone Of: 1972432
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jens Petersen 2025-05-27 10:57:18 UTC
+++ This bug was initially created as a clone of Bug #1972432 +++

Description of problem: Looks like git-annex was branched for EL8 but the build was not triggered. 

Version-Release number of selected component (if applicable):

git-annex-8.20210428-1

Actual results:

Git-annex is not present in EPEL-8.

Expected results:

Git-annex to be present in EPEL-8.

--- Additional comment from Ben Boeckel on 2021-08-22 19:58:27 +08 ---



--- Additional comment from Odilon Sousa on 2021-10-27 04:55:57 +08 ---

Hi fedora.net there's anything that I can do to help with this build for EPEL-8?

--- Additional comment from Ben Boeckel on 2021-11-05 22:04:22 +08 ---

I don't usually do EPEL work. I think @juhp would know better what the state of the Haskell stack overall in EPEL is.

--- Additional comment from Jens Petersen on 2021-12-20 12:34:14 +08 ---

(In reply to Odilon Sousa from comment #2)
> Hi fedora.net there's anything that I can do to help with this
> build for EPEL-8?

I still want to get to this soon, but if you want to help you could make a copr repo say or something like that.

--- Additional comment from Jens Petersen on 2024-11-12 20:02:17 +08 ---

Moving to epel9, which is also missing.

Comment 1 Jens Petersen 2025-05-27 10:58:35 UTC
EPEL 10 was done recently (bug 1972432), but I still intend to build for epel 9.

Tracking that here.


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