From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH] gnu: bash-completion: Update to 2.3. Date: Sat, 6 Aug 2016 23:06:05 -0400 Message-ID: <20160807030605.GD30934@jasmine> References: <20160803085311.24325-1-sleep_walker@gnu.org> <20160805185346.GA1227@solar> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49351) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bWEPu-0007Cz-4A for guix-devel@gnu.org; Sat, 06 Aug 2016 23:06:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bWEPp-0004ng-Sy for guix-devel@gnu.org; Sat, 06 Aug 2016 23:06:21 -0400 Content-Disposition: inline In-Reply-To: <20160805185346.GA1227@solar> 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: Andreas Enge Cc: guix-devel@gnu.org On Fri, Aug 05, 2016 at 08:53:46PM +0200, Andreas Enge wrote: > The autoreconf phase is strange. Why is it suddenly needed? If there is no > way around it, you should at least add a comment. I notice that when projects move to GitHub, they sometimes forget to cut a new release. GitHub automatically generates a tarball of the source tree for each tag, and those are not bootstrapped. That's probably what happened here, and it's worth an upstream bug report, IMO.