- Arch-general - lists.archlinux.org

Split apache package
by Polarian 05 Feb '23

05 Feb '23

Hello, I would like to make a suggestion for the apache package, I was not too sure which mailing list to put this in, so I picked the general mailing list for the avoidance of doubt :P So the apache package: https://archlinux.org/packages/extra/x86_64/apache/ Currently contains tools which are used by nginx users, and the issue is that is that you can only run one webserver as once, they both are going to try to bind to port 80 and 443 so you got to choose. htpaswd utility is used by nginx users too, and the issue is they have to install the entire apache web server in order to be able to use the single utility. I suggest splitting the package into apache-utils and apache, or, if the maintainer(s) are willing to maintain it, split the utilities into their own separate pacakge and use apache-utils as a group of all the subpackages (htpasswd, htdigest etc). I feel this would be a good change so that nginx users do not need to install the entire apache web server just to use the apache utilities which nginx suggests to use within their documentation (see https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http…) As you can see in the guide, Debian, Ubuntu, RHEL, CentOS and Oracle Linux already have seen this issue within their own repositories and split the packages up, why can't arch linux? Thanks for reading this suggestion, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

19 60

Detected unsafe path transition when creating chroot
by Polarian 04 Feb '23

04 Feb '23

Hello, So recently I wrongly diagnosed a package as being broken based on this issue until I realised it was my chroot. Due to the doas issue I have with dev tools, I use a manual chroot using the following steps, I will use (# to denote root and $ to denote unpriviliged) 1. Make the directory $ mkdir chroot I made this in the home directory of my user, polarian 2. Install the base system # pacstrap chroot base base-devel This will install the base system and also the base-devel tools used for building packages. but when doing this recently I have been getting the following issues: Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/lib. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/lib/dbus. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/dbus. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /etc (owned by root) during canonicalization of /etc. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/lock. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/lib. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/sudo. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/systemd/netif. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/systemd/netif. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/systemd/netif. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/lib. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/lib. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/lib/systemd. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/systemd. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/lib/systemd. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/lib. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/log. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/cache. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/lib/tpm2-tss/system. Detected unsafe path transition / (owned by 1000) → /run (owned by root) during canonicalization of /run/tpm2-tss. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/log. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/log. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/log. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/log/journal. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/log/journal. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/log/journal. Detected unsafe path transition / (owned by 1000) → /var (owned by root) during canonicalization of /var/log/journal/remote. Detected unsafe path transition / (owned by 1000) → /dev (owned by root) during canonicalization of /dev/snd/seq. Detected unsafe path transition / (owned by 1000) → /dev (owned by root) during canonicalization of /dev/snd/timer. Detected unsafe path transition / (owned by 1000) → /dev (owned by root) during canonicalization of /dev/loop-control. Detected unsafe path transition / (owned by 1000) → /dev (owned by root) during canonicalization of /dev/net/tun. Detected unsafe path transition / (owned by 1000) → /dev (owned by root) during canonicalization of /dev/fuse. Detected unsafe path transition / (owned by 1000) → /dev (owned by root) during canonicalization of /dev/kvm. Detected unsafe path transition / (owned by 1000) → /dev (owned by root) during canonicalization of /dev/vhost-net. Detected unsafe path transition / (owned by 1000) → /dev (owned by root) during canonicalization of /dev/vhost-vsock. During the pacstrap install... this happens when installing built packages inside my chroot, which resulted in me going mental yesterday and breaking a package... badly... (I should have taken a break). Anyways does any have any ideas on how to fix this? Thank you, Polarian -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

2 2

glibc 2.37 release
by Frederik Schwan 04 Feb '23

04 Feb '23

Glibc 2.37 is about to be released to [testing]. Please be aware that any package that links against the 2.37 libc has to stay in testing for as long as glibc stays there. Otherwise breakage will be imminent. Best regards, Frederik

1 0

TU contact emails?
by Polarian 04 Feb '23

04 Feb '23

Hello, So I have noticed every TU gets given their own @archlinux.org email address, but I am unsure what are the conventions when it comes to contacting TU members. Some TUs still use their personal emails a lot (especially within the mailing lists), so how am I meant to know which email to email, either the @archlinux.org email or their personal email when it comes to contacting them about arch-related issues? Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

3 2

Why does new php conflict with older php-intl packages? Workaround?
by David C. Rankin 03 Feb '23

03 Feb '23

All, I have a requirement for an older version of php for a groupware package that isn't yet updated. The last system update to php8.2 created a new conflict with php-intl. Why? and how best to work around the new conflict? -- David C. Rankin, J.D.,P.E.

2 1

State of Netbeans package
by Jens Pelzetter 01 Feb '23

01 Feb '23

Hello everyone, I'm using NetBeans as IDE for Java development. In the past, the NetBeans package in Arch Linux was updated soon after the NetBeans project published a new release. But now the NetBeans package is flagged as out-of-date since September. But there are no bugs in the bug tracker that show that there are technical issues which prevent an update. Is there of lack of resources on the side of the maintainer, or what is the reason that the package hasn't been updated yet? Because if the package will not be updated in the near future, I may either switch to the AUR package, or to download NetBeans directly from Apache. Unfortunately, I don't have any experience yet with creating packages for Arch Linux. If I had already some experience with building packages for Arch Linux, I may would be interested in supporting the maintainers of the NetBeans package, or even taking over the maintainer role for the package if the package is looking for a new maintainer. But I'm also not sure if I have the time resources for maintaining such a package. Best, Jens

3 3

Network Bridge - Do not pass back to router
by Polarian 31 Jan '23

31 Jan '23

Hello, So my current setup on my server is a network bridge (br0) with a physical interface as a slave to the bridge. I deploy lxc containers using the bridge, it is not a NAT bridge, and thus DHCP is used to lease an address from the physical router in which the server is connected to. My issue is, each LXC container can communicate with one another over the bridge, this means as I have an Arch mirror in a container, I can pull packages close to the SATA limit (just under 6gbps). However when the host wants to pull from the Arch mirror, it passes back to the router and then back to the server then to the bridge to the LXC container. I am not very experienced with virtual interfaces, but I would like the server to stop wasting router resources passing packets back to the router just to be passed back into itself. Any advice would be useful. Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

4 9

Meshroom: Strange rendering problem in save dialog
by Peter Nabbefeld 30 Jan '23

30 Jan '23

Hello, when I want to save sth. in meshroom, there's a strange rendering problem: I can see changes only after switching to another workspace and back again, effectively causing re-rendering of the screen. As I don't have this behaviour with other file dialogs, I'd guess there's some problem with meshroom or one of the Python libraries? Kind regards, Peter

1 0

Starting meshroom
by Peter Nabbefeld 30 Jan '23

30 Jan '23

Hello, after installing community/meshroom, I'm looking for how to start it. Following https://meshroom-manual.readthedocs.io/en/latest/first-steps/install/index.… I looked for some Meshroom command, but couldn't find it. What am I doing wrong? Kind regards, Peter

3 4

Unofficial arch ports within the ArchWiki?
by Polarian 30 Jan '23

30 Jan '23

Hello, I was looking at Arch Linux Arm's (ALARM) website and I realised, a lot of their support just points right back to the ArchWiki. I thought the ArchWiki was only designed for the official distribution (Arch Linux) and not any other ports for other architectures? Thank you, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

2 1