On 2022-03-25 17:12:42, Felix Zielcke wrote:
> I'm not yet sure if I should file a removal bug for pcmemtest.
> But I think I'll just wait and see if that is necessary
I think you should: right now pcmemtest *will* ship with Debian
bookworm, and I don't think that's right if upstream development
Control: severity -1 serious
Am Freitag, dem 09.09.2022 um 10:55 -0400 schrieb Antoine Beaupré:
> On 2022-03-25 17:12:42, Felix Zielcke wrote:
> > I'm not yet sure if I should file a removal bug for pcmemtest.
> > But I think I'll just wait and see if that is necessary
>
> I think you should:
Am Freitag, dem 25.03.2022 um 16:59 +0100 schrieb Christoph Anton
Mitterer:
> Hey.
>
> Just for you information:
>
> Memtest86+ upstream (Samuel D. ) had already told me that
> a while
> ago... and pcmemtest upstream seems to have confirmed it now:
>
On Fri, 2022-03-25 at 17:12 +0100, Felix Zielcke wrote:
> thanks for your report.
> I already agreed with Fabio to Co-Maintain memtest86+ with him.
Ah great... well I guess if you're anyway already aware of this, than
you can also just close this bug right away.
> Actually it's memtest86+ which
Source: pcmemtest
Version: 1.5-3
Severity: normal
X-Debbugs-Cc: fantonifa...@tiscali.it
Hey.
Just for you information:
Memtest86+ upstream (Samuel D. ) had already told me that a while
ago... and pcmemtest upstream seems to have confirmed it now:
5 matches
Mail list logo
