Le dimanche 14 août 2011 à 13:15 +0200, Boris Dušek a écrit : > Hello Jean,
Hi, > > Also I noticed your output module is named espeak-pico-generic, but the > official Debian package has this as just pico-generic. You should be using > the official pico-generic module for reporting bugs in the future, or > updating this bug report - even though I reproduced the problem fine with the > original pico-generic, it's better we use consistent modules. I didn't know this difference. Probably because I introduced this module manually before upgrading the system to sid and didn't know the new name and the new module (and didn't expected it exists). I use the official module now I know it exists. > W.r.t. upgrade to git, the right thing now is to try debugging the generic > module to see where the problem is and then fix it, instead of just upgrading > to git. Below are my thoughts about packaging current upstream git in Debian: ok perfect. That's right for me upgrading is easier because I don't know to do better than packaging, I don't know programming. But with your help... every debug is possible. :) > First if there will be upstream's git packaged for Debian, I would definitely > put it into experimental, not unstable, especially for the reason that I have > no experience about how stable and usable the current git is, and also have > no way to tell whether there will be any developments in the git version, > which would be good for providing subsequent updated versions of the package > in the future. I have no information about upcoming upstream release, the > better place to ask would be the speech-dispatcher mailing list. ok. > Note that if this was about packaging an upstream beta into experimental or > even unstable, it would be much more OK for me to package it. You're right. I don't know what does upstream too with speech-dispatcher and releases. Of course if we can debug current release, it's better. > Also providing libao is not a valid reason, since libao output is already > enabled in unstable (0.7.1-4) and testing (0.7.1-6). Ok I understand. > If you feel adventurous and really want to try out speech-dispatcher from > git, there is current speech-dispatcher git packaged (including native pico > module) for Ubuntu using automated daily build system - it's in the > ppa:dusek/spd-daily PPA. So you might try installing that directly with dpkg > or somehow with apt (I haven't tried), hopefully the Ubuntu package will be > usable in Debian. You also need to install libdotconf1.0 from that repository > first. Please let me (and/or the debian-accessibility list) know about your > results if you try it. Ok I'll try someday when I have time. If we fix the most important bugs in current release, I prefer helping this instead of adventures. Because I've other hard adventures with orca, gnome, etc. in sid. :) > But in general, the preferred approach by me to handling bugs is to fix > problem in current release than upgrading to git. Great, I can help for such approach by my tests. > If you want to discuss upgrade to git further, please open a new bug, it > really would confuse communication in this bug which is really about the > specific problem of generic module not working, and there might be other > reasons, apart from native pico module, that you or others might mention why > upgrading to git is a good thing. You can always mention that other bug > number in this bug. Ok right. When I wrote things were not clear in my mind, due to the thread about libao on debian-a11y ml. I guess with: SPEECHD_ADDRESS=unix_socket:/var/run/speech-dispatcher/speechd.sock spd-say you also experience the bug. Here the result is similar. I can try tracking logs if you need. Thanks for your answer, Regards, -- Jean-Philippe MENGUAL accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels Tél.: 06.76.34.93.37 Mail: mengualjean...@free.fr Site Web: http://www.accelibreinfo.eu
signature.asc
Description: Ceci est une partie de message numériquement signée
