indicator-network needs to declare a minimal version of unity8 in the package dependencies

[Oliver Grawert]

it recently happened that we had a change of the indicator protocol in unity8.
due to indicator-network not declaring a "Breaks: unity8 (<< $minimal_version)" dependency against the first unity8 version that ships the needed protocol, indicator-network was able to migrate alone from the proposed archive pocket to the main archive which caused breakage.

to prevent this in the future indicator-network mush add a dependency on the minimal version of unity8 that ships the needed protocol version.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Robert Bruce Park (robru)]

Agreed, but this is really just one instance of a much larger pattern of problems. We are *constantly* publishing silos that contain sets of interdependent changes, for which the debian packaging does not reflect the minimum required versions of each package. Most of the time the packages migrate through -proposed in a reasonable time frame, but on more than one occaision we have been bitten by -proposed holding back just part of a silo, for a long enough length of time that an image gets built with half a silo landed in it.

The basic problem is that we *test* silos as if they were atomic units, but they really are in no way atomic. I'd ideally like to see CI Train grow an automatic debian dependency munger that makes each package migrate atomically through -proposed, but more feasibly we need developers to just update their packaging versions every time they do a landing.