v1.6.0 not available in Android Market ?
Moderator: ScummVM Team
- Mister Floppy
- Posts: 3
- Joined: Sat Nov 19, 2005 9:37 am
v1.6.0 not available in Android Market ?
Hi,
why is v1.6.0 not available in Android Market?
Regards,
Mister Floppy
why is v1.6.0 not available in Android Market?
Regards,
Mister Floppy
Simply because the Android maintainer has not packaged and released it yet... There is some lag after v1.6.0 source release for various porters to provide their builds.
Though you are correct that the Downloads page is in error, as the Market still only has v1.5.0, not v1.6.0
But I have no date for when this will be released. I will poke the Android team.
Though you are correct that the Downloads page is in error, as the Market still only has v1.5.0, not v1.6.0
But I have no date for when this will be released. I will poke the Android team.
OK... Have talked to fuzzie about this.
This has been due to Google Play (The new name for the Marketplace) giving very cryptic error messages when we
try to submit the upgraded build... and a lack of time for
the porter to fight with the app store.
In order to avoid this in future, we are going to provide
the v1.6.0 and future builds as a zipfile of the signed apks for download on our downloads page in addition to a link to Google Play:
http://www.scummvm.org/downloads/?p=downloads
We will then try again to work out why Google are giving us problems...
I should point out that you can also download the v1.6 branch stable or v1.7 development autogenerated builds from the buildbot: http://buildbot.scummvm.org/builds.html
You need to uninstall all previous versions of ScummVM before you can install a buildbot build.
Also, you need to enable "Installation of third party applications" in the Settings menu during the installation as these apks are not signed.
This has been due to Google Play (The new name for the Marketplace) giving very cryptic error messages when we
try to submit the upgraded build... and a lack of time for
the porter to fight with the app store.
In order to avoid this in future, we are going to provide
the v1.6.0 and future builds as a zipfile of the signed apks for download on our downloads page in addition to a link to Google Play:
http://www.scummvm.org/downloads/?p=downloads
We will then try again to work out why Google are giving us problems...
I should point out that you can also download the v1.6 branch stable or v1.7 development autogenerated builds from the buildbot: http://buildbot.scummvm.org/builds.html
You need to uninstall all previous versions of ScummVM before you can install a buildbot build.
Also, you need to enable "Installation of third party applications" in the Settings menu during the installation as these apks are not signed.
Nazo: Sorry about this. The buildbot box keeps a number of snapshots of builds, not just the latest linked on the builds page. The link to this is at the top of this page:
http://buildbot.scummvm.org/builds.html
where it says (all):
http://buildbot.scummvm.org/snapshots/
Anyway, to ensure that the box doesn't run out of disk space, a script runs periodically to purge snapshots older than 1 week. Unfortunately, as nightly builds are only performed if there has been a commit in the last 24 hours, the stable builds can age to the point where all builds are removed.
This is a bug (The script should check and not remove if only 1 set of builds is present)... I need to look at fixing it.
For now, please use the v1.7.0git development snapshots.
I will trigger a manual nightly v1.6.0 build and look at changing the script code to preserve the final build...
http://buildbot.scummvm.org/builds.html
where it says (all):
http://buildbot.scummvm.org/snapshots/
Anyway, to ensure that the box doesn't run out of disk space, a script runs periodically to purge snapshots older than 1 week. Unfortunately, as nightly builds are only performed if there has been a commit in the last 24 hours, the stable builds can age to the point where all builds are removed.
This is a bug (The script should check and not remove if only 1 set of builds is present)... I need to look at fixing it.
For now, please use the v1.7.0git development snapshots.
I will trigger a manual nightly v1.6.0 build and look at changing the script code to preserve the final build...
I guess your manual trigger worked. When I checked just now it gave me 1.6.0pre82-gbd42dee dated today, which I'm guessing is essentially the stable version, right? At the very least it should be more stable than the 1.7 nightly surely.
I've seen Google's useless errors first-hand before btw. I've been fighting with an app called Name Generator for ages (great for generating names for character creation in games) which just says "App not installed" when I try to install it with no details whatsoever. How they thought it was a good idea to not give the user something usable as an error message is beyond me entirely, but clearly Google isn't thinking ahead when it comes to error messages... More recently it started saying "app cannot be installed in the default install location" which is still pretty useless as all of my searches on what could cause this come back to ancient 2.x Android versions from back when some people had to install in a very limited internal partition and none of the solutions still applies today whatsoever. Thus still an equally useless error message...
I've seen Google's useless errors first-hand before btw. I've been fighting with an app called Name Generator for ages (great for generating names for character creation in games) which just says "App not installed" when I try to install it with no details whatsoever. How they thought it was a good idea to not give the user something usable as an error message is beyond me entirely, but clearly Google isn't thinking ahead when it comes to error messages... More recently it started saying "app cannot be installed in the default install location" which is still pretty useless as all of my searches on what could cause this come back to ancient 2.x Android versions from back when some people had to install in a very limited internal partition and none of the solutions still applies today whatsoever. Thus still an equally useless error message...
@Nazo: Yes, the manual trigger has restored the v1.6.0 stable build... Stable and development are a bit of misnomer.
We rarely have major regressions in the main development "master" trunk in Git, but it is possible.. so hence these builds are recommended only to Developers, Power Users and other people who like to live on the edge... The worst they are likely to do is corrupt your ./scummvmrc configuration file, but they could crash or do nasty stuff due to new bugs... although they also have a lot of fixes for older bugs since the last release... *SHRUG* Your mileage may vary.
The autogenerated stable builds are generated from the latest branch-1-x-x which occurs at feature freeze prior to release testing and are intended for testers and thus receive backports of bug fixes, but not further development work..
@Karsten: No problem... I tend to end up with the Tech Support hat on!
We rarely have major regressions in the main development "master" trunk in Git, but it is possible.. so hence these builds are recommended only to Developers, Power Users and other people who like to live on the edge... The worst they are likely to do is corrupt your ./scummvmrc configuration file, but they could crash or do nasty stuff due to new bugs... although they also have a lot of fixes for older bugs since the last release... *SHRUG* Your mileage may vary.
The autogenerated stable builds are generated from the latest branch-1-x-x which occurs at feature freeze prior to release testing and are intended for testers and thus receive backports of bug fixes, but not further development work..
@Karsten: No problem... I tend to end up with the Tech Support hat on!
- MusicallyInspired
- Posts: 1138
- Joined: Fri Mar 02, 2007 8:03 am
- Location: Manitoba, Canada
- Contact:
- MusicallyInspired
- Posts: 1138
- Joined: Fri Mar 02, 2007 8:03 am
- Location: Manitoba, Canada
- Contact:
Stable version
Hi Guys, hm, I'm trying for several days to download the stable version but no luck. Whas up with that link? Thanks for help.
Right... have debugged and tested the build cleanup script. I had made two minor errors, which resulted in the stable still be overzealously cleaned... and the master failed to be cleaned at all! *facepalm* Fixed now and should stay fixed. Manual build of stable running... so stable build links will be restored shortly.