This is regarding the Fedora KDE 3.2 packages on the KDE mirrors. They are not on the official Fedora repositories, but the packager line says "Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>" and so I am reporting here. For some reason, the kdemultimedia packages do not include the juk media player. Since I consider juk to be superior to the other two KDE media players (which are included), this is disappointing. Oddly, however, the kdemultimedia package does include some help files related to juk: $ rpm -q --filesbypkg kdemultimedia |grep juk kdemultimedia /usr/share/doc/HTML/en/juk kdemultimedia /usr/share/doc/HTML/en/juk/common kdemultimedia /usr/share/doc/HTML/en/juk/index.cache.bz2 kdemultimedia /usr/share/doc/HTML/en/juk/index.docbook kdemultimedia /usr/share/doc/HTML/en/juk/toolbar.png If juk is going to be packaged separately, please disregard this bug, although there's no juk Fedora RPM currently on the KDE mirrors based on KDE 3.2.
OK, I downloaded the SRPM for kdemultimedia to figure out why juk isn't building. It appears that the reason is that taglib isn't present. Fedora Core 1 doesn't have a taglib RPM, and taglib is not currently in the package list for Fedora Core 2. So, I'm attaching a specfile that can build the taglib 1.0 tarball. This may need some tweaking, but anyway it's a start. taglib has no dependencies so it should be low-overhead to maintain. I've tested it on my Core 1 system; with the presence of this RPM, kdemultimedia at least attempts to build juk. The taglib tarball is at: http://ktown.kde.org/~wheeler/taglib/taglib-1.0.tar.gz BTW the taglib homepage: http://ktown.kde.org/~wheeler/taglib/
Created attachment 97638 [details] taglib spec file
i have already rebuilt all kde 3.2 against qt 3.3.0 yesterday. This new on will include juk of course. I will upload one soon on ftp.kde.org
I have kdemultimedia-3.2.0-1.3 installed from rawhide and juk is still not there. Running "rpm -q --filesbypkg kdemultimedia |grep juk" produces exactly the same output as the one in the bug opening comment. If the bug is fixed in an internal build, please disregard this comment.