How to Sync Albums Across Machines?

[Mick Sulley]

Hi,

When I sync my album between laptop and desktop I get a message when I
open it on the destination machine saying that the collection is
available but the identifier has changed.

I have looked in the database on each machine and it seems that the
problem is that the AlbumRoots table is slightly different, the
identifier field is different -
desktop = "volumeid:?uuid=bf835257-ad63-4580-9692-9d2600740cd1"
laptop = "volumeid:?uuid=2a6a238c-c404-46b6-886f-873683917b9c"

It does seem to be OK if I just accept the message and continue, but is
there any way to stop it happening?  Is it likely to cause any problems?

Thanks
Mick
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Jean-François Rabasse]

On Wed, 20 Feb 2013, Mick Sulley wrote:

> Hi,
>
> When I sync my album between laptop and desktop I get a message when I open
> it on the destination machine saying that the collection is available but the
> identifier has changed.
>
> I have looked in the database on each machine and it seems that the problem
> is that the AlbumRoots table is slightly different, the identifier field is
> different -
> desktop = "volumeid:?uuid=bf835257-ad63-4580-9692-9d2600740cd1"
> laptop = "volumeid:?uuid=2a6a238c-c404-46b6-886f-873683917b9c"
>
> It does seem to be OK if I just accept the message and continue, but is there
> any way to stop it happening?  Is it likely to cause any problems?

Hi Mick,

Well, this is an old issue, often discussed on this list.
Identifying disk devices by UUID, instead of mount pathname as it should
be - at least on Unix platforms - makes the database hardware dependant.

Same problem occurs if you manage your collections on USB drives, even on
the same machine. Changing a drive by a backup drive, or replacing an old
drive by a new one with a mirror copy of collections will also change the
physical device UUID.

The (dirty) fix to work around sync problems is to use small scripts to
make the transfert, e.g. using rsync, then update the database from
SQL command line tool and issue things like that :
UPDATE albumroots SET identifier = 'volumeid:?uuid= new UUID'
  WHERE identifier = 'volumeid:?uuid = old UUID';

Jean-François
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Sjoerd]

On 21-02-2013 08:33, Jean-François Rabasse wrote:
> The (dirty) fix to work around sync problems is to use small scripts
> to
> make the transfert, e.g. using rsync, then update the database from
> SQL command line tool and issue things like that :
> UPDATE albumroots SET identifier = 'volumeid:?uuid= new UUID'
>  WHERE identifier = 'volumeid:?uuid = old UUID';
>

Isn't it more easy just to accept the new roots when digikam mentions
the change of uuids after syncing?
So far it didn't gave me problems


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Jean-François Rabasse]

On Thu, 21 Feb 2013, Sjoerd wrote:

> On 21-02-2013 08:33, Jean-François Rabasse wrote:
>> The (dirty) fix to work around sync problems is to use small scripts to
>> make the transfert, e.g. using rsync, then update the database from
>> SQL command line tool and issue things like that :
>> UPDATE albumroots SET identifier = 'volumeid:?uuid= new UUID'
>>  WHERE identifier = 'volumeid:?uuid = old UUID';
>>
>
> Isn't it more easy just to accept the new roots when digikam mentions the
> change of uuids after syncing?
> So far it didn't gave me problems

Of course it is more easy, if it works well.
Perhaps it depends on software versions, I don't known, but I had problems
with that, so...
(Anyway, I still have problems with USB drives. I have about 15% of my
images on local hard drive, and 85% on USB drives, not always the same
ones. So, I still do a bit of setup before starting DK, checking which
drives are plugged and setting the proper UUIDs.)

But you're right Sjoerd, if accepting works (no rescan of collections,
etc.) it's the right way.

Jean-François
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users