Bug 16261

Summary:	scanmem: version 0.13 is outdated and full of bugs - use 0.15.2
Product:	Mageia	Reporter:	Sebastian Parschauer <s.parschauer>
Component:	RPM Packages	Assignee:	Shlomi Fish <shlomif>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	marja11
Version:	5
Target Milestone:	---
Hardware:	All
OS:	Linux
URL:	https://github.com/scanmem/scanmem/issues/119
Whiteboard:
Source RPM:	scanmem-0.13-3.mga5.src.rpm	CVE:
Status comment:

Description Sebastian Parschauer 2015-07-01 01:02:43 CEST

Description of problem:

The scanmem/GameConqueror version 0.13 is completely outdated (more than 4 years old) and contains tons of bugs. At upstream we can't support this version any more as development speed stepped up.

This is why we recommend to update to v0.15.2. We've optimized performance so that we scan in half the time than before. Memory alignment trouble on ARM systems is fixed. We've fixed all the nasty bugs in the GUI making it working with Python 3 as good as with Python 2. While testing we've found and fixed more bugs affecting both.
We have a couple of cool new features like ASLR/PIC/PIE, Android and endianness support.

Furthermore, Google-Code is closing. So upstream is now located on GitHub:
https://github.com/scanmem/scanmem

Please pick up version v0.15.2:
https://github.com/scanmem/scanmem/releases

Version-Release number of selected component (if applicable): 0.13-3


How reproducible:

E.g. try to use GameConqueror with Python 3 or use the differential number search in the GUI or lock a value and end the game. All this causes major problems with version 0.13.


Reproducible: 

Steps to Reproduce:

Comment 1 Samuel Verschelde 2015-07-01 12:48:31 CEST

Thanks for the report. Assigning to our maintainer.

Assignee: bugsquad => shlomif
Summary: scanmem: version 0.13 is outdated - use 0.15.2 => scanmem: version 0.13 is outdated and full of bugs - use 0.15.2
Severity: normal => major

Comment 2 Shlomi Fish 2015-07-01 13:19:01 CEST

(In reply to Samuel VERSCHELDE from comment #1)
> Thanks for the report. Assigning to our maintainer.

scanmem-0.15.2 was already made available in Cauldron. Should we provide an update for the Mageia 5 package too?

Comment 3 Sebastian Parschauer 2015-07-01 13:22:35 CEST

Yes, would make sense. I really want to get rid of that old version and that people test what we've achieved recently. Thanks!

Comment 4 Samuel Verschelde 2015-07-01 14:16:55 CEST

(In reply to Sebastian Parschauer from comment #3)
> Yes, would make sense. I really want to get rid of that old version and that
> people test what we've achieved recently. Thanks!

Our updates policy favours patching bugs rather than updating to a newer version, in order to avoid important changes. However, I think you can ask an exception to be made here because the version shipped with Mageia 5 is so old and has so many bugs. Could users have bad surprises when going from 0.13 to 0.15.2?

Comment 5 Sebastian Parschauer 2015-07-01 14:27:22 CEST

In general I also prefer maintaining stable branches and separating bugfixes from new features but I'm just the (more active) co-maintainer. I couldn't convince the original maintainer Lu Wang (https://github.com/scanmem/scanmem/issues/112).

Bad surprises are not expected for distributions maintaining binary packages. With Arch there is a problem with the python cache we are currently working on (https://github.com/scanmem/scanmem/issues/116).

Comment 6 Shlomi Fish 2015-07-05 09:18:38 CEST

So what should we do?

Status: NEW => ASSIGNED

Comment 7 Sebastian Parschauer 2015-07-05 13:27:33 CEST

IMHO updating, but the decision is yours.

Comment 8 Marja Van Waes 2018-04-14 10:56:22 CEST

Thank you for having taken the needed time to report this issue!

IINM, this did not get fixed for Mageia 5, but we do have version 0.15.7 in Mageia 6 and version 0.17 in Cauldron.

We regret that we weren't able to fix it in Mageia 5. There is no chance it'll get fixed there: Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then.

CC: (none) => marja11
Status: ASSIGNED => RESOLVED
Resolution: (none) => OLD