Package: stow
Version: 1.3.3-2

I have a chroot mounted in /usr/local/chroot that I use for the
sbuild package.  It appears that since proc is mounted inside
the chroot, when unstowing a package, stow gets confused and
goes after symlinks that are not there:

$ sudo stow -D findbugs-0.8.6/
stow: Cannot read link /usr/local/chroot/woody/proc/2/task/2/exe (No
such file or directory)

It unstows properly, but maxes CPU for a few seconds and then spews
the above error.  Also, this causes a failure when restowing (with the
-R option) a package, as the unstow operation errors out and it never
gets back around to stowing again.

Recommend modyifing stow to not traverse (either on a stow or an
unstow operation) into any pseudo filesystem (proc, dev, and so on).

Regards,

-Roberto Sanchez

--
Roberto C. Sanchez
http://familiasanchez.net/~sanchezr

Attachment: signature.asc
Description: OpenPGP digital signature



Reply via email to