Hi Seb,

I've seen this occur for a different scenario (which I'll mention further below).

There are a couple of things to do. Firstly, try to see what packages are held, by typing apt-mark showhold

If you see just one or two packages held, then perhaps they need reinstalling.

However, if you see many packages held, then that's a sign that they may have been held by some install or config script or maybe some package manager issue in the background. Since many packages to be held is unlikely to be an actual problem with the packages, I reckon there's a fair chance it's safe to unhold them all in bulk. The command is apt-mark unhold $(apt-mark showhold)

The scenario in which I've seen it occur: I managed to cause a boot issue by adding an extra file system incorrectly, and so I had to re-image everything (there's a document which explains how to do that). However, some things have to be manually done after the reimage, and I noticed all packages held as part of my work to get things back to where they were after re-imaging. This is why I felt it was some script or package manager issue, but I've not dug deeper since I was more focused on getting things back up and running at the time.

Note: I can't guarantee that things will work for you if you just unhold things, it may make things worse. My suggestion to unhold it all is given in good faith but I dont know the underlying reason the hold occurred. However as mentioned there is a reimaging process although you won't entirely get everything back to precisely the original state as shipped, but it's good enough that there's no real concern if Linux gets corrupted during experimentation (although obviously it's worth getting things right to never have to re-image, it's a fallback just in case is what I mean). The re-imaging process requires an x64 Linux box and a USB type A to USB type C cable by the way.

Thanks ​@shabaz . I fixed it by just wiping the venv and then re-installing everything from scratch. So I am not really sure what the problem was. In the first install I got a bunch of warnings about packages, that had to be overwritten. In the second install there was no warnings just went through without any issues.

Great, glad it's all sorted! One thing I've noticed is that it's easy to accidentally fill up the storage while experimenting, so it's good to make use of the supplied microSD card as soon as possible too. I've tried installing a M.2 SSD, that works too (I'll write up the steps that I took in the next few days but in brief, I just used a SATA III M.2 SSD and then formatted and mounted it, no special steps required). But maybe its overkill since the microSD will likely be sufficient anyway.

Thanks for the help with this ​@shabaz !

Yeah, ​@Steven Hunsche was the one who suggested that a microSD card would be a good addition to the kit, for this reason!

I encountered the same error messages. I just replied “y” whenever it asked to attempt to install missing dependencies etc. And when it finished with errors, I ran the installation script again (without doing anything else). I think in total I ran the installation script 4 times. Each time it got some more packages fixed before everything got sorted out and I received a successful installation message.