The XiVO GIT repository re-organisation aims at creating a single repository for each software. In order to prepare for this migration, the repository directory can be specified as GIT_DIRECTORY to submit-xivo.sh.
The 2.0.17 version of packaging-farm was published with a fix for when a package failed to build but packaging-farm thinks it succeeded and was installed on all machines.
Continue reading “XiVO GIT repository re-organisation”
The sustainability of packaging-farm depends on the number of its users. There currently are four: a company shipping a software suite to its customers ( Avencall with XiVO ), the software that initiated the development ( pokersource as found in Debian GNU/Linux with poker-eval, poker-engine etc), a university developed set of packages for bioinformatics ( biopp from université de montpellier ) and a single package web game in its early stages of development ( cardstori.es from farsides).
The problem packaging-farm is facing to get new users is described below in terms that may apply to other projects with a similar size and scope. No solution to the problem is found and there probably is none. The web site information was improved and a beginner guide written.
Continue reading “bring packaging-farm to users who need it”
After submitting an asterisk version with a version lower than the previous one, the packaging-farm created an inconsistent repository. The existing version was
and the version being submitted was
According to dpkg –compare-versions, the version being submitted is actually older than the release candidate -rc2, because – is after + lexicographicaly. This is a mistake and should be replaced by a version number that is higher than the -rc2. But packaging-farm silently ignored the problem and created a bugous package, mixing the sources being submitted with a version number coming from the existing version.A safeguard was added and packaging-farm will now abort with an error message explaining the error and suggesting a course of action.
The 2.0.15 was published and installed on the gallifrey, gallifrey-dev and skaro build machines.
Continue reading “Safeguard against downgrades in XIVO packages”
A recuring pattern in the past two weeks has been the need to resolve a situation where the build machines and the associated respositories could not be used because either:
- the reprepro repository rejected one of the packages found in a build machine because of a checksum error, i.e. because it contained the same version of the package with a different checksum
- the packaging-farm installed on the build machine claimed it had no work to do
- packages were not manually submitted to the build machine
In the following each source of confusion is analyzed and clarified.
Continue reading “resolving XiVO submissions confusion”
A default configuration file for submit-xivo.sh was created to avoid typos. When the environment of submit-xivo.sh changes, the sources are rebuilt. The 2.0.14 version of packaging-farm was released with these modifications, installed on all build machines with the associated migrations.
Continue reading “XiVO submission configuration”
The production version of gallifrey was rebuilt to strip the timestamp and hash. A compilation problem with sangoma-wanpipe blocking the development version of gallifrey was diagnosed. A bug on kernel-modules dependencies was fixed. To avoid confusion the build configuration files were moved to /etc/packaging-farm. The 2.0.13 version of packaging-farm was released with these modifications, installed on all build machines with the associated migrations.
Continue reading “Rebuilding XiVO gallifrey”
The version 2.0.12 of packaging-farm was published with modifications to the package version conventions and disk usage optimization. The gallifrey production and development build machines were upgraded and the errors found when trying to rebuild were reported.
Continue reading “XiVO package versioning”
The version 2.0.11 of packaging-farm was published with bug fixes mostly related to the submission of XiVO packages. The bug fixed were kernel-module ignores SOURCE_MODULE, submit-xivo.sh must reuse tarbal and epoch always triggers submission. The submission script was enhanced to reduce the number of hg pull when examining multiple packages. The skaro build machine was upgraded with the latest version of packaging-farm. The versions of the XiVO packages that were using the old SVN convention were updated.
Continue reading “Bug fixing XiVO package generation”
The 2.0.10 version of packaging-farm was published with safeguards against package version inconsistencies and reduced verbosity. It was installed on the skaro and gallifrey virtual machine used to build XiVO and tested on gallifrey-dev.
Continue reading “XiVO packaging verbosity and safeguards”
As the avencall team start to use packaging-farm to build the next release of XiVO, locking was implemented to avoid confusion. The +build prefix is now added automatically by packaging-farm to avoid the publication of duplicate packages. The addition of a source.list was documented. A kernel module bug occurring when the module had a name different than the package was fixed. The git repositories were set togit://git.proformatique.com/official . The version 2.0.9 was published with all the changes and installed.
Continue reading “Multiple users building on the XiVO packaging machine”