A published file in not accessible anymore when updated

Bug #652019 reported by Mahendra Tallur on 2010-09-30
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
Wishlist
Ubuntu One Foundations+ team

Bug Description

Binary package hint: ubuntuone-client

Hi !

Here's an issue that occurs with the current Maverick RC.

Short form : "A published file in not accessible anymore when updated"

How to reproduce :

1) synchronize any drawer
2) inside this drawer, publish a file
3) open the URL into a browser in order to check it's been published properly (should be OK)
4) modify the file (example : add a line to the text file)
5) try to open the URL again : it's not available anymore

I wonder whether this behaviour is a bug or on purpose ? This is annoying, because sometimes, for instance, you may want to publish a listing, or a work-in-progress with people.

Cheers !

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubuntuone-client 1.4.3-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Sep 30 14:44:36 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100923)
PackageArchitecture: all
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SourcePackage: ubuntuone-client
UbuntuOneSyncdaemonExceptionsLog:
 2010-09-30 13:39:53,354 - ubuntuone.SyncDaemon.EQ - ERROR - Error encountered while handling: AQ_MOVE_ERROR in <ubuntuone.syncdaemon.sync.Sync object at 0x2789ad0>
 Traceback (most recent call last):
   File "/usr/lib/pymodules/python2.6/ubuntuone/syncdaemon/event_queue.py", line 825, in _dispatch
     method(*args, **kwargs)
 TypeError: handle_AQ_MOVE_ERROR() got an unexpected keyword argument 'new_name'
UbuntuOneUserSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 51200
 on = True

Mahendra Tallur (mahen) wrote :
Roman Yepishev (rye) on 2011-02-15
Changed in ubuntuone-client (Ubuntu):
assignee: nobody → Roman Yepishev (rye)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntuone-client (Ubuntu):
status: New → Confirmed

Hello,
I am affected with the same bug, this is a real issue and I consider this as a real issue with the product.
After saving an update of a published file on my desktop, it will automatically "synchronise" with the corresponding files at UbuntuOne (and it does). Problem is that the "new file", actually the updated file with the same name, is no longer published. Pressing the publish button results is a new URL. The old file is still publish but url is no longer valid!
Please do something!

On Wed, Feb 15, 2012 at 4:27 PM, Stephane Trillat
<email address hidden> wrote:
> Hello,
> I am affected with the same bug, this is a real issue and I consider this as a real issue with the product.
> After saving an update of a published file on my desktop, it will automatically "synchronise" with the corresponding files at UbuntuOne (and it does). Problem is that the "new file", actually the updated file with the same name, is no longer published. Pressing the publish button results is a new URL. The old file is still publish but url is no longer valid!
> Please do something!
>
> --
> You received this bug notification because you are a member of Ubuntu
> One hackers, which is subscribed to ubuntuone-client in Ubuntu.
> https://bugs.launchpad.net/bugs/652019
>
> Title:
>  A published file in not accessible anymore when updated

This is not a bug, it is by design.

John O'Brien (jdobrien) wrote :

This is not a bug, this is by design. If you make it public again, it will have the same URL.

Changed in ubuntuone-client (Ubuntu):
importance: Undecided → Wishlist
status: Confirmed → Triaged

Thanks for your answer,
I still believe that this should be changed. If we have to manually republish all files that are updated, this is a nightmare!
Maybe we could choose what to do (option)?
What could we do to ask for this change ?
Thanks much.

John O'Brien (jdobrien) wrote :

On Thu, Feb 16, 2012 at 11:35 AM, Stephane Trillat
<email address hidden> wrote:
> Thanks for your answer,
> I still believe that this should be changed. If we have to manually republish all files that are updated, this is a nightmare!
> Maybe we could choose what to do (option)?
> What could we do to ask for this change ?
> Thanks much.
>

Yes, I agree, which is why i set this to wishlist. I do not know the
underlying reasons why we were asked to make it like this.

Leo Arias (elopio) on 2012-02-16
Changed in ubuntuone-client (Ubuntu):
assignee: Roman Yepishev (rye) → Ubuntu One Foundations+ team (ubuntuone-foundations+)

Hello all,
please note that the possibility to publish any file or folder, independently from its path is also available on Dropbox.
(see http://www.dropbox.com/help/167)
I have done some tests of publishing and updating files using Dropbox, everything is fine with them. Any updated file keeps the same url and is published.
This confirms to me even more that we have now a competitive problem with UbuntuOne...
I am very sad to see that this discussion is opened since 1,5 years
Hope things change very very soon. Please could you all click the link "this affects me" such that we have more weight ?
Cheers, Stephane.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers