Date: Fri, 25 Feb 2011 17:39:18 -0600
From: William Pitcock <nenolod@dereferenced.org>
To: Andrew Manison <amanison@anselsystems.com>
Cc: Alpine Development <alpine-devel@lists.alpinelinux.org>
Subject: Re: [alpine-devel] Distfiles mirror
Message-ID: <20110225173918.2fc0dd91@petrie>
In-Reply-To: <4D66E7BB.1060908@anselsystems.com>
References: <4D66E7BB.1060908@anselsystems.com>
Precedence: list
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Andrew,

On Thu, 24 Feb 2011 18:20:27 -0500
Andrew Manison <amanison@anselsystems.com> wrote:

>   There will soon be a spate of emails from AlpineBuildBot regarding
> the building of various modules. I have developed a script, intended
> to be run at regular intervals, which goes through the aports tree
> and builds all packages. The current run has failures and the build
> logs from them are being mailed to the maintainers, as well as to the
> list. Many of the failures are due to missing source archives. At
> present, the distfiles mirror (distfiles.alpinelinux.org/distfiles)
> is quite out of date. If the primary source goes offline we have no
> archived copy of it. There a two remedies to this: either make sure
> that the source tarball is on the distfiles mirror, or update the
> package to the current release. If the latter course is taken, the
> source tarball still need to find its way onto the distfiles mirror
> to preserve it for future builds.

Tinderbox-style testing is a great idea.  What would be useful on the
reports, though, is if the build architecture is listed.  The reason
why I say this, is because it is possible that a build may succeed on
x86 and x86_64, but fail on powerpc or arm which are both slated to be
included as an official port post-2.2.

Would you be able to add this to the report?

> 
> At one point I had the build down to just two failing packages. Now
> it's up to 30 in main and 8 in testing. I am available to work with
> the maintainers to get the builds working. Sometimes it's a matter of 
> missing dependencies in the APKBUILD script, that don't show up
> because the packages are installed on the maintainers system. Others
> are due to mutually exclusive packages. For example, libiconv is
> remarkably 'sticky' and once installed for a build sometimes fails to
> uninstall.
> 
> My goal is to make it so that it is easy to setup a build server,
> point it at the git repository, and build all the packages for edge
> or a given release. I'm not there yet, but getting closer. In harmony
> with Nataneal's earlier email, this would fit well with the proposed
> team structure, and provide some redundancy to the build and release
> process. This periodic total build would belong to the 'stable
> maintainers' sub-team of the developers team, while the total build
> is a useful step as part of the release process.

Great!  I think doing archive-wide rebuilds will improve the QA process
of edge and keep us fixing bugs quickly.  Which fits into my goal of
keeping edge in a more releasable state always.

William


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---