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

F-Droid can't build #5563

Closed
licaon-kter opened this issue Nov 18, 2022 · 7 comments
Closed

F-Droid can't build #5563

licaon-kter opened this issue Nov 18, 2022 · 7 comments

Comments

@licaon-kter
Copy link

...since we build reanimated first and we hit this issue: facebook/react-native#35210

I've hacked around it by bumping react-native to 0.67.5: https://gitlab.com/fdroid/fdroiddata/-/commit/4a750ce2145dd4773092ed3ac551e59d47dccdb3 (based on https://github.com/laurent22/joplin/pull/7307/files)

Can you do this update project wide instead?

@gnprice
Copy link
Member

gnprice commented Nov 18, 2022

Reasonable to take that upgrade. Want to send a PR?

To be explicit here, this is something that's caused by some of the munging that that F-Droid script does with our build. Out of the box our build works fine, after we fixed that issue the day it happened: 117e548 / #5535

@licaon-kter
Copy link
Author

I could.

What I don't know is, where is this hash coming from at the end of .tgz: https://github.com/zulip/zulip-mobile/blob/main/yarn.lock#L13512 ?

@licaon-kter
Copy link
Author

licaon-kter commented Feb 20, 2023

@licaon-kter licaon-kter reopened this Feb 20, 2023
@gnprice
Copy link
Member

gnprice commented Feb 22, 2023

Google Services sneaked in :(
ref: 0f6cf39

Nothing snuck in. We've been quite clear all along that we use Google Play Services for getting notifications. This is part of that.

What happened is that the way you chose to make an F-Droid build involves some sed scripts that depend on the exact details of our source code. We never promised that those details would stay the same. In fact, I specifically warned you that they would probably change, and that your approach was likely to break: #1270 (comment)

Just to make sure we have a shared set of expectations: there's a lot of stuff in that prebuild recipe that we can't guarantee will keep working. It's entirely likely that some of that recipe will break in the future.

If you have specific questions, we can try to help. But this isn't the right tracker for a build failure in the F-Droid script, so I'm closing this issue for now. If you have a specific question to ask, just reply (or feel free to open a new issue) and I can reopen.

@gnprice gnprice closed this as completed Feb 22, 2023
@licaon-kter
Copy link
Author

I guess I forgot what the workflow is for this app. My bad.

@eighthave
Copy link

How about making an fdroid build flavor? That works well for lots of other apps in a similar boat.

@gnprice
Copy link
Member

gnprice commented Feb 25, 2023

How about making an fdroid build flavor? That works well for lots of other apps in a similar boat.

Sure, we'd be open to a PR for that. Here's previous discussion of what it would look like:
#1270 (comment)

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

3 participants