I believe this will only happen if you are overwriting your existing rpi-clone drive AFTER moving from buster to bullseye (if your old clone drive had the older buster on it).
cmake
cmake: error while loading shared libraries: libhogweed.so.4: cannot open shared object file: No such file or directory
bc -l
bc: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory
You will need to update the rsync options to include '-c' for checksum to get around this issue.
I resolved it on a booted clone by: sudo apt reinstall bc libreadline6 libreadline8 readline-common librtmp1
I believe this will only happen if you are overwriting your existing rpi-clone drive AFTER moving from buster to bullseye (if your old clone drive had the older buster on it).
cmake
cmake: error while loading shared libraries: libhogweed.so.4: cannot open shared object file: No such file or directory
bc -l
bc: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory
You will need to update the rsync options to include '-c' for checksum to get around this issue.
I resolved it on a booted clone by: sudo apt reinstall bc libreadline6 libreadline8 readline-common librtmp1
Here are threads about the issue: https://forums.raspberrypi.com/viewtopic.php?p=1965273&sid=1f60f9cad9620f8474d33d2a0db1d2d4#p1965273
https://forums.raspberrypi.com/viewtopic.php?t=325414
I assume this can also be avoided if you use the rpi-clone -f command to initialize a clone after an upgrade.