From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: The broken 0.13 release for GuixSD Date: Wed, 24 May 2017 12:26:34 +0200 Message-ID: <874lwaa6ud.fsf@elephly.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37053) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dDTV7-0007on-6Q for guix-devel@gnu.org; Wed, 24 May 2017 06:26:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dDTV4-0008Fm-1k for guix-devel@gnu.org; Wed, 24 May 2017 06:26:45 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21142) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dDTV3-0008FW-Pl for guix-devel@gnu.org; Wed, 24 May 2017 06:26:41 -0400 In-reply-to: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: ng0@pragmatique.xyz Cc: guix-devel ng0@pragmatique.xyz writes: > Going from within GuixSD 0.12 to 0.13 (multiple guix pull issued to get > all the dependencies you might lack) works. > > GuixSD 0.13 medium on new installations, with no system present previously, > so far failed on all types of hardware from the last 1 - 15 years for me including > bios and uefi systems. > > All get stuck on the same test. > This should not happen at all with a release. Please, the least you could do when using words like “broken” and “should not happen at all” is to be precise about *what* fails. This is not constructive. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net