Bug 1233215

Summary: leiningen package should be resurected for fedora
Product: [Fedora] Fedora Reporter: ycollet <ycollette.nospam>
Component: leiningenAssignee: Michel Lind <michel>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: admiller, braoru, cadesalaberry, dcleal, extras-qa, jberan, lmacken, martin.hynar, martin, michel, nmvega, tmokros, willb, xingfe123, ycollette.nospam
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1063457 Environment:
Last Closed: 2016-07-19 14:54:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description ycollet 2015-06-18 12:59:24 UTC
+++ This bug was initially created as a clone of Bug #1063457 +++

--- Additional comment from ycollet on 2015-05-29 06:58:22 EDT ---

The package leiningen is not shipped anymore in fedora 21 and 22.
Should I open a new bug report to ask for somebody package leiningen for fedora 22 ?
Or should I retarget this bug report to fedora 22 ?

--- Additional comment from Mat Booth on 2015-06-18 08:51:56 EDT ---

This package was retired: http://pkgs.fedoraproject.org/cgit/leiningen.git/tree/dead.package

--- Additional comment from ycollet on 2015-06-18 08:56:29 EDT ---

Leave this open.
This package was under fedora and has been retired without any good reason.
This package should go back to fedora ...

Comment 1 Fedora End Of Life 2016-07-19 14:54:16 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.