issues upgrading from kali 2.0 to 2016.1 rolling.

[gunner_k]

Dear all,
i have been facing issues upgrading from kali 2.0 to the latest 2016.1 rolling.
I have a kali 2.0 in virtual box and with recent upgrades, i tried to do the same.
As per the instructions given on the page of kali.org

cat << EOF > /etc/apt/sources.list
deb http://http.kali.org/kali kali-rolling main non-free contrib
EOF

apt-get update
apt-get dist-upgrade # get a coffee, or 10.
reboot

i followed the instructions to upgrade, but after downloading the required upgrades, there is a fatal error that i encounter:

E: This installation run will require temporarily removing the essential package sysvinit-utils:i386 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.
E: Internal Error, Could not early remove sysvinit-utils:i386 (2)

I tried to research for the error, but i am unable to find a solution for this. As per the information i can find, it is a 'severe' bug in debian.

I am curious that did anybody encounter the same error while upgrading?
Is there any way this can be resolved??

Thanking you.

[Pirtal]

Hi,

I have the same error, and so far couldn't solve it !
Did you find a way to complete the upgrading process ?

Thanks in advance,

[DebUserHere]

I'm having the same issue, but with Debian Jessie 8.3: as soon as I

apt dist-upgrade

to testing, or

apt install virtualbox-guest-utils and virtualbox-guest-x11

, I get the same error. Strangely, this only happens when installing inside VirtualBox 5.0.16 r105871. I didn't have this issue when installing inside VMWare Player 6.0.7 build-2844087 (I did have major kernel problems here, on the other hand). It seems that Jessie 8.3 does not play nicely with virtual machines, and since Kali is based upon it (I think), no wonder that the two Kali users above encountered the same issue.

[DebUserHere]

As per the information i can find, it is a 'severe' bug in debian.

Could you please add a link towards the information that you have found specific to Debian? My web searches only produce answers from May 2015 the latest, nothing about this very instance of the bug (an almost exactly one having been closed as solved in May 2015).https://bugs.debian.org/cgi-bin/bugr...cgi?bug=786469