Control: reopen -1 Control: reassign -1 systemd 215-4
Am Donnerstag, den 18.09.2014, 08:09 +0200 schrieb Martin Pitt: > Paul Menzel [2014-09-17 23:08 +0200]: > > 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. > > Well yes, then systemd would be held back for upgrading until > systemd-shim 8-2 lands. Isn't that pretty much what we are looking > for? I would have thought so too, but systemd was upgraded on my systemd when running `aptitude safe-upgrade`. > But can this happen in the first place? The newer systemd in unstable > makes systemd-shim uninstallable in testing, so britney ought to hold > back the systemd migration until systemd and systemd-shim can enter > testing in lockstep. The point is, if systemd-shim 8-1 is already installed from before (some months ago). > > In my opinion, unfortunately systemd needs to have a line similar to: > > > > Breaks: systemd-shim (<< 8-2) > > Now that we stopped having the "API gap" between unstable and > experimental we could indeed do that. I'm a bit surprised that we need > that in the first place though (see above). > > > Are you going to reassign to systemd or should I do it? > > If we need it, please go ahead. (I might have misunderstood how > britney works) I reopen the bug and reassign it to systemd. But I am still confused, how this problem occurred, that means why systemd was allowed to upgrade in the first place. Thanks, Paul
signature.asc
Description: This is a digitally signed message part
