From unknown Fri Jun 20 07:19:58 2025 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) Content-Type: text/plain; charset=utf-8 From: bug#61882 <61882@debbugs.gnu.org> To: bug#61882 <61882@debbugs.gnu.org> Subject: Status: emacs-next-pgtk does not find emacs-org-roam, other path issues Reply-To: bug#61882 <61882@debbugs.gnu.org> Date: Fri, 20 Jun 2025 14:19:58 +0000 retitle 61882 emacs-next-pgtk does not find emacs-org-roam, other path issu= es reassign 61882 guix submitter 61882 Csepp severity 61882 normal tag 61882 moreinfo unreproducible thanks From debbugs-submit-bounces@debbugs.gnu.org Tue Feb 28 22:03:57 2023 Received: (at submit) by debbugs.gnu.org; 1 Mar 2023 03:03:57 +0000 Received: from localhost ([127.0.0.1]:52293 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXCl2-0005Lz-Rw for submit@debbugs.gnu.org; Tue, 28 Feb 2023 22:03:57 -0500 Received: from lists.gnu.org ([209.51.188.17]:53640) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXCl1-0005Lr-VE for submit@debbugs.gnu.org; Tue, 28 Feb 2023 22:03:56 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pXCl0-0000nU-Bl for bug-guix@gnu.org; Tue, 28 Feb 2023 22:03:54 -0500 Received: from mx1.riseup.net ([198.252.153.129]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pXCkx-0004uE-IA for bug-guix@gnu.org; Tue, 28 Feb 2023 22:03:53 -0500 Received: from fews1.riseup.net (fews1-pn.riseup.net [10.0.1.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 4PRJwP1KLyzDqMD for ; Wed, 1 Mar 2023 03:03:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1677639829; bh=bZuhAABsi44aVNXF3XPFq6HNorlCcIDRAcEtWko63yM=; h=From:To:Subject:Date:From; b=bkq/dXZ0Ij03HSBA5ml+7peYIAyZQuiHayWaxC3iOpyr1ct3+o/obaioTu3fSQ6pe BibCG2VbOQaxGYrKDp70gIumtTP/JzwH4QGRp0gFpAhTMUa6IUs+GTJI0lv9KIFE4v Jfdi/WVo2ilchnwEssITmQnmiPJeHkeLF6b7yVCY= X-Riseup-User-ID: 60E0ED6350CFF691941E7AEF5623487A181DC07E7D895E5E0A72FA2998BC0D48 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews1.riseup.net (Postfix) with ESMTPSA id 4PRJwN3hX2z5vgM for ; Wed, 1 Mar 2023 03:03:48 +0000 (UTC) From: Csepp To: bug-guix@gnu.org Subject: emacs-next-pgtk does not find emacs-org-roam, other path issues Date: Wed, 01 Mar 2023 02:58:15 +0000 Message-ID: <87bkld896j.fsf@riseup.net> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=198.252.153.129; envelope-from=raingloom@riseup.net; helo=mx1.riseup.net X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: -1.4 (-) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.4 (--) emacs-org-roam is installed in my default profile and all the other emacs packages work with the emacs-next-pgtk package in the same profile. guix shell emacs-org-roam emacs-next-pgtk does not work, guix shell emacs-org-roam emacs does. Possibly related: when I had flatpak installed it was not showing up in my profile's bin directory, so I had to open it through guix shell. Maybe this is related to the bug where shell and build produce different derivations? current guix describe output (but this has been going on for at least a month or so) Generation 186 Feb 28 2023 02:57:13 (current) guix ff5fbcc repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit: ff5fbcc19bce6e94ead0cc79b27ae8ed0307463d raingloom c75fd77 repository URL: https://git.sr.ht/~raingloom/guix-packages branch: master commit: c75fd77980c7c5b45c91b0d921a25d8558266f41 guix-science 5fc5e3e repository URL: https://github.com/guix-science/guix-science.git branch: master commit: 5fc5e3e855c298a692c62129e9edd0fcc7c6949f nonguix 3a1e9f0 repository URL: https://gitlab.com/nonguix/nonguix.git branch: master commit: 3a1e9f0507d99403d1ba0f5557ee868b95b61eef From debbugs-submit-bounces@debbugs.gnu.org Wed Mar 01 04:25:53 2023 Received: (at 61882) by debbugs.gnu.org; 1 Mar 2023 09:25:53 +0000 Received: from localhost ([127.0.0.1]:52688 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXIib-0004Yj-5O for submit@debbugs.gnu.org; Wed, 01 Mar 2023 04:25:52 -0500 Received: from mailrelay.tugraz.at ([129.27.2.202]:39009) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXIiY-0004YY-D2 for 61882@debbugs.gnu.org; Wed, 01 Mar 2023 04:25:47 -0500 Received: from lprikler-laptop.ist.intra (gw.ist.tugraz.at [129.27.202.101]) by mailrelay.tugraz.at (Postfix) with ESMTPSA id 4PRTP21Jrlz3wd0; Wed, 1 Mar 2023 10:25:42 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tugraz.at; s=mailrelay; t=1677662743; bh=1TGX4TWVeUnnCeN+NXzz0/HpJeHmlIQULnxo6ERYLzg=; h=Subject:From:To:Date:In-Reply-To:References; b=V1or5PXGFdIiUTa0A9vinluBDmRofArS8HYku1PzxInY5pJkTeaoOY8mzMxwgWi0v 0L+4hmzlb5krE1Ko9Q7JZO+P6IRKCN3naBVunoCXCrwn7YmeTB7h2eAtREilmpcCM+ tRLmnXcQr9hLFDa3fiqyzlzoHn0zYCBXP48bk7/0= Message-ID: <6525e61f911b5c03547594432ff9102636c9a5cf.camel@ist.tugraz.at> Subject: Re: emacs-next-pgtk does not find emacs-org-roam, other path issues From: Liliana Marie Prikler To: Csepp , 61882@debbugs.gnu.org Date: Wed, 01 Mar 2023 10:25:41 +0100 In-Reply-To: <87bkld896j.fsf@riseup.net> References: <87bkld896j.fsf@riseup.net> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.0 MIME-Version: 1.0 X-TUG-Backscatter-control: waObeELIUl4ypBWmcn/8wQ X-Spam-Scanner: SpamAssassin 3.003001 X-Spam-Score-relay: -1.9 X-Scanned-By: MIMEDefang 2.74 on 129.27.10.116 X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 61882 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) Am Mittwoch, dem 01.03.2023 um 02:58 +0000 schrieb Csepp: > emacs-org-roam is installed in my default profile and all the other > emacs packages work with the emacs-next-pgtk package in the same > profile. > guix shell emacs-org-roam emacs-next-pgtk does not work, guix shell > emacs-org-roam emacs does. >=20 > Possibly related: when I had flatpak installed it was not showing up > in my profile's bin directory, so I had to open it through guix > shell. >=20 > Maybe this is related to the bug where shell and build produce > differen derivations? You probably messed up some of your paths. As a hint, guix shell --pure -E DISPLAY emacs-next-pgtk emacs-org-roam -- emacs should run without any issues (apart from your init.el not working as intended =E2=80=93 in that case, supply -Q). Try adding --check to your invocation of guix shell to see whether your rc files are borked. From debbugs-submit-bounces@debbugs.gnu.org Wed Mar 01 06:22:23 2023 Received: (at 61882) by debbugs.gnu.org; 1 Mar 2023 11:22:23 +0000 Received: from localhost ([127.0.0.1]:52877 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXKXP-000433-I3 for submit@debbugs.gnu.org; Wed, 01 Mar 2023 06:22:23 -0500 Received: from mx0.riseup.net ([198.252.153.6]:42308) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXKXN-00042o-8P for 61882@debbugs.gnu.org; Wed, 01 Mar 2023 06:22:22 -0500 Received: from fews1.riseup.net (fews1-pn.riseup.net [10.0.1.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx0.riseup.net (Postfix) with ESMTPS id 4PRWzW2XvMz9s3N; Wed, 1 Mar 2023 11:22:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1677669735; bh=qGbpA7oCKU0dzCCK5p/RS0+Z0UaYaMbTMw00TNxlg6w=; h=References:From:To:Cc:Subject:Date:In-reply-to:From; b=qTkbz0TRWhD2jMK3jRlEvu6WDbWCPJmJqU8E+2Ra7b+WFu9WV+pdCPNoPqqXrQmRI gBWUG+BesH6Am1YWg5NcS1lBc73GH2UvBnQ2dV8nw+oUkl2vd1wpIcq292I6+Iimog Cfout1f+cbuttGXfChzpmy00Qf0EvrQc34U8JfRU= X-Riseup-User-ID: 385A679598CFBA16014F84F7CD9DEC96320096EC1DC85D59D7DF19973DC75273 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews1.riseup.net (Postfix) with ESMTPSA id 4PRWzV4VmLz5vTc; Wed, 1 Mar 2023 11:22:13 +0000 (UTC) References: <87bkld896j.fsf@riseup.net> <6525e61f911b5c03547594432ff9102636c9a5cf.camel@ist.tugraz.at> From: Csepp To: Liliana Marie Prikler Subject: Re: emacs-next-pgtk does not find emacs-org-roam, other path issues Date: Wed, 01 Mar 2023 12:16:56 +0100 In-reply-to: <6525e61f911b5c03547594432ff9102636c9a5cf.camel@ist.tugraz.at> Message-ID: <87ilfklns5.fsf@riseup.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 61882 Cc: 61882@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Liliana Marie Prikler writes: > Am Mittwoch, dem 01.03.2023 um 02:58 +0000 schrieb Csepp: >> emacs-org-roam is installed in my default profile and all the other >> emacs packages work with the emacs-next-pgtk package in the same >> profile. >> guix shell emacs-org-roam emacs-next-pgtk does not work, guix shell >> emacs-org-roam emacs does. >>=20 >> Possibly related: when I had flatpak installed it was not showing up >> in my profile's bin directory, so I had to open it through guix >> shell. >>=20 >> Maybe this is related to the bug where shell and build produce >> differen derivations? > You probably messed up some of your paths. As a hint, > guix shell --pure -E DISPLAY emacs-next-pgtk emacs-org-roam -- emacs > should run without any issues (apart from your init.el not working as > intended =E2=80=93 in that case, supply -Q). > > Try adding --check to your invocation of guix shell to see whether your > rc files are borked. How the hell would my paths affect what's in the bin folder? Like, the flatpak binary is literally not present in the profile, that's why it's not showing up in $PATH. Well, I'll check next time I'm on that machine, right now I'm writing from the netbook and I'm in a bit of a hurry and don't want to wait for derivation computations. But I'm like 99% sure it's not due to my paths, because all other emacs packages work. From debbugs-submit-bounces@debbugs.gnu.org Wed Mar 01 09:40:55 2023 Received: (at 61882) by debbugs.gnu.org; 1 Mar 2023 14:40:55 +0000 Received: from localhost ([127.0.0.1]:53119 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXNdX-0003jE-8x for submit@debbugs.gnu.org; Wed, 01 Mar 2023 09:40:55 -0500 Received: from mailout.easymail.ca ([64.68.200.34]:33456) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXNdU-0003iy-TM for 61882@debbugs.gnu.org; Wed, 01 Mar 2023 09:40:53 -0500 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id DE5DD68ADB; Wed, 1 Mar 2023 14:40:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bokr.com; s=easymail; t=1677681646; bh=aSnO0hUMDSRAO/Q9x4DPhpYfcTyUVReRqiKFXPv/FPE=; h=From:Date:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=h2B0mIX226t+bZT83NVciZWyxQFBCD2H0ZDkyGa27EZ6w1zlaUCWO51/CqzJcQSKA y38B7CP1SbiJAbjRfiqr/jKsM3Nrv7gYBBw1vTDvbkTGvZYkgp4psSx+9UQDXCL9T6 yd91AY4woOqwc/Mu14dLTnMqJAtACT7x1N5f3qTfrO3I6l8aRFZxi82kZuq30yem3/ SABBlojeEj0Ttj5yixYA1hGQPZpd0AT+blHEGFK/QKry+op34gbW3w1kNRzj5Lt14h X95+q1r2uCm3mmAp+9pTFo5wVrLlKEza8/zYg9/a9gPLGQ+jCBKlfYicOzHvd9v2qX uluEf8PzXY5PA== X-Virus-Scanned: Debian amavisd-new at emo07-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo07-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lQg3J_ZzXDDS; Wed, 1 Mar 2023 14:40:46 +0000 (UTC) Received: from localhost (m5-242-216-138.cust.tele2.se [5.242.216.138]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 1E197607A7; Wed, 1 Mar 2023 14:40:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bokr.com; s=easymail; t=1677681646; bh=aSnO0hUMDSRAO/Q9x4DPhpYfcTyUVReRqiKFXPv/FPE=; h=From:Date:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=h2B0mIX226t+bZT83NVciZWyxQFBCD2H0ZDkyGa27EZ6w1zlaUCWO51/CqzJcQSKA y38B7CP1SbiJAbjRfiqr/jKsM3Nrv7gYBBw1vTDvbkTGvZYkgp4psSx+9UQDXCL9T6 yd91AY4woOqwc/Mu14dLTnMqJAtACT7x1N5f3qTfrO3I6l8aRFZxi82kZuq30yem3/ SABBlojeEj0Ttj5yixYA1hGQPZpd0AT+blHEGFK/QKry+op34gbW3w1kNRzj5Lt14h X95+q1r2uCm3mmAp+9pTFo5wVrLlKEza8/zYg9/a9gPLGQ+jCBKlfYicOzHvd9v2qX uluEf8PzXY5PA== From: bokr@bokr.com Date: Wed, 1 Mar 2023 15:40:28 +0100 To: Csepp Subject: Re: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues Message-ID: <20230301144027.GA37832@LionPure> References: <87bkld896j.fsf@riseup.net> <6525e61f911b5c03547594432ff9102636c9a5cf.camel@ist.tugraz.at> <87ilfklns5.fsf@riseup.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <87ilfklns5.fsf@riseup.net> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 61882 Cc: Liliana Marie Prikler , 61882@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: bokr@bokr.com Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) Hi, On +2023-03-01 12:16:56 +0100, Csepp wrote: [...] > How the hell would my paths affect what's in the bin folder? Like, the > flatpak binary is literally not present in the profile, that's why it's > not showing up in $PATH. Could something in one of your path directories accidentally have gotten a name starting with '-' ? (or full name '-')? Surprising things can happen depending on how an app rejects an unexpected option, or tries to use it :) BTW: If you can't delete a file named '-' try emacs dirmode. IIRC emacs seems to see anything and be able to delete it. Do you have any scripts that are both sourced and executed? If so, are they doing return or exit respectively or something trickier as intended? -- Regards, Bengt Richter From debbugs-submit-bounces@debbugs.gnu.org Wed Mar 01 11:25:28 2023 Received: (at 61882) by debbugs.gnu.org; 1 Mar 2023 16:25:28 +0000 Received: from localhost ([127.0.0.1]:54764 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXPGh-0001MM-Ur for submit@debbugs.gnu.org; Wed, 01 Mar 2023 11:25:28 -0500 Received: from mx0.riseup.net ([198.252.153.6]:39216) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXPGe-0001M4-1B for 61882@debbugs.gnu.org; Wed, 01 Mar 2023 11:25:26 -0500 Received: from fews2.riseup.net (fews2-pn.riseup.net [10.0.1.84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx0.riseup.net (Postfix) with ESMTPS id 4PRfjB0nntz9t2X; Wed, 1 Mar 2023 16:25:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1677687918; bh=zo2hU3i1I9+I8EIe6AbK09UPGZ3hD+AbGQCpn9f74js=; h=References:From:To:Cc:Subject:Date:In-reply-to:From; b=q/G/QLM/CeTp6fvaCRRdE+O1XGGv6Qw5VEMhbLsAojWMIpNqraEiaSy4fueCNCw4L iI2mo3bTRPu6Xbkqm3Gv68ykpyTZRKLAHWttZlLaBBdMPjjBmgizRC7VgAErP0TPbM 8uJ/zXhRYxHB5sijkZmnACBnM/hk1z3CLu27yA00= X-Riseup-User-ID: D35D44672FD7BCE7EC3CDF5B87E069B683258AE5177455C5C47E19B4DEF72177 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews2.riseup.net (Postfix) with ESMTPSA id 4PRfj90rldz1y8Z; Wed, 1 Mar 2023 16:25:16 +0000 (UTC) References: <87bkld896j.fsf@riseup.net> <6525e61f911b5c03547594432ff9102636c9a5cf.camel@ist.tugraz.at> <87ilfklns5.fsf@riseup.net> <20230301144027.GA37832@LionPure> From: Csepp To: bokr@bokr.com Subject: Re: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues Date: Wed, 01 Mar 2023 17:11:12 +0100 In-reply-to: <20230301144027.GA37832@LionPure> Message-ID: <87edq8sal2.fsf@riseup.net> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 61882 Cc: Liliana Marie Prikler , 61882@debbugs.gnu.org, Csepp X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) bokr@bokr.com writes: > Hi, > > On +2023-03-01 12:16:56 +0100, Csepp wrote: > [...] >> How the hell would my paths affect what's in the bin folder? Like, the >> flatpak binary is literally not present in the profile, that's why it's >> not showing up in $PATH. > > Could something in one of your path directories > accidentally have gotten a name starting with '-' ? > (or full name '-')? > > Surprising things can happen depending on how an > app rejects an unexpected option, or tries to use it :) > > BTW: If you can't delete a file named '-' > try emacs dirmode. IIRC emacs seems to see > anything and be able to delete it. > > Do you have any scripts that are both sourced and executed? > If so, are they doing return or exit respectively or > something trickier as intended? So, first things first: % guix package -I | grep -E '(flatpak|roam)' emacs-org-roam 2.2.2-0.74422df out /gnu/store/bxxjy8ydm62fr0bckxfrj27xnlvqbfmy-emacs-org-roam-2.2.2-0.74422df flatpak 1.14.1 out /gnu/store/mf0k987xvpgk79l74lmdjv9jz8gy8cdf-flatpak-1.14.1 Both are installed. ls $(guix build flatpak)/bin/ flatpak flatpak-bisect flatpak-coredumpctl The store paths also match. This path also exists: $(guix build emacs-org-roam)/share/emacs/site-lisp/org-roam-2.2.2-0.74422df I don't know the details of how Emacs loads things, but org-roam has an org-roam-autoloads.el while lsp-mode (a package that does work) does not. Some relevant paths: EMACSLOADPATH=/home/raingloom/.guix-profile/share/emacs/site-lisp PATH=/home/raingloom/.local/bin:/run/setuid-programs:/home/raingloom/.config/guix/current/bin:/home/raingloom/.guix-profile/bin:/home/raingloom/.guix-profile/sbin:/run/current-system/profile/bin:/run/current-system/profile/sbin The only additional item is on PATH and at worst it would shadow an existing flatpak binary. But it doesn't, there is just a single utility script there that I should probably get rid of. Also: guix shell --check -p .guix-profile This seems to hang. Or at least it's taking an awful long time for something so simple. I'm running Guix as my system distro and I'm not in the habit of adding random junk to my dotfiles, so I would be rather surprised if this turned out to be a path issue, especially when it's obvious the packages are literally not even showing up in the profile they are supposed to show up in. % ls ~/.guix-profile/share/emacs/site-lisp/ This does not print any org-roam directory. From debbugs-submit-bounces@debbugs.gnu.org Thu Mar 02 02:11:24 2023 Received: (at 61882) by debbugs.gnu.org; 2 Mar 2023 07:11:25 +0000 Received: from localhost ([127.0.0.1]:55654 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXd64-0004JR-Aj for submit@debbugs.gnu.org; Thu, 02 Mar 2023 02:11:24 -0500 Received: from mailrelay.tugraz.at ([129.27.2.202]:45626) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXd61-0004JA-M3 for 61882@debbugs.gnu.org; Thu, 02 Mar 2023 02:11:22 -0500 Received: from lprikler-laptop.ist.intra (gw.ist.tugraz.at [129.27.202.101]) by mailrelay.tugraz.at (Postfix) with ESMTPSA id 4PS2MT2tYYz3whG; Thu, 2 Mar 2023 08:11:17 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tugraz.at; s=mailrelay; t=1677741077; bh=afpNiULnBSPRmBMkZ933531wae8W6drFEPve/Zz4WmI=; h=Subject:From:To:Cc:Date:In-Reply-To:References; b=Q6yGBluNKrkkZ5PWjcJmzUW7nqXjr9wUkIBWZvZWhPV57lfEyBAMqSpz5zR0Ttjk1 ePb/LNSouqVnBIHDsaijaxIvMFbkbp1GLPYZ4Q7sUKUPsndCTcR46NbDPwJPkokue8 H6wHHit9ezbujOXYLfopsosr3rT1glE+CZLtMzDQ= Message-ID: <19974c7f997015c1c19c2ebf305996ea32af0199.camel@ist.tugraz.at> Subject: Re: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues From: Liliana Marie Prikler To: Csepp , bokr@bokr.com Date: Thu, 02 Mar 2023 08:11:16 +0100 In-Reply-To: <87edq8sal2.fsf@riseup.net> References: <87bkld896j.fsf@riseup.net> <6525e61f911b5c03547594432ff9102636c9a5cf.camel@ist.tugraz.at> <87ilfklns5.fsf@riseup.net> <20230301144027.GA37832@LionPure> <87edq8sal2.fsf@riseup.net> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.0 MIME-Version: 1.0 X-TUG-Backscatter-control: waObeELIUl4ypBWmcn/8wQ X-Spam-Scanner: SpamAssassin 3.003001 X-Spam-Score-relay: -1.9 X-Scanned-By: MIMEDefang 2.74 on 129.27.10.117 X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 61882 Cc: 61882@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) Am Mittwoch, dem 01.03.2023 um 17:11 +0100 schrieb Csepp: >=20 > bokr@bokr.com=C2=A0writes: >=20 > > Hi, > >=20 > > On +2023-03-01 12:16:56 +0100, Csepp wrote: > > [...] > > > How the hell would my paths affect what's in the bin folder?=C2=A0 > > > Like, the flatpak binary is literally not present in the profile, > > > that's why it's not showing up in $PATH. > >=20 > > Could something in one of your path directories > > accidentally have gotten a name starting with '-' ? > > (or full name '-')? > >=20 > > Surprising things can happen depending on how an > > app rejects an unexpected option, or tries to use it :) > >=20 > > BTW: If you can't delete a file named '-' > > =C2=A0=C2=A0=C2=A0=C2=A0 try emacs dirmode. IIRC emacs seems to see > > =C2=A0=C2=A0=C2=A0=C2=A0 anything and be able to delete it. > >=20 > > Do you have any scripts that are both sourced and executed? > > If so, are they doing return or exit respectively or > > something trickier as intended? >=20 > So, first things first: > % guix package -I | grep -E '(flatpak|roam)' > emacs-org-roam=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A02.2.2- > 0.74422df=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0out=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0/gn= u/store/bxxjy8ydm62fr0bckxfrj27x > nlvqbfmy-emacs-org-roam-2.2.2-0.74422df > flatpak=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A01.14.1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= out=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0/gnu/ > store/mf0k987xvpgk79l74lmdjv9jz8gy8cdf-flatpak-1.14.1 >=20 > Both are installed. >=20 > ls $(guix build flatpak)/bin/ > flatpak=C2=A0 flatpak-bisect=C2=A0 flatpak-coredumpctl >=20 > The store paths also match. >=20 > This path also exists: > $(guix build emacs-org-roam)/share/emacs/site-lisp/org-roam-2.2.2- > 0.74422df You're comparing apples to oranges here. `guix build' need not reproduce the contents of your profile, especially if you pulled a new version of guix in between. Instead, try listing the contents of the reported store paths. As for `guix build' and `guix shell' producing different results within a single generation, the only instance I know of which has this requires the presence of grafts (and IIRC might already be fixed?) > I don't know the details of how Emacs loads things, but org-roam has > an org-roam-autoloads.el while lsp-mode (a package that does work) > does not. There ought to be a subdirs.el in your $GUIX_PROFILE/share/emacs/site- lisp, which explicitly mentions the directories to add to your load path. These are store paths. Thus, even in the off chance that some symlink in your profile is gone (which I'd find highly alerting in the first place), it should correctly see the package to add. > Some relevant paths: > EMACSLOADPATH=3D/home/raingloom/.guix-profile/share/emacs/site-lisp > PATH=3D/home/raingloom/.local/bin:/run/setuid- > programs:/home/raingloom/.config/guix/current/bin:/home/raingloom/.gu > ix-profile/bin:/home/raingloom/.guix-profile/sbin:/run/current- > system/profile/bin:/run/current-system/profile/sbin >=20 > The only additional item is on PATH and at worst it would shadow an > existing flatpak binary.=C2=A0 But it doesn't, there is just a single > utility > script there that I should probably get rid of. >=20 > Also: > guix shell --check -p .guix-profile > This seems to hang.=C2=A0 Or at least it's taking an awful long time for > something so simple. You could try something easier like the aforementioned `guix shell emacs-next-pgtk emacs-org-roam --pure --check'. > I'm running Guix as my system distro and I'm not in the habit of > adding random junk to my dotfiles, so I would be rather surprised if > this turned out to be a path issue Good to know. > especially when it's obvious the packages are literally not even > showing up in the profile they are supposed to show up in. This was not obvious from your previous report, which see > emacs-org-roam is installed in my default profile and all the other > emacs packages work with the emacs-next-pgtk package in the same > profile. > guix shell emacs-org-roam emacs-next-pgtk does not work, guix shell > emacs-org-roam emacs does. Basing my response on this rather than the otherwise inconsequential bit about flatpak, it would appear as though you are reporting a bug specific to emacs-next-pgtk rather than emacs-org-roam. > % ls ~/.guix-profile/share/emacs/site-lisp/ >=20 > This does not print any org-roam directory. Which leads me to believe that $ ls /gnu/store/bxxjy8ydm62fr0bckxfrj27xnlvqbfmy-emacs-org-roam-2.2.2- 0.74422df/share/emacs/site-lisp does not report any such directory either. If that is indeed the case, try `guix build --repair'-ing it. This still does not explain the different behaviour of emacs vs. emacs- next-pgtk in your shell, which has further debugging complexities due to the lack of isolation. Cheers From debbugs-submit-bounces@debbugs.gnu.org Thu Mar 02 07:49:34 2023 Received: (at 61882) by debbugs.gnu.org; 2 Mar 2023 12:49:34 +0000 Received: from localhost ([127.0.0.1]:56085 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXiNK-00073b-4a for submit@debbugs.gnu.org; Thu, 02 Mar 2023 07:49:34 -0500 Received: from mx1.riseup.net ([198.252.153.129]:36786) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXiNI-00073M-TM for 61882@debbugs.gnu.org; Thu, 02 Mar 2023 07:49:33 -0500 Received: from fews2.riseup.net (fews2-pn.riseup.net [10.0.1.84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 4PS9sR5p0LzDrlK; Thu, 2 Mar 2023 12:49:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1677761366; bh=4iojBqR2ss6YnHvSGDZmUDBgolQLHOaemFX8YFuFsDg=; h=References:From:To:Cc:Subject:Date:In-reply-to:From; b=l8R9qgO4z5EGocTxrIXyLbTEJFxgtLN1QwzODjLVxZxnBKJvhhOfFT0XPXdHrYVHn UynOt2dJK4KP8jsNNNi8XvT2UmfumHUoZKpwCtLtRzjJpyDM0ivvxjb8mlz1Yoae4z e+TV+x5HIMBcHzt2QUADQJoLSSBDVVJSEjWB6pPg= X-Riseup-User-ID: 2F74145C3773B8A0335FC6EF95739127E1A1B262D24B89192433D92195515415 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews2.riseup.net (Postfix) with ESMTPSA id 4PS9sQ6LcMz1yBT; Thu, 2 Mar 2023 12:49:14 +0000 (UTC) References: <87bkld896j.fsf@riseup.net> <6525e61f911b5c03547594432ff9102636c9a5cf.camel@ist.tugraz.at> <87ilfklns5.fsf@riseup.net> <20230301144027.GA37832@LionPure> <87edq8sal2.fsf@riseup.net> <19974c7f997015c1c19c2ebf305996ea32af0199.camel@ist.tugraz.at> From: Csepp To: Liliana Marie Prikler Subject: Re: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues Date: Thu, 02 Mar 2023 13:39:54 +0100 In-reply-to: <19974c7f997015c1c19c2ebf305996ea32af0199.camel@ist.tugraz.at> Message-ID: <87a60v9v3z.fsf@riseup.net> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 61882 Cc: 61882@debbugs.gnu.org, bokr@bokr.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Liliana Marie Prikler writes: >> % ls ~/.guix-profile/share/emacs/site-lisp/ >> >> This does not print any org-roam directory. > Which leads me to believe that > $ ls /gnu/store/bxxjy8ydm62fr0bckxfrj27xnlvqbfmy-emacs-org-roam-2.2.2- > 0.74422df/share/emacs/site-lisp > does not report any such directory either. It definitely reports it, I just didn't paste the result to save space. I'll try running a repair when I get home, since FS corruption could lead to any kind of weird behaviour, but I haven't had any corruption on that machine ever, BTRFS has been pretty reliable for me. Sorry for being so grumpy, I guess I should have highlighted the profile corruption thing over the emacs-next-pgtk specific bits. From debbugs-submit-bounces@debbugs.gnu.org Thu Apr 06 12:11:09 2023 Received: (at 61882) by debbugs.gnu.org; 6 Apr 2023 16:11:09 +0000 Received: from localhost ([127.0.0.1]:54796 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pkSCZ-00019E-0a for submit@debbugs.gnu.org; Thu, 06 Apr 2023 12:11:09 -0400 Received: from mx0.riseup.net ([198.252.153.6]:38714) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pkSCT-00018C-76 for 61882@debbugs.gnu.org; Thu, 06 Apr 2023 12:11:05 -0400 Received: from fews2.riseup.net (fews2-pn.riseup.net [10.0.1.84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx0.riseup.net (Postfix) with ESMTPS id 4Psmgz2jsjz9s8t for <61882@debbugs.gnu.org>; Thu, 6 Apr 2023 16:10:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1680797455; bh=BhEYdo3/dOb3VNKUFXvJsWiDs/Wphre5hRN/hdD2iV8=; h=References:From:To:Subject:Date:In-reply-to:From; b=ZOplWr9UEgeSqxv5aXCOOqfAbFr8LGHDDtDYylBzBT1UwnXB8g8rBIwT9YfG9zB3g v9t6VpdKcn63m3tS02Uy0g2FADVgOI00maUNxmKRcGWydgtdruWJ3LHGE3T7y2yh3k 1SXPN8sVw5/ZPdkH4oEj7w/fvTN984ttmmPoTsCE= X-Riseup-User-ID: DF474E2692F6B3698E19720E8108ADC6179D891A1DAE2947B4AC57B38F5C86BA Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews2.riseup.net (Postfix) with ESMTPSA id 4Psmgy53VKz1yTY for <61882@debbugs.gnu.org>; Thu, 6 Apr 2023 16:10:54 +0000 (UTC) References: <87bkld896j.fsf@riseup.net> From: Csepp To: 61882@debbugs.gnu.org Subject: profile is frozen / packages can't be installed Date: Thu, 06 Apr 2023 16:59:41 +0200 In-reply-to: Message-ID: <875ya92dpz.fsf@riseup.net> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 61882 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) (Jump forward a bit, this is a bit stream-of-consciousness-y, I wrote things down as I was debugging things. TLDR: profile got corrupted somehow, it's not related to the packages themselves.) Certain packages like flatpak do not get installed in my main user profile for some unknown reason. So far they are: * gallery-dl * flatpak * emacs-org-roam It has been happening for at least a month across several pulls. If I export a manifest and load it in either guix shell -m or guix package -m to a different profile, bin/flatpak exists, if I do guix package -m without a profile argument or with the profile set to the default user profile, bin/flatpak is missing. The packages that are broken are always the same. If I create a manifest with only the broken packages, guix package -I reports exactly those packages, but when I look in ~/.guix-profile/bin it still has a bunch of other packages in it. So it seems the profile is frozen? I have no idea how this could happen. guix package --list-generations reports three generations, but there is only one generation in my home directory, called .guix-profile-1-link. There is also a .guix-profile.lock, maybe that's related? I see no lock for the other profile with the same manifest. Removed the lock, tried guix package -m again, still don't have flatpak, still only one generation symlink. Deleted all the symlinks, ran guix package -m, now it works. I'm gonna hold off on running the GC for a few days, if anyone has an idea of where the bug is and wants me to upload some files, I can do it until then. For my own reference, this is the store item of the broken profile: /gnu/store/0w3jxl95cchxn14zph3lmnqwmijf8971-profile From debbugs-submit-bounces@debbugs.gnu.org Tue Oct 03 22:54:51 2023 Received: (at 61882-done) by debbugs.gnu.org; 4 Oct 2023 02:54:51 +0000 Received: from localhost ([127.0.0.1]:41061 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qns2E-0006aG-U5 for submit@debbugs.gnu.org; Tue, 03 Oct 2023 22:54:51 -0400 Received: from mail-qv1-xf2a.google.com ([2607:f8b0:4864:20::f2a]:55567) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qns2C-0006Zy-SO; Tue, 03 Oct 2023 22:54:49 -0400 Received: by mail-qv1-xf2a.google.com with SMTP id 6a1803df08f44-65afd8af8bbso10337826d6.3; Tue, 03 Oct 2023 19:54:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696388065; x=1696992865; darn=debbugs.gnu.org; h=mime-version:user-agent:message-id:in-reply-to:date:references :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=21x+XseXOsrCHTla+0wxOHSBLerZoBYivDFchYsL/Zw=; b=RycmOw6UOaAZTf9WpSMEkc2tGAKFQJJhj9ZsmbFPsmBelXpXBXQWg+FJjxJLwucENN YyNeKDmiLLWzFiqpqLlVBdNoQ/JdcT7uKxUhkSxSIK8SMEN6F4dKi51ksJEPbi4noZtd FO50qPj/Ro7rtji/DvfpDjzzq1ojmBSWP8o+qP+9XRR8xKzee1w9oHikxsTp99/Z/w+H LnAz5ziVMqBGNnKQVqoeAfuFjZVTkUuo0dqGbFiVfXfhULhnDfsGja9m9NxUrpvVJ47V aDq7Noo6tEY5lFftzpZ4qBBD6ObTs3JVtF3r5FvYkiuZfmLQPUz2+z8S8uzF25kO3cFg /6cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696388065; x=1696992865; h=mime-version:user-agent:message-id:in-reply-to:date:references :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=21x+XseXOsrCHTla+0wxOHSBLerZoBYivDFchYsL/Zw=; b=iXKnBa8Vr5th9iVj05rShASxv2FWXYJSL3UnolNeBj6EkjXiR1gngtq3WY1Cjp1i2O K9bPWKBgZK60F5FpQ2OukXYww250/58ohcDFDqSTrExkHrNiqE5E9INJbKkIZkQBGWCR d/R5WhKO/btezYbKjXbG5c5F86thtG7Xr2Cg63kMJ0aYcepAseLgR4BDPJnrgHk6iN4e bWLcfT2sBeXOgIOZ749TnW0yDyC4VmFXpfGFt8sPK+TXZ5/HxVaRzCzx+2ktrpWGpC4p i1qYOKNWuA2SKCljxDoSkspMwoxmGNdX40oBzBG4nVGvw4dpSTLXn82+1JpubznMEyF5 yAEg== X-Gm-Message-State: AOJu0YzVEWf2JOtLIP9CEMPegsiG/40LHr8ZnWuRlyKMnrJJrEKXkmyC 178sYa10ulgxHF/1XhK6q0Cd6v0m1iA= X-Google-Smtp-Source: AGHT+IENDNGpRuJ5QFSqAcIwwI63g1GwWdmHLCrCdoaIi1Rt1tHTG7htRyug5q4+KU2XqAw102C8Yw== X-Received: by 2002:a0c:b411:0:b0:658:8cc0:ddc3 with SMTP id u17-20020a0cb411000000b006588cc0ddc3mr980810qve.62.1696388065153; Tue, 03 Oct 2023 19:54:25 -0700 (PDT) Received: from hurd (dsl-141-24.b2b2c.ca. [66.158.141.24]) by smtp.gmail.com with ESMTPSA id a3-20020a05620a16c300b0076efaec147csm945242qkn.45.2023.10.03.19.54.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 03 Oct 2023 19:54:24 -0700 (PDT) From: Maxim Cournoyer To: Csepp Subject: Re: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues References: <87bkld896j.fsf@riseup.net> <875ya92dpz.fsf@riseup.net> Date: Tue, 03 Oct 2023 22:54:23 -0400 In-Reply-To: <875ya92dpz.fsf@riseup.net> (Csepp's message of "Thu, 06 Apr 2023 16:59:41 +0200") Message-ID: <87v8bn3xnk.fsf_-_@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 61882-done Cc: GNU Debbugs , 61882-done@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) tags 61882 +notabug quit Hello, Csepp writes: > (Jump forward a bit, this is a bit stream-of-consciousness-y, I wrote > things down as I was debugging things. TLDR: profile got corrupted > somehow, it's not related to the packages themselves.) > > Certain packages like flatpak do not get installed in my main user > profile for some unknown reason. > So far they are: > * gallery-dl > * flatpak > * emacs-org-roam > > It has been happening for at least a month across several pulls. > > If I export a manifest and load it in either guix shell -m or guix > package -m to a different profile, bin/flatpak exists, if I do guix > package -m without a profile argument or with the profile set to the > default user profile, bin/flatpak is missing. > > The packages that are broken are always the same. > > If I create a manifest with only the broken packages, guix package -I > reports exactly those packages, but when I look in ~/.guix-profile/bin > it still has a bunch of other packages in it. > > So it seems the profile is frozen? I have no idea how this could > happen. > > guix package --list-generations reports three generations, but there is > only one generation in my home directory, called .guix-profile-1-link. > > There is also a .guix-profile.lock, maybe that's related? > I see no lock for the other profile with the same manifest. > > Removed the lock, tried guix package -m again, still don't have flatpak, > still only one generation symlink. > > Deleted all the symlinks, ran guix package -m, now it works. > > I'm gonna hold off on running the GC for a few days, if anyone has an > idea of where the bug is and wants me to upload some files, I can do it > until then. > For my own reference, this is the store item of the broken profile: > /gnu/store/0w3jxl95cchxn14zph3lmnqwmijf8971-profile Did you have any corruption at the FS level or something equally bad? Were you using a different Guix in between the 'guix package -m' attempts? If the profile was in the cache, it wouldn't rebuild it, and you'd be stuck with your broken version. I'm closing this, as I we don't have much to push the investigation further, but if you have a more precise idea of what happened and ways to reproduce that do reopen. -- Thanks, Maxim From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 08 10:36:53 2023 Received: (at 61882-done) by debbugs.gnu.org; 8 Oct 2023 14:36:53 +0000 Received: from localhost ([127.0.0.1]:58246 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qpUto-0002SD-L9 for submit@debbugs.gnu.org; Sun, 08 Oct 2023 10:36:53 -0400 Received: from mx0.riseup.net ([198.252.153.6]:50054) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qpUtn-0002Ry-9H for 61882-done@debbugs.gnu.org; Sun, 08 Oct 2023 10:36:52 -0400 Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4S3PqY1LHQz9sYT; Sun, 8 Oct 2023 14:36:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1696775785; bh=N74nSsWO1/OSVzNGWAczXm1aHp0d7j5Kv/eihuRCnJU=; h=References:From:To:Cc:Subject:Date:In-reply-to:From; b=Q7eYNm5z+js0HWjyXaN46qY6xre5XUDbNAOhKWa8GXhsx/okqbchGsY2sKYkD0Iwy yuGImAJPfAsciLfaDuhq/72GuGrLWjnVgoox0Q0Q86zo7Vdh2zyBROMWTQUOZeuuna QoW4M0FFVPx1z4MdgBLPni9cud2Mln8nG5ZOFUts= X-Riseup-User-ID: A90ED5F54C5FD24A2F2E7ECE00908EB2995377D4246DAB135CCE5A8926D536BA Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4S3PqX391DzJmlV; Sun, 8 Oct 2023 14:36:24 +0000 (UTC) References: <87bkld896j.fsf@riseup.net> <875ya92dpz.fsf@riseup.net> <87v8bn3xnk.fsf_-_@gmail.com> From: Csepp To: Maxim Cournoyer Subject: Re: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues Date: Sun, 08 Oct 2023 16:29:36 +0200 In-reply-to: <87v8bn3xnk.fsf_-_@gmail.com> Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 61882-done Cc: 61882-done@debbugs.gnu.org, Csepp X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Maxim Cournoyer writes: > tags 61882 +notabug > quit I don't think notabug applies until we actually know the root cause. > Hello, > > Csepp writes: > >> (Jump forward a bit, this is a bit stream-of-consciousness-y, I >> wrote >> things down as I was debugging things. TLDR: profile got corrupted >> somehow, it's not related to the packages themselves.) >> >> Certain packages like flatpak do not get installed in my main user >> profile for some unknown reason. >> So far they are: >> * gallery-dl >> * flatpak >> * emacs-org-roam >> >> It has been happening for at least a month across several pulls. >> >> If I export a manifest and load it in either guix shell -m or guix >> package -m to a different profile, bin/flatpak exists, if I do guix >> package -m without a profile argument or with the profile set to the >> default user profile, bin/flatpak is missing. >> >> The packages that are broken are always the same. >> >> If I create a manifest with only the broken packages, guix package >> -I >> reports exactly those packages, but when I look in >> ~/.guix-profile/bin >> it still has a bunch of other packages in it. >> >> So it seems the profile is frozen? I have no idea how this could >> happen. >> >> guix package --list-generations reports three generations, but there >> is >> only one generation in my home directory, called >> .guix-profile-1-link. >> >> There is also a .guix-profile.lock, maybe that's related? >> I see no lock for the other profile with the same manifest. >> >> Removed the lock, tried guix package -m again, still don't have >> flatpak, >> still only one generation symlink. >> >> Deleted all the symlinks, ran guix package -m, now it works. >> >> I'm gonna hold off on running the GC for a few days, if anyone has >> an >> idea of where the bug is and wants me to upload some files, I can do >> it >> until then. >> For my own reference, this is the store item of the broken profile: >> /gnu/store/0w3jxl95cchxn14zph3lmnqwmijf8971-profile > > Did you have any corruption at the FS level or something equally bad? > Were you using a different Guix in between the 'guix package -m' > attempts? If the profile was in the cache, it wouldn't rebuild it, > and you'd be stuck with your broken version. > > I'm closing this, as I we don't have much to push the > investigation further, but if you have a more precise idea of what > happened and ways to reproduce that do reopen. I'm pretty sure I already went through these, but once again, to be sure: - no there was no file system corruption as far as I could tell - store was checked for corruption multiple times - the issue persisted through multiple guix pulls - only one profile was affected From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 08 16:52:02 2023 Received: (at 61882-done) by debbugs.gnu.org; 8 Oct 2023 20:52:02 +0000 Received: from localhost ([127.0.0.1]:58759 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qpaks-0003fX-BR for submit@debbugs.gnu.org; Sun, 08 Oct 2023 16:52:02 -0400 Received: from mail-qt1-x834.google.com ([2607:f8b0:4864:20::834]:52240) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qpakq-0003f8-T9 for 61882-done@debbugs.gnu.org; Sun, 08 Oct 2023 16:52:01 -0400 Received: by mail-qt1-x834.google.com with SMTP id d75a77b69052e-417f872fb94so28233311cf.0 for <61882-done@debbugs.gnu.org>; Sun, 08 Oct 2023 13:51:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696798295; x=1697403095; darn=debbugs.gnu.org; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=6yoV3meGIzmSGceFjQ5E586G8ruOJX8UMYR7RKAsjDs=; b=kp1JAxT6pq1Xf9Kd0AFNbkO0jx7ndX+GtvGqlUNcqZtxzJMGPsOVy6wcgTZlSkNPYx 3p0fWPREk3I312CfECPuHe9wgOcIJlBvkGWF9dOa2rWFkZiI2XmoyhifBgr1Z2na8N5v pa3vzRvFGjQ0Ylz2iDek9luvJ8brVjOU34UDnvFzsB1yb7H1iXrKGLA9kF9om+GxeiLq laNJIUh9DhRLiZwuW2PbcG2VAQIkjzkc5db27BcXF0ac6+g/pw+FWsyp2BlL8VUZ8hUR 8KQ3K5aaHCw2ZXJyzj+o+Po3JN5JIpKQlwYx5/9TrQ2SQiMBMF1AdElEpsegQwCZrans IYFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696798295; x=1697403095; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=6yoV3meGIzmSGceFjQ5E586G8ruOJX8UMYR7RKAsjDs=; b=cvguN/BYZK39J64lXt+ZwyFse7iul4ZOJrZDViqjEUddl66AeLo+2FdAEKbZAtQN6Z ntlWEwyYPa/x6Ti5UTEeOYiUC9gvZeWxuvVVCBjmZQYv0GQgEghmyM0Wy8f8bTI2kQtF g/mtlIN67jdWDUrnXXEhZjv/YmXzJ1cFtSOzkOnq83Jh52xd3Jiyj8lD/4Tpx287Jla7 JR88Fb4lkPcddD/1FSYiBpD0Ae+AoIQDiQe4Qd0T4QXUUkQGWSBvjFwWe3pF+gY4yoVv GWlUlEJJmMNId8peORFqQ83PSHaPMunVXBHXzzQwx3uPUYjuePe4QD/gBrRv42LNXscW Todg== X-Gm-Message-State: AOJu0YyC3Djw5isMhiDp3SbROTzlbRqmmpzsCkLJvvV1g4xLSDbMWjkL oK2mDjMlu+FWerOTV8HJNThBH05FbfY= X-Google-Smtp-Source: AGHT+IFVf+zVfxoUmABeGa0+oe70j5SELzR1dANc8lV34CprDvaX6Y68p5eovukylijWLoAqwgn+hw== X-Received: by 2002:a05:622a:4cb:b0:414:68a7:9d98 with SMTP id q11-20020a05622a04cb00b0041468a79d98mr16394170qtx.67.1696798294800; Sun, 08 Oct 2023 13:51:34 -0700 (PDT) Received: from hurd (dsl-158-21.b2b2c.ca. [66.158.158.21]) by smtp.gmail.com with ESMTPSA id x15-20020a0ce0cf000000b0065b2e561c17sm3267612qvk.123.2023.10.08.13.51.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 08 Oct 2023 13:51:34 -0700 (PDT) From: Maxim Cournoyer To: Csepp Subject: Re: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues In-Reply-To: (Csepp's message of "Sun, 08 Oct 2023 16:29:36 +0200") References: <87bkld896j.fsf@riseup.net> <875ya92dpz.fsf@riseup.net> <87v8bn3xnk.fsf_-_@gmail.com> Date: Sun, 08 Oct 2023 16:51:32 -0400 Message-ID: <871qe4et2j.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 61882-done Cc: 61882-done@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hi, Csepp writes: > Maxim Cournoyer writes: > >> tags 61882 +notabug >> quit > > I don't think notabug applies until we actually know the root cause. Sadly I don't think there's anything actionable here until you can reproduce the problem and share the recipe with us, so I wanted to close the issue without it being marked as "resolved". -- Thanks, Maxim From debbugs-submit-bounces@debbugs.gnu.org Tue Oct 10 19:02:38 2023 Received: (at 61882-done) by debbugs.gnu.org; 10 Oct 2023 23:02:38 +0000 Received: from localhost ([127.0.0.1]:37094 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qqLkM-0007cI-G9 for submit@debbugs.gnu.org; Tue, 10 Oct 2023 19:02:38 -0400 Received: from mx1.riseup.net ([198.252.153.129]:38768) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qqLkK-0007c4-02 for 61882-done@debbugs.gnu.org; Tue, 10 Oct 2023 19:02:37 -0400 Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4S4ry85CvBzDqjL; Tue, 10 Oct 2023 23:02:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1696978928; bh=Rr+5K0G4mzoYWq3vzxqxD/t5W6U3zxbHLZinY1WvV5k=; h=References:From:To:Cc:Subject:Date:In-reply-to:From; b=G8Y5AsnS/BW5HoA0vkD09zKM4czxrtKHB5+r93ZerjFCv9iKLTsleLftvfTFQ+gey 3HU+JqyCq1t/NIdl0AnwMKVlt7+RPn/FC3Qu91NJv62Q9TjrLNU9qvji7ctzdYwqyF 8tvux5cLKMIEpzeEn0u0g/gIvTT/mb3/3bJ507dY= X-Riseup-User-ID: 38BF73C6CA9BE58971B6705C555CB6E312F3AE179192B8C3140B5512E5B42BFF Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4S4rxx0BxTzJmhX; Tue, 10 Oct 2023 23:01:56 +0000 (UTC) References: <87bkld896j.fsf@riseup.net> <875ya92dpz.fsf@riseup.net> <87v8bn3xnk.fsf_-_@gmail.com> <871qe4et2j.fsf@gmail.com> From: Csepp To: Maxim Cournoyer Subject: Re: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues Date: Wed, 11 Oct 2023 00:52:51 +0200 In-reply-to: <871qe4et2j.fsf@gmail.com> Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 61882-done Cc: 61882-done@debbugs.gnu.org, Csepp X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Maxim Cournoyer writes: > Hi, > > Csepp writes: > >> Maxim Cournoyer writes: >> >>> tags 61882 +notabug >>> quit >> >> I don't think notabug applies until we actually know the root cause. > > Sadly I don't think there's anything actionable here until you can > reproduce the problem and share the recipe with us, so I wanted to close > the issue without it being marked as "resolved". Neither "resolved" nor "notabug" are applicable. If stalled incident reports / issues are a problem, they should probably be marked as stalled, or needinfo, for easy filtering. Marking it as notabug is just going to make the job of the next person harder when they search for issues related to these symptoms. I appreciate all the work going into closing old issues, but I don't think chasing a low open issue count should be a goal unto itself See https://fvsch.com/stale-bots . From debbugs-submit-bounces@debbugs.gnu.org Tue Oct 10 21:47:46 2023 Received: (at 61882) by debbugs.gnu.org; 11 Oct 2023 01:47:46 +0000 Received: from localhost ([127.0.0.1]:37236 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qqOK9-0007dE-UD for submit@debbugs.gnu.org; Tue, 10 Oct 2023 21:47:46 -0400 Received: from mail-qk1-x736.google.com ([2607:f8b0:4864:20::736]:45541) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qqOK6-0007cq-Ch; Tue, 10 Oct 2023 21:47:44 -0400 Received: by mail-qk1-x736.google.com with SMTP id af79cd13be357-7740aa4b545so423664985a.3; Tue, 10 Oct 2023 18:47:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696988835; x=1697593635; darn=debbugs.gnu.org; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=3LjIai2QHbTwCCTqk6jdGcdHyKFI35AIP6e95JTXwbU=; b=PuIe4S81pAVsZD3Pf0c3buQ0uz1knUhXYtyfE6/dD9ZhVNJy/cdTjk8YSW90r1CWpK bkf24RS2D2kvQpkaj0qEn5DSAGt0NlX8rtayepxg6l4r89kjMxKe+9r1IEnap7iMmKE4 x0Ssa/EUHrvRpYyqWKza5Zm90K4BT5YStaCMI1hCzbBpqncy3TsyEAKcAvF/G3zauI2J er3LGEN+vGqHbuTfdQp6RgPDBBFONNKKDDGfyRQc3+CRo8ufyoVHHwTe5tKyJjqVAHaK HLbauogZVpiYNycQNIoxJkAeO1xQwJ8EB33+QCbgnjNgXbt54T+wYtwXYBz+2BIiFOke CH6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696988835; x=1697593635; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=3LjIai2QHbTwCCTqk6jdGcdHyKFI35AIP6e95JTXwbU=; b=qd4s9zIo66MCOqx4w6zGoKy14+gD53d8Vaj9ja+kX/7dhDn7Ek6c/eLP/LIHbjHCc9 MtpkReCHlVdSf2ifoa8AI1YNmz6atHgiUFxSRbbZ0/Yn/8vqk01tjfK/E+ukq7oOMF0x PzNemWEpr0RXrBiZwbSBearj93CoL+HdqFDkAEPAhlfjRcMXlTEr32VLU6JoDIQ4NczV b7ek+w7i7mEwmU1uGowvq9HDX4+AUnxKg1jptyl64LgwFv0nOI84Wb4LQMEoDzCoK0Es J9vJYrV+gvZKLsoSzivMyuz5xgAFIS2oKirudQi2PBocVJDCUVsfB4QNVYko93E3MzuM rMIg== X-Gm-Message-State: AOJu0Yx1o2JP3WAOXhx0z0whbGx2kdw90AwYBPMHjWeiMCmOMlZb0TUU mBuEbOXtvnuPttRc0ysg7V/ioCJuY00xBw== X-Google-Smtp-Source: AGHT+IFIYgR8sCpBVAdZMkje2EGfbaIUDVhDE1eNpTV1DJ7EyOsdRwJAbnYJqTNbqF96gCbznB8Huw== X-Received: by 2002:a05:620a:25cc:b0:768:11ff:7899 with SMTP id y12-20020a05620a25cc00b0076811ff7899mr23396685qko.64.1696988834788; Tue, 10 Oct 2023 18:47:14 -0700 (PDT) Received: from hurd (dsl-10-149-16.b2b2c.ca. [72.10.149.16]) by smtp.gmail.com with ESMTPSA id q27-20020a05620a039b00b007757eb88172sm4839317qkm.21.2023.10.10.18.47.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 10 Oct 2023 18:47:14 -0700 (PDT) From: Maxim Cournoyer To: Csepp Subject: Re: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues In-Reply-To: (Csepp's message of "Wed, 11 Oct 2023 00:52:51 +0200") References: <87bkld896j.fsf@riseup.net> <875ya92dpz.fsf@riseup.net> <87v8bn3xnk.fsf_-_@gmail.com> <871qe4et2j.fsf@gmail.com> Date: Tue, 10 Oct 2023 21:47:13 -0400 Message-ID: <8734yiexr2.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 61882 Cc: GNU Debbugs , 61882@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) tags 61882 = moreinfo unreproducible quit Hi, Csepp writes: > Maxim Cournoyer writes: > >> Hi, >> >> Csepp writes: >> >>> Maxim Cournoyer writes: >>> >>>> tags 61882 +notabug >>>> quit >>> >>> I don't think notabug applies until we actually know the root cause. >> >> Sadly I don't think there's anything actionable here until you can >> reproduce the problem and share the recipe with us, so I wanted to close >> the issue without it being marked as "resolved". > > Neither "resolved" nor "notabug" are applicable. If stalled incident > reports / issues are a problem, they should probably be marked as > stalled, or needinfo, for easy filtering. Marking it as notabug is just > going to make the job of the next person harder when they search for > issues related to these symptoms. I don't think a bug as particular as 'my profile got corrupted' without any way to recreate it has much value; it's also the first time I've heard of such a report. That's why I'd prefer to treat it as an oddity and close it; if it reproduces (by you or others) let's reopen it, with fresh and clear information. > I appreciate all the work going into closing old issues, but I don't > think chasing a low open issue count should be a goal unto itself > See https://fvsch.com/stale-bots . To be clear, I wholly agree. I've now tagged it as moreinfo and unreproducible. -- Thanks, Maxim From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 15 16:12:19 2023 Received: (at 61882) by debbugs.gnu.org; 15 Oct 2023 20:12:19 +0000 Received: from localhost ([127.0.0.1]:54179 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qs7TH-0005nw-6S for submit@debbugs.gnu.org; Sun, 15 Oct 2023 16:12:19 -0400 Received: from mx0.riseup.net ([198.252.153.6]:38360) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qs7TC-0005ng-Fi for 61882@debbugs.gnu.org; Sun, 15 Oct 2023 16:12:17 -0400 Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4S7rxD0HbPz9s3r; Sun, 15 Oct 2023 20:11:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1697400704; bh=hOWuJgA4RD8KG4Upeqkbwf9mo/G0/TSmhGxbs+k6ukE=; h=References:From:To:Cc:Subject:Date:In-reply-to:From; b=g8fN3msfPp+ANR47jmlnJnpWaFKCMQCTjQLTcpcMmHIDvNul3Fe8o9xFaOhNddqNS E24kY6UWVm+EUFK5+IConxN4pTMXv5iEIIrmAqSAtjJ72AdpKphLIVpVwnEp5A48JJ nV9vDTrhXZd98Jln2X6VOzHgal/RcMIHCzkfXSMI= X-Riseup-User-ID: 97B0C4D0321A5FDA747DEC98AE450EE523FA5A172E74D6ED78D74887A52EDFB4 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4S7rxC2KlczJnGc; Sun, 15 Oct 2023 20:11:43 +0000 (UTC) References: <87bkld896j.fsf@riseup.net> <875ya92dpz.fsf@riseup.net> <87v8bn3xnk.fsf_-_@gmail.com> <871qe4et2j.fsf@gmail.com> <8734yiexr2.fsf@gmail.com> From: Csepp To: Maxim Cournoyer Subject: Re: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues Date: Sun, 15 Oct 2023 22:06:50 +0200 In-reply-to: <8734yiexr2.fsf@gmail.com> Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 61882 Cc: 61882@debbugs.gnu.org, Csepp X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Maxim Cournoyer writes: > tags 61882 = moreinfo unreproducible > quit > > Hi, > > Csepp writes: > >> Maxim Cournoyer writes: >> >>> Hi, >>> >>> Csepp writes: >>> >>>> Maxim Cournoyer writes: >>>> >>>>> tags 61882 +notabug >>>>> quit >>>> >>>> I don't think notabug applies until we actually know the root >>>> cause. >>> >>> Sadly I don't think there's anything actionable here until you can >>> reproduce the problem and share the recipe with us, so I wanted to >>> close >>> the issue without it being marked as "resolved". >> >> Neither "resolved" nor "notabug" are applicable. If stalled incident >> reports / issues are a problem, they should probably be marked as >> stalled, or needinfo, for easy filtering. Marking it as notabug is >> just >> going to make the job of the next person harder when they search for >> issues related to these symptoms. > > I don't think a bug as particular as 'my profile got corrupted' > without > any way to recreate it has much value; it's also the first time I've > heard of such a report. That's why I'd prefer to treat it as an oddity > and close it; if it reproduces (by you or others) let's reopen it, > with > fresh and clear information. > >> I appreciate all the work going into closing old issues, but I don't >> think chasing a low open issue count should be a goal unto itself >> See https://fvsch.com/stale-bots . > > To be clear, I wholly agree. I've now tagged it as moreinfo and > unreproducible. It could be a file system bug, but while there are reports of BTRFS being unstable in certain RAID modes, I would be very surprised if there was a data corruption issue in the default single device mode. My hunch is that Guix's profile update logic is not actually as atomic as it's advertised and I interrupted it at the wrong moment. From unknown Fri Jun 20 07:19:58 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Mon, 13 Nov 2023 12:24:07 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator