Hide Forgot
Description of problem: The package does not provide development components: the shared object file, and the headers. Version-Release number of selected component (if applicable): 1.4.0-0.11.svn305 The package should provide developer components in a -devel sub package. It is required by other libraries, such as libmpc. Please fix the package. http://www.musepack.net/index.php?pg=src The changelog says: * Wed Mar 26 2008 Paul P. Komkoff Jr <i@stingr.net> - 1.4.0-0.2.svn305 - add COPYING and doc/formats.txt - remove *.so Why? Thanks, Warm regards, Ankur
Can you also please comment the patches? Especially the bz2 patch that has been included.
Created attachment 811522 [details] Patch with specfile fixes
If upstream doesn't include devel components as part of the standard "make install", why are you advocating against that?
ah, nevermind, needed by libmpc
While you're at it, a format 1.4.0 release is available (at https://github.com/svend/cuetools/releases), so there's less need to continue carrying a snapshot.
(In reply to Rex Dieter from comment #3) > If upstream doesn't include devel components as part of the standard "make > install", why are you advocating against that? Well, the make install step does install an unversioned soname that goes into the -devel subpackage. I'm assuming this is useless if the headers aren't installed too. Probably why the maintainer got rid of it in the first place. (In reply to Rex Dieter from comment #4) > ah, nevermind, needed by libmpc I found out that musepack upstream keeps their own version of this library, as "libcuefile". I'm packing that up separately for musepack: http://svn.musepack.net/libcuefile/ (In reply to Rex Dieter from comment #5) > While you're at it, a format 1.4.0 release is available (at > https://github.com/svend/cuetools/releases), so there's less need to > continue carrying a snapshot. I haven't tinkered with the sources since I don't know what the patches do. I'll look into if I have the time, but since I don't need this package for libmpc any more, it's not too high on my task list. Thanks Warm regards, Ankur
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.