UnboundLocalError after naive log command
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/
> cd F:\My Documents\Visual Studio 2005\Projects VB\SysBak DEVELOPMENT\SysBak ORIGINAL\
> bzr checkout "file:///X:/Derek's Temp Backups/SysBak REPOSITORY/
> 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\
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
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_
File "bzrlib\log.pyo", line 972, in _filter_
UnboundLocalError: local variable 'next_keys' referenced before assignment
bzr 1.13 on python 2.5.2 (win32)
arguments: ['bzr', 'log', 'SysBak\
encoding: 'cp1252', fsenc: 'mbcs', lang: None
plugins:
bzrtools L:\Bazaar\
gtk C:\Documents and Settings\
.0.final.1]
launchpad L:\Bazaar\
netrc_
qbzr L:\Bazaar\
svn L:\Bazaar\
*** Bazaar has encountered an internal error.
Please report a bug at https:/
including this traceback, and a description of what you
were doing when the error occurred.
Related branches
Changed in bzr: | |
assignee: | nobody → vila |
importance: | Undecided → Low |
milestone: | none → 1.14rc1 |
status: | New → Fix Committed |
Changed in bzr: | |
status: | Fix Committed → Fix Released |
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...