Launchpad itself

changes in hosted branch formats not propagated/noticed

Bug #368920 reported by Robert Collins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Medium
Unassigned

Bug Description

This may be false, but its worth investigating:

> Because I haven't added any new revisions, Launchpad hasn't re-mirrored
> it yet. This is a Launchpad bug. For read-only users, bzrtools looks
> like it's in the old format, but I'll commit a NEWS update so that
> Launchpad mirrors it.

Rich root conversions will be confusing enough to users without toolchain issues.

Tags: lp-code
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

I think what happens here is that the branch format is actually propagated, but that the branch page won't reflect this change until a new revision is seen.

summary: - changes in hosted branch formats not propogated/noticed
+ changes in hosted branch formats not propagated/noticed
Revision history for this message
Jonathan Lange (jml) wrote :

A fix to bug 280578 would fix this. In the meantime, we could extend the "should I scan this branch" check to also compare the database format against the Bazaar format, or we could make the branch puller set the format (thus pre-empting bug 280578 in a way).

summary: - changes in hosted branch formats not propagated/noticed
+ changes in hosted branch formats not propagated/noticed until scan
summary: - changes in hosted branch formats not propagated/noticed until scan
+ changes in hosted branch formats not propagated/noticed
Changed in launchpad-bazaar:
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.