Processed: Re: Bug#974737: transition: botan

2020-11-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + confirmed Bug #974737 [release.debian.org] transition: botan Added tag(s) confirmed. > forwarded -1 https://release.debian.org/transitions/html/auto-botan.html Bug #974737 [release.debian.org] transition: botan Set Bug forwarded-to-address to

Bug#974737: transition: botan

2020-11-15 Thread Sebastian Ramacher
Control: tags -1 + confirmed Control: forwarded -1 https://release.debian.org/transitions/html/auto-botan.html On 2020-11-14 13:37:03 +0100, László Böszörményi wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi

Bug#959469: buster-pu: package openssl/1.1.1g-1

2020-11-15 Thread Sebastian Andrzej Siewior
On 2020-11-15 20:59:18 [+0100], Paul Gevers wrote: > Hi Sebastian, Hi Paul, > I don't fully understand what you say here. We *do* run autopkgtests in > stable to check for issues. Yes, but the package does not use it in stable. Sebastian

Bug#959469: buster-pu: package openssl/1.1.1g-1

2020-11-15 Thread Paul Gevers
Hi Sebastian, On 15-11-2020 11:29, Sebastian Andrzej Siewior wrote: > The same error is also present in the stable version of swi-prolog. > However, this is not the only failure in the test suite (it also > complains about too small keys) and there is no debci for stable which > would cause a

Processed: Re: Bug#959469: buster-pu: package openssl/1.1.1g-1

2020-11-15 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 buster-pu: package openssl/1.1.1h-1 Bug #959469 [release.debian.org] buster-pu: package openssl/1.1.1g-1 Changed Bug title to 'buster-pu: package openssl/1.1.1h-1' from 'buster-pu: package openssl/1.1.1g-1'. -- 959469:

Bug#959469: buster-pu: package openssl/1.1.1g-1

2020-11-15 Thread Sebastian Andrzej Siewior
control: retitle -1 buster-pu: package openssl/1.1.1h-1 On 2020-05-02 22:34:40 [+0100], Adam D. Barratt wrote: > > > Do we have any feeling for how widespread such certificates might > > > be? > > > The fact that there have been two different upstream reports isn't > > > particularly comforting.