search

OpenOrienteering / mapper

OpenOrienteering Mapper is a software for creating maps for the orienteering sport.
https://www.openorienteering.org/apps/mapper/
GNU General Public License v3.0
400 stars 106 forks source link

Screenshots for F-Droid #1845

Open mondlicht-und-sterne opened 3 years ago

mondlicht-und-sterne commented 3 years ago

You can add Screenshots for F-Droid, too, if you want.

https://f-droid.org/en/docs/All_About_Descriptions_Graphics_and_Screenshots/

https://gitlab.com/snippets/1895688

dg0yt commented 3 years ago

The F-Droid version is outdated and unmaintained: "0.6.8 (608) - Added on 2017-03-08".

I assume maintenance is hindered by the fact that Mapper relies on app. 25 third-party components, including Qt and GDAL. For full compliance, all of this needs to be build from source. We do offer build scripts and sources: https://github.com/OpenOrienteering/superbuild/releases

jmacura commented 3 years ago

FTR: OO Mapper on F-Droid is also available from the IzzyOnDroid repository, where the current version (0.9.4) is available.

dg0yt commented 3 years ago

FTR: OO Mapper on F-Droid is also available from the IzzyOnDroid repository, where the current version (0.9.4) is available.

Sorry, I missed that.

dg0yt commented 3 years ago

Can someone remove the outdated version?

stevogray commented 2 years ago

The 'help wanted' tag prompted me to contact the F-Droid maintainers (it was Izzy who responded). He has moved the package to the F-Droid 'archive', removed the page and OOM now doesn't appear in the F-Droid search.

The package will remain available on the IzzyOnDroid repository. I couldn't see a reason to request it was removed from there as well since this is the latest version, and will auto-update when a new release is published.

The automated update failed on F-Droid, part of email from Izzy:

at F-Droid.org, automated updates are disabled as auto-update stopped working (the note is "disable: patches do not apply"). The last version published on F-Droid was v0.6.8, v0.7.0 failed with the mentioned problem. Someone would need to make a merge request at fdroiddata adding a more recent version in order to get it published, that's all – as no such merge request was made, none was processed. If it's preferred to "unlist" the app, we can of course also move it to the archive.

Following the comment directly above, I asked him to 'unlist' the app.

And in a later email from Izzy:

Should you later decide to revive it, just open a corresponding merge request on fdroiddata for metadata/org.openorienteering.mapper.yml which adds the corresponding build block and removes the ArchivePolicy line.