floss.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
For people who care about, support, and build Free, Libre, and Open Source Software (FLOSS).

Administered by:

Server stats:

686
active users

#Repology only has marginal support for F-Droid, only seeing a few handpicked packages for software which is also available in Linux:

repology.org/projects/?inrepo=

I've recently had a few PRs which improve F-Droid support and add #IzzyOnDroid, allowing full-fledged version comparison within Android ecosystem.

I wonder if any #fdroid maintainers or @IzzyOnDroid would be interested in that.

repology.orgProjects list - RepologyMultiple package repositories analyzer

@AMDmi3 i can check when i'm back at my desk next week. What would you need from us to support repology for IzzyOnDroid?

@IzzyOnDroid nothing really - just a feedback. Here's, for instance, list of projects in IzzyOnDroid which intersect with other repos (F-Droid, that is, but I am still to recheck if there are any projects which also intersect with *nix repos)

repology.org/projects/?inrepo=

repology.orgProjects list - RepologyMultiple package repositories analyzer

@AMDmi3 PS, just another thing I found: dev.jahidhasanco.bmicalculator at F-Droid is a different package than at IoD (coming from different repositories, thus should not have the same packageId; actually their 4.0.2 is OLDER than IoD's 1.0.3 (theirs is 4 years old, ours 1 year). Not sure which should be marked "outdated" there. Comparing the source URL might help detect such things.

@IzzyOnDroid sure, Repology has facilities to split similarly named projects (and I've in fact seen more cases of this problem), but these imply expanding manually maintained ruleset, and that has its cost. So I'm asking for a feedback - if that's not useful for either IoD or F-Droid, it would make sense to cut the maintenance cost and hide android-specific projects in Repology.

IzzyOnDroid ✅

@AMDmi3 I just returned from vacation and still have to catch up with the backlog, which will take at least a week – so apologies if I cannot dig in deeper at this time. But it already helpedd me to identify some issues (like the one mentioned – but also a new one I was not aware of, with apps falling behind due to GitLab API issues I have to dig into later). To thanks once more for reaching out with your project – and let's check more later, shall we?