David Griffith <d...@661.org> wrote: > On Mon, 27 Mar 2017, Sven Hartge wrote: >> David Griffith <d...@661.org> wrote:
>>> I also saw this >>> https://packages.qa.debian.org/j/jasper/news/20170212T221713Z.html, which >>> suggests that the original maintainer has stepped back up. In any case, I >>> should perhaps convert my code from using Jasper to using OpenJPEG. But >>> then I notice that there is no libopenjpeg5-dev in Stretch to go along >>> with libopenjpeg5. Is this just temporary? >> >> Umm, openjpeg has also been removed from Stretch/Testing and Unstable >> >> See https://tracker.debian.org/pkg/openjpeg and >> https://tracker.debian.org/news/791076 >> >> It has been replaced by openjpeg2: >> >> https://tracker.debian.org/pkg/openjpeg2 > Okay, now I see it. Why is the package named "openjp2-7" instead of > "openjpeg2-7"? It seems to me that the latter would be easier to find. Because the library is called "libopenjp2.so.7": https://packages.debian.org/sid/amd64/libopenjp2-7/filelist Why is the library named like that? You have to ask upstream about that. I smell a SO name conflict in there somewhere. > Why is/was there a "libopenjpeg5" package? Was: because it was the name of the library in the past. Debian Jessie is the last Version of Debian containing both libopenjpeg2 and libopenjp2. Is: There is not, at least in Testing and Unstable. If you still have the package, then maybe because you have libavcodec-ffmpeg56 or libavcodec56 installed, both still depend on it. Grüße, Sven. -- Sigmentation fault. Core dumped.
