found -1 4.11.0+dfsg-1 thanks Hi,
I've been using pelican for some time and it was only when investigating this bug that I realised that pelican-themes even existed. The bug originates here: https://salsa.debian.org/python-team/packages/pelican/-/blob/debian/master/pelican/tools/pelican_themes.py?ref_type=heads#L27 _THEMES_PATH could easily be adjusted for Debian but I'm not clear on the purpose or objective of pelican-themes is within Debian. In the virtualenv environment, bringing the theme files into the pelican paths makes sense. Once packaged, the only objective when adding, upgrading and removing themes would seem to be git operations from the various pelican-themes available at https://github.com/getpelican/pelican-themes or testing a local theme. There seems to be no real point in having pelican-themes in Debian as an executable - it's largely replaced by git operations (possibly submodules) and then a config change in pelicanconf.py to specify a path. So, my initial reaction to the bug would be to patch pelican_themes.py to use os.getcwd() instead of pelican.__file__ -- Neil Williams ============= [email protected] https://www.codehelp.co.uk/
