I haven't had much time to work on this 'audacity' bug until today, but
by tomorrow I hope to either provide draft patches that allow it to run
on my system, or at least provide a more complete description of what's
going wrong with the code.
I see that upstream does not allow people to open t
On Tue, Jun 15, 2010 at 02:30:52AM -0400, Dave Witbrodt wrote:
> (I really wish that I could bisect using 'git'. Does the 'audacity'
> upstream use 'git', or do the Debian maintainers have their own 'git'
> repo where they merge new versions from upstream? I am merely a
http://packages
I didn't accomplish very much after work tonight toward debugging this
problem, but I have some new information to report.
Since 'audacity' was working for me just a few months ago, I decided I
wanted to try to locate an earlier version that works on my hardware. I
looked at /usr/share/doc/au
On Sun, Jun 13, 2010 at 06:11:08PM -0400, Dave Witbrodt wrote:
> *vol = snd_mixer_find_selem(dev->handle, sid);
> i = 530
> In stack frame #2, we clearly have a value of 530 in "i". When did
> that happen, since last we saw "i" was just set to 0?
Weird.
> This must mean that t
Thank you for your very extensive analysis.
On Mon, Jun 14, 2010 at 00:11:08 (CEST), Dave Witbrodt wrote:
> The following discussion must be understood in the context of the packages
> on my system. I believe that I am using FFMPEG from debian-multimedia.org:
>
> $ apt-cache policy libavfor
Package: audacity
Version: 1.3.12-3+fix03
Severity: normal
Forgive the version listed above: it is from my local build, and is obviously
not an official Debian package.
After applying the patch suggested, I was getting a FTBFS:
--
[...]
g++ -c -g -O2 -g -Wall -O2 -I../lib-src/portmixer
6 matches
Mail list logo
