Processing of bristol_0.60.2-1_amd64.changes

bristol_0.60.2-1_amd64.changes uploaded successfully to localhost along with the files: bristol_0.60.2-1.dsc bristol_0.60.2.orig.tar.gz bristol_0.60.2-1.diff.gz bristol_0.60.2-1_amd64.deb bristol-data_0.60.2-1_all.deb Greetings, Your Debian queue daemon (running on host ries.deb

Bug#580113: [mplayer] No audio output to pulse

> If you have reportbug installed, please post the output of > 'reportbug --template mplayer'. Adam already sent that, but just in case you want to compare, here's mine (reportbug-ng though). --- System information. --- Architecture: amd64 Kernel: Linux 2.6.33.1 Debian Release: squeeze

Bug#512786: audacity recording freezes in 1.3.6-2 to 1.3.12

I have still the same problem as in the first report of this thread, now with audacity 1.3.12. Kernel: 2.6.33.2 Debian-Sid 26.04.2010. So I return to audacity 1.3.5 again. Changing the prferences ( bit-rate, frequenz-sample-rate) has no effect. wkauz ___

[ras...@gmx.de: Bug#512786: audacity recording freezes in 1.3.6-2 to 1.3.12]

Hi! Is it just me or is audacity broken in 9 out of 10 cases? I think it's the most overrated audio application ever, its portaudio is a pure mess, either playback or recording doesn't work as expected, random freezes on various platforms and so on. If I were a company's QA department, I'd compl

深圳钟先生

±¾¹«Ë¾³¤ÆÚÓи÷Àà¨Q°l…dƯ©ƒ¶ÔÍ⡺´ú¡â¿ª¡»136¨H8689£¤5587ÖÓÏÈÉú ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers

Bug#580113: [mplayer] No audio output to pulse

On Tue, May 04, 2010 at 08:40:58 (CEST), Adam wrote: > AO: [pulse] 48000Hz 2ch s16be (2 bytes per sample) > Assertion 'channels > 0' failed at pulse/volume.c:76, function > pa_cvolume_set(). Aborting. This assertion doesn't look like it comes from mplayer, but rather from libpulse. In fact, afte

bristol 0.60.0-4 MIGRATED to testing

FYI: The status of the bristol source package in Debian's testing distribution has changed. Previous version: 0.40.6-1 Current version: 0.60.0-4 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will recei

bristol_0.60.2-1_amd64.changes ACCEPTED

Accepted: bristol-data_0.60.2-1_all.deb to main/b/bristol/bristol-data_0.60.2-1_all.deb bristol_0.60.2-1.diff.gz to main/b/bristol/bristol_0.60.2-1.diff.gz bristol_0.60.2-1.dsc to main/b/bristol/bristol_0.60.2-1.dsc bristol_0.60.2-1_amd64.deb to main/b/bristol/bristol_0.60.2-1_amd64.deb

Bug#580262: idjc: Mixer reports segmentation fault

Package: idjc Version: 0.8.2-1 Severity: important After the last Update of idjc and jack, idjc doesnt start up anymore with error Message: "Mixer reports a segmentation fault mixer crashed something bad happened and IDJC could not continue" Other programs using jack still work great. So I think

Processing of ladspa-sdk_1.13-1_source.changes

ladspa-sdk_1.13-1_source.changes uploaded successfully to localhost along with the files: ladspa-sdk_1.13-1.dsc ladspa-sdk_1.13.orig.tar.gz ladspa-sdk_1.13-1.diff.gz Greetings, Your Debian queue daemon (running on host ries.debian.org) __

Re: Processing of ladspa-sdk_1.13-1_source.changes

On Tue, May 4, 2010 at 18:21, Archive Administrator wrote: > ladspa-sdk_1.13-1_source.changes uploaded successfully to localhost > along with the files: >  ladspa-sdk_1.13-1.dsc >  ladspa-sdk_1.13.orig.tar.gz >  ladspa-sdk_1.13-1.diff.gz Sorry about this, I confused my dput line. -- Saludos,

ladspa-sdk_1.13-1_source.changes REJECTED

Reject Reasons: source only uploads are not supported. Source package ladspa-sdk does not have 'DM-Upload-Allowed: yes' in its most recent version (1.1-6) === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which add

Re: Bug#580262: idjc: Mixer reports segmentation fault

On Tue, 4 May 2010, Stefan Bischoff wrote: "Mixer reports a segmentation fault mixer crashed something bad happened and IDJC could not continue" Unfortunately, if /anything/ crashes in idjcmixer... you get this same error message. So, some manner of backtrace is really necc. in order to i

Processed: reassign 509330 to src:liblo, reassign 543374 to src:liblo

Processing commands for cont...@bugs.debian.org: > reassign 509330 src:liblo Bug #509330 [liblo0-dev] liblo0-dev: New version (0.25) available Bug reassigned from package 'liblo0-dev' to 'src:liblo'. Bug No longer marked as found in versions liblo/0.23-2.2. > reassign 543374 src:liblo Bug #543374

Bug#509330: marked as done (liblo0-dev: New version (0.25) available)

Your message dated Wed, 5 May 2010 00:58:55 -0400 with message-id and subject line 0.26 was uploaded a while ago has caused the Debian Bug report #509330, regarding liblo0-dev: New version (0.25) available to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#543374: marked as done (liblo0-dev: OSC client/server does not handle blobs correctly)

Your message dated Wed, 5 May 2010 00:58:55 -0400 with message-id and subject line 0.26 was uploaded a while ago has caused the Debian Bug report #543374, regarding liblo0-dev: OSC client/server does not handle blobs correctly to be marked as done. This means that you claim that the problem has b