[SOGo] Re: SOGo upgrade issue
On 06/19/2015 02:26 PM, Steve Ankeny wrote: Rowland Penny recreated my problem in a VM (similar to my setup) here's the content of his e-mail -- OK, there appears to be something wrong with the inverse samba packages, I created a VM, installed latest Ubuntu 14.04 server, updated this, installed samba: apt-get install samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient winbind python-samba libnss-winbind libpam-winbind libsmbclient libwbclient0 didn't do anything else except added: deb http://inverse.ca/ubuntu-nightly trusty trusty To /etc/apt/sources.list ran 'apt-get update' and then 'apt-get upgrade' This lead to: The following packages have been kept back: libldb-dev libldb1 libnss-winbind libpam-winbind libsmbclient libwbclient0 linux-generic-lts-utopic linux-headers-generic-lts-utopic linux-image-generic-lts-utopic python-ldb python-samba samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient winbind The following packages will be upgraded: libparse-pidl-perl libtalloc-dev libtalloc2 libtdb-dev libtdb1 libtevent0 python-talloc python-tdb tdb-tools 9 to upgrade, 0 to newly install, 0 to remove and 20 not to upgrade. Need to get 468 kB of archives. After this operation, 253 kB of additional disk space will be used. Do you want to continue? [Y/n] y Installed the packages and then ran 'apt-get update' and then 'apt-get upgrade' again Calculating upgrade... Done The following packages have been kept back: libldb-dev libldb1 libnss-winbind libpam-winbind libsmbclient libwbclient0 linux-generic-lts-utopic linux-headers-generic-lts-utopic linux-image-generic-lts-utopic python-ldb python-samba samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient winbind 0 to upgrade, 0 to newly install, 0 to remove and 20 not to upgrade. I 'think' I could probably force the upgrade with 'apt-get dist-upgrade', but I also think I wouldn't be running Trusty any more due to the installation of the Utopic kernel. therefore, Inverse packages *must* be borked, if they will not cleanly upgrade standard distro packages. Rowland I think the Samba mailing list has gone the second mile in trying to help me upgrade Samba. I'm needing a resolution from Inverse or an alternative source for the Samba packages. thx (I'm patient! I know it's the weekend.) understanding that I'm ignorant of the build process used by Inverse . . . However, could it be the Inverse packages were built on a system with a different kernel? -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] BTS activities for Friday, June 19 2015
Title: BTS activities for Friday, June 19 2015 BTS Activities Home page: http://www.sogo.nu/bugs Project: SOGo For the period covering: Friday, June 19 2015 idlast updatestatus (resolution)categorysummary 3235 2015-06-19 14:09:16 updated (open) ActiveSync a programming error in SOGoMailObject+ActiveSync.m 3257 2015-06-19 16:02:15 resolved (fixed) OpenChange backend openchange_ocsmanager 2.2 3012 2015-06-19 15:17:49 closed (suspended) OpenChange backend Cannot run ocsmanger
Re: [SOGo] free/busy between two organizations - expose free/busy in SOGo / Read external free/busy
On 06/16/2015 05:23 PM, Marc Patermann wrote: Is there some documentation how this works? How is the /ews of the exchange server is found etc.? You need to define an extra usersource like this: type = ldap; CNFieldName = cn; IDFieldName = sAMAccountName; UIDFieldName = sAMAccountName; baseDN = DC=company,DC=com; canAuthenticate = NO; bindDN = a_dn_to_bind_with; bindPassword = a_secret; displayName = Descriptive name; hostname = ldap://q.w.e.r ldap://a.s.d.f;; MSExchangeHostname = webmail.company.com; id = exch-ad; isAddressBook = YES; port = 3268; scope = SUB; After this, free/buzy lookups are done 'automatically'. Several fixes were made for timezone conversion issue, but latest sogo works very well. Let me know if you need more info. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Problems with Contact sync TB38.0.1, Connector 31.0.1 and owncloud 7.05/8.0.4
Hi André, I did not know about a correlation between TB 31.x and Connector 31.x. I've downgraded to TB 31.6.0. But unfortunately the same problems... :-o I made a lot changes to the contacts before and after upgrade to TB 38. Specially I removed Surname and Givenname from Company-only contacts and edited in some contacts the Display-name also. It seems, that not of all changes, specially if I do this very quickly, will be recognized by Sogo Connector!? This end in no sync of this changes. Also it seems that no full sync between TB address book and the CalDAV-Server (owncloud) taking place at any time!? The expected outcome should be a address book in sync... The manual command sync know should do that. I have now to TB, 31.6.0 and 38.0.1, running with Sogo Connector 31.0.1. Gruss Ralf Am 18.06.2015 um 23:38 schrieb André Schild: Hello Ralf, I think the Connector 31 is for TB 31, for TB 38 there is no release available at the moment. Best to downgrade TB to 31 until the connector is updated. André Am 18.06.2015 um 22:56 schrieb RalfK: Hi, after upgrading TB to 38.0.1 I have the following problems: - @TB: Contacts, drag and dropped to the synced address book, shows SC message no changes. The contact will only synced to owncloud by change something. - some contacts gets multiplication during syncs Example: BEGIN:VCARD VERSION:3.0 FN;CHARSET=UTF-8:Büro-Creativ GmbH ORG;CHARSET=UTF-8:Büro-Creativ GmbH; ADR;TYPE=WORK,POSTAL;CHARSET=UTF-8:;;Schönbornluster Str. 53;Koblenz;;56070; TEL;TYPE=WORK,VOICE:+49 261 579780 TEL;TYPE=FAX:+49 261 579785 EMAIL;TYPE=PREF,INTERNET:i...@buero-creativ.de URL;TYPE=WORK:http://buero-creativ.de/ END:VCARD Any changes in TB 38.0.1? Thanks for help Ralf -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Problems with Contact sync TB38.0.1, Connector 31.0.1 and owncloud 7.05/8.0.4
After some muggeling to get my contacts to the CalDAV-Server, I deleted all TB address books, re-installed SoGo Connector and added the remote address books again. It seems to be a stable situation now... :-) Am 19.06.2015 um 13:10 schrieb RalfK: Hi André, I did not know about a correlation between TB 31.x and Connector 31.x. I've downgraded to TB 31.6.0. But unfortunately the same problems... :-o I made a lot changes to the contacts before and after upgrade to TB 38. Specially I removed Surname and Givenname from Company-only contacts and edited in some contacts the Display-name also. It seems, that not of all changes, specially if I do this very quickly, will be recognized by Sogo Connector!? This end in no sync of this changes. Also it seems that no full sync between TB address book and the CalDAV-Server (owncloud) taking place at any time!? The expected outcome should be a address book in sync... The manual command sync know should do that. I have now to TB, 31.6.0 and 38.0.1, running with Sogo Connector 31.0.1. Gruss Ralf Am 18.06.2015 um 23:38 schrieb André Schild: Hello Ralf, I think the Connector 31 is for TB 31, for TB 38 there is no release available at the moment. Best to downgrade TB to 31 until the connector is updated. André Am 18.06.2015 um 22:56 schrieb RalfK: Hi, after upgrading TB to 38.0.1 I have the following problems: - @TB: Contacts, drag and dropped to the synced address book, shows SC message no changes. The contact will only synced to owncloud by change something. - some contacts gets multiplication during syncs Example: BEGIN:VCARD VERSION:3.0 FN;CHARSET=UTF-8:Büro-Creativ GmbH ORG;CHARSET=UTF-8:Büro-Creativ GmbH; ADR;TYPE=WORK,POSTAL;CHARSET=UTF-8:;;Schönbornluster Str. 53;Koblenz;;56070; TEL;TYPE=WORK,VOICE:+49 261 579780 TEL;TYPE=FAX:+49 261 579785 EMAIL;TYPE=PREF,INTERNET:i...@buero-creativ.de URL;TYPE=WORK:http://buero-creativ.de/ END:VCARD Any changes in TB 38.0.1? Thanks for help Ralf -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Problems with Contact sync TB38.0.1, Connector 31.0.1 and owncloud 7.05/8.0.4
Am 19.06.2015 um 15:08 schrieb RalfK: After some muggeling to get my contacts to the CalDAV-Server, I deleted all TB address books, re-installed SoGo Connector and added the remote address books again. Probably the TB38 did upgrade your addressbooks, so it did break when downgrading That's the nice thing about server-backed things, you can always get the back from the server when you screwed up things locally ;) André -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Compiling SOGo from sources
Hello, I am trying to compile SOGo from sources to do some customization. What are correct versions of tools and libraries to compile SOGo under Ubuntu 14.04 ? I have started with compiling latest GNUStep (trunk) with clang according to their instructions: http://wiki.gnustep.org/index.php/GNUstep_under_Ubuntu_Linux All packages have been compiled and installed fine. Then while compiling SOPE framework 2.3.0, I am getting warnings while compiling: WOChildComponentReference.m:191:36: warning: 'sel_get_name' is deprecated [- Wdeprecated-declarations] [[child name] cString], sel_get_name(_cmd), diff); ^ /usr/GNUstep/Local/Library/Headers/objc/runtime-deprecated.h:63:13: note: 'sel_get_name' has been explicitly marked deprecated here const char *sel_get_name(SEL selector); and errors while linking: Linking tool wod ... clang-3.7: warning: argument unused during compilation: '-F.' ./obj/wod.obj/NSObject+WO.m.o: In function `WOGetKVCGetMethod': /media/dima/HDD/post/sogo/SOPE/sope-appserver/NGObjWeb/NSObject+WO.m:270: undefined reference to `sel_get_uid' /media/dima/HDD/post/sogo/SOPE/sope-appserver/NGObjWeb/NSObject+WO.m:276: undefined reference to `__objc_responds_to' ./obj/wod.obj/NSObject+WO.m.o: In function `WOGetKVCValueUsingMethod': /media/dima/HDD/post/sogo/SOPE/sope-appserver/NGObjWeb/NSObject+WO.m:321: undefined reference to `__objc_responds_to' ../../sope-core/EOControl/./obj/libEOControl.so: undefined reference to `sel_get_any_uid' ./../../sope-mime/obj/libNGMime.so: undefined reference to `sel_eq' ././obj/libNGObjWeb.so: undefined reference to `sel_get_name' clang-3.7: error: linker command failed with exit code 1 (use -v to see invocation) Please help to identify correct combination of tools/libraries. Dima -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Re: SOGo upgrade issue
On 06/13/2015 05:02 PM, Steve Ankeny wrote: . . . doing a bit of research . . . Others have had this error in the past. The following looks interesting. Samba: subprocess post-installation script returned error exit status 1 http://languor.us/samba-subprocess-post-installation-script-returned-error-exit-status-1 The suggestion above was to create a blank smb.conf in /etc/samba, then purge and reinstall samba During the upgrade, it suggested I keep my current 'smb.conf' I currently have the 'dcerpc' lines commented. Perhaps, I should uncomment those since they call the OpenChange and 'mapiproxy' functions? I inserted the 'dcerpc' comments as I was unable to login after a reboot of my 'samba-ad-dc,' and the problem was perceived to be the calls to a 'broken' OpenChange (which applies to OpenChange before this upgrade) Using a blank 'smb.conf' might not find my domain parameters to complete the configuration. If I purge my 'samba' db, will it delete all my user and machine accounts? That's a worry! Another suggestion might be to install an upgrade between my current 'samba' file and the Inverse package. I've been concerned about the installed version since before starting this upgrade to Samba 4.1.18 Are there any suggestions? Has anyone else ran into this situation? Should I ask the Samba list? On 06/13/2015 12:01 PM, Steve Ankeny wrote: Problems seem to start here . . . dpkg: error processing package samba (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of winbind: winbind depends on samba (= 2:4.1.18+dfsg-3~inverse1); however: Package samba is not configured yet. I asked the Samba mailing list, and they suggested the problem was the differences between the Ubuntu and Inverse packages. They suggested I change the installed status and attempt to force installation. That failed, however, and now I wonder where to go from here? Is 'winbind' actually needed for my installation? It is not running on my Samba-AD-DC adam@sogo:~$ sudo initctl list | egrep 'samba|smb|mnb|winbind' winbind stop/waiting smbd stop/waiting reload-smbd stop/waiting samba-ad-dc start/running, process 807 here are the packages installed on my server adam@sogo:~$ sudo dpkg-query -l | egrep 'samba|smb|nmb|winbind' ii libnss-winbind:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii libpam-winbind:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii libsmbclient:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii libwbclient0:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii python-samba 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba-common 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba-common-bin 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba-dev 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba-dsdb-modules 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba-libs:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba-vfs-modules 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii smbclient 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii winbind 2:4.1.6+dfsg-1ubuntu2.14.04.7 Since the suggestion above is to purge Samba, it would be better to purge 'winbind' instead. The error involves the post-install script which the Samba mailing list considers the problem. Is there a source for the Samba 2:4.1.18+dfsg packages with a different post-install script? Or, will purging the 'winbind' packages resolve my issue with upgrading my Samba-AD-DC installation? Any suggestions? thx -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Re: SOGo upgrade issue
On 06/19/2015 01:35 PM, Steve Ankeny wrote: On 06/13/2015 05:02 PM, Steve Ankeny wrote: . . . doing a bit of research . . . Others have had this error in the past. The following looks interesting. Samba: subprocess post-installation script returned error exit status 1 http://languor.us/samba-subprocess-post-installation-script-returned-error-exit-status-1 The suggestion above was to create a blank smb.conf in /etc/samba, then purge and reinstall samba During the upgrade, it suggested I keep my current 'smb.conf' I currently have the 'dcerpc' lines commented. Perhaps, I should uncomment those since they call the OpenChange and 'mapiproxy' functions? I inserted the 'dcerpc' comments as I was unable to login after a reboot of my 'samba-ad-dc,' and the problem was perceived to be the calls to a 'broken' OpenChange (which applies to OpenChange before this upgrade) Using a blank 'smb.conf' might not find my domain parameters to complete the configuration. If I purge my 'samba' db, will it delete all my user and machine accounts? That's a worry! Another suggestion might be to install an upgrade between my current 'samba' file and the Inverse package. I've been concerned about the installed version since before starting this upgrade to Samba 4.1.18 Are there any suggestions? Has anyone else ran into this situation? Should I ask the Samba list? On 06/13/2015 12:01 PM, Steve Ankeny wrote: Problems seem to start here . . . dpkg: error processing package samba (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of winbind: winbind depends on samba (= 2:4.1.18+dfsg-3~inverse1); however: Package samba is not configured yet. I asked the Samba mailing list, and they suggested the problem was the differences between the Ubuntu and Inverse packages. They suggested I change the installed status and attempt to force installation. That failed, however, and now I wonder where to go from here? Is 'winbind' actually needed for my installation? It is not running on my Samba-AD-DC adam@sogo:~$ sudo initctl list | egrep 'samba|smb|mnb|winbind' winbind stop/waiting smbd stop/waiting reload-smbd stop/waiting samba-ad-dc start/running, process 807 here are the packages installed on my server adam@sogo:~$ sudo dpkg-query -l | egrep 'samba|smb|nmb|winbind' ii libnss-winbind:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii libpam-winbind:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii libsmbclient:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii libwbclient0:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii python-samba 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba-common 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba-common-bin 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba-dev 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba-dsdb-modules 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba-libs:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii samba-vfs-modules 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii smbclient 2:4.1.6+dfsg-1ubuntu2.14.04.7 ii winbind 2:4.1.6+dfsg-1ubuntu2.14.04.7 Since the suggestion above is to purge Samba, it would be better to purge 'winbind' instead. The error involves the post-install script which the Samba mailing list considers the problem. Is there a source for the Samba 2:4.1.18+dfsg packages with a different post-install script? Or, will purging the 'winbind' packages resolve my issue with upgrading my Samba-AD-DC installation? Any suggestions? thx Rowland Penny recreated my problem in a VM (similar to my setup) here's the content of his e-mail -- OK, there appears to be something wrong with the inverse samba packages, I created a VM, installed latest Ubuntu 14.04 server, updated this, installed samba: apt-get install samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient winbind python-samba libnss-winbind libpam-winbind libsmbclient libwbclient0 didn't do anything else except added: deb http://inverse.ca/ubuntu-nightly trusty trusty To /etc/apt/sources.list ran 'apt-get update' and then 'apt-get upgrade' This lead to: The following packages have been kept back: libldb-dev libldb1 libnss-winbind libpam-winbind libsmbclient libwbclient0 linux-generic-lts-utopic linux-headers-generic-lts-utopic linux-image-generic-lts-utopic python-ldb python-samba samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient winbind The following packages will be upgraded: libparse-pidl-perl libtalloc-dev libtalloc2 libtdb-dev libtdb1 libtevent0 python-talloc python-tdb tdb-tools 9 to upgrade, 0 to newly install, 0 to remove and 20 not to upgrade. Need to get 468 kB of archives. After this operation, 253 kB of additional disk space will be used. Do you want to continue? [Y/n] y Installed the packages and then ran 'apt-get update' and then 'apt-get upgrade' again
