Arch Linux User Repository

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.

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 \

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

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.

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.

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.

Nope, still no openssl support on Arch (due to openssl 1.1 :(

(ldd on the bconsole binary should have both libssl and libcrypto)

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

@bsdice, Thanks
I agree that determining the package layout based on the debian files is wrong. I don't have a lot of time to maintain the package and the author of bareos has moved/renamed files between releases. Rather than the aur package breaking after every upgrade this "hack" allowed it to keep working. However, this package does not follow "arch" standards. A lot of what you list such as sbins binaries are installed in the incorrect places or indirect results of depending on this debian file layout.

Maybe if I get some time and am less lazy,I will move away from that, its more work to maintain as the bareos author changes stuff around.

A side note:
It appears like bareos isn't very active anymore. I was thinking about looking at bacula.

TLDR; I audited the software and made a new package from scratch with below issues imho fixed, see https://pastebin.com/QiJPwdzd (snip into files PKGBUILD and bareos.install) Credits to the maintainers of bareos and bacula for workarounds and a little template help.

Hello,

I've been tinkering with a spare LTO5 drive for homeoffice backup needs using this package. Here are some issues I have encountered:

- OpenSSL-1.1 API breakage
- sbin binaries are installed in /usr/bin/sbin/ (should be /usr/bin)
- wrong chmod of /etc/bareos and its files (+x for config files is wrong)
- on my fully up-to-date Arch machine, /etc/nst0 (tape) is owned by root:storage. Post-install script should add user bareos to group storage in order to access the tape drive without root
- configure parameters not fully up to date with 16.2.6 i.e. some superfluous settings (ipv6 is enabled by default, others I forget)
- build/package/opt dependencies slightly out of tune (e.g. openssl is basically installed everywhere, configure will see it and try to use it, make will fall over due to API breakage, in essence making openssl-1.0 a hard dependency)
- Not using /run for PID and lock files (together with tmpfiles.d by systemd)
- Config files that come with the package are in the way if you modify them and want to upgrade. Imho Arch philosophy should be more like "supply samples and let the user pick any configs" instead of throwing active upstream configs in his face on every install and upgrade. Compare http://pr0gramm.com/user/Pr0G0/uploads/1484494 for a visual image. ;-)
- with bat qt-gui deprecated upstream in favor of web-gui I wonder what is gained from splitting this package up into client, server, database support and whatnot instead of doing one package. Granted, it will pull in postgresql as well as mysql support libs (sqlite is pulled in by python already) but with an uncertain future of bat, it no longer requires graphical libs on the server.
- post-remove cleanup could use some work (not stopping and disabling services in pre-uninstall etc.)
- This package imho wrongly relies on Debianisms and I may be wrong but does pulling in dbconfig-common files make any sense on Arch?
- Since I have a lot of cores I use aggressive parallel make settings to speed things up; make install of bareos requires -j1 otherwise it will error out (just to note that)
- In my package there is no requirement for logrotate and also there is no /var/log/bareos, the user should log to systemd and let it do all the rotating work
- I ran namcap -i on PKGBUILD and .xz and may have fixed a couple of other things

I won't upload my PKGBUILD into AUR because I have little time to maintain it right now, so just contributing some hopefully valuable feedback.

Regards,
--se