From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id SCxfO19EpWRzZAAASxT56A (envelope-from ) for ; Wed, 05 Jul 2023 12:22:24 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id AOVdOl9EpWRNBgAAG6o9tA (envelope-from ) for ; Wed, 05 Jul 2023 12:22:23 +0200 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 7A0C9257F4 for ; Wed, 5 Jul 2023 12:22:23 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=reproduciblemedia.com header.s=key1 header.b=Jn8NzznK; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1688552543; a=rsa-sha256; cv=none; b=o91vCD/O0pg8S6Q4HccmxN9lArjH0f6fQl+BPFCV0q4izeEJMeVxI/QrZMpoXHpiJIPgJ5 /I1tB9fQnb1AUApyon2x10AKA619xujpWdW/M6EL60NJkWFJ/TseM89ovErESGNTjskslE Uo3xhViU6XRxQz/8/rDY2HIN95DKsVfdUoZ/xxpLQeuTMcU5vezEDPQTG5Ks9yc4pjoyLd IETOAAAeZKIl9Bo8q8YV0DP95zT26wPNnR3dY0/v3MiVUckjIXDOjOHQzUHlkG6e/jq0r3 MUI1bOVMgxTEiU7Jq/yxkFNaEkJwgTN/cnvgv9ooypaL/yxlXUeTpS+ZwKYJ9Q== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=reproduciblemedia.com header.s=key1 header.b=Jn8NzznK; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1688552543; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:resent-cc: resent-from:resent-sender:resent-message-id:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=77H+kfqW0LlFFA8GuSH/voOCfU9IUxqK4JMjSXu12Mc=; b=P+KWvyQudGwi70S4OFzzjPYM1wwnBGBNHHbC8EAMUIoUblMjDYMmlqfzNCIzx+Y+pwuSy8 L4evkJDMZOwRy8vH7Cl7UygWcrzqNE3kun6ThJjwFH+/dBfHzw2630vqGP9GdAzbQ8oVK6 bYtVbo7kQbIidgO+xr3gLqvCCGq2qd+No+Lpds8ANpkz9olERnU5TWlXyukGqIpzWfJHiI uRbVerKPVGYp7EK1Ycgi0zKurxILln5VGyeXgts8JQE2k8ZQNoewiXrhYoXYAvjLuqCA/2 fvW7emYBOmsyin4M0heNrL+E96Cx6dVL+d5tfhwdu2hhsSkx+ynK0gRd3HR7qw== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qGze9-0007bl-HR; Wed, 05 Jul 2023 06:22:05 -0400 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 1qGze7-0007bO-5w for bug-guix@gnu.org; Wed, 05 Jul 2023 06:22:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qGze6-0000QW-TA for bug-guix@gnu.org; Wed, 05 Jul 2023 06:22:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qGze6-0006pq-D7 for bug-guix@gnu.org; Wed, 05 Jul 2023 06:22:02 -0400 X-Loop: help-debbugs@gnu.org Subject: bug#64472: guix pull --roll-back breaks guix Resent-From: Blake Shaw Original-Sender: "Debbugs-submit" Resent-CC: bug-guix@gnu.org Resent-Date: Wed, 05 Jul 2023 10:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: report 64472 X-GNU-PR-Package: guix X-GNU-PR-Keywords: To: 64472@debbugs.gnu.org X-Debbugs-Original-To: bug-guix@gnu.org Received: via spool by submit@debbugs.gnu.org id=B.168855250826246 (code B ref -1); Wed, 05 Jul 2023 10:22:02 +0000 Received: (at submit) by debbugs.gnu.org; 5 Jul 2023 10:21:48 +0000 Received: from localhost ([127.0.0.1]:37144 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qGzdr-0006pF-Da for submit@debbugs.gnu.org; Wed, 05 Jul 2023 06:21:47 -0400 Received: from lists.gnu.org ([209.51.188.17]:35366) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qGzdm-0006p4-HA for submit@debbugs.gnu.org; Wed, 05 Jul 2023 06:21:46 -0400 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 1qGzdm-0007TM-8A for bug-guix@gnu.org; Wed, 05 Jul 2023 06:21:42 -0400 Received: from out-43.mta1.migadu.com ([95.215.58.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qGzdh-0000MO-UT for bug-guix@gnu.org; Wed, 05 Jul 2023 06:21:41 -0400 X-Is-Generated-Message-Id: true DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=reproduciblemedia.com; s=key1; t=1688552492; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=77H+kfqW0LlFFA8GuSH/voOCfU9IUxqK4JMjSXu12Mc=; b=Jn8NzznKY3thafEplJCfd1E9eQxLTEEMev3eYzWI070iCtc/rrA2IbLjgtkANwMxAsiNQk eCykaNv6cPhr7QDZgdWMujoz2JOIVs8FV8lwVaWc/HY6l4k229DB2TMrVTCmQrTgWg8x3+ xmqxGlVe8Uq6/HQNcHUgjIXrG/MfZBTjIMDNJH3N+wtfWGpFywpgnyuln3fcOE12WnfE0t VAmq25OfR/zdUAOIsyIP996cp/i5lvU55rm4CneMJ3OUGMfTfJbIXaSf4VFiP86yyjw+AB 2wGwqqtx1G78XbPhCOe625/TAOgGKV6hmWRU18GdXvMjgMIM5dEOuTZ6KPcRoA== X-Blue-Identity: !l=2305&o=0&pl=2100&po=0&qs=PREFIX&f=HTML&p=2079&q=NONE MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----WYQYVGZ3R31RPRYU0N7NG07ZZHATXU" Content-Transfer-Encoding: 7bit X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. Date: Wed, 05 Jul 2023 17:21:23 +0700 Message-ID: Received-SPF: pass client-ip=95.215.58.43; envelope-from=blake@reproduciblemedia.com; helo=out-43.mta1.migadu.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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: , Reply-to: Blake Shaw From: Blake Shaw via Bug reports for GNU Guix Errors-To: bug-guix-bounces+larch=yhetil.org@gnu.org Sender: bug-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: scn1.migadu.com X-Migadu-Spam-Score: -3.96 X-Migadu-Queue-Id: 7A0C9257F4 X-Spam-Score: -3.96 X-TUID: ZebnEPIWL9nx ------WYQYVGZ3R31RPRYU0N7NG07ZZHATXU Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Hiya Guix, I just encountered a surprising bug=2E I've been trying to ge= t the [redacted] proprietary GPU drivers to work on my system (but this isn= t particular to the issue at hand), and I "guix installed" the [redacted-mo= dule] package in my =2Eguix-profile, to see if that would help me with the = failed $ modprobe [redacted] that I was experiencing=2E It didn't, so I= decided to do what we do best: roll-back=2E But I accidentally ran $ guix= pull --roll-back instead of $ guix package --roll-back This mistake sho= uld be trivial, fixable by running $ guix pull --switch-generation=3DN Wh= ere N is the "FROM" field of the roll-back message that guix displays follo= wing a successfull roll back=2E But to my surprise an anomaly appeared in = the "TO" field of the roll-back message: $ guix pull --roll-back building = path(s) `/gnu/store/2s7a7h=2E=2E=2Egj23-profile` switched from generation 8= 6 to 0 Huh? Zero? It should have switched to 85=2E Weird, but np, let's ju= st direct it to 85=2E $ guix pull --switch-generation=3D85 -bash: /home/my= -profile/=2Econfig/guix/current/bin/guix So now it can't find guix=2E Visi= ting =2Econfig/guix/current/ it is empty except an etc dir and a manifest= =2E so I use guix from the run directory to get back on track: $ exec /run= /current-system/profile/bin/guix --switch-generation=3D85 guix pull error: = cannot switch to generation '85' $ exec /run/current-system/profile/bin/gu= ix --switch-generation=3D86 switched from generation 0 to 86 And then $HOM= E/=2Econfig/guix/current is back to normal and everything works fine=2E So = I assume this was due to yesterday's guix gc --delete-generations=3D1d Bu= t like, should this happen? Should we ever be rolling back to an empty "0" = generation that doesn't even contain guix, and thus creates a pickle for th= ose who don't have prior knowledge of how to get out of it? Should we limit= gc --delete-generations to always keep a previous generation at hand, perh= aps unless forced by some other flag, so that [in particular, new] users do= n't break their systems in the middle of the day and then have something to= solve that encumbers their plans & work? Happy hacking! Blake ------WYQYVGZ3R31RPRYU0N7NG07ZZHATXU Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Hiya Guix,

I just encountered a surprising bug=2E

I've been trying to get the [redacted] proprietary GPU drivers t= o work on my system (but this isnt particular to the issue at hand), and I = "guix installed" the [redacted-module] package in my =2Eguix-profile, to se= e if that would help me with the failed

$ m= odprobe [redacted]

that I was experiencing= =2E

It didn't, so I decided to do what we d= o best: roll-back=2E But I accidentally ran

$ guix pull --roll-back

instead of

=
$ guix package --roll-back

This mistake should be trivial, fixable by running

=
$ guix pull --switch-generation=3DN

Where N is the "FROM" field of the roll-back message that guix d= isplays following a successfull roll back=2E

But to my surprise an anomaly appeared in the "TO" field of the roll-back= message:

$ guix pull --roll-back
=
building path(s) `/gnu/store/2s7a7h=2E=2E=2Egj23-profile= `
switched from generation 86 to 0

Huh? Zero? It should have switched to 85=2E Weird, but = np, let's just direct it to 85=2E

$ guix pu= ll --switch-generation=3D85
-bash: /home/my-pro= file/=2Econfig/guix/current/bin/guix

So now= it can't find guix=2E Visiting =2Econfig/guix/current/ it is empty except = an etc dir and a manifest=2E so I use guix from the run directory to get ba= ck on track:

$ exec /run/current-system/pro= file/bin/guix --switch-generation=3D85
guix pul= l error: cannot switch to generation '85'

$= exec /run/current-system/profile/bin/guix --switch-generation=3D86
switched from generation 0 to 86

And then $HOME/=2Econfig/guix/current is back to normal and ever= ything works fine=2E So I assume this was due to yesterday's guix gc --dele= te-generations=3D1d

But like, should this = happen? Should we ever be rolling back to an empty "0" generation that does= n't even contain guix, and thus creates a pickle for those who don't have p= rior knowledge of how to get out of it? Should we limit gc --delete-generat= ions to always keep a previous generation at hand, perhaps unless forced by= some other flag, so that [in particular, new] users don't break their syst= ems in the middle of the day and then have something to solve that encumber= s their plans & work?

Happy hacking!
Blake
------WYQYVGZ3R31RPRYU0N7NG07ZZHATXU--