Changes

Jump to: navigation, search

Koji Follow

596 bytes added, 10:27, 8 July 2013
Run Notes
= Koji Follow Que Script =
== Build Notes ==
* This script does not automatically solve circular dependency issues (which there are a lot of, especially packages like sub perl modules)
** latest-follow mode will perform a "list-tagged --latest" and que each unbuilt package in the given order
== Possible Common Repository Breakage Scenarios due to basic circular dependencies ==
=== Scenario 1 All of the following examples take place after this series of events ===
* Start of initial-build
# libA-1.0-1.fc17 is built (Provides: libA.so.1)
# packageB-1.0-1.fc17 depends on (BuildRequires: libA,packageC but ) is bootstrapped without it and temporarily builtwith its packageC requirement removed (Requires: libA.so.1)# packageC-1.0-1.fc17 depends on (BuildRequires: libA,packageB and is built with ) installs libA-1.0-1.fc17,packageB-1.0-1.fc17 and is built (Requires: libA.so.1)# packageB-1.0-2.fc17 depends on (BuildRequires: libA,packageC and is built with ) installs libA-1.0-1.fc17,packageC-1.0-1.fc17and is built (Requires: libA.so.1) === Building a new library first and the packages that depend on it later === * Start of mass-rebuild
# libA-2.0-1.fc18 is built (Provides: libA.so.2)
## * Attempting to build the full version of packageB-2.0-1.fc18 or packageC will depend on packageC-1.0-1.fc17 BuildRequire each other and which requires both will then Require libA.so.1 which will then only find libA.so.2 with in the current repodata (this package needs to be bootstrapped again)## Attempting to build packageC-2.0-1.fc18 will depend on packageB-1.0-2.fc17 which will depend on packageC-1.0-1.fc17 which brings us to the same breakage error above
=== Scenario 2 Building new packages first and then the following libraries they depend on after ===
* Start of mass-rebuild# libApackageB-12.0-12.fc17 is built fc18 (ProvidesBuildRequires: libA.so.1,packageC)# packageBinstalls libA-1.0-1.fc17 depends on packageC but is bootstrapped without it and built# ,packageC-1.0-1.fc17 depends on libA,packageB and is built with libA-1.0-1.fc17,packageB-1.0-1.fc17 (Requires: libA.so.1)# packageB-1.0-2.fc17 depends on packageC and is built with packageC-1.0-1.fc17# packageB-2.0-1.fc18 depends on packageC and is built with packageC-1.0-1.fc17# packageC-2.0-1.fc18 depends on (BuildRequires: libA,packageB and is built with ) installs libA-1.0-1.fc17,packageB-2.0-12.fc18 and is built (Requires: libA.so.1)
# libA-2.0-1.fc18 is built (Provides: libA.so.2)
## * All packages will now appear to be up to date and current except that the repo is now broken as trying to install packageB or packageC will require libA.so.1 which is not being provided for at all since the updated libA only provides libA.so.2 == Run Notes == * Packages are not processed in alphabetical order and the output is not displayed in numerical order* The koji error log is for processing messages and the koji stdout log is for queing messages* You need to add any new package names to a tag before they are built* You need a lot of free space in the current directory that the script is running in* Before running the script, attempt a scratch build of a sample package with the given build tag* You can redirect stderr to stdout and write stdout to a file so that the messages are in order with each other
= Downloads =
</pre>
<b>python ~/kf/koji-follow.py ~/kf/koji-follow.conf > ~/logskf/kfo.log 2> ~/logskf/kfe.log</b>
== latest-follow mode ==
</pre>
== Execution Example == <b>python ~/kf/koji-follow.py ~/kf/koji-follow.conf > ~/logskf/kfo.log 2> ~/logskf/kfe.log</b>
= Example Log Output =
== STDOUT Messages ==
1
edit

Navigation menu