Bug#852814: Fails at 'policy-rc.d already exists'

[Guido Günther]

control: retitle -1 Poor error reporting on update

On Fri, Jan 27, 2017 at 04:40:13PM +0000, Thorsten Glaser wrote:
> Guido Günther dixit:
> 
> ># echo $?
> >139
> 
> That is signal 11, i.e. segfault; is your RAM good?

It sure is. But…

with 0.228.3:

  Jan 27 15:52:23 bogon kernel: dpkg-architectu[13253] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffc46aa0158 ax:ffffffffff600400 si:0 di:1f38590
  Jan 27 15:52:47 bogon kernel: dpkg-architectu[13345] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffeae684aa8 ax:ffffffffff600400 si:0 di:dfe590

and with 0.227

   Jan 27 15:55:31 bogon kernel: http[14645] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7fff7e826e28 ax:ffffffffff600400 si:0 di:1719968
   Jan 27 15:55:31 bogon kernel: http[14644] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffebd3197d8 ax:ffffffffff600400 si:0 di:122d968

This was reported properly as http download error (since apt noticed
that it's helper died) in 0.227. But 0.228.3 simply dies without any
hint what the error could be and where it happened to the user. It would
be great if pbuilder would at least print the command that failed.

(the vsyscall issue leading to process termination via SIGSEGV is fixed in newer sid kernels).

Thanks for the hint!
 -- Guido


> I can upgrade my chroots (pbuilder 0.228.3, cowbuilder 0.83).