Hide Forgot
Spec URL: http://ankursinha.fedorapeople.org/libcuefile/libcuefile.spec SRPM URL: http://ankursinha.fedorapeople.org/libcuefile/libcuefile-0-0.1.svn475.fc21.src.rpm Description: %{name} is a stripped down version of the original cuetools library. This is used by the musepack tools. Fedora Account System Username: ankursinha rpmlint errors: [asinha@ankur-laptop SRPMS]$ rpmlint /var/lib/mock/fedora-rawhide-x86_64/result/*.rpm libcuefile.src: W: spelling-error Summary(en_US) cuetools -> cue tools, cue-tools, stools libcuefile.src: W: spelling-error %description -l en_US cuetools -> cue tools, cue-tools, stools libcuefile.src: W: spelling-error %description -l en_US musepack -> muse pack, muse-pack, mudpack libcuefile.x86_64: W: spelling-error Summary(en_US) cuetools -> cue tools, cue-tools, stools libcuefile.x86_64: W: spelling-error %description -l en_US cuetools -> cue tools, cue-tools, stools libcuefile.x86_64: W: spelling-error %description -l en_US musepack -> muse pack, muse-pack, mudpack libcuefile.x86_64: W: shared-lib-calls-exit /usr/lib64/libcuefile.so.0.0.0 exit@GLIBC_2.2.5 libcuefile.x86_64: E: incorrect-fsf-address /usr/share/doc/libcuefile/COPYING libcuefile-debuginfo.x86_64: E: incorrect-fsf-address /usr/src/debug/libcuefile_r475/src/toc_parse.h libcuefile-debuginfo.x86_64: E: incorrect-fsf-address /usr/src/debug/libcuefile_r475/src/toc_parse.c libcuefile-debuginfo.x86_64: E: incorrect-fsf-address /usr/src/debug/libcuefile_r475/src/cue_parse.c libcuefile-debuginfo.x86_64: E: incorrect-fsf-address /usr/src/debug/libcuefile_r475/src/cue_parse.h libcuefile-devel.x86_64: W: no-documentation 4 packages and 0 specfiles checked; 5 errors, 8 warnings.
(In reply to Ankur Sinha (FranciscoD) from comment #0) > %{name} is a stripped down version of the original cuetools library. This is > used by the musepack tools. Why can't musepack use libcue? From what I can gather from a brief glance, libcuefile is mostly API compatible to libcue.
(In reply to Ralf Corsepius from comment #1) > (In reply to Ankur Sinha (FranciscoD) from comment #0) > > %{name} is a stripped down version of the original cuetools library. This is > > used by the musepack tools. > > Why can't musepack use libcue? From what I can gather from a brief glance, > libcuefile is mostly API compatible to libcue. I've mailed upstream asking them to clarify how libcuefile is different from the library that cuetools provides. I'm not sure yet.
Not required any more. musepack builds against libcue now. Closing