Hi! On Tue, 2026-01-06 at 23:56:24 +0100, [email protected] wrote: > Package: dpkg > Version: 1.22.21 > Severity: important
> I had a machine with amd-geode-processor running Devuan 5 (daedalus) > (equivalent to Debian Bookworm). Updating this machine to Devuan 6 > (excalibur)(equivalent to debian Trixie) failed in the process after > dpkg was updated to 1.22.21. Starting with Debian trixie i386 is only partially supported, see: https://www.debian.org/releases/stable/release-notes/issues.html#reduced-support-for-i386 In addition, dpkg's build system should not be optimized explicitly against any specific CPU, so I'm assuming that if its execution is generating invalid opcode traps, then that's because the compiler bumped its baseline. (You could try to rebuild dpkg in that non-VM i386 machine and pass -march=native -mcpu=native or similar.) > Flags: fpu de pse tsc msr cx8 sep pge cmov clflush > mmx mmxext 3dnowext 3dnow cpuid 3dnowprefetch vmmcall I'm not sure what opcode is emitting the trap (didn't dig into the disassembled output for that version), but sse2 is missing from this flags list, so that would be an obvious suspect. I'm afraid, given the support Debian offers over this, and unless Devuan wants to override that and provide support for this class of CPUs with mass rebuilds, there's not much to be done, and your best option is to not upgrade to a Debian trixie equivalent distribution. I'm thus planning on closing this report in a bit, unless there's compelling reasons to do otherwise. Thanks, Guillem
