Dear mentors,

I am looking for a sponsor for my package "pyment":

 * Package name    : pyment
   Version         : 0.3.4+ds-1
   Upstream Author : https://github.com/dadadel/pyment/issues
 * URL             : https://github.com/dadadel/pyment
 * License         : GPL-3, BSD-3-Clause or GPL-2+
 * Vcs             : https://salsa.debian.org/debian/pyment
   Section         : utils

The source builds the following binary packages:

  pyment - generate/convert the docstrings from code signature

To access further information about this package, please visit the following URL:

https://mentors.debian.net/package/pyment/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/p/pyment/pyment_0.3.4+ds-1.dsc


https://salsa.debian.org/nilsonfsilva/pyment

Note:


I made a manual that was sent

https://github.com/dadadel/pyment/pull/122


Changes for the initial release:

 pyment (0.3.4+ds-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #876813)

Regards,
--
  Josenilson Ferreira da SIlva

Hi Nilson,

I see that you maintain python-dirq as part of the Debian Python Team.
Is there any good reason that you do not make this a team-maintained package as well?
I would prefer sponsoring a team-maintained package.

Thanks,
Bastian

Am 15.05.22 um 15:30 schrieb Nilson Silva:

Then please move the git repo to https://salsa.debian.org/python-team/packages/pyment
(or create a new one if you cannot move), reference that repo in d/control's Vcs fields
and change the Maintainer/Uploaders according to the team's policy.

Am 15.05.22 um 17:43 schrieb Nilson Silva:

Okay, I created the Python Team repo for you and invited you. You should request joining the team to get the access
rights for all team-maintained Python packages: https://debian-python.readthedocs.io/en/latest/dpmt-policy.html

Please change d/copyright's Files-Excluded to the whole doc/sphinx/html directory.
Please force push the upstream branch, rebase debian/master on it and then force push debian/master.

Why don't you build the documentation? It should be included as separate binary package.
Please see the dh_make python template on how to build it without using the Makefile.

I have slightly changed d/copyright and d/watch in git. Please pull the changes.

When you have updated the package please untag moreinfo.

Am 21.05.22 um 14:21 schrieb Nilson Silva:

See an example in source package cbor2 that builds binary package python-cbor2-doc.
Look at d/control, d/rules, and d/python-cbor2-doc.* files.
This uses the template-generated source almost untouched.

Am 25.05.22 um 23:42 schrieb Nilson Silva:

Keep it as-is.

I have correected the team repo. You had the debian/ dir in the upstream branch commit and one upstream file was
touched. I do not know why the CI in your user namespace passed.
There are examples in the sources that do not show up in the package. I have added them.

I am uploading this. For future python team packages, please hand in the RFS as topic change in the team's IRC.

Hi!

As the package has already been accepted.
I have already updated the salsa repository with the new changelog entry for unstable. I created the new tag and pushed it;

But it is not passing the CI/CD test.

It is saying that this file has been modified.
source_dir/doc/sphinx/source/pyment.rst.


But don't mess with anything. So much so that in my repository it is passing normally.

https://salsa.debian.org/nilsonfsilva/pyment/-/commit/8e784390ef3c4d7a0cc5e3e7808419003a128799/pipelines?ref=debian%2Fmaster

I didn't understand this one.
If you can explain, thank you.

.

Thanks!

I decided

Deleted the branches and made a new push.

Just go up foul to unstable.

Thanks!

Hi Nilson,

This is not at all the idea of collaboration via git. You now do not have a version that matches the published archive
version. Please do not do such things! CI may pass or not. It is not the idea to have the Salsa CI passing all the time
but to have a working copy that 1) represents the archive and 2) makes it easier for people to contribute without being
the uploader.

So, please recover the old version.

Thanks,
Bastian

Am 06.06.22 um 06:23 schrieb Nilson Silva:

This is the previous version.

Before making a push, I made a pull. because you had created a debian tag.
the remote branch was a commit ahead of me.

after I made a pull,
I made the new entry in the changlog and then I made the last commit. then I pushed again.
as it was not passing the CI/CD test I did a force.

If I have to go back to the previous state, could you tell me how to do it?

I thought in my ignorance, that as I had made a pull before there would be no problem.

forgive
thanks!