[Piuparts-devel] bullseye branch rename [was Re: piuparts.py and piuparts-analyze.py]

[Herbert Fortes]

On 7/10/19 12:49 PM, Holger Levsen wrote:
> On Tue, Jul 09, 2019 at 12:55:11PM -0300, Herbert Fortes wrote:
>> The fork has two bullseye branches. One is a mess and the other is clean
>> and I did a sync. The last commit - 27 May.
> 
> thanks for providing a clean branch!
> 
>> The name of the clean branch is 'bullseye_sync_clean'[0]. Please take a 
>> look when you have time for it.
>>
>>  - d.iteritems() -> iter(d.items()) Py 2 3 compatible
>>     https://www.python.org/dev/peps/pep-0469/
> 
> looks good to me, though as you rename some variables I'd like an ACK
> from Andreas as well.

Ok.

> 
>>  - Popen - universal_newlines=True. Py2, Py3 compatible
> 
> cherry-picked into the develop branch, thanks! \o/

:)

> 
>>  - Dir with files for Sphinx
> 
> please replace the existing files instead... (and adjust Makefile,
> d/control, etc as needed.)

I am changing piuparts.1.txt to something like that (Sphinx just for 
html files):

-NOTES
------
+.SH NOTES
 Output of commands run by piuparts is limited to three megabytes. To change this limit, the source code needs to be edited.
 Commands exceeding this limit will be aborted.
-
-SEE ALSO
---------
+.SH SEE ALSO
 *pbuilder*(1), *debootstrap*(8)
-

No tool needed to generate the manpage.

It is possible to see that the text wasn't changed. Just the title.
But I can not start a line with a dot - '.' - because the line will
not be showed by 'man ./piuparts.1'. Three paragraph will appear as
changed in a 'diff'. Unless you edit the file later to add a space
at the beginning of the line.

I did one file this afternoon. If that is ok I can do the same for
the other 3 files.


> 
>>  - obsolete_conffiles.mail file
> 
> cherry-picked into the develop branch, thanks! \o/

:)

> 
> I haven't deployed this changes yet, however.
> 
Ok.



Regards,
Herbert