Re: libespeak / espeakup

2014-07-11 Thread Samuel Thibault
Samuel Thibault, le Fri 11 Jul 2014 11:58:31 +0200, a écrit : > Samuel Thibault, le Fri 11 Jul 2014 11:04:02 +0200, a écrit : > > Cyril Brulebois, le Mon 07 Jul 2014 02:44:03 +0200, a écrit : > > > Right now we have a cronned edos/dose job that looks for uninstallable > > > udebs and let me know wh

Re: libespeak / espeakup

2014-07-11 Thread Samuel Thibault
Samuel Thibault, le Fri 11 Jul 2014 11:04:02 +0200, a écrit : > Cyril Brulebois, le Mon 07 Jul 2014 02:44:03 +0200, a écrit : > > Right now we have a cronned edos/dose job that looks for uninstallable > > udebs and let me know when situation changes (be it for better or for > > worse); so at least

Re: libespeak / espeakup

2014-07-11 Thread Samuel Thibault
Cyril Brulebois, le Mon 07 Jul 2014 02:44:03 +0200, a écrit : > Samuel Thibault (2014-05-22): > > Some time ago, I realized that espeakup-udeb needs to be rebuilt on > > each new upstream libespeak upload, because libespeak needs an exact > > match between the library version and the data version,

Re: libespeak / espeakup

2014-07-06 Thread Cyril Brulebois
[Sorry for the lag.] Samuel Thibault (2014-05-22): > Some time ago, I realized that espeakup-udeb needs to be rebuilt on > each new upstream libespeak upload, because libespeak needs an exact > match between the library version and the data version, and espeakup > is linked statically against lib

libespeak / espeakup

2014-05-21 Thread Samuel Thibault
Hello, Some time ago, I realized that espeakup-udeb needs to be rebuilt on each new upstream libespeak upload, because libespeak needs an exact match between the library version and the data version, and espeakup is linked statically against libespeak. So whenever we get a new upstream version of