[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1011018: marked as done (RFS: pyment/0.3.4+ds-1 [ITP] -- generate/convert the docstrings from code signature)



Your message dated Thu, 26 May 2022 02:21:02 +0200
with message-id <dda79209-7d6c-3483-5018-ec7237552568@debian.org>
and subject line Re: ENC: RFS: pyment/1.0-1 [ITP] -- generate/convert the docstrings from code signature (CONSIDER THIS)
has caused the Debian Bug report #1011018,
regarding RFS: pyment/0.3.4+ds-1 [ITP] -- generate/convert the docstrings from code signature
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1011018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011018
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

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


--- End Message ---
--- Begin Message ---
Am 25.05.22 um 23:42 schrieb Nilson Silva:
Below are the requirements you made earlier:

Following the pattern of the package you had suggested to me as an example, this three lintian remained:

X: python-pyment-doc: new-package-should-not-package-python2-module python-pyment-doc
X: python3-pyment: application-in-library-section python usr/bin/pyment
X: python3-pyment: library-package-name-for-application usr/bin/pyment

To remove the lintians would have to change the names of pyment and pymentt-doc and the pyment session. But I don't know if it would be correct. I preferred to wait for you to guide me first.

Keep it as-is.

Please change d/copyright's Files-Excluded to the whole doc/sphinx/html directory.
*done*.

Please force push the upstream branch, rebase debian/master on it and then force push debian/master.
**done*.*

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.

*done*.

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


When you have updated the package please untag moreinfo.
*done*.

I followed the repository with the changes.

https://salsa.debian.org/python-team/packages/pyment/-/tree/debian/master/
https://salsa.debian.org/nilsonfsilva/pyment

strangely in my repository the CI/CD test passes. In salsa Debian is giving error.

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.

--- End Message ---

Reply to: