From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: bug#27212: 203a9455c4695152fc5d0085bffeead9ce3216c2 broke system boot Date: Sat, 3 Jun 2017 17:30:56 +0000 Message-ID: <20170603173056.7622qgvocdbn3gpi@abyayala> References: <20170603165321.iocqorc25mmvjhjf@abyayala> <8737bh0zvt.fsf@fastmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="gnifaadafqpfa4ks" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36734) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dHCuE-0006R8-Qb for bug-guix@gnu.org; Sat, 03 Jun 2017 13:32:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dHCuB-0007Zc-KL for bug-guix@gnu.org; Sat, 03 Jun 2017 13:32:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:51393) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dHCuB-0007Z9-Gt for bug-guix@gnu.org; Sat, 03 Jun 2017 13:32:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dHCuA-0008Oh-57 for bug-guix@gnu.org; Sat, 03 Jun 2017 13:32:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <8737bh0zvt.fsf@fastmail.com> 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: Marius Bakke Cc: 27212@debbugs.gnu.org --gnifaadafqpfa4ks Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Marius Bakke transcribed 1.4K bytes: > ng0 writes: >=20 > > Otherwise perfectly working systems I have *all* break after > > https://git.savannah.gnu.org/cgit/guix.git/commit/?id=3D203a9455c469515= 2fc5d0085bffeead9ce3216c2 > > > > and the last thing they display before guile repl is the > > message in that commit. > > > > Yes, I use labels. No, I don't use complicated setups. > > Please test such changes before applying them in the wild.. > > I just hope this happened here and the break is a mistake. >=20 > I *just* noticed the same thing. I also tried reverting this commit, but > that just entered a (re)boot loop. Not sure what's up, but two of my > GuixSD systems are affected. >=20 > On my way out now, but will investigate more tomorrow. CC Danny in case > of insight (which report by Chris did this address?). >=20 > Older generations are fine. Thanks. Results like this should be avoided. As long as this happens there is a reason for the 'beta' label. It might be usable in all kinds of environments, but we have to have rules and guidelines when something can be applied just like this after QA or when a certain set of people have to aprove the change as they did test the change and it worked. I consider file-system one of these cases. If the commit touches the way towards boot, approval is the way to go. --=20 ng0 OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588 --gnifaadafqpfa4ks Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlky8ksACgkQ4i+bv+40 hYgcMg//ZVlqt1nwh/9sUFmxAxCdlOUtnFiasHyi1OeMni+I1y1ZIhZTJxndesm1 pSzefRDSuqHFu8JIdEOrAK3i+wirlnpWwPEHNINe6D9iGIgWVmerrNEdIp6skcsf /zLS5GOSjh3UZ1Om8V208x7+RbodWmAU+hv7eLeYUQJPNk/FNP6HmaSmRepLPczD FWF9bSqbulw0N7rwhNK/Fwhk3zTyw4gnDQU9d7lbak2kiPgzXrWfVt5M5VpYWH0P yMI8Qf9cstm3S2OjGjvwgspd77IDxmqz9G2C92BiWfEv53jutzg2lGfbrpQ28reY +QbAk8NhtOaT40VgmAljQVHpnKyBikaJnNmavtmh5H8r3rsjm4aikcNPxSpl5eQy 3lR+x0QR/YH52SFMgI3PtVgvanQwOEJOLTjDV4WzGRbwtIZXjLhDwVWc5bXjWafZ FUjn09+DRqrvE06OZC9+2NPtm0Air/e7U5QrkHFmruG1slPqLR9Gwji9StkZwUZH l/JGPCLtzfpFZ/EZenbC2oJjC5t/qVPvYNOqngHLhY9Gtu99wLefyux9zA4ncGtZ NyvOTKm4JgGqm8acUvMUf30bdLteYLg5uF7iANN0Z35XHsGdxN0wIrOSGatGtnOR nItQAoVX2PB5apfQI54pJpahY/peHP1nwyZKbDhe19W7bWtNwtg= =uNX/ -----END PGP SIGNATURE----- --gnifaadafqpfa4ks--