Bug#999544: Update golang-v2ray-core to new upstream
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 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 > > GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2
Bug#999544: Update golang-v2ray-core to new upstream
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 GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2
Bug#999544: Update golang-v2ray-core to new upstream
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. Cheers, Roger On Fri, Nov 12, 2021 at 5:22 PM Aloïs Micard wrote: > > Hello there, I hope you are doing fine! > > I don't know if you recall me, but we've worked a bit together > on Go packages in the past (al...@micard.lu). :) > > I have a request regarding golang-v2ray-core: > > The package will be removed on 01-12-21 because of error with Go 1.17 > which is now the defaults in the archive. > > I wanted to update golang-v2ray-core to latest upstream (4.43.0) and backport > the commit > https://github.com/v2fly/v2ray-core/commit/77b88171d6bd837b76a5ad6e6b23689391530ed6 > in order to get the package to build with Go 1.17 and allow transition to > testing of > golang-github-lucas-clemente-quic-go which is needed to prevent Syncthing > from being > RM of testing. > > The thing is: the Salsa repository for golang-v2ray-core doesn't have > upstream branch, > therefore I'm unable to import new upstream via gbp: > > > ``` > 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. > ``` > > Have you forgot to push upstream branch to Salsa? Or are you using a special > workflow? > > If you can either import latest upstream or push missing upstream branch it > would > be greatly helpful. > > Many thanks. > > Cheers, > > -- > Aloïs Micard > > GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2
Bug#999544: Update golang-v2ray-core to new upstream
Hello there, I hope you are doing fine! I don't know if you recall me, but we've worked a bit together on Go packages in the past (al...@micard.lu). :) I have a request regarding golang-v2ray-core: The package will be removed on 01-12-21 because of error with Go 1.17 which is now the defaults in the archive. I wanted to update golang-v2ray-core to latest upstream (4.43.0) and backport the commit https://github.com/v2fly/v2ray-core/commit/77b88171d6bd837b76a5ad6e6b23689391530ed6 in order to get the package to build with Go 1.17 and allow transition to testing of golang-github-lucas-clemente-quic-go which is needed to prevent Syncthing from being RM of testing. The thing is: the Salsa repository for golang-v2ray-core doesn't have upstream branch, therefore I'm unable to import new upstream via gbp: ``` 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. ``` Have you forgot to push upstream branch to Salsa? Or are you using a special workflow? If you can either import latest upstream or push missing upstream branch it would be greatly helpful. Many thanks. Cheers, -- Aloïs Micard GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2 OpenPGP_signature Description: OpenPGP digital signature
