Felix Lechner dixit:
>Uploaded, although I am still looking for it on the buildds:
First it must be ACCEPTED, then the dak run for incoming must
run, then B-Ds are checked, then it gets into Needs-Build status,
and only then the buildds pick it up.
It’s there now: https://buildd.debian.org/statu
Dixi quod…
>It’s there now: https://buildd.debian.org/status/package.php?p=wolfssl
… and already FTBFSing on s390x:
/usr/bin/ld: src/.libs/libwolfssl.so: undefined reference to `ByteReverseWords'
bye,
//mirabilos
--
[16:04:33] bkix: "veni vidi violini"
[16:04:45] bkix: "ich kam, sah und vergei
Hi Thorsten,
Uploaded, although I am still looking for it on the buildds:
> wolfssl_4.5.0+dfsg-1_source.changes uploaded successfully to localhost
> along with the files:
> wolfssl_4.5.0+dfsg-1.dsc
> wolfssl_4.5.0+dfsg.orig.tar.xz
> wolfssl_4.5.0+dfsg-1.debian.tar.xz
> wolfssl_4.5.0+dfsg-
Felix Lechner dixit:
>> Is there anything I can help to ensure it’s not autoremoved?
>
>I just saw it this morning and plan to upload 4.5.0 later today. From
>what I understand, closing #969663 should postpone the autoremoval
>process?
Thanks!
The autoremoval will go on until a version with #969
Hi Thorsten,
> Is there anything I can help to ensure it’s not autoremoved?
I just saw it this morning and plan to upload 4.5.0 later today. From
what I understand, closing #969663 should postpone the autoremoval
process?
Kind regards
Felix
Debian testing autoremoval watch dixit:
>polyphone 2.2.0.20200612+dfsg1-1 is marked for autoremoval from testing on
>2020-10-20
>
>It (build-)depends on packages with these RC bugs:
>969663: wolfssl: CVE-2020-12457 CVE-2020-15309 CVE-2020-24585 CVE-2020-24613
> https://bugs.debian.org/969663
Is
6 matches
Mail list logo
