* Giulio Paci , 2016-03-08, 22:24:
we do seem to have an s390x buildd with only 3GB of RAM:
https://db.debian.org/machines.cgi?host=zemlinsky
So we may have a failure there. :-/
Perhaps. But with the current limits, the package would be built with
-j1 there, so reducing parallelism further w
Hi Jakub,
On 08/03/2016 19:00, Jakub Wilk wrote:
> * Giulio Paci , 2016-03-07, 17:44:
>> I added a README.source
>
> I don't like the phrase "build environment must not change during automated
> builds". It makes me think of that you must not install or remove packages
> when you package is
> b
* Giulio Paci , 2016-03-07, 17:44:
I added a README.source
I don't like the phrase "build environment must not change during
automated builds". It makes me think of that you must not install or
remove packages when you package is building, which is technically true,
but certainly not what yo
A quick update.
On 07/03/2016 17:44, Giulio Paci wrote:
> 1005_kaldi_patch.patch has been submitted, but it is still under revision and
> may require some work.
>
> On Friday I discovered an issue with this patch that, randomly, prevents
> tests to complete.
> I am not able to deal with the iss
On 04/03/2016 21:12, Jakub Wilk wrote:
> * Giulio Paci , 2016-03-02, 09:45:
>> - added a new patch 1008_fix_linking_issues.patch, replacing and extending
>> unresolved_symbols.diff.
> At the moment there's nothing in the changelog indicating any relation
> between 1008_fix_linking_issues.patch an
* Giulio Paci , 2016-03-02, 09:45:
- added a new patch 1008_fix_linking_issues.patch, replacing and
extending unresolved_symbols.diff.
At the moment there's nothing in the changelog indicating any relation
between 1008_fix_linking_issues.patch and unresolved_symbols.diff.
When you saying you
On 29/02/2016 16:37, Jakub Wilk wrote:
> * Giulio Paci , 2016-02-29, 13:24:
>> 1) I need to package latest version, as the differences are not trivial
>> anymore;
>> 2) I have to convince upstream stop these bad practices (however it seems
>> very hard, as they stop for one release and then start
* Giulio Paci , 2016-02-29, 13:24:
1) I need to package latest version, as the differences are not trivial
anymore;
2) I have to convince upstream stop these bad practices (however it
seems very hard, as they stop for one release and then start again a
immediately after);
3) *mangle mechanism s
Hi Jakub,
On 29/02/2016 00:27, Jakub Wilk wrote:
> * Giulio Paci , 2016-02-28, 23:19:
>> I packaged
>> "http://openfst.org/twiki/bin/viewfile/FST/FstDownload?filename=openfst-1.5.1.tar.gz;rev=1";
>> and noticed the behaviour when upstream was at
>> "http://openfst.org/twiki/bin/viewfile/FST/FstD
Hi Giulio!
* Giulio Paci , 2016-02-28, 23:19:
I packaged
"http://openfst.org/twiki/bin/viewfile/FST/FstDownload?filename=openfst-1.5.1.tar.gz;rev=1";
and noticed the behaviour when upstream was at
"http://openfst.org/twiki/bin/viewfile/FST/FstDownload?filename=openfst-1.5.1.tar.gz;rev=3";.
Ri
Hi Jakub,
On 27/02/2016 19:04, Jakub Wilk wrote:
> [When filing a bug, please use X-Debbugs-CC instead of plain CC, so that the
> copied person receives the message with bug number from the BTS.]
Thank you for the hint. I will do that next time.
> * Giulio Paci , 2016-02-16, 01:03:
>> https://a
Control: owner -1 !
Hi Giulio!
[When filing a bug, please use X-Debbugs-CC instead of plain CC, so that
the copied person receives the message with bug number from the BTS.]
* Giulio Paci , 2016-02-16, 01:03:
https://anonscm.debian.org/git/collab-maint/openfst.git
I had only a very quick l
Package: sponsorship-requests
Severity: wishlist
Dear Jakub,
I am looking for a sponsor for my package "openfst", that you sponsored in
the past
and that recently I managed to update.
* Package name: openfst
Version : 1.5.1-1
Upstream Author : Cyril Allauzen , Michael
13 matches
Mail list logo
