Lerking/rpi-clone
1
0
Fork 0
Code Issues 129 Pull Requests 10 Packages Projects Releases Wiki Activity

rclone fails to update libraries with same timestamp & length. #146

New Issue
Open
opened 2022-09-17 15:32:24 +02:00 by bdwilson · 0 comments
bdwilson commented 2022-09-17 15:32:24 +02:00 (Migrated from github.com)
Copy Link

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.

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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
duplicate
enhancement
invalid
question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Lerking
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Lerking/rpi-clone#146
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?