#678407 pbuilder: pdebuild --use-pdebuild-internal gets it's knickers into a twist when in symplinked dir

#678407#5
Date:
2012-06-21 14:18:56 UTC
From:
To:
Dear Maintainer,

I am symlinking various directories under my home to a different,
faster and not backup-ed, filesystem. when running pdebuild
--use-pdebuild-internal from one of these, funny things happen. assume
/home/test is a symlink to /store/test:

cd /home/test/wM7cwjmM0I/gzip-1.4/
pdebuild --use-pdebuild-internal
...
I: Mounting /store/test/wM7cwjmM0I
...
/runscript: line 38: cd: /home/test/wM7cwjmM0I/gzip-1.4: No such file or directory

so it seems to mount the /store/ part ( i assume it mounts it to the
same location within the cchroot), but then tries to mount the /home/
version

this can of course be worked around by starting pdebuild from
/store/test/wM7cwjmM0I/gzip-1.4.

regards  robert

#678407#10
Date:
2012-11-19 22:07:16 UTC
From:
To:
I believe you can work around by sending extra directories to
--bindmounts option.

Currently for convenience the default is:
        --bindmounts $(readlink -f ..) \

I assume that .. is symlinked to somewhere else and that breaks some
assumption here.

Not sure what the generic solution will be.

Would doing 'cd $(readlink -f .)' inside pdebuild help ?


At Thu, 21 Jun 2012 15:18:56 +0100,
Robert Lemmen wrote: