Skip to content
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

ship alphas to f-droid / app store #512

Open
anarcat opened this issue Apr 19, 2017 · 7 comments
Open

ship alphas to f-droid / app store #512

anarcat opened this issue Apr 19, 2017 · 7 comments

Comments

@anarcat
Copy link

anarcat commented Apr 19, 2017

Hi,

I see the Android client is making huge progress. My particular pet peeve is the lack of tag support in the 1.x versions, which seems to have improved in the first alpha already... Is there a way to get a version distributed on f-droid and/or the app store? In f-droid at least, there is a way to mark a version as "beta" so that people don't upgrade by default.

Now, i know I could install the packages straight from the release pages on GitHub, but the signature seemed different the last time I checked. This may be because F-Droid rebuilds the APKs and resigns them with its own signatures... I am not sure how to fixed this, so I asked the F-Droid people to clarify that part:

https://forum.f-droid.org/t/are-reproducible-builds-possible-now/335

Still - I can't wait to get tag support and it would be great to be able to test that easily.

Thanks!

@tcitworld
Copy link
Member

Ask the f-droid guys, since they disable the build of beta tags : https://gitlab.com/fdroid/fdroiddata/commit/ae516b9fe2a2b6e9eaf9204a6f3d8f2c17736d87

The builds attached to releases on github and available on github are signed by our key. The F-Droid builds are signed by theirs, so that's why you need to reinstall the app if you change the origin of your apk files, there's not much to do here.

@anarcat
Copy link
Author

anarcat commented Apr 19, 2017

done. regarding signing keys, I asked on the f-droid forum, but i believe it may be possible to reuse the official signing key.... stay tuned.

@anarcat
Copy link
Author

anarcat commented Apr 19, 2017

regarding key signatures, if there is a place where .apk files can be downloaded, it's possible to reuse your signature. i'm not sure how it could be migrated without first uninstalling the app, unfortunately... but it may be a good idea to use the 2.0 update as an opportunity to fix this for the future...

@anarcat
Copy link
Author

anarcat commented Apr 19, 2017

filed an issue in f-droid about the signature part: https://gitlab.com/fdroid/fdroiddata/issues/700

@anarcat
Copy link
Author

anarcat commented Apr 19, 2017

and this issue is about the beta tags: https://gitlab.com/fdroid/fdroiddata/issues/701

@tcitworld
Copy link
Member

regarding key signatures, if there is a place where .apk files can be downloaded, it's possible to reuse your signature

What ?

@anarcat
Copy link
Author

anarcat commented Apr 19, 2017

What ?

Not sure what you mean there. I'll assume you didn't understand what I said and explain it again. It'd be nice to have some more clarity next time...

It's possible to ship APKs signed with your developer signature on F-Droid, by populating the "Binaries" field in their metadata, pointing at a URL where your APK can be downloaded. F-Droid then compares that binary against the build it did and reuses it if it matches. Since Wallabag is reproducible, that should just work - it's just a matter of making a small change on F-Droid's configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants