[digiKam-users] I think I have found the synchronization bug/problem

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[digiKam-users] I think I have found the synchronization bug/problem

Chris Green
After much going back and forth between my two systems running Digikam
6.0 beta1 I *think* I have found the problem with failing to
synchronize tags.

In Settings->Metadata I have the "Update file timestamp when files are
modified" box ticked.  I rely on this as I use the "--update" option
in rsync when copying files from one system to the other.  Only files
whose timestamp has been updated will get copied across to the other
system.

If I delete a tag that's at the 'bottom' of the hierarchy (i.e. a tag
which has no sub-tags) then the timestamp *is* updated and everything
works as it should.  

However if I delete a tag which has sub-tags then the image files
*don't* get their timestamp updated and thus my rsync doesn't copy
them across to the other system as required.

Where/how do I report this as a bug in 6.0beta1 ?

--
Chris Green
·

Reply | Threaded
Open this post in threaded view
|

Re: I think I have found the synchronization bug/problem

Maik Qualmann
I think it is not a bug. You will have a few images where the tag is only in the database. If you now delete the tag, there is no change to the file and date.

Maik

Chris Green <[hidden email]> schrieb am Di., 2. Okt. 2018 17:03:
After much going back and forth between my two systems running Digikam
6.0 beta1 I *think* I have found the problem with failing to
synchronize tags.

In Settings->Metadata I have the "Update file timestamp when files are
modified" box ticked.  I rely on this as I use the "--update" option
in rsync when copying files from one system to the other.  Only files
whose timestamp has been updated will get copied across to the other
system.

If I delete a tag that's at the 'bottom' of the hierarchy (i.e. a tag
which has no sub-tags) then the timestamp *is* updated and everything
works as it should. 

However if I delete a tag which has sub-tags then the image files
*don't* get their timestamp updated and thus my rsync doesn't copy
them across to the other system as required.

Where/how do I report this as a bug in 6.0beta1 ?

--
Chris Green
·

Reply | Threaded
Open this post in threaded view
|

Re: I think I have found the synchronization bug/problem

Chris Green
Maik Qualmann <[hidden email]> wrote:

> Chris Green <[hidden email]> schrieb am Di., 2. Okt. 2018 17:03:
>
> > After much going back and forth between my two systems running Digikam
> > 6.0 beta1 I *think* I have found the problem with failing to
> > synchronize tags.
> >
> > In Settings->Metadata I have the "Update file timestamp when files are
> > modified" box ticked.  I rely on this as I use the "--update" option
> > in rsync when copying files from one system to the other.  Only files
> > whose timestamp has been updated will get copied across to the other
> > system.
> >
> > If I delete a tag that's at the 'bottom' of the hierarchy (i.e. a tag
> > which has no sub-tags) then the timestamp *is* updated and everything
> > works as it should.
> >
> > However if I delete a tag which has sub-tags then the image files
> > *don't* get their timestamp updated and thus my rsync doesn't copy
> > them across to the other system as required.
> >
> > Where/how do I report this as a bug in 6.0beta1 ?
> >
>
> I think it is not a bug. You will have a few images where the tag is only
> in the database. If you now delete the tag, there is no change to the file
> and date.
>
I guess that *might* be the problem.  It all hangs on the difficulty
of keeping files and database metadata in sync.

I'll keep looking.

--
Chris Green
·