QBzr

qpush: Add ui for --no-strict

Bug #402211 reported by Alexander Belchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QBzr
Fix Released
High
Alexander Belchenko
QBzr 0.13

Bug Description

Thanks to recent changes in bzr push we now have problem with qpush:

when user working in lightweight checkout of branch with the tree then often master branch tree will be out of date because all work done in checkout. And because qpush using branch root to run `push -d branch_root` then builtin push starts to complain about wt out-of-date, although in checkout the tree is clean.

We have to change value of -d option for push.

Tags: qpush
Alexander Belchenko (bialix)
Changed in qbzr:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Gary van der Merwe (garyvdm) wrote :

I don't think that this is a bug with qpush, because qpush behaves the same as the command line.

I do think we need to add the --no-strict option to the ui. So I'm going to change this bug to that.

summary: - qpush + bzr 1.17 problems
+ qpush: Add ui for --no-strict
Revision history for this message
Gary van der Merwe (garyvdm) wrote :

Rather than just adding a checkbox to the ui, I think we should check if push is going to stop, and if so, popup a msg box that says:

bzr: ERROR: Working tree is out of date, please run 'bzr update'.
Do you wish to continue anyway?
[yes] [no]

And if they click yes, then we pass --no-strict.

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 402211] Re: qpush + bzr 1.17 problems

Gary van der Merwe пишет:
> Rather than just adding a checkbox to the ui, I think we should check if
> push is going to stop, and if so, popup a msg box that says:
>
> bzr: ERROR: Working tree is out of date, please run 'bzr update'.
> Do you wish to continue anyway?
> [yes] [no]
>
> And if they click yes, then we pass --no-strict.

I like this.

Alexander Belchenko (bialix)
Changed in qbzr:
assignee: nobody → Alexander Belchenko (bialix)
status: Confirmed → In Progress
status: In Progress → Fix Released
milestone: none → 0.13
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.