Bug 817229 - Will lilv 0.14.2 be back ported to fedora 16?
Will lilv 0.14.2 be back ported to fedora 16?
Product: Fedora
Classification: Fedora
Component: lilv (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Brendan Jones
Fedora Extras Quality Assurance
: 817230 817231 817233 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2012-04-28 02:53 EDT by Simon Lewis
Modified: 2013-02-13 07:40 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 07:40:00 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Simon Lewis 2012-04-28 02:53:26 EDT

Comment 1 Brendan Jones 2012-04-28 04:16:13 EDT
The lv2core maintainer expressed some desire not to push it any of the new stack further than F17 - (package lv2-1.0.0 obsoletes lv2core=6.0). Currently we are being held up due to an issue in rawhide at the moment with new package sratom which I hope to resolve with upstream soon. 

What's your driving reason here? If there's a good enough case made we can reconsider pushing to F17. 

All of these bugs you have raised are really the same issue (ie we'll push them together), so if you could choose one and mark the others duplicates that would be great.

Bug 814542 (lv2) is the new package required by the new suil/lilv and bug 814916 is where we are currently held up.
Comment 2 Simon Lewis 2012-04-28 06:35:51 EDT
*** Bug 817230 has been marked as a duplicate of this bug. ***
Comment 3 Simon Lewis 2012-04-28 06:36:16 EDT
*** Bug 817231 has been marked as a duplicate of this bug. ***
Comment 4 Simon Lewis 2012-04-28 06:36:45 EDT
*** Bug 817233 has been marked as a duplicate of this bug. ***
Comment 5 Simon Lewis 2012-04-28 06:45:53 EDT
The driving reason is naturally the superb linux DAW "Qtactor" has switched to lilv and slv2 support will no longer be maintained. 

More importantly, users of the sound studio apps will stick with the very stable fedora 16 and wait for fedora 17 to settle down before switching.

For this reason it is very important that the drobilla apps are back-ported to fedora 16.
Comment 6 Fedora End Of Life 2013-01-16 07:23:56 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
Comment 7 Fedora End Of Life 2013-02-13 07:40:02 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.