Re: upstream release of unreleased package

[Brian May]

llu...@autistici.org writes:

> 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.

Ignore that. That is just the git server providing helpful information
that isn't really appropriate here.
-- 
Brian May 

upstream release of unreleased package

[lluvia]

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 g...@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