@opensuse I also updated the @fedora #Rawhide package, and according to the syslog-ng page on #repology, it's already there: https://repology.org/project/syslog-ng/versions

However, Rawhide still had #syslog_ng 4.10.2, when I checked a few minutes ago...

syslog-ng package versions - Repology

List of package versions for project syslog-ng in all repositories

New at haikuports, lasermagic 0.1.36, after the first recipe draft by @pulkomandy for this and some pointers found at #repology I was able to complete the package and make it available as an extention for Inkscape.

https://lasermagic.ci-yow.com/

#HaikuOS #haikuports #lasermagic #repology #Inkscape

#repology service may be intermittent due to DDoS attack on the hoster. Status and plans: https://github.com/repology/repology-rs/issues/278
Repology may be unavailable, hosting under DoS · Issue #278 · repology/repology-rs

Repology rewrite in Rust. Contribute to repology/repology-rs development by creating an account on GitHub.

GitHub
#repology's linkchecker rewritten in rust and now back live (wasn't working since Aug 2024). Keep an eye for new broken upstream and download URLs in your repositories.
Does #repology have a way to filter a page like https://repology.org/project/kwallet/versions to show only the currently supported distributions? I.e. hide Fedora before 39 and so on?
kwallet package versions - Repology

List of package versions for project kwallet in all repositories

On the downside, I'll have to maintain ruleset (merging related projects, splitting unrelated ones, and blacklisting incorrect versions) in whole another ecosystem, and one which lacks good package naming (names are long unicode strings which need normalization) and versioning (`v` prefix and random suffixes all over the place) traditions.

So for now I'm hesitant about making Android repos first class citizens in #repology.

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

https://repology.org/projects/?inrepo=fdroid

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.

Projects list - Repology

Multiple package repositories analyzer

Ah, nice. I just deprecated #qXmoji, now that #Xmoji has all the "important" features (and more). Didn't even know someone packaged it for AUR.

In general, I've seen very mixed quality in AUR, unfortunately. If #Xmoji appears there, I should notice (thanks to #repology) and review what was done 😁

When I don't know what library to use in my #Python project, I search my distro's repos first and then check how many distros also packaged it (using #Repology).

If a library is packaged, then some of the following things are automatically true:

  • This library is used by other projects.
  • This library is maintained.
  • This library has a working test suite.

And if I have to use an unpackaged library, that means each distro needs to package its dependency graph, including test dependencies. Maintainers will think twice before doing this.

#Dependencies #SoftwareDevelopment

So after doing a few small projects in #rust, I've finally started rewriting #repology backend (currently in #python) in Rust.

First discovery - what I naively though of as a database-bound workload, e.g. where database RTT (for small queries) or response generation time (for complex queries) dominates, are still 5-10x faster (in terms of both max RPS and latency) in Rust!

Also rust process takes 3-10x less memory compared to single uwsgi worker, which there are 10-20 of.