Fails to indicate required debuild dependency

Bug #428722 reported by Steven Sheehy on 2009-09-13
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

Running bzr dailydeb without debuild installed displays this useless error:

Building the source package
bzr: ERROR: [Errno 2] No such file or directory

The script should either check for debuild being installed before running or at the very least throw a useful error message to indicate to the user that they need to install debuild. I had to look into bzr-builder source to find out why it was failing.

Changed in bzr-builder:
status: New → Confirmed
James Westby (james-w) wrote :

Catching and wrapping this error would be good, and making the packaging depend on
devscripts if it doesn't already.



Changed in bzr-builder:
status: Confirmed → Triaged
importance: Undecided → High
tags: added: easy
James Westby (james-w) wrote :

Oh, catching and wrapping would be something like

except OSError, e:
   if e.errno != 2:
   raise MissingDependency("debuild...

defining MissingDependency near the top of the file if bzr doesn't provide something
we can re-use.



errors.DependencyNotPresent is probably what you want.

BTW, better to use errno.ENOENT rather than '2' - more portable.


James Westby (james-w) on 2010-04-08
Changed in bzr-builder:
status: Triaged → Fix Committed
James Westby (james-w) on 2010-07-23
Changed in bzr-builder:
milestone: none → 0.3
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers