Best way of action would be to send a PR upstream to remove this old leftover (from Python 2.x times ?) line in setup.py
tchet@quieter:/tmp/dlp-build$ grep -ir configpar setup.py: "configparser", klpbuild/klplib/utils.py: git_data = git.GitConfigParser() klpbuild/klplib/config.py:from configparser import ConfigParser klpbuild/klplib/config.py:_config = ConfigParser() klpbuild/klplib/config.py: config = ConfigParser(allow_no_value=True) python3 -c 'from configparser import ConfigParser' --> it's already there, no need to ITP and old backport Le sam. 30 mai 2026 à 13:41, Aryan Karamtoth <[email protected]> a écrit : > > >Hi, > > >Please show where dlp-build is packaged. > >I have strong doubts that this backports makes any sense > >to package when we already have a python3.13 > > >A 2 lines patch is most likely all you need to make dlp-build work > > Hi, > > Dlp-build is more of a work-in-progress piece of software that I'm trying to > work on by forking klp-build to introduce kernel livepatches in Debian as > part of my GSoC project. > > I don't have a debian/ folder yet but the source code can be found here: > https://salsa.debian.org/spaciouskarter78/dlp-build > > I saw the upstream i.e klp-build list configparser as a dependency so I filed > an ITP for the same. Please let me know if there's a workaround, it'd be of > great help. > > Regards, > > Aryan Karamtoth > Debian Maintainer > (IRC: spaciouskarter78) > >
