Bug#528701: Ticket created upstream

I can confirm that the bug is present in the latest version of fluidsynth upstream, and I have created a ticket upstream as well. You can follow this bug report here: http://fluidsynth.resonance.org/trac/ticket/45 -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a

lib3ds_1.3.0-3_i386.changes ACCEPTED

Accepted: lib3ds-1-3_1.3.0-3_i386.deb to pool/main/lib3/lib3ds/lib3ds-1-3_1.3.0-3_i386.deb lib3ds-dev_1.3.0-3_i386.deb to pool/main/lib3/lib3ds/lib3ds-dev_1.3.0-3_i386.deb lib3ds_1.3.0-3.diff.gz to pool/main/lib3/lib3ds/lib3ds_1.3.0-3.diff.gz lib3ds_1.3.0-3.dsc to pool/main/lib3/lib3ds/lib

Processing of lib3ds_1.3.0-3_i386.changes

lib3ds_1.3.0-3_i386.changes uploaded successfully to localhost along with the files: lib3ds_1.3.0-3.dsc lib3ds_1.3.0-3.diff.gz lib3ds-1-3_1.3.0-3_i386.deb lib3ds-dev_1.3.0-3_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@list

Bug#528701: One more comment

I've forgotten to add, that the commands used in my config file work perfectly, when entered in the fluidsynth shell. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#528701: fluidsynth segfaults when loading the configuration file

Package: fluidsynth Version: 1.0.8-2 Severity: important When I try to run fluidsynth letting it to read the configuration from the file, it segfaults at the first command related to the MIDI router. If e.g. my config files looks like this: flsynth.conf: == loa

Службa доставки почты

Можно ли экономить на рекламе? ДА! Pеклама в интернете стоит намного дешевле стандартных видов рекламы, и эффективность в несколько раз выше - это доказанный факт! Обращайтесь к нам, и Вы сэкономите свои средства. Наш Телефон : (495)502 61 85 ICQ: 409571 759 Любые формы оплаты.

spline 1.1-13 MIGRATED to testing

FYI: The status of the spline source package in Debian's testing distribution has changed. Previous version: 1.1-11 Current version: 1.1-13 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive la

rpncalc 1.36.8 MIGRATED to testing

FYI: The status of the rpncalc source package in Debian's testing distribution has changed. Previous version: 1.36.6 Current version: 1.36.8 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive l

gvidm 0.8-9 MIGRATED to testing

FYI: The status of the gvidm source package in Debian's testing distribution has changed. Previous version: 0.8-8 Current version: 0.8-9 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later

Гоpящие Ра{LET: c,с}cи от ЧOOOp!

Сколько Вы т{LET: р,p}атите на pл{LET: а,a}му? Хотите т{LET: р,p}атить меньше? Обр{LET: а,a}щайтесь к н{LET: а,a}м, мы сделaем В{LET: а,a}шу {LET: кламную kамп{LET: а,a}нию д{LET: е,e}ш{LET: е,e}вле и эфф{LET: е,e}ктивнее. Соо{LET: б,6}щите всем о своем тов{LET: а,a}ре, ведь чем больше людей о н

Bug#528669: init script failing when specter already running or already stopped

Package: specter Version: 1.4-3 Severity: normal Tags: patch Init script returns a non zero status when called to stop / start an already stopped / started specter daemon. This has unexcepted behaviour when trying to restart specter or to uninstall it when daemon is already stopped. An example ou