Package Details: bareos-director-python3-plugin 23.0.1-2

Git Clone URL: https://aur.archlinux.org/bareos.git (read-only, click to copy)
Package Base: bareos
Description: Bareos - Backup Archiving Recovery Open Sourced - Python plugin for director daemon
Upstream URL: http://www.bareos.org
Keywords: Backup bacula bareos
Licenses: AGPL3
Groups: bareos
Conflicts: bareos-director-python-plugin
Submitter: AlD
Maintainer: None
Last Packager: khvalera
Votes: 23
Popularity: 0.000025
First Submitted: 2014-07-23 09:45 (UTC)
Last Updated: 2024-02-20 22:01 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 18 Next › Last »

freaknils commented on 2018-03-22 08:09 (UTC)

Hi, is there a reason why arm is not in arch=(i686 x86_64) ? On my armv7h cubietruck i am able to build and use bareos.

spradlim commented on 2018-02-20 02:28 (UTC)

Fixed Cephfs broken build. I did not see this issue since I didn't have the lib for cephfs installed and autotools did not try to build with cephfs.

@bsdice FYI: I have updated the PKGBUILD quite a bit, I made it more ArchLinux way of doing stuff, rather than a hacking script. You don't need those CPPFLAGS for openssl anymore.

bsdice commented on 2018-02-19 22:14 (UTC) (edited on 2018-02-19 22:16 (UTC) by bsdice)

As a temp fix, see sed line below to disable.

    build() {
    cd "${srcdir}/${pkgname}"

    # Disable cephfs, broken
    sed -i 's/have_cephfs=\"yes\"/have_cephfs=\"no\"/' configure

    CPPFLAGS+=" -I/usr/include/openssl-1.0" \
    LDFLAGS+=" -L/usr/lib/openssl-1.0" \
    DISTNAME="systemd" \
    ./configure \

ferion commented on 2018-02-19 20:17 (UTC) (edited on 2018-02-19 20:18 (UTC) by ferion)

Any way around to not compilie ceph in bareos-common ?

cephfs-fd.c:470:97: error: cannot convert 'stat' to 'ceph_statx' for argument '4' to 'int ceph_readdirplus_r(ceph_mount_info, ceph_dir_result, dirent*, ceph_st

It's an open bug report here:

https://bugs.bareos.org/view.php?id=872&history=1#history

spradlim commented on 2017-12-08 17:41 (UTC) (edited on 2017-12-08 20:05 (UTC) by spradlim)

I have upgraded the package to 17.2.4rc2.

Several things have changed, hopefully all for the better.

  • openssl 1.1 is now supported, fixes all ssl issues

  • I moved config files to /usr/share/bareos/config to prevent pacnew files being created whenever you upgraded. bsdice suggested this idea.

  • Moved to the systemd script included with bareos.

  • I am actually correctly managing the package rather than using my script that used the debian paths. This means binaries have moved from /sbin to /bin to fit with ArchLinux.

  • Tested bareos-webui works with arch package jansson, community doesn't seeem to be required.

I have successfully upgraded my database and machines from 16.2 to 17.2. Some manual work was required.

TODO:

  • Fix some namcap warnings.

  • Move some required dependencies to optional.

Renich commented on 2017-09-15 18:36 (UTC) (edited on 2017-09-15 18:36 (UTC) by Renich)

Guys, if you don't have community/jansson installed, the webui will not work. It will claim that you need to "upgrade" to an older version. IMHO, this should be included as a dependency.

bsdice commented on 2017-08-30 09:51 (UTC)

My build with my PKGBUILD has this: # ldd /usr/bin/bconsole ... libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0 (0x00007feafbafd000) libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0x00007feafb688000) ... Not tested though because I only use localhost.

svenne_k commented on 2017-08-30 06:21 (UTC)

Nope, still no openssl support on Arch (due to openssl 1.1 :( (ldd on the bconsole binary should have both libssl and libcrypto)

svenne_k commented on 2017-08-30 06:15 (UTC)

@spradlim Regarding your side-note: the Bareos project is active, they just have fewer releases in the open source version that the commercial version (I run both). A new version is probably out within a month, most likely called 17.2. I work at a danish Bareos partner company, so I know for sure :) I have been bugging them for an official Arch build, but they have not had the ressources to set it up yet.. (it should be doable as they run their infrastructure on Suse Opn Build Service (OBS). Is the SSL working? I currently use a hacked build to have it working in the current aur-version...