Bug#580984: dpkg: --root value not removed from filename inside chroot

2010-05-10 Thread Philipp Kern
Package: dpkg Version: 1.15.7.1 Hi, 1.15.7.1 seems to have a regression with relation to the handling of `--root'. It chroot()s into that directory nowadays and then fails to call the right maintainer script due to the root value still being prepended to the filename. This causes the following

Bug#580984: dpkg: --root value not removed from filename inside chroot

2010-05-10 Thread Raphael Hertzog
Hi, On Mon, 10 May 2010, Philipp Kern wrote: 1.15.7.1 seems to have a regression with relation to the handling of `--root'. It chroot()s into that directory nowadays and then fails to call the right maintainer script due to the root value still being prepended to the filename. This causes

Bug#580984: dpkg: --root value not removed from filename inside chroot

2010-05-10 Thread Guillem Jover
Hi! On Mon, 2010-05-10 at 14:26:02 +0200, Raphael Hertzog wrote: On Mon, 10 May 2010, Philipp Kern wrote: 1.15.7.1 seems to have a regression with relation to the handling of `--root'. It chroot()s into that directory nowadays and then fails to call the right maintainer script due to the

Bug#580984: dpkg: --root value not removed from filename inside chroot

2010-05-10 Thread Raphael Hertzog
On Mon, 10 May 2010, Guillem Jover wrote: This regression was introduced with 5050748f1a6bb0c0728f8c07f9058d545c80d7e0, it's missing assigning the path returned by preexecscript to cmd-filename. I'm testing it right now, just to make sure. We could prepare an upload with this and the other