Re: [Kolab-devel] Kolab 16 for Debian
hede <[email protected]> Tue, 29 Nov 2016 21:42:50 +0100
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Organization | der-he.de |
| Message-ID | <[email protected]> |
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