Bug 807865 – mail-filter/spf-engine-2.9.2-r1 uses a probably incorrect DISTUTILS_USE_SETUPTOOLS value

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Agostino Sarubbo 2021-08-12 09:10:41 UTC]

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: mail-filter/spf-engine-2.9.2-r1 uses a probably incorrect DISTUTILS_USE_SETUPTOOLS value.
Discovered on: amd64 (internal ref: tinderbox)

[Comment 1 Agostino Sarubbo 2021-08-12 09:10:44 UTC]

Created attachment 732448 [details]
build.log

build log and emerge --info

[Comment 2 Michael Orlitzky 2021-08-17 02:15:29 UTC]

I don't know how to make the QA warning go away, but I left a comment in the ebuild when I did this:

  # setup.py defines entry_points                                                 
  DISTUTILS_USE_SETUPTOOLS=rdepend
  inherit distutils-r1

[Comment 3 Sam James 2021-08-17 02:18:09 UTC]

(In reply to Michael Orlitzky from comment #2)
> I don't know how to make the QA warning go away, but I left a comment in the
> ebuild when I did this:
> 
>   # setup.py defines entry_points                                           
> 
>   DISTUTILS_USE_SETUPTOOLS=rdepend
>   inherit distutils-r1

I've personally not been 100% sure on this since the "recent changes" in newer Pythons/distutils: https://blogs.gentoo.org/mgorny/2020/10/21/distutils_use_setuptools-qa-spam-and-more-qa-spam/.

Specifically, see the "Entry points via importlib.metadata" part of the post.

mgorny may be able to offer further guidance and/or update the Python guide with a way to tell if the QA check is right in a particular case?

[Comment 4 Michael Orlitzky 2021-08-17 02:28:39 UTC]

I'm also not 100% sure, but I think "rdepend" is still correct these days when entry_points is used for console_scripts. Here's the setup.py file in question:

  https://git.launchpad.net/spf-engine/tree/setup.py

[Comment 5 Michael Orlitzky 2021-09-03 01:22:16 UTC]

*** Bug 811252 has been marked as a duplicate of this bug. ***

[Comment 6 Michael Orlitzky 2021-10-29 11:47:49 UTC]

*** Bug 820662 has been marked as a duplicate of this bug. ***