[PlanetCCRMA] FC5 app problems

Fernando Lopez-Lezcano nando@ccrma.Stanford.EDU
Fri Jun 23 13:05:01 2006


On Fri, 2006-06-23 at 20:00 +0100, BJaY wrote:
> /On Thu, 2006-06-22 at 23:11 -0700, Fernando Lopez-Lezcano wrote:
> /> On Fri, 2006-06-23 at 03:02 +0100, BJaY wrote:
> /> > Now I'm thoroughly confused. The jack rack site has the current stable
> /> > version1.4.4.
> />
> /> Correct.
> />
> /> > Before you released the rc version, I installed 1.4.4-2 from
> /> > the fc5 ccrma yum repo which was clearly an early version with no save
> or
> /> > load rack functionality though it proclaimed version 1.4.4 on the
> command
> /> > line (jack-rack -h).
> />
> /> Well, that is being printed by jack-rack itself, now I'm confused.
> />
> /> > This is the version in the fc4 repository which I had
> /> > used on fc4 and had this functionality.
> />
> /> I'll check this tomorrow, I don't have fc4 here right now.
> [MUNCH]
> when I yum-remove jack-rack and then try and run it I get No such file or
> directory
> 
> Just to verify the URL for the rpm of the 1.4.4-2 version :
> http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/5/i386
> /jack-rack-1.4.4-2.rhfc5.ccrma.i386.rpm
> 
> sha1sum jack-rack-1.4.4-2.rhfc5.ccrma.i386.rpm
> 947d1084f5f14e7f3d0da9a85e42a704f9cc30ff
> jack-rack-1.4.4-2.rhfc5.ccrma.i386.rpm
> 
> Sorry to be such a pain but I really need to understand this.

No, no problem, you are not alone, I also want to know what's going on! 

I think I got it, sorry I was also confused about fc4 vs fc5. I'm
getting the same behavior you see in 1.4.4-2 in fc5 (ie: no save/load,
no "about" box, etc). 

It looks like this was a build problem in 1.4.4 only on fc5. I can see a
couple of problems (now that I'm looking for them) in the build log for
the package and they seem to affect things related to what we see, for
example, gnome_about_new (which I presume would be used to show the
"About" information). So most probably it was a problem of dependencies
being wrong, or improper headers, or something like that, and,
apparently that was fixed in 1.4.5rc1. 

-- Fernando