From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] openjpeg2-2.3.1p113
Date: Thu, 17 Dec 2020 07:06:49 +0900 [thread overview]
Message-ID: <20201217070646.7854.50F79699@gmail.com> (raw)
In-Reply-To: <20201216210447.26BE.50F79699@gmail.com>
On Wed, 16 Dec 2020 21:04:51 +0900, Lemures Lemniscati
> Hi!
>
> ITA for openjpeg2, which has been maintained by Yaakov [1].
>
> Now, the latest upstream of openjpeg is at 113 commits after v2.3.1 [2].
> The commits contain bug fixes and security patches.
>
> A new candidate cygport file is placed at [3] (but it is not tested
> on Cygwin AppVeyor CI, yet).
>
> Generated package files are placed at [4] and [5]:
>
> * libopenjp2-devel-2.3.1p113-1.tar.xz
> * libopenjp2-doc-2.3.1p113-1.tar.xz
> * libopenjp2_7-2.3.1p113-1.tar.xz
> * openjpeg2-2.3.1p113-1.tar.xz
>
> * openjpeg2-2.3.1p113-1-src.tar.xz
> * openjpeg2-debuginfo-2.3.1p113-1.tar.xz
>
> [1]: https://cygwin.com/git/?p=git/cygwin-packages/openjpeg2.git
> [2]: https://github.com/uclouvain/openjpeg/tree/98a4c5c3709e0cc43b0a1c151ed5bd85a2d607fa
> [3]: https://github.com/cygwin-lem/openjpeg2-cygport/tree/n_2.3.1-1
> [4]: https://cygwin-lem.github.io/openjpeg2-cygport/
> [5]: https://github.com/cygwin-lem/openjpeg2-cygport/tree/n_2.3.1-1_gh-pages
>
>
> Regards,
>
> Lem
And, it passed the Cygwin AppVeyor CI:
https://ci.appveyor.com/project/cygwin/scallywag/builds/36868332
Some failures have occurred while src_test(),
but all of them are known failures.
Regards,
Lem
prev parent reply other threads:[~2020-12-16 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 12:04 Lemures Lemniscati
2020-12-16 17:46 ` Marco Atzeri
2020-12-16 22:18 ` Lemures Lemniscati
2020-12-16 22:06 ` Lemures Lemniscati [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=20201217070646.7854.50F79699@gmail.com \
--to=lemures.lemniscati@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).