Summary: | Stabilise =media-sound/audacity-1.3.12 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeremy Murphy <jeremy.william.murphy> |
Component: | Current packages | Assignee: | Professional Audio Applications Maintainers <proaudio> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | richard |
Priority: | High | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 273971 | ||
Bug Blocks: | |||
Attachments: | Build log |
Description
Jeremy Murphy
2010-11-21 09:32:46 UTC
A couple of the outstanding bugs have been confirmed to exist with 1.3.12, namely bugs #273971 and #302990. I don't know how long they should hold up the stabilization process though since they've existed for awhile. (In reply to comment #1) > A couple of the outstanding bugs have been confirmed to exist with 1.3.12, > namely bugs #273971 and #302990. I don't know how long they should hold up the > stabilization process though since they've existed for awhile. #302990 is probably an alsalib / portaudio bug, or even in Jack given the only people who hit the problem are ones who divert their ALSA output into jack (i.e. aren't using native ALSA for Audacity to talk to). 1.3.13 will ship a newer portaudio snapshot which at a minimum will emit better errors, but I don't have a release date. #273971 is a really obscure build failure due to using advanced CFLAGS which seem to give pkg-config trouble. I'd have no problem with a patch to change audacity's use of pkg-config given a reasonable explanation, but running sed on configure is not on! More importantly both bugs are reported back at Audacity 1.3.7, i.e. haven't appeared new in 1.3.12. So if you don't like them still being open, logically 1.3.7 should loose stable ... I agree with the info about the bugs in comment #2 so we'll just start the stabilization process for 1.3.12 unless someone has a major objection. Arches, please test and mark stable: =media-sound/audacity-1.3.12 Created attachment 255615 [details]
Build log
QA Notice: Unrecognized configure options:
configure: WARNING: unrecognized options: --enable-nyquist, --enable-ladspa, --with-libsndfile, --with-expat, --with-libsamplerate, --without-libresample, --with-libvorbis, --with-libmad, --with-libflac, --with-libid3tag, --with-soundtouch, --with-libvamp, --with-libtwolame, --with-ffmpeg, --with-midi, --with-alsa, --with-jack, --with-wx-config
configure: WARNING: unrecognized options: --enable-nyquist, --enable-ladspa, --with-libsndfile, --with-expat, --with-libsamplerate, --without-libresample, --with-libvorbis, --with-libmad, --with-libflac, --with-libid3tag, --with-soundtouch, --with-libvamp, --with-libtwolame, --with-ffmpeg, --with-midi, --with-alsa, --with-jack, --with-wx-config
configure: WARNING: unrecognized options: --enable-unicode, --enable-nyquist, --enable-ladspa, --with-libsndfile, --with-expat, --with-libsamplerate, --without-libresample, --with-libvorbis, --with-libmad, --with-libflac, --with-libid3tag, --with-soundtouch, --with-libvamp, --with-libtwolame, --with-ffmpeg, --with-midi, --with-alsa, --with-jack, --with-wx-config, --disable-programs, --disable-programs
configure: WARNING: unrecognized options: --enable-unicode, --enable-nyquist, --enable-ladspa, --with-libsndfile, --with-expat, --with-libsamplerate, --without-libresample, --with-libvorbis, --with-libmad, --with-libflac, --with-libid3tag, --with-soundtouch, --with-libvamp, --with-libtwolame, --with-ffmpeg, --with-midi, --with-alsa, --with-jack, --with-wx-config, --disable-programs, --disable-programs
(In reply to comment #4) This is a known and not easily fixable issue. See comment #1 in bug #265208. Comment on attachment 255615 [details]
Build log
i see.
Anyway, works well for me on amd64
Archtested on x86: Everything fine amd64 done. Thanks Agostino x86 stable, thanks David sparc done ppc stable ppc64 stable HPPA, you may want to stabilize 1.3.13 instead, please see bug #372757. Cheers. No need for this bug report while we have bug #372757. |