Bug#711030: mplayer: Sound cracking on a Sheeva Plug

Package: mplayer Version: 2:1.0~rc3++final.dfsg1-1 Severity: normal Hi, I have a Sheeva with Debian Squeeze. aplay and mplayer have sound cracking. Mplayer is much better, almost perfect compared to aplay, but still some cracking remain all the time. I tried to fix it with working on the

Processed: severity of 690828 is serious, merging 710619 690828

Processing commands for cont...@bugs.debian.org: severity 690828 serious Bug #690828 [src:csound] csound: FTBFS on all architectures Severity set to 'serious' from 'important' merge 710619 690828 Bug #710619 [src:csound] csound: FTBFS: csound_orcparse.h:153:22: error: unknown type name

Bug#637611: marked as done (mplayer: redirected stdin from /dev/null causes 100% busy loop)

Your message dated Tue, 4 Jun 2013 21:32:37 +1000 (EST) with message-id alpine.deb.2.02.1306042130550.8...@dirac.rather.puzzling.org and subject line Re: Bug#637611: mplayer: redirected stdin from /dev/null causes 100% busy loop has caused the Debian Bug report #637611, regarding mplayer:

Processing of mp4v2_2.0.0~dfsg0-2_amd64.changes

mp4v2_2.0.0~dfsg0-2_amd64.changes uploaded successfully to localhost along with the files: mp4v2_2.0.0~dfsg0-2.dsc mp4v2_2.0.0~dfsg0-2.debian.tar.gz libmp4v2-2_2.0.0~dfsg0-2_amd64.deb libmp4v2-dev_2.0.0~dfsg0-2_amd64.deb mp4v2-dbg_2.0.0~dfsg0-2_amd64.deb

mp4v2_2.0.0~dfsg0-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Jun 2013 18:16:52 +0200 Source: mp4v2 Binary: libmp4v2-2 libmp4v2-dev mp4v2-dbg mp4v2-utils Architecture: source amd64 Version: 2.0.0~dfsg0-2 Distribution: unstable Urgency: low Maintainer: Debian Multimedia

Bug#709127: marked as done (mp4v2-utils: mp4tags -P corrupts ALBUMARTIST)

Your message dated Tue, 04 Jun 2013 16:33:46 + with message-id e1ujub8-00055d...@franck.debian.org and subject line Bug#709127: fixed in mp4v2 2.0.0~dfsg0-2 has caused the Debian Bug report #709127, regarding mp4v2-utils: mp4tags -P corrupts ALBUMARTIST to be marked as done. This means that

radium-compressor 0.5.1-3 MIGRATED to testing

FYI: The status of the radium-compressor source package in Debian's testing distribution has changed. Previous version: 0.5.1-2 Current version: 0.5.1-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

Bug#706154: gecko-mediaplayer: claims that an additional plugin is needed, but standalone gnome-mplayer plays the video

On Sun, 2 Jun 2013 19:27:54 +0200 Sebastian Ramacher wrote: On 2013-06-02 18:27:11, Francesco Poli wrote: [...] Could you check with stat or similar if the files from /usr/lib/mozilla/plugins are loaded and by setting the appropriate LD_DEBUG flags (check ld-linux.so(8) for details) if

Bug#711118: gnome-mplayer: messes up with dconf settings even when the user didn't change anything

Package: gnome-mplayer Version: 1.0.8-1 Severity: normal Hello, I noticed a misbehavior of gnome-mplayer with respect to the dconf configuration management. After the following steps: 0) start dconf-editor 1) reset all gnome-mplayer/gecko-mediaplayer preferences to their defaults 2) quit

Bug#711118: gnome-mplayer: messes up with dconf settings even when the user didn't change anything

Control: tags -1 + upstream On 2013-06-04 22:35:36, Francesco Poli (wintermute) wrote: Package: gnome-mplayer Version: 1.0.8-1 Severity: normal Hello, I noticed a misbehavior of gnome-mplayer with respect to the dconf configuration management. After the following steps: 0) start

Processed: Re: Bug#711118: gnome-mplayer: messes up with dconf settings even when the user didn't change anything

Processing control commands: tags -1 + upstream Bug #78 [gnome-mplayer] gnome-mplayer: messes up with dconf settings even when the user didn't change anything Added tag(s) upstream. -- 78: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=78 Debian Bug Tracking System Contact

Processing of yoshimi_1.1.0-1_amd64.changes

yoshimi_1.1.0-1_amd64.changes uploaded successfully to localhost along with the files: yoshimi_1.1.0-1.dsc yoshimi_1.1.0.orig.tar.bz2 yoshimi_1.1.0-1.debian.tar.gz yoshimi_1.1.0-1_amd64.deb yoshimi-data_1.1.0-1_all.deb yoshimi-dbg_1.1.0-1_amd64.deb Greetings, Your Debian

yoshimi_1.1.0-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Jun 2013 23:47:33 +0200 Source: yoshimi Binary: yoshimi yoshimi-data yoshimi-dbg Architecture: source amd64 all Version: 1.1.0-1 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers

Processed: Re: Bug#706154: gecko-mediaplayer: claims that an additional plugin is needed, but standalone gnome-mplayer plays the video

Processing control commands: tags -1 + help Bug #706154 [gecko-mediaplayer] gecko-mediaplayer: claims that an additional plugin is needed, but standalone gnome-mplayer plays the video Added tag(s) help. -- 706154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706154 Debian Bug Tracking

Bug#706154: gecko-mediaplayer: claims that an additional plugin is needed, but standalone gnome-mplayer plays the video

Control: tags -1 + help On 2013-06-04 22:25:35, Francesco Poli wrote: $ strace -o /tmp/strace.log -f iceweasel $ grep /usr/lib/mozilla/ /tmp/strace.log 8065 access(/usr/lib/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}, F_OK) = 0 8065

Processing of csound_5.17.11~dfsg-3_amd64.changes

csound_5.17.11~dfsg-3_amd64.changes uploaded successfully to localhost along with the files: csound_5.17.11~dfsg-3.dsc csound_5.17.11~dfsg-3.debian.tar.gz csound-data_5.17.11~dfsg-3_all.deb libcsound64-dev_5.17.11~dfsg-3_all.deb libcsnd-dev_5.17.11~dfsg-3_all.deb

Processing of laborejo_0.7~ds0-1_amd64.changes

laborejo_0.7~ds0-1_amd64.changes uploaded successfully to localhost along with the files: laborejo_0.7~ds0-1.dsc laborejo_0.7~ds0.orig.tar.gz laborejo_0.7~ds0-1.debian.tar.gz laborejo_0.7~ds0-1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)

laborejo_0.7~ds0-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Jun 2013 23:43:54 +0100 Source: laborejo Binary: laborejo Architecture: source all Version: 0.7~ds0-1 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers

csound_5.17.11~dfsg-3_amd64.changes REJECTED

Version check failed (source=csound, version=1:5.17.11~dfsg-3, other-version=1:5.17.11~dfsg-3, suite=stable) === 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 address our concerns.

Processing of libshout-idjc_2.3.1-1_amd64.changes

libshout-idjc_2.3.1-1_amd64.changes uploaded successfully to localhost along with the files: libshout-idjc_2.3.1-1.dsc libshout-idjc_2.3.1.orig.tar.gz libshout-idjc_2.3.1-1.debian.tar.gz libshout-idjc-dev_2.3.1-1_amd64.deb libshout-idjc3_2.3.1-1_amd64.deb Greetings, Your Debian

libshout-idjc_2.3.1-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Jun 2013 23:56:04 +0100 Source: libshout-idjc Binary: libshout-idjc-dev libshout-idjc3 Architecture: source amd64 Version: 2.3.1-1 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers

Processing of csound_5.17.11~dfsg-4_amd64.changes

csound_5.17.11~dfsg-4_amd64.changes uploaded successfully to localhost along with the files: csound_5.17.11~dfsg-4.dsc csound_5.17.11~dfsg-4.debian.tar.gz csound-data_5.17.11~dfsg-4_all.deb libcsound64-dev_5.17.11~dfsg-4_all.deb libcsnd-dev_5.17.11~dfsg-4_all.deb

csound_5.17.11~dfsg-4_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 05 Jun 2013 01:18:00 +0200 Source: csound Binary: csound csound-data csound-gui csound-utils libcsound64-5.2 libcsnd-java libcsound64-dev libcsnd-dev libcsoundac-dev pd-csound python-csound libcsnd5.2

Bug#710619: marked as done (csound: FTBFS: csound_orcparse.h:153:22: error: unknown type name 'PARSE_PARM')

Your message dated Tue, 04 Jun 2013 23:33:21 + with message-id e1uk0jb-0006un...@franck.debian.org and subject line Bug#710619: fixed in csound 1:5.17.11~dfsg-4 has caused the Debian Bug report #710619, regarding csound: FTBFS: csound_orcparse.h:153:22: error: unknown type name 'PARSE_PARM'

Bug#690828: marked as done (csound: FTBFS on all architectures)

Your message dated Tue, 04 Jun 2013 23:33:21 + with message-id e1uk0jb-0006un...@franck.debian.org and subject line Bug#710619: fixed in csound 1:5.17.11~dfsg-4 has caused the Debian Bug report #710619, regarding csound: FTBFS on all architectures to be marked as done. This means that you

Processing of rubberband_1.8.1-2_amd64.changes

rubberband_1.8.1-2_amd64.changes uploaded successfully to localhost along with the files: rubberband_1.8.1-2.dsc rubberband_1.8.1-2.debian.tar.gz librubberband2_1.8.1-2_amd64.deb librubberband-dev_1.8.1-2_amd64.deb rubberband-cli_1.8.1-2_amd64.deb rubberband-ladspa_1.8.1-2_amd64.deb

rubberband_1.8.1-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 05 Jun 2013 01:31:40 +0200 Source: rubberband Binary: librubberband2 librubberband-dev rubberband-cli rubberband-ladspa rubberband-vamp Architecture: source amd64 Version: 1.8.1-2 Distribution: unstable Urgency:

Re: jack2 packaging

On Wed, May 29, 2013, at 09:12 AM, Kaj Ailomaa wrote: Has there been a discussion on what would be the best approach for packaging jack? I find that there sometimes is a problem where users wind up having both jackd and jackdbus running simultaniously. Is there any good reason for that to

Re: jack2 packaging

On 06/05/2013 02:18 AM, Kaj Ailomaa wrote: On Wed, May 29, 2013, at 09:12 AM, Kaj Ailomaa wrote: I'd like to go ahead and change this in packaging, making jackdbus and jackd separate for jack2. Also, make jackdbus conflict with jackd. But, that is only if there are no bad implications from

Re: jack2 packaging

sorry, seems like I replied to the wrong receiver. On Wed, Jun 5, 2013, at 05:42 AM, Kaj Ailomaa wrote: On Wed, Jun 5, 2013, at 02:49 AM, Robin Gareus wrote: On 06/05/2013 02:18 AM, Kaj Ailomaa wrote: On Wed, May 29, 2013, at 09:12 AM, Kaj Ailomaa wrote: I'd like to go ahead and