Dear Aloïs, Personally I don't use upstream branch, and I don't think it's necessary. But if it meet your workflow, I don't have objectection to add this branch.
My workflow is simple: - use "uscan -dd" to download latest or specified upstream tarball - merge debian (or master) branch with upstream tag. Maybe removing some files in "excluded" of d/copyright is necessary. - use gbp command to build Hope it helps. Cheers, Roger On Sun, Nov 14, 2021 at 5:49 PM Aloïs Micard <creekor...@debian.org> wrote: > > Hello Roger, > > On 14/11/2021 09:11, Roger Shimizu wrote: > > Dear Aloïs, > > > > Thanks for your work to go packages! > > Sorry I don't have time lately. So if you can update the packages and > > fix the RC bugs, it'd be appreciated. > > > > Sure thing. The only thing is: have you push the upstream branch on the > repository? It looks like there's none and therefore `gbp import-orig --uscan` > is failing: > > ``` > creekorful@debuild:~/code/golang-v2ray-core$ gbp import-orig --uscan > gbp:error: Repository does not have branch 'upstream' for upstream sources. > If there is none see > file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT > on howto create it otherwise use --upstream-branch to specify it. > ``` > > It could be really helpful if you either push upstream branch or explain me > which workflow you are using. > > > Cheers, > > Roger > > > > Cheers, > > -- > Aloïs Micard <creekor...@debian.org> > > GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2
