Description of problem: please update ogre to 1.7 in rawhide Version-Release number of selected component (if applicable): 1.6.4
I'll look at updating Ogre to 1.7 or 1.8 in f14. I was aware that a release was due soon, but it's really too late to do this for f13.
thats why i asked for it for rawhide (which is f14 currently). i just did a test build and updated the spec somewhat (the samples work). if you are on freenode irc i can show you what i already did. just about testing and rebuilding chess and ember.
I am reporting this update too.
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
now we are at 1.7.1 and i guess it is too late for f14... i am reassigning this bug to rawhide again.
It's too late now. Unfortunately I got stuck doing a lot of Spins SIG work and didn't have time for this in addition to that.
Hi Rudolf, It seems atorkhov is not active in koji since 2009.10, maybe you can orphan his packages through Non-responsive Maintainer Policy. See http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
And what do you think will happen then? If you guys are actually packagers who want to help work on this (noting that there are license complexities with this package), apply for access. Trying to get the package orphaned isn't going to help otherwise. I'm a co-maintainer who could work on it if someone freed up some of my time by doing some of the other stuff I am stuck doing. (I am not a good fit for the other stuff, but it's more important to Fedora and no one else is doing that work. So I need to work there for now.)
in reply to #8: What will happen then? I am not sure. Maybe it gets picked up by someone having time and dedication for one of the most important 3d engines we have in the open source sector... or it will get dropped. The current state is pretty much unacceptable. The last build of ogre in koji was: ogre-1.6.4-3.fc12 bruno 2009-11-28 20:10:32, which was done by you bruno. Note that one year has passed. Current upstream release: 1.72 Current fedora package: 1.64 Do you think the situation should stay as it is? What would you recommend to do? Wait? Wait how long and for what? Until the 3rd freeze since this bug is open gehts issued? I am constantly building new ogre releases on rawhide for my personal purpose and they just build. If the other stuff is so central and important it can be done by alot people i guess. If no one else steps up it is probably not that important. Dont get me wrong i appreciate your efforts but if you look at it in an unemotional way packages shouldnt stall and rot for 12 months.
in addition to #8: are there any other legal concerns but nvidia Cg support i am currently not aware of?
Anyone who wants to help now and is already a packager can ask for commit access. I personally don't have ACL access, but don't expect any offers of help to be refused. That's a much simpler process than getting the packaged orphaned first. There is a license change that needs to be documented. That's not a big deal, it just needs to get done. Other than that, I think just a review to make sure what's there is OK, since this was a major update. Particularly things like samples. The build process is different now if I remember correctly.
On the nVidia CG support, I don't go back far enough to know what the real issue was there. It might have been patents or it might have been that while we didn't want to enable it in Fedora, we didn't want to keep rpmfusion from being able to supply it. It would possibly be useful to go back and look at the Ogre review to see what the underlying issue was. It may be we can disable that in a simpler way.
It turns out I do have approveacls access for ogre. (I didn't remember asking for that, but I guess I must have.) So I can approve any current packager who wants to help work on getting 1.7 working in rawhide.
i can update the src.rpm or spec file if wanted/necassery. someone else will have to build it though.
Spot did a bunch of leg work for this. I need to do a couple of licensing checks, but I should be able to use what he provided to update Ogre and a few dependencies over the holiday break.
I have built Ogre 1.7.2 for rawhide. I still need to get the dependencies updated, so for now updates will be blocked by dependency conflicts unless you aren't actually using ogre.
Most of the normal stuff has been rebuilt, so people can use 1.7.