[digikam] [Bug 372047] New: Migration fails: collection path contains %2F instead of /

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

[digikam] [Bug 372047] New: Migration fails: collection path contains %2F instead of /

bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372047

            Bug ID: 372047
           Summary: Migration fails: collection path contains %2F instead
                    of /
           Product: digikam
           Version: 5.2.0
          Platform: Gentoo Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Database-Migration
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

I’m a user of Digikam 4.14 and trying out a freshly built 5.2.0 on my Gentoo
system with Plasma 5.8.3, frameworks 5.26.0.

After going through the conversion wizard, I see the root entry of the
collection I am trying to migrate in the album tree, but after a short moment
it vanishes and I see a progress popup at 100 %.

The tag tree is still there. The timeline also shows how many images I have for
a given month. But this one is cleared once I closed and reopened Digikam.

I found out that in Digikam’s Settings→Collections I see the collection that I
tried to migrate, but its path is written as "%2Fhome%2Ffrank%2Fbilder". So I
delete that, add a new collection with the proper path, click OK and then the
collection is correctly imported. Quickly glancing over it, all tags and so on
seem to be there. After a while of processing, the timeline is also populated
again.

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 372047] Migration fails: collection path contains %2F instead of /

bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372047

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
          Component|Database-Migration          |Database-Setup

--- Comment #1 from [hidden email] ---
Must be fixed with next digiKam 5.3.0.

Please test and report with preview of 5.3.0 AppImage bundle for Linux :

https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 372047] Switch from DK4 to DK5 fails: collection path contains %2F instead of /

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372047

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Migration fails: collection |Switch from DK4 to DK5
                   |path contains %2F instead   |fails: collection path
                   |of /                        |contains %2F instead of /

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 372047] Switch from DK4 to DK5 fails: collection path contains %2F instead of /

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372047

--- Comment #2 from Frank Steinmetzger <[hidden email]> ---
5.3.0 reached my package manager, so I could easily install it. I have several
collection databases which I manage independently from one another. It appears
to me that migration is only performed on the database that was last opened in
Digikam 4, because that is what the migration wizard can find. The migration
worked successfully and I can browse my collection.

However, Any other database that is opened afterwards is not migrated and keeps
the '%2F'. I checked my digikam4.db files, and indeed the identifier column in
the AlbumRoots table of the first database was adjusted ("volumeid:?path=" now
uses / instead of %2F). But in the second database file it still said %2F.

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 372047] Switch from DK4 to DK5 fails: collection path contains %2F instead of /

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372047

Arnaud <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #3 from Arnaud <[hidden email]> ---
Hello,
is there a way to modify the path in DK 5.2.0, I get the same bug, since I
upgrade Opensuse from 42.1 to 42.2. May I delete the collection with the %2 and
add a same new one with / ?
Does the DB will recognise the new path or I will lost some tags, ...
Thank you,
Arnaud

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 372047] Switch from DK4 to DK5 fails: collection path contains %2F instead of /

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372047

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #4 from Maik Qualmann <[hidden email]> ---
*** Bug 379415 has been marked as a duplicate of this bug. ***

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 372047] Switch from DK4 to DK5 fails: collection path contains %2F instead of /

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372047

--- Comment #5 from Marty <[hidden email]> ---
Folks i hit this upgrading from from 4.14 to 5.6 (via appimage)

It complained it could not find the existing network collections, an example
was:
networkshareid:?mountpath=%2Fmnt%2Fmunich%2Fphotos

I edited the sqllite database directly replacing the ascii %2F with / and when
i restarted everything was fine again.

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 372047] Switch from DK4 to DK5 fails: collection path contains %2F instead of /

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372047

--- Comment #6 from Arnaud <[hidden email]> ---
(In reply to Marty from comment #5)
> Folks i hit this upgrading from from 4.14 to 5.6 (via appimage)
>
> It complained it could not find the existing network collections, an example
> was:
> networkshareid:?mountpath=%2Fmnt%2Fmunich%2Fphotos
>
> I edited the sqllite database directly replacing the ascii %2F with / and
> when i restarted everything was fine again.

Just did it, works like a charm ! Thank you very much.

--
You are receiving this mail because:
You are the assignee for the bug.