Custom Query (344 matches)

The common build cycle is rpmbuild-bot PACKAGE test followed by rpmbuild-bot PACKAGE followed by rpmbuild-bot PACKAGE upload. All steps are usually done on the same machine and the third one commits the resulting .spec file after all .RPMs are successfully uploaded.

However, there is a different scheme used by e.g. Y. Dario. He first makes a test build on his local machine, then commits the .spec file, then runs the main build and the upload command on a remote machine. Perhaps, we should add a commit command to rpmbuild-bot that just shows the .spec diff and then commits it. To have unified version checks, unified commit messages and so on. Should be trivial.

We should purge old packages as new ones get released — this is to avoid cluttering the repositories with outdated and unneeded RPMs. Currently we do it by hand which is very time consuming and error prone.

A better idea is to teach rpmbuild-bot to automatically move outdated packages to a trash area when newer ones for a given program are uploaded. The trash is then to be purged each few months. This approach will require to store package build logs (used as indexes to collect RPM files belonging to a single build) on the repository machine rather than locally. But that's a needed feature anyway as it will allow to e.g. move packages between repositories not only by a person who built it but by anyone who has the required access.

Considering how many things need %TMPDIR%, we should add this and point it to %TMP%.