Red Hat Bugzilla – Bug 467029
please update the package version to 3.0.7
Last modified: 2009-03-20 20:28:49 EDT
please update the package version to 3.0.7 since the current svn at least 3.0.7 (not 3.0.4).
and at the same time please build on epel too.
no i check it again and it seems that f-9, f-10, f-11 (aka devel) and epel alse has older jna. unfortunately i need newer jna version in order to be able to push gstreamer-java into fedora and epel.
The current version is actually an SVN snapshot.
ok but that's svn is newer then 3.0.7!
anyway the version is just less important, the more important that this version get into the f-9 updates, f-10 and epel asap. since otherwise i can't submit gstreamer-java because it's not build on older version.
any change to a f-9 and epel jna push?
i know f-10 is less then a month now, but i still like to push f-9 and epel gstreamer-java packages...
Would you request the request on bodhi to push F-9 newest package to repository,
Just for reference I'm fine if anyone makes modifications or updates for any of my packages, as long as you know what you're doing.
But I did just create a Bodhi update for f9:
As for EPEL, I don't have time right now to set up plague etc. If someone else wants to do it please feel free.
i don't really understand you since jna already has the EL-5 cvs branch you only need to do:
./common/cvs-import.sh -b EL-5 jna-3.0.4-9.svn729.fc9.src.rpm
and it's do all the plague build.
but if you cam give me write access to the EL-5 branch i'm also willing to maintain it.
i've been build it and now in the needsign queue:
anyway the latest devel and F-10 brach the spec file contains a patch jna-callback-exception.patch which is not in the cvs.
could you commit it.
Done; that was an in-progress patch, not yet intended for application.
Jruby 1.1.5 (and soon, 1.1.6) need jna 3.0.9. So I'd request this be made available for at least rawhide and I'd like F-10 and F-9 as well. (I noticed the CVS jna/devel/jna.spec is version 3.0.9 so maybe this will be a really quick fix.)
from my part this bug can be closed. or 3.0.9 can be submitted to epel.
This works for me also; closing.