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.

neon's update to v0.33 seems to be a problem

configure: incompatible neon library version 0.33.0: wanted 0.27 28 29 30 31 32
configure: error: could not find neon

I got the package installed using pikaur. Installation using Manjaro's pamac or makepkgkeeps failing.

Hi @carlosal1015, thanks for your help.

The output of

gpg -v --recv-keys B94556F81C85D0D5

is

gpg: enabled compatibility flags:
gpg: data source: https://185.125.188.27:443
gpg: armor header: Comment: Hostname:
gpg: armor header: Version: Hockeypuck 2.1.1-10-gec3b0e7
gpg: key B94556F81C85D0D5: number of dropped non-self-signatures: 7
gpg: pub  rsa4096/B94556F81C85D0D5 2020-03-02  Ali Abdallah <aabdallah@suse.com>
gpg: key B94556F81C85D0D5: "Ali Abdallah <aabdallah@suse.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

(don't see any chance to attach a file here)

Hi @amphiprion, I test today but no problems from my side. Could you please attach in a text file the log generated by gpg in debug or verbose mode.

PGP verification keeps failing for me on two systems although I did

$ gpg --recv-keys B94556F81C85D0D5

and

$ gpg --import <file>

with the keyring from https://savannah.nongnu.org/project/release-gpgkeys.php?group=davfs2 as <file>.

Both operations succeed and I did

$ sudo pacman-key --refresh-keys

Nonetheless, PGP signature verification fails when trying to build the package with both makepkg and pamac (Manjaro).

Am I missing something or is this related to the package itself?

@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?