Remote upgrade not triggering rescans
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
I ran "bzr upgrade --default lp:configglue" on Sept 23, and having no new revisions at this time, has still not rescanned. Thus, it shows "Bazaar RepositoryForma
https:/
Thu 2010-09-23 11:09:34 -0400
0.025 bazaar version: 2.2.0
0.025 bzr arguments: [u'upgrade', u'--default', u'lp:configglue']
0.034 looking for plugins in /usr/lib/
0.100 encoding stdout as sys.stdout encoding 'UTF-8'
1.058 ssh implementation is OpenSSH
34.674 creating repository in bzr+ssh:
37.594 Using fetch logic to copy between KnitPackReposit
37.594 fetch up to rev {None}
67.750 Packing repository GCRepositoryPac
67.941 repacking 43 revisions
68.157 repacking 43 inventories
68.795 repacking chk: 43 id_to_entry roots, 9 p_id_map roots, 52 total keys
69.802 repacking 178 texts
70.224 repacking 31 signatures
90.112 Transferred: 1235kB (13.9kB/s r:716kB w:520kB)
90.113 return code 0
tags: | added: branch-scanner |
Changed in launchpad: | |
importance: | Medium → High |
tags: | added: branches upgrade |
I can't reproduce this. I created a branch in pack-0.92, let it get scanned, upgraded it, and it showed the correct repository format.