dpkg warning today: /lib/firmware/raspberrypi/bootloader-2712/latest': Directory not empty

  • Today I've seen the following warnings when updating the system:

    ...

    Unpacking rpi-eeprom (26.9-1) over (26.8-1) ...

    dpkg: warning: unable to delete old directory '/lib/firmware/raspberrypi/bootloader-2712/latest': Directory not empty

    dpkg: warning: unable to delete old directory '/lib/firmware/raspberrypi/bootloader-2711/latest': Directory not empty

    ...


    I've seen this on another RPi w/o omv ...


    What does this mean?

    Anything to fix it?

    Raspi 4B, 4GB RAM, SSD-Boot, 2TB & 1TB SSD as data-disks in Sata/USB enclosure, IcyBox USB3-Hub

  • Have you tried the raspberry forum for answers?


    What I can think is maybe try to change the version of the eeprom via raspi-config to the STABLE instead of LATEST to see if it can clear the error

  • Have you tried the raspberry forum for answers?


    What I can think is maybe try to change the version of the eeprom via raspi-config to the STABLE instead of LATEST to see if it can clear the error

    No, not yet. If I can't get a definitive answer here, I'll give it a try.


    Your hint could help. Or I just do a clone from my system SD of my other RPI, and just try to delete the directories manually and see what happens ...


    But my hope was that other more experienced RPi users are observing the same warnings and have a safe solution.


    These warnings appeared last week first w the latest Linux updates.

    Raspi 4B, 4GB RAM, SSD-Boot, 2TB & 1TB SSD as data-disks in Sata/USB enclosure, IcyBox USB3-Hub

    • New
    • Official Post

    But my hope was that other more experienced RPi users are observing the same warnings and have a safe solution.


    These warnings appeared last week first w the latest Linux updates.

    These warnings are completely harmless. There is nothing to solve. It just means another package had a file in the directory. It is very common in many packages especially kernel and firmware packages.

    omv 7.6.0-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.1 | kvm 7.0.16 | compose 7.3.3 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • These warnings are completely harmless. There is nothing to solve. It just means another package had a file in the directory. It is very common in many packages especially kernel and firmware packages.

    Would mean: "Just do nothing - maybe its somehow fixed or just disappearing in future"?

    Those warnings, especially if they occur the first time, are making me a little bit nervous because I cannot overview what are possible future implications

    Raspi 4B, 4GB RAM, SSD-Boot, 2TB & 1TB SSD as data-disks in Sata/USB enclosure, IcyBox USB3-Hub

    • New
    • Official Post

    Would mean: "Just do nothing - maybe its somehow fixed or just disappearing in future"?

    It means just do nothing. What needs to be fixed? The package is trying to clean up a directory IF it is empty. It isn't empty so it doesn't need to clean it up. There is no way a package can know if another package puts files in the same directory. This is why the rmdir command is so safe. It will remove the directory if it is empty otherwise it leaves it alone.

    Those warnings, especially if they occur the first time, are making me a little bit nervous because I cannot overview what are possible future implications

    Why are you nervous about it? What do you think might happen? Absolute worst case, there is an empty directory on your system. There could be hundreds of empty directories on your system now causing zero problems.

    omv 7.6.0-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.1 | kvm 7.0.16 | compose 7.3.3 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Just for information and interested people. Found more info/backgroud here in the official Raspberry forum.


    Just did the update, got the same warnings, but I did a "dpkg -L rpi-eeprom" before and after which let me diagnose it. The paths in the package have changed from /lib/firmware/raspberrypi to /usr/lib/firmware/raspberrypi. dpkg isn't smart enough to understand that /lib is a symlink to /usr/lib on modern Debian, so it tries to delete the paths which are no longer in the package. Everything that should be there seems to be there after the upgrade, and "dpkg -V rpi-eeprom" doesn't show any problems. Whether that's an intentional change, or more "correct", I can't really say for sure. I can, however, say for certain that it's just harmless noise in practical terms.


    An Issue is reported at GitHub: https://github.com/raspberrypi/rpi-eeprom/issues/655

    Raspi 4B, 4GB RAM, SSD-Boot, 2TB & 1TB SSD as data-disks in Sata/USB enclosure, IcyBox USB3-Hub

    Edited once, last by Teschbert ().

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!