From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: [PATCH] gnu: Add slurm. Date: Sat, 13 Feb 2016 18:00:57 +0100 Message-ID: <20160213170057.GA2487@debian> References: <56bb7530.v5bvas2QpzoMjKMl%pjotr.public12@thebird.nl> <20160210220447.0917f1a1@openmailbox.org> <20160211081534.GA8987@thebird.nl> <20160212122042.GA14275@thebird.nl> <20160212123010.GA6019@debian.eduroam.u-bordeaux.fr> <20160212123141.GB14324@thebird.nl> <20160212125719.GA14615@thebird.nl> <20160213085940.GA18223@thebird.nl> <20160213102825.GA19194@debian> <20160213164257.GA19241@thebird.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44838) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aUdZC-0006Cg-Df for guix-devel@gnu.org; Sat, 13 Feb 2016 12:01:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aUdZ8-0000DN-Ti for guix-devel@gnu.org; Sat, 13 Feb 2016 12:01:06 -0500 Received: from mailrelay2.public.one.com ([91.198.169.125]:32617) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aUdZ8-0000Ce-GQ for guix-devel@gnu.org; Sat, 13 Feb 2016 12:01:02 -0500 Content-Disposition: inline In-Reply-To: <20160213164257.GA19241@thebird.nl> 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Pjotr Prins Cc: guix-devel@gnu.org On Sat, Feb 13, 2016 at 05:42:57PM +0100, Pjotr Prins wrote: > On Sat, Feb 13, 2016 at 11:28:25AM +0100, Andreas Enge wrote: > > Some lines are way beyond 80 characters; this should be detected by > > "guix lint". > guix lint has not been working for me: Strange, it works for me with other packages. > I am using a recent repo of guix. I did do a rebase and the patch applies > on my tree (as did the previous one). Is there no more information? No, that is all (except a few more lines explaining what to do now in a git context). Could these two issues be related? It would be good if someone else could try to apply the patch. Andreas