On domingo, 10 de julio de 2016 2:01:04 P. M. ART Steve M. Robbins wrote:
> Hi,
> I wanted to make people aware that I have uploaded Digikam 5.0.0 packages to
> Debian earlier today.

First of all: thanks a lot.
> I uploaded to experimental for staging for a few reasons:
> 1. To work through the build issues on various architectures.
> 2. The configuration files are in a new location, but digikam does no
> migration [1].  To the user, it appears you are starting from scratch and
> there is a risk of confusion -- the referenced bug is from someone who
> thought (mistakenly) that a migration procedure was required.  The bug also
> references possibly using a KF5 function KConfig::copyTo() to migrate the
> files, but then concludes that some digikam 4 settings cause digikam 5 to
> crash.  At this point, it seems that automatic migration is unsafe but that
> the initial configuration wizard should be augmented with text that
> describes the upgrade- from-4.x scenario better.  I'm seeking suggestions
> on what might be the best approach here.

I would for starters file an RC bug to the version in experimental so users 
know this before it gets installed (thanks to apt-listbugs). This would also 
make the bug more visible.

Then I guess it's either provide patches upstream or wait for a fix :-/

> 3. The showfoto internationalized docs are missing due to an upstream bug
> [2]. The bug is now patched upstream; however, the fix re-structures the
> source tarball so it is unclear whether this is easy to port into the
> current version; or better to wait for upstream 5.1.0 source tarball.

We still have time before the freeze, do you think a new upstream release will 
happen during this timeframe? Else it could be an upstream snapshot.

Thanks a lot Steve!

Those are my principles. If you don't like them I have others.
 -- Groucho Marx

Lisandro Damián Nicanor Pérez Meyer

Attachment: signature.asc
Description: This is a digitally signed message part.

pkg-kde-extras mailing list

Reply via email to