cdparanoia III 10pre0 was released back in August. It seems to contain a lot of bugfixes (though I'm not sure what exactly, couldn't find a changelog). Should this be added to portage ?
I second this request. I do suspect it's more than just a version bump in terms of effort.
Well, I hoped to get this in portage yesterday but it started quite bad: a) the gnuconfig support files are still named in the wrong way _and_ they are not updated (so it does not detect x86_64 CHOST by default, funny for something released this year); b) the configure file checks for int16_t and int32_t with an #ifdef HAVE_STDINT_H bug without checking for stdint.h presence before: result it fails to find them (at least on amd64). Knowing this, I'm not going to update it myself, and I'd rather leave it to someone else more interested in this... that someone _might_ become the victim of every Xiph-released software :P Basically, the best way to get this fixed would be to spank upstream till they release something vaguely working.
Created attachment 117692 [details] cdparanoia-3.10_pre0.ebuild Hello, since I was flooded with kernel messages caused by cdparanoia after the switch from the ide layer to the new libata-pata layer, I modified the latest cdparanoia ebuild to work with cdparanoia 3.10 pre0. cdparanoia now includes most of the current patches. Two patches are still needed and work as they are now: * cdparanoia-3.9.8-include-cdda_interface_h.patch * cdparanoia-3.9.8-use-destdir.patch Another patch needed some minor changes, I'll attach it in the next comment. I'm on x86, so I don't know anything about the mentioned x86_64 problems, this ebuild works here, however.
Created attachment 117693 [details, diff] cdparanoia-3.10-respectflags-pio.patch Modified patch. The 3.9.8 patch didn't apply because the Makefiles were slightly different.
Bumped but p.masked for testing with reference to this bug.
