Arch Linux User Repository

Hello,

I was added as a co-maintainer to maintain this package which I had the willingness to do at the time due to me using the package myself however due to me stepping away from it I don't check for updates etc as frequently as can be noted with the recent increase in time it took for a patch to be submitted.

I am looking for somebody to replace me as co-maintainer due to this, if you are willing to do this please contact me at arch@alias.selfhostable.net. Until one can be found I will continue to maintain this package however it might take longer than usual.

Have a pleasant day, Stetsed

@talone: rewritten improved PKGBUILD https://pastebin.com/raw/96cqMDqr

I'm not sure if that's what you are referring to, but yes we could likely use libadwaita instead of libadwaita-git. However, this package (authenticator) is no more maintained, as the upstream project doesn't want it packaged, and hence has made the packaging nearly impossible.

I might be wrong, but I think https://archlinux.org/packages/extra/x86_64/libadwaita/ can be used now?

Yes, the PKGBUILD is clean now, but it couldn't have been a week ago, and the actual version still doesn't work, hence the packaging is unreliable. If we wanted to package it right (make it work), it could require to bundle in another version of gst-plugins, and most likely a lot of its dependencies, and so on and so fourth.

@talone I did not know about the problems with the developer. He seems to be quite incompetent referencing his comments. I do not understand why you say that the software is hard to package. If I look at the PKGBUILD it is as clean as possible. I packaged way more difficult software.

Here is the list of applications for password managers from which an alternative can be chosen: https://wiki.archlinux.org/index.php/List_of_applications#Password_managers.

Personally, I would recommend the alternatives keysmith from KDE and qtpass.

Hold on. I've made the update to version 4, but still this package won't work. The maintainer doesn't seem really upset about adding untested commits to official releases (for instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/merge_requests/767). This added to the zbar problem that was still there less than a week ago makes me fear a lot about the future of authenticator.

Due to the developer decisions, the software cannot be packaged correctly. If you want to install it, you can use Flatpack as recommended by the maintainer, even tough I would strongly advise against using it at all, considering the position of the software developer (to make it short "use Flatpack, I won't make any effort to make Authenticator packageable").

When the issue above will be closed (on gst-plugins-good), there will be chances for the package to work... but for how long? Unstable, untested, or completely outdated dependencies might be added any time, so we do not know what to really expect. I'll still try to do my best packaging this, but, for now, I recommend you to:

1. stick to version 3;

2. quickly switch to another OTP generator.

For people who want more information, you can find that the maintainer of authenticator-git is also having trouble packaging this: https://aur.archlinux.org/packages/authenticator-git/

Also, awful citations of the software developer: https://gitlab.gnome.org/World/Authenticator/-/issues/219 including: "What can be done here is using Flatpak really." or even "Don't package it, thanks.".

Same on this issue: https://gitlab.gnome.org/World/Authenticator/-/issues/255

If someone feels like having the energy to patch the software, I'd be happy to hear about it, but for now I'm forced to comply with the developer's decision because no workaround seems to exist. I profoundly regret it, as I've been myself using this software for years.

Actually there was: the maintainer switched from Python to Rust for his package, and one of the library used (zbar) was required (by rust-zbar) in a version inferior to the one available on the Arch repositories, making the update very tricky. At least, when I looked at it, it seemed impossible without nasty tricks.

Now, it's fortunate you're asking because it seems the maintainer of the binding (rust-zbar), has made an update 6 days ago that might allow the update here. I'll have a look as fast as I can. Apologizes for the delay.

Is there a reason why this package is not updated for over a month?

Hello FirstAirBender, alesasnouski and everyone,

I made an update that should fix the reported problem. Feel free to comment for any bug.