create.py crashed with E.g. bzr whoami "Your Name <email address hidden>" in username()

Bug #648496 reported by Victor Vargas
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Quickly
Fix Released
Undecided
Unassigned
quickly (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: quickly

This is first attemp after install quickly I ran in the terminal "quickly create ubuntu-application foo1" and then crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: quickly-ubuntu-template 0.6-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Sun Sep 26 22:12:40 2010
ExecutablePath: /usr/share/quickly/templates/ubuntu-application/create.py
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/quickly/templates/ubuntu-application/create.py ejemplo1
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_CL.UTF-8
PythonArgs: ['/usr/share/quickly/templates/ubuntu-application/create.py', 'ejemplo1']
QuicklyDataPath: /usr/share/quickly
QuicklyTemplates:
 /usr/share/quickly/templates/ubuntu-cli
 /usr/share/quickly/templates/ubuntu-pygame
 /usr/share/quickly/templates/ubuntu-application
QuicklyTemplatesDirectories: /usr/share/quickly/templates/
SourcePackage: quickly
Title: create.py crashed with E.g. bzr whoami "Your Name <email address hidden>" in username()
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare video

Related branches

Revision history for this message
Victor Vargas (kamus) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Michael Terry (mterry) wrote :

This is easily reproducable:
1) Make sure you don't have whoami info (bzr whoami "")
2) Try to run quickly create ubuntu-application test

It seems that nowadays bzr won't let you commit without whoami info. I don't recall that was always the case. One solution would be to grab the user's information from launchpad and fill it out during the create step. That would be ideal because then the information would match what they will eventually push to LP. It might feel a little odd though, to be hitting LP just to create a local project...

visibility: private → public
Changed in quickly (Ubuntu):
status: New → Confirmed
Revision history for this message
Michael Terry (mterry) wrote :

(another solution would be to just clean up the message to not look like a drastic crash, and just to ask the user to use bzr whoami)

Revision history for this message
Victor Vargas (kamus) wrote :

Right, after set bzr profile (whoami) all works fine. Thanks for the efforts

Revision history for this message
Michael Terry (mterry) wrote :

Fixed by reverting the big bzr rewrite a while back.

Changed in quickly:
status: New → Fix Committed
Changed in quickly:
status: Fix Committed → Fix Released
Changed in quickly (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package quickly - 0.6.1-0ubuntu1

---------------
quickly (0.6.1-0ubuntu1) maverick; urgency=low

  * New bugfix release:
   + ubuntu-application-template and derivatives:
    - don't overwrite files in add command if already exists (Tony Byrne)
      (LP: #645490)
    - fix crash in in help() (Michael Terry) (LP: #649881)
    - force utf8 when creating a gpg key (LP: #640689)
   + common:
    - revert internal bzr calls to use subprocess calls again
      (LP: #648496, #642455)
    - translations update (en_GB, es, fr, uk)
    - urkkk, just saw that the tutorial contains the name and revision number.
      Update that as a workaround. Should be removed for next release.
 -- Didier Roche <email address hidden> Wed, 06 Oct 2010 12:18:39 +0200

Changed in quickly (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

I hadn't seen this bug report earlier. FWIW the related regression in Bazaar is bug #616878, introduced in Bazaar 2.2.

The easiest way to work around it while using the Bazaar API directly would probably be to explicitly specify a committer when doing a commit. This way the configuration doesn't have to be changed and the behaviour would be the same as before 2.2.

As Michael mentions, it'd be nicer to ask the user for credentials or retrieve them from the Launchpad account though.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.