Bug 771577

Summary: No mantis package for EL6
Product: [Fedora] Fedora EPEL Reporter: Jan ONDREJ <ondrejj>
Component: mantisAssignee: Orphan Owner <extras-orphan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: el6CC: david, extras-orphan, giallu, michel, ondrejj, ubellavance
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 771575 Environment:
Last Closed: 2020-11-30 14:58:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 771575    
Bug Blocks:    

Description Jan ONDREJ 2012-01-04 08:01:48 UTC
+++ This bug was initially created as a clone of Bug #771575 +++

Description of problem:
In RHEL6/CentOS6 there is no mantis package. Same problem as for php-nusoap, which is required in Fedora's mantis package.

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

How reproducible:
always

Steps to Reproduce:
1. yum install mantis
  
Actual results:
bind: Address already in use
channel_setup_fwd_listener: cannot listen to port: 3307
Could not request local forwarding.
Last login: Wed Jan  4 08:36:05 2012 from work.salstar.sk
[root@pnext-dev ~]# yum install php-nusoap
Loaded plugins: downloadonly, fastestmirror
Loading mirror speeds from cached hostfile
 * base: ftp.energotel.sk
 * epel: mirror.karneval.cz
 * extras: ftp.energotel.sk
 * updates: ftp.energotel.sk
Setting up Install Process
No package mantis available.
Error: Nothing to do

Expected results:
installed php-nusoap

Additional info:
You need only to recompile and make a new update. No need to request new branch.

Comment 1 Michel Alexandre Salim 2014-02-13 03:49:31 UTC
Adding this to my to-do list - I'm planning on deploying Mantis on EL6 systems. Jan, are you interested in co-maintaining?

Comment 2 Jan ONDREJ 2014-02-13 11:21:18 UTC
(In reply to Michel Alexandre Salim from comment #1)
> Adding this to my to-do list - I'm planning on deploying Mantis on EL6

Thank you. And please add EL7 too.

> systems. Jan, are you interested in co-maintaining?

No.

Comment 3 Ugo Bellavance 2016-04-11 17:11:59 UTC
Any plan on porting this package to RHEL7? If not, RHEL6?

Thanks,

Comment 4 Ugo Bellavance 2016-04-11 17:42:00 UTC
I know that mantis may be old, but it works for us and RHEL5 will be EOL in less than one year so I'd like to be able to move it to a RHEL server.

Comment 5 Ben Cotton 2020-11-05 16:51:38 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 6 Ben Cotton 2020-11-05 16:54:18 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.

Comment 7 Ben Cotton 2020-11-30 14:58:44 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 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
EPEL 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.