Talk-android: F-Droid build fails with unknown maven repo https://dl.bintray.com/mdjanic/maven

[Bubu]

F-Droid doesn't like your custom maven repo.

Using jitpack like for your other forks doesn't work here?
Do you see any possible way to get rid of this maven repo?

If not, how could I recreate that repo prior to the f-droid build?

[mario]

I tried using Jitpack but it didn't work out due to complicated nature of Fresco building :(

I can take a look at it again eventually. What's the issue with maven btw?

[Bubu]

There's no guarantee that the artifacts published in a maven repo correspond to any published sources.

That is of course the same for any maven repo, but things like maven.google.com or jcenter have much more eyes on them that could detect anything malicious going on.

In short, it's a current policy of F-Droid to only allow a whitelist of known-good maven repositories. That's far from ideal but we don't have anything better for the moment.

(Ideally we would never rely on binaries built by the developers but could get them from an independently trusted source like Debian or compile them ourself)

[gerroon]

Hi

Any plans on when we can get the F-droid builds?

[mario]

@gerroon no idea, sorry :(

[mario]

This will be fixed for the next stable. Sorry for the delay.

[Bubu]

@mario can you share what will be the solution?

[mario]

@Bubu Jitpack managed to build my repository :)