Package Details: nautilus-seafile 0.1-1

Git Clone URL: https://aur.archlinux.org/nautilus-seafile.git (read-only, click to copy)
Package Base: nautilus-seafile
Description: Nautilus extension for Seafile
Upstream URL: https://github.com/benruijl/seafile-client/nautilus-seafile
Keywords: nautilus network seafile sync
Licenses: GPL
Groups: network
Submitter: Revelation60
Maintainer: Revelation60
Last Packager: Revelation60
Votes: 6
Popularity: 0.000000
First Submitted: 2017-04-08 09:02
Last Updated: 2017-04-08 09:02

Latest Comments

pablo1 commented on 2020-02-29 16:07

The package fails to build for me with this error:

:: Parsing SRCINFO (1/1): nautilus-seafile
==> Making package: nautilus-seafile 0.1-1 (2020-02-29T17:06:01 CET)
==> Retrieving sources...
  -> Downloading v0.1.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   129  100   129    0     0    464      0 --:--:-- --:--:-- --:--:--   462
100 2100k    0 2100k    0     0   948k      0 --:--:--  0:00:02 --:--:-- 1856k
==> Validating source files with md5sums...
    v0.1.tar.gz ... Passed
==> Making package: nautilus-seafile 0.1-1 (2020-02-29T17:06:05 CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found v0.1.tar.gz
==> Validating source files with md5sums...
    v0.1.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting v0.1.tar.gz with bsdtar
==> Sources are ready.
==> Making package: nautilus-seafile 0.1-1 (2020-02-29T17:06:08 CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
+ set -e
++ dirname ./build.sh
+ CURRENT_PWD=.
++ uname -s
+ '[' Linux '!=' Linux ']'
+ pushd .
~/.cache/yay/nautilus-seafile/src/seafile-client-0.1/nautilus-seafile ~/.cache/yay/nautilus-seafile/src/seafile-client-0.1/nautilus-seafile
+ CONFIG=Debug
+ '[' a '!=' adebug ']'
+ rm -rf CMakeCache.txt CMakeFiles
+ CONFIG=Release
+ cmake -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_EXPORT_COMPILE_COMMANDS=on
CMake Warning:
  No source or binary directory provided.  Both will be assumed to be the
  same as the current working directory, but note that this warning will
  become a fatal error in future CMake releases.


-- The C compiler identification is GNU 9.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.6.3") 
CMake Warning (dev) at CMakeLists.txt:12 (SET):
  implicitly converting 'Path to Nautilus Extenstion Directory' to 'STRING'
  type.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Checking for module 'glib-2.0>=2.15'
--   Found glib-2.0, version 2.62.5
-- Checking for module 'libnautilus-extension>=2.0'
--   Found libnautilus-extension, version 3.34.2
-- Checking for module 'libccnet>=1.3'
--   Package 'libccnet', required by 'virtual:world', not found
CMake Error at /usr/share/cmake-3.16/Modules/FindPkgConfig.cmake:463 (message):
  A required package was not found
Call Stack (most recent call first):
  /usr/share/cmake-3.16/Modules/FindPkgConfig.cmake:643 (_pkg_check_modules_internal)
  CMakeLists.txt:41 (PKG_CHECK_MODULES)


-- Configuring incomplete, errors occurred!
See also "/home/binaryplease/.cache/yay/nautilus-seafile/src/seafile-client-0.1/nautilus-seafile/CMakeFiles/CMakeOutput.log".
==> ERROR: A failure occurred in build().
    Aborting...
Error making: nautilus-seafile

carlos commented on 2017-04-26 13:15

The Upstream URL should be: https://github.com/benruijl/seafile-client/tree/nautilus_extension/nautilus-seafile

Revelation60 commented on 2017-04-24 20:53

Sadly this package crashes with nautilus 3.24, since nautilus is compiled with the new libssl-1.0. The seafile packages don't compile with the latest libssl yet, so there is nothing you can do other than to uninstall the plugin for now...