cecilia_5.0.7-2_amd64.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 26 Nov 2012 23:53:58 -0500 Source: cecilia Binary: cecilia Architecture: source all Version: 5.0.7-2 Distribution: experimental Urgency: low Maintainer: Debian Multimedia Maintainers Changed-By: Tiago Bortoletto Va

Processing of cecilia_5.0.7-2_amd64.changes

cecilia_5.0.7-2_amd64.changes uploaded successfully to localhost along with the files: cecilia_5.0.7-2.dsc cecilia_5.0.7-2.debian.tar.gz cecilia_5.0.7-2_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ p

zynaddsubfx_2.4.3-3_amd64.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 27 Nov 2012 01:39:14 + Source: zynaddsubfx Binary: zynaddsubfx zynaddsubfx-dssi zynaddsubfx-dbg Architecture: source amd64 Version: 2.4.3-3 Distribution: experimental Urgency: low Maintainer: Debian Multimedia Ma

Processing of zynaddsubfx_2.4.3-3_amd64.changes

zynaddsubfx_2.4.3-3_amd64.changes uploaded successfully to localhost along with the files: zynaddsubfx_2.4.3-3.dsc zynaddsubfx_2.4.3-3.debian.tar.gz zynaddsubfx_2.4.3-3_amd64.deb zynaddsubfx-dssi_2.4.3-3_amd64.deb zynaddsubfx-dbg_2.4.3-3_amd64.deb Greetings, Your Debian queue da

Bug#694406: Backported patch

I've attached a patch for your convenience. I expect this patch will probably apply cleanly and work just fine against whatever version of Rosegarden is in your repository. It's very limited in scope and impact, and is very unlikely to carry hidden consequences. It appears to fix the upstream

Bug#694483: CVEs: CVE-2012-2882 CVE-2012-5359 CVE-2012-5360 CVE-2012-5361

Source: libav Version: 0.8.4 Severity: grave Tags: security Justification: user security hole Dear Maintainer, I have here another series of CVEs for ffmpeg/libav: CVE-2012-2882 CVE-2012-5359 CVE-2012-5360 CVE-2012-5361 For the last 3 http://technet.microsoft.com/en-us/security/msvr/msvr12-017

Bug#688847: Unclear status of CVE-2012-2774 CVE-2012-2783 CVE-2012-2791 CVE-2012-2797 CVE-2012-2803 CVE-2012-2804

I just had a look at the above mentioned problems and I am a bit unsure about their status. As far as I can see the fixes are not applied, the status in http://security-tracker.debian.org/tracker/source-package/libav still lists these issues as open, but the bug is closed. Are these problems real?

Re: shotdetect updates

On Mon, Nov 26, 2012 at 5:21 PM, Giulio Paci wrote: > 2) Some time ago I joined the pkg-multimedia-maintainers group and I would > like to move shotdetect maintainance there. Is this the right moment to do > that? What should I do > to perform the switch? If you have already read our packaging

shotdetect updates

Hi Thorsten, hi all, recently I got a bug report (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694299) about shotdetect FTBFS with libav 0.9. A patch was attached fixing the issue, so I included it in shotdetect and I pushed my git repository on collab-maint: git://git.debian.org/git

Bug#694291: marked as done (liblscp-doc: missing Breaks+Replaces: liblscp-dev (<< 0.5.6-4))

Your message dated Mon, 26 Nov 2012 14:49:11 + with message-id and subject line Bug#694291: fixed in liblscp 0.5.6-6 has caused the Debian Bug report #694291, regarding liblscp-doc: missing Breaks+Replaces: liblscp-dev (<< 0.5.6-4) to be marked as done. This means that you claim that the prob

Bug#694274: marked as done (libgmerlin-dev: missing Breaks+Replaces: gmerlin-data (<< 1.0.0~dfsg-13))

Your message dated Mon, 26 Nov 2012 14:48:06 + with message-id and subject line Bug#694274: fixed in gmerlin 1.2.0~dfsg-3 has caused the Debian Bug report #694274, regarding libgmerlin-dev: missing Breaks+Replaces: gmerlin-data (<< 1.0.0~dfsg-13) to be marked as done. This means that you cla

Bug#681983: marked as done (gmerlin: should recommend (not suggest) gmerlin-encoders)

Your message dated Mon, 26 Nov 2012 14:48:06 + with message-id and subject line Bug#681983: fixed in gmerlin 1.2.0~dfsg-3 has caused the Debian Bug report #681983, regarding gmerlin: should recommend (not suggest) gmerlin-encoders to be marked as done. This means that you claim that the probl

liblscp_0.5.6-6_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 26 Nov 2012 13:52:33 + Source: liblscp Binary: liblscp-dbg liblscp-dev liblscp-doc liblscp6 Architecture: source amd64 all Version: 0.5.6-6 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Mainta

gmerlin_1.2.0~dfsg-3_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 26 Nov 2012 13:28:56 + Source: gmerlin Binary: gmerlin gmerlin-plugins-base gmerlin-doc gmerlin-data gmerlin-dbg libgmerlin0 libgmerlin-common libgmerlin-dev libgmerlin-doc Architecture: source all amd64 Version

Processing of liblscp_0.5.6-6_amd64.changes

liblscp_0.5.6-6_amd64.changes uploaded successfully to localhost along with the files: liblscp_0.5.6-6.dsc liblscp_0.5.6-6.debian.tar.gz liblscp-dbg_0.5.6-6_amd64.deb liblscp-dev_0.5.6-6_amd64.deb liblscp-doc_0.5.6-6_all.deb liblscp6_0.5.6-6_amd64.deb Greetings, Your Debian qu

Processing of gmerlin_1.2.0~dfsg-3_amd64.changes

gmerlin_1.2.0~dfsg-3_amd64.changes uploaded successfully to localhost along with the files: gmerlin_1.2.0~dfsg-3.dsc gmerlin_1.2.0~dfsg-3.debian.tar.gz gmerlin-doc_1.2.0~dfsg-3_all.deb gmerlin-data_1.2.0~dfsg-3_all.deb libgmerlin-doc_1.2.0~dfsg-3_all.deb gmerlin_1.2.0~dfsg-3_amd64.deb

Processed: tagging 690006

Processing commands for cont...@bugs.debian.org: > tags 690006 - wheezy Bug #690006 [src:fluidsynth] fluidsynth: FTBFS Removed tag(s) wheezy. > thanks Stopping processing here. Please contact me if you need assistance. -- 690006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690006 Debian Bug

Bug#694406: rosegarden: Exporting file with umlaut in file name, the name is incorrectly saved

Package: rosegarden Version: 1:12.04-1 Severity: important Tags: upstream fixed-upstream Control: forwarded -1 https://sourceforge.net/p/rosegarden/bugs/1375/ Dear Maintainer, exporting files (not saving, which works) with umlauts or other special characters in their file name saves the filename

Processed: rosegarden: Exporting file with umlaut in file name, the name is incorrectly saved

Processing control commands: > forwarded -1 https://sourceforge.net/p/rosegarden/bugs/1375/ Bug #694406 [rosegarden] rosegarden: Exporting file with umlaut in file name, the name is incorrectly saved Set Bug forwarded-to-address to 'https://sourceforge.net/p/rosegarden/bugs/1375/'. -- 694406: