Make F-Droid repo
genofire opened this issue · 39 comments
Preliminary checklist
- I have read the README
- I have read the FAQs.
- I have searched existing issues for my feature request. This is a new issue (NOT a duplicate) and is not related to another issue.
- This is a feature request for the Bromite browser; not the website nor F-Droid nor anything else.
Is your feature request related to privacy?
Yes
Is there a patch available for this feature somewhere?
No
Describe the solution you would like
Publish in F-Droid repo (again)
Describe alternatives you have considered
own F-Droid Repo
this is a first test, consider it still in alpha
https://static.cromite.org/@pages/fdroid/repo
I also decided to host it in codeberg, since their privacy policy is better than github's.
@uazo Does this mean you will stop releasing your browser here at some point in the near future?
Does this mean you will stop releasing your browser here at some point in the near future?
no, no intention
Downloading the apk from the repo fails because the connection is closed randomly. Can you please verify the issue?
With fdroidcl
$ fdroidcl install org.cromite.cromite
(lots of useless progress lines here)
https://uazo.codeberg.page/cromite-static/@pages/fdroid/repo/arm64_ChromePublic.apk
20% || (20/98 MB, 1.207 MB/s) [16s:1m4s]install: could not download org.cromite.cromite: unexpected EOF
With wget
$ wget https://uazo.codeberg.page/cromite-static/@pages/fdroid/repo/arm64_ChromePublic.apk
--2023-07-23 14:42:44-- https://uazo.codeberg.page/cromite-static/@pages/fdroid/repo/arm64_ChromePublic.apk
Resolving uazo.codeberg.page (uazo.codeberg.page)... 2001:67c:1401:20f0::1, 217.197.91.145
Connecting to uazo.codeberg.page (uazo.codeberg.page)|2001:67c:1401:20f0::1|:443... connected.
HTTP request sent, awaiting response... 307 Temporary Redirect
Location: https://static.cromite.org/@pages/fdroid/repo/arm64_ChromePublic.apk [following]
--2023-07-23 14:42:44-- https://static.cromite.org/@pages/fdroid/repo/arm64_ChromePublic.apk
Resolving static.cromite.org (static.cromite.org)... 2001:67c:1401:20f0::1, 217.197.91.145
Connecting to static.cromite.org (static.cromite.org)|2001:67c:1401:20f0::1|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 102481025 (98M) [application/vnd.android.package-archive]
Last-modified header invalid -- time-stamp ignored.
--2023-07-23 14:42:45-- https://static.cromite.org/@pages/fdroid/repo/arm64_ChromePublic.apk
Reusing existing connection to [static.cromite.org]:443.
HTTP request sent, awaiting response... 200 OK
Length: 102481025 (98M) [application/vnd.android.package-archive]
Saving to: ‘arm64_ChromePublic.apk’
arm64_ChromePublic.apk 26%[=============> ] 26.33M 1.20MB/s in 22s
2023-07-23 14:43:07 (1.19 MB/s) - Connection closed at byte 27608545. Retrying.
--2023-07-23 14:43:08-- (try: 2) https://static.cromite.org/@pages/fdroid/repo/arm64_ChromePublic.apk
Connecting to static.cromite.org (static.cromite.org)|2001:67c:1401:20f0::1|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 102481025 (98M) [application/vnd.android.package-archive]
Saving to: ‘arm64_ChromePublic.apk’
arm64_ChromePublic.apk 27%[=============> ] 26.47M 1.20MB/s in 22s
2023-07-23 14:43:31 (1.19 MB/s) - Connection closed at byte 27756001. Retrying.
^C
It was a bit worse a few hours ago, because it would drop at ~10-15%.
It was a bit worse a few hours ago, because it would drop at ~10-15%
https://docs.codeberg.org/getting-started/faq/#what-is-the-size-limit-for-my-repositories
I feel that I have already reached the limits of codeberg.... OK, that is not the correct solution.
try with https://www.cromite.org/fdroid/repo/
again, consider it still an alpha test
Is it me or it still gets it from codeberg? Relevant lines in fdroidcl's config file
{
"id": "cromite",
"url": "https://www.cromite.org/fdroid/repo/",
"enabled": true
}
which seems to work as it should
$ fdroidcl update
https://www.cromite.org/fdroid/repo//index-v1.jar 100% || (4.1/4.1 kB, 19.550 MB/s)
but in the end it still gets it from codeberg and fails for the same reason
https://uazo.codeberg.page/cromite-static/@pages/fdroid/repo/arm64_ChromePublic.apk
20% || (20/98 MB, 1.193 MB/s) [16s:1m5s]install: could not download org.cromite.cromite: unexpected EOF
try now, I had not mistakenly changed the url in the configuration
It is now fixed, thank you very much!
https://www.cromite.org/fdroid/repo/arm64_ChromePublic.apk 100% || (98/98 MB, 1.207 MB/s)
Installing org.cromite.cromite
try with https://www.cromite.org/fdroid/repo/ again, consider it still an alpha test
👍
Alternately, https://www.cromite.org/fdroid/repo?fingerprint=49F37E74DEE483DCA2B991334FB5A0200787430D0B5F9A783DD5F13695E9517B
Uazo, try this link by two way :-
- click this link (if system prompt's > 'open with' from list of apps) 'select F-Droid' to open it directly > under 'add repository' &
- copy this link & paste it in F-Droid's repo to add.
Alternately, Cromite's F-Droid repo with fingerprint
Uazo, check & notice the browser's address bar (completely), share this link to / with F-Droid app.
please try to check if fdroid detects the update.
Uazo, Yes, Check Screenshot.
Details
How to fold this screenshot & wrap with expand & collapse button ?, that just you edited my comment.
slash commands, press / and the details
try with https://www.cromite.org/fdroid/repo/ again, consider it still an alpha test
Could you please make an announcement once it's considered stable? Like adding it to the readme with the f-droid logo.
Thanks allot for doing this.
Could you please make an announcement once it's considered stable?
I have to prepare a new repo and update scripts and actions, in the meantime I will put a reference to this issue (see https://github.com/uazo/cromite#releases)
This link can be added and works in F-droid app, but can not be added in Neo Store (F-droid fork).
Is this Neo store's problem ? Should I raise an issue in their site ?
This link can be added and works in F-droid app, but can not be added in Neo Store (F-droid fork).
As unhelpful as it sounds it works for me™
When you add it it will show up as "new repository"
click on it to add to synchronized repositories, neo store will synchronise (if not, do it manually) and it will look like this:
I was doing wrong.
Now it's working.
Thanks.
IK this is probably bit off-topic.
Any plans to have it released on play Store? I know bromite was never published, but is it the plan to follow the footsteps and never release on Play Store?
IK this is probably bit off-topic.
Any plans to have it released on play Store? I know bromite was never published, but is it the plan to follow the footsteps and never release on Play Store?
It is a fact that being in play store results to be in limelight, and many 'open source' privacy-friendly projects are there, like - VLC, Brave, Kiwi, Privacy browser, FOSS browser, MPV, Collabora - are only few to name.
But I don't know (and suspect a lot) that, if these projects had to compromise or not, with Google's terms and conditions (and to what extent) to be in play store.
It's like dealing with a jackal, and have to be very cautious. I don't think our good man Uazo alone should take the risk.
I agree to this point but having it on play Store, you can install and recommend the apps to others too who aren't obviously not in FOSS.
I think Cromite can be a good replacement for Brave for many people who aren't tech savvy and don't want the crypto/etc the brave puts in the browser.
Any plans to have it released on play Store?
No, no plans yet.
@uazo Do you need some help with it? Not that I have experience with it, but F-droid repos is something I wanted to get into for other projects.
Do you need some help with it?
yes thanks, I have to do a github action for updating the fdroid site, I've already partially done the script but I don't feel like launching it by hand every time.
I'm on holiday :) maybe we'll talk about it when I get back, but If I can, I will make the script available to you.
@uazo Hi.
Could you, please, explain why you decided to go the Bromite way and host own F-Droid repo instead of pushing to the main F-Droid repo? Is it your position or theirs?
I am worried about security.
Having a program in F-Droid means that at least its builds are truly reproducible and the built programs are 100% from the provided source code.
I would like very-very much to finally have any maintained chromium-based browser in F-Droid main repo.
@sankhababu Kiwi is not open source. Beware, it's probably malware.
Will be excellent, as there is only ff forks at present in default F-droid.
@sankhababu Kiwi is not open source. Beware, it's probably malware.
Though they claim repeatedly as open source, in their Telegram group.
I have no knowledge to confirm that.
Kiwi's privacy policy, not the bad one.
I just use it occasionally for test purpose as have unique feature like extension support and unlimited custom speed dial like Vivaldi.
I don't use seriously any chromium based browser except Bromite (now Cromite 👍).
My default is Mull.
@uazo Hi. Could you, please, explain why you decided to go the Bromite way and host own F-Droid repo instead of pushing to the main F-Droid repo? Is it your position or theirs? I am worried about security. Having a program in F-Droid means that at least it is builds are truly reproducible and the built programs are 100% from the provided source code.
I am not even sure if Bromite/Cromite are eligible for F-Droid main repo based on their inclusion policy:
https://f-droid.org/en/docs/Inclusion_Policy/
As for security, my understanding is that Cromite's releases are build by GitHub Actions, not by the developer himself? So the builds should be reproducible as the build scripts for GitHub Actions are in this repo. This makes everything way more transparent, unlike Bromite.
Could you, please, explain why you decided to go the Bromite way and host own F-Droid repo instead of pushing to the main F-Droid repo? Is it your position or theirs?
simply because it is simpler.
also bear in mind that I can't do everything myself: if someone takes it upon themselves to check how to do the build with the fdroid servers, I might consider it.
Though they claim repeatedly as open source, in their Telegram group.
try asking where the source code is. I haven't found them for a long time.
my understanding is that Cromite's releases are build by GitHub Actions
is correct, anyone capable of reading the repo can confirm this.
Here again, if anyone knows of a method that improves transparency, I will be happy to evaluate it.
As I mentioned, I can help by looking into the F-droid part. Just waiting for your available to check the script you mentioned
Hey, is there a plan to include changelogs? If so, in a fdroid compatible way? And copying in the chrome ones and/or the changes to the diffs of this project?
task completed
action finally made: https://github.com/uazo/cromite/blob/master/.github/workflows/update_fdroid_repo.yaml
Thank you for that!
FYI, repo: https://www.cromite.org/fdroid/repo
Could you also publish the fingerprint of the signing key?
Aside from that, the link to the release note doesn't point to the up-to-date notes. Could you also fix that?
When will the app get icon pic in fdroid?
Details
@uazo
What about to make reproducible build (signed by your keys) in the official f-droid repo? Cromite could reach much more people if it was available in f-droid out of box.
When will the app get icon pic in fdroid?
buth, sooner or later maybe someone will help me fix the problem.
What about to make reproducible build (signed by your keys) in the official f-droid repo?
bromite has already tried this with poor results, the biggest (and insurmountable) problem being the build times from what I remember. if anyone wants to think about it, they are welcome