Re: [Kolab-devel] Kolab 16 for Debian

Hi hede

thanks for your answer, but I was more concerned about Jereons Call to
get Kolab:16 for Debian tested and fixed. Therefore I was looking around
what has changed in the last half year.

In the end there hasn't changed much to be fair :-) Especially not the
laggy OBS :-) I really haven't missed it.

In the mean time I've already fixed couple packages in Kolab:16 and
Winterfell which are already pushed through and live. At least a default
Debian Installation should now go through without any major drawbacks.
But there's still some packages and components missing to be feature
complete compared to the Centos Release.


--
Regards
Daniel



On 2016-11-29 21:42, hede wrote:
> Am Sun, 27 Nov 2016 09:30:37 +0100 schrieb Daniel Hoffend <[email protected]>:
> 
> > What's the correct way to fix package bugs nowadays? Send patch requests to kolab16 in obs or winterfell or both or what?
> 
> Good question. 
> 
> AFAIK there are 2 ways: 
> 
> 1:
>  - branch/fork the corresponding project/package in OBS[1]
>  - fix errors in your personal home project
>  - file a submit request to the upstream maintainer (within obs)
>  - the package maintainer will hopefully include your work
> 
>  [1] https://obs.kolabsys.com/
> 
> 2: Submit a patch in fabricator[2] 
>  - create a task
>  - add your patch/diff to the task
>  - the upstream developer will hopefully include your work
> 
>  [2] https://git.kolab.org/
> 
> With way 1 you get your working packages in [3] (at least for AMD64). Incredibly handy for direct inclusion within some local kolab installation. With way 2 you'll better reach upstream developers. 
> 
> [3] http://obs.kolabsys.com:82/Kolab:/
> 
> regards
> hede
> _______________________________________________
> devel mailing list
> [email protected]
> https://lists.kolab.org/mailman/listinfo/devel