digikam (4:7.7.0-2) unstable; urgency=medium

  * Database upgrade failure: occasionally seen with external database 
    due to lack of database permissions.  This can be solved by issuing 
    the following mysql command: 
        set global log_bin_trust_function_creators=1;
    See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007220

 -- Steve M. Robbins <smr@debian.org>  Mon, 11 Jul 2022 19:40:00 -0500

digikam (4:5.9.0-1) unstable; urgency=medium

  * Build contains video support using QtAV.

 -- Steve M. Robbins <smr@debian.org>  Sun, 15 Apr 2018 20:46:17 -0500

digikam (4:5.6.0-1) unstable; urgency=medium

  * Build is missing video support -- waiting on the new QtAV package to
    pass through the NEW package queue processing.  See #737016.

 -- Steve M. Robbins <smr@debian.org>  Sun, 01 Oct 2017 13:49:51 -0500

digikam (4:5.0.0-1) experimental; urgency=medium

    Upgrade from DigiKam 4: The configuration files for DigiKam 5 are in a
    different location than DigiKam 4.  The configuration is NOT migrated
    automatically and -- due to unresolved bugs -- it is NOT recommended
    to do so manually.  Instead, configure DigiKam to use the same
    location for collections and database.  The database generated by
    DigiKam 4 can be used by DigiKam 5 unchanged.

 -- Steve M. Robbins <smr@debian.org>  Wed, 10 Aug 2016 22:56:38 -0500
