This probably sounds stupid, but it’s real. Is there a link to documentation for Verdin imx8m-plus line where we have a Yocto script that builds a stripped down Linux. Some other script that builds and deploys Uboot then deploys our Linux OS leaving a writable partition for cross compiled debugging deployment?
This container stuff is getting to be a real problem.
Canonical/Ubuntu is adding to the pain lately as well.
The following packages have unmet dependencies: libglib2.0-dev : Depends: libglib2.0-0 (= 2.64.6-1~ubuntu20.04.3) but 2.64.6-1~ubuntu20.04.4 is to be installed Depends: libglib2.0-bin (= 2.64.6-1~ubuntu20.04.3) libmount-dev : Depends: libmount1 (= 2.34-0.1ubuntu9) but 2.34-0.1ubuntu9.1 is to be installed Depends: libblkid-dev but it is not going to be installed uuid-dev : Depends: libuuid1 (= 2.34-0.1ubuntu9) but 2.34-0.1ubuntu9.1 is to be installed zlib1g-dev : Depends: zlib1g (= 1:1.2.11.dfsg-2ubuntu1) but 1:1.2.11.dfsg-2ubuntu1.2 is to be installed E: Unable to correct problems, you have held broken packages.
They pushed out new runtime libraries for 20.04 LTS and did not bother to update the dev package dependencies. I haven’t yet gone further up the food chain to see if Debian itself is the one at fault here. That’s an after lunch problem.
Given that this is a medical device, we would like to see what it takes to completely remove containers, using this SOM as any other embedded system.
It’s partially a security/getting it through FDA approval thing. The other part is flexibility. If Debian is the one that hosed up the repos then all Debian based distros will have this problem. That means we have to move to RPM or Arch or … based to get something stable.
Being forced to update is a dangerous thing. Broken packages get pushed to repos all of the time.