[digikam] [Bug 491042] New: MariaDB (MySQL) embedded files missing in fresh install

[Michael Miller]

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

            Bug ID: 491042
           Summary: MariaDB (MySQL) embedded files missing in fresh
                    install
    Classification: Applications
           Product: digikam
           Version: 8.4.0
          Platform: macOS (DMG)
                OS: macOS
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Database-Mysql
          Assignee: digikam-bugs-null at kde.org
          Reporter: michael_miller at msn.com
  Target Milestone: ---

Created attachment 172135
  --> https://bugs.kde.org/attachment.cgi?id=172135&action=edit
Migration screenshot

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
Several MariaDB files are missing when doing a fresh install.  I'm unable to
migrate to MySQL Internal DB.  There are several bugs, but they all appear to
be related to packaging MariaDB.  I'll try to document them all here in way
that makes sense.

When using the Database Migration tool, MariaDB files are not detected by
digiKam.  See screenshot "migration". The MariaDB files have the "Find" button
instead of the "Change" button.  When I point the binaries to an installation
of MariaDB using the "Find" button to a different MariaDB installation
installed via homebrew into /opt/homebrew/, I get an error message "Internal
server is not used and not active!" (see screenshot "Internal server").

Further research shows the mariadb symlinks in
/Applications/digiKam.org/digikam.app/Contents/etc and
/Applications/digiKam.org/digikam.app/Contents/lib don't actually point to any
binaries (see screenshot "symlinks").  Also, none of the MariaDB binaries exist
anywhere in the /Applications/digiKam.org/digikam.app/Contents subtree,
including mariadbd, mariadb-admin, mariadb-install-db, and mariadb-upgrade.

Not all of the *.sql files needed to create a new MariaDB database exist in the
digiKam subtree. 

STEPS TO REPRODUCE
1. Fresh install of digiKam
2. Configure digiKam normally with SQLLite
3. Add a few images to the library
4. Shut down digiKam
5. Start digiKam
6. Navigate to Settings->Database Migration
7. Select MySQL Internal as the destination type

OBSERVED RESULT
Unable to migrate to MySQL Internal.

EXPECTED RESULT
Migration tool works as before.  The last time I used the migration was several
versions ago.  Maybe 7.x something, or maybe early 8.x.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 14.5 (23F79)
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.