bug#27447: closed (pelican-quickstart produces files with store path shebangs)

[GNU bug Tracking System]

Your message dated Tue, 05 Oct 2021 10:06:28 +1100
with message-id <8735pg2xvv.fsf@sturm.com.au>
and subject line Re: bug#27447: pelican-quickstart produces files with store 
path shebangs
has caused the debbugs.gnu.org bug report #27447,
regarding pelican-quickstart produces files with store path shebangs
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
27447: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=27447
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> pelican-quickstart produces files with store path shebangs
>
>
>
>
> Date: 
>
> Thu, 22 Jun 2017 12:35:28 +0000
>
>
>
>
> In a pelican directory after running pelican-quickstart:
>
> egrep -nr "store"
> …
> pelicanconf.py:1:#!/gnu/store/bf54hnwd8mb63zmssc23fwslf5zvxpxs-python-wrapper-3.5.3/bin/python
> develop_server.sh:1:#!/gnu/store/k7029k5va68lkapbzcycdzj7m5bjb4b8-bash-4.4.12/bin/bash
> publishconf.py:1:#!/gnu/store/bf54hnwd8mb63zmssc23fwslf5zvxpxs-python-wrapper-3.5.3/bin/python
>
>
> We have a couple more bugs like this. If they are already grouped,
> add this bug to them.
> -- 
> ng0
> OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
> https://krosos.org/~/ng0/ https://www.infotropique.org
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#27447: pelican-quickstart produces files with store path shebangs
>
>
>
>
> Date: 
>
> Tue, 05 Oct 2021 10:06:28 +1100
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
>
>
>
>
> On Tue, 05 Oct 2021, Ben Sturmfels wrote:
>
> >> ng0 wrote on 22 Jun 2017 14:35:
> >>
> >> In a pelican directory after running pelican-quickstart:
> >> egrep -nr "store"
> >> …
> >> pelicanconf.py:1:#!/gnu/store/bf54hnwd8mb63zmssc23fwslf5zvxpxs-python-wrapper-3.5.3/bin/python
> >> develop_server.sh:1:#!/gnu/store/k7029k5va68lkapbzcycdzj7m5bjb4b8-bash-4.4.12/bin/bash
> >> publishconf.py:1:#!/gnu/store/bf54hnwd8mb63zmssc23fwslf5zvxpxs-python-wrapper-3.5.3/bin/python
> >
> > This is a technically a bug, but it's in upstream and has no effect in
> > practise, so I'll close this bug report. Details below.
> >
> > As of Pelican 4.7.0 which I've just submitted an update patch for,
> > develop_server.sh is no longer created:
> >
> > $ egrep -nr "store"
> > pelicanconf.py:1:#!/gnu/store/nckjv3ccwdi6096j478gvns43ssbls2p-python-wrapper-3.8.2/bin/python
> > publishconf.py:1:#!/gnu/store/nckjv3ccwdi6096j478gvns43ssbls2p-python-wrapper-3.8.2/bin/python
> >
> > This is *technically* a bug because these configuration files are
> > created once when the user is setting up their blog and will be used
> > forever after. In practise though, there's no issue since these files
> > are not executable - they are configuration only.
> >
> > This also isn't a packaging bug in Guix, it's upstream as zimoun
> > suggests. Here's the first line of those files as generated by upstream
> > pelican-quickstart:
> >
> > $ head -n1 pelicanconf.py publishconf.py 
> > ==> pelicanconf.py <==
> > #!/usr/bin/env python
> >
> > ==> publishconf.py <==
> > #!/usr/bin/env python
> >
> > These upstream files should not contain shebangs since they are not
> > executable or ever intended to be executed directly - they're config
> > only and have no functionality.
>
> I've now submitted a patch upstream:
>
> https://github.com/getpelican/pelican/pull/2932
>
> Closing.
>
>
> --- End Message ---