bzr shelve handles newly added and newly deleted files badly
Bug #4007 reported by
Guilherme Salgado
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
If you try to shelve changes that contain newly added files, you'll get a traceback like this:
bzr: ERROR: [Errno 2] No such file or directory: '/tmp/bzrtest/foo'
command: '/usr/bin/bzr' 'shelve'
pwd: u'/tmp/bzrtest'
error: exceptions.OSError
at /usr/lib/
see ~/.bzr.log for debug information
It's not a big deal because if you unshelve later you'll get the added file back. The only problem is that it seems to fail.
Revision history for this message
| Aaron Bentley (abentley) wrote | #1 |
| Changed in bzr: | |
| status: | New → PendingUpload |
Revision history for this message
| Robert Collins (lifeless) wrote | #2 |
| Changed in bzr: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The bug is actually in bzr diff and bzr status. I've fixed it in bzr.ab