UnboundLocalError after naive log command

Bug #346431 reported by Jem_Throgg
8
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
Low
Vincent Ladeuil

Bug Description

I am completely new to version control - and struggling. My actions might look silly, but not as silly as the ones I removed from the list below!

Here's what I did, with summarised results, including traceback:

> cd L:\Bazaar\
> L:
> bzr whoami
Derek
> cd F:\My Documents\Visual Studio 2005\Projects VB\SysBak DEVELOPMENT\
> F:
> bzr init-repo --trees .
> bzr init-repo --no-trees "file:///X:/Derek's Temp Backups/SysBak REPOSITORY/bzr"
> bzr init "file:///X:/Derek's Temp Backups/SysBak REPOSITORY/bzr/SysBak"
> cd F:\My Documents\Visual Studio 2005\Projects VB\SysBak DEVELOPMENT\SysBak ORIGINAL\
> bzr checkout "file:///X:/Derek's Temp Backups/SysBak REPOSITORY/bzr/SysBak" "SysBak ORIGINAL"
> bzr --dry-run add
> bzr ignore *.resx
> bzr ignore *.user
> bzr ignore *.vbproj
> bzr ignore *.myapp
> bzr ignore *.Designer.*
> bzr ignore AssemblyInfo.vb
> bzr ignore Settings.settings
> bzr ignore *.vbproj.*
> bzr ignore *.exe
> bzr ignore *.pdb
> bzr ignore *.xml
> bzr ignore *.resources
> bzr ignore TempPE
> bzr add --dry-run
> bzr add
> bzr status
> bzr log OverlayWindow.vb
bzr: ERROR: Path unknown at end or start of revision range: OverlayWindow.vb
> bzr log SysBak\OverlayWindow.vb
bzr: ERROR: exceptions.UnboundLocalError: local variable 'next_keys' referenced before assignment

Traceback (most recent call last):
  File "bzrlib\commands.pyo", line 716, in exception_to_return_code
  File "bzrlib\commands.pyo", line 911, in run_bzr
  File "bzrlib\commands.pyo", line 547, in run_argv_aliases
  File "bzrlib\commands.pyo", line 926, in ignore_pipe
  File "bzrlib\builtins.pyo", line 2168, in run
  File "bzrlib\log.pyo", line 182, in show_log
  File "bzrlib\log.pyo", line 227, in _show_log
  File "bzrlib\log.pyo", line 317, in _create_log_revision_iterator
  File "bzrlib\log.pyo", line 972, in _filter_revisions_touching_file_id
UnboundLocalError: local variable 'next_keys' referenced before assignment

bzr 1.13 on python 2.5.2 (win32)
arguments: ['bzr', 'log', 'SysBak\\OverlayWindow.vb']
encoding: 'cp1252', fsenc: 'mbcs', lang: None
plugins:
  bzrtools L:\Bazaar\plugins\bzrtools [1.13]
  gtk C:\Documents and Settings\Derek\Application Data\bazaar\2.0\plugins\gtk [0.95
.0.final.1]
  launchpad L:\Bazaar\plugins\launchpad [unknown]
  netrc_credential_store L:\Bazaar\plugins\netrc_credential_store [unknown]
  qbzr L:\Bazaar\plugins\qbzr [0.9.8]
  svn L:\Bazaar\plugins\svn [0.5.3]
*** Bazaar has encountered an internal error.
    Please report a bug at https://bugs.launchpad.net/bzr/+filebug
    including this traceback, and a description of what you
    were doing when the error occurred.

Revision history for this message
Vincent Ladeuil (vila) wrote :

bzr log shouldn't backtrace, so this is a genuine bug.

On the other hand, you can't log a file which has never been committed, so you want to 'bzr commit' after your 'bzr add'.

'commit' is the operation that create a revision, it's the way you tell bzr that you're happy with the state of your working tree (where you work) and want that state to become part of the history of your project.

It's a good practice to commit often.

I'm not sure you want that bug to be private, the less people can see it, the less people can fix it...

Revision history for this message
Jem_Throgg (jem-throgg) wrote :

Your comment is very helpful as I am trying to get a grasp of the Bazaar concepts. I made it private because I'm a little embarrassed by my ignorance - and because I'm concerned about computer security and personal privacy. However, if i can see how, I shall make it public.
Thanks.

Vincent Ladeuil (vila)
Changed in bzr:
assignee: nobody → vila
importance: Undecided → Low
milestone: none → 1.14rc1
status: New → Fix Committed
Vincent Ladeuil (vila)
Changed in bzr:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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