Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11338
| From | lluvia@autistici.org |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: upstream release of unreleased package |
| Date | 2019-02-22 20:20 +0100 |
| Message-ID | <xuowy-6vj-3@gated-at.bofh.it> (permalink) |
| References | (6 earlier) <xu3V7-2JZ-7@gated-at.bofh.it> <xu4xQ-2VZ-11@gated-at.bofh.it> <xu6zD-4kY-7@gated-at.bofh.it> <xu7m1-4zS-3@gated-at.bofh.it> <xujZU-3OR-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 2019-02-22 14:29, Dmitry Shachnev wrote: > The last commits in upstream and pristine-tar branches look fine, no > need to revert them. > > Just revert the last commit in debian/master (as you did above), then > merge upstream/0.3.8 tag into debian/master and update the changelog. > It should be enough. Ok. These are the commands I would use: $ gbp clone git@salsa.debian.org:python-team/applications/visualequation.git $ cd visualequation/ (debian/master)]$ git revert HEAD [debian/master 7cc491f] Revert "Adding patches" 3 files changed, 524 deletions(-) delete mode 100644 debian/patches/0001-Imported-Upstream-version-0.3.8.patch delete mode 100644 debian/patches/0002-modifying-d-changelog-for-new-upstream-release.patch delete mode 100644 debian/patches/series (debian/master)]$ git merge upstream/0.3.8 Merge made by the 'recursive' strategy. README.md | 12 ++++-- [...] 10 files changed, 167 insertions(+), 51 deletions(-) (debian/master)]$ dch -v 0.3.8-1 (debian/master)]$ git add debian/changelog (debian/master)]$ git commit -m "Updating debian/changelog to 0.3.8-1" [debian/master b5496f5] Updating debian/changelog to 0.3.8-1 1 file changed, 3 insertions(+), 2 deletions(-) (debian/master)]$ git push origin : --tags Best regards, Daniel
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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