Package Details: sogo 4.0.8-1

Git Clone URL: (read-only)
Package Base: sogo
Description: groupware server built around (OGo) and the SOPE application server
Upstream URL:
Licenses: GPL
Replaces: sogo2
Submitter: DJ_L
Maintainer: deons
Last Packager: deons
Votes: 7
Popularity: 0.000703
First Submitted: 2016-05-05 01:05
Last Updated: 2019-08-03 06:06

Dependencies (16)

Required by (0)

Sources (4)

Latest Comments

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

DJ_L commented on 2016-07-29 17:21

Looks like this is fixed in gnustep-make-2.6.8-2.

DJ_L commented on 2016-07-23 19:40

Okay, so gnustep-make-2.6.8-1 is broken. So was gnustep-make-2.6.7-1, but it happened to work with this package. The quick fix is:

# sed 's@/usr/sbin@/usr/bin@' -i.bak /usr/GNUstep/GNUstep.conf

I've created a bug (with patch) for the package at

DJ_L commented on 2016-07-23 18:33

Well, fakeroot is not the culprit. Looks like gnustep-make had some changes.

pohl7589 commented on 2016-07-23 11:04


test -d $pkgdir/usr/sbin && install -v -d -m 0755 $pkgdir/usr/bin && mv $pkgdir/usr/sbin/* $pkgdir/usr/bin && rmdir $pkgdir/usr/sbin

at the end of package() {} section of the pkgbuild as you suggested in your previous post. As a result the binaries are moved in the correct /usr/bin directory.

Thanks. Maybe you will be able to reproduce this bug on your host and find a permanent solution.

pohl7589 commented on 2016-07-23 04:42

My hosts were installed both after and before your install date. I noticed I have fakeroot version 1.21-1 installed. Yours is one version behind. Could this be the difference?

DJ_L commented on 2016-07-22 18:15

Okay, I'll get a new host built tomorrow morning (maybe tonight) and pkgbuild updated to handle this case. Hopefully I'll actually be able to see the issue. I'd still like to figure out why these hosts behave differently. I'm kind of grasping at straws here. Do you happen to know when your testing hosts were brought online? My build host for this package was brought online 20160418. Earliest version of pacman was 5.0-1, fakeroot has only ever been 1.20.2-1. Not really sure what else to look at. I was guessing maybe the pacman-4.2 update, when the symlink handling was changed, but that was back in December 2014 and is unrelated to makepkg. Fakeroot install seems to be the difference (which is default on my system)...

[pkguser@server3 sogo]$ makepkg -s
==> Making package: sogo 3.1.4-1 (Fri Jul 22 13:07:19 CDT 2016)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading SOGo-3.1.4.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 246 100 246 0 0 867 0 --:--:-- --:--:-- --:--:-- 869
100 265 100 265 0 0 414 0 --:--:-- --:--:-- --:--:-- 414
100 30.7M 100 30.7M 0 0 4527k 0 0:00:06 0:00:06 --:--:-- 6484k
-> Found sogo_configure.patch
-> Found sogo.service
-> Found sogo.confd
==> Validating source files with sha256sums...
SOGo-3.1.4.tar.gz ... Passed
sogo_configure.patch ... Passed
sogo.service ... Passed
sogo.confd ... Passed
==> Extracting sources...
-> Extracting SOGo-3.1.4.tar.gz with bsdtar
==> Starting prepare()...
patching file configure
Hunk #1 succeeded at 263 (offset 12 lines).
==> Starting build()...
GNUstep environment:
system: /usr/System
local: /usr/Local
user: /home/pkguser/GNUstep
path: /usr/System:/usr/Network:/usr/Local:/root/GNUstep
flat: yes
arch: x86_64-unknown-linux-gnu
combo: gnu-gnu-gnu
==> Tidying install...
-> Removing libtool files...
-> Purging unwanted files...
-> Removing static library files...
-> Compressing man and info pages...
==> Checking for packaging issue...
==> Creating package "sogo"...
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Adding install file...
-> Generating .MTREE file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: sogo 3.1.4-1 (Fri Jul 22 13:09:52 CDT 2016)
[pkguser@server3 sogo]$ ls -l pkg/sogo/usr/
total 12
drwxr-xr-x 2 pkguser pkguser 4096 Jul 22 13:09 bin
drwxr-xr-x 5 pkguser pkguser 4096 Jul 22 13:09 include
drwxr-xr-x 5 pkguser pkguser 4096 Jul 22 13:09 lib
[pkguser@server3 sogo]$ cd src/SOGo-3.1.4
[pkguser@server3 SOGo-3.1.4]$ make DESTDIR=$PWD/dest install
This is gnustep-make 2.6.7. Type 'make print-gnustep-make-help' for help.
Making all in SOPE/NGCards ...
Making all for library libNGCards...
make[4]: Nothing to be done for 'internal-library-compile'.
Making install for tool sogo-slapd-sockd...
Installing tool sogo-slapd-sockd...
Making install for tool sogo-ealarms-notify...
Installing tool sogo-ealarms-notify...
Making install in Tests/Unit ...
Skipping installation of test tools...
[pkguser@server3 SOGo-3.1.4]$ ls -l dest/usr/
total 12
drwxr-xr-x 5 pkguser pkguser 4096 Jul 22 13:13 include
drwxr-xr-x 4 pkguser pkguser 4096 Jul 22 13:13 lib
drwxr-xr-x 2 pkguser pkguser 4096 Jul 22 13:13 sbin
[pkguser@server3 SOGo-3.1.4]$

Sorry so long, but really curious why this works here and not there.

pohl7589 commented on 2016-07-22 17:25

I tried on desktop (x86_64), laptop (x86_64) and odroid C2 (aarch64) with up to date arch linux installations. On all hosts the binaries are going to be installed under /usr/sbin.

$ git clone
$ makepkg -s
$ ls -la /home/alarm/aur/sogo/pkg/sogo/usr
drwxr-xr-x 5 alarm alarm 4096 Jul 22 19:05 include
drwxr-xr-x 5 alarm alarm 4096 Jul 22 19:05 lib
drwxr-xr-x 2 alarm alarm 4096 Jul 22 19:05 sbin

The symlink "/usr/sbin" is pointing to "bin" (typo in previous post).

DJ_L commented on 2016-07-21 10:48

[pkguser@server3 usr]$ pacman -Q sogo
sogo 3.1.4-1
[pkguser@server3 usr]$ pwd
[pkguser@server3 usr]$ ls -l
total 12
drwxr-xr-x 2 pkguser pkguser 4096 Jul 17 12:17 bin
drwxr-xr-x 5 pkguser pkguser 4096 Jul 17 12:17 include
drwxr-xr-x 5 pkguser pkguser 4096 Jul 17 12:17 lib

Did you use something other than makepkg to build? Did you make any changes other than adding aarch64 to the arch array? A plain 'make DESTDIR=$PWD/dest install' does install those files to ./dest/usr/sbin, while in package(), the symlink is accounted for and the files are correctly installed into $pkgdir/usr/bin. I'm not clear on exactly how this works, I assume some fakeroot magic.

While I could work around this, something like 'test -d $pkgdir/usr/sbin && install -vdm755 $pkgdir/usr/bin && mv $pkgdir/usr/sbin/* $pkgdir/usr/bin && rmdir $pkgdir/usr/sbin' at the end of the package function, it shouldn't be necessary. Something is working differently on your system vs my build host.

You mentioned that /usr/sbin was a link to /bin. I'm not sure if that was just typing fast or if it is broken (or if even related). /usr/sbin should be a symlink to bin (not /bin, nor a hard link - though that would probably work as well if /bin weren't a symlink itself). If your original message was not a typo, then that might an issue, I don't know.

Anyway, the string of commands above will work around it, but I'm not sure that it is appropriate to work around it. As to where this is defined in the build machinery, it's not quite that simple. This is defined in GNUStep's environment. That said, there is a makefile that specifies FHS layout and moves these to the sbin directory in the install prefix. I'll try the build on a fresh host this weekend and see if something has changed since my build host was brought up, but I suspect not.

pohl7589 commented on 2016-07-20 16:27

Package 3.1.4 does not install. Tried 'x86_64' and new 'aarch64' architecture.

$ sudo pacman -U sogo-3.1.4-1-aarch64.pkg.tar.xz

debug: checking possible conflict: /usr/sbin/
debug: found file conflict /usr/sbin, packages sogo and (filesystem)
debug: returning error 49 from _alpm_sync_check : conflicting files
error: failed to commit transaction (conflicting files)
sogo: /usr/sbin exists in filesystem
Errors occurred, no packages were upgraded.

/usr/sbin is a link to /bin and is therefore treated as a file rather than a directory. I extracted the package and files sogo-ealarms-notify, sogo-slapd-sockd, sogo-tool and sogod want to be installed in /usr/sbin rather than in /usr/bin.

In which file is specified where the binaries are going to be installed?

DJ_L commented on 2016-06-09 01:01

Updated to 3.1.2. Angular was updated again (rc5), clear browser cache as usual.