hi,
On Wed, Mar 15, 2023 at 3:33 PM Shengjing Zhu wrote:
>
> On Wed, Mar 15, 2023 at 3:24 PM Bo YU wrote:
> > ```
>
> We just use `gbp dch`.
>
> Besides, a question for uploaders of golang-github-zyedidia-pty, do we
> really need this fork? Can you convince upstream to forward their
> patch to
On Wed, Mar 15, 2023 at 6:40 PM Shengjing Zhu wrote:
>
> On Wed, Mar 15, 2023 at 6:34 PM Bo YU wrote:
> [...]
> > From man manual[1], the `--upstream-vcs-tag` option should enable
> > upstream branch contains all upstream git history.
>
> Yes. You need add a new remote which points to upstream r
On Wed, Mar 15, 2023 at 6:34 PM Bo YU wrote:
[...]
> From man manual[1], the `--upstream-vcs-tag` option should enable
> upstream branch contains all upstream git history.
Yes. You need add a new remote which points to upstream repository,
and fetch tags from it.
Well, dh-make-golang does that
On Wed, Mar 15, 2023 at 5:59 PM Shengjing Zhu wrote:
>
> On Wed, Mar 15, 2023 at 5:55 PM Bo YU wrote:
> > How to understand this?
> > "“upstream” branch should contain upstream git history"
> >
> > But from my observation, both ways(upstream branch contains upstrream
> > git history
> > and it do
On Wed, Mar 15, 2023 at 5:55 PM Bo YU wrote:
> How to understand this?
> "“upstream” branch should contain upstream git history"
>
> But from my observation, both ways(upstream branch contains upstrream
> git history
> and it does not contain upstream git history) was accepted for go team.
Which
hi，
On Wed, Mar 15, 2023 at 3:33 PM Shengjing Zhu wrote:
>
> On Wed, Mar 15, 2023 at 3:24 PM Bo YU wrote:
> [...]
> > 4. git checkout upstream
> > 5. git merge v1.1.20
> > 6. git merge --continue
> > 7. git tag -a upstream/1.1.20
> > 8. git checkout debian/sid
> > 9. git merge upstream/1.1.20
>
hi，
On Wed, Mar 15, 2023 at 3:33 PM Shengjing Zhu wrote:
>
> On Wed, Mar 15, 2023 at 3:24 PM Bo YU wrote:
> [...]
> > 4. git checkout upstream
> > 5. git merge v1.1.20
> > 6. git merge --continue
> > 7. git tag -a upstream/1.1.20
> > 8. git checkout debian/sid
> > 9. git merge upstream/1.1.20
>
On Wed, Mar 15, 2023 at 3:24 PM Bo YU wrote:
[...]
> 4. git checkout upstream
> 5. git merge v1.1.20
> 6. git merge --continue
> 7. git tag -a upstream/1.1.20
> 8. git checkout debian/sid
> 9. git merge upstream/1.1.20
>
No. We use gbp. You can just use `gbp import-orig --uscan
--upstream-vcs-tag
Hi,
This is my the first time to upload package updated for go team. So
I seek for the help to confirm the workflow is right and avoid to
cause trouble for the package.
Here is the olang-github-zyedidia-pty that I want to upgrade it and
fix #1032265[0]. Below is my workflow to update it.
```
1.
