- Aur-general - lists.archlinux.org

TU Application - tpkessler
by Torsten Keßler 20 Nov '22

20 Nov '22

Hi! I'm Torsten Keßler (tpkessler in AUR and on GitHub) from Saarland, a federal state in the south west of Germany. With this email I'm applying to be become a trusted user. After graduating with a PhD in applied mathematics this year I'm now a post-doc with a focus on numerical analysis, the art of solving physical problems with mathematically sound algorithms on a computer. I've been using Arch Linux on my private machines (and at work) since my first weeks at university ten years ago. After initial distro hopping a friend recommended Arch. I immediately liked the way it handles packages via pacman, its wiki and the flexibility of its installation process. Owing to their massively parallel architecture, GPUs have emerged as the leading platform for computationally expensive problems: Machine Learning/AI, real-world engineering problems, simulation of complex physical systems. For a long time, nVidia's CUDA framework (closed source, exclusively for their GPUs) has dominated this field. In 2015, AMD announced ROCm, their open source compute framework for GPUs. A common interface to CUDA, called HIP, makes it possible to write code that compiles and runs both on AMD and nVidia hardware. I've been closely following the development of ROCm on GitHub, trying to compile the stack from time to time. But only since 2020, the kernel includes all the necessary code to compile the ROCm stack on Arch Linux. Around this time I've started to contribute to rocm-arch on GitHub, a collection of PKGBUILDs for ROCm (with around 50 packages). Soon after that, I became the main contributor to the repository and, since 2021, I've been the maintainer of the whole ROCm stack. We have an active issue tracker and recently started a discussion page for rocm-arch. Most of the open issues as of now are for bookkeeping of patches we applied to run ROCm on Arch Linux. Many of them are linked to an upstream issue and a corresponding pull request that fixes the issues. This way I've already contributed code to a couple of libraries of the ROCm stack. Over the years, many libraries have added official support for ROCm, including tensorflow, pytorch, python-cupy, python-numba (not actively maintained anymore) and blender. Support of ROCm for the latter generated large interest in the community and is one reason Sven contacted me, asking me if I would be interested to take care of ROCm in [community]. In its current version, ROCm support for blender works out of the box. Just install hip-runtime-amd from the AUR and enable the HIP backend in blender's settings for rendering. The machine learning libraries require more dependencies from the AUR. Once installed, pytorch and tensorflow are known to work on Vega GPUs and the recent RDNA architecture. My first action as a TU would be to add basic support of ROCm to [community], i.e. the low level libraries, including HIP and an open source runtime for OpenCL based on ROCm. That would be enough to run blender with its ROCm backend. At the same time, I would expand the wiki article on ROCm. The interaction with the community would also move from the issue tracker of rocm-arch to the Arch Linux bug tracker and the forums. In a second phase I would add the high level libraries that would enable users to quickly compile and run complex libraries such as tensorflow, pytorch or cupy. #BEGIN Technical details The minimal package list for HIP which includes the runtime libraries for basic GPU programming and the GPU compiler (hipcc) comprises eight packages * rocm-cmake (basic cmake files for ROCm) * rocm-llvm (upstream llvm with to-be-merged changes by AMD) * rocm-device-libs (implements math functions for all GPU architectures) * comgr (runtime library, "compiler support" for rocm-llvm) * hsakmt-roct (interface to the amdgpu kernel driver) * hsa-rocr (runtime for HSA compute kernels) * rocminfo (display information on HSA agents: GPU and possibly CPU) * hip-runtime-amd (runtime and compiler for HIP, a C++ dialect inspired by CUDA C++) All but rocm-llvm are small libraries under the permissive MIT license. Since ROCm 5.2, all packages successfully build in a clean chroot and are distributed in the community repo arch4edu. The application libraries for numerical linear algebra, sparse matrices or random numbers start with roc and hip (rocblas, rocsparse, rocrand). The hip* packages are designed in such a way that they would also work with CUDA if hip is configured with CUDA instead of a ROCm/HSA backend. With few exceptions (rocthrust, rccl) these packages are licensed under MIT. Possible issues: There are three packages that are not fully working under Arch Linux or lack an open source license. The first is rocm-gdb, a fork of gdb with GPU support. To work properly it needs a kernel module currently not available in upstream linux but only as part of AMD's dkms modules. But they only work with specific kernel versions. Support for this from my side on Arch Linux was dropped a while ago. One closed source package is hsa-amd-aqlprofile. As the name suggests it is used for profiling as part of rocprofiler. Above mentioned packages are only required for debugging and profiling but are no runtime dependencies of the big machine learning libraries or any other package with ROCm support I'm aware of. The third package is rocm-core, a package only part of the meta packages for ROCm with no influence on the ROCm runtime. It provides a single header and a library with a single function that returns the current ROCm version. No source code has been published by AMD so far and the official package lacks a license file. A second issue is GPU support. AMD officially only supports the professional compute GPUs. This does not mean that ROCm is not working on consumer cards but merely that AMD cannot guarantee all functionalities through excessive testing. Recently, ROCm added support for Navi 21 (RX 6800 onwards), see https://docs.amd.com/bundle/Hardware_and_Software_Reference_Guide/page/Hard… I own a Vega 56 (gfx900) that is officially supported, so I can test all packages before publishing them on the AUR / in [community]. #END Technical details On the long term, I would like to foster Arch Linux as the leading platform for scientific computing. This includes Machine Learning libraries in the official repositories as well as packages for classical "number crunching" such as petsc, trilinos and packages that depend on them: deal-ii, dune or ngsolve. The sponsors of my application are Sven (svenstaro) and Bruno (archange). I'm looking forward to the upcoming the discussion and your feedback on my application. Best, Torsten

7 15

Comment on cemu page
by Fabio Loli 18 Nov '22

18 Nov '22

User Anuskuss have returned today to harass the cemu maintainer https://aur.archlinux.org/packages/cemu#comment-890175 Previous behaviour can be seen on aur-requests about cemu and cemu comments section

1 0

Are CachyOS PKGBUILDs allowed on AUR?
by Frederic Bezies 16 Oct '22

16 Oct '22

Hello. CachyOS - https://cachyos.org/ - is another archlinux based distribution with a lot of custom tools and kernels, using KDE as a GUI. I installed in a VM CachyOS and noticed all its customized package in a dedicated repository. My question is: are these custom PKGBUILD are or not allowed on AUR? Here is a link to all CachyOS related PKGBUILDs (30): https://aur.archlinux.org/packages?O=0&K=cachyos Thanks a lot for your kind answer. -- Frederic Bezies fredbezies(a)gmail.com

3 2

Lost account
by Nielzsen 26 Sep '22

26 Sep '22

Hi, I deleted the gmail address linked to my AUR account "Nielzsen" (which is roman.brasseur(a)gmail.com) Is there a way to recover it despite my mistake? Regards.

2 2

May be http://mirroir.wptheme.fr/archlinux/$repo/os/$arch is failing
by marnout 21 Sep '22

21 Sep '22

Hello every body, I had problems with the updates. For some weeks pacman told me everything is up to date, there is nothing to do. So, I commented the first mirror (http://mirroir.wptheme.fr/archlinux/$repo/os/$arch) and then I had 116 packages to update. Maybe this mirror is failing. For me the problem is solved. Friendly. N.B. Sorry if my English is not good, I do not speak English, but a little. -- Mourad Arnout 25 rue de la Vieille Pierre 79800 Exoudun http://arad.free.fr https://github.com/marnout

2 2

RFC / RFO: Extra (CI) files in AUR packages
by Knut Ahlers 17 Sep '22

17 Sep '22

Hey there, I'd like to fetch some comments / opinions regarding maintaining AUR packages with the help of automated build systems. I do maintain several packages in the AUR containing the typical files as `PKGBUILD`, `.SRCINFO`, files referenced in the `source()` section and a special script `update-version.sh`. This script is not mentioned in the PKGBUILD and not used during the build process. It contains the required steps to figure out the latest version of the package and to patch the PKGBUILD. This script is a) used to document how the package is updated and b) is used by my CI system (atm Jenkins) to check for updates and update the package. (Extra steps to verify the package is still building fine before doing any update are common to all packages and are executed after this package-specific script.) For most of my packages there were no complaints about this and users seem to be happy to get the updates usually delivered within an hour after release. Though in one package (librespeed-cli) I got two comments asking me to remove that script. Now I found no explicit statement in the package / AUR submission guidelines against this. Therefore I'd like to ask other maintainers / TUs for your opinions: Are you strictly against adding a script which documents / is used for the update? Is it fine to keep it there? Shall it be removed though doing no harm? Cheers Knut -- Knut Ahlers Software & Infrastructure Developer Web & Blog: https://ahlers.me/ GPG-Key: 0xD215AD7D (https://knut.in/gpg)

2 1

Re: [aur-general] Why was xenia-git orphaned immeditately?
by Sandy Carter 12 Sep '22

12 Sep '22

Glad to hear it wasn't intentional. I find it very strange indeed that the system accepted the request. I don't remember it being flagged OOD but that's on me. Would you mind orphaning xenia-git so I can pick it up again? It would require some rebasing of the patch branches. On Sun, Sep 11, 2022 at 7:36 PM Alessandro Marchioro < marciozgaming(a)gmail.com> wrote: > Hi, I had the same question, I was trying to get an update to the package > without orphaning but by clicking the link it was automatically orphaned by > the system in no time, instead of respecting the time as per the page > suggestion, is this because it was out of date for over a year? > > I wasn't trying to get access as a maintainer other than make it build > again with a simple patch of the PKGBUILD, due to the fact that I was > trying out the emulator with the latest builds on Arch and saw it on a bad > state. > > I too wanna be sure that you are the maintainer, it wasn't my intention in > being the one for this package. > > Hope you'll understand, > > Alessandro > Il 12 set 2022, 01:30 +0200, Sandy Carter <bwrsandman(a)gmail.com>, ha > scritto: > > Hello, > > I used to maintain xenia-git [1] and have since its creation. I am also > the author of the Linux threading, windowing, debug and other patches that > the package uses. > > At *19:20:00 UTC* today, an orphan request was submitted and immediately > orphaned by user ilbuonmarcio. The user made no attempt to contact me about > the issue either by email or in the comments. If they had, I would have > responded as I usually do to issues in my packages. > > I am active on AUR and have been for over 10 years now. I usually can fix > a package issue in a day to a week. > > According to the arch wiki: > > Orphan requests will be granted after two weeks if the current > maintainer did not react > > I was not given the time to react as it is now a few hours later. > > I would like to request this orphaning be undone and steps can be taken to > avoid this happening again. > > Thank you, > -- > Sandy > > [1] https://aur.archlinux.org/packages/xenia-git > >

1 0

[aur-general] Why was xenia-git orphaned immeditately?
by Sandy Carter 12 Sep '22

12 Sep '22

Hello, I used to maintain xenia-git [1] and have since its creation. I am also the author of the Linux threading, windowing, debug and other patches that the package uses. At *19:20:00 UTC* today, an orphan request was submitted and immediately orphaned by user ilbuonmarcio. The user made no attempt to contact me about the issue either by email or in the comments. If they had, I would have responded as I usually do to issues in my packages. I am active on AUR and have been for over 10 years now. I usually can fix a package issue in a day to a week. According to the arch wiki: > Orphan requests will be granted after two weeks if the current maintainer did not react I was not given the time to react as it is now a few hours later. I would like to request this orphaning be undone and steps can be taken to avoid this happening again. Thank you, -- Sandy [1] https://aur.archlinux.org/packages/xenia-git

1 0

[aur-general] Compiling with CMake
by Guilhem Saurel 09 Sep '22

09 Sep '22

Hi, In AUR, there are many packages with an old-school > mkdir build && cd build > cmake -DCMAKE_INSTALL_PREFIX=/usr .. > make Other packages say they require ninja and use > mkdir build && cd build > cmake -DCMAKE_INSTALL_PREFIX=/usr -G Ninja .. > ninja But I think we should let the end user choose if they want make or ninja, by letting them configure their CMAKE_GENERATOR environment variable¹ Currently if someone has CMAKE_GENERATOR=Ninja in their environment, many AUR packages in the first category will fail, because eg.: > […] > -- Configuring done > -- Generating done > -- Build files have been written to: /home/nim/.cache/paru/clone/octomap/src/octomap-1.9.8/octomap/build > make: *** No targets specified and no makefile found. Stop. And on the other hand for the second case, packages say they require ninja while they would work as well with make. Therefore I think we should ask CMake to compile, no matter which generator is available on the machine and/or was chosen by the user, with: > mkdir build && cd build > cmake -DCMAKE_INSTALL_PREFIX=/usr .. > cmake --build . Or even better > cmake -B build -S . -DCMAKE_INSTALL_PREFIX=/usr > cmake --build build Any opinions ? Should we put that on the wiki² ? Or write an RFC, like ³ ? Cheers ! Guilhem, aka. Nim65s ¹: https://cmake.org/cmake/help/latest/envvar/CMAKE_GENERATOR.html ²: https://wiki.archlinux.org/title/CMake_package_guidelines ³: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/10

2 2

[aur-general] TU Application - blakkheim
by T.J. Townsend 07 Sep '22

07 Sep '22

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello. I'd like to apply to become a trusted user. I started using Arch around 2009 when we still had the curses installer, rc.conf, hal... the good old days. I left at some point and came back as a full-time user about three years ago. You can find me on IRC under the name blakkheim, usually in #archlinux-security since that's my main area of interest. I'm the maintainer or co-maintainer for a few OpenBSD-derived packages in the AUR: openiked, rpki-client, and openbgpd. I've been involved with OpenBSD since 2014 and became a project committer there in early 2016. In the last two years I've submitted just over 150 patches to the Arch bug tracker: https://bugs.archlinux.org/index.php?opened=32638&status[]= Some community packages I'd like to co-maintain are openntpd, opensmtpd, libressl, sndio, mandoc, signify, dnscrypt-proxy, bmake, scrot, firejail, xcalib, mktorrent, parallel, ncmpcpp... And more (frankly, lots more) in the core/extra repos if that option opens up in the future. I keep up with many software projects via their mailing lists and RSS/atom feeds. If I'm accepted, one of my goals will be to get missing security fixes into Arch's repository shortly after their upstream release. The sponsors of my application are dvzrv, kpcyrd, and anthraxx. (yep, three) -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQRUwf0nM2HqUUojd5Pylr3lA2jGzgUCYvuMwwAKCRDylr3lA2jG zvh9AQDOvEQbJdu3vfoPUY+Q+amtiwOatfD7nHje2XcviXF82gD/SL2aw0SNm9/Q sxcT+MltS0EoPTyR+OwOU9lHkpyuFQw= =4mzL -----END PGP SIGNATURE-----

9 16