May 2019 - Aur-general - lists.archlinux.org

[aur-general] mesa-git / lib32-mesa-git need new maintainer
by Lone_Wolf 09 May '19

09 May '19

Hi, Due to irreconcilable differences wrt mesa trunk packaging, I am stepping down as the maintainer of those packages. I hope someone will volunteer to take over these packages and there will be a smooth transition. The packages will keep depending on llvm trunk until I transfer maintainership. If no new maintainer comes forward, I will orphan these packages no later than june 3 2019. Since TUs have made very clear there's no room in AUR for mesa trunk packages that match my views, I will take my versions elsewhere . I have not yet decided whether I will keep maintaining my other aur packages. Lone_Wolf

1 1

[aur-general] Spammy post on cntlm's AUR page
by Oon-Ee Ng 08 May '19

08 May '19

Latest post, the only one by this account - https://aur.archlinux.org/account/RonaldSteele - post unrelated to other comments on cntlm and links to dodgy blog. Account just registered today. Surprised there's only one post so far.

2 2

[aur-general] Kernel version requirement
by Julien Nicoulaud 08 May '19

08 May '19

Hi, In the oomd package <https://aur.archlinux.org/packages/oomd/>, I put a linux>=4.20 dependency requirement since it requires the new resource pressure metrics <https://facebookmicrosites.github.io/psi/> introduced in linux 4.20. But as another user pointed out, some of the alternatives kernel packages declare provides=("linux=${pkgver}"), but several of the most popular do not (linux-lts, linux-dzen, linux-hardened). What we would be correct way to handle this ? Should I just drop the version requirement (since having a kernel>=4.20 does not imply you are running this one anyway) ? Or should these packages be improved ?

5 5

[aur-general] Are AUR VCS packages that depend on AUR VCS packages from other projects a good idea and who should decide on that ?
by Lone_Wolf 07 May '19

07 May '19

Hi, recently a mesa developer contacted me and asked me to change mesa-git to depend on released llvm/clang instead of llvm/clang trunk. He did convince me there's a demand for such a package. Currently people wanting to build mesa-git against released versions need to edit the pkgbuild and make a few changes (not documented atm). I have been building mesa trunk against llvm trunk since mesa started using llvm and tailored the package to my personal workflow and style. Adjusting the mesa-git PKGBUILD to use repo llvm/clang would force me to either change my workflow or maintain a package I don't use in that form. I'd probably stop maintaining mesa-git. I do feel there's an underlying issue here that concerns us all as stated in the title: Are AUR VCS packages that depend on AUR VCS packages from other projects a good idea and who should decide on that? Lone_Wolf

9 39