have you tried just sed'ing the version in the toml line to the version
that ships with slackware 15.0 ?
quite often that works, and the only reason the requirement changed was
that the system it was developed on had a newer setuptools, not that it
actually used any new features.
regards, Tim
On 09/06/2023 10:23, fourtysixandtwo wrote:
Hi Yth,
I have a slackbuild for setuptools, using the same version (65.1.1)
and patch from current source that I've been thinking of uploading.
I've tested it with a newer version as well, so I'm not set on using
the one from current.
I've attached the slackbuild if you want to give it a try. It could
use another set of eyes and testing. Let me know your thoughts.
Here's a snippet from the README on how to use it.
Installs to /opt/python3.9/site-packages.
Add the following before the python3 build commands in your
Slackbuild to use this version over the stock one in 15.0:
export PYTHONPATH=/opt/python3.9/site-packages/
Cheers
P.S. It's currently 26C in my house and I can't sleep so you're
getting this reply now instead of later
On Fri, Jun 9, 2023 at 1:44 AM Arnaud via SlackBuilds-users
<slackbuilds-users@slackbuilds.org> wrote:
Hi everybody !
I'm facing a slight problem.
I've updated python3-dulwich, apparently more than a month ago.
It is used by Kallithea and hg-git which I also maintain, I'm not
using hg-git
often, but I have a working and updated Kallithea service around.
Well it seems I didn't test this update as throughly as I thought.
Or at all, for that matter.
The build is broken and produces those files :
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/PKG-INFO
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/SOURCES.txt
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/dependency_links.txt
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/top_level.txt
That, obviously, doesn't work as expected.
The problem resides in the python-setuptools package of Slackware
15.0 which is
at version 57.5.0.
In dulwich/pyproject.toml lies the answer :
[build-system]
requires = ["setuptools>=61.2"]
Here I've got three solutions :
* revert dulwich to earlier version, 0.21.3, and wait for
Slackware 15.1.
* create a python3-setuptools package which'll overwrite
Slackware's stock
python-setuptools with a newer version. Could even name it
python-setuptools for
obvious, and transparent, replacement. It'll probably be updated
naturally when
Slackware releases 15.1 is out.
-> I have it working with latest setuptools 67.8.0, and dulwich
builds fine.
* somehow prepare a local setuptools to use for building dulwich,
adding the
source to dulwich's info file, and building both while installing
only dulwich.
Does anyone have any advice on that ?
I mean, apart from the obvious « test your friggin' SlackBuilds before
submitting them », I've got it in a loop between my ears, and in
French...
- Yth.
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ -https://slackbuilds.org/faq/
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
