Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11325
| From | Brian May <bam@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: upstream release of unreleased package |
| Date | 2019-02-17 09:30 +0100 |
| Message-ID | <xspZL-3l8-1@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <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> <xrF0R-8sk-1@gated-at.bofh.it> |
| Organization | Debian |
Andrey Rahmatullin <wrar@debian.org> writes: > 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. That would probably explain why I had problems. I didn't check that the latest upstream branch correctly matched the source without patches, and generated the orig.tar.gz file based on the lastest upstream branch (which wasn't tagged correctly either). It is possible in this case no patches are required. Not sure I entirely understand the situation however. "for a new upstream release of the unreleased" - has it been released upstream or not? -- Brian May <bam@debian.org>
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