DLRN builds and maintains yum repositories following OpenStack upstream commit streams. (DLRN is not an acronym or an abbreviation, and it can be pronounced “dee el arr en”.)
Documentation is available at http://dlrn.readthedocs.org/en/latest/
Setup
# yum install git createrepo python-virtualenv mock gcc \
redhat-rpm-config rpmdevtools httpd libffi-devel \
openssl-devel yum-utilsAdd the user you intend to run as to the mock group and login again.
$ git clone https://github.com/softwarefactory-project/DLRN.gitIf you want to serve the built packages and the status reports, enable the httpd service, and then either add a section in the server configuration to map a URL to the data directories, or create a symbolic link:
# systemctl start httpd
# cd /var/www/html
# ln -s <datadir>/repos .Preparing
$ cd DLRN
$ virtualenv ../dlrn-venv
$ . ../dlrn-venv/bin/activate
$ pip install --upgrade pip
$ pip install -r requirements.txt
$ python setup.py developEdit projects.ini if needed.
Bootstrapping
Some of the projects require others to build. As a result, use the special option --order to build in the order computed from the BuildRequires and Requires fields of the spec files when you bootstrap your repository.
$ dlrn --orderWhen using this special option, a special variable repo_bootstrap is defined in the specs, with a value of 1. You can use this variable if needed, to break dependency loops between packages. For example:
%if 0%{?repo_bootstrap} == 0
BuildRequires: package-with-circular-dependency
%endifRunning
Once all the packages have been built once, you can get back to build the packages in the order of the timestamps of the commits.
$ dlrnTroubleshooting
If you interrupt dlrn during mock build you might get an error
OSError: [Errno 16] Device or resource busy: '/var/lib/mock/dlrn-fedora-x86_64/root/var/cache/yum'Solution is to clear left-over bind mount as root:
# umount /var/lib/mock/dlrn-fedora-x86_64/root/var/cache/yumOther requirements
If the git clone operation fails for a package, DLRN will try to remove the source directory using sudo. Please make sure the user running DLRN can run rm -rf /path/to/dlrn/data/* without being asked for a password, otherwise DLRN will fail to process new commits.
3 maintainers
Metadata
3 maintainers
Release files for DLRN 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| DLRN-0.4.0.tar.gz | 476.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| DLRN-0.4.0-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 580.7 kB
Release files / DLRN-0.4.0.tar.gz
| Download URL | DLRN-0.4.0.tar.gz |
|---|---|
| Size | 476.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f12edfcfdb148ba639f62056803f2c79e59927aa8d492ac2f85f40831aade92f
|
|
BLAKE2b-256 checksum How to use checksums |
5d0e72ad8184221c8a0a66db9f3dd543f959ad42d6b04886d9afa66db884c8ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / DLRN-0.4.0-py2-none-any.whl
| Download URL | DLRN-0.4.0-py2-none-any.whl |
|---|---|
| Size | 103.9 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
cd5561e52220f20de4b82210332f8d99c73470411ce5cce93ba00424f47dfb9e
|
|
BLAKE2b-256 checksum How to use checksums |
48e22d1aa554dcdb3cf3a6b938e207160f2b91c9ab035f8a1f7b1f02f19c716b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
