Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Andrey Rahmatullin <wrar@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: Side effect of dropping python2 with -doc packages
Date: Tue, 13 Aug 2019 19:50:01 +0200
Message-ID: <yuJ5L-4Wj-1@gated-at.bofh.it>
References: <yuICJ-4LH-7@gated-at.bofh.it>
Old-Return-Path: <wrar@debian.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="lMM8JwqTlfDpEaS6"
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Approved: robomod@news.nic.it
Lines: 70
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:11616


--lMM8JwqTlfDpEaS6
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Aug 13, 2019 at 10:16:28AM -0700, Joseph Herlant wrote:
> While tidying up some packages before taking some time off I realized
> that some packages like django-tables had binary packages that took
> the convention of creating -doc packages using <binary package>-doc (a
> very long time ago).
>=20
> The result was the location of the doc changed from
> /usr/share/doc/python-django-tables2-doc to
> /usr/share/doc/python-django-tables2 with the bump to compat 11.
>=20
> But now that we dropped the python2 binary package we end up with the
> "main package" not being detected anymore and the doc moved back to
> /usr/share/doc/python-django-tables2-doc.
Yes, this is the third email on this in the last month, previous two
didn't get any replies.

> The way I read the policy, it seems the -doc package should be <source
> package name>-doc. Am I correct to read it this way?
I don't think 12.3 mentions source packages or describes what to do when
there are multiple main subpackages.

> 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 <source package>-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."
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.

--=20
WBR, wRAR

--lMM8JwqTlfDpEaS6
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAl1S9g4tFIAAAAAAFQAP
cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh
QqwP/1doqJr2M2OUeZHmquNSA1oneSbkY3KjOihrV2qVj2pdqTCVuDBFXzZ2TbOy
37MaV76xxkfV5RXUZRWMg9ut7ptNzxd7pto1THmFm+UARoj/nA1AbcolwW1oVLAD
8U0+LTTnTQEBAXGf6Gj6nqvMHAmamis/9fMsVK7JHMivzrvNUfOKKSmCrs3Z0lz3
F7dDID7E+XgaJ/81cpQ4O2LU/dRBBNVCAa5niLTv12wq2AyvmjrG6RwsfSGs0tsW
pRd6PBZR9KD6t/GRu7QxDn+oWr65LpKQ6mS1P+pHv9Oi3ld8gat+0hjk705HT7wW
z/7RGqarbyzc5il7QQj2UVq81Zz+ld6j6LSCktO5ZH0mW/2q7F8JfkgCsi3HZvBf
KDuB6PuGyT1HoV0BtaRDFgtNxto7zoYnegC7zXsBcPkDqeSSo068mYgicp13VhHW
d99bbRW+S7Iu8p3RMAEYojU7Sq8jQhcarEZ9a+cfpqo/UT7SePl1CMi2EDXX7ZRI
gvU34moWAO0haWJ7MHO9fGO8hWQ8Ld8q5aQxPomOnK78bcIxZg0SPNL28BOSR1cB
qVl7lL+VGSUJlMSzQ2wCulTSIXJwvyhtx2l5HztfnUDOuka0GIeD0TKv7gG0BPA/
rDdD/3qJ/hT0ihxyFWqDu9/pka4n+NoWrlFRtvmAm9VSje9Q
=jSnd
-----END PGP SIGNATURE-----

--lMM8JwqTlfDpEaS6--