Bug 508281 - Split raydium from maniadrive
Split raydium from maniadrive
Product: Fedora
Classification: Fedora
Component: maniadrive (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Alexey Torkhov
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-06-26 08:05 EDT by Alexey Torkhov
Modified: 2010-12-05 01:47 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-05 01:47:11 EST
Type: ---
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 Alexey Torkhov 2009-06-26 08:05:19 EDT
Description of problem:
Maniadrive carries some old snapshot of raydium 3d engine.
Is it possible to split it to separate package? And will maniadrive continue to work with newer version of raydium?

I’m asking as I’ve find some small game that may be packaged, but it seem to require newer version of raydium:
Comment 1 Hans de Goede 2009-06-26 08:54:59 EDT
I wouldn't mind switching to a newer release of raydium (assuming we can fix maniadrive to work with it) but there is no newer upstream release. There has been some activity in svn, but not much, atleast not at:

So where would one get this newer raydium ?
Comment 2 Alexey Torkhov 2009-06-26 10:04:58 EDT
Hmm... I think, they didn't make new release, so only svn is available:
svn co svn://cqfd-corp.org/raydium/trunk

Their svn log:

There is even some commits for maniadrive.
Comment 3 Hans de Goede 2009-06-26 10:41:26 EDT

I'm really busy with other stuff, can you package up the latest svn please? Then
when that is done I'll see if maniadrive will work with that.
Comment 4 Alexey Torkhov 2009-06-26 10:45:34 EDT
Ok, will try a bit later.
Comment 5 Hans de Goede 2009-08-10 05:40:05 EDT
Hi Alexey, any progres on this ?
Comment 6 Alexey Torkhov 2009-08-12 12:33:25 EDT
Hi, didn't make any progress until vacation which is now, so this is defered a bit.
Comment 7 Bug Zapper 2009-11-16 05:28:11 EST
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
Comment 8 Bug Zapper 2010-11-04 06:57:29 EDT
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 to the applicable version.  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.

The process we are following is described here: 
Comment 9 Bug Zapper 2010-12-05 01:47:11 EST
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.