Dmitry Marakasov

Take related to #rust ai #ethics case.

Projects without no-AI policy: AI may be involved in writing the code.

Projects with no-AI policy: AI still may be involved in writing the code. AI is also involved on contributors side to ensure that written code does not look like AI written code to get changes accepted. AI is involved on upstream side (dare to ask me why) to verify that contributed code is not AI written.

Take related to #rust ai #ethics case.

Bram Moolenaar, creator of vim text editor, had supported AIDS victims in Uganda (for which he has my deepest respect). As far as I know, no other text editor author does the same. Are they ignoring ethics probem? Should we have policies of now allowing these editors?

So I've finally polished and published https://crates.io/crates/libversion crate, a pure #rust implementation of version comparison algorithm #Repology depends on.

You may or may not be a fan of rewriting anything in rust, but when someone submits you rust bindings of your own C library, it's absolutely 100% the valid case.

In fact though, it was the first thing I've rewritten in rust when I started learning it 2 years ago, though it took more time to gain enough XP to implement and publish it cleanly.

It looks like #axum is finally going to get proper route matching with prefixes and suffixes support (e.g. `/images/{foo}.jpg`, while before only `/images/{foo}` was supported).
https://github.com/tokio-rs/axum/pull/3702

#repology service may be intermittent due to DDoS attack on the hoster. Status and plans: https://github.com/repology/repology-rs/issues/278

#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.

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.

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.

If you work with #NVD, note that CPEs in NVD are subject to change. I've just discovered that a lot of CPE bindings in #Repology are outdated due to changes in CPE vendors and products (aiohttp_project:aiohttp -> aiohttp:aiohttp, stlport:stlport → stlport_project:stlport, soundexchange:sound_exchange → sox_project:sox etc). If you maintain CPE bindings for any purpose, you should revisit and update them.

#security

New repositories support added recently to #repology:
- #chromebrew (package manager for Chrome OS)
- #opam (#OCaml package manager; this should be of great help to highlight outdated packages of ocaml modules in all supported repositories)
- @serpentos

In other news, #guix is blocking access from Russia again, so it's not updated in Repology.

@rrahl0 do you really have arguments for that repos should use fake versions instead of verbatim upstream versions and all tools should implement complex logic instead of just comparing versions directly?

You seem to be right that opensuse doesn't seem to use epochs, however at least `revertto` is not a common pattern there, see #repology statistics.

#buildroot is now tracked by #Repology, huge thanks to Bernd Kuhls for pointing me to usable repository data. Repository freshness is currently 56.7%.

I don't believe in paid conferences. Conferences are meant for free thought sharing with as little borders as possible, and paywall is a huge border, not only for the price but just for inconvenience of paying, especially from some countries. I've been asked several times if I'm going to represent #repology on #packagingcon. Well, I don't see any point, and I don't expect to see many enthusiasts there and I can't see how [FOSS] packaging can be improved in such unwelcome commercial environment.

Many thanks to #altlinux devs for providing comprehensive data on packages in their repositories to #repology. The more data from repositories the more use for package maintainers and #foss project developers.

https://github.com/repology/repology-updater/pull/1204

@mdrights
#freeorion #endlesssky #flarerpg #dhewm3 #minetest #teeworlds #wyrmsun

Feels nice to finally return some technical debt. Shamefully, I have some #FreeBSD bugs assigned to me since 2017, but I'm finally at squishing them.

The biggest one is #OpenSceneGraph port update which I'm going to commit tomorrow, another is #UnknownHorizons update to 2019.1 which also requires #fifengine and other dependencies update (pending maintainer feedback/timeout).

After these, only 3 ancient bugs left!