https://bugs.kde.org/show_bug.cgi?id=372047
--- Comment #2 from Frank Steinmetzger <war...@gmx.de> ---
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 watching all bug changes.
