June 2024 - Aur-general - lists.archlinux.org

1 week break bittin
by Luna Jernberg 20 Jun '24

20 Jun '24

Hey! i will be in Germany helping out at the openSUSE Conference 25th of June to 2th July and won't have time to update my AUR packages during that period, a couple of them have comaintainers however

1 0

User jiangyc reuploads
by Fabio Loli 18 Jun '24

18 Jun '24

Hi, user jiangyc continue to re-upload 1panel-stable-bin; a duplicate of 1panel-bin 1panel-bin is orphan while their pkgbuild use curl in pkgver() and build() to get version and download, they have been informed on the first upload to not do that, I get there may be a language barrier but didn't get a reply and behaviour continued Third deletion request will come soon Please take appropriate action

1 0

Please take actions against a problematic user
by Kimiblock Moe 17 Jun '24

17 Jun '24

Hi all, I'm Kimiblock, requesting AUR moderators to take action against packager 7Ji and 2 packages: wechat-universal-bwrap and wechat-beta-bwrap. Despite the fact that we already discussed[a][b]: wechat-universal-bwrap and wechat-beta-bwrap is now duplicated packages of the original wechat-uos-bwrap (which has been renamed to wechat-uos-qt to avoid confusion[c]), user 7Ji still filed a deletion request against wechat-uos-bwrap[d]. He filed the deletion request because "don't want unrelated comments in the history of -universal, neither its votes". Ironically, he admitted that wechat-beta-bwrap is based on wechat-uos-bwrap and another package wechat-uos-qt is based on -beta-bwrap. He then said he "would want no history from -uos-bwrap". This is a serious violation of AUR submission guidelines[e]: "*Check the AUR* if the package *already exists*. If it is currently maintained, changes can be submitted in a comment for the maintainer's attention." and this is not the end of this user's problematic behaviour. In the merge request of wechat-beta-bwrap filed by me, he said: "Additionally, as of writing, `wechat-beta-bwrap` has 21 votes, and `wechat-uos-bwrap`has 11 votes, it is not right to merge from a highly voted one a lowly voted one". This can't be right: if someone can mislead AUR users and let them vote the duplicated package, then the original package should be merged into the duplicated one? I can't understand the rationale behind this. All in all, please take actions against this user and 2 duplicated packages: wechat-universal-bwrap and wechat-beta-bwrap. -- Sincerely, Kimiblock [a]: https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/t… [b]: https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/m… [c]: https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/m… [d]: https://lists.archlinux.org/archives/list/aur-requests@lists.archlinux.org/… [e]: https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submiss…

1 0

About the intentionally duplicated package wechat-beta-bwrap and wechat-universal and unmaintained orginal package wechat-uos
by Kimiblock Moe 14 Jun '24

14 Jun '24

Hello people, I'm Kimiblock, the maintainer of wechat-uos-bwrap, writing to request Package Maintainer's action to solve the intentionally duplicated package on AUR. WeChat is a closed-source software developed by Tencent which is used by almost all people in China. In March 5, people in #archlinux-cn discovered that there is a testing version available and shortly after, it became a installable package for China's UOS. I've packaged wechat-uos-bwrap in 2024-03-05 23:37 (CST). 2 days after in 2024-03-07 09:18 (CST), AUR account leaeasy submitted wechat-beta-bwrap. If you look at the initial commit <https://aur.archlinux.org/cgit/aur.git/commit/?h=wechat-beta-bwrap&id=76c45…> of wechat-beta-bwrap, it was almost completely copied from wechat-uos-bwrap (other than a different way to extract the .deb), even the .desktop file. The only major thing they changed is wechat.sh, which sanbox function is removed. But wechat-uos-bwrap can read a environment variable "trashAppUnsafe=1" and disable its sandbox function. So I filed a merge request (#PRQ57379) to merge wechat-beta-bwrap <https://aur.archlinux.org/pkgbase/wechat-beta-bwrap/> into wechat-uos-bwrap <https://aur.archlinux.org/pkgbase/wechat-uos-bwrap/>. After that, one of the wechat-beta-bwrap <https://aur.archlinux.org/pkgbase/wechat-beta-bwrap/> maintainer 7Ji <https://aur.archlinux.org/account/7Ji> submitted a new package called wechat-universal-bwrap <https://aur.archlinux.org/pkgbase/wechat-universal-bwrap>, which is also a duplicate package of wechat-uos-bwrap. So, I'm thinking to merge all that duplicate packages and my wechat-uos-bwrap <https://aur.archlinux.org/pkgbase/wechat-uos-bwrap/> into wechat-uos. Sadly, the original Maintainer DuckSoft disappeared (the last message he sent in #archlinux-cn is over 3 years ago). Therefore, I'm requesting Package Maintainers to merge wechat-beta-bwrap <https://aur.archlinux.org/pkgbase/wechat-beta-bwrap/> and wechat-universal-bwrap <https://aur.archlinux.org/pkgbase/wechat-universal-bwrap> and give Maintainer role to previous wechat-uos maintainer, sukanka <https://aur.archlinux.org/account/sukanka> so that this package can be updated. I'll merge wechat-uos-bwrap <https://aur.archlinux.org/pkgbase/wechat-uos-bwrap/> into wechat-uos once sukanka finish updating this package and add the sandbox function. I've contacted sukanka via Matrix and he/she is willing to maintain this package. -- Sincerely, Kimiblock

7 17

Package Maintainer application - Giovanni Harting
by Giovanni Harting 12 Jun '24

12 Jun '24

Hey everyone. I'm hereby applying as a package maintainer, which is kindly sponsored by David (dvzrv) and Jelle (jelly) and formally by Levente (anthraxx), for whom Jelle has taken over the sponsorship. ## Who I'm Giovanni, also known as anonfunc or idlegandalf. I've been using Arch Linux as my day-to-day driver since 2013 and Linux in general since probably 2008 (mostly server-side until 2011-12, last Windows I actually used was 7). As for notable contributions, you might have heard of ALHP, which I started in 2020. ALHP developed from the idea of utilising modern CPU extensions all the way back in Q4 2019 (after I had a quick Gentoo detour on one of my laptops). At the time, no x86_64 levels were defined, so the first rough outlines still considered building for specific gcc CPU-baselines, like Haswell for example (which seems crazy in hindsight). When the x86_64 levels were announced in 2020, I started developing a buildbot capable of doing the heavy lifting, at the time in Python. After ditching Python in 2021 (after I got annoyed of multi-process) and rewriting the buildbot in Go, the project launched in July 2021. At the time, ALHP only provided x86_64-v3, shortly after launch x86_64-v2 followed. In December 2023 the x86_64-v4 repo launched, after I got my hands on a machine capable of building v4. Not sure how many users it actually has, since I do not do any tracking, but as far as requests on the tier 0 mirror go (ALHP has 7 mirrors in total, one operated by myself), it seems to see some usage. The buildbot is completely FOSS, you can have a look down in the links section. Outside of my Arch Linux involvement I work as a DevOps engineer. I can also support Arch Linux there if needed. ## Goals & Packages I want to help with package maintenance and advance infrastructure topics with the overall goal of bringing x86_64-v3 and build automation to life, as well as helping with potential problems that may come with v3, since ALHP had plenty of those already. As for packages, I have a few that I think would benefit the general Arch Linux audience by being promoted to official packages, mostly QoL stuff: - batsignal - wljoywake - jellyfin-mpv-shim (+ deps) - prismlauncher - victoriametrics - asus-numpad - mmdbinspect I'm also open to co-maintainer roles if there are any packages in need. Candidates could include DevOps related packages like Grafana or packages from the Go ecosystem in general, since I use that language extensively. Besides the mentioned categories, I'm also interested to co-maintain: - home-assistant - jellyfin ## Links AUR packages: https://aur.archlinux.org/packages?SeB=m&K=anonfunc AUR source repo: https://somegit.dev/anonfunc/aur-packages ALHP: https://somegit.dev/ALHP/ALHP.GO ALHP Status: https://status.alhp.dev/ Feel free to criticise PKGBUILDs to your heart's content :) Improvement is a continuous thing, so keep them coming. Giovanni

6 10

User tallero comments
by james smith 02 Jun '24

02 Jun '24

A request for the pkgbuild to be updated[1] [2] quickly degenerated in insults [1]https://aur.archlinux.org/packages/duckstation#comment-960352 [2]https://aur.archlinux.org/packages/duckstation#comment-960355 Please take appropriate action

3 2