Bug#1008263: pcmemtest is goging to replace memtest86+ upstream
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 has shifted to memtest86+... Instead of maintaining this package, it seems to me efforts should be made to bring memtest86+ 6 into bookworm (which it is currently not, it seems stuck in experimental). A fair way to keep this package out of bookworm would be to raise the severity of this bug report to `serious`, which should kick it out of bookworm in no time. Then, of course, an RM request would be appropriate as well. Thanks for maintaining those packages! A. -- Blind respect for authority is the greatest enemy of truth. - Albert Einstein
Bug#1008263: pcmemtest is goging to replace memtest86+ upstream
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: right now pcmemtest *will* ship with Debian > bookworm, and I don't think that's right if upstream development has > shifted to memtest86+... > > Instead of maintaining this package, it seems to me efforts should be > made to bring memtest86+ 6 into bookworm (which it is currently not, > it > seems stuck in experimental). > > A fair way to keep this package out of bookworm would be to raise the > severity of this bug report to `serious`, which should kick it out of > bookworm in no time. > > Then, of course, an RM request would be appropriate as well. > > Thanks for maintaining those packages! > > A. > Thanks for the reminder. I wasn't sure if I should wait until the new memtest86+ gets out of beta and uploaded to unstable. But yeah, maybe it's better to just file the RM now Regards, Felix
Bug#1008263: pcmemtest is goging to replace memtest86+ upstream
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: > https://github.com/martinwhitaker/pcmemtest/issues/13#issuecomment-1079164505 > > The current pcmemtest will "replace" memtest86+ (AFAIU under the name > of the > latter) in its next major version. > > > Cheers, > Chris. Hi Chris, thanks for your report. I already agreed with Fabio to Co-Maintain memtest86+ with him. Actually it's memtest86+ which will replace pcmemtest. pcmemtest won't be developed any further. 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 Cheers, Felix
Bug#1008263: pcmemtest is goging to replace memtest86+ upstream
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 will replace pcmemtest. > pcmemtest won't be developed any further. Well the codebase from the latter and the name from the former ;-) Cheers, Chris.
Bug#1008263: pcmemtest is goging to replace memtest86+ upstream
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: https://github.com/martinwhitaker/pcmemtest/issues/13#issuecomment-1079164505 The current pcmemtest will "replace" memtest86+ (AFAIU under the name of the latter) in its next major version. Cheers, Chris.
