Ziggy Avetisyan <[email protected]> wrote: > Can confirm, I've been getting them as well. If the issue persists I'll > simply write a little bash script to search for and delete specific empty > directories following this pattern, but for now the inconvenience doesn't > bother me much. More interested to know about the commit that led to this, > did I miss it somewhere?
Copied from https://gitlab.archlinux.org/pacman/pacman/-/issues/297#note_379655: A git bisection points to https://gitlab.archlinux.org/pacman/pacman/-/commit/45c4eef61de33bcdf3efcc2e97dc5eefb29e97b4 as the culprit. cc @morganamilo > > On Thu, Jan 8, 2026 at 8:02 PM David C Rankin <[email protected]> wrote: > > > All, Devs, > > > > From earlier discussions, I thought the empty stray directory problem > > in /var/cache/pacman/pkg had been identified and solved. But I was hit > > again today with directories created this year, e.g. sudo pacman -Sc > > > > error: could not open file /var/cache/pacman/pkg/download-peUZUV: Error > > reading fd 7 > > error: could not open file /var/cache/pacman/pkg/download-uq8lgk: Error > > reading fd 7 > > > > Where, e.g.: > > > > $ sudo ls -al /var/cache/pacman/pkg/download-peUZUV > > total 352 > > drwx------ 2 alpm alpm 4096 Jan 1 03:42 . > > drwxr-xr-x 4 root root 352256 Jan 8 21:56 .. > > > > I went ahead and just removed both directories. If there are any logs > > you are interested in, let me know, but I know the commit that led to > > this has already been identified. I'm just not sure of the fix. > > > > > > -- > > David C. Rankin, J.D.,P.E. > > > >
