Ewoud Kohl van Wijngaarden
Ewoud Kohl van Wijngaarden
Since Fedora 31 it's possible to use [Dynamic BuildRequires](https://fedoraproject.org/wiki/Changes/DynamicBuildRequires). This removes the need to change the spec file all the time to keep in sync with the Foreman repo itself....
This approach is based on rpmdist-repoquery where a certain directory structure is used to track repositories. That is then selected, together with a releasever. Our own repositories are made generic...
I found out there already was a task to create the .mo files. This avoids having to store them in git as part of the release. The goal of this...
By owning the directories we can also ensure they are properly cleaned up on upgrade. This is now a draft to see if this works. If it does, we should...
This allows regular tools, like spectool, to retrieve the sources which makes development easier. Once the build changes to rc1 or actual releases the old URL is used automatically. Right...
This creates separate RPMs for each scenario. This allows the user to install just a single scenario and never use the --scenario parameter. Packages created: * foreman-installer-scenario-$scenario foreman/katello/foreman-proxy-content scenarios *...
Needs https://github.com/theforeman/foreman-installer/pull/822. To test: ``` dnf install https://yum.theforeman.org/releases/latest/el8/x86_64/foreman-release.rpm https://yum.puppet.com/puppet7-release-el-8.noarch.rpm cat
The aim of this is to run tests on the built RPM to verify various scenarios using real systems.
This allows copying the scenario without having to modify the target version everywhere. Ideally more steps would be taken out and reused. This should probably be applied to many files,...
This is the latest documented version now. What this PR really is about is to see if master is also broken. At least the released version fails to build in...