X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 4EBCBDC008C for ; Thu, 27 Jun 2013 07:47:16 +0000 (UTC) Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 4581D20BFC for ; Thu, 27 Jun 2013 03:47:15 -0400 (EDT) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 27 Jun 2013 03:47:15 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:subject:message-id :references:mime-version:content-type:in-reply-to; s=smtpout; bh=htWr1N+4cw9LX+kYoo3NOnwtu20=; b=LEfnKpDd5J875+4wEhUL+sbPJzz7 FSV9t3HnRSeYu3vHFIlSLjXJElO98e8UwTH5yASrieScmQIzvsW34foGwUdL+fPF s6yZTuZ3XyLlNomFzGBqA8cr8H4romC57WNBhcWHZLiosuLwqW4Oq4UP6nRfeUB+ G6LcXOtXn8EKR1c= X-Sasl-enc: 2oueX1+nKZtvjBLva6Z1STl/GUskGU4RUnxw+Fc33pTR 1372319235 Received: from localhost (unknown [69.86.161.244]) by mail.messagingengine.com (Postfix) with ESMTPA id 0E3DF680285 for ; Thu, 27 Jun 2013 03:47:15 -0400 (EDT) Date: Thu, 27 Jun 2013 03:47:14 -0400 From: Dubiousjim To: alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] Can't build apk-tools Message-ID: <20130627074714.GI18572@zen> Mail-Followup-To: alpine-devel@lists.alpinelinux.org References: <1371469130.31289.140661244826657.5DE65BF9@webmail.messagingengine.com> <20130618085359.78d9215d@vostro> <20130626212843.GA18572@zen> <20130627093917.00014ea3@vostro> X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130627093917.00014ea3@vostro> User-Agent: Mutt/1.5.21 (2010-09-15) On Thu, Jun 27, 2013 at 09:39:17AM +0300, Timo Teras wrote: > > While debugging this I noticed a larger issue with apk-tools though: > > for some reason a bunch of files and links get (correctly) reported > > as owned by `apk info -W /path/to/file`, but get (incorrectly) > > reported as unowned (that is, no output and exit code 1) by `apk info > > -e /path/to/file`. > > > > Just run this to find some: > > > > find /sbin /bin /lib /usr \! -type d -exec sh -c 'apk info -q -e $1 > > \ || { apk info -W $1 2>/dev/null | fgrep -q " is owned by " && \ > > echo $1; }' sh {} \; > > Not all symlinks are owned. They get owned by a package only if > the .apk file contained the symlink. One notable misuser is busybox, > that uses busybox -s --install via triggers to install it's symlinks. > When you install the utility providing the real command it overwrites > those - and when you remove it, the bb install recreates the symlink > back to bb. Yeah, I thought I saw a problem that went beyond busybox though. But never mind, this is just more of my stupidity. `apk info -e` operates on packages not on files. I had momentarily thought it worked like `apk info -W path/to/file 2>/dev/null` actually works. I'm batting rather idiot today... At least doing it out loud leads to the mistakes eventually getting discovered. -- Dubiousjim dubiousjim@gmail.com --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---