Red Hat Bugzilla – Bug 499813
Package and ship 0.11.x
Last modified: 2009-06-15 21:24:12 EDT
Right now the latest Jokosher release available for Fedora is 0.4, which seams to be quite old.
Jokosher has seen two nice releases (0.11.0 and 0.11.1) this year. Besides tons of fixes and improvements, it features PulseAudio support which is very important to have for F11 imho.
Please update the package.
Where did you get the version number from? Current Jokosher is from svn snapshot, albeit October last year. I will update the snapshot anyway.
Thanks for the bug.
(In reply to comment #1)
> Where did you get the version number from? Current Jokosher is from svn
> snapshot, albeit October last year.
Latest build in Koji says "jokosher-1.0-0.5.20081012svn.fc11", I read that as an SVN version leading up to 0.5... didn't really pay attention to the date :)
> I will update the snapshot anyway.
0.11.2 has some requirements that prevent me from updating the F10 package.
However F11 + Rawhide should be good to go so will push that later today. In the meantime I've done a scratch build in koji for you:
Let me know how you go with it and if its all good I'll close off the bug after it gets pushed.
Thanks Chris, the RPM installs without problem. As for "working", well... I guess I need to still file a few bugs upstream, but at least Fedora is has a build that is up-to-date again.
I only wonder about the package name/version...
-> jokosher-1.0-0.11.2.20090509svn.fc11.noarch.rpm maybe ?
(In reply to comment #4)
> Thanks Chris, the RPM installs without problem. As for "working", well... I
> guess I need to still file a few bugs upstream, but at least Fedora is has a
> build that is up-to-date again.
The developers always appreciate bug reports. :)
> I only wonder about the package name/version...
> -> jokosher-1.0-0.11.2.20090509svn.fc11.noarch.rpm maybe ?
No. The 0.5 is part of the Release tag in the spec file. This gets bumped for every build that takes place from the source. Therefore if there was a mass rebuild as part of the F12 cycle, this would become 0.12.2, only increasing the confusion.
The 1.0 refers to the Version number and because the developers changed their mind and release 0.10 and 0.11 after I started doing snapshots from svn (now bzr), I'm sticking with the current convention. I could use Epochs but this isn't recommended and there is no over-riding reason to do so.
The build seems to be gone from koji. Where is it?
FYI, the SVN revision that was packaged on koji had a bug that prevented new projects from being created correctly. IIRC this is fixed now in trunk, in case you want to update the package.
Hi Matej, Michael,
I am intending to update this but only for releases > F11 and only after F11 is released as Jesse recently commented about the number of updates queued which could have been pushed previous to the freeze. I don't want to upset him :)
Michael - will update the bzr snapshot - thanks for tip.
(In reply to comment #8)
> I am intending to update this but only for releases > F11 and only after F11 is
> released as Jesse recently commented about the number of updates queued which
> could have been pushed previous to the freeze. I don't want to upset him :)
Well, I am generally all for RHEL-like access to updates (i.e., updating only to fix bugs), but in this case I would say that the development is so fast and older versions of jokosher so useless, I think upgrade wouldn't hurt. But, of course, it is your call.
Would love to but the requirements for the current code are only fulfilled by versions >= F11.
Michael - I am updating now but for F11 also and will publish the koji URL for you.
jokosher-1.0-0.5.20090604svn.fc11 has been submitted as an update for Fedora 11.
Bodhi will autoclose this bug in a few days...
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
jokosher-1.0-0.5.20090604svn.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.