Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11308
| From | lluvia@autistici.org |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | upstream release of unreleased package |
| Date | 2019-02-10 02:20 +0100 |
| Message-ID | <xpLWO-2Vv-3@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Dear all,
I followed the steps indicated in
https://wiki.debian.org/Python/GitPackaging
for a new upstream release of the unreleased
https://salsa.debian.org/python-team/applications/visualequation
My intention is to check that this new version can be packaged correctly
and then ask for sponsorship.
Things that I did that were not explicitly written:
* git add and git commit debian/changelog
* git add and git commit debian/patches/*
Then, I did git push. It was correct? What should I do next? The output
(see below) suggest to create a merge request.
Thanks in advance.
Daniel
$ git push origin : --tags
Counting objects: 27, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (26/26), done.
Writing objects: 100% (27/27), 13.16 KiB | 0 bytes/s, done.
Total 27 (delta 16), reused 0 (delta 0)
remote:
remote: To create a merge request for pristine-tar, visit:
remote:
https://salsa.debian.org/python-team/applications/visualequation/merge_requests/new?merge_request%5Bsource_branch%5D=pristine-tar
remote:
remote: To create a merge request for upstream, visit:
remote:
https://salsa.debian.org/python-team/applications/visualequation/merge_requests/new?merge_request%5Bsource_branch%5D=upstream
remote:
To git@salsa.debian.org:python-team/applications/visualequation.git
ca7f63e..8b678bd debian/master -> debian/master
718faf5..8687008 pristine-tar -> pristine-tar
17e6b53..f6d5e2e upstream -> upstream
* [new tag] upstream/0.3.8 -> upstream/0.3.8
Back to linux.debian.maint.python | Previous | Next — 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