Bug#857948: marked as done (gsequencer: missing mutex locks might crash the application)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857948: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857948, regarding gsequencer: missing mutex locks might crash the application to be marked as done. This means that you claim that the prob

Bug#857947: marked as done (gsequencer: possible data-race as clearing buffer of soundcard)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857947: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857947, regarding gsequencer: possible data-race as clearing buffer of soundcard to be marked as done. This means that you claim that the p

Bug#857937: marked as done (gsequencer: memory leaks while g_timeout_add() function in GUI)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857937: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857937, regarding gsequencer: memory leaks while g_timeout_add() function in GUI to be marked as done. This means that you claim that the p

Bug#857936: marked as done (gsequencer: duplicated flag AGS_MIDI_PARSER_EOT makes header useless)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857936: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857936, regarding gsequencer: duplicated flag AGS_MIDI_PARSER_EOT makes header useless to be marked as done. This means that you claim that

Bug#857935: marked as done (gsequencer: SIGSEGV as doing NULL pointer dereference as restoring AgsFFPlayer)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857935: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857935, regarding gsequencer: SIGSEGV as doing NULL pointer dereference as restoring AgsFFPlayer to be marked as done. This means that you

Bug#857934: marked as done (gsequencer: configuration in-place broken thread frequency)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857934: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857934, regarding gsequencer: configuration in-place broken thread frequency to be marked as done. This means that you claim that the probl

Bug#857931: marked as done (gsequencer: AgsSynth possible division by zero by oscillator)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857931: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857931, regarding gsequencer: AgsSynth possible division by zero by oscillator to be marked as done. This means that you claim that the pro

Bug#857933: marked as done (gsequencer: The MIDI connection dialog is not provided by restoring AgsLv2Bridge)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857933: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857933, regarding gsequencer: The MIDI connection dialog is not provided by restoring AgsLv2Bridge to be marked as done. This means that y

Bug#857915: marked as done (gsequencer: should link libraries using LIBADD instead of LDFLAGS)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857915: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857915, regarding gsequencer: should link libraries using LIBADD instead of LDFLAGS to be marked as done. This means that you claim that th

Bug#857930: marked as done (gsequencer: Wrong GParamSpec of mixed properties containing GObject and GList)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857930: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857930, regarding gsequencer: Wrong GParamSpec of mixed properties containing GObject and GList to be marked as done. This means that you

Bug#857910: marked as done (gsequencer: GObject::dispose() is not implemented)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857910: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857910, regarding gsequencer: GObject::dispose() is not implemented to be marked as done. This means that you claim that the problem has be

gsequencer_0.8.0-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 01 May 2017 22:31:04 +0200 Source: gsequencer Binary: gsequencer gsequencer-doc libags0 libags-audio0 libags-gui0 libags-dev libags-audio-dev libags-gui-dev libags-doc libags-audio-doc libags-gui-doc Architecture:

Processing of gsequencer_0.8.0-1_amd64.changes

gsequencer_0.8.0-1_amd64.changes uploaded successfully to localhost along with the files: gsequencer_0.8.0-1.dsc gsequencer_0.8.0.orig.tar.gz gsequencer_0.8.0-1.debian.tar.xz gsequencer_0.8.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

libopenmpt_0.2.8043~beta23-1_source.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 01 May 2017 20:16:49 +0100 Source: libopenmpt Binary: openmpt123 libopenmpt0 libopenmpt-dev libopenmpt-doc libopenmpt-modplug1 libopenmpt-modplug-dev Architecture: source Version: 0.2.8043~beta23-1 Distribution: e

Processing of libopenmpt_0.2.8043~beta23-1_source.changes

libopenmpt_0.2.8043~beta23-1_source.changes uploaded successfully to localhost along with the files: libopenmpt_0.2.8043~beta23-1.dsc libopenmpt_0.2.8043~beta23.orig.tar.gz libopenmpt_0.2.8043~beta23-1.debian.tar.xz libopenmpt_0.2.8043~beta23-1_source.buildinfo Greetings, Your Deb

Bug#861595: audacious wrong mimetype

Package: audacious Version: 3.7.2-1+b1 Severity: important Dear Maintainer, the current version of audacious sets itself as the default application for inode/directory this breaks many packages(for example firefox>toolbar>downloadbutton>open containing folder will become unusable since firefox