Hi. On Mon, Dec 30, 2019 at 10:33:28AM +0200, Andrei POPESCU wrote: > dpkg would not even warn if one would install packages from one on the > other (they are both "armhf"), but the result is hard to predict.
For Raspberry Pi the result was predictable. If a package was providing a binary executable or a library - it failed with SIGILL. If a package was providing some kind of arch-independent script - it worked. Starting with Raspberry Pi 2 nearly any Debian-provided binaries have started to work. The exceptions to this rule are packages that depend on kernel features which are included in Debian, but are missing in Raspbian, and OpenGL-dependent ones. Latter are more-or-less operational with Raspberry Pi 3. > [1] Not sure if/how this applies with current Raspbian releases. Do they > still recompile Debian packages? If yes, why? Yes, they do. Some packages have Raspbian-specific patches (dhcpcd, to name a few), most are rebuilt "just in case". Reco