[arch-dev-public] Automated rebuild for ncurses 6.0 in progress

Evangelos Foutras evangelos at foutrelis.com
Sun Sep 6 18:51:24 UTC 2015


On 06/09/15 21:18, Pierre Schmitz wrote:
> On 06.09.2015 19:02, Evangelos Foutras wrote:
>> You can follow the progress at: https://rebuilds.foutrelis.com/
>>
>> If anyone wants to tackle a build failure, you can commit the fix in
>> /trunk (without bumping pkgrel) and then click on the failing package
>> and select "Retry build task".
>>
>> Note: This rebuild is not listed on https://www.archlinux.org/todo/ in
>> order to avoid any confusion.
> 
> Looks awesome. How exactly is this down? Did you setup jenkins etc.?
> 
> Greetings,
> 
> Pierre

The source is hosted at https://github.com/foutrelis/arch-rebuilds

It currently requires some manual setup at the start of a rebuild; steps
are roughly:

1) Create a new arch_rebuilds database and copy a few tables from the
live archweb database.

2) Import the list of packages to be rebuilt using mkrebuild.pl; at this
point you also specify which packages are going to be built manually
before the rebuild starts (in this case: ncurses, lib32-ncurses,
readline and bash; the latter two due to bootstrapping issues).

3) After the above is done, multiple packagers can start rebuilding
stuff by running builder/build.sh. The build.sh script queries the web
service for a package to build, it bumps its pkgrel, builds and releases
the package into the respective staging repo. (Builders are
authenticated using a database-stored token and also need to use the
private mirror on nymeria to receive updates immediately.)


More information about the arch-dev-public mailing list