[Bug 567011] Re: Give a better error message if trying to pbuilder a .changes file

[Maarten Bezemer]

Version 0.206 gives this error:
  E: Command line parameter [<whatever>.changes] is does not exist

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644507

So upgrading to 0.206 gives an even better error message

** Bug watch added: Debian Bug tracker #644507
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644507

** Also affects: pbuilder via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644507
   Importance: Unknown
       Status: Unknown

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

Title:
  Give a better error message if trying to pbuilder a .changes file

Status in Debian Package Builder:
  Unknown
Status in “pbuilder” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pbuilder

  A common mistake I make when running pbuilder is to specify the
  .changes file instead of the .dsc.  Probably because my fingers are
  trained that the .changes is the "important" file (since it's what
  I'll be uploading).

  Unfortunately, pbuilder generates a very confusing and unfriendly set
  of error messages when you give it a .changes file instead of a .dsc
  file, and it's not at all clear that the problem is that you gave it
  the wrong kind of file.

  I'd like to see pbuilder be given a clearer error message when this
  happens.  Maybe something like,

      Error:  <whatever>.changes is not in the right format (did you
  mean to build <whatever>.dsc?)

  What would be even more slick would be if pbuilder could DoWhatIMean,
  and figure out the .dsc from the .changes filename, and pbuilder it.
  But at least giving a sane error message would be a step in the right
  direction.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pbuilder/+bug/567011/+subscriptions