Adam Dickmeiss wrote:
> Adam Dickmeiss wrote:
>> I don't know why tst_oid fails on arm. A stack strace would be
>> appreciated.. But failing, just run tst_oid and send me the contents
>> of tst_oid.log .
>>
>> / Adam
>>
>>
> OK.. It's tst_icu_I18N that fails.. A backtrace or just tst_icu_I18N.log
>
Adam Dickmeiss wrote:
I don't know why tst_oid fails on arm. A stack strace would be
appreciated.. But failing, just run tst_oid and send me the contents of
tst_oid.log .
/ Adam
OK.. It's tst_icu_I18N that fails.. A backtrace or just tst_icu_I18N.log
might be useful..
/ Adam
--
To UN
I don't know why tst_oid fails on arm. A stack strace would be
appreciated.. But failing, just run tst_oid and send me the contents of
tst_oid.log .
/ Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi,
[I'm CCing Adam (upstream) in case he has any comments]
Regis Boudin wrote:
> Package: yaz
> Version: 3.0.26+debian.1-1
>
> Hi,
>
> yaz FTBFS on arm, with a segfault in one of the tests run at the end of the
> build.
You are right. I just saw that two builds have been attempted[1] and th
Package: yaz
Version: 3.0.26+debian.1-1
Hi,
yaz FTBFS on arm, with a segfault in one of the tests run at the end of the
build.
This is fairly annoying for me, as it means tellico is stuck at the moment
and
can't transition to testing with the soname change.
Thanks,
Regis
--
To UNSUBSCRIBE
5 matches
Mail list logo