conflict in file that isn't changed locally

Bug #645335 reported by John Lenton
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu One Client
Status tracked in Trunk
Stable-1-4
Fix Released
Critical
Lucio Torre
Trunk
Fix Released
Critical
Lucio Torre
ubuntuone-client (Ubuntu)
Fix Released
Medium
Ubuntu One Foundations+ team

Bug Description

This might be the same as bug #508778, but I have logs :)
In a share I got .u1conflict files despite not changing those files. Nothing in the logs, so I removed the .u1conflicts, but then it happened again, so now I have logs :)
Attached.

Steps to reproduce:
Two clients, Client A & B running Maverick
1. Disconnect client B
2. On client A: $ > foo.txt
3. Sync client B (connect and disconnect)
4. On client A (while connected): $ echo hola > bar.txt ; mv bar.txt foo.txt
5. Connect client B

Related branches

Revision history for this message
John Lenton (chipaca) wrote :
Revision history for this message
Lucio Torre (lucio.torre) wrote :

aq_HANDLE_DELTA_OK leaves deletes for last, so a move over a file remotely creates a conflict.

Changed in ubuntuone-client:
importance: Undecided → Critical
status: New → Triaged
Revision history for this message
Lucio Torre (lucio.torre) wrote :

Instructions to reproduce:
 1- disconnect client B
 2- on client A: $ > foo.txt
 3- sync client B (connect and disconnect)
 4- on client A (while connected): $ echo hola > bar.txt ; mv bar.txt foo.txt
 5- connect client B

Changed in ubuntuone-client:
status: Triaged → In Progress
assignee: nobody → Lucio Torre (lucio.torre)
description: updated
Changed in ubuntuone-client (Ubuntu):
status: New → In Progress
milestone: none → ubuntu-10.10
assignee: nobody → Ubuntu One Foundations+ team (ubuntuone-foundations+)
importance: Undecided → Medium
tags: added: chicharra chicharra-maverick desktop+ foundations+ u1-maverick
Changed in ubuntuone-client (Ubuntu):
milestone: ubuntu-10.10 → maverick-updates
dobey (dobey)
Changed in ubuntuone-client (Ubuntu):
status: In Progress → Fix Released
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.