1
edit
Changes
→Possible Breakage Scenarios
# libA-1.0-1.fc17 is built (Provides: libA.so.1)
# packageB-1.0-1.fc17 depends on has a BuildRequires: packageC but is bootstrapped without it and built# packageC-1.0-1.fc17 depends on has a BuildRequires: 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 has a BuildRequires: packageC and is built with packageC-1.0-1.fc17,libA-1.0-1.fc17,packageB-1.0-1.fc17
# libA-2.0-1.fc18 is built (Provides: libA.so.2)
## Attempting to build the full version of packageB-2.0-1.fc18 will depend on packageC-1.0-1.fc17 which requires libA.so.1 which only find libA.so.2 with the current repodata (this package needs to be bootstrapped again)
# libA-1.0-1.fc17 is built (Provides: libA.so.1)
# packageB-1.0-1.fc17 depends on has a BuildRequires: packageC but is bootstrapped without it and built# packageC-1.0-1.fc17 depends on has a BuildRequires: 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 has a BuildRequires: packageC and is built with packageC-1.0-1.fc17,libA-1.0-1.fc17,packageB-1.0-1.fc17# packageB-2.0-1.fc18 depends on has a BuildRequires: packageC and is built with packageC-1.0-1.fc17,libA-1.0-1.fc17,packageB-1.0-2.fc17# packageC-2.0-1.fc18 depends on has a BuildRequires: libA,packageB and is built with libA-1.0-1.fc17,packageB-2.0-1.fc18 ,packageC-1.0-1.fc17 (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 packageC will require libA.so.1 which is not being provided for since the updated libA only provides libA.so.2
=== Scenario 3 ===
# libA-1.0-1.fc17 is built (Provides: libA.so.1)
# packageB-1.0-1.fc17 has a BuildRequires: packageC but is bootstrapped without it and built
# packageC-1.0-1.fc17 has a BuildRequires: libA,packageB and is built with libA-1.0-1.fc17,packageB-1.0-1.fc17 (Requires: libA.so.1)
# packageC-2.0-1.fc18 has a BuildRequires: libA,packageB and is built with libA-1.0-1.fc17,packageB-1.0-1.fc17 (Requires: libA.so.1)
# libA-2.0-1.fc18 is built (Provides: libA.so.2)
## packageB-2.0-1.fc18 depends on packageC which requires packageC-2.0-1.fc18,libA-2.0-1.fc18,packageB-1.0-1.fc17 which requires libA.so.1 which only finds libA.so.2 given the current repodata
=== Scenario 4 ===
# libA-1.0-1.fc17 is built (Provides: libA.so.1)
# packageB-1.0-1.fc17 has a BuildRequires: packageC but is bootstrapped without it and built
# packageC-1.0-1.fc17 has a BuildRequires: libA,packageB and is built with libA-1.0-1.fc17,packageB-1.0-1.fc17 (Requires: libA.so.1)
# packageB-2.0-1.fc18 has a BuildRequires: packageC and is built with packageC-1.0-1.fc17,libA-1.0-1.fc17,packageB-1.0-1.fc17
# libA-2.0-1.fc18 is built (Provides: libA.so.2)
## packageC-2.0-1.fc18 has a BuildRequires: libA,packageB which finds libA-2.0-1.fc18,packageB-2.0-1.fc18,packageC-1.0-1.fc17 which requires libA.so.1 which only finds the latest libA.so.2 in the repodata
= Downloads =
