Your message dated Sun, 4 Jan 2026 13:48:57 +0100
with message-id <[email protected]>
and subject line Closing "extension-helpers: (build-)depends on deprecated 
module python3-pkg-resources" (invalid)
has caused the Debian Bug report #1083379,
regarding extension-helpers: (build-)depends on deprecated module 
python3-pkg-resources
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1083379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083379
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:extension-helpers
Version: 1.1.1-2
Severity: normal
Tags: sid trixie
User: [email protected]
Usertags: pkg-resources-deprecation

[This bug is targeted to the upcoming trixie release]

The package build-depends or depends on python3-pkg-resources, which is
deprecated upstream. Details can be found at

    https://setuptools.pypa.io/en/latest/pkg_resources.html

Use of pkg_resources is deprecated in favor of importlib.resources,
importlib.metadata and their backports (importlib_resources, 
importlib_metadata).
Some useful APIs are also provided by packaging (e.g. requirements and version
parsing). Users should refrain from new usage of pkg_resources and should work
to port to importlib-based solutions.

Python 3.12 in unstable provides both importlib_resources and
importlib_metadata, so no additional dependencies on those packages are needed.

--- End Message ---
--- Begin Message ---
Hi Matthias,

The only place where pkg_resources is used is in docs/conf.py, but the documentation is not built for this package. python3-pkg-resources is neither a build nor a run dependency; a grep on the build log showed nothing.

In the package changes after the bug was opened, I however could not find a change that would have removed the dependency.

Assuming that was opened by mistake, I close the bug. If that was wrong, please reopen.

Thanks

Ole

--- End Message ---

Reply via email to