Bug#969663: polyphone is marked for autoremoval from testing

2020-09-15 Thread Thorsten Glaser
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/status/package.php?p=wolfssl
(ports will pick it up in a bit)

bye,
//mirabilos
-- 
„Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund,
mksh auf jedem System zu installieren.“
-- XTaran auf der OpenRheinRuhr, ganz begeistert
(EN: “[…]uhr.gz is a reason to install mksh on every system.”)



Bug#969663: polyphone is marked for autoremoval from testing

2020-09-15 Thread Thorsten Glaser
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 vergeigte"...



Bug#969663: polyphone is marked for autoremoval from testing

2020-09-15 Thread Felix Lechner
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-1_source.buildinfo
>
> Greetings,
>
> Your Debian queue daemon (running on host usper.debian.org)

Kind regards
Felix Lechner



Bug#969663: polyphone is marked for autoremoval from testing

2020-09-15 Thread Thorsten Glaser
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 #969663 fixed
enters testing, but that is why such a long advance notice is
given (five weeks or so).

bye,
//mirabilos
-- 
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend.   -- Andreas Bogk über boehm-gc in d.a.s.r



Bug#969663: polyphone is marked for autoremoval from testing

2020-09-15 Thread Felix Lechner
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



Bug#969663: polyphone is marked for autoremoval from testing

2020-09-15 Thread Thorsten Glaser
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 there anything I can help to ensure it’s not autoremoved?

Thanks,
//mirabilos
-- 
  “Having a smoking section in a restaurant is like having
  a peeing section in a swimming pool.”
-- Edward Burr