On Sun, Jul 8, 2018 at 9:09 AM Tong Sun wrote: > On Sun, Jul 8, 2018 at 2:30 AM Geert Stappers wrote:
>> . . . >> `gbp clone URL` is only intended for URL which has gbp information. >> >> Direction to go: Take a detour >> >> Do `gbp clone EXISTING_GBP_REPO` and check which branches it has. >> Then work on a "fresh git repo" where you add branches. > > Thanks for your input Groeten, but I'm afraid that your workflow is still > pre-gbp, i.e., you are still doing steps manually that gbp is already doing > it for us. Let me quota again what gbp can automatically do: > > > If upstream doesn't build upstream tarballs, or you don't care about > > them, the simplest way is to clone upstream's repository and create a > > separate packaging branch in there. You will not need gbp import-orig at > > all with this workflow. gbp buildpackage will handle creating the upstream > > tarballs needed for the Debian source package. > > I.e., it will do it, provided that I can find the correct way of doing it... I'm sorry Geert, Not only I copied your name wrong, but my interpretation about the above paragraph is totally wrong too. You are totally right and I was totally wrong. I don't know what possessed me, turning me into a total dick. Sorry about that and thanks again for your kind help
