- Aur-general - lists.archlinux.org

Toxic user activity on AUR and ArchWikiCN
by Kimiblock Moe 01 Jan '25

01 Jan '25

3 2

Package Maintainer Application - Adam Perkowski
by Adam Perkowski 28 Dec '24

28 Dec '24

Dear Arch Linux Package Maintainers, I hope this message finds you well. My name is Adam Perkowski. The usernames I use are: adamperkowski, xx0a_q or xeqo. I am writing to express my interest in applying to become a Package Maintainer. My application is sponsored by Orhun Parmaksız (orhun) and Frederik Schwan (freswa), who have kindly offered their support. I've been actively programming and using Linux since around 2016, with Arch Linux serving as my primary desktop OS since 2021. Over the years, my passion for FOSS and programming has only grown stronger. I live in Poland. In my free time, I enjoy contributing to open-source projects (obviously), experimenting with electronics, listening to and sometimes making music. I also enjoy 3D printing (and derivative technologies) and I do it part-time professionally for a few years now. I am fluent in English and Polish. I also have a basic understanding of German and Russian. Here's a brief overview of my technical skills and experience: Programming Languages: - Primary: Rust, Jule, C, C++ - Additional: Lua, Python, JavaScript, Go, Zig, Bash Package Maintenance Experience: I currently maintain about 50 packages in the AUR [6]. All my packages follow the Arch packaging guidelines with reproducible builds and thorough testing procedures. They can also be found in my "PKGBUILDs" GitHub repository [7]. Online Presence: My GitHub profile [8] showcases my commitment to open source development. I maintain several active projects (mentioned below). My repositories show consistent activity and meaningful contributions. On the Arch Linux GitLab [9], I've been familiarizing myself with the Arch Linux development workflow and infrastructure. While I'm relatively new to it, I've been studying the development processes to prepare for a more active role in package maintenance. My personal website [10] serves as a technical portfolio and blog where I document my experiences primarily with open source development. It reflects my approach to software development and commitment to sharing knowledge with the community. I plan on updating it regularly but we all know how that goes. Since 2023 I have been actively contributing to open-source projects. My most notable contributions include: - HighlightOS [1]: A x86_64 kernel in Rust & Assembly - Maintainer Demonstrates low-level systems programming expertise and long-term project maintenance - nvrs [2]: Fast new version checker for software releases - Maintainer A tool designed to help with package maintenance, features direct integration with multiple version control platforms (more about it below) - Linutil [3]: Distro-agnostic toolbox for Linux system management - Co-Maintainer Contributed core functionality and maintaining package dependencies - HyprUtils [4]: Unofficial Hyprland and Wayland-first tools - Co-Maintainer Focus on user experience and system integration - Jule [5]: Effective programming language for building efficient, fast, reliable and safe software while maintaining simplicity - Contributor, Projects Maintainer With a deep interest in both development and maintainership, I am eager to contribute further to the Arch Linux ecosystem. My starting goals include: - Assisting with the development/maintainership of various Arch Linux projects, such as alpm, arch-repro-status, or gluebuddy. - Improving automation of package maintainership by introducing nvrs [2] as an alternative to the already utilized nvchecker and enhancing the experience by applying improvements/QOL enhancements/bug fixes "on the fly". - Maintaining Rust, Zig, C, C++ and Go packages in the official repositories, as well as the AUR. - Transferring some useful AUR packages (linutil, nvrs, julec, ntfy) to the official repositories to improve their accessibility and maintenance. - Watching over the operation of the AUR, as I noticed that it can take some time for Deletion/Merge/Orphan Requests to be resolved. I'd like to speed up that process. I fully understand the responsibilities and commitment that come with being a Package Maintainer, and after (a long) careful consideration, I am confident that I can meet these challenges, regardless of their complexity. Relevant links: [1]: https://github.com/adamperkowski/highlightos [2]: https://github.com/adamperkowski/nvrs [3]: https://github.com/christitustech/linutil [4]: http://web.archive.org/web/20241130095841/https://github.com/hyprutils [5]: https://github.com/julelang [6]: https://aur.archlinux.org/packages?K=adamperkowski&SeB=m [7]: https://github.com/adamperkowski/pkgbuilds [8]: https://github.com/adamperkowski [9]: https://gitlab.archlinux.org/adamperkowski [10]: https://adamperkowski.dev I appreciate your consideration of my application and I am excited about the opportunity to contribute to the Arch Linux community's ongoing development. Sincerely, Adam Perkowski

1 1

Removal of Xyne as Package Maintainer due to inactivity
by gromit 14 Dec '24

14 Dec '24

Hi all, I'd like to start a ["Special Removal of an Inactive Package Maintainer"][0] for Xyne based on prolonged inactivity. Xyne has not executed any of the expected packaging or AUR maintenance duties for more than a year now. When I contacted all people who were inactive in votings for a longer period of time[1] (August '23) we heard back[2] from Xyne stating that he would still like to help out with Arch but does not have time/capacity due to personal circumstance right now, but is on track to getting back to things. This has not happened since and when I pinged the inactive maintainers recently ago I also did not hear back from him. - His last voting[3] was vote nr. 150 (ended 2023-12-03), since then 6 other votings were done. - His last packaging activity was in 2023-08-01[4] - He did not do any AUR Moderation for that timeframe (to my knowledge) Given these circumstances I'm requesting him to be removed as a Package Maintainer. If at some later point he has the time / resources to help out again I'm very much in favour of welcoming him back as they seemed to have made excellent contributions to the community. The discussion period for this proposal will last for three days, after which there will be a voting period of five days as outlined in the bylaws. Cheers, gromit [0]: https://package-maintainer-bylaws.aur.archlinux.org/#_special_removal_of_an… [1]: https://lists.archlinux.org/archives/list/arch-tu@lists.archlinux.org/threa… [2]: https://lists.archlinux.org/archives/list/arch-tu@lists.archlinux.org/messa… [3]: https://aur.archlinux.org/package-maintainer [4]: https://gitlab.archlinux.org/archlinux/packaging/state/-/commit/5a8dc54e49b…

1 2

Are packages for other architectures allowed in the AUR?
by Valentin Hăloiu 27 Nov '24

27 Nov '24

Hello, I have recently created an AUR package (uboot-cm3588-nas <https://aur.archlinux.org/cgit/aur.git/?h=uboot-cm3588-nas>) that's only usable on the "aarch64" architecture (e.g.: Arch Linux ARM) which got promptly removed due to: "not for Arch Linux, aarch64 only package". However, the AUR submission guidelines <https://wiki.archlinux.org/title/AUR_submission_guidelines> do not make it very clear whether non-x86_64 packages are allowed in the AUR or not. The closest reference that I could find in relation to this is the Arch package guidelines - Architectures <https://wiki.archlinux.org/title/Arch_package_guidelines#Architectures> section which mentions: > The arch array should contain 'x86_64' if the compiled package is architecture-specific. Otherwise, use 'any' for architecture independent packages. This makes it sound like only x86_64 packages are allowed but, to me, that still sounds like there is some room for interpretation. So, my main question is: *are packages for other architectures allowed in the AUR?* Also, in light of recent discussions around Arch Linux Ports <https://rfc.archlinux.page/0032-arch-linux-ports/>, I think it would be helpful to spell out the answer to this question explicitly in the AUR submission guidelines.

2 2

nvidia-390xx-utils kernel-6.12.patch provided - is there a way I can do pull-request?
by David C. Rankin 24 Nov '24

24 Nov '24

AUR folk, I've created the 6.12 patch for the nvidia-390xx-utils package and posted to the package page (as has been the practice for the past couple of years). Is there a way I can simply do a pull-request so it makes it easier to incorporate by vnctdj (the current maintainer)? That would save the manual edit, patch and checksum update to the PKGBUILD and I don't mind doing it. Let me know what the best way to make this process easier on the maintainer is. If I had an e-mail, I could just e-mail the updated and signed source package. -- David C. Rankin, J.D.,P.E.

1 0

Wrong email address for newly registered account
by schance995 17 Nov '24

17 Nov '24

I registered with username schance995 but typoed the email. Please let me know if the account's email could be corrected to this one.

2 1

User "Scimmia" is misusing "Report out-of-date" button for purposely spamming excessive off-topic messages
by Actionless Loveless 13 Nov '24

13 Nov '24

The field is designed for notifying the maintainer of the package when a new release is available, not for reporting any other sort of problems (for which there are other means of reporting). But aside of misusing the purpose of the field, there is also a clear intention for spamming as could be seen : https://imgur.com/a/54O3TTR

3 8

mongdb44 - updated - request comments on PKGBUILD
by David C. Rankin 02 Nov '24

02 Nov '24

Aur folks, I had a need to use mongodb44 and only mongo44-bin was available. mongodb44 was out of date and was orphaned. Not knowing what options the mongodb-bin package is built with and it having different user:group, I decided to update the mongodb44 package. I spent a good deal of time patching it for boost 1.86 and resolved a number of minor redundant std::move(), and like issues (I still have a few more to go, I missed a couple). However, the package now builds cleanly and you can follow along with what is being built instead of it being lost in a sea of warnings. Since there is no one-shot update, I adopted the package as maintainer and pushed the update to https://aur.archlinux.org/packages/mongodb44. The following patches are new: mongodb-4.4.29-boost-1.86.patch mongodb-4.4.29-fix-scons.patch mongodb-4.4.29-no-enterprise.patch mongodb-4.4.29-redudant-std-move.patch I'd appreciate thoughts on anything else I should fix in the PKGBUILD. I am also unclear whether I should list debugedit as a build dependency -- it being somewhat of a generic dependency to the makepkg process. Should it be included as well? (note: this is a BIG build and can take over an hour with link-time optimizations at -j4 or -j8, the source is about a 50M download from github) -- David C. Rankin, J.D.,P.E.

1 0

Is there a way to submit a one-shot update to an Aur package without becoming the maintainer?
by David C. Rankin 01 Nov '24

01 Nov '24

Aur Mods, I updated https://aur.archlinux.org/packages/mongodb44 to build with the last 4.4.29 source and patched for boost 1.86. The package builds fine now against current Arch. I wanted to pass on the results of those efforts and update the Aur package, but didn't want to take on the maintainer role from here on out. Is there a way to provide an update for the package and bring in back into date without becoming the maintainer? I still have to merge a few patches and roll a couple of sed substitutions from the PKGBUILD into a final boost 1.86 patch, but I'm happy to package and sign a package source and provide that to you for update. There was about 8 hours of effort to find and fix all the issue, I'd like to make that available to whoever may need the 4.4 version of mongodb. I didn't think I'd ever need it, but it is the last version that wasn't built requiring avx - so it is useful if you need it for those cases. Let me know. Also has my sentence to the moderated list been served? I'm still a bit bewildered about what prompted that and who signed off on it. Let me know there too. -- David C. Rankin, J.D.,P.E.

1 0

How to become a co-maintainer of a package
by Nikita Goncarenko 30 Sep '24

30 Sep '24

Hey, I would like to know how could I become a co-maintainer of a package (specifically `satdump`) Nikita

2 1