Re: pylint3 reverse dependencies.

[Joseph Herlant]

Hi Peter,


On Tue, Oct 1, 2019 at 4:22 PM peter green  wrote:
>
> pylint3 is now a cruft package, however it still has a fair few reverse 
> dependencies, from
> https://ftp-master.debian.org/users/dktrkranz/NBS
>
> Are there plans to deal with this centrally or should bugs be filed against 
> all the reverse dependencies.

Yes this is a known issue and we are currently waiting for an upload
of dh-python to avoid automatic replacement of pylint by pylint3 when
on python3 before pushing those changes further.
There were several discussions already on the subject on the
debian-python list but as long as dh-python is still automatically
replacing pylint by pylint3 there's not much the reverse deps can
really do afaik.


Joseph

Re: dh-python and pylint

[Joseph Herlant]

Hi!

> thanks a lot, but what about backports. On backports we still need this 
> mapping.
Aren't the backports built using the dh-python version of the platform
they are ported to? In this case it shouldn't really matter right?

I see that Ubuntu released a new dh-python with this exact fix. It
seems to work fine.
Right now the packages we push with the pylint3 dependency renamed
still end up with pylint3 as dependency, so should we hold off on the
auto-pylint transition until
https://salsa.debian.org/python-team/tools/dh-python/merge_requests/9
is merged and release? Or is an automatic rebuild of the packages
having that problem planned when that fix in dh-python is release?

Thanks,
Joseph

Re: py2-rm: a few leaf packages to work on

[Joseph Herlant]

I'll try to take care of the asciidoc* ones over the weekend even if
there's no official release of asciidoc with python3 support yet (and
upstream advises to use asciidoctor instead).

Joseph

Re: Side effect of dropping python2 with -doc packages

[Joseph Herlant]

Hi Andrey,

Thanks for your reply.

On Tue, Aug 13, 2019 at 10:40 AM Andrey Rahmatullin  wrote:
> Yes, this is the third email on this in the last month, previous two
> didn't get any replies.

Sorry I didn't mean to anger you or be disrespectful in any way. My
apologies if I did.
I was off the list for a bit (because I unsubscribed from all of them
for personal reasons) and didn't find what I was looking for while
searching in the archive.

> I don't think 12.3 mentions source packages or describes what to do when
> there are multiple main subpackages.

That's what I wanted to clarify as there are mention of "package" and
"binary package" I wanted to make sure that package (as not "binary
package") was referring to source package.

> > I see several possibilities on how to handle that:
> >  * leave it as is and it's fine (but doesn't match Policy 12.3)
> >  * overwrite dh_installdocs to pass --doc-main-package
> >  * rename the -docs package to match -doc and have the
> > ftp-master rm the old one
> >  * have dh_installdocs translate python into python3 package names
> > when looking for the main package
> Note that there are two questions here, about the package name and about
> the file path. For the first question the answer is in
> https://lists.debian.org/debian-python/2019/07/msg00080.html: "Please keep
> the python-foo-doc package. Do not rename it to python3-foo-doc. If
> python-foo was providing documentation: move it to python3-foo or create
> python-foo-doc (not python3-foo-doc!) binary package."

Thanks for pointing out this one, I missed it during my research,

> For the second question, I'm keeping the things as is if the docs are
> installed into /python-foo-doc/ and change /python-foo/ to /python3-foo/
> otherwise. I'm not bumping the compat level so no /python-foo-doc/ to
> /python-foo/ changes occur.

Thanks for the explanation.

Have a nice day,
Joseph

Re: Joining DMPT and PAPT

[Joseph Herlant]

Yep, no problem.
I was just double-checking that my mail went throught. I realized I forgot
to switch the subscription to debian-python@ to my debian email from my old
one ;)

Joseph


On Thu, Oct 11, 2018, 7:40 PM eamanu15  wrote:

> Hi Joseph,
>
> Be patient. Maybe the person responsible for doing that did not have time.
>
> Cheers,
>
> Arias Emmanuel
> eamanu.com
>
> El jue., 11 de oct. de 2018 20:52, Joseph Herlant 
> escribió:
>
>> Hi guys,
>>
>> Did you have the time to consider adding me to at least the DPMT team?
>> There are a few of my packages that I'd like to update and I've
>> already moved my gpg key to my new account.
>>
>> Thanks a lot for your help,
>> Joseph
>>
>> On Tue, Oct 2, 2018 at 8:50 PM Joseph Herlant 
>> wrote:
>> >
>> > Hi,
>> >
>> > I'm already in there as aerostitch-guest but I just got my DD account
>> > so I'd like to migrate my access to my new account: aerostitch.
>> >
>> > Of course I have read and accept the Python policy (in addition to the
>> > global Debian policy).
>> >
>> > Thanks for your help,
>> > Joseph
>>
>>

Re: Joining DMPT and PAPT

[Joseph Herlant]

Hi guys,

Did you have the time to consider adding me to at least the DPMT team?
There are a few of my packages that I'd like to update and I've
already moved my gpg key to my new account.

Thanks a lot for your help,
Joseph

On Tue, Oct 2, 2018 at 8:50 PM Joseph Herlant  wrote:
>
> Hi,
>
> I'm already in there as aerostitch-guest but I just got my DD account
> so I'd like to migrate my access to my new account: aerostitch.
>
> Of course I have read and accept the Python policy (in addition to the
> global Debian policy).
>
> Thanks for your help,
> Joseph

Joining DMPT and PAPT

[Joseph Herlant]

Hi,

I'm already in there as aerostitch-guest but I just got my DD account
so I'd like to migrate my access to my new account: aerostitch.

Of course I have read and accept the Python policy (in addition to the
global Debian policy).

Thanks for your help,
Joseph

Re: Policy missing from the python* packages?

[Joseph Herlant]

> This is fixed in 3.6.6-1 in unstable.

Thanks Matthias.
Is https://salsa.debian.org/python-team/defaults/python3-defaults the
right repo? I don't see any changes there related to the 3.6.6-1 that
is currently in unstable.

Thanks
Joseph

Policy missing from the python* packages?

[Joseph Herlant]

Hi guys,

It's probably a mistake on my side but I'm looking for the package
that provides the python policy locally.

In https://packages.debian.org/testing/amd64/python/filelist I can see
that the python package provides the files in the
'/usr/share/doc/python/python-policy.html/' directory.

But locally the package doesn't seem to have it when looking at dpkg
-L of python, python-doc, python3 or python3-doc.
I do see the rule for building the policy in python3-defaults in
https://salsa.debian.org/python-team/defaults/python3-defaults/blob/master/debian/rules#L54
 but amm I wrong to think that it could be due to the predepend on the
next rule to be commented? (stamp-doc: #stamp-doc-policy)

Thanks for your help,
Joseph

Re: Remove wiki version of the python policy?

[Joseph Herlant]

https://wiki.debian.org/Python/Policy has been updated/cleaned up.
Sorry it took so long.

Joseph

On Mon, May 14, 2018 at 10:50 PM, Ben Finney <bign...@debian.org> wrote:
> Joseph Herlant <herla...@gmail.com> writes:
>
>> Hi,
>>
>> On Mon, May 14, 2018, 10:01 PM Ben Finney <bign...@debian.org> wrote:
>>
>> > Joseph, do you mean simply replacing the article content with a “now
>> > the policy is in the packaging manuals” external link?
>>
>> Yes, that's what I meant, sorry for the confusion.
>
> Okay. Yes, that sounds fine to me.
>
> Hopefully just pointing (not redirecting) to the canonical location will
> be enough to gradually teach search engines the correct answer :-)
>
> --
>  \  “I would rather be exposed to the inconveniences attending too |
>   `\  much liberty than those attending too small a degree of it.” |
> _o__)—Thomas Jefferson, 1791-12-23 |
> Ben Finney
>

Remove wiki version of the python policy?

[Joseph Herlant]

Hi guys,

I noticed that https://wiki.debian.org/Python/Policy is full of
obsolete ways to do.
Is it worth updating it or should I just remove everything there and
redirect to https://www.debian.org/doc/packaging-manuals/python-policy/
?

It's ranked 3rd in Google when looking for "Debian Python Policy", so
there might still be more people than it should ending up there.

Thanks for your help,
Joseph

Re: Addition in lintian to warn about debian/pyversions file

[Joseph Herlant]

Hi,

On Mon, May 14, 2018 at 3:14 AM, Thomas Goirand  wrote:
> As Ondrej wrote, there's only a few packages having this. How about we
> just do a few NMUs as a team to fix that completely in the archive?

I was actually thinking about integrating that removal to Ondřej's
next mass-update (along with debian/pycompat) and if the packages are
not released in the next 2 months or so, I was planning to do some
team uploads on them (I saw some that have not been touched in a while
and that would benefit from a big cleanup).

On Mon, May 14, 2018 at 3:24 AM, Ondrej Novy  wrote:
> I didn't write count and I don't have list :)

The lintian tag would help getting the number easily! ;)

One of my thoughts about introducing it on info level is that we
should probably update https://wiki.debian.org/Python/Policy (I'll
start a separate thread on that) before having it on error level as
the page still shows examples with old/deprecated build systems.

Another reason to put that in lintian is that we still have all the
openstack python package to migrate to DPMT and those have a bunch of
pycompat and pyversions file that a lintian note about it would help
not forgetting that when we migrate those (I'll try to do some when I
got more spare time).


Thanks,
Joseph

Addition in lintian to warn about debian/pyversions file

[Joseph Herlant]

Hi guys,

FYI I am requesting a new lintian tag to warn about the presence of
the debian/pyversions file as it is supposed to be obsolete since
dh_python2 [1].

According to the policy[2], we are supposed to use the
X-Python3-Version field in debian/control to specify the version now.

Please let me know if that is an issue for you.

Bug report: #898592

Thanks,
Joseph

[1] https://wiki.debian.org/Python/TransitionToDHPython2
[2] 
https://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-specifying_versions

Re: Mass-commit fix of lintian ancient-python-version-field

[Joseph Herlant]

Hi,


On Fri, May 11, 2018 at 1:10 AM, Ondrej Novy  wrote:
> Are we sure it's completely safe to remove it globally?

Also, it's written in the python policy to do so:
https://wiki.debian.org/Python/Policy
"Another note: if there is a debian/pycompat file, you must launch
dh_python after dh_pysupport, but the recommended way is to remove
that file."

Checked in dh-python2 and 3 and I don't see how this could be an
issue. As Scott said, if that breaks any of the 18 packages, that
would probably be a bug or that the package needs to be updated to use
a supported build system.

Joseph

Re: Mass-commit fix of lintian ancient-python-version-field

[Joseph Herlant]

Hi,

On Fri, May 11, 2018, 1:10 AM Ondrej Novy  wrote:

> no problem, so just remove that file?
>
>
> https://github.com/onovy/onovy-mass/commit/2c24adf1ecd8fc934328f69c75b2b2d9256ee3c9
>
> Are we sure it's completely safe to remove it globally?
>

This file has been deprecated for about 10 years if I'm correct. It was
used in old versions of dh_python and dh_pysupport.
I will double-check the code of dh_python when I'm back at a computer but
it was already asked to remove it when we migrated to dh_python2 in 2015,
see: https://wiki.debian.org/Python/TransitionToDHPython2

Re: Mass-commit fix of lintian ancient-python-version-field

[Joseph Herlant]

On Thu, May 10, 2018 at 4:29 AM, Ondrej Novy  wrote:
> Removing Python 2 version: <= 2.7 (thus all)
> Removing Python 3 version: <= 3.4 (older than jessie)
>
> Any objections?

Thanks for doing that Ondřej, maybe we could delete the pycompat file
when exists at the same time (in a separate commit of course) to to
get rid of debian-pycompat-is-obsolete. It seems there are still 18
python modules with that file in.
If not, no worries I was planning to check the packages that have this
linitian tag in the next week or so, see what I can do to get rid of
that.

Thanks
Joseph

Re: tablib module: ok to migrate repo from openstack to DPMT?

[Joseph Herlant]

Hi guys,

Thanks, the repo is has been migrated to
https://salsa.debian.org/python-team/modules/python-tablib (ready for
review even if I already asked one of my usual sponsors about it).

> as Openstack team member: Go ahead.

@Ondrej as Openstack team member would you be willing to take care of
deleting the original repo (aka
https://salsa.debian.org/openstack-team/python/python-tablib) to avoid
confusion in the future please?

> Anything inside https://salsa.debian.org/openstack-team/python/* can be
> migrated to DPMT.
>
> See:
> https://salsa.debian.org/openstack-team/debian/stuff/blob/master/groups.txt#L6

Thanks for pointing that out, I'll have a look and see if I can help
on that in the days to come.

Thanks,
Joseph

tablib module: ok to migrate repo from openstack to DPMT?

[Joseph Herlant]

Hi guys,

I need to upgrade python-tablib (and build the python3 version) to
upgrade django-tables2.

Based on https://bugs.debian.org/865855 it seems the openstack team
don't want to manage it anymore.

Do you mind if I move the repo to the DPMT before upgrading the package?

Thanks
Joseph

Help proposed for migration of PAPT repos to Salsa

[Joseph Herlant]

Hi,

I've seen that there are some SVN repositories for PAPT on alioth and
I was wondering if you'd want help to move them to Salsa.

I'm familiar with the procedure to transfert a repo from svn to git
without loosing the tags, commits, branches, etc and I can do some on
my spare time if it helps.

Best,
Joseph

Access to DPMT and PAPT on salsa

[Joseph Herlant]

Hi,

I'm one of the maintainers of pylint-django, pylint-plugin-utils and asciidoc.
I'd like to be added to the DPMT team for the 2 first repos and I'd
like to move asciidoc to PAPT (it is EOL but it will take a few months
for me to take care of its EOL properly).

My account on salsa is aerostitch-guest
Thanks
Joseph