Dear Martin,
thank you for your quick response!
Am Mittwoch, den 17.09.2014, 10:25 +0200 schrieb Martin Pitt:
> Version: 8-2
>
> Control: reassign 76194 systemd-shim 8-1
>
> Paul Menzel [2014-09-17 9:29 +0200]:
> > Dear Debian folks,
> >
> >
> > running `aptitude safe-upgrade`, systemd failed to upgrade because
> > systemd-shim conflicts with systemd >= 205.
> >
> > systemd-shim (8-1) beschÃĪdigt systemd (>= 209) und ist
> > installiert.
>
> This was fixed yesterday in systemd-shim 8-2, which works with systemd >= 209.
That is great, but it does not fix the error of broken upgrade path to
my knowledge. Users might experience that bug when systemd 215-4
migrates to testing before systemd-shim 8-2.
In my opinion, unfortunately systemd needs to have a line similar to:
Breaks: systemd-shim (<< 8-2)
I have no idea why aptitude did not figure that out itself by the
systemd-shim meta data.
Are you going to reassign to systemd or should I do it?
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
