X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 850251CE4213 for ; Tue, 25 Oct 2011 10:09:16 +0000 (UTC) Received: by faar19 with SMTP id r19so463643faa.13 for ; Tue, 25 Oct 2011 03:09:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=8TcJ1Uesc6Q9+N8qp9Rz6r6oHzKtVXTLANdX9PMwdn0=; b=wwMKgNn0XoEWSBg2dYjwJihX+WEkR798E+t/TKysSTxJrJyxcQvT58vQsHT50K8Rh/ u/WUMlV70vr68/ky2z/mrKZjXJkKc8LZi1Mna+5RzOnJGsEj8mfxrKZLtLAQQqYEENof ArblbbyLUw1leY5m3uR+Pil40wEktLpDvVR7U= X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.182.134.9 with SMTP id pg9mr2163696obb.35.1319537354286; Tue, 25 Oct 2011 03:09:14 -0700 (PDT) Received: by 10.182.144.9 with HTTP; Tue, 25 Oct 2011 03:09:14 -0700 (PDT) In-Reply-To: <4EA657D6.8000906@freemail.gr> References: <4EA555E7.1030301@freemail.gr> <4EA657D6.8000906@freemail.gr> Date: Tue, 25 Oct 2011 12:09:14 +0200 Message-ID: Subject: Re: [alpine-devel] APKBUILD for liboping From: Carlo Landmeter To: Harry Lachanas Cc: Alpine Development Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Oct 25, 2011 at 8:31 AM, Harry Lachanas wrote= : > On 10/24/2011 05:29 PM, Carlo Landmeter wrote: >> >> 6. You dont need to specify the dev or doc functions when nothing >> special has to be done. It will be automatically called by subpackages >> var. >> 7. liboping didn't correctly "make install". (missing setcap). If you >> use abuild you would have noticed. > > Hi Carlo, > Many thanks for your nice remarks, > indeed I had no idea about the "newapkbuild" approach. > However by now I am sure that you know that the "setcap missing" problem > arises from the fact that there are a couple executables missing from > libcap-2.20-r0.apk. > > Since I've downloaded and compiled it manually on my test system the libc= ap > tar thing provides the binaries bellow > > capsh, =A0 =A0 =A0 =A0( ok ) > getcap, =A0 =A0 =A0( ** missing in alpine ) > getpcaps, =A0( ok ) > setcap, =A0 =A0 =A0 ( ** missing in alpine ) > > Now the *apkbuild approach as far as the above package is concerned has t= o > be revised by the maintainer, We already fixed it in: http://git.alpinelinux.org/cgit/aports/commit/?id=3D942d1793c6caeb7793f115d= 1185d0f80b929266e I am aware of the broken src link, but our current build infra has this specific src still cached. I'm not sure about the current status of kernel.org and if src packages will be restored. If not we will have to update a few apkbuilds in our repo. -carlo > the aports/main/libcap/APKBUILD is broken and =A0probably outdated since = the > web page of the package states > > "You can download libcap2 in the following ways: > As a tar file (kernel.org hacked so this is temporarily unavailable). > Or browse the git managed source here." > > while the APKBUILD tries to download =A0from: > > http://www.kernel.org/pub/linux/libs/security/linux-privs/libcap2 > > Which is a =A0dead link. > > Cheers, > Harry. > > --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---