X-Original-To: alpine-devel@lists.alpinelinux.org
Received: from mail.bitmessage.ch (mail.bitmessage.ch [146.228.112.252])
	by lists.alpinelinux.org (Postfix) with ESMTP id 187A75C4D48
	for <alpine-devel@lists.alpinelinux.org>; Sat,  9 Dec 2017 01:24:46 +0000 (GMT)
dkim-signature: v=1; a=rsa-sha256; d=bitmessage.ch; s=mail;
	c=relaxed/relaxed; q=dns/txt; h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References;
	bh=7PxJcdqlP18zKmKUwVS2mXYve9ighMZrq8yPmUkT1hU=;
	b=YUgsz8lcM2p+/GNvVW1m0phzLlU8DlnCIU7crtViBz4KQzOTUtfUS7vUmyUcfASVuckr42X+MZ68zUACoWicA4Zdp4I6yI3Mr9ctDlHlJexewjQvxc/eL9siOZPJQbl7EkOpQ9mNH22Lk3ohOgDsrRZkBiVFpfnMrVSG5bguqqM=
Received: from [127.0.0.1] (BITMESSAGE [127.0.0.1])
	by mail.bitmessage.ch with ESMTPA
	; Sat, 9 Dec 2017 02:23:47 +0100
Subject: [alpine-devel] abuild -f should verify checksums, right?
References: <redmine.issue-8257.20171207211716.c855d71d57165827@bugs.alpinelinux.org>
To: alpine-devel@lists.alpinelinux.org
From: Oliver Smith <ollieparanoid@bitmessage.ch>
X-Forwarded-Message-Id: <redmine.issue-8257.20171207211716.c855d71d57165827@bugs.alpinelinux.org>
Message-ID: <bf252f98-cb7c-0ed1-1dbd-23c402822a89@bitmessage.ch>
Date: Sat, 09 Dec 2017 01:24:00 +0000
X-Mailinglist: alpine-devel
Precedence: list
List-Id: Alpine Development <alpine-devel.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-devel+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-devel@lists.alpinelinux.org>
List-Help: <mailto:alpine-devel+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-devel+subscribe@lists.alpinelinux.org?subject=subscribe>
MIME-Version: 1.0
In-Reply-To: <redmine.issue-8257.20171207211716.c855d71d57165827@bugs.alpinelinux.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit

Hello Alpine devs,

I have noted that abuild does not verify the checksums in the APKBUILD when the -f (force) flag gets passed. kaniini said "I think this is intentional" and asked me to write here.

So is this intentional (and if so, for which reasons)?
See the full bug report below.

Best regards,
Olvier

-------- Forwarded Message --------
Subject: [Alpine Linux - Bug #8257] (New) abuild -f doesn't verify checksums
Date: Thu, 07 Dec 2017 21:17:17 +0000
From: alpinelinux@bugs.alpinelinux.org

Issue #8257 has been reported by Oliver Smith.

----------------------------------------
Bug #8257: abuild -f doesn't verify checksums
https://bugs.alpinelinux.org/issues/8257

* Author: Oliver Smith
* Status: New
* Priority: High
* Assignee: 
* Category: Toolchain
* Target version: 3.7.1
* Affected versions: 3.7.0, 3.7.1, 3.8.0
----------------------------------------
h2. Versions
abuild-3.1.0-r3

h2. What happens
Build an aport with -f does not verify the checksums.

h2. What I expected
I've expected it to verify them, since the help sounds like it will build again if a package already exists. But it's unexpected to me, that the checksums don't get verified.

abuild -h says:
<pre>
-f  Force specified cmd, even if they are already done
</pre>


h2. How to reproduce
<pre>
mkdir hello-world
cd hello-world
wget https://raw.githubusercontent.com/postmarketOS/pmbootstrap/a876a428dde66a334aec8da446df5b23ae35ddf1/aports/main/hello-world/APKBUILD
wget https://raw.githubusercontent.com/postmarketOS/pmbootstrap/a876a428dde66a334aec8da446df5b23ae35ddf1/aports/main/hello-world/Makefile
wget https://raw.githubusercontent.com/postmarketOS/pmbootstrap/a876a428dde66a334aec8da446df5b23ae35ddf1/aports/main/hello-world/main.c
echo "// modification" >> main.c
abuild # checksums get verified
abuild -f # checksums don't get verified!
</pre>



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: https://bugs.alpinelinux.org/my/account




---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---