Bug#928381: unblock: stunnel4/3:5.54~b3-1

2019-05-31 Thread Sam Hartman
> "Peter" == Peter Pentchev  writes:

Peter> On Thu, May 30, 2019 at 09:00:18PM +0200, Paul Gevers wrote:
>> Hi Peter,
>> 
>> On 30-05-2019 11:24, Peter Pentchev wrote:
>> > Just for my information, is there a chance that this upgrade
>> could be > allowed later on during the buster lifecycle as a
>> stable update?
>> 
>> If it would be suitable for a stable release point update, it
>> would be suitable now. We're close to releasing, but not that
>> close yet.

Peter> So what you're saying is that stunnel4 will have a bug that
Peter> leads to random crashes all through the buster lifetime?
Peter> That's...  a bit unfortunate, I guess...

Well, if you can produce a small targeted fix, and argue that the bug is
at least important priority,
then you can ask for that small fix to be reviewed now or later.



Bug#928381: unblock: stunnel4/3:5.54~b3-1

2019-05-31 Thread Peter Pentchev
On Fri, May 31, 2019 at 11:14:15AM +0300, Peter Pentchev wrote:
> On Thu, May 30, 2019 at 09:00:18PM +0200, Paul Gevers wrote:
> > Hi Peter,
> > 
> > On 30-05-2019 11:24, Peter Pentchev wrote:
> > > Just for my information, is there a chance that this upgrade could be
> > > allowed later on during the buster lifecycle as a stable update?
> > 
> > If it would be suitable for a stable release point update, it would be
> > suitable now. We're close to releasing, but not that close yet.
> 
> So what you're saying is that stunnel4 will have a bug that leads to
> random crashes all through the buster lifetime? That's...
> a bit unfortunate, I guess...

I'm sorry, I shouldn't have sent that e-mail, it probably comes off
a bit... bad. I'm looking at options for a targeted bugfix for
the threading issue; thanks for your time and patience in considering
this upgrade and explaining the situation!

G'luck,
Peter

-- 
Peter Pentchev  roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature


Bug#928381: unblock: stunnel4/3:5.54~b3-1

2019-05-31 Thread Peter Pentchev
On Thu, May 30, 2019 at 09:00:18PM +0200, Paul Gevers wrote:
> Hi Peter,
> 
> On 30-05-2019 11:24, Peter Pentchev wrote:
> > Just for my information, is there a chance that this upgrade could be
> > allowed later on during the buster lifecycle as a stable update?
> 
> If it would be suitable for a stable release point update, it would be
> suitable now. We're close to releasing, but not that close yet.

So what you're saying is that stunnel4 will have a bug that leads to
random crashes all through the buster lifetime? That's...
a bit unfortunate, I guess...

G'luck,
Peter

-- 
Peter Pentchev  roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature


Bug#928381: unblock: stunnel4/3:5.54~b3-1

2019-05-30 Thread Paul Gevers
Hi Peter,

On 30-05-2019 11:24, Peter Pentchev wrote:
> Just for my information, is there a chance that this upgrade could be
> allowed later on during the buster lifecycle as a stable update?

If it would be suitable for a stable release point update, it would be
suitable now. We're close to releasing, but not that close yet.

Paul



signature.asc
Description: OpenPGP digital signature


Bug#928381: unblock: stunnel4/3:5.54~b3-1

2019-05-30 Thread Peter Pentchev
On Thu, May 30, 2019 at 11:08:02AM +0200, Paul Gevers wrote:
> tags 928381 wontfix
> thanks
> 
> Hi Peter,
> 
> On Fri, 3 May 2019 13:48:43 +0300 Peter Pentchev  wrote:
> > I am aware that new upstream versions are not usually allowed in during
> > a release freeze; however, the upstream author has said that the changes
> > in the stunnel internal operation to fix the thread interlock problem
> > are too extensive to be easily backported :(
> 
> We're too uncomfortable with all the changes (they are too big to
> properly review). I recognize that the bug isn't pretty, but introducing
> new ones at this stage is even less so (that's why we have the freeze).

Thanks for considering this and for the reply; I cannot say that
I didn't expect such a resolution at all.

Just for my information, is there a chance that this upgrade could be
allowed later on during the buster lifecycle as a stable update?

Thanks for everything you are doing for Debian!

G'luck,
Peter

-- 
Peter Pentchev  roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature


Bug#928381: unblock: stunnel4/3:5.54~b3-1

2019-05-03 Thread Peter Pentchev
On Fri, May 03, 2019 at 01:48:43PM +0300, Peter Pentchev wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hi,
> 
> I am requesting permission to upload stunnel4/3:5.54~b3-1 to unstable
> and to have it unblocked for testing migration. The reason is that
> this is the first upstream version of stunnel that contains a fix for
> a problem involving threads and OpenSSL that may lead to a crash in
> certain situations - see #880659 for more information.

I forgot to mention that stunnel4/3:5.54~b3-1 is in experimental as
of yesterday; it is built and installed pretty much everywhere, I am
currently investigating the hppa build failure, although I couldn't
reproduce it easily in a panama.d.o schroot.

G'luck,
Peter

-- 
Peter Pentchev  roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature