Bug#459873: python-apt: Unmet dependencies

[Luk Claes <luk@debian.org>]

Christian Perrier wrote:
> Quoting Pierre Habouzit (madcoder@debian.org):
> 
>>> Wajig depends on python-apt but trying to install it I get:
>>>
>>>  python-apt: Depends: libapt-inst-libc6.6-6-1.1 but it is not installable
>>>               Depends: libapt-pkg-libc6.6-6-4.6 but it is not installable
>>   Yes, python-apt needs a binNMU as do the other apt usual suspects.
> 
> 
> This situation triggers a wild (and maybe not sooriginal...) idea in
> my mind:
> 
> This APT upload was planned and announced for a few days. Otavio
> mentioned it.
> 
> However, of course, all maintainers of packages that would need a
> binNMU can only request that binNMU when the planned apt package is
> uploaded, not before. Or, more precisely, the binNMU cannot be
> scheduled before the upload.
> 
> However, if binNMUs could specify a package/version combination to
> "wait" for, they could then be scheduled *before* the package that
> triggers the binNMU is uploaded. Then, the autobuilders would build
> the binNMU only when that package reaches the archive for their
> architecture.
> 
> I hope this is clear (harder to explain then the real idea,
> indeed)....
> 
> Here, all packages that require a binNMU because of apt 0.7.10 upload
> could have been scheduled *before* the upload with "Needs: apt (>=0.7.10)"
> or something similar....

The problem is that binNMU and dep-wait can't be scheduled at the same
time, they have to be scheduled one after the other: the dep-wait after
the binNMU. For some packages when this was done this meant that the
binNMU was already building before a dep-wait could be scheduled...

Cheers

Luk