>>>>> "D'R" == Didier 'OdyX' Raboud <o...@debian.org> writes:
D'R> On those 'slow' architectures, unsatisfied dependencies are frequent, but
almost
D'R> always get solved by _waiting_ (I run 'aptitude update; aptitude
safe-upgrade'
D'R> daily and I don't even see these issues).
Try 'aptitude update; aptitude full-upgrade'
All I know is I use
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
I don't know if that architecture is slow.
Looking again at
The following packages have unmet dependencies:
linux-image-2.6-686: Depends: linux-image-2.6.37-1-686 which is a virtual
package.
linux-image-686: Depends: linux-image-2.6.37-1-686 which is a virtual package.
linux-doc-2.6: Depends: linux-doc-2.6.37 which is a virtual package.
Why can't they simply ensure the lower layers in this particular
dependency pyramid are sent out before or at the same time as the other
parts?
E.g., if I have two web pages, one referring to the other, I know to
make sure the one does not appear before the other.
Anyway, there upon full upgrade we get asked:
The following actions will resolve these dependencies:
Remove the following packages:
1) linux-doc-2.6
2) linux-image-2.6-686
3) linux-image-686
One slip of the finger and we have removed our operating system, "never
to boot again", "it was time for grandpa to retire anyway".
Yes of course it will probably ask us "are we sure?".
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/871v37gdgv....@jidanni.org
