Hi, At Tue, 24 Mar 2009 15:26:46 +0100, Andreas Beckmann wrote: > > Hi, > > Junichi Uekawa wrote: > > pbuilder --execute [options] -- script [script options] > > > > pbuilder execute takes a script, /bin/echo isn't a script. > > > > .... hmmm, it might be that documentation is wrong. > > The manpage is quite clear in the > local-script-is-copied-into-the-builder respect, but I looked at > pbuilder --help instead: > > pbuilder --login > pbuilder --execute -- [command] [command-options] > Logs in to the build environment and execute command. > > And, well, a command is something residing in the builder (imho). > > > Could you try without the '--'? > > > > sudo pbuilder execute --basetgz /tmp/base-sid-i386.tgz \ > > /bin/echo hello world > > > > (and something other than /bin/echo) > > Actually using a "script" or a 32bit binary works fine, -- does not > matter, the problem is that the i386-builder can't execute a 64bit > program (because libraries are missing), but the error message is more > than unclear. E.g. this does work: > sudo pbuilder execute --basetgz /tmp/base-sid-i386.tgz -- \ > /chroot/sid-i386/bin/echo hello world > something I would have (until yesterday) expected to fail because that > path does not exist in the pbuilder.
Ah, so, binary sometimes works (if the required shared libs exist). I think it's unreliable to send random binary file to inside chroot and hope that it can work. What can be improved? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org