First: apologies for a late response; unfortunately your email was stuck in my spam filter :-(
On Wednesday, March 18, 2026 1:31:05 a.m. Central Daylight Time Karine Crévecœur wrote: > Hi, > > I set severity of this bug to serious, but I probably should have set it > to grave, because digikam is unusable (Am I the only one that encounter > this bug?) I'm waiting for libopenexr update to 3.4.6+ds3. But I doubt > that solve the issue. The other package impacts with this was swayimg. > The rebuild of swayimg solves it! Should I need to rebuild digikam > myself to prove digikam needs a rebuild? Thanks. No, I recognize that digikam needs a rebuild. But not just digikam because digikam's usage of libopnexr is actually through one or two other packages - all need a rebuild. I'm pleased to report that the rebuild is now complete and digikam is fixed for unstable. If you are tracking testing, the migration is waiting on the migration of qt6-base. I can't predict when that might be but hopefully not too long. -Steve
signature.asc
Description: This is a digitally signed message part.
