Arch Linux User Repository

Important note: Is recommended to receive the following key before to install:

$ gpg --recv-keys B94556F81C85D0D5

Also is possible skip the verification, adding the flag for (e.g makepkg, yay) --skippgpcheck, --nopgpfetch, respectively.

@AllesMeins, are you still experiencing crashes? Indeed, since a while, now my Seafile mount crashes when trying to access the "lost+found" dir:

$ ls <your-mount>/lost+found ls: cannot access 'dir-lost+found-SKTcFr': Software caused connection abort ls: cannot access 'dir-lost+found-JJZzpr': Transport endpoint is not connected ....

-------------------->8-------------------------- [Feb15 10:41] mount.davfs[5816]: segfault at 0 ip 00007fbfeb6cb76c sp 00007ffe5779fee0 error 4 in libneon.so.27.5.5[7fbfeb6c7000+16000] [ +0.000031] Code: 1e fa 41 57 41 56 41 55 41 54 55 89 f5 83 e5 01 53 48 89 fb f7 dd 66 81 e5 83 73 89 e8 48 83 ec 08 80 cc 40 83 e6 02 0f 45 e8 <0f> b6 07 84 c0 0f 84 d1 00 00 00 48 89 fa 45 31 e4 4c 8d 2d 7c 3b -------------------->8--------------------------

Otherwise, the FS can be remounted after removing the PID file

"/var/run/mount.davfs/<whatever>.pid"

This package has no problem compiling on ARM. Please add the 'armv7h' and 'aarch64' architectures to 'arch'.

Since the last update davfs keeps segfaulting for me - has anybody experienced similar issues? It was running stable for the last year or so now I've noticed that the mount keeps getting lost (transport endpoint not connected). dmesg shows a:

"[22463.946668] mount.davfs[28726]: segfault at 0 ip 00007f70d9b1176c sp 00007fffda724100 error 4 in libneon.so.27.5.4[7f70d9b0d000+16000] [22463.946687] Code: 1e fa 41 57 41 56 41 55 41 54 55 89 f5 83 e5 01 53 48 89 fb f7 dd 66 81 e5 83 73 89 e8 48 83 ec 08 80 cc 40 83 e6 02 0f 45 e8 <0f> b6 07 84 c0 0f 84 d1 00 00 00 48 89 fa 45 31 e4 4c 8d 2d fc 3b [22463.946756] audit: type=1701 audit(1668002619.496:2042): auid=1000 uid=1000 gid=90 ses=3 subj=unconfined pid=28726 comm="mount.davfs" exe="/usr/bin/mount.davfs" sig=11 res=1"

I can unmount the folder and mount it again and it will work for a few seconds until it crashes again.

I really don't know. Tried again today and it compiled without problems on all systems. I could probably check if I had pkgrel -1 and not -2 of neon and if it was an issue with the openssl transition. Far stretched, as the version check still should have succeeded... Or it was another dep which had funny ideas.
As of now, issue is gone and sorry for the noise :)

Hi @TrialnError, I did not find such error. What could be happening?

I somehow get this following error when I try to compile 1.7.0:

checking for neon-config... /usr/bin/neon-config
checking linking against neon... no
configure: incompatible neon library version 0.32.4: wanted 0.27 28 29 30 31 32
configure: error: could not find neon

Important note: Is recommended to receive the following key before to install:

$ gpg --recv-keys B94556F81C85D0D5

Also is possible skip the verification, adding the flag for (e.g makepkg, yay) --skippgpcheck, --nopgpfetch, respectively.

PGP fails to retrieve keys through AUR helper (yay) install - can be manually retrieved from https://savannah.nongnu.org/project/release-gpgkeys.php?group=davfs2 if necessary.