Wrong branch format shown on web page after remote upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
While trying to exercise bug 60695, I created a new branch in pack-0.92 format, let it get scanned, remotely upgraded it (to 2a), and only its repository format was updated on the web page. The branch format was listed as "Branch format 6", but "bzr info -v nosmart+..." correctly listed the branch format as "Branch format 7".
Steps to reproduce:
$ bzr init lp:~abentley/+junk/old-format --pack-0.92
Created a standalone branch (format: unnamed)
$ bzr checkout lp:~abentley/+junk/old-format
$ cd old-format/
$ bzr commit -m "test" --unchanged
Committing to: bzr+ssh:
You need a passphrase to unlock the secret key for
user: "Aaron Bentley <email address hidden>"
1024-bit DSA key, ID 5616A88D, created 2004-12-08
Committed revision 1.
$ bzr upgrade lp:~abentley/+junk/old-format
starting upgrade of bzr+ssh:
making backup of bzr+ssh:
to bzr+ssh:
starting repository conversion
repository converted
finished
abentley@
Standalone branch (format: 2a)
Location:
branch root: nosmart+
Format:
control: Meta directory format 1
branch: Branch format 7
repository: Repository format 2a - rich roots, group compression and chk inventories
Branch history:
1 revision
0 days old
first revision: Thu 2010-10-14 14:02:15 -0400
latest revision: Thu 2010-10-14 14:02:15 -0400
Repository:
1 revision
abentley@
Changed in launchpad-code: | |
status: | New → Triaged |
importance: | Undecided → Low |
summary: |
- Wronng branch format shown on we page after remote upgrade + Wronng branch format shown on web page after remote upgrade |
tags: | added: branch-scanner |
summary: |
- Wronng branch format shown on web page after remote upgrade + Wrong branch format shown on web page after remote upgrade |
tags: | added: branches upgrade |