Control: severity -1 normal Hi! On Thu, May 22, 2014 at 11:32:22PM -0400, Martin Furter wrote: > Package: apt > Version: 1.0.3 > Severity: critical > Justification: breaks the whole system Well, if apt segfaults before anything is installed it by definition isn't breaking the system. You can't upgrade your system, which defeats the propose of apt, but your system is still okay. Hence downgrading and the following hopefully describes why I set it so low… > Before the dist-upgrade I upgraded apt. Then I ran "apt-get dist-upgrade". It > downloaded all packages and then crashed with "segmentation fault". Old system, policykit (and therefore libpam-systemd) in the bug title and the list of downloaded packages includes systemd-sysv… I bet you are one of those hit by #748355. See there for the nitty-gritty details, but in essence: APT encounters an "impossible to upgrade safely" and "forbidden by debian policy" situation here, which the involved packages have to solve, so that a good upgrade path exists and apt can do its assigned work. I finally managed to get a patch together yesterday to restore apts detection for these kind of situations, so the next upload should fix the segfault and instead a user should in the future be greeted again with the following old error message: | E: This installation run will require temporarily removing the essential | package sysvinit:amd64 due to a Conflicts/Pre-Depends loop. This is | often bad, but if you really want to do it, activate the | APT::Force-LoopBreak option. Not really a lot better from a user point as you still can't really upgrade, it is just slightly less scary than a segfault, but that bug has really to be resolved on the systemd/sysvinit-side … Best regards David Kalnischkies
Attachment:
signature.asc
Description: Digital signature