Groups > linux.debian.maint.python > #11323

Re: upstream release of unreleased package

From	Andrey Rahmatullin <wrar@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: upstream release of unreleased package
Date	2019-02-15 07:20 +0100
Message-ID	<xrF0R-8sk-1@gated-at.bofh.it> (permalink)
References	(4 earlier) <xpYhj-2eV-1@gated-at.bofh.it> <xq43o-5N6-17@gated-at.bofh.it> <xqLBo-7To-13@gated-at.bofh.it> <xqLL3-7WG-9@gated-at.bofh.it> <xrx3k-3rn-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Thu, Feb 14, 2019 at 09:43:19PM +0000, lluvia@autistici.org wrote:
> I changed the strategy to git revert and now I am able to build the package
> with the following commands:
> 
> gbp clone git@salsa.debian.org:python-team/applications/visualequation.git
> cd visualequation/
> uscan
> git revert HEAD # "Revert last commit due to human error"
> dch -v 0.3.8-1
> dpkg-source --commit
>  -> Enter the desired patch name: 0001-Imported-Upstream-version-0.3.8.patch
> git add debian/changelog debian/patches/*
> git commit -m "Fixing upstream version 0.3.8"
> debuild -us -uc
> 
> Do you find it correct/appropriate?
No, you should not add the new upstream version as a patch. Especially as
you already have the tarball imported. What is the repo missing is merging
upstream/0.3.8 into the master branch. If you imported the tarball with
gbp import-orig it would have happened automatically.

-- 
WBR, wRAR

Thread

upstream release of unreleased package lluvia@autistici.org - 2019-02-10 02:20 +0100
  Re: upstream release of unreleased package Brian May <bam@debian.org> - 2019-02-10 02:40 +0100
    Re: upstream release of unreleased package lluvia@autistici.org - 2019-02-10 14:30 +0100
      Re: upstream release of unreleased package Andrey Rahmatullin <wrar@debian.org> - 2019-02-10 14:40 +0100
        Re: upstream release of unreleased package lluvia@autistici.org - 2019-02-10 15:30 +0100
          Re: upstream release of unreleased package Brian May <bam@debian.org> - 2019-02-10 21:40 +0100
            Re: upstream release of unreleased package daniel <lluvia@autistici.org> - 2019-02-11 11:50 +0100
            Re: upstream release of unreleased package lluvia@autistici.org - 2019-02-12 20:10 +0100
              Re: upstream release of unreleased package Andrey Rahmatullin <wrar@debian.org> - 2019-02-12 20:20 +0100
                Re: upstream release of unreleased package lluvia@autistici.org - 2019-02-14 22:50 +0100
                Re: upstream release of unreleased package lluvia@autistici.org - 2019-02-14 23:20 +0100
                Re: upstream release of unreleased package Andrey Rahmatullin <wrar@debian.org> - 2019-02-15 07:20 +0100
                Re: upstream release of unreleased package Brian May <bam@debian.org> - 2019-02-17 09:30 +0100
                Re: upstream release of unreleased package lluvia@autistici.org - 2019-02-17 13:00 +0100
                Re: upstream release of unreleased package lluvia@autistici.org - 2019-02-21 22:20 +0100
                Re: upstream release of unreleased package Dmitry Shachnev <mitya57@debian.org> - 2019-02-21 23:00 +0100
                Re: upstream release of unreleased package lluvia@autistici.org - 2019-02-22 01:10 +0100
                Re: upstream release of unreleased package lluvia@autistici.org - 2019-02-22 02:00 +0100
                Re: upstream release of unreleased package Dmitry Shachnev <mitya57@debian.org> - 2019-02-22 15:30 +0100
                Re: upstream release of unreleased package lluvia@autistici.org - 2019-02-22 20:20 +0100
                Re: upstream release of unreleased package Dmitry Shachnev <mitya57@debian.org> - 2019-02-22 21:30 +0100

csiph-web