January 2026 - Aur-general - lists.archlinux.org

Problem connecting to AUR via SSH (User: Venik1821)
by Venik 01 Feb '26

01 Feb '26

Hello, I'm having trouble connecting to the Arch User Repository (AUR) via SSH to manage my packages. I generated a new key pair, ED25519, verified that all local permissions are correct, and gradually added the public key to my profile on the AUR website (User: Venik1821). However, I keep getting the error "Permission denied (public key)" when connecting using the "ssh aur" command. I've already performed all the standard troubleshooting steps (checking permissions, using IdentitiesOnly, regenerating keys, verifying the public/private key integrity). Below is the full debug output of the 'ssh -vvv aur' command: debug1: OpenSSH_10.2p1, OpenSSL 3.6.1 27 Jan 2026 debug3: Running on Linux 6.18.7-x64v2-xanmod1 #0~20260123.g58e1b7b SMP PREEMPT_DYNAMIC Fri Jan 23 16:28:56 UT C x86_64 debug3: Started with: ssh -vvv aur debug1: Reading configuration data /home/venik/.ssh/config debug1: /home/venik/.ssh/config line 1: Applying options for aur debug1: Reading configuration data /etc/ssh/ssh_config debug3: /etc/ssh/ssh_config line 2: Including file /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf depth 0 debug1: Reading configuration data /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/venik/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/venik/.ssh/known_hosts2' debug2: resolving "aur.archlinux.org" port 22 debug3: resolve_host: lookup aur.archlinux.org:22 debug3: channel_clear_timeouts: clearing debug3: ssh_connect_direct: entering debug1: Connecting to aur.archlinux.org [209.126.35.78] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0xb8 debug1: Connection established. debug1: loaded pubkey from /home/venik/.ssh/id_aur: ED25519 SHA256:7EMZei8mAP4DgvB2YVKd7hO9tB6H5ZD+Vd/TzWeLwC Q debug1: identity file /home/venik/.ssh/id_aur type 2 debug1: no identity pubkey loaded from /home/venik/.ssh/id_aur debug1: Local version string SSH-2.0-OpenSSH_10.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_10.2 debug1: compat_banner: match: OpenSSH_10.2 pat OpenSSH* compat 0x04000000 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to aur.archlinux.org:22 as 'Venik1821' debug3: record_hostkey: found key type RSA in file /home/venik/.ssh/known_hosts:2 debug3: record_hostkey: found key type ECDSA in file /home/venik/.ssh/known_hosts:4 debug3: record_hostkey: found key type ED25519 in file /home/venik/.ssh/known_hosts:6 debug3: load_hostkeys_file: loaded 3 keys from aur.archlinux.org debug1: load_hostkeys: fopen /home/venik/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug3: order_hostkeyalgs: have matching best-preference key type ssh-ed25519-cert-v01(a)openssh.com, using Hos tkeyAlgorithms verbatim debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: mlkem768x25519-sha256,sntrup761x25519-sha512, sntrup761x25519-sha512(a)openssh.com,curve 25519-sha256,curve25519-sha256(a)libssh.org ,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hel lman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14 -sha256,ext-info-c,kex-strict-c-v00(a)openssh.com debug2: host key algorithms: ssh-ed25519-cert-v01(a)openssh.com, ecdsa-sha2-nistp256-cert-v01(a)openssh.com,ecdsa- sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com ,sk-ssh-ed25519-cert-v01(a)openssh.c om,sk-ecdsa-sha2-nistp256-cert-v01(a)openssh.com, rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openss h.com ,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521, sk-ssh-ed25519(a)openssh.com,sk-e cdsa-sha2-nistp256(a)openssh.com,rsa-sha2-512,rsa-sha2-256 debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-gcm@openssh.com, aes256-gcm(a)openssh.com,aes128-ctr, aes192-ctr,aes256-ctr debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-gcm@openssh.com, aes256-gcm(a)openssh.com,aes128-ctr, aes192-ctr,aes256-ctr debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com, hmac-sha2-256-etm(a)openssh.com,hmac-sha2-5 12-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com, umac-128(a)openssh.com,hmac-sha2-256,hmac-sha2 -512,hmac-sha1 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com, hmac-sha2-256-etm(a)openssh.com,hmac-sha2-5 12-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com, umac-128(a)openssh.com,hmac-sha2-256,hmac-sha2 -512,hmac-sha1 debug2: compression ctos: none,zlib(a)openssh.com debug2: compression stoc: none,zlib(a)openssh.com debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug2: peer server KEXINIT proposal debug2: KEX algorithms: mlkem768x25519-sha256,sntrup761x25519-sha512, sntrup761x25519-sha512(a)openssh.com,curve 25519-sha256,curve25519-sha256(a)libssh.org ,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,ext-info-s ,kex-strict-s-v00(a)openssh.com debug2: host key algorithms: rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-gcm@openssh.com, aes256-gcm(a)openssh.com,aes128-ctr, aes192-ctr,aes256-ctr debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-gcm@openssh.com, aes256-gcm(a)openssh.com,aes128-ctr, aes192-ctr,aes256-ctr debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com, hmac-sha2-256-etm(a)openssh.com,hmac-sha2-5 12-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com, umac-128(a)openssh.com,hmac-sha2-256,hmac-sha2 -512,hmac-sha1 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com, hmac-sha2-256-etm(a)openssh.com,hmac-sha2-5 12-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com, umac-128(a)openssh.com,hmac-sha2-256,hmac-sha2 -512,hmac-sha1 debug2: compression ctos: none,zlib(a)openssh.com debug2: compression stoc: none,zlib(a)openssh.com debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug3: kex_choose_conf: will use strict KEX ordering debug1: kex: algorithm: mlkem768x25519-sha256 debug1: kex: host key algorithm: ssh-ed25519 debug1: kex: server->client cipher: chacha20-poly1305(a)openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha20-poly1305(a)openssh.com MAC: <implicit> compression: none debug3: send packet: type 30 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug3: receive packet: type 31 debug1: SSH2_MSG_KEX_ECDH_REPLY received debug1: Server host key: ssh-ed25519 SHA256:RFzBCUItH9LZS0cKB5UE6ceAYhBD5C8GeOBip8Z11+4 debug3: record_hostkey: found key type RSA in file /home/venik/.ssh/known_hosts:2 debug3: record_hostkey: found key type ECDSA in file /home/venik/.ssh/known_hosts:4 debug3: record_hostkey: found key type ED25519 in file /home/venik/.ssh/known_hosts:6 debug3: load_hostkeys_file: loaded 3 keys from aur.archlinux.org debug1: load_hostkeys: fopen /home/venik/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug1: Host 'aur.archlinux.org' is known and matches the ED25519 host key. debug1: Found key in /home/venik/.ssh/known_hosts:6 debug3: send packet: type 21 debug1: ssh_packet_send2_wrapped: resetting send seqnr 3 debug2: ssh_set_newkeys: mode 1 debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: Sending SSH2_MSG_EXT_INFO debug3: send packet: type 7 debug1: expecting SSH2_MSG_NEWKEYS debug3: receive packet: type 21 debug1: ssh_packet_read_poll2: resetting read seqnr 3 debug1: SSH2_MSG_NEWKEYS received debug2: ssh_set_newkeys: mode 0 debug1: rekey in after 134217728 blocks debug2: KEX algorithms: mlkem768x25519-sha256,sntrup761x25519-sha512, sntrup761x25519-sha512(a)openssh.com,curve 25519-sha256,curve25519-sha256(a)libssh.org ,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hel lman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14 -sha256,ext-info-c,kex-strict-c-v00(a)openssh.com debug2: host key algorithms: ssh-ed25519-cert-v01(a)openssh.com, ecdsa-sha2-nistp256-cert-v01(a)openssh.com,ecdsa- sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com ,sk-ssh-ed25519-cert-v01(a)openssh.c om,sk-ecdsa-sha2-nistp256-cert-v01(a)openssh.com, rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openss h.com ,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521, sk-ssh-ed25519(a)openssh.com,sk-e cdsa-sha2-nistp256(a)openssh.com,rsa-sha2-512,rsa-sha2-256 debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-gcm@openssh.com, aes256-gcm(a)openssh.com,aes128-ctr, aes192-ctr,aes256-ctr debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-gcm@openssh.com, aes256-gcm(a)openssh.com,aes128-ctr, aes192-ctr,aes256-ctr debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com, hmac-sha2-256-etm(a)openssh.com,hmac-sha2-5 12-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com, umac-128(a)openssh.com,hmac-sha2-256,hmac-sha2 -512,hmac-sha1 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com, hmac-sha2-256-etm(a)openssh.com,hmac-sha2-5 12-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com, umac-128(a)openssh.com,hmac-sha2-256,hmac-sha2 -512,hmac-sha1 debug2: compression ctos: none,zlib(a)openssh.com debug2: compression stoc: none,zlib(a)openssh.com debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug3: send packet: type 5 debug3: receive packet: type 7 debug1: SSH2_MSG_EXT_INFO received debug3: kex_input_ext_info: extension server-sig-algs debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa -sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com ,rsa-sha2-512,rsa-sha2-256> debug3: kex_input_ext_info: extension publickey-hostbound(a)openssh.com debug1: kex_ext_info_check_ver: publickey-hostbound(a)openssh.com=<0> debug3: kex_input_ext_info: extension ping(a)openssh.com debug1: kex_ext_info_check_ver: ping(a)openssh.com=<0> debug3: receive packet: type 6 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug3: send packet: type 50 debug3: receive packet: type 7 debug1: SSH2_MSG_EXT_INFO received debug3: kex_input_ext_info: extension server-sig-algs debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa -sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com ,rsa-sha2-512,rsa-sha2-256> debug3: receive packet: type 51 debug1: Authentications that can continue: publickey debug3: start over, passed a different list publickey debug3: preferred publickey,keyboard-interactive,password debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug3: ssh_get_authentication_socket_path: path '/home/venik/.ssh/agent/s.6aEaxAqYZx.agent.bSN50DTxCl' debug1: get_agent_identities: bound agent to hostkey debug1: get_agent_identities: ssh_fetch_identitylist: agent contains no identities debug1: Will attempt key: /home/venik/.ssh/id_aur ED25519 SHA256:7EMZei8mAP4DgvB2YVKd7hO9tB6H5ZD+Vd/TzWeLwCQ explicit debug2: pubkey_prepare: done debug1: Offering public key: /home/venik/.ssh/id_aur ED25519 SHA256:7EMZei8mAP4DgvB2YVKd7hO9tB6H5ZD+Vd/TzWeLw CQ explicit debug3: send packet: type 50 debug2: we sent a publickey packet, wait for reply debug3: receive packet: type 51 debug1: Authentications that can continue: publickey debug2: we did not send a packet, disable method debug1: No more authentication methods to try. Venik1821(a)aur.archlinux.org: Permission denied (publickey).

2 1

Freerdp2 package installed for seemingly no reason
by Keon Cachia 30 Jan '26

30 Jan '26

The aur package freerdp2 was installed on my system when I had no packages depending on it and had not explicitly installed it. I saw that there is is package called freerdp in the extra repo with the same contributor mentioned. Is this like GTK2? If so, I still don't understand why it was on my system when I didn't have any packages beforehand that depended on freerdp2 afaik.

2 2

New package: zimfw
by Eric Nielsen 24 Jan '26

24 Jan '26

Hi, This is my first time attempting to create an AUR package. I'd like to submit it to the official repository (the extra repository, to my understanding) and would appreciate a review of the PKGBUILD beforehand: https://gist.github.com/ericbn/d6b11516306f1673c0fb38f8abb10a94 Thank you, Eric

2 2

Sanity check on first PKGBUILD
by Garrett 24 Jan '26

24 Jan '26

Howdy y'all - I found a neat project called [RMPC-Auto-Theme](https://github.com/animegolem/RMPC-Auto-Theme) that generates rmpc themes from album art, and to build up my portfolio, I figured I'd try adding it to the AUR. I've created a [pkgbase](https://dl.depot.4d2.org/CClGAodB6ZtU.tar.xz) that I'd like to push - I bootstrapped from a PKGBUILD make by `cargo-pkgbuild`, have been using an install for the day from a local `makepkg -si`, and got it to build in a `pkgctl build` with no errors from `namcap` - but I'd like a sanity check on licensing and reproducibility first. * I didn't understand the `REUSE.toml` business from `pkgctl license setup` and `pkgctl license check` so, rather than use Arch's `0BSD` license, just copied the MIT license from upstream - is this valid? * There was some strangeness with the `checkpkg`: ``` Checking PKGBUILD Checking rmpc-auto-theme-git-debug-r22.e0f6399-1-x86_64.pkg.tar.zst rmpc-auto-theme-git-debug W: Directory (usr/src/debug/rmpc-auto-theme-git) is empty Checking rmpc-auto-theme-git-r22.e0f6399-1-x86_64.pkg.tar.zst ==> Running checkpkg error: target not found: rmpc-auto-theme-git ==> WARNING: Skipped checkpkg due to missing repo packages ==> Generating .SRCINFO...done ``` Is this cause for concern? * Otherwise, does everything read sanely? If everything looks good, I'll push to the AUR and also request from upstream that they add the AUR link to their repo. Cheers, appreciate y'all's input! Garrett

3 2

godot-next-bin existence conflict needing higher moderation
by Nova Bürky 24 Jan '26

24 Jan '26

The Package godot-next-bin was deleted previously cause it was identical to godot-preview-bin. We can see in the git history it was the same. freehuntx has recreated it, with an disingenuous comment against me. Because of a mistake of mine, sending deletion requests for packages they had given up for a span of 2 days (until they realized that it wasn't an decision process initiated by the AUR Maintainers, but by me), the maintainer freehuntx does assume i am a malicious actor and am actively hurting the open source community. The previous successful delete-request implies preference for the godot-preview-bin package as a name, and the one benefit of now providing a mono build should be in godot-preview-bin I do not think freehuntx should be maintainer for any package that just repackages godot versions, and through their implicit presumptions that packages (for software that he doesn't even develop in the case of godot-next-bin) that they maintain are in their ownership, is hurting the open source spirit (a thing they accuse me regularly (in the comments of godot-beta-bin and godot-next-bin)) more than me making mistakes. I personally do see a case for godot-beta-bin to exist, but frankly that one is just excluding dev builds out of the whole process that godot-preview-bin does too. And possibly also RC versions, cause that package hasnt been updated ever to include RC versions. I am not sending a request (merge, delete, orphan) of any kind here for godot-next-bin, because i think this is a issue for moderation and freehuntx would probably just remake those packages.

1 1

Add detail to deletion emails due to TU adoption
by Gesh 20 Jan '26

20 Jan '26

Hi, TL;DR: the notification emails when AUR packages are adopted by TUs are indistinguishable from deletions, and communications norms around them makes it hard to discover otherwise. Please change either or both. I recently was notified that three packages I was monitoring had been deleted from AUR, with no further detail beyond eg > grawlinson [1] deleted python-markdownify [2]. > > You will no longer receive notifications about this package. > > [1] https://aur.archlinux.org/account/grawlinson/ > [2] https://aur.archlinux.org/pkgbase/python-markdownify/ Concerned, I checked whether I was still using them, and indeed I was -- python-markdownify is an optdepend of papis. I was just about to contact the previous maintainer about the abrupt deletion (instead of disownment) -- I'd checked the ML archives and couldn't find any mention of such plans -- when I realised grawlinson is actually a TU. On a hunch, since this isn't the first time this has happened, I checked > $ pacman -Si python-markdownify > Repository : extra > Name : python-markdownify > Version : 1.2.2-2 > Description : Convert HTML to Markdown > Architecture : any > URL : https://github.com/matthewwithanm/python-markdownify > Licenses : MIT > Groups : None > Provides : None > Depends On : python python-beautifulsoup4 > Optional Deps : None > Conflicts With : None > Replaces : None > Download Size : 30.74 KiB > Installed Size : 128.32 KiB > Packager : George Rawlinson <grawlinson(a)archlinux.org> > Build Date : Thu 15 Jan 2026 03:48:32 > Validated By : SHA-256 Sum Signature Of course, once the package updates and pacman notices a newer version exists in extra, it *will* notify me of that. However, in the absence of that, I needed to luck into guessing what had happened. Instead, the following three possibilities suggest themselves to avoid this situation again: - Have moving from AUR to repos be a change warranting a pkgrel bump. - Change TU adoption policy to require a form announcment to aur-general. - Have TU adoption trigger a distinct automated email from aurweb to listeners. Any or all of these would've been enough to save me the detective work. Thanks, Gesh

1 0

Request: Package Removal: alterfalter
by linux_service＠gmx.de 15 Jan '26

15 Jan '26

Please remove this package: alterfalter This software is not helping any one. It is a shame, that this software is still available in the AUR. If you want war, I can recommned the french legion etrangère. Merci beaucoup

1 0

Request: Package Removal: whisparr-nightly-bin
by linux_service＠gmx.de 15 Jan '26

15 Jan '26

Please remove this package: whisparr-nightly-bin This software is not helping any one. Every one who has adultmovies and feels the need to organize them has lost the connection to real life. Do yourself a favour and delete this package. I guess you can see yourself now, what pornofication did to humanity.

1 0

Guidance on renaming helium-browser-bin
by Sam Sinclair 02 Jan '26

02 Jan '26

Hello everyone, I maintain the /helium-browser-bin/ packaging, and I'm considering a rename to /helium-bin/, which I've also put forward to the community in the comments. This consideration comes as upstream Linux packaging matures [1]. When I submitted the package initially, my thinking was to append /-browser/ to avoid potential naming conflicts, but it now seems unnecessary and isn't consistent with upstream. I was hoping to get some guidance on whether a rename is reasonable in this case, and if so, how to best go about it while minimising problems for end users. My current plan is: 1. Submit the /helium-bin/ package to the AUR as normal 2. Add `conflicts=('helium-browser-bin')' to /helium-bin/ PKGBUILD to allow users to cleanly remove the old version on install 3. Push existing package to the new repo to preserve git history 4. Initiate a merge request for /helium-browser-bin/ to /helium-bin/ to preserve comments and remove the old package I would do this after the next release at the time while keeping users up to date. I've tested packaging locally with success, and impacts to users should be constrained to the package name and install paths removing the 'browser' suffix. The entry point remains `/usr/bin/helium-browser'. Questions :: - Is this the correct/preferred method? - While in between merge requests, which repo should I treat as the source of truth in the case of updates? - Anything that I've missed? Thanks very much in advance! Cheers, Sam [1]: https://github.com/imputnet/helium-linux/pull/149

1 0