Message-ID: <4D66E7BB.1060908@anselsystems.com>
Date: Thu, 24 Feb 2011 18:20:27 -0500
From: Andrew Manison <amanison@anselsystems.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3
Precedence: list
MIME-Version: 1.0
To: Alpine Development <alpine-devel@lists.alpinelinux.org>
Subject: [alpine-devel] Distfiles mirror
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

  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.

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.

Andrew


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---