I ran into this last fall as well.
Questions:
1. Can anyone else reproduce this on the Trixie Lite image? Is it actually a bug?
2. Does anyone know which build script or package rule mistakenly created this path as a directory during the image creation?
3. To work around this safely, should I simply `rm -rf` the directory and `touch` it as a standard 0644 file?
Thank you!
- You're using an old IMG (2025-10-01), which most definitely had this problem. This issue does NOT exist on the most recent IMG (2026-04-21).
- See 1)
- You could, but there were a few other issues in that IMG. Best to just move forward and use the most recent IMG
Statistics: Posted by bls — Tue Jun 02, 2026 11:02 pm





