Hi Mark, First, one key point is the dates… >> On Fri, 18 Dec 2020 at 21:10, zimoun wrote: >>> On Thu, 22 Jun 2017 at 12:35, ng0 wrote: …so more than 3 years without any comment. By without any comment, I mean literally no comment; my email was the first. I can tell you that most of the old and forgotten bug reports like this one are simply emails addressed to incorrect list (bug-guix instead of guix-devel); as a rule of thumb. I am trying hard to avoid some false positive by first understand and second carefully check, so if I do not understand nor be able to check then I let the report as it is. Well, I am sorry if I have failed to one or the other. Second, it does not appear to me a bug. The “quickstart” generates local configuration files that contain absolute path to the Python interpreter. --8<---------------cut here---------------start------------->8--- $ guix environment -C --ad-hoc pelican coreutils grep [env]$ mkdir foo && cd foo && ls -l total 0 [env]$ pelican-quickstart Welcome to pelican-quickstart v4.2.0. This script will help you create a new Pelican-based website. Please answer the following questions so this script can generate the files needed by Pelican. > Where do you want to create your new web site? [.] > What will be the title of this web site? Foo > Who will be the author of this web site? zimoun > What will be the default language of this web site? [en] > Do you want to specify a URL prefix? e.g., https://example.com (Y/n) n > Do you want to enable article pagination? (Y/n) n > What is your time zone? [Europe/Paris] > Do you want to generate a tasks.py/Makefile to automate generation and publishing? (Y/n) y > Do you want to upload your website using FTP? (y/N) N > Do you want to upload your website using SSH? (y/N) N > Do you want to upload your website using Dropbox? (y/N) N > Do you want to upload your website using S3? (y/N) N > Do you want to upload your website using Rackspace Cloud Files? (y/N) N > Do you want to upload your website using GitHub Pages? (y/N) N Done. Your new project is available at /tmp/bar [env]$ ls Makefile content output pelicanconf.py publishconf.py tasks.py [env]$ egrep -nr "store" pelicanconf.py:1:#!/gnu/store/h8jw9qhyfp6fm6nb3cgh4335qhr31wfz-python-wrapper-3.8.2/bin/python publishconf.py:1:#!/gnu/store/h8jw9qhyfp6fm6nb3cgh4335qhr31wfz-python-wrapper-3.8.2/bin/python --8<---------------cut here---------------end--------------->8--- Why is it a bug? Since the test suite is #f, I have not checked if the package is really functional. But the last updates are in 2019-12-29 and a revamp in 2019-01-15 so I assumed the package is functional and this reference in config files is not an issue. >>>> We have a couple more bugs like this. If they are already grouped, >>>> add this bug to them. >>> >>> What are these other “couple more bugs like this”? >>> >>> >> >> No moreinfo so I am closing. If I am missing something, then please >> reopen it. Third, no moreinfo about the bug itself, which I consider myself as notabug. And no moreinfo about other cases to examine them case per case. So I closed after waiting couple of weeks. BTW, the submitter of the report clearly stated they is not working on Guix anymore [1], therefore, they will no provide moreinfo. 1: > The lack of response about the "couple more bugs like this" does not > invalidate the bug reported in this bug report. I think it was merely a > suggestion that this bug might possibly be merged with other similar > bugs. The key point is that we don't need an answer to that question to > investigate/fix this bug. Sorry if it has not appeared as this but I have investigated this bug and from my understanding, it is not a bug. Since no one commented, I have moved forward. Again sorry if I have missed something. > Unless we have reason to believe that 'pelican-quickstart' is no longer > embedding store paths in the generated files, I think we should keep > this bug open. Does that make sense? Why does embed store paths in configuration files is an issue? Pelican is a Python application which therefore requires a Python interpreter. Running ’pelican’ against another Python VM than the one it was built seems a bad idea. And if the point is run “pelican-quickstart” with one Pelican version built against one Python VM, and then reuse these generated config files with another Pelican version built against another Python VM, in this use-case, the bug is upstream because it embeds absolute path which does not respect PEP 394 [2]. I agree that in this case, the bug should/must still be opened until upstream fix. Well, I am probably missing the story about shebang and Guix. 2: All the best, simon