Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #179442 > unrolled thread

libjasper in Stretch

Back to article view | Back to linux.debian.user

Contents

  libjasper in Stretch David Griffith <dave@661.org> - 2017-03-27 14:20 +0200
    Re: libjasper in Stretch Reco <recoverym4n@gmail.com> - 2017-03-27 14:30 +0200
      Re: libjasper in Stretch David Griffith <dave@661.org> - 2017-03-27 15:10 +0200
        Re: libjasper in Stretch Sven Hartge <sven@svenhartge.de> - 2017-03-27 16:10 +0200
          Re: libjasper in Stretch David Griffith <dave@661.org> - 2017-03-28 03:50 +0200
            Re: libjasper in Stretch Sven Hartge <sven@svenhartge.de> - 2017-03-28 10:00 +0200

#179442 — libjasper in Stretch

Why is libjasper missing from Stretch?

According to https://bugs.debian.org/812630 the stated reason for its 
removal is that libjasper has not been updated for ten years.  In this 
same bug report is a note that this assertion is not true and a link was 
provided to a Github repository.  Nonetheless, the bug report was closed 
without further explanation.

-- 
David Griffith
dave@661.org

A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

[toc] | [next] | [standalone]

#179444

	Hi.

On Mon, Mar 27, 2017 at 12:16:25PM +0000, David Griffith wrote:
> 
> Why is libjasper missing from Stretch?
> 
> According to https://bugs.debian.org/812630 the stated reason for its
> removal is that libjasper has not been updated for ten years.

No, actual reason for the removal was that the only package's maintainer
stepped down. Quote:

Due to lack of time, I'm looking for a new maintainer for this package.


> In this same
> bug report is a note that this assertion is not true and a link was provided
> to a Github repository.

On January 25th maintainer stepped down. On October 25th (i.e. more than
half-year later) someone noticed that upstream was back to life.
The fact that the second assertion (i.e. 'dead upstream') was
invalidated did not do anything to first (i.e. 'package unmaintained').

> Nonetheless, the bug report was closed without
> further explanation.

The explanation was provided, in fact:

------------------- Reason -------------------
RoQA; dead upstrem, replaced by openjpeg
----------------------------------------------

Reco

[toc] | [prev] | [next] | [standalone]

#179450

On Mon, 27 Mar 2017, Reco wrote:

> 	Hi.
>
> On Mon, Mar 27, 2017 at 12:16:25PM +0000, David Griffith wrote:
>>
>> Why is libjasper missing from Stretch?
>>
>> According to https://bugs.debian.org/812630 the stated reason for its
>> removal is that libjasper has not been updated for ten years.
>
> No, actual reason for the removal was that the only package's maintainer
> stepped down. Quote:
>
> Due to lack of time, I'm looking for a new maintainer for this package.
>
>
>> In this same
>> bug report is a note that this assertion is not true and a link was provided
>> to a Github repository.
>
> On January 25th maintainer stepped down. On October 25th (i.e. more than
> half-year later) someone noticed that upstream was back to life.
> The fact that the second assertion (i.e. 'dead upstream') was
> invalidated did not do anything to first (i.e. 'package unmaintained').
>
>> Nonetheless, the bug report was closed without
>> further explanation.
>
> The explanation was provided, in fact:
>
> ------------------- Reason -------------------
> RoQA; dead upstrem, replaced by openjpeg
> ----------------------------------------------

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?


-- 
David Griffith
dave@661.org

A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

[toc] | [prev] | [next] | [standalone]

#179459

David Griffith <dave@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

Grüße,
Sven.


-- 
Sigmentation fault. Core dumped.

[toc] | [prev] | [next] | [standalone]

#179506

On Mon, 27 Mar 2017, Sven Hartge wrote:

> David Griffith <dave@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.

Why is/was there a "libopenjpeg5" package?

-- 
David Griffith
dave@661.org

A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

[toc] | [prev] | [next] | [standalone]

#179512

David Griffith <dave@661.org> wrote:
> On Mon, 27 Mar 2017, Sven Hartge wrote:
>> David Griffith <dave@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.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web