releases gone? about gps_locker

[MrRar]

I removed it as part of trying to add this app to F-Droid: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/14862

Honestly I didn't expect anyone to notice that it was gone. I think it should be easy enough to put back. Let me give it a try...

Edit: alright the old release is back now. If/when it's published to F-Droid the app ID will be different than the APK in the releases the old one was com.github.mrrar.gps_lock new one is com.github.mrrar.gps_locker. Also the APK will be signed differently.

[IzzySoft]

I removed it as part of trying to add this app to F-Droid

F-Droid would ask you for those even when trying to establish reproducible builds. And your app is already in my repo since 2023-07-07 – which is how I noticed (my update checker complained) 😉

alright the old release is back now

Thanks!

Also the APK will be signed differently.

The one at releases, or the one at F-Droid? If reproducible builds are established, F-Droid would ship the APK you signed (provided verification succeeds of course).

[MrRar]

The one at releases, or the one at F-Droid? If reproducible builds are established, F-Droid would ship the APK you signed (provided verification succeeds of course).

I meant the releases on F-Droid. For F-Droid to use my signed APK, I think I need to specify a download URL and probably some other things as well. I don't see much of an advantage to putting APKs signed by me on F-Droid. The problem with having APKs with different signatures on F-Droid vs. Github releases is that updates won't work if the user switches where they get updates from. I don't see this app getting a lot of updates so I don't think it's much of a problem.

[IzzySoft]

For F-Droid to use my signed APK, I think I need to specify a download URL

Yes. And that needs to be built from the very same commit the tag points to. Then reproducible build tools will be used to match their build and yours; if those confirm, your APK will be taken, else the build will be declared "failed". There might be some adjustments to be made initially to make that succeed.

I don't see much of an advantage to putting APKs signed by me on F-Droid.

1. double-trust: you approved, F-Droid approved.
2. seamless switching for folks getting your app from different places (e.g. had it installed from PlayStore but want to cut their Google ties and get it from F-Droid now
3. a chance to get out (security) updates fast when needed (F-Droid installs can be updated with APKs you provide directly

Github releases is that updates won't work if the user switches where they get updates from.

Not if F-Droid uses the very same 😉

[MrRar]

For F-Droid to use my signed APK, I think I need to specify a download URL

Yes. And that needs to be built from the very same commit the tag points to. Then reproducible build tools will be used to match their build and yours; if those confirm, your APK will be taken, else the build will be declared "failed". There might be some adjustments to be made initially to make that succeed.

I don't see much of an advantage to putting APKs signed by me on F-Droid.

1. double-trust: you approved, F-Droid approved.

2. seamless switching for folks getting your app from different places (e.g. had it installed from PlayStore but want to cut their Google ties and get it from F-Droid now

3. a chance to get out (security) updates fast when needed (F-Droid installs can be updated with APKs you provide directly

Github releases is that updates won't work if the user switches where they get updates from.

Not if F-Droid uses the very same 😉

OK I did it: https://gitlab.com/MrRar/fdroiddata/-/commit/749a5dfd421e508872b91a81ea4da9983b05437b
I guess I did it correctly. I grep -r'ed fdroiddata and found a bunch of apps that are doing the same thing.

I also added a new release for 0.1.1 which is exactly 2 bytes smaller than the old release for whatever reason.

[IzzySoft]

The lines look correct, just the linter will complain they are in the "wrong place" (take a look where the other YAML files have it). But you'll be helped there with it. Thanks!

[IzzySoft]

Now that your app is available at F-Droid, I see you've added their badge. Congrats first! But do you want me to remove it from IoD then (your app is still listed here? I'd happily keep it there and offer you to pick a badge to add here as well, @MrRar – what do you say? Always good to have options 😉

[MrRar]

Now that your app is available at F-Droid, I see you've added their badge. Congrats first! But do you want me to remove it from IoD then (your app is still listed here? I'd happily keep it there and offer you to pick a badge to add here as well, @MrRar – what do you say? Always good to have options 😉

Thanks! I'd recommend removing the old version with a different app id (com.github.mrrar.gps_lock). I'm cool with leaving the new version on IoD and I've added a button for it on the readme now.

[IzzySoft]

I'd recommend removing the old version with a different app id (com.github.mrrar.gps_lock)

Yes, that was planned anyhow. From the MaintainerNotes on that one:

MaintainerNotes:
  AppAdded: 2023-07-07
  Todo: 2024-07-01 remove as package was renamed to com.github.mrrar.gps_locker

Intention was to give people a hint and time to switch. I just saw I forgot to add the usual note to the app description – done that now:

<p><b>Note:</b> this app is <a href='https://apt.izzysoft.de/packages/com.github.mrrar.gps_locker'>continued using a different name</a>, please switch to the new app!</p>

I'm cool with leaving the new version on IoD and I've added a button for it on the readme now.

Wonderful! Then I'm very cool to keep it and just marked it accordingly:

  DoubleList: keep
  DoubleListRef: https://github.com/MrRar/gps_locker/issues/1#issuecomment-2170465544

The corresponding hint should show up on the repo browser with the next sync then:

Thanks a lot – also for adding the badge 🤩