@ktht Thanks for the extensive debugging, that's super helpful and I've made your post sticky for the time being until curl is updated.
Search Criteria
Package Details: cvmfs 2.13.2-3
Package Actions
| Git Clone URL: | https://aur.archlinux.org/cvmfs.git (read-only, click to copy) |
|---|---|
| Package Base: | cvmfs |
| Description: | A client-server file system implemented in FUSE and developed to deliver software distributions onto virtual machines in a fast, scalable, and reliable way. |
| Upstream URL: | http://cernvm.cern.ch/portal/filesystem |
| Licenses: | BSD |
| Submitter: | bins |
| Maintainer: | fsiegert (vandelli) |
| Last Packager: | vandelli |
| Votes: | 13 |
| Popularity: | 0.48 |
| First Submitted: | 2010-12-08 13:59 (UTC) |
| Last Updated: | 2025-08-07 13:59 (UTC) |
Dependencies (11)
- c-ares (c-ares-gitAUR)
- curl (curl-gitAUR, curl-c-aresAUR)
- fuse3 (fuse3-gitAUR)
- leveldb (leveldb-gitAUR)
- pacparser
- sqlite (sqlite-fossilAUR)
- cmake (cmake3AUR, cmake-gitAUR) (make)
- gtest (googletest-gitAUR) (make)
- help2man (help2man-gitAUR, python-help2manAUR) (make)
- make (make-gitAUR, make-staticAUR) (make)
- sparsehash (make)
Required by (0)
Sources (2)
fsiegert commented on 2025-09-30 19:51 (UTC)
ktht commented on 2025-09-30 18:12 (UTC)
@DiV21dSREL I had almost the exact same issue: after the Manjaro update on 29/09/25 I was unable to access /cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase, although its parent directory was accessible. After a fair bit of debugging (rebuilding cvmfs with debug symbols; setting CVMFS_HTTP_TRACING=on and specifying CVMFS_DEBUGLOG in /etc/cvmfs/default.local), it finally clicked for me that the offending package must be curl, as it got stuck waiting for the response from cvmfs servers. It also lines up with the fact that curl was upgraded from version 8.15 to 8.16 with the Manjaro update. After downgrading curl to version 8.15 (with sudo manjaro-downgrade curl if you're on Manjaro), I was able to access cvmfs just like before the update.
I also ran git bisect between tags 8.15 and 8.16 in the curl repo to figure out the commit that broke cvmfs. The offending commit happens to be this one, which is part of this PR. Following the discussion there, it seems that the PR introduced a regression in curl, which effectively caused it to run into a deadlock in some scenarios (cf this issue for details). The bug was fixed 2 weeks ago, and the problem is now gone with the current master branch. So we'll just have to wait for the next release of curl.
TLDR: downgrade curl to version 8.15; skip 8.16; wait for version 8.17.
DiV21dSREL commented on 2025-09-22 12:30 (UTC)
After updating to 2.13.2 I've found it impossible to mount properly:
-> ls /cvmfs/lhcb.cern.ch
-> sudo mount -t cvmfs lhcb.cern.ch /cvmfs/lhcb.cern.ch
CernVM-FS: running with credentials 949:948
CernVM-FS: loading Fuse module... done
CernVM-FS: mounted cvmfs on /cvmfs/lhcb.cern.ch
-> ls /cvmfs/lhcb.cern.ch
conda/ containers/ etc/ group_login.csh@ group_login.csh.pre-LBCORE-1949@ group_login.sh@ group_login.sh.pre-LBCORE-1949@ lhcbdirac/ lib/ README
-> ls /cvmfs/lhcb.cern.ch/etc
This then simply hangs.
In parallel I can search for any cmvfs processes, but don't see anything odd:
-> ps aux | grep cvmfs
cvmfs 6122 0.0 0.0 37540 3292 ? S 13:26 0:00 /usr/bin/cvmfs2 -o rw,system_mount,fsname=cvmfs2,allow_other,grab_mountpoint,uid=949,gid=948 lhcb.cern.ch /cvmfs/lhcb.cern.ch
cvmfs 6124 0.0 0.0 48128 12008 ? Sl 13:26 0:00 /usr/bin/cvmfs2 __cachemgr__ . 11 12 4194304000 2097152000 1 3 -1 :
cvmfs 6128 0.0 0.0 37540 3264 ? S 13:26 0:00 /usr/bin/cvmfs2 __cachemgr__ . 11 12 4194304000 2097152000 1 3 -1 :
cvmfs 6133 0.0 0.0 636512 31672 ? Sl 13:26 0:00 /usr/bin/cvmfs2 -o rw,system_mount,fsname=cvmfs2,allow_other,grab_mountpoint,uid=949,gid=948 lhcb.cern.ch /cvmfs/lhcb.cern.ch
dan 6188 0.0 0.0 5872 3852 pts/0 S+ 13:26 0:00 ls --color=auto -F /cvmfs/lhcb.cern.ch/etc
Any tips?
vavolkl commented on 2025-08-07 13:50 (UTC)
At least the makedepends (perhaps the depends too) need fuse3.
Good catch! Yes, fuse3 is now the default. I'd recommend to just s/fuse2/fuse3/ in the depends.
sfleisch commented on 2025-08-05 20:12 (UTC)
-- Looked for FUSE3 libraries named fuse3.
CMake Error at cmake/Modules/FindFUSE3.cmake:74 (MESSAGE):
Could NOT find FUSE3 library
Call Stack (most recent call first):
CMakeLists.txt:484 (find_package)
At least the makedepends (perhaps the depends too) need fuse3.
vandelli commented on 2025-08-04 15:01 (UTC)
Hello @vavolkl,
thanks for your message and for helping both with the PKGBUILD and with the upstream changes. This all looks very. I plan to test and merge your patch in the coming days.
Wainer
vavolkl commented on 2025-08-01 10:04 (UTC)
Dear CvmFS package maintainers, @fsiegert, @vandelli, Thanks from the devs for your great efforts in maintaining this package. I had a look at the PKGBUILD if there's anything to upstream and have added a cmake option in the recently released 2.13.2 that allows you to drop the externals.patch. Here's my proposal for a patch to update:
diff --git a/PKGBUILD b/PKGBUILD
index 361501a..f8957b2 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,36 +4,26 @@
# Contributor: Konstantin Gizdov < arch at kge dot pw >
# Contributor: Lin Further
pkgname=cvmfs
-pkgver=2.13.1
-pkgrel=2
+pkgver=2.13.2
+pkgrel=1
pkgdesc="A client-server file system implemented in FUSE and developed to deliver software distributions onto virtual machines in a fast, scalable, and reliable way."
arch=('x86_64')
url="http://cernvm.cern.ch/portal/filesystem"
license=('BSD')
depends=('fuse2' 'curl' 'c-ares' 'pacparser' 'sqlite' 'leveldb')
-makedepends=('cmake' 'make' 'gtest' 'sparsehash')
+makedepends=('cmake' 'make' 'gtest' 'sparsehash' 'help2man')
backup=('etc/cvmfs/default.local')
install=cvmfs.install
options=('!emptydirs')
-source=("https://ecsft.cern.ch/dist/$pkgname/$pkgname-$pkgver/$pkgname-$pkgver.tar.gz"
- 'settings.cmake'
- 'externals.patch' # TODO: use libcrypto from system openssl instead of building libressl here?
+source=("https://github.com/cvmfs/cvmfs/archive/refs/tags/$pkgname-$pkgver.tar.gz"
+ 'settings.cmake' # TODO: use libcrypto from system openssl instead of building libressl here?
)
-md5sums=('a47c44910e4e44c9fa7f05dd7dcdfd9d'
- '20dc60c61077f4a3711463e8686d260d'
- '0b8d3324e5d7821d0182f1409888f473')
-
-prepare() {
- cd "$srcdir/$pkgname-$pkgver"
-
- # Tweak external packages
- # We remove all those that are provided by Arch/AUR and leave only
- # the ones not currently available
- patch -Np1 -i "$srcdir/externals.patch"
-}
+md5sums=('8b64afe4e7acfe1b847a52d67b9a289a'
+ '2c0adcc2f67d0294d47583a77c06a88b')
build() {
- cd "$srcdir/$pkgname-$pkgver"
+ # github tarballs have naming convention projectname-tagname, and tags are called cvmfs-2.XX.Y
+ cd "$srcdir/$pkgname-$pkgname-$pkgver"
mkdir -p build
cd build
cmake -C "${srcdir}/settings.cmake" -DCMAKE_BUILD_TYPE=Release ../
@@ -42,11 +32,11 @@ build() {
}
package() {
- cd "$srcdir/$pkgname-$pkgver/build"
+ cd "$srcdir/$pkgname-$pkgname-$pkgver/build"
make DESTDIR="$pkgdir/" install
sed -e "s/\/etc\/auto.master/\/etc\/autofs\/auto.master/g" -i $pkgdir/usr/bin/cvmfs_config
sed "s/\/etc\/auto.cvmfs/\/etc\/autofs\/auto.cvmfs/g" -i $pkgdir/usr/bin/cvmfs_config
- install -Dm644 "${srcdir}/${pkgname}-${pkgver}/COPYING" "${pkgdir}/usr/share/licenses/cvmfs/COPYING"
+ install -Dm644 "${srcdir}/${pkgname}-${pkgname}-${pkgver}/COPYING" "${pkgdir}/usr/share/licenses/cvmfs/COPYING"
mkdir -p ${pkgdir}/etc/autofs
ln -s /usr/lib/${pkgname}/auto.cvmfs ${pkgdir}/etc/autofs/auto.cvmfs
diff --git a/settings.cmake b/settings.cmake
index ac83d1f..d0889dd 100644
--- a/settings.cmake
+++ b/settings.cmake
@@ -2,3 +2,4 @@ set (BUILD_SERVER OFF CACHE BOOL "" FORCE)
set (BUILD_RECEIVER OFF CACHE BOOL "" FORCE)
set (BUILD_LIBCVMFS_CACHE OFF CACHE BOOL "" FORCE)
set (BUILD_LIBCVMFS OFF CACHE BOOL "" FORCE)
+set (BUILTIN_EXTERNALS_LIST "libcrypto;vjson;sha3" CACHE STRING "" FORCE)
- This patch also takes pacparser from the system. The compilation has been fixed recently.
- The source tarball url is changed to github. I feel that that is more reliable
- Also adds help2man to the makedepends in order to install manpages.
I've made a note of the numerous compilation warnings and the questions in the .INSTALL and will update that when I find the time.
Cheers, Valentin
i.further commented on 2025-07-22 13:10 (UTC)
Maybe should update the md5sum to sha256sums
bwynneHEP commented on 2025-05-28 15:54 (UTC)
Updated the package with clean build and it worked fine.
Thanks Frank, and no worries - earlier commenters solved the problem and it was easy for me to implement locally.
Cheers, Ben
fsiegert commented on 2025-05-13 17:44 (UTC)
Hi @bwynneHEP and @kgizdov,
Sorry about the late response. I have updated the PKGBUILD, and it seems to work for me. Can you try?
Best,
Frank
Pinned Comments
ktht commented on 2025-09-30 18:12 (UTC)
@DiV21dSREL I had almost the exact same issue: after the Manjaro update on 29/09/25 I was unable to access
/cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase, although its parent directory was accessible. After a fair bit of debugging (rebuilding cvmfs with debug symbols; settingCVMFS_HTTP_TRACING=onand specifyingCVMFS_DEBUGLOGin/etc/cvmfs/default.local), it finally clicked for me that the offending package must be curl, as it got stuck waiting for the response from cvmfs servers. It also lines up with the fact that curl was upgraded from version 8.15 to 8.16 with the Manjaro update. After downgrading curl to version 8.15 (withsudo manjaro-downgrade curlif you're on Manjaro), I was able to access cvmfs just like before the update.I also ran
git bisectbetween tags 8.15 and 8.16 in the curl repo to figure out the commit that broke cvmfs. The offending commit happens to be this one, which is part of this PR. Following the discussion there, it seems that the PR introduced a regression in curl, which effectively caused it to run into a deadlock in some scenarios (cf this issue for details). The bug was fixed 2 weeks ago, and the problem is now gone with the current master branch. So we'll just have to wait for the next release of curl.TLDR: downgrade curl to version 8.15; skip 8.16; wait for version 8.17.