bzr push bzr+ssh:// does not include working files and .bzr/checkout directory

Bug #903070 reported by Nobuto Murata
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bzr (Ubuntu)
New
Undecided
Unassigned

Bug Description

The result of bzr push with bzr+ssh:// lacks working files and .bzr/checkout directory.

How to reproduce:
 1. mkdir test1 && cd test1
 2. bzr init
 3. echo 'Hello world!' > test.txt
 4. bzr add .
 5. bzr commit -m 'Initial commit'
 6. bzr push bzr+ssh://SERVER_NAME/~user/bzr/test-remote

Expected to happen:
 `ls . .bzr` on remote server outputs:
==========
$ ls . .bzr
.:
test.txt

.bzr:
README branch branch-format branch-lock checkout repository
==========

What happened instead:
==========
$ ls . .bzr
.:

.bzr:
README branch branch-format branch-lock repository
==========
(no test.txt and no checkout directory)

NOTE:
`bzr push ../test-local` works fine as expected.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: bzr 2.4.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Dec 12 15:25:10 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111005)
PackageArchitecture: all
SourcePackage: bzr
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Nobuto Murata (nobuto) wrote :
Revision history for this message
Martin Packman (gz) wrote :

Not adding a working tree is the expected, but somewhat surprising, behaviour. See bug 44663 about making it clearer a branch does exist in this case, and bug 606249 about internal work needed before creating a remote tree could be supported.

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.