- Aur-general - lists.archlinux.org

Package Maintainer application
by Claudia Pellegrino 11 Apr '26

11 Apr '26

Hi! I’m Claudia aka Auerhuhn [1] from Darmstadt, Germany (@claui on GitHub [2]), and I’d love to join your team as a Package Maintainer. When I’m not busy putting stuff into packages (e.g. on the AUR), you can probably find me playing the piano, maintaining personal side projects in Python and other languages, and generally learning things. At my day job as a software developer for DB Systel, I maintain software that displays coach and seat numbers on trains so passengers know where to board („Reisendeninformation“). I was a maintainer with Homebrew for seven years, first with Cask [3] and later as a core team member [4], maintaining formulae and the CLI. I also helped bootstrap and orchestrate the aarch64 migration [5]. In 2021, I decided to leave the Apple ecosystem [6], even though that meant I had to say farewell to my fellows from Homebrew [7]. I’ve been daily driving Arch Linux ever since. I’m pretty much invested in free and open-source software: my phone runs a mobile Debian, and according to an LLM-generated roast, I’m a “FOSS Martyr.” When you meet me in person, ask me how life is going with absolutely no apps. Or don’t; I’ll probably tell you about it anyway. On `extra`, I’d like to maintain a couple of packages that I think will be useful for the CLI crowd: python-xlsx2csv (Excel textconv for Git), aider-chat (a FOSS alternative to Copilot), and python-llm. I’m also looking into adopting a number of entries from the list of orphaned Python packages [8] and possibly co-maintaining those that currently have only one maintainer. I’ve been occasionally contributing to Arch projects as well, e.g. namcap and aurweb [9], and will continue to do so if time allows. Thanks to Gromit and Anthraxx for sponsoring my application. Regards Claudia [1]: https://aur.archlinux.org/packages?SeB=M&K=Auerhuhn [2]: https://github.com/claui [3]: https://github.com/Homebrew/homebrew-cask/pull/7705 [4]: https://github.com/Homebrew/brew/commit/ba410959 [5]: https://github.com/Homebrew/brew/issues/7857 [6]: https://web.archive.org/web/20210811115015/https://twitter.com/c_pellegrino… [7]: https://github.com/Homebrew/brew/commit/7c799c4e [8]: https://archlinux.org/packages/?q=python-&maintainer=orphan [9]: https://gitlab.archlinux.org/auerhuhn

7 12

Stale snapshots in the AUR
by Andreas Baumann 10 Apr '26

10 Apr '26

Hi all, I got report that AUR download snapshots are stale. See: https://aur.archlinux.org/packages/pacman-static#comment-1066707 File /tmp/mutt-eurox-500-25464-10703324287384108442 not changed so no update needed 1208 kept, 0 deleted. abaumann@eurox:~> cat > /dev/null Hi all, I got report that AUR download snapshots are stale. See: https://aur.archlinux.org/packages/pacman-static#comment-1066707 https://aur.archlinux.org/packages/pacman-static#comment-1066703 Is there a check-in hook or a background process not running for the snapshot generation? Cheers Andreas -- Andreas Baumann Trottenstrasse 20 CH-8037 Zuerich Telefon: +41(0)76/373 01 29 E-mail: mail(a)andreasbaumann.cc Homepage: www.andreasbaumann.cc

1 0

Can I maintain ttf-hanazono on the AUR?
by keonfarrugia＠gmail.com 07 Apr '26

07 Apr '26

4 3

Can I maintain ttf-hanazono on the AUR?
by keonfarrugia＠gmail.com 03 Apr '26

03 Apr '26

Ttf-hanazono was dropped from the main repositories and I wanted to ask if it was on purpose. It seems to be that way and that is why I have already made a package.(I didn't read the package's issue board before the last email, my bad). I'm sorry about the encrypted email, this is my first time sending non-test mail using Gnus and I accidentally encrypted instead of signed. I won't do it again. Keon Cachia

1 0

Fwd: Update AUR package DbSchema
by Тимофей 27 Mar '26

27 Mar '26

Hi, I have contacted the current maintainer of the DbSchema AUR package ( marcin.j.nowak(a)gmail.com) requesting to be added as a co-maintainer, as the package is outdated and fails to build due to checksum mismatch. Version 10.1.0 is available, and I have prepared a working PKGBUILD with updated checksums. However, I have not received a response from the maintainer within a reasonable timeframe. I would like to either: 1. Be added as a co-maintainer to keep the package updated, or 2. Adopt the package if the current maintainer is unavailable I am committed to maintaining this package and ensuring it stays up to date. Thank you! -------- Перенаправленное сообщение -------- Тема: Update AUR package DbSchema Дата: Wed, 7 Jan 2026 15:25:45 +0300 От: Тимофей Бруханчик <asyncbtd(a)gmail.com> <asyncbtd(a)gmail.com> Кому: marcin.j.nowak(a)gmail.com Hi, I noticed that the current AUR package for DbSchema is outdated and fails to build due to checksum mismatch. A new version (10.0.2) is available, and I’ve prepared a working PKGBUILD with updated checksums. Could you please add me as a co-maintainer so I can keep the package up to date? Thanks!

4 3

PKGBUILD licenses
by manganeese 26 Mar '26

26 Mar '26

Hello! I have a couple of questions, mostly regarding licensing for PKGBUILDs. 1. What should be put as the license for projects that have a license similar to a SPDX license, but doesn't match any? * One example of this would be allwpilib[1], which has a license very similar to the BSD 3-clause license, but since it has the word "NONINFRINGEMENT" after "MERCHANTABILITY", it doesn't match as the BSD 3-clause license (if I am reading the SPDX matching guidelines correctly) 2. I have a PKGBUILD that I made for allwpilib, and I needed to create a patch to allow it to build with -O2 instead of -O3. Should this patch be licensed under 0BSD, or the aforementioned modified BSD 3-clause license? I was thinking of submitting the PKGBUILD for allwpilib to the AUR, and any feedback would be greatly appreciated! I put a tarball with everything on google drive[2]. [1]: https://github.com/wpilibsuite/allwpilib [2]: https://drive.google.com/file/d/1oY2cfxBIaBDzEerZ1AJHniI4dT_UpOBZ/view

2 1

AUR package with python venv
by 7thCore 23 Mar '26

23 Mar '26

Hello, I want to submit five packages to the AUR for the Psono Password Manager. It's open source and I got permission from the developer to do so with the disclaimer that they are not officially supported. Three of these packages require a python virtual environment (due to the extensive list of python dependencies that are not available in the Arch Linux repositories) and the way I initially approached this was to use the post_install() function in the install script. Here's the PKGBUILD review link on the forums: https://bbs.archlinux.org/viewtopic.php?id=312591 With the advice of Lone_Wolf and twelveeighty I moved the venv creation to the build() function of the PKGBUILD. Psono is only available in a docker image format so I created a custom dlagent to download the docker image, extract the software I need for the package, tarball it and use the tarball as a source file for hash verification. Using a constant mtime value while creating the tarball makes sure the hash stays the same with the same files if they aren't changed upstream. My question for the AUR moderators and package maintainers is as follows: the python venv is created when building the package and is shipped with the package. Is this acceptable for the AUR? What's your opinion? Am I allowed to submit these packages like they are? I also attached one of the three packages' source so you can test building it yourself. Currently it doesn't have licenses set up yet. It's the enterprise edition of Psono's server software. There's also a community edition available that's free that I also intend to submit if allowed. The hashes should be up to date with the enterprise edition. Let me know what you think. Kind regards, 7thCore

5 6

davinci-resolve no longer downloads the upstream package; was this actually an AUR rules violation?
by kleines Filmröllchen 22 Mar '26

22 Mar '26

Hello all, this issue has been on my mind for a while, but I haven’t bothered to write to the mailing list about it until now. Before Muflone took over maintainership of the davinci-resolve packages (including davinci-resolve-studio and davinci-resolve-beta), the PKGBUILD would automatically download the upstream package from Blackmagic’s website. While Resolve is proprietary, the non-Studio version (and the beta) are freely available, requiring not even a proper login with the vendor. The download link on the website (https://www.blackmagicdesign.com/products/davinciresolve ) is behind a “registration” form, but this does not create a user account and to the best external knowledge, the data entered here is never verified in any way. Therefore, previous versions of the AUR package either used a download link obtained by the maintainer after filling out the form with arbitrary data, or replayed the form submission with fixed data during prepare(), obtaining a new download link for the user. Either way, the package contents are obviously always identical (regular hashing applied). The same is true for packages retrieved through the support center (https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion ), where in fact the Studio version (which requires a paid license) does not require the submission of a form at all. However, Muflone changed this behavior to instead require a locally-downloaded version of the upstream package in all three cases. The user reception for this was mixed, additionally caused by the issue that AUR helpers need the upstream package file located in special cache directories and not the current working directory. Personally, I am strongly opposed to this change, but Muflone has deflected criticism by pointing out that “Packages must not contain black magic or unknown/hard to understand commands as users are required to check the PKGBUILDs before installing/updating from AUR” (https://aur.archlinux.org/packages/davinci-resolve?O=60#comment-1013733 ). While I agree in spirit, I disagree in this specific case. There are multiple easy ways of obtaining the package that have been known for some time; a review of the package commit history confirms this. On the contrary, some of the changes required to make more technical aspects of the package work properly will not be easy to understand for users at times. Furthermore, a careful review of the AUR rules reveals to me that this kind of direct download is perfectly allowed, since in my opinion it doesn’t circumvent any real technical measures by the upstream provider; see elaboration above: form contents are not checked by the Blackmagic website, and sometimes skippable altogether. I’m writing to the mailing list to gain clarification on the matter: whether the manual download is actually more compliant with AUR rules than what was happening previously (before commit 7351177b553aa3983163450822bf251ec7f7ab75), and whether the previous approach was even in violation. If not, I’m not sure—if it’s possible that the AUR maintainers can urge Muflone to change it back, that would be excellent, but I don’t remember the AUR working that way. Blocking Muflone and/or orphaning the package is also not a reasonable approach, unless there is someone to step up to maintainership for the package (unfortunately not me, as I don’t use Resolve frequently enough, and often need to stay on older versions due to bugs frequently introduced in new releases). I hope I’m not overstepping any lines with this request, but as a user of the package it is very annoying when a (new) maintainer degrades the user experience for unclear/nebulous “rules compliance” and refuses to engage in discussions about it. This is also the reason I am writing here in the first place, I want to make it clear that I did of course try to discuss this on the package comment page first; over a year ago in fact. I also finally want to make it clear that this is not about piracy of the Studio version in any way shape or form; while the package download for it is still freely available from Blackmagic, it’s less important to change the PKGBUILD as the software isn’t free in the first place. Greetings, kleines Filmröllchen

12 15

Unsubscribe from list please
by Bernd Kaßel 20 Mar '26

20 Mar '26

2 1

Deletion request: "fuck" (empty repo, no package)
by Ronan Hevenor 16 Mar '26

16 Mar '26

Hi, I'd like to request deletion of the AUR repo "fuck" ( https://aur.archlinux.org/cgit/aur.git/log/?h=fuck) The repo was created by eshnd in September 2025 with three throwaway commits ("test", "added all", "/"). No valid PKGBUILD or .SRCINFO was ever pushed, so the package doesn't appear in AUR search or have a package page. It's effectively a name squat on an empty repo. I have a legitimate package I'd like to publish under this name. Thanks, Ronan

6 6