Bug 250829 - Csound packages in Fedora repository are getting outdated
Summary: Csound packages in Fedora repository are getting outdated
Alias: None
Product: Fedora
Classification: Fedora
Component: csound
Version: 7
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-08-03 20:29 UTC by Hector Centeno
Modified: 2008-06-17 02:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-06-17 02:05:44 UTC

Attachments (Terms of Use)

Description Hector Centeno 2007-08-03 20:29:10 UTC
Description of problem: The current version of Csound in the Fedora repository
is 5.03. Current upstream version is 5.06 (and maybe 5.07 soon to come) which
contains several improvements (new opcodes) and bug fixes.

Comment 1 Hector Centeno 2008-01-07 16:41:18 UTC
Version 5.07 is out now and Fedora's package is still 5.03. I would like to
become co-maintainer of this package, is that possible?

Comment 2 Dan Williams 2008-01-07 18:44:55 UTC
Sure!  If you wouldn't mind requesting the necessary ACLs from the fedora
package DB, I'll gladly add you.  Either that, or I could just open it up to
anyone with CVS access.

Comment 3 Hector Centeno 2008-01-07 19:52:50 UTC
(In reply to comment #2)
> Sure!  If you wouldn't mind requesting the necessary ACLs from the fedora
> package DB, I'll gladly add you.  Either that, or I could just open it up to
> anyone with CVS access.

Thanks! I'm not currently a Fedora packager. How do I request the ACLs?

Comment 4 Dan Williams 2008-01-07 21:00:37 UTC
First, you get to join the Fedora Project as a developer.  The following wiki
page has more information:


It looks long and complicated, but it's really not a long process since you're
not creating a _new_ package, you'd like to work on an existing one.  But it
wouldn't hurt if you tried to package up the latest csound and then submit it
like you're reviewing it just so people can get a sample of your work.

Comment 5 Bug Zapper 2008-05-14 13:51:47 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

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 Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 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 please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2008-06-17 02:05:42 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 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.

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

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