My main concern is with passlib. The original passlib was super out of date and wask forked. The python module it provides had its name changed to 'libpass' with the fork. Would this update be fine or should something with "transitional dummy package" be added and/or a package name of python3-libpass?

From searching void-packages I've found the following packages other than radicale to have some sort of dependency on python3-passlib:

• ansible-core
• libxcrypt
• mitmproxy
• salt

My other question, should I take maintainer ownership of the argon and passlib packages?

python3-passlib and python3-libpass should be different packages. only radicale uses libpass so far.

python3-passlib and python3-libpass should be different packages. only radicale uses libpass so far.

Did that, now there's a conflict for x86_64 only. Wondering why.
I heard xlocate only exists on x86_64 for the CI. I must have been wrong about the python site-packages folder, it uses 'passlib' for the 'libpass' package. Maybe my first approach was correct and should be reverted to that?