Possible License conflict (?) with setuptools during build on 2.2.8 #779

dschmide · 2026-02-10T14:31:58Z

dschmide
Feb 10, 2026

Version 2.2.8 of mysqlclient seems to have a bug in its packaging configuration file (pyproject.toml) that causes it to fail when building on our system

this is the error log we get during the build process

  configuration error: `project.license` must be valid exactly by one definition (2 matches found):
  
      - keys:
          'file': {type: string}
        required: ['file']
      - keys:
          'text': {type: string}
        required: ['text']

  ...
  
  OFFENDING RULE: 'oneOf'
  
  DEFINITION:
      {
          "oneOf": [
              {
                  "properties": {
                      "file": {
                          "type": "string",
                          "$$description": [
                              "Relative path to the file (UTF-8) which contains the license for the",
                              "project."
                          ]
                      }
                  },
                  "required": [
                      "file"
                  ]

  ...
  
  × Encountered error while generating package metadata.
  ╰─> mysqlclient

I am unfamiliar with this error, but downgrading to version 2.2.7 fixed the issue. I am wondering what caused this, or if it it something that happened only on our system. Anyone else getting this?
We are using python 3.11 which seems to be fine according to the requirements: Requires: Python >=3.10

added seed packages: pip==23.0.1, setuptools==66.1.1, wheel==0.38.4

dschmide · 2026-02-10T14:41:21Z

dschmide
Feb 10, 2026
Author

maybe this is related?

11752de
#772

is it possible that the version of setuptools caused this?

Please use a simple string containing a SPDX expression for project.license. You can also use project.license-files. (Both options available on setuptools>=77.0.0).

0 replies

methane · 2026-02-11T08:12:38Z

methane
Feb 11, 2026
Maintainer

You need to use setuptools>=77

0 replies

dschmide · 2026-02-11T20:55:15Z

dschmide
Feb 11, 2026
Author

I see, thats unfortunate because the default setuptools that comes with python 3.11 (which is supported by this package) is 75.6.0 and most linux version only have 66.1.1, but I guess that explains it.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Possible License conflict (?) with setuptools during build on 2.2.8 #779

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 3 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Possible License conflict (?) with setuptools during build on 2.2.8 #779

Uh oh!

Uh oh!

dschmide Feb 10, 2026

Replies: 3 comments

Uh oh!

Uh oh!

dschmide Feb 10, 2026 Author

Uh oh!

methane Feb 11, 2026 Maintainer

Uh oh!

dschmide Feb 11, 2026 Author

dschmide
Feb 10, 2026

dschmide
Feb 10, 2026
Author

methane
Feb 11, 2026
Maintainer

dschmide
Feb 11, 2026
Author