Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: the nightly thread for Kopano Core 8.2.0

  1. #1
    Zarafa Testing
    Suyi's Avatar
    Join Date
    Jul 2008
    Location
    irc.freenode.com > #zarafa
    Posts
    839

    the nightly thread for Kopano Core 8.2.0

    Hi all,

    We notice some users are running the nightly builds and also actively provide feedback, which we highly appreciate!
    Therefore I would like to dedicate a specific thread for the people that are running the nightly builds.

    Please use this thread to report the issue that you are experiencing and we will do our up most best to solve it in a timely manner.
    Also we would like to take the opportunity to share which invasive changes have been planned for this release. Please understand that based on input, certain changes can be reverted.

    SSLv2 support is removed for platforms with OpenSSL v1.1 (concerns only Gentoo and Debian Experimental at this time) (KC-230) - customer config files will not be updated automatically and will lead to kopano-{server,gateway,ical} refusing to start.
    search in shared store (in review, not in master yet)
    LDAP configuration file locations have shuffled around a bit (KC-229) - only affects new installs, not upgrades
    Different default search filter (KC-218) - customer config files will not be updated automatically!
    Python 3 support (experimental) (KC-48, in review)
    PST importer (linux tool set -> KC-59)
    New gsoap version 2.8.35/36 gets shipped (KC-261)
    New libvmime 0.9.2 planned, pending crashtests/smoketests (KC-263)

    To view the changes that are made it into master, this is the branch that we use for the nightly builds, please head over to our or you can view the , which get periodically updated.
    To view a ticket, please use jira.kopano.io, you can sign up for an account and even watch a ticket

    Please use feedback[a]kopano.com if you have discovered a (potential) vulnerability or if you want to share something confidential which is related to an issue.
    You can access the packages via

    Feel free drop a comment if you have any questions regarding the nightly build.

    Cheers,
    -Suyi
    Looking for users to test our releases, interested? send me a PM

  2. #2
    Zarafa Testing
    Suyi's Avatar
    Join Date
    Jul 2008
    Location
    irc.freenode.com > #zarafa
    Posts
    839
    hi all,

    It seems that Apache segfault with the latest core packages ->

    keep you all posted regarding this issue.
    -Suyi
    Looking for users to test our releases, interested? send me a PM

  3. #3
    Zarafa Testing
    Suyi's Avatar
    Join Date
    Jul 2008
    Location
    irc.freenode.com > #zarafa
    Posts
    839
    Hi all,
    has been addressed and we have released a new build.
    -Suyi
    Looking for users to test our releases, interested? send me a PM

  4. #4

    [Deleted]

    Sorry, my question about any news concerning the z-push issue with php7 was answered in another threat.
    It will be addressed in z-push 2.3.4 ().
    thx,
    jacks
    Last edited by jackson5; 20-10-2016 at 11:16 AM.

  5. #5
    Junior Member
    Join Date
    Oct 2008
    Posts
    14
    So i took a quick glance today and actually there was only ONE issue left to make z-push work on 16.04 with php7 for me.
    I merged the 804 branch into develop and applied a very very basic fix to the PHPWrapper class

    As retmapimessage is never used - i guess it's actually meant to be removed completely - this "fix" is kind of dirty, but it's enough for not having php7 throw an exception.
    It fixes z-push with php7 at least from what I am seeing at a first glance.
    So my mobile is fully synced again, which is a BIG relieve for me .
    Last edited by reichi; 25-10-2016 at 09:41 AM.

  6. #6
    Zarafa Testing
    Suyi's Avatar
    Join Date
    Jul 2008
    Location
    irc.freenode.com > #zarafa
    Posts
    839
    Thanks for your "patch", maybe Jackson5 can finally get his mobiles to work too
    -Suyi
    Looking for users to test our releases, interested? send me a PM

  7. #7
    Hi,

    thanks for the fix. That was the call-by-reference warning I cited earlier.

    Unfortuntately, I am still not able to resync with the git developer branch.
    After a full clear on the z-push-server and resync, I get log entries like

    or

    Whats up with reason '4'?

    thx,
    jacks
    Last edited by jackson5; 26-10-2016 at 06:12 AM.

  8. #8
    Senior Member
    Join Date
    Sep 2007
    Location
    Aka SebastianBrasil
    Posts
    1,467
    Reason four is a semantic error, meaning that z-push classifies the email as broken. Could you enable debug or wbxml log level and see if there is further output?
    Last edited by fbartels; 26-10-2016 at 01:14 PM.

  9. #9
    Junior Member
    Join Date
    Aug 2016
    Posts
    6
    After getting the latest ZP-804 branch from git, I was able to successfully sync on my iphone (so nice to be able to do this!).

    I get the reason 4 as well. I will enable debug as well and see if it gives further output.

  10. #10
    Sure,

    nothing that does help me.
    I sent the detailed logs to .

    Oh, and after the resynchronization attempt, the tasks on the mobile client were garbled up - lotsa new entries with a subject of "0".
    According to kopano-fsck, all of the entries on the server are still correct.

    thx,
    jacks
    Last edited by jackson5; 27-10-2016 at 05:36 AM.

Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 16
    Last Post: 31-10-2016, 12:30 PM
  2. Replies: 22
    Last Post: 20-10-2016, 10:46 AM
  3. Kopano Core 8.2.0.109 & Ubuntu 16.04
    By forager in forum Beta Feedback
    Replies: 8
    Last Post: 13-10-2016, 04:42 PM
  4. Replies: 1
    Last Post: 13-10-2016, 10:05 AM
  5. Replies: 4
    Last Post: 03-08-2016, 08:59 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •