Mail archive

[alpine-devel] abuild -f should verify checksums, right?

From: Oliver Smith <>
Date: Sat, 09 Dec 2017 01:24:00 +0000

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,

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

Issue #8257 has been reported by Oliver Smith.

Bug #8257: abuild -f doesn't verify checksums

* 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

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:
-f Force specified cmd, even if they are already done

h2. How to reproduce
mkdir hello-world
cd hello-world
echo "// modification" >> main.c
abuild # checksums get verified
abuild -f # checksums don't get verified!

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:
Received on Sat Dec 09 2017 - 01:24:00 UTC