...
In the given example, the relevant parts in the dependency graph are
| No Format |
|---|
diffimg-8.0.28+2 |
...
--- coreUtils-0.5.2+4 |
...
--- psycopg-2.4.6+4 |
...
--- python-2.7.6+1 |
...
--- cxOracle-5.1.2+8 |
...
--- python-2.7.6+1 |
The new packages proposed by the system would be the following:
| No Format |
|---|
diffimg-8.0.28+3E |
...
--- coreUtils-0.5.2+5E |
...
--- psycopg2-2.4.6+5E |
...
--- cxOracle-5.1.2+9E |
where psycopg-2.4.6+5E and cxOracle-5.1.2+9E would have dependencies on python-2.7.7+0. The 'E' appended to the package version indicates that by default EXPERIMENTAL packages are created. On the console, you would see something like:
| No Format |
|---|
cxOracle-5.1.2+8 |
...
== |
...
> cxOracle-5.1.2+9E |
...
psycopg2-2.4.6+4 |
...
== |
...
> psycopg2-2.4.6+ |
...
5E coreUtils-0.5.2+4 |
...
== |
...
> coreUtils-0.5.2+5E |
...
diffimg-8.0.28+ |
...
2 ==> diffimg-8.0.28+3E |
Note that if there would already be a psyopg2-2.4.6 version with the same dependencies as psycopg-2.4.6+4 but the new python version and identical build file there would be no need to create a new package version for psyopg2-2.4.6. This is recognized by the system and no new psyopg2-2.4.6 package version would be proposed. This means that if you specify a reference and a package to be replaced for which a propagated version already exists no propagation is performed.
...