Package Details: authenticator 4.0.3-1

Git Clone URL: https://aur.archlinux.org/authenticator.git (read-only, click to copy)
Package Base: authenticator
Description: 2FA code generator for GNOME
Upstream URL: https://gitlab.gnome.org/World/Authenticator
Keywords: 2FA authentication gnome
Licenses: GPL3
Submitter: lll2yu
Maintainer: talone
Last Packager: talone
Votes: 16
Popularity: 0.008502
First Submitted: 2018-03-23 18:23
Last Updated: 2021-03-28 09:24

Pinned Comments

talone commented on 2021-03-28 10:53

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.

Latest Comments

1 2 3 Next › Last »

talone commented on 2021-03-28 17:40

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.

Spixmaster commented on 2021-03-28 12:56

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

talone commented on 2021-03-28 10:53

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.

talone commented on 2021-03-28 08:10

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.

Spixmaster commented on 2021-03-28 06:27

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

talone commented on 2021-01-22 19:02

Hello FirstAirBender, alesasnouski and everyone,

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

talone commented on 2021-01-18 08:53

Yes, I saw the comment by FirstAirBender and need to have a look at it. This problem was supposed to be fixed by the patch included.

alesasnouski commented on 2021-01-18 08:02

Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/Authenticator/widgets/window.py", line 79, in add_account
    add_window = AddAccountWindow()
  File "/usr/lib/python3.9/site-packages/Authenticator/widgets/accounts/add.py", line 41, in __init__
    self.init_template('AddAccountWindow')
TypeError: <lambda>() takes 0 positional arguments but 1 was given

FirstAirBender commented on 2021-01-15 03:55

Trying to add a new account button gives the following error:

Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/Authenticator/widgets/window.py", line 79, in add_account
    add_window = AddAccountWindow()
  File "/usr/lib/python3.9/site-packages/Authenticator/widgets/accounts/add.py", line 41, in __init__
    self.init_template('AddAccountWindow')
TypeError: <lambda>() takes 0 positional arguments but 1 was given

talone commented on 2020-12-12 20:53

Hello there,

I had to upgrade python-yoyo-migrations to 7.2 because it was flagged out-of-date. Because this package depends on it, there could potentially be problems due to this update; please comment if you experience any trouble.