Bug#459873: python-apt: Unmet dependencies
Christian Perrier wrote: > Quoting Pierre Habouzit ([EMAIL PROTECTED]): > >>> 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#459873: python-apt: Unmet dependencies
Quoting Pierre Habouzit ([EMAIL PROTECTED]): > > 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 signature.asc Description: Digital signature
Bug#459873: python-apt: Unmet dependencies
On Wed, Jan 09, 2008 at 08:41:46AM +, Anthony Campbell wrote: > Package: python-apt > Version: 0.7.4 > Severity: grave > Justification: renders package unusable > > 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. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpBx7TEvh3FH.pgp Description: PGP signature
Bug#459873: python-apt: Unmet dependencies
Package: python-apt Version: 0.7.4 Severity: grave Justification: renders package unusable 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 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.23-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-apt depends on: pn libapt-inst-libc6.6-6-1(no description available) pn libapt-pkg-libc6.6-6-4.(no description available) ii libc6 2.7-5GNU C Library: Shared libraries ii libgcc1 1:4.3-20080104-1 GCC support library ii libstdc++6 4.3-20080104-1 The GNU Standard C++ Library v3 ii lsb-release 3.1-24 Linux Standard Base version report ii python 2.4.4-6 An interactive high-level object-o ii python-central 0.5.15 register and build utility for Pyt python-apt recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
