Bug 856937
Summary: | Ganglia new version | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Christopher Meng <i> |
Component: | ganglia | Assignee: | Kostas Georgiou <k.georgiou> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | el6 | CC: | ggillies, joshua, k.georgiou |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-22 03:31:56 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
Christopher Meng
2012-09-13 07:46:05 UTC
See BZ # 868424 ... already exists in Fedora 18 so it should be easy. (In reply to comment #1) > See BZ # 868424 ... already exists in Fedora 18 so it should be easy. F18 != EPEL Not saying that is, but the packages are there and ripe for the taking. I know it's "there",but this doesn't mean I can yum install ganglia" and get that version. I still can get old 3.1.7 not this one. Again, I'm not assuming that one is the same as the other. I include this note to the package owner of the EPEL side; the hard work is already finished due to the Fedora side having gotten to the update first. Well, I've checked the bodhi and found that ganglia for f18 has been pushed since 1/8. Today is 1/29 in UTC+8, well, I don't think ganglia is a hard-to-maintain one. But nothing happened, in fact I'll wait for this update in EPEL, not f18, because f18 one is useless for me. I can use srpm to rebuild, but I don't want to do this. It seems the epel maintainer of this package is dead. Quoting from the EPEL policy: The packages in the repository should, if possible, be maintained in similar ways to the Enterprise Packages they were built against. In other words: have a mostly stable set of packages that normally does not change at all and only changes if there are good reasons for changes. This is the spirit of a stable enterprise environment. The changes that cant be avoided get routed into different release trees. Only updates that fix important bugs (say: data-corruption, security problems, really annoying bugs) go to a testing branch for a short time period and then are pushed to the stable branch; those people that sign and push the EPEL packages to the public repo will skim over the list of updated packages for the stable repo to make sure that sure the goal "only important updates for the stable branch" is fulfilled. I can provide a more recent package under repos.fedorapeople.org I guess if demand is high but I can not change the existing 3.1.7 version unless there is a very good reason. That makes sense, thank you for the explanation. I'd love to see the newer packages available for RHEL6 though, if you've a mind to put them up somewhere. Thank you! |