New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

F-Droid support for new builds #796

Open
simonpoole opened this Issue Nov 11, 2018 · 13 comments

Comments

Projects
None yet
3 participants
@simonpoole
Copy link
Collaborator

simonpoole commented Nov 11, 2018

@Bubu & @roptat the 11.2 release build now generates 2 APKs:

  • osmeditor4android-current... with support for Android 4.0 (SDK 14) and higher with a current support library version.
  • osmeditor4android-legacy... with support for Android 2.3 (SDK 9) and higher with an old support library version.

If there needs to be a choice using the "current" flavor is preferable, both use the same Android version code (801) but that could in principle be changed.

@simonpoole simonpoole added the Question label Nov 28, 2018

@simonpoole

This comment has been minimized.

Copy link
Collaborator

simonpoole commented Dec 12, 2018

It seems as if f-droid is also providing beta builds see #813 I don't have anything against that except that the status really really really needs to be indicated.

@Bubu

This comment has been minimized.

Copy link

Bubu commented Dec 12, 2018

Ping @roptat.

@simonpoole

This comment has been minimized.

Copy link
Collaborator

simonpoole commented Dec 18, 2018

@Bubu the 12.0.0.1 on f-droid should really really be removed (beta build with a bug on older devices) anyway that can be done?

@Bubu

This comment has been minimized.

Copy link

Bubu commented Dec 18, 2018

@simonpoole

This comment has been minimized.

Copy link
Collaborator

simonpoole commented Dec 18, 2018

Thanks a lot.

@Bubu

This comment has been minimized.

Copy link

Bubu commented Dec 18, 2018

Done. We need to figure out a way to prevent that automatic updating to betas in the future. I have no time to look into this right now though.

@simonpoole

This comment has been minimized.

Copy link
Collaborator

simonpoole commented Dec 18, 2018

I do set the pre-release flag on such releases and in the past that never caused an issue (except naturally the one-time I forgot to do so).

@Bubu

This comment has been minimized.

Copy link

Bubu commented Dec 18, 2018

@simonpoole

This comment has been minimized.

Copy link
Collaborator

simonpoole commented Dec 18, 2018

The beta tags in our case have the fourth digit set to non-null, so
12.0.0.0 12..0.1,0 etc are proper releases, 12.0.0.1 12.0.0.2 12.0.1.1 would all be betas.

@Bubu

This comment has been minimized.

Copy link

Bubu commented Dec 18, 2018

Repository owner deleted a comment from Unamely00 Jan 5, 2019

@simonpoole

This comment has been minimized.

Copy link
Collaborator

simonpoole commented Jan 5, 2019

@Bubu & @roptat there's a release of 12.0.0 available now so that could be distributed by f-droid however it doesn't seem to being picked up.

@roptat

This comment has been minimized.

Copy link

roptat commented Jan 7, 2019

Version 12.0.1 was added here: https://gitlab.com/fdroid/fdroiddata/commit/499391c435b925b5603397a78b9ce20836c97341.

Do you mean that that wasn't correct, or simply that 12.0.0 is missing?

@simonpoole

This comment has been minimized.

Copy link
Collaborator

simonpoole commented Jan 7, 2019

The build metadata was missing in general so it wasn't possible to determine if it was in the queue to be build or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment