Source: digikam
Severity: important
User: j...@debian.org
Usertags: jasper-rm
Hi, jasper will be removed from Debian for the stretch release (and
following that, the archive in general).
It's been unmaintained for nearly a decade, please als see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8
For the records, I've asked upstream whether openjpeg support would be
possible:
https://bugs.kde.org/show_bug.cgi?id=364231
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth
Oh no! Please don't remove me
On 12 June 2016 at 15:00, Christoph Anton Mitterer
wrote:
> For the records, I've asked upstream whether openjpeg support would be
> possible:
> https://bugs.kde.org/show_bug.cgi?id=364231
>
> Cheers,
> Chris.
___
pkg-kde-
control: tag -1 patch
On Mon, Mar 14, 2016 at 08:19:29PM +0100, j...@debian.org wrote:
> Hi, jasper will be removed from Debian for the stretch release (and
> following that, the archive in general).
Since we are pretty near the removal of jasper, I intend to NMU digikam
disabling jasper support
Hi Mattia,
I can take care of this.
On June 27, 2016 01:11:57 PM Mattia Rizzolo wrote:
> Since we are pretty near the removal of jasper, I intend to NMU digikam
> disabling jasper support with the attached patch.
> I'm currently holding off the upload as I first need to have imagemagick
> done
On Mon, Jun 27, 2016 at 11:00:26PM -0500, Steve M. Robbins wrote:
> I can take care of this.
Great!
> I have prepared an upload with a second change: to remove the
> find_package(Jasper) in cmake. This way, even if libjasper-dev is
> accidentally present, the build won't use it.
cool, thanks
