ubuntu-packaging-guide-team team mailing list archive

[Thiago Masato Costa Sueto <1536578@xxxxxxxxxxxxxxxxxx>]

Hello.
Doan Manh, that seems to be correct, this likely occurred because although the command does initially create a hello folder, if it's the first time one runs bzr, they'll be requested to run "bzr whoami" for setting the username and email for bzr and the command does not properly finish.
So after setting username and email, the next time the user tries to run "bzr dh-make hello 2.10 hello-2.10.tar.gz" the folder has already been made and the error message appears.
I think a section telling the user to run "bzr whoami" immediately before trying to use bzr would be ideal.

-- 
You received this bug notification because you are a member of Ubuntu
Packaging Guide Team, which is subscribed to Ubuntu Packaging Guide.
https://bugs.launchpad.net/bugs/1536578

Title:
  Session 6.2. Starting a Package shows wrong command line

Status in Ubuntu Packaging Guide:
  New

Bug description:
  When following the steps on creating a package for Ubuntu, under
  session 6.2 Starting a Package (and using the hello-2.7.tar.gz project
  example), this line on the first box returned me an error:

  $ bzr dh-make hello 2.7 hello-2.7.tar.gz
  bzr: ERROR: Either run the command from an existing branch of upstream, or move hello aside and a new branch will be created there.

  Tweaking a little bit around with the commands and searching online, I
  found out the proper command should be:

  dh_make

  ..instead, so we'd get:

  $ bzr dh_make hello 2.7 hello-2.7.tar.gz
  Fetching tarball                                                                                                                                                                                 
  Looking for a way to retrieve the upstream tarball
  Upstream tarball already exists in build directory, using that
                                                                                                                                                                                                   
  Type of package: single binary, indep binary, multiple binary, library, kernel module, kernel patch?
   [s/i/m/l/k/n]

  Thanks,
  Daniel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-packaging-guide/+bug/1536578/+subscriptions