Arch Linux User Repository

The only way to cause rebuilds is to watch when libxml2 gets an update, then manually bump the AUR package's pkgrel every time (and maybe add a versioned dependency on libxml2>=2.14 to ensure users will upgrade the new libxml before doing any rebuilds – but specifically >=, not =).

e.g. I do the pkgrel bump for some of my own packages (although without the versioned dep) because I'm adding them to an internal pacman repo which makes it necessary to increment pkgrel for each new build anyway.

If anyone is having issues with libxml2 references, this isn't a problem with autofs, this means that you need to rebuild autofs after the libxml2 update. There isn't a way to cause those rebuilds automatically, that I am aware of.

@jackycxh I don't have any problems on my machine with "libxml2 2.14.3-1", but I had to rebuild after the 2.14 update, like @nicknight commented here directly below your comment.

Error after libxml2 updated recently: automount: error while loading shared libraries: libxml2.so.2: cannot open shared object file: No such file or directory.

Workaround: manual install "libxml2-legacy"

the dependencies need to be updated from libxml2 to libxml2-legacy

FYI

With the update libxml2 2.13.8-1 -> 2.14.2-2 autofs stop to work automount: error while loading shared libraries: libxml2.so.2: cannot open shared object file: No such file or directory

One has to rebuild autofs

Cheers

That is because ls auto* will list the contens of /etc/autofs/ in the directory there is a file autofs.conf but not in /etc

After installing autofs using makepkg -si I experienced the very, very weird situation when trying to edit the conf files that they didn't exists! In my many years with Linux I've never seen anything like this. When listing the files in /etc with wildcard auto* they appear to exist, and even have a size, but when trying to list the files individually, the shell claims they don't exist.

I'm not sure if this is caused by the way makepkg -si installs files that are supposed to be owned by root or if my btrfs filesystem is simply corrupted.

[root@archbox etc]# ls -lb auto*
total 36
-rw-r--r-- 1 root root 16216 Mar 21 14:58 autofs.conf
-rw------- 1 root root   232 Mar 21 14:58 autofs_ldap_auth.conf
-rw-r--r-- 1 root root  1317 Mar 21 14:58 auto.master
drwxr-xr-x 1 root root     0 Mar 21 14:58 auto.master.d
-rw-r--r-- 1 root root   519 Mar 21 14:58 auto.misc
-rwxr-xr-x 1 root root   897 Mar 21 14:58 auto.net
-rwxr-xr-x 1 root root  2083 Mar 21 14:58 auto.smb
[root@archbox etc]# ls -lb autofs.conf
ls: cannot access 'autofs.conf': No such file or directory

If I try using auto dot wildcard I get the same:

[root@archbox etc]# ls auto.*
ls: cannot access 'auto.*': No such file or directory

When it asks Packages to cleanBuild?, choose [A]ll instead of the default ([N]one).

How do I delete the old source files? I am using yay