Package Details: cvmfs 2.11.3-1

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: 12
Popularity: 1.00
First Submitted: 2010-12-08 13:59 (UTC)
Last Updated: 2024-04-26 06:18 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

i.further commented on 2020-10-28 10:27 (UTC)

Hi it misses the /etc/auto.cvmfs

fsiegert commented on 2020-06-14 10:27 (UTC)

Thanks for the suggestion @ryuwd. This causes a lot of unused-variable warnings during compilation due to assert statements being optimised out, but I think it's still a change worth having. I've pushed this to the PKGBUILD now.

ryuwd commented on 2020-06-11 21:00 (UTC)

Hi, and thank you for providing this package. It works well.

I noticed in a recent install that CVMFS was not being compiled with optimisation (_FORTIFY_SOURCE warnings). CMake doesn't compile with optimisation as default, so I edited the PKGBUILD, and added this option to the CMake command in build():

-DCMAKE_BUILD_TYPE=Release

which added the desired optimisation flags when building. I wondered if this perhaps worth adding to the package?

Cheers, Ryun

dpm commented on 2017-08-16 16:33 (UTC)

Hi @vandelli, @fsiegert and @Bigben37, I reported it upstream https://sft.its.cern.ch/jira/browse/CVM-1362 Cheers, Davide

dpm commented on 2017-08-16 14:12 (UTC) (edited on 2017-08-16 16:31 (UTC) by dpm)

Hi @vandelli, I was looking exactly at line 44, because we have /etc/manjaro-release insted of /etc/arch-release. A quick fix could be something like that: 44 if (EXISTS /etc/arch-release or EXISTS /etc/manjaro-release) 45 set (ARCHLINUX TRUE) but I've never work with CMakeList ("or" or "OR" or other sign?) and also I would like to implement a sed command quite strong to pass future update of CMakeList.txt Cheers, Davide

vandelli commented on 2017-08-16 13:55 (UTC)

Hi @dpm, thanks for looking into this. While I believe this can be worked around in the PKGBUILD, perhaps it should also be reported upstream (https://sft.its.cern.ch/jira/projects/CVM/issues/)? The problem seems to originate around line 44 of the original CMakeList.txt file: 39 if (${CMAKE_SYSTEM_NAME} MATCHES "Linux") 40 set (LINUX TRUE) 41 if (EXISTS /etc/debian_version) 42 set (DEBIAN TRUE) 43 endif (EXISTS /etc/debian_version) 44 if (EXISTS /etc/arch-release) 45 set (ARCHLINUX TRUE) 46 endif (EXISTS /etc/arch-release) I assume /etc/arch-release does not exists in Manjaro, right? This causes Manjaro to be treated like a Redhat-like distribution. Cheers Wainer

dpm commented on 2017-08-16 13:17 (UTC)

Hi @fsiegert, I think that the problem comes from the CMakeList in cvmfs package, because Manjaro users fall in the section for other system where /usr/lib folder is the 32-bit one. In the following weeks, I could try to modify your PKGBUILD and mail it to you (Manjaro users have full access to AUR and for the next time you update the package I would like to have a smooth update) or even submit a pull request to GitHub repo. I'll see what to do. @Bigben37: nice workaround, simpler than mine! (I don't know if it could be dangerous remove the symlink from a such important folder, some other application could have a runtime error if access to it... I don't know) Cheers, Davide

Bigben37 commented on 2017-08-16 12:57 (UTC)

Hi @fsiegert and @dpm, I'm also running on Manjaro and had the same problem. In Manjaro /usr/lib64 is a symlink to /usr/lib, maybe this is the problem. My workaround was: - delete the /usr/lib64 symlink - install cvmfs - move the files installed in /usr/lib64 to /usr/lib - delete the /usr/lib64 directory - recreate the /usr/lib64->/usr/lib symlink

fsiegert commented on 2017-08-16 12:36 (UTC)

Hi @dpm, my /usr looks identically and I haven't seen this problem before and also have no idea where it should come from. So unless somebody on Arch encounters the same problem, I would suspect it's specific to Manjaro. Cheers, Frank

dpm commented on 2017-08-14 14:59 (UTC) (edited on 2017-08-14 16:38 (UTC) by dpm)

Hi @fsiegert and @vandelli, Thank you very much for mantaining this package! I've a problem installing it: error: failed to commit transaction (conflicting files) cvmfs: /usr/lib64 exists in filesystem I've seen that this should be already solved (comment of rajanandakumar 2016-01-28 11:55), but modified PKGBUILD doesn't work for me. Hint : with respect to rajanandakumar, I don't have the line 'cvmfs: /sbin exists in filesystem'. Addiotional info: I'm on Manjaro (Arch - based OS) and my /usr folder look like this: drwxr-xr-x 9 root root 4,0K 14 ago 16.22 . drwxr-xr-x 17 root root 4,0K 22 giu 10.31 .. drwxr-xr-x 5 root root 132K 14 ago 16.22 bin drwxr-xr-x 508 root root 68K 14 ago 16.22 include drwxr-xr-x 240 root root 224K 14 ago 16.22 lib drwxr-xr-x 30 root root 36K 13 ago 16.09 lib32 lrwxrwxrwx 1 root root 3 21 giu 16.44 lib64 -> lib drwxr-xr-x 13 root root 4,0K 7 giu 14.14 local lrwxrwxrwx 1 root root 3 21 giu 16.44 sbin -> bin drwxr-xr-x 342 root root 12K 14 ago 16.22 share drwxr-xr-x 3 root root 4,0K 14 ago 16.22 src Cheers, Davide EDIT: I managed to install package, modifying by hand CMakeList.txt line 113 ("lib64" to "lib") and 115 ("lib" to "lib32") and recompilying by means of your PKGBUILD after changing the md5sum for the pkg source. This CMakeList doesn't see Manjaro as Arch, so I've ended up in the section for Fedora, CentOS etc that probably have a different structure of /usr folder.

« First ‹ Previous 1 2 3 4 Next › Last »