Edit: fixed. thx!

This is not an architecture independent package, so arch should be x86_64. Also, consider updating to build process to PEP-517, also the license SPDX identifier (GPL-2.0-or-later).

@truocolo: I understand about dealing with IRL issue. No worries.

@yochananmarqos:

Yes, I had some heavy irl issues, I'm just now coming back to a computing platform. I haven't been able to access almost nothing for almost 6 months.

Watching the out-of-dates pile up, progressively losing maintainerships and seeing people getting mad without being able to do anything has very much felt like being eaten alive.

I am updating everything that has piled up as fast as I can, please don't get mad if it will take just a little more than it always has been, it's not exactly easy working as I am.

@truocolo: I noticed because there were new tags in the repo today (though 2.6.0 is still the stable version). I realized I had forgotten to answer your question here and noticed the package was still flagged out of date since August. I see you have 62 other packages that are flagged out of date as well...

@yochananmarqos:

it does feel so weird to get all these 'if you are not going to maintain it, orphan it' messages as of lately, as if I hadn't maintained this and other packages for years.

Do you want to co-maintain it?

Please don't take it personally but it does feel even weirder because of how nobody have seemed to notice I have disappeared for like six months or so.

The general vibe is like if I had died I would have kept receiving ever more harsh messages over time.

@yochananmarqos it works at least on a dozen architectures. do you want me to write them all?

@tallero: The 2.1.3 tag no longer exists and 2.2.1 was just released. Are you planning on maintaining this or not?