Comment 32 for bug 1876157

Revision history for this message
Fantu (fantonifabio) wrote (last edit ):

I already know and as already told upstream developer already working contacting developers of these forks for collaborate and try to merge works of all upstream.
For now I'll wait progress of this instead wasting time applying, adapt (for 5.31b) and testing patches from forks now, I'll apply them only if there will be important issue that can't wait.
I have other projects/packages I contribute to, I only recently became a maintainer of memtest86+ after investing many hours in the last 2 months to update it, fix a lot of problems and make some other improvements.
If there are still important issues (with latest version, 5.31b+dfsg-4) let me know please, for now on all cases where old version was not working the latest is on my tests and the only thing not working is the multiboot (which is secondary and disabled by default) which I am not able to fix quickly (I have no knowledge about it) and so I left it like this (after adapting the old patch to at least fix the memory detection) to better invest the time in other parts and projects where I have more knowledge.
If anyone wants to contribute a patch that fixes it is welcome and I would apply immediately (after testing if it doesn't cause regressions) and I will do new build.