<html><body><div id="edo-message"><div></div>Hey Tonus (and list),</div><div id="edo-message"><br></div><div id="edo-message">I can take it, it’s a dead package anyway and is superseded by pyxdg in current, so it can be wiped away whenever we get a new release regardless. I’d have to refresh my memory on gammastep, but it’s not dependent on that specific python xdg implementation, it just requires any python xdg package. That just happened to be the one I used when making the SlackBuild.</div><div id="edo-message"><br></div><div id="edo-message">I’ll look it over when I push my PRs for this week and if you want I can update python3-xdg with my info for the time being. </div><div id="edo-message"><br></div><div id="edo-message">Thanks for the heads up,</div><br><div id="edo-meta"><div id="edo-signature" style="font-family: sans-serif, 'Helvetica Neue', Helvetica, Arial;">— Jay Lanagan</div></div><div id="edo-original"><div><br><br><blockquote type="cite" style="margin:1ex 0 0 0; height: min-content; border-left:1px #ccc solid;padding-left:0.5ex;"><div>On Jul 29, 2025 at 5:16 PM, <<a href="mailto:tonus1@free.fr">Tonus</a>> wrote:<br><br></div><div><pre class="edo-pre">Hi all,
Hi Jay,
I updated i3expo-ng and patched the derecated dependency of python3-xdg
to switch to python3-xdg-base-dirs according to
https://pypi.org/project/xdg-base-dirs/ :
"xdg-base-dirs was previously named xdg, and was renamed due to an
import collision with PyXDG. If you used xdg prior to the rename, update
by changing the dependency name from xdg to xdg-base-dirs and the import
from xdg to xdg_base_dirs."
I will drop the maintenace of python3-xdg (that will not evolve anyway).
Since the only package that depends on it is gammastep, would you, Jay
take it ?
--
Regards,
Tonus.
</pre></div></blockquote></div></div></body></html>