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

2022-06-06 Thread 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!


From: Bastian Germann 
Sent: Monday, June 6, 2022 4:52:22 AM
To: Nilson Silva ; 1011...@bugs.debian.org 
<1011...@bugs.debian.org>
Subject: Re: Bug#1011018: marked as done (RFS: pyment/0.3.4+ds-1 [ITP] -- 
generate/convert the docstrings from code signature)

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:
> I decided Deleted the branches and made a new push. Just go up foul to 
> unstable. Thanks!
>
>
> 
> *De:* Nilson Silva 
> *Enviado:* segunda-feira, 6 de junho de 2022 00:30
> *Para:* Bastian Germann ; 1011...@bugs.debian.org 
> <1011...@bugs.debian.org>
> *Assunto:* RE: Bug#1011018: marked as done (RFS: pyment/0.3.4+ds-1 [ITP] -- 
> generate/convert the docstrings from code
> signature)
>
> 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!
>
>
> 
> *De:* Debian Bug Tracking System 
> *Enviado:* quarta-feira, 25 de maio de 2022 21:24
> *Para:* Bastian Germann 
> *Assunto:* 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 
> 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 ow...@bugs.debian.org
> immediately.)
>
>
> --
> 1011018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011018
> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011018>
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems



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

2022-06-06 Thread Bastian Germann

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:

I decided Deleted the branches and made a new push. Just go up foul to 
unstable. Thanks!



*De:* Nilson Silva 
*Enviado:* segunda-feira, 6 de junho de 2022 00:30
*Para:* Bastian Germann ; 1011...@bugs.debian.org 
<1011...@bugs.debian.org>
*Assunto:* RE: Bug#1011018: marked as done (RFS: pyment/0.3.4+ds-1 [ITP] -- generate/convert the docstrings from code 
signature)


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!



*De:* Debian Bug Tracking System 
*Enviado:* quarta-feira, 25 de maio de 2022 21:24
*Para:* Bastian Germann 
*Assunto:* 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 
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 ow...@bugs.debian.org
immediately.)


--
1011018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011018 
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011018>

Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems




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

2022-06-05 Thread Nilson Silva
I decided

Deleted the branches and made a new push.

Just go up foul to unstable.

Thanks!


De: Nilson Silva 
Enviado: segunda-feira, 6 de junho de 2022 00:30
Para: Bastian Germann ; 1011...@bugs.debian.org 
<1011...@bugs.debian.org>
Assunto: RE: Bug#1011018: marked as done (RFS: pyment/0.3.4+ds-1 [ITP] -- 
generate/convert the docstrings from code signature)



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.


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

2022-06-05 Thread Nilson Silva

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.


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

2022-05-25 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 02:21:02 +0200
with message-id 
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 ow...@bugs.debian.org
immediately.)


-- 
1011018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011018
Debian Bug Tracking System
Contact ow...@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 ---