Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Ben Finney Newsgroups: linux.debian.maint.python Subject: How to convince =?utf-8?B?4oCYZGhfcHl0aG9uM+KAmQ==?= to handle =?utf-8?Q?=E2=80=98=2Fusr=2Flib=2Fpython3=2E7=2Fdist-packages=2Ffoo=2Eegg?= =?utf-8?Q?-info=2F=E2=80=99?= correctly? Date: Sun, 15 Jul 2018 09:00:01 +0200 Message-ID: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Jul 15 06:51:05 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.069 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LDO_WHITELIST=-5, RDNS_NONE=0.793, SARE_HEAD_8BIT_SPAM=0.888] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 X-Injected-Via-Gmane: http://gmane.org/ Lines: 41 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-Public-Key-ID: 0xAC128405 X-Public-Key-Fingerprint: 517C F14B B2F3 98B0 CB35 4855 B8B2 4C06 AC12 8405 X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-pubkey.asc X-Post-From: Ben Finney Cancel-Lock: sha1:zmUfFRWmU7JLh55Y2KF4AszPcWM= X-Mailing-List: archive/latest/16109 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/85zhyt801z.fsf@benfinney.id.au Approved: robomod@news.nic.it Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sun, 15 Jul 2018 16:50:32 +1000 X-Original-Message-ID: <85zhyt801z.fsf@benfinney.id.au> X-Original-X-Complaints-To: usenet@blaine.gmane.org Xref: csiph.com linux.debian.maint.python:10693 Howdy all, The ‘python-coverage’ source package has some special handling of build and install rules. How can I convince the packaging tools to correctly handle ‘/usr/lib/python3.7/dist-packages/foo.egg-info/’? This was brought to my attention by the recent addition of the Lintian tag “python-module-in-wrong-location”: W: python3-coverage: python-module-in-wrong-location usr/lib/python3.7/dist-packages/coverage-4.5.1.egg-info/ usr/lib/python3/dist-packages/coverage-4.5.1.egg-info/ N: N: The package installs a Python module or debug information for a Python N: module in the wrong location for the given version of Python. N: N: dh_python3 can be used to fix this for Python 3 modules. N: N: Refer to Debian Python Policy section 2.5 (Module Path) and N: https://bugs.debian.org/576012 for details. N: N: Severity: normal, Certainty: possible N: N: Check: files, Type: binary, udeb N: W: python3-coverage: python-module-in-wrong-location usr/lib/python3.7/dist-packages/coverage-4.5.1.egg-info/entry_points.txt usr/lib/python3/dist-packages/coverage-4.5.1.egg-info/entry_points.txt Which particular of those files are right or wrong, according to the Debian Python Policy §2.5? * usr/lib/python3.7/dist-packages/coverage-4.5.1.egg-info/ * usr/lib/python3/dist-packages/coverage-4.5.1.egg-info/ * usr/lib/python3.7/dist-packages/coverage-4.5.1.egg-info/entry_points.txt * usr/lib/python3/dist-packages/coverage-4.5.1.egg-info/entry_points.txt How should I change the package's ‘debian/rules’ to conform to Debian Python Policy §2.5? -- \ “I went to the hardware store and bought some used paint. It | `\ was in the shape of a house.” —Steven Wright | _o__) | Ben Finney