From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#25852: Users not updating their installations of Guix Date: Mon, 6 Mar 2017 16:34:34 -0500 Message-ID: <20170306213434.GA25316@jasmine> References: <20170223211156.GA24382@jasmine> <877f429kju.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33782) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cl0Hb-0002oQ-G9 for bug-guix@gnu.org; Mon, 06 Mar 2017 16:35:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cl0HW-0007a2-JN for bug-guix@gnu.org; Mon, 06 Mar 2017 16:35:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:45081) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cl0HW-0007Zm-GI for bug-guix@gnu.org; Mon, 06 Mar 2017 16:35:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cl0HW-0003yv-BP for bug-guix@gnu.org; Mon, 06 Mar 2017 16:35:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <877f429kju.fsf@gnu.org> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 25852@debbugs.gnu.org On Mon, Mar 06, 2017 at 10:12:21PM +0100, Ludovic Courtès wrote: > Leo Famulari skribis: > > > In my opinion, the recent bug #25775 (Can't install packages after guix > > pull) [0] exposed a sort of meta-bug: there are a significant number of > > users who were still using the guix-daemon from 0.10.0. > > > > It seems unlikely that they have been updating all of root's > > packages except for the guix package. Rather, I bet they never updated > > root's packages at all, for ~1 year. They could have been stuck with an old daemon if they copied the systemd or upstart service files we provide. That problem should be fixed by 613d0895b92c677e0639d5e77c55043e38e020c8 (build: Don't embed absolute paths in .service and .conf service files.).