Bug 297911

Summary:	Request for updated package
Product:	[Fedora] Fedora	Reporter:	Mark Knoop <mark>
Component:	lilypond	Assignee:	Quentin Spencer <qspencer>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	7
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-09-20 18:37:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mark Knoop 2007-09-20 11:06:00 UTC

Lilypond has not been updated in F7 since March (2.10.20-1) - prior to this
there were regular updates as new versions were released upstream (thank you).
Upstream are now at 2.10.33 with many bugfixes. I see that 2.10.29 is in
development - is there a reason why this hasn't been pushed to f7?

Comment 1 Quentin Spencer 2007-09-20 18:37:32 UTC

There were a lot of changes in how Fedora is managed with the release of Fedora
7. Now that I've figured out now to navigate the new update system, I think I
can go back to doing periodic updates now. I've now built a 2.9.33 release in
development and for F7, but it may take a couple of days to get it into the F7
repositories.

Comment 2 Mark Knoop 2007-09-21 09:48:15 UTC

That's great, thanks very much. (I didn't want to hassle you, just wondered if
the package was still being maintained.)