Hi,
> This is because your CPU architecture is not 32 bit, and not i586 or lower.
> I'm sure if you set that by hand, you will be able to reproduce that.
Yes, I know. Just wanted to confirm that upgrade is safe on 64-bit systems :)
On 17/05/16 14:21, Vlad Orlov wrote:
> Hi,
>
> This doesn't happen even in VirtualBox working on a host with an old Core 2
> Duo
> (both host and guest Debian installations are 64-bit). The upgrade went fine.
This is because your CPU architecture is not 32 bit, and not i586 or lower.
I'm sure if
Hi,
This doesn't happen even in VirtualBox working on a host with an old Core 2 Duo
(both host and guest Debian installations are 64-bit). The upgrade went fine.
Like Lee, me neither can reproduce it on my AMD Athlon(tm) II X4 640 processor.
I think it is safe to upgrade.
Regards.
--
Diego.-
Hi Dirk,
which type of processor do you have on that machine? As ydirson pointed out,
older CPU types (80586 and below on the i386 architecture) are not supported
anymore in stretch.
For everyone else: I can't reproduce this bug on my Intel i5, so it's safe to
upgrade.
Regards,
Lee
Would it be related to gcc taking advantage of the drop of i565 support ?
https://lists.debian.org/debian-devel-announce/2016/05/msg1.html
Package: tar
Version: 1.28-2.2
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
upgrading tar breaks apt-get/dpkg due to "illegal instruction" errors.
* What led up to the situation?
tar was upgraded: tar (1.28-2.1 => 1.28-2.2)
* What exactly did you do (or
7 matches
Mail list logo
