[Bug 708584] Re: debuild returns 0 on SIGINT

Maarten Bezemer maarten.bezemer at gmail.com
Mon Apr 16 09:41:04 UTC 2012


Such a question should be asked at the developers of the devscript package/debuild application.
I would assume they have a reason for it, but maybe it is 'legacy' code and it should be cleaned...?

See https://wiki.ubuntu.com/Debian/Bugs for more information on
contacting the Debian package developers. (Although I am not 100%
certain that this is the preferred way of contacting them...)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to devscripts in Ubuntu.
https://bugs.launchpad.net/bugs/708584

Title:
  debuild returns 0 on SIGINT

Status in “devscripts” package in Ubuntu:
  New

Bug description:
  Binary package hint: devscripts

  I call debuild inside another shell script. Most of the time in the
  whole script is spent in dpkg-buildpackage, called by debuild. Now if
  I hit ctrl+c to SIGINT the build, it stops. However, debuild happens
  to ignore the return value of dpkg-buildpackage in case it was
  terminated by a signal. The following function is responsible (around
  line 1337 in /usr/bin/debuild):

  sub system_withecho(@) {
      print STDERR " ", join(" ", @_), "\n";
      system(@_);
      if ($?>>8) {
  	fatal "@_ failed";
      }
  }

  Why is the condition for terminating bitshifted, and not just != 0?

  I'm using devscripts 2.10.61ubuntu5 on lucid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/708584/+subscriptions




More information about the foundations-bugs mailing list