Hide Forgot
Description of problem: The autoconf-archive RPM package is missing from RHEL-6, although it seem to have been there (and even in EPEL for RHEL5). Package is present in EPEL for RHEL7 and recent Fedora versions. Version-Release number of selected component (if applicable): How reproducible: Every time. Steps to Reproduce: 1. yum makecache 2. yum search autoconf-archive Actual results: No RPM found. Expected results: RPM should be present. Additional info: autoconf-archive is a set of autoconf macros which are essential for software developers, e.g., AX_PTHREAD (why is this not in glibc-devel is another mystery). Without a macro like this it is impossible to autoconf any package that uses libptheard (i.e. most of the modern networked services or applications). The RPM and SRPM lists do not show this RPM also: https://dl.fedoraproject.org/pub/epel/6/SRPMS/repoview/letter_a.group.html The autoconf-archive is present for RHEL7 and recent fedora versions (at least 21-23) and it seemed to have been present for RHEL5 and 6 - e.g., see #1122747 .
autoconf-archive for EPEL 6 and 5 was orphaned and retired in late 2014: http://pkgs.fedoraproject.org/cgit/rpms/autoconf-archive.git/commit/?h=el6 If you want it for older EPEL than 7, you will need to find a maintainer for those branches, or become one yourself.
(In reply to David King from comment #1) > autoconf-archive for EPEL 6 and 5 was orphaned and retired in late 2014: > > http://pkgs.fedoraproject.org/cgit/rpms/autoconf-archive.git/commit/?h=el6 > > If you want it for older EPEL than 7, you will need to find a maintainer for > those branches, or become one yourself. Hi Is there any equivalent of autoconf-archive in Redhat7? I got missing to find some MACROS which autoconf-archive contains.
oh, may I ask why it's orphaned? Thanks!
(In reply to Fan Du from comment #3) > oh, may I ask why it's orphaned? > Thanks! I believe nobody volunteered in EPEL to continue with packaging. I believe actual maintainers would be OK if you offered a help here with packaging?
Seeing that EL6 is in production 3 phase (only critical security patches), I have mixed thoughts about reintroducing a package. That being said, the current Fedora SRPM does successfully build on EL6. Given the low update cycle, it might only be updated a few times before EL6 goes EOL.
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.
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.
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.