[Kolab-devel] Kolab 16 for Debian

[Daniel Hoffend]

Hi all

I still live :-) (even with very little free time). But I managed to spin up new kolab VM last night to give kolab 16.1 a try, especially because a good friend wants to migrate to kolab. My production still runs on 3.4 without flaws. Sure an upgrade from my debian7 installation to 8 and from kolab 3.4 to 16.1 is something that im looking into as well. But that requires lots of testing to be confident with.

I found stumpled already across the class not found but of sabredav which results of a wrong autoload_psr4.php in roundcubemail package.  It that should be easy to fix/patch it's only a single wrong line. Maybe the composer run during the package build injects a wrong path. Who knows. I'll try to push it to obs once I've check my environment

I also see some couple error 500 in the kolab_files plugin after a minute idle or so. I'm still trying to find time to dig out those small things.

The next thing I stumpled across was the missing chwala MySQL tables but that's likely because chwala is completely missing in setup-kolab

I know I'm out of the loop. What's the correct way to fix package bugs nowadays? Send patch requests to kolab16 in obs or winterfell or both or what?

I'll try to dig out some free time which will be hard but I'll try to give it a few spins.

-- 
Best regards
Daniel Hoffend

> Am 25.11.2016 um 08:57 schrieb hede <kolab983 at der-he.de>:
> 
> Am Thu, 24 Nov 2016 22:33:05 +0100 schrieb Timotheus Pokorra <timotheus at pokorra.de>:
> 
>> here is the log from the meeting.
> 
> Thanks for the log. 
> 
>> Thanks to everyone who showed up.
>> Those who were not online were sadly missed...
> 
> Sorry, I missed it. 
> 
> I even had some prepared questions. Nevermind. Hopefully there will be some KS guy next time. 
> 
> Hence I would like to share some comments here: 
> 
> With packaging php-sabre-* I tried using composer, like the kolab-sources and the rpm do. For me it didn't work this way out of the box so I tried some other (simple) approach which works. I've never done php packaging in before and do not know all those autoloading stuff and I'm pretty sure I'm still missing some parts (I didn't spent too much time to it). So maybe KS maintainers and most certainly a real debian maintainer will eat it alive, if they risk a closer look at it. Feel free to do so. :-)
> 
> Regarding "getting rid of PHP": Why? PHP sounds out-of-vogue in modern times, principally because it was brought into disrepute. I don't think the language as such is bad. Speaking of disrepute: JavaScript (esp. Server-side) has already replaced php in this respect - I think. ;-)
> 
> Regarding "email reminder for appointments": I don't think this should be part of the client. I consider Roundcube as one of many kolab clients. What if I'm creating such an appointment with some other kolab client? Then roundcube must be run for that user even if he's not using it.
> Unfortunately there's no server-side part parsing appointments right now, isn't it? (At least if there is one, I'm not actively using it.)
> 
> regards
> hede
> 
> 
> and btw: I'm using kolab winterfell on debian lxc vm with systemd. What a pity I missed that meeting, that closely fits in there. :-D
> (((It's only some little 4 users family with no hard stability requirements a commercial company has. Nevertheless, kolab turns out to be quite stable. More than I thought of in before. At least my last snapshot which I'm still using ;-). I'm going to give kolab 16.1 a chance for my stable service while continue using continuous winterfell for testing.)))
> _______________________________________________
> devel mailing list
> devel at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/devel