[pkg-bacula-devel] Contribution

[Carsten Leonhardt]

Mario Pranjic <mario at pranjic.no> writes:

> On 9/30/20 10:09 PM, Carsten Leonhardt wrote:
>> Hi Mario,
>>
>> I've created an empty git repository for bacula-libs3, see
>> https://salsa.debian.org/bacula-team/bacula-libs3 and gave you access.
>>
>> If you already have something to share, you can put it there. If you
>> need a helping hand, just ask.
>>
>> Regards,
>>
>> Carsten
>
>
> Hi Carsten,
>
> Thank you very much!
>
> Still not done with wrestling with PATH changing in src. Working on it...
>
> As for repository, what are the rules? To put initial src as commit in
> master first? To open PR for changes?

After having read a recent discussion on the debian-devel list, I'd
start with putting the clean upstream sources into branch
"upstream/latest", branch off "debian/latest" from there and add Debian
specifics there (i.e. the debian/ subdirectory).

Details are here, not yet updated after the recent discussion though:

https://dep-team.pages.debian.net/deps/dep14/

(Out of respect to people who feel that "master" is not a good word to
use, it will probably be replaced it with "latest" or "sid" in that draft)


This command might do all that work (I haven't used that yet for an initial import):

gbp import-orig --upstream-branch=upstream/latest --debian-branch=debian/latest --pristine-tar <tarball>


Usually we create new branches for changes that we feel aren't good
enough for inclusion in the packages yet. Once we think they are good,
we merge them to the main branch.

Regards,

Carsten