There's definitely somethng strange going on with the bind mount, and
debootstrap also doesn't like the filesystem being mounted nodev.
Here's what I've tried:
- setting --buildplace and --aptcache to a directory under /usr/local
(which was mounted nodev): failed
- remounting /usr/local with dev, and setting --buildplace and
--aptcache: succeeded
- building under /var (with is partition mounted nodev): failed
- building under /var (remounting its partition dev): failed
- setting --buildplace and --aptcache to /pbuilder/build and
/pbuilder/aptcache, where /pbuilder is a bind mount on a partition
with no special mount flags: succeeded
So the bind mount wasn't causing any problems, but the nodev flag was.
I guess when I remounted the partition that contained /var, the bind
mount still thought it was mounted nodev.
So as far as I'm concerned, you can close this bug. My only comment
is that it may be nice to put something in the documentation about
what flags the /var partition should not be mounted as (nodev, noexec,
etc.), if it isn't there already. (That's the only reason I'm not
closing this bug myself.)
Thanks for helping debug this.
--
Hubert Chan <[EMAIL PROTECTED]> - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA
Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA
Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
