From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id uBsnALTNAGAWfwAA0tVLHw (envelope-from ) for ; Thu, 14 Jan 2021 23:03:16 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id qHV9N7PNAGBOCAAAbx9fmQ (envelope-from ) for ; Thu, 14 Jan 2021 23:03:15 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 0068C9402A2 for ; Thu, 14 Jan 2021 23:03:14 +0000 (UTC) Received: from localhost ([::1]:60866 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l0Be5-0000U0-CF for larch@yhetil.org; Thu, 14 Jan 2021 18:03:13 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:35224) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l0Bdu-0000TC-DM for bug-guix@gnu.org; Thu, 14 Jan 2021 18:03:02 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:56244) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1l0Bdu-0002d4-5s for bug-guix@gnu.org; Thu, 14 Jan 2021 18:03:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1l0Bdu-00019E-0e for bug-guix@gnu.org; Thu, 14 Jan 2021 18:03:02 -0500 X-Loop: help-debbugs@gnu.org Subject: bug#27447: pelican-quickstart produces files with store path shebangs Resent-From: Mark H Weaver Original-Sender: "Debbugs-submit" Resent-CC: bug-guix@gnu.org Resent-Date: Thu, 14 Jan 2021 23:03:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 27447 X-GNU-PR-Package: guix X-GNU-PR-Keywords: moreinfo To: zimoun Received: via spool by 27447-submit@debbugs.gnu.org id=B27447.16106653234349 (code B ref 27447); Thu, 14 Jan 2021 23:03:01 +0000 Received: (at 27447) by debbugs.gnu.org; 14 Jan 2021 23:02:03 +0000 Received: from localhost ([127.0.0.1]:39557 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1l0Bcw-000184-Mn for submit@debbugs.gnu.org; Thu, 14 Jan 2021 18:02:03 -0500 Received: from world.peace.net ([64.112.178.59]:45862) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1l0Bct-00017Y-Gt for 27447@debbugs.gnu.org; Thu, 14 Jan 2021 18:02:01 -0500 Received: from mhw by world.peace.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l0Bcm-0000L0-Vu; Thu, 14 Jan 2021 18:01:53 -0500 From: Mark H Weaver In-Reply-To: <86h7njsvtn.fsf@gmail.com> References: <20170622123528.7xhnrkj5ksjznp3g@abyayala> <868s9uvprq.fsf@gmail.com> <86a6tftyrm.fsf@gmail.com> <87im804dds.fsf@netris.org> <86h7njsvtn.fsf@gmail.com> Date: Thu, 14 Jan 2021 18:00:40 -0500 Message-ID: <87a6tb3yz0.fsf@netris.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-guix@gnu.org List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: 27447@debbugs.gnu.org, ng0 Errors-To: bug-guix-bounces+larch=yhetil.org@gnu.org Sender: "bug-Guix" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -2.36 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of bug-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=bug-guix-bounces@gnu.org X-Migadu-Queue-Id: 0068C9402A2 X-Spam-Score: -2.36 X-Migadu-Scanner: scn1.migadu.com X-TUID: pX8I4cJjAbVb Hi Simon, zimoun writes: > First, one key point is the dates=E2=80=A6 > >>> On Fri, 18 Dec 2020 at 21:10, zimoun wrote: >>>> On Thu, 22 Jun 2017 at 12:35, ng0 wrote: > > =E2=80=A6so more than 3 years without any comment. That a bug has been neglected for years does not imply that it's no longer a bug, or that we should forget about it. > Second, it does not appear to me a bug. The =E2=80=9Cquickstart=E2=80=9D= 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 fil= es > needed by Pelican. > >=20=20=20=20=20 >> Where do you want to create your new web site? [.]=20 >> 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]=20 >> 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]=20 >> Do you want to generate a tasks.py/Makefile to automate generation and p= ublishing? (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-wra= pper-3.8.2/bin/python > publishconf.py:1:#!/gnu/store/h8jw9qhyfp6fm6nb3cgh4335qhr31wfz-python-wra= pper-3.8.2/bin/python > --8<---------------cut here---------------end--------------->8--- > > Why is it a bug? It's a bug because these absolute file names will cease to exist after the next 'core-updates' merge happens, and more precisely after the older system generations (or user profiles) are deleted and 'guix gc' subsequently deletes these obsolete store items. At that point, maybe things will break. I think that would need to be investigated before dismissing this bug report. >>> 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. In many cases, the lack of "moreinfo" prevents us from further investigating a bug, and in such cases I agree that it is justifiable to close a bug report. For example, users often report a bug that we are unable to reproduce, and then they stop communicating. However, this case is quite different. In this case, we already enough information to reproduce and investigate this bug. The "moreinfo" that you requested was regarding a side comment that ng0 made about the possibility of other similar bugs that might be merged with this one. The fact that ng0 never answered that side question doesn't imply that the bug he reported is no longer relevant. I think that there's good reason to believe that this bug is still relevant. It certainly has not yet been established here that this bug does not exist or is harmless. Therefore, we should not forget about it, even if ng0 has moved on. Does that make sense? Nonetheless, I very much appreciate your ongoing work on these old bug reports. It is a great help. Regards, Mark