From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 818811395E2 for ; Sun, 4 Dec 2016 06:41:11 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C72EC21C0CA; Sun, 4 Dec 2016 06:40:52 +0000 (UTC) Received: from caladan.c-14.de (caladan.c-14.de [78.47.48.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 52B30E0B85 for ; Sun, 4 Dec 2016 06:40:52 +0000 (UTC) Received: from sardaukar.c-14.de (HSI-KBW-109-192-117-105.hsi6.kabel-badenwuerttemberg.de [109.192.117.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by caladan.c-14.de (Postfix) with ESMTPSA id 894C21AF27B for ; Sun, 4 Dec 2016 06:40:50 +0000 (UTC) Date: Sun, 4 Dec 2016 07:40:49 +0100 From: Simon Thelen To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Metalog & runscript Message-ID: <20161204064049.GA2328@anonymous> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <1567fe0b-3f30-dcee-9fce-a48ee6acf18d@wht.com.au> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1567fe0b-3f30-dcee-9fce-a48ee6acf18d@wht.com.au> User-Agent: Mutt/1.7.1 (2016-10-04) X-Archives-Salt: 9d6ce918-b689-48b1-8308-026a12b6ae8c X-Archives-Hash: 3974d82ab44ce96b3cd8a81e65cbfd80 On 16-12-04 at 14:18, Andrew Lowe wrote: > Hi all, > I'm still getting the warning during boot about metalog using runscript > during the boot process. I decided to track things down and see what was > going on. My first stop was bugs.gentoo.org where there is this one: > > https://bugs.gentoo.org/show_bug.cgi?id=581926 > > Upon reading this, I would have thought that the ebuild had been > updated with the supplied patch by the developers. I looked at the > ebuild on my machine and it still is the "older" one. > Packages.gentoo.org has the same ebuild as me. > > Has something just fallen through the cracks and things should have > been "officially" updated or do I need to apply this patch myself? The patch was applied to the initscript, but the ebuild was not revbumped. You'll have to reinstall the package to get the new initscript. You can rebuild all packages that use /sbin/runscript with: `emerge --oneshot -av $(grep -l '/sbin/runscript' /etc/init.d/*)' This was mentioned in a newsitem draft on gentoo-dev, but as far as I can tell that newsitem was never published. -- Simon Thelen