apt full-upgrade fails - [1.20250326] - /etc/kernel/postinst.d/z50-raspi-firmware: 78: rsync: not found #1963
Comments
|
What's the output of |
and |
|
Okay, you seem to have the right version of raspi-firmware which lists rsync as a dependency. I'm not sure how you could've ended up without rsync. |
|
@XECDesign, note: this is after I already installed rsync and rerun the raspi-firmware:
Installed: (none)
Candidate: 1:1.20250326-1
Version table:
1:1.20250326-1 500
500 http://archive.raspberrypi.com/debian bookworm/main arm64 Packages
500 http://archive.raspberrypi.com/debian bookworm/main armhf Packages
1:1.20241126-1 -1
100 /var/lib/dpkg/status
1.20220830+ds-1 500
500 http://deb.debian.org/debian bookworm/non-free-firmware arm64 Packages
500 http://deb.debian.org/debian bookworm/non-free-firmware armhf Packages
raspi-firmware
PreDepends: dpkg (>= 1.17.14)
dpkg:armhf
Depends: dosfstools
Depends: rsync
rsync:armhf
Breaks: <linux-firmware-raspi3> (<< 1.20161123-2)
Breaks: <raspi3-firmware> (<< 1.20190718-1~)
Suggests: firmware-brcm80211
Suggests: firmware-misc-nonfree
Suggests: bluez-firmware
Replaces: <linux-firmware-raspi3> (<< 1.20161123-2)
Replaces: <raspi3-firmware> (<< 1.20190718-1~) |
|
Ah, just saw that the previous reply wasn't from OP... @Gyakusetsu If I had to guess, you removed raspi-firmware from your system (which is required for kernel updates to work) and kept the conffiles. so, the kernel hooks from that package still exist but won't work properly. |
|
On my side, I did with the Raspberry Pi what most helpdesks ask first: reboot! Surprise, the issues were gone. However, the Hailo was complaining about a version mismatch between the drive and the application, so I did with the Raspberry Pi what most helpdesks ask in second place: perform a fresh installation. |
|
@rei-vilo I don't think your issue is related to this one. |
|
I got the exact same issue on a fresh install of Raspberry Pi OS Lite (64-BIT) today on an old RPi3, I feel like a lot of people are experimenting the same but I cannot find what's wrong on my side. I'm interested in a solution if you guys ever come up with one. Let me know if there is any info that might help debugging. |
The info requested earlier should be enough to check whether it's the same issue for you. If you didn't uninstall raspi-firmware, then instructions on how to reproduce the issue would be good, starting from a clean install of Raspberry Pi OS from an official image. |
Describe the bug
Updating from kernel 6.6.51 to latest 6.12.20.
And installing rsync solves it, I wonder why rsync is needed at post kernel install script?
To reproduce
$ sudo apt update $ sudo apt upgrade # full-upgradeExpected behaviour
No errors
Actual behaviour
Errors
This is the info after installing rsync
sudo apt install rsync, so it might not be useful anymoreSystem
raspinfo.txt
Raspberry Pi 5
cat /etc/rpi-issue)?Raspberry Pi reference 2024-11-19
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 891df1e21ed2b6099a2e6a13e26c91dea44b34d4, stage2
vcgencmd version)?2025/03/10 17:10:37
Copyright (c) 2012 Broadcom
version 2bb2ae64 (release) (embedded)
uname -a)?Linux raspberrypi 6.12.18-v8-16k+ Enhancement Proposal: 16GB RAM Option for Future Raspberry Pi 5b+ Model #1862 SMP PREEMPT Wed Mar 12 12:33:09 GMT 2025 aarch64 GNU/Linux
Logs
Additional context
Add any other relevant context for the problem.
The text was updated successfully, but these errors were encountered: