Package Details: ausweisapp2 2.1.1-1

Git Clone URL: (read-only, click to copy)
Package Base: ausweisapp2
Description: A software application that you install on your computer to use your national identity card or your electronic residence permit for online identification
Upstream URL:
Licenses: custom:EUPL1.2
Submitter: J5lx
Maintainer: Misery
Last Packager: Misery
Votes: 69
Popularity: 3.44
First Submitted: 2017-09-15 18:13 (UTC)
Last Updated: 2024-04-12 18:59 (UTC)

Pinned Comments

williX commented on 2022-09-18 17:08 (UTC) (edited on 2022-09-18 17:09 (UTC) by williX)

Thanks to older comments, problem with unknown pgp key is solved. Had to enter

gpg --keyserver --recv-keys 699BF3055B0A49224EFDE7C72D7479A531451088

I tried several keyservers, but was the right one.

Latest Comments

1 2 3 4 5 6 .. 12 Next › Last »

mroethke commented on 2024-04-24 08:47 (UTC)


Instead of changing the PKGBUILD you can also change either the global(/etc/makepkg.conf) makepkg config or create a user specific one(~/.makepkg.conf or $XDG_CONFIG_HOME/pacman/makepkg.conf where $XDG_CONFIG_HOME is most likely ~/.config) and overwrite the setting there.

This has the advantage, that it disables debug packages for all packages, not just this one.

martin-de commented on 2024-04-24 08:31 (UTC)

Since there is no bug tracker for the application and I know that the developer is reading here, I'm sharing my experiences here, even if they don't directly relate to building the package.

After installing version 2.1.x, the paired devices could no longer be seen on the PC. After downgrading to version 2.0.3, the devices were visible again. After I re-paired the smartphone with the PC via the app, the smartphone was visible and the PC was visible twice in the app.

Apparently old connections from versions before 2.1.x are no longer recognized in the current version and the devices have to be re-paired.

In addition, the home page now appears every time you start it; previously the application was moved directly to the systray.

martin-de commented on 2024-04-24 08:30 (UTC)

@pand0ra: The debug packages have been built for some time because the standard settings have changed. If you don't want a debug package, override the setting with



pand0ra commented on 2024-04-17 17:34 (UTC)

Hello, sorry if this is a stupid question, but when using yay to get ausweisapp2, at the end I got prompted to install ausweisapp2 and ausweisapp2-debug. Is this okay? I was a little confused because this debug-package like came out of nowhere. It doesn't seem to exist on it's own in the aur and isn't a dependency to anything. Is it normal, that some packages come up with a debug-package like this?

BlauFx commented on 2024-04-13 14:42 (UTC)

I also the same error "merging /home/user/.cache/yay/ausweisapp2: fatal: No current branch."

Deleting the cache fixed it for me. rm -rf /home/$USER/.cache/yay/ausweisapp2

ng0177 commented on 2024-04-13 07:14 (UTC) (edited on 2024-04-13 07:17 (UTC) by ng0177)

AUR Explicit (1): ausweisapp2-2.1.1-1
Sync Dependency (2): qt6-websockets-6.7.0-1, qt6-scxml-6.7.0-1
Sync Make Dependency (1): qt6-tools-6.7.0-2
:: PKGBUILD up to date, skipping download: ausweisapp2
 -> error merging /home/user/.cache/yay/ausweisapp2: fatal: No current branch.

aur_person23 commented on 2024-04-12 19:07 (UTC) (edited on 2024-04-12 19:09 (UTC) by aur_person23)

Thank you, now the update works for me.

Misery commented on 2024-04-12 19:01 (UTC)

Strange... I did a "git push" again.

mroethke commented on 2024-04-12 18:58 (UTC)

The commit with the update was pushed, but the master branch was not updated. If you clone the repository you get a detached head pointing at the latest commit. If you already have the repository and pull you won't get it since it is not part of a branch.

I have no idea how something like this might have happened, maybe you can try pushing again?

aur_person23 commented on 2024-04-12 18:48 (UTC) (edited on 2024-04-12 18:57 (UTC) by aur_person23)

@Misery that's strange, I see that you updated the pkgver to 2.1.1 here:

but when using the ==> PKGBUILDs to edit? option in yay to inspect the PKGBUILD it still shows pkgver=2.1.0:

# Maintainer: A. Klitzing <>



I guess that's what is causing the loop for some people.

I already tried manually updating my mirrors.

EDIT: When I use yay -Gp ausweisapp2 (Print to stdout PKGBUILD from AUR) it shows the correct pkgver. Very strange:

# ausweisapp2

# Maintainer: A. Klitzing <>