Il 25/10/2012 15:37, Jakub Wilk ha scritto:
Please bump Standards-Version to 3.9.4. (But note that lintian isn't aware of
it yet, so you'll get a spurious newer-standards-version, which you should
ignore for the time
being.)
Done.
Would it be possible to enable parallel builds?
Done.
Please bump Standards-Version to 3.9.4. (But note that lintian isn't
aware of it yet, so you'll get a spurious newer-standards-version, which
you should ignore for the time being.)
Would it be possible to enable parallel builds?
g2p segfaults if the model doesn't exist:
$ phonetisaurus-g2p
* Giulio Paci giuliop...@gmail.com, 2012-10-22, 23:55:
1) Upstream make clean is not idempotent: it fails it there's
nothing to clean. Replacing rm with rm -f should fix this issue.
Fixed by using $(RM).
This fix appears to be part of 1002_remove_some_warnings.patch. Could
you move it into a
Il 24/10/2012 16:56, Jakub Wilk ha scritto:
* Giulio Paci giuliop...@gmail.com, 2012-10-22, 23:55:
1) Upstream make clean is not idempotent: it fails it there's nothing to
clean. Replacing rm with rm -f should fix this issue.
Fixed by using $(RM).
This fix appears to be part of
* Giulio Paci giuliop...@gmail.com, 2012-10-22, 23:55:
There's also a few dozens of compiler warnings. Is upstream aware of
them?
I just sent an email about them, along with a patch removing most of
them.
I think fix would be a better verb than remove here (in the patch
name and its
Il 23/10/2012 21:36, Jakub Wilk ha scritto:
* Giulio Paci giuliop...@gmail.com, 2012-10-22, 23:55:
There's also a few dozens of compiler warnings. Is upstream aware of them?
I just sent an email about them, along with a patch removing most of them.
I think fix would be a better verb than
* Giulio Paci giuliop...@gmail.com, 2012-10-21, 15:04:
What does --fst_field_separator exactly do? In my experiments it did
not affect phonetisaurus-align in any way.
Unfortunately I do not know most of the options of this program. I
asked upstream about this option.
Upstream replied that
Il 22/10/2012 17:48, Jakub Wilk ha scritto:
* Giulio Paci giuliop...@gmail.com, 2012-10-21, 15:04:
Is it mandatory to identify possibly useless flags and to hide them?
I understand that removing/hiding unneeded option might be infeasible, but I
would expect that these no-ops are documented
Errata corrige.
Il 22/10/2012 23:55, Giulio Paci ha scritto:
Il 22/10/2012 17:48, Jakub Wilk ha scritto:
* Giulio Paci giuliop...@gmail.com, 2012-10-21, 15:04:
Is it mandatory to identify possibly useless flags and to hide them?
I understand that removing/hiding unneeded option might be
* Giulio Paci giuliop...@gmail.com, 2012-10-23, 00:24:
2) cdbs doesn't ignore errors from make clean. This was reported in
#441020 over 5 years ago. (Sigh...)
I just read the bug report. Actually cdbs ignores errors in make clean.
So the problem here seems to be that building should fail on
Il 21/10/2012 04:39, Giulio Paci ha scritto:
Il 20/10/2012 22:55, Jakub Wilk ha scritto:
What does --fst_field_separator exactly do? In my experiments it did not
affect phonetisaurus-align in any way.
Unfortunately I do not know most of the options of this program. I asked
upstream about
* Giulio Paci giuliop...@gmail.com, 2012-10-20, 00:00:
I just had a look to the already opened bugs and I found that there is
an RFP bug for utfcpp:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552618
Do you think I should do anything else (e.g., reply to the bug with the
maintainers of
Il 20/10/2012 22:55, Jakub Wilk ha scritto:
* Giulio Paci giuliop...@gmail.com, 2012-10-20, 00:00:
I just had a look to the already opened bugs and I found that there is an
RFP bug for utfcpp:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552618
Do you think I should do anything else
Hi!
Il 17/10/2012 16:19, Jakub Wilk ha scritto:
* Giulio Paci giuliop...@gmail.com, 2012-10-17, 00:05:
How can I set Built-Using field? Should I set it by hand? Is it possible
to set it automatically?
Value of this field must be generated at build time. Unfortunately, there
are currently
* Giulio Paci giuliop...@gmail.com, 2012-10-17, 00:05:
How can I set Built-Using field? Should I set it by hand? Is it
possible to set it automatically?
Value of this field must be generated at build time. Unfortunately,
there are currently no convenient tools to help you with this task;
see
* Giulio Paci giuliop...@gmail.com, 2012-10-13, 15:54:
How can I set Built-Using field? Should I set it by hand? Is it
possible to set it automatically?
Value of this field must be generated at build time. Unfortunately,
there are currently no convenient tools to help you with this task; see
Hi!
Il 16/10/2012 17:12, Jakub Wilk ha scritto:
* Giulio Paci giuliop...@gmail.com, 2012-10-13, 15:54:
How can I set Built-Using field? Should I set it by hand? Is it possible to
set it automatically?
Value of this field must be generated at build time. Unfortunately, there are
currently
Hi!
There has been a new phonetisaurus release (0.6).
All the patches have been applied upstream, the backup file in sparsehash has
been removed, FstPathFinder.* have been rewritten from scratch.
I updated the Debian package files accordingly. All the phonetisaurus files
have a
Hi!
There has been a new phonetisaurus release (0.6).
All the patches have been applied upstream, the backup file in sparsehash has
been removed, FstPathFinder.* have been rewritten from scratch.
I updated the Debian package files accordingly. All the phonetisaurus files
have a
Hi!
Thank you for your review.
Il 13/10/2012 00:02, Jakub Wilk ha scritto:
* Giulio Paci giuliop...@gmail.com, 2012-10-11, 03:52:
git://git.debian.org/git/collab-maint/phonetisaurus.git.
Last but not least, why do you need to recover this file? It looks like it
shouldn't have been
* Giulio Paci giuliop...@gmail.com, 2012-10-11, 03:52:
git://git.debian.org/git/collab-maint/phonetisaurus.git.
The ugly hack in debian/rules is indeed ugly. :)
I definitively agree.
I found a cleaner way to do that and applied it (by setting
DEB_CLEAN_EXCLUDE in debian/rules).
Much better,
* Giulio Paci giuliop...@gmail.com, 2012-10-09, 02:16:
git://git.debian.org/git/collab-maint/phonetisaurus.git.
The ugly hack in debian/rules is indeed ugly. :)
Could you split it into multiple lines? 410 characters is really too
long.
Why is the filename between two -e expressions?
Last
Il 10/10/2012 22:59, Jakub Wilk ha scritto:
* Giulio Paci giuliop...@gmail.com, 2012-10-09, 02:16:
git://git.debian.org/git/collab-maint/phonetisaurus.git.
The ugly hack in debian/rules is indeed ugly. :)
I definitively agree.
I found a cleaner way to do that and applied it (by setting
Hi Jakub!
Finally a new upstream release of phonetisaurus came out with the
pending issues solved (i.e., non-free data files have been dropped, the only
remaining script does not
have an extension).
I just updated the Debian package on
24 matches
Mail list logo
