Ubuntu One Client

Published, renamed file not followed by it's public URL in Nautilus context menu.

Bug #538792 reported by Luca Ferretti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu One Client
Confirmed
Wishlist
Ubuntu One Foundations+ team

Bug Description

Ubuntu version: lucid lynx
ubuntuone-client package version: 1.1.4-0ubuntu1

It seems that file publishing on latest UbuntuOne is based on file name, non file "ID".

# Steps to reproduce
  * create a file $HOME/Ubuntu\ One/first-file
  * publish $HOME/Ubuntu\ One/first-file
  * rename $HOME/Ubuntu\ One/first-file to $HOME/Ubuntu\ One/first_file
  * create a new $HOME/Ubuntu\ One/first-file

# Current result
  The "second" first-file is currently published, the "first" and renamed one in not published

# Expected result
  first_file should be published, first-file not... shouldn't it?

Duane Hinnen (duanedesign)
summary: - Publishing based on file name
+ file publishing based on file name, non file "ID"
Revision history for this message
Joshua Hoover (joshuahoover) wrote : Re: file publishing based on file name, non file "ID"

Hi Luca,

Thank you for taking the time to file this bug report. You are correct, the first_file should be published and we should not publish the new file named "first-file".

Thank you,

Joshua

Changed in ubuntuone-client:
status: New → Confirmed
assignee: nobody → Ubuntu One Foundations+ team (ubuntuone-foundations+)
tags: added: chicharra foundations+
tags: added: u1-maverick
Facundo Batista (facundo)
Changed in ubuntuone-client:
importance: Undecided → Wishlist
Revision history for this message
Michał Karnicki (karni) wrote :

Actually the behaviour is different. I tried to replicate the problem. I renamed the file not to use 'first' in the name, it's misleading.

# Steps to reproduce
  * create a file $HOME/Ubuntu\ One/foo-bar
  * publish $HOME/Ubuntu\ One/foo-bar
  * rename $HOME/Ubuntu\ One/foo-bar to $HOME/Ubuntu\ One/foo_bar
  * create a new $HOME/Ubuntu\ One/foo-bar

# Current result
  Nautilus thinks that the foo-bar is currently published, and the initial, renamed foo_bar is not. What really occurs is that copying a public URL from the "oh-so" published foo-bar copies a public link of foo_bar! So it looks like the problem is revealed on the Nautilus side. We never publish a file that user has not explicitly published on his own.

# Expected result
  foo_bar should be published, foo-bar not... - that's the case, but public URL of foo_bar is "attached" via context menu to the foo-bar file, and this is the bug.

summary: - file publishing based on file name, non file "ID"
+ Published, renamed file not followed by it's public URL in Nautilus
+ context menu.
Leo Arias (elopio)
tags: added: maverick
removed: u1-maverick
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.