From mboxrd@z Thu Jan 1 00:00:00 1970 From: zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze) Subject: bug#36876: guix system delete-generations removes custom boot menu entries Date: Mon, 05 Aug 2019 12:05:57 -0400 Message-ID: <8736ifzjfe.fsf@sdf.lonestar.org> References: <20190731094857.28829b11@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:60912) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hufYh-0003x7-Ej for bug-guix@gnu.org; Mon, 05 Aug 2019 12:10:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hufYg-0007J4-DV for bug-guix@gnu.org; Mon, 05 Aug 2019 12:10:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:55145) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hufYg-0007Iz-9u for bug-guix@gnu.org; Mon, 05 Aug 2019 12:10:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hufYg-0007h0-3N for bug-guix@gnu.org; Mon, 05 Aug 2019 12:10:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20190731094857.28829b11@gmail.com> (Jesse Gibbons's message of "Wed, 31 Jul 2019 09:48:57 -0600") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Jesse Gibbons Cc: 36876@debbugs.gnu.org --=-=-= Content-Type: text/plain Hi Jesse, Jesse Gibbons writes: > I dual-booted Guix with another gnu/linux-libre distro. > My configuration includes the other distro in the grub menu. When I run > "sudo guix system delete-generations" the changes to the grub menu drop > the other distro with the older system generations of guix. > > My current work-around for this is to run "guix system reconfigure ..." > which includes the boot menu entries specified in the configuration. Thanks for reporting this; it's a rather serious issue. The problem lies in the 'reinstall-bootloader' procedure. Chiefly, it uses the default bootloader configuration for whatever it can find using 'lookup-bootloader-by-name' and generates menu entries for the generations reachable from '%system-profile', which is quite a bit different from how 'guix system reconfigure' produces the bootloader configuration. It really isn't ideal. To quote a comment in 'system.scm': "[i]t will be enough to allow the system to boot." I don't think this should be _too_ hard to fix. To me, parsing the installed Grub configuration to get existing menu entries seems like a logical step forward. Thoughts from anyone else? Regards, Jakob --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEa1VJLOiXAjQ2BGSm9Qb9Fp2P2VoFAl1IU+YACgkQ9Qb9Fp2P 2Vp/xhAAk/8YsIdUIUoAXsarGj/LJe4AuVhMJKR2uJGsgVUFbB1F825rSj6PTk7L Oa2l5BvRq3fuULT46zEzgCaE4LHu2xwe0FFjhKGPrsAx9I6AMHp1hItRwj3u57CC oFQBDOAKOQBqQT8h9ynJ45KdJ+dkzwmOYVXIp5/17FfjIefZOL0XTE7Bmr3ycd5y YW/n+B0LCrMPtdwVmFy999o0in/Z5BPh2RLLo/NW36viT+kafqSBAk9YymYqEbe4 H/uF7n5nb9Z/zWOlwj3gpDJ/TGU797TSVYSwZOFkO+dekYsw7PlesqQApXX3qfGe VgRSwSn22NwzwjyCgLGtvjgxEloV8pihodceznRZXi25Ld1N9DUQndN6Ryk65JiO RzLVGn/vfCq8yR5OOiWcQApd7Xz8XPXxe9fX9mkG/KJW6U4g8BjfjjwAvELsrKmg +6OFg0bUdn+Gr9OVZKAEVlgtThhxdGIpVFxXChBJdRK/K/QyZeY2DQarRhgkm3h5 vzKwBncEOOj+sQfDs09nT/1Bz/DjpQJpLT+FTsqRVGzfknzYVamKiKamm59RdxJS jI9EUTFLT/oqk254utSc8lhXBhemynKN+GiBV6uW45BqYKMtUgdRxFSyRn8XRThB BBebjQQhxGk9gliCsZMIJhWs26BsGrgEUwfAciJJfNypZWUoHbk= =ZPUK -----END PGP SIGNATURE----- --=-=-=--