On Tue, Jun 28, 2016 at 08:52:53PM +0200, Andras Horvath wrote: > Hi, I am the mainstream developer. How much time do I have to react on this > and rewrite the code to remove the libjasper dependency? Thanks, Andras
For sure jasper won't be in Debian stretch, period.
ATM the only 2 blockers for jasper removal are kodi (which is already
fixed in upstream git and yesterday I bumped its bug to RC too, if we
wanted to really remove it quickly we could upload the current alpha of
it), and aaphoto.
The other rdeps of jasper currently in the archive are:
* opencv: I uploaded it yesterday morning and it started a transition
itself, I have to ask an ftpmaster to forcefully remove the old
binaries (as there is an rdep FTBFSing, but I don't care of it)
* kopete: (only in kfreebsd): I'm going to request RM on those archs
* imagemagick: I NMUed it, tomorrow should get in
* ziproxy: I NMUed it, tomorrow should get in
kodi should be autoremoved from testing at the end of July, after that
I'll have the release team to remove jasper from testing too (it's not
going to be autoRMed).
What I know is that I'm not going to break or remove kodi, so once
that's fixed I don't think I'll be so patient, as I really hate to keep
things blocked only for a leaf package that is not getting ported/fixed,
so to give you an idea, so probably you have a bit less than 2 months;
which could be plenty, but of course depends on your availability and
how your life is currently, which I know nothing about.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
