Weekly builds
Re: Weekly builds
Well, your last compiled sty+ct+ap was r849... the latest is r1048... you might wanna consider adding +ap to your weekly builds...
Re: Weekly builds
I'm currently updating/recreating the build VM for SDL2. When that's done, I'll check.
Re: Weekly builds
There's a new PPA:
https://launchpad.net/~armagetronad-dev ... untu/daily
It gets fed by automatic builds from git from here:
https://code.launchpad.net/%7Earmagetro ... d/+recipes
The process is a bit of a Rube Goldberg machine. First, launchpad clones/updates our git repository locally, that happens about once every five hours. Then, once a day, a build is started. Some machine clones the launchpad clones again, merges them with the fresh packaging repository (https://gitlab.com/armagetronad/ubuntu-packaging, essentially manages the debian/ subdirectories), builds debian source packages. Those are uploaded to all the build machines and built. Then they upload the result to the PPA infrastructure, which also has do do whatever (copying to mirrors, presumably) before you finally get to download the result. All in all, whenever there is a change in git, you can expect a build with it after 36 hours.
Currently available:
armadaily-experimental: builds from master/0.4
armadaily-alpha: builds from 0.2.8
armadaily-beta: builds from 0.2.8.3
Of course, the 'daily' in the name is to be taken with unhealthy amounts of salt. It's definitely only an upper limit to the build frequency.
https://launchpad.net/~armagetronad-dev ... untu/daily
It gets fed by automatic builds from git from here:
https://code.launchpad.net/%7Earmagetro ... d/+recipes
The process is a bit of a Rube Goldberg machine. First, launchpad clones/updates our git repository locally, that happens about once every five hours. Then, once a day, a build is started. Some machine clones the launchpad clones again, merges them with the fresh packaging repository (https://gitlab.com/armagetronad/ubuntu-packaging, essentially manages the debian/ subdirectories), builds debian source packages. Those are uploaded to all the build machines and built. Then they upload the result to the PPA infrastructure, which also has do do whatever (copying to mirrors, presumably) before you finally get to download the result. All in all, whenever there is a change in git, you can expect a build with it after 36 hours.
Currently available:
armadaily-experimental: builds from master/0.4
armadaily-alpha: builds from 0.2.8
armadaily-beta: builds from 0.2.8.3
Of course, the 'daily' in the name is to be taken with unhealthy amounts of salt. It's definitely only an upper limit to the build frequency.
Re: Weekly builds
The new ppa from the last post is gone again. The process there was inferior in every way to the GitLab CI process now feeding the regular PPA.
https://gitlab.com/armagetronad/ubuntu-packaging is also to be considered dead, I folded the relevant bits into the main source (under docker/build/context/debian). We need to easily be able to adapt Debian builds in arbitrary git branches, and juggling two repositories for that just is too much, for me anyway.
https://gitlab.com/armagetronad/ubuntu-packaging is also to be considered dead, I folded the relevant bits into the main source (under docker/build/context/debian). We need to easily be able to adapt Debian builds in arbitrary git branches, and juggling two repositories for that just is too much, for me anyway.