Hi Guido,
On 08/07/18 21:53, Guido Günther wrote:
[...]
>> - gbp pull --ignore-branch
>> - gbp buildpackage --git-ignore-branch --git-export-dir=${WORKING_DIR} -us
>> -uc
>>
>> All seems to work fine (actually it does work), but we found that gbp is not
>> using the `pristine-tar` branch for building the orig tarball. Reading the
>> doc,
>> I can see the recommended way is using gbp clone but here we don't have any
>> control over how Gitlab does the cloning. Is there a gbp friendly command to
>> track the remote pristine-tar branch after the repo was cloned using just
>> `git
>> clone`?
>
> In gitlab-ci this would be somthing like
>
> script:
> - git fetch origin pristine-tar
> - git branch pristine-tar FETCH_HEAD
>
> or did I misunderstand your question?Yeah, that could work. Oh, rereading my previous email I see that I didn't explain the whole scenario correctly, sorry. We are trying to write a pipeline that could be applied to any repository i.e. there are repositories with pristine-tar and there are other repositories without it. So as far I can see there isn't an automagically way for telling gbp track the origin pristine-tar if it's present. One of the goal if to KIS as possible and writing a detection first if pristine-tar is enabled (maybe using gbp config) and then fetching the remote it doesn't sound very simple. If I write a patch with a new option like --git-force-track-remote-pristine-tar or something like that, are you willing to merge it? Thanks, -- TiN
signature.asc
Description: OpenPGP digital signature
_______________________________________________ git-buildpackage mailing list [email protected] http://lists.sigxcpu.org/mailman/listinfo/git-buildpackage
