[rt.cpan.org #132811] Win32: Crash a week after start

2020-06-14 Thread Roderich Schupp via RT
Sun Jun 14 11:49:03 2020: Request 132811 was acted upon. Transaction: Correspondence added by RSCHUPP Queue: PAR-Packer Subject: Win32: Crash a week after start Broken in: (no value) Severity: (no value) Owner: Nobody Requestors: ralf.neuba...@wido.bv.aok.de

[rt.cpan.org #132811] Win32: Crash a week after start

2020-06-14 Thread Roderich Schupp via RT
Sun Jun 14 11:24:18 2020: Request 132811 was acted upon. Transaction: Correspondence added by RSCHUPP Queue: PAR-Packer Subject: Win32: Crash a week after start Broken in: (no value) Severity: (no value) Owner: Nobody Requestors: ralf.neuba...@wido.bv.aok.de

RE: [rt.cpan.org #132811] Win32: Crash a week after start

2020-06-14 Thread Neubauer, Ralf via RT
Sun Jun 14 16:21:45 2020: Request 132811 was acted upon. Transaction: Correspondence added by ralf.neuba...@wido.bv.aok.de Queue: PAR-Packer Subject: RE: [rt.cpan.org #132811] Win32: Crash a week after start Broken in: (no value) Severity: (no value) Owner: Nobody

Re: [rt.cpan.org #132811] Win32: Crash a week after start

2020-06-14 Thread Oliver Betz
Neubauer, Ralf wrote: [PAR_TEMP] What is your concept for getting rid of old PAR_TEMP locations once you get (or create) an updated version of the application or just stop using it? My simple concept is not to hide the unpacking but tell the users the truth: There is a bunch of files