<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
have you tried just sed'ing the version in the toml line to the
version that ships with slackware 15.0 ?<br>
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.<br>
regards, Tim<br>
<br>
<div class="moz-cite-prefix">On 09/06/2023 10:23, fourtysixandtwo
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAAZ8Hag3U+Ki9SKZwOY4bmMSp61pLjFHkHD3mfkFb-vB11LwZg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi Yth,<br>
<br>
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.<br>
<br>
<div>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.<br>
</div>
<div><br>
</div>
<div>Here's a snippet from the README on how to use it.</div>
<br>
Installs to /opt/python3.9/site-packages.<br>
<br>
Add the following before the python3 build commands in your<br>
Slackbuild to use this version over the stock one in 15.0:<br>
<br>
<div>export PYTHONPATH=/opt/python3.9/site-packages/</div>
<div><br>
</div>
<div>Cheers<br>
</div>
<div><br>
</div>
<div>P.S. It's currently 26C in my house and I can't sleep so
you're getting this reply now instead of later<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Jun 9, 2023 at 1:44 AM
Arnaud via SlackBuilds-users <<a
href="mailto:slackbuilds-users@slackbuilds.org"
moz-do-not-send="true" class="moz-txt-link-freetext">slackbuilds-users@slackbuilds.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi
everybody !<br>
<br>
I'm facing a slight problem.<br>
I've updated python3-dulwich, apparently more than a month
ago.<br>
It is used by Kallithea and hg-git which I also maintain, I'm
not using hg-git<br>
often, but I have a working and updated Kallithea service
around.<br>
Well it seems I didn't test this update as throughly as I
thought.<br>
Or at all, for that matter.<br>
<br>
The build is broken and produces those files :<br>
<br>
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/<br>
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/PKG-INFO<br>
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/SOURCES.txt<br>
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/dependency_links.txt<br>
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/top_level.txt<br>
<br>
That, obviously, doesn't work as expected.<br>
<br>
The problem resides in the python-setuptools package of
Slackware 15.0 which is<br>
at version 57.5.0.<br>
In dulwich/pyproject.toml lies the answer :<br>
[build-system]<br>
requires = ["setuptools>=61.2"]<br>
<br>
<br>
Here I've got three solutions :<br>
<br>
* revert dulwich to earlier version, 0.21.3, and wait for
Slackware 15.1.<br>
<br>
* create a python3-setuptools package which'll overwrite
Slackware's stock<br>
python-setuptools with a newer version. Could even name it
python-setuptools for<br>
obvious, and transparent, replacement. It'll probably be
updated naturally when<br>
Slackware releases 15.1 is out.<br>
-> I have it working with latest setuptools 67.8.0, and
dulwich builds fine.<br>
<br>
* somehow prepare a local setuptools to use for building
dulwich, adding the<br>
source to dulwich's info file, and building both while
installing only dulwich.<br>
<br>
<br>
Does anyone have any advice on that ?<br>
I mean, apart from the obvious « test your friggin'
SlackBuilds before<br>
submitting them », I've got it in a loop between my ears, and
in French...<br>
<br>
- Yth.<br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">SlackBuilds-users@slackbuilds.org</a><br>
<a
href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a
href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://slackbuilds.org/faq/</a><br>
<br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
SlackBuilds-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a>
<a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a>
Archives - <a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a>
FAQ - <a class="moz-txt-link-freetext" href="https://slackbuilds.org/faq/">https://slackbuilds.org/faq/</a>
</pre>
</blockquote>
<br>
</body>
</html>