From debbugs-submit-bounces@debbugs.gnu.org Sun Nov 27 18:35:14 2022 Received: (at 59598) by debbugs.gnu.org; 27 Nov 2022 23:35:14 +0000 Received: from localhost ([127.0.0.1]:44823 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ozRB3-00026w-VT for submit@debbugs.gnu.org; Sun, 27 Nov 2022 18:35:14 -0500 Received: from mailout.easymail.ca ([64.68.200.34]:56644) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ozRB2-00026o-0Z for 59598@debbugs.gnu.org; Sun, 27 Nov 2022 18:35:13 -0500 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 2A1BA6300F; Sun, 27 Nov 2022 23:35:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bokr.com; s=easymail; t=1669592104; bh=6gqoQNR9pTVph32cTbBYqccdnIN/blJ58UqZmWKdaeQ=; h=From:Date:To:Cc:Subject:References:In-Reply-To:From; b=OM5fMN45vd+N74zj8F3LKxYwvKZS4rIHphF5Uyx5ANryfHjbuMaxXpRVpj84k3oNm CEgjtVWi15EIDoQM815ZPUCaRDM+/q19VsoSviYEAcCzLTGVXlUM9cOZSM+aXkt/9o IoGIq9PP/SrBYa0G1am2Ikcm9Itfi3r1FHzD2B5OZrSzPD22G8vK355gaVxUMw28ws C1TS64Kcy4h/iLuCziXCU4Oy8zwQ6wPLZZip1gGeucq1b9LQG8NYdLX7XaDa2wUYxz q01xof+1wion2VbTFAnSj4L21vNR94NbdFOxbYiLipm6AeT/LU9Wr5Ql5y86pKdDdG hHAbsAC/1d/pw== 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 SGZ0R5S-WPah; Sun, 27 Nov 2022 23:35:03 +0000 (UTC) Received: from localhost (m83-185-34-32.cust.tele2.se [83.185.34.32]) (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 40A5161C6B; Sun, 27 Nov 2022 23:35:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bokr.com; s=easymail; t=1669592103; bh=6gqoQNR9pTVph32cTbBYqccdnIN/blJ58UqZmWKdaeQ=; h=From:Date:To:Cc:Subject:References:In-Reply-To:From; b=AEanzj74KLcuAi2ZjawX9bKfD7bcA1u7awvL5GpUFTq7T1s6IeYSJEJFLRNsLCYcs eDKA9/ijI8+jAT5lMQ103EYpc7pDtu0WWTgtGhN1fN1ZKgP8jht9r/qFBX/jDE7dlq 9XVzm7pGtVjxl4QEEmMsvfomSmy9HvOW6Z2IUeiVWO3BeczNpXig6Yo5u9afoerMpd +Q/ldacRVclFkO38KIUj2WPGSoxgPec2CTjP0AErEyMEeAgTsXI+ovWCqJWeTZ/NsK GrzvFLUBXhq3IEtHfkxR16A5PO6Z3QCbBRiEHGFFIp4U2XiQM1HI2RtAABvYkFJDr6 MthDWb98gvFAQ== From: bokr@bokr.com Date: Mon, 28 Nov 2022 00:34:43 +0100 To: zimoun Subject: Re: bug#59598: "Unsupported manifest format" error Message-ID: <20221127233443.GA3070@LionPure> References: <86bkos1ta9.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <86bkos1ta9.fsf@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 59598 Cc: 59598@debbugs.gnu.org, Tyler Wolf 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 (---) Hi zimoun, On +2022-11-27 13:22:22 +0100, zimoun wrote: [...] > > This file lives in the store. Hum, I am surprised that a power shutdown > removed this file. > Are all the conditions for a clean sync of the file system where /gnu/store is mounted guaranteed? What is the difference between power shutdown when you let the battery run down and the OS shuts everything down vs if you log out and click power down? Is it not possible that when you have recharged the battery and boot up that a journaling file system will discover traces of an incomplete transaction (i.e. the one that was supposed to record and atomically commit the missing file) and discards it to reestabllish coherent file system state? And what about continuations that were possibly waiting for availability of that file? Hopefully the OS will recover a good state, but what can userland innocents expect to be guaranteed, in terms of work flow they can understand? (those with the grok-fu to understand internals won't need much to imagine failure scenarios, but will presumably appreciate /design/rationale/implementation/ documentation tips) > Well, I do not know if you can recover this empty file. At least, you > can the previous generation; e.g., guix package --roll-back. > Assuming the file system recovered -- a pretty good bet, but ... :) > Or you can extract a previous manifest with, > > guix package -p /var/guix/profiles/per-user//guix-profile--link \ > --export-manifest > /tmp/manifest-.scm > > where and depends on. Then, > > guix package -m /tmp/manifest-scm > > will reinstall the same list of packages but at their current version > (the ones of current Guix revision; guix describe). > > > Cheers, > simon > -- Regards, Bengt Richter