public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: Updated: {jasper/libjasper1/libjasper-devel}-1.900.22-1: JPEG-2000 codec library
Date: Sun, 07 May 2017 08:42:00 -0000	[thread overview]
Message-ID: <3857c3e9-3469-d333-3cf9-7c96d336a6e3@gmail.com> (raw)
In-Reply-To: <7916dc59-7541-fe66-cf04-e41f806fbc97@cygwin.com>

On 05/05/2017 22:37, Yaakov Selkowitz wrote:
> On 2017-03-24 14:02, Yaakov Selkowitz wrote:
>> On 2017-02-22 13:53, Yaakov Selkowitz wrote:
>>> No, the details are in the .spec file.  In short, you want 1.900.13 plus
>>> the jasper-1.900.1-CVE-2008-3520.patch and
>>> jasper-1.900.13-CVE-2016-9583.patch patches.
>>
>> There are now additionally jasper-1.900.13-CVE-2016-9262.patch and
>> jasper-1.900.13-CVE-2016-8654.patch.
>>
>>> Once that's uploaded, then let's proceed with an upgrade to 2.0.10,
>>> which already has all the fixes along with the ABI version change.
>>
>> That's 2.0.12 now.
>
> Unfortunately, some of my packages ended up being built against the
> later libjasper1, so it's too late to revert this cleanly.  Therefore, I
> have left it alone, uploaded 2.0.12, and rebuilt all my dependent packages.
>
> Marco, that leaves your gdal and GraphicsMagick as the only packages
> still using libjasper1.


rebuilding GraphicsMagick.
Gdal should have a new release in short.

Regards
Marco

      reply	other threads:[~2017-05-07  8:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <announce.vriv4m1gi57u.fsf@volkerzell.de>
2017-01-12 20:26 ` Yaakov Selkowitz
2017-01-18 12:12   ` Dr. Volker Zell
2017-02-22 19:53     ` Yaakov Selkowitz
2017-03-24 19:02       ` Yaakov Selkowitz
2017-05-05 20:37         ` Yaakov Selkowitz
2017-05-07  8:42           ` Marco Atzeri [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3857c3e9-3469-d333-3cf9-7c96d336a6e3@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).