- Aur-general - lists.archlinux.org

Can't seem to find the issue within PKGBUILD
by Polarian 03 Feb '23

03 Feb '23

Hello, https://onedev.polarian.dev/polarrepo/reposilite/~files/fix Find above the link to the git repository, please check branch fix and not master. A lot of these edits were not made by me and were made by another user, but I can't seem to find what is causing the following issue when trying to install this package: (3/4) Creating temporary files... Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/lib. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/lib/dbus. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/dbus. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/lock. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/lib. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/lib. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/sudo. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/systemd/netif. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/systemd/netif. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/systemd/netif. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/lib. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/lib. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/lib/systemd. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/lib/systemd. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/lib. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/log. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/cache. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/lib/tpm2-tss/system. Detected unsafe path transition / (owned by build) → /run (owned by root) during canonicalization of /run/tpm2-tss. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/log. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/log. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/log. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/log/journal. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/log/journal. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/log/journal. Detected unsafe path transition / (owned by build) → /var (owned by root) during canonicalization of /var/log/journal/remote. Detected unsafe path transition / (owned by build) → /dev (owned by root) during canonicalization of /dev/snd/seq. Detected unsafe path transition / (owned by build) → /dev (owned by root) during canonicalization of /dev/snd/timer. Detected unsafe path transition / (owned by build) → /dev (owned by root) during canonicalization of /dev/loop-control. Detected unsafe path transition / (owned by build) → /dev (owned by root) during canonicalization of /dev/net/tun. Detected unsafe path transition / (owned by build) → /dev (owned by root) during canonicalization of /dev/fuse. Detected unsafe path transition / (owned by build) → /dev (owned by root) during canonicalization of /dev/kvm. Detected unsafe path transition / (owned by build) → /dev (owned by root) during canonicalization of /dev/vhost-net. Detected unsafe path transition / (owned by build) → /dev (owned by root) during canonicalization of /dev/vhost-vsock. error: command failed to execute correctly (4/4) Arming ConditionNeedsUpdate... Some advice would be appreciated! Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

2 1

Multiple packages in PKGBUILD and creating groups?
by Polarian 31 Jan '23

31 Jan '23

Hello, I have two questions, I merged it into one post to prevent people complaining about Polarian Notifications (aka me popping up on their email every 5 mins). Does anyone have a good reference I can use to properly make a multi-package PKGBUILD, I have no experience doing this and I want to stick to conventions, and the PKGBUILD ArchWiki page does not seem to cover it. Secondly, is it possible to create PKG groups within the AUR, I would like to group a few packages together, but I am unsure if I am allowed, or able to do this, unless it is added to an official repository. Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

3 5

Removal of Kyle Keen (keenerd) as Trusted User/ Package Maintainer
by David Runge 29 Jan '23

29 Jan '23

Hi all, I would like to bring up the removal of Kyle Keen (keenerd) [1] as Trusted User/ Package Maintainer on the basis of inactivity [2]. As main key holder I have been trying to get Kyle's previous packager key revoked (no @archlinux.org UID, RSA2048, SHA-1 binding signature) and have a new one be created since October 2021. Jelle also tried to reach out to get a response via arch-dev-public in May 2022 [3]. There had been no reply to my requests, until I had DevOps disable SSH access to the package server in July of last year (which I had to do as packages were still being released and I had to rebuild them constantly [4][5] for us to be able to disable one of the main packager keys). After some time an @archlinux.org mail address had been requested and a ticket been created for archlinux-keyring [6]. However, since October 2022 this process is dormant again (after pinging about missing bits). Other issues were raised around the splitting of the python-jaraco packages [7], which stalled updates to a bunch of the building blocks of the Python ecosystem due to no response from Kyle. After spending 16 months on a key change and multiple times of failing to follow up, I am of the opinion, that Kyle is not able to keep up with packaging and the process that is required for it (e.g. communication with other packagers or key holders). The discussion period on this topic lasts for three days (starting today), after which there will be a voting period of five days. Best, David [1] https://aur.archlinux.org/packages?K=keenerd&SeB=m [2] https://tu-bylaws.aur.archlinux.org/#_special_removal_of_an_inactive_tu [3] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.o… [4] https://archlinux.org/todo/rebuild-packages-signed-by-48c3b1f30ddd0fe67e516… [5] https://archlinux.org/todo/rebuild-packages-signed-by-48c3b1f30ddd0fe67e516… [6] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/201 [7] https://archlinux.org/packages/?q=python-jaraco -- https://sleepmap.de

2 5

Onedev-docs - check
by Polarian 29 Jan '23

29 Jan '23

Hello again, Could you please check a new package I have been working on to allow for onedev documentation to be viewed offline. You can view the PKGBUILD on the aur, or using the link below: https://onedev.polarian.dev/aur/onedev-docs/~files/master/PKGBUILD Before anyone comments why I have fetched the source within the prepare function, which is non-conventional, git-lfs does not support makepkg as it can not fetch from local filesystem, which is how MAKEPKG syncs the cloned repository (bare) to the repository within the src directory, thus I have had to manually clone the package with git-lfs installed, this will properly fetch the git-lfs files. Also for those who are wondering why you cant view the html directory, read the edit I have made to the onedev page here: https://wiki.archlinux.org/title/Onedev Thank you, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

1 0

Eureka-notes AUR package - check
by Polarian 25 Jan '23

25 Jan '23

Hello, Could anyone who has experience with AUR packages please check over the PKGBUILD I have submitted to the AUR. It works, and I have already written up the ArchWiki page for it (https://wiki.archlinux.org/title/Eureka) but I want a second set of eyes to read through my work to ensure I have not screwed anything up, and to ensure my package is sticking to conventions (and in case anyone has any improvements). You can either read it from the git interface provided by the AUR (this can be a little annoying) or you can read it on the git repository which is hosted elsewhere here: https://onedev.polarian.dev/aur/eureka-notes/~files/master/PKGBUILD Any issues with the package let me know :) Thank you, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

4 16

Building in clean chroot dilemma
by Polarian 25 Jan '23

25 Jan '23

Hello, So I currently do not test my packages in a clean chroot because of this issue: https://gitlab.archlinux.org/archlinux/devtools/-/issues/105 It seems a little stupid but I hate sudo being installed on my system, I do not like it, and I do not like when tools force me to use sudo. Without sudo installed the makechrootpkg script breaks and thus I can't use dev tools to test in a chroot environment. I did try and just manually build a chroot environment, but for whatever reason it was not writable to disk, in other words I kept getting "filesystem full" errors when the filesystem was not full, and I couldn't see to find a decent guide on how to actually setup a chroot manually, all recommend using different parts of the devtools. I have posted this for 2 reasons: 1. I want to know if anyone else agrees that doas support should be added to the devtool scripts. 2. I am looking for temporary alternatives from using devtools to build AUR packages in a clean environment. I have in the case of the movim package built it in an lxc container, which are similar to chroots, but the issue is the base arch linux container image contains a few dependencies which could mean I miss out some of the dependencies. And also every time I want to deploy a package to the container I have to copy it over to my production server which is not ideal. If anyone has any solutions please let me know :) Thank you, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

7 16

TU Application - Antiz
by Robin Candau 25 Jan '23

25 Jan '23

Hello, My name's Robin Candau and I'd like to apply to become a Trusted User. My sponsors are Leonidas Spyropoulos <artafinde> and T.J. Townsend <blakkheim>. I'm 26 years old and I live in France. I'm working as a Linux system, Infrastructure and DevOps engineer. I've been using Linux for the last decade and been using Arch for a few years now. During my Arch journey, I started contributing to it in various ways: - I subscribed to every "major" mailing lists and reply to users' questions in it from time to time (mostly in the AUR-General one). - I'm answering questions on the Arch subreddit (even though I'm aware it is not an official Arch resource) and on the IRC channels from time to time. I'm a bit less present on IRC though, but I'm still passing by here and there. - I contribute to some wiki pages. - I maintain some packages on the AUR. - I'm reviewing PKGBUILDs (both on aurweb and the AUR-General mailing list). - I'm a member of the "Arch Testing Team" and I'm regularly testing and signing off packages. - I made rare contributions to the Arch DevOps Gitlab's issues (this is something I'd like to do more in the future, I just haven't take the time yet). Since I started contributing to Arch, my interest for it kept growing and I'd like to do more. This is why I'm applying to become a TU through this mail. For the minimum requirements: - I'm fine with shell scripting. - I maintain a few packages in the AUR with what I think are high-quality/clean PKGBUILDs [1]. - I'm doing basic community involvement (as stated earlier). - I can Google. - Aside from Arch, I've been involved in a few open-source projects: - My own open-source projects are hosted on GitHub [2]. - I'm a package and infrastructure maintainer for Crystal-Linux [3] which is an Arch based distribution that promotes the use of current and modern technologies and that brings an alternative to some widely used software through its own tools such as "jade" (the Crystal Linux's installer) or "amethyst" (the Crystal Linux's pacman wrapper and AUR helper). I'm basically maintaining the Crystal's specific PKGBUILDs [4] and helping them with infrastructure stuff. - More recently, I've been working with Rudra Saraswat (the Ubuntu Unity project lead) to help him properly packaging the Unity desktop environment for Arch (this is still a WIP) [5]. As a TU, I'm looking forward to help with the AUR moderation (reviewing PKGBUILDs, answering AUR related questions and handling AUR requests). I'd also be interested in moving the following AUR packages to Community: - protonmail-bridge - distrobox - unrar-free (which I currently maintain) - ddgr (which I currently maintain) Finally, those are the packages I use and/or I'd be interested in (co-)maintaining in Community: - glow - flameshot - xautolock - numlockx - playerctl - autorandr - hq - hexchat - pacman-contrib - zathura* (zathura, zathura-cb, zathura-djvu, zathura-pdf-mupdf, zathura-pdf-poppler, zathura-ps) - tmux - icewm - firewalld - picom - notification-daemon - blueman - redshift - xautolock - gsimplecal - tint2 - feh Globally, my package interests are CLI tools and GTK apps, but I can maintain anything else if needed. My primary goal is to help/contribute :) Also, even though it has no direct link with the TU position, I'm willing to take the time to bring some help and contributions to the DevOps side of things in the future, as stated in the beginning of my application. I'm looking forward to contribute more to Arch Linux. Thanks for reading my application! [1] https://aur.archlinux.org/packages?O=0&SeB=M&K=Antiz&outdated=&SB=p&SO=d&PP… [2] https://github.com/Antiz96 [3] https://getcryst.al/site [4] https://git.getcryst.al/crystal/pkgbuilds [5] https://gitlab.com/users/Antiz96/activity Regards, Robin Candau - Antiz

8 20

GPG signature renewal vs new key
by Polarian 25 Jan '23

25 Jan '23

Hello, When looking at the archlinux gpg keyring, I notice that when GPG keys expire, TU's regenerate a new key instead of renewing it. Why do they regenerate a new key instead of renewing, is it the same reason we put expire dates on our TLS certificates (for security). Is it bad to just renew your key without regenerating it? Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

2 2

Package updating database schema
by Polarian 16 Jan '23

16 Jan '23

Hello AUR community, I have a very annoying issue which I have not been able to find a solution to. So conventionally Arch Linux packages which require migration and updating of database schemas tend to have the following pattern: - Stop service - Update the package - Run some script which migrates the database manually - Start service However I have been packaging https://code.onedev.io/onedev/server with Bengcooper for the AUR and we have hit into a major issue. The upgrade guide, as defined in their wiki page (https://docs.onedev.io/upgrade-guide) requires the old code and the new code. This is due to the use of JSW (a proprietary wrapper) which they ship their binaries with. This does not comply with how you traditionally package software, and thus I have no clue how I am meant to integrate this into the AUR. I have in my own time been working on packaging the raw java code without JSW (cause f*ck the proprietary wrapper), however this is taking longer than I thought it would and I really need an AUR package to make things easier for me running my public OneDev instance over at https://onedev.polarian.dev Does anyone have any ideas of how I can at least get the package semi-working with database migrations, even if it is unconventional and annoying to do so? Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

6 13

Re: Package updating database schema
by Polarian 13 Jan '23

13 Jan '23

Hello, I have used the pre_upgrade hook, but the issue is I need access to the pkg contents, and I do not think that is possible using the pre_upgrade hook, I need it to execute the update.sh script which is within the package on the /opt/onedev directory when before upgrading. Basically, onedevs update script will migrate everything itself and also back it up. When installing onedev for the first time, there is no problems it will go smoothly, its when it needs to execute the update script on the directory (then preferably) discard of the upgrade files because onedevs update script also replaces all the code with the new code. It is highly annoying as it is semi-packaged by onedev, I dont mind if pacman comes along and just overwrites stuff, but I need to use the update.sh script from within the package from within the pre_upgrade hook. Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

1 0