currently, the problem is:
systemd-shim vesion 8-2 (testing) breaks systemd <209, but in testing we still
have systemd 208-8, while 215.xx still stays in unstable.
this situation causes systemd-shim in testing to be unupgradable without
installing systemd-215 from unstable manually.
below is the illustration for this dependecy trap:
>21:09:44 276 ~$ apt-cache policy systemd-shim
systemd-shim:
Установлен: 7-1
Кандидат: 8-2
Таблица версий:
8-2 0
990 ftp://ftp.ru.debian.org/debian/ testing/main amd64 Packages
50 ftp://ftp.ru.debian.org/debian/ unstable/main amd64 Packages
*** 7-1 0
100 /var/lib/dpkg/status
>21:09:55 276 ~$ apt-cache show systemd-shim/testing | grep "break"
Breaks: systemd (<< 209)
>21:10:41 276 ~$ apt-cache policy systemd
systemd:
Установлен: 208-8
Кандидат: 208-8
Таблица версий:
215-5+b1 0
50 ftp://ftp.ru.debian.org/debian/ unstable/main amd64 Packages
*** 208-8 0
990 ftp://ftp.ru.debian.org/debian/ testing/main amd64 Packages
100 /var/lib/dpkg/status
44-11+deb7u4 0
500 ftp://ftp.ru.debian.org/debian/ wheezy/main amd64 Packages
500 http://security.debian.org/ wheezy/updates/main amd64 Packages
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
