Bug#542915: pbuilder: removes data from bind-mounted directories

[Jakub Wilk]

submitter 542915 !
thanks

* Matthew Palmer <mpalmer at debian.org>, 2010-12-12, 14:07:
>I'm trying to reproduce this bug, but I can't manage to get pbuilder to
>behave in the manner you describe -- but I can't find any changes to
>pbuilder in the meantime that would explain a change in behaviour.

Thanks for taking care of this bug.

>Here is what I did, using pbuilder 0.199:
>
>1) Created a minimal package that failed to build
>
>2) mkdir /tmp/hooks
>
>3) cp /usr/share/pbuilder/examples/C10shell /tmp/hooks

s,pbuilder,doc/pbuilder,

>4) pbuilder --build --basetgz ~/chroots/sid.tgz --hookdir /tmp/hooks broken.dsc
>
>5) Wait for build to fail and drop into a shell; switch to another xterm
>
>6) mkdir /tmp/valuable
>
>7) touch /tmp/valuable/do-not-delete-please
>
>8) mount -o bind /tmp/valuable /var/cache/pbuilder/build/XXXXX/home
>
>9) Switch back to the pbuilder xterm; exit out of the shell
>
>Now pbuilder reports a couple of errors:
>
>rmdir: failed to remove `/var/cache/pbuilder/build//XXXXX/home': Device or resource busy
>rmdir: failed to remove `/var/cache/pbuilder/build//XXXXX': Directory not empty

Yup, this is exactly what I was doing.

>But if I ls /tmp/valuable, the file do-not-delete-please is still there.

Are /tmp/valuable and /var/cache/pbuilder/build/XXXXX/ on the same 
partition? If they are not, the bug won't trigger.

>Would you be able to tell me where my attempt at reproducing the 
>problem differs from your experience, or let me know if the bug no 
>longer appears in pbuilder 0.199?

I can reproduce this bug with pbuilder 0.199 using your procedure.

-- 
Jakub Wilk