public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: [ITA] popt-1.18-1
Date: Thu, 31 Dec 2020 21:57:56 +0900	[thread overview]
Message-ID: <20201231215751.5F22.50F79699@gmail.com> (raw)

Hi!

ITA for popt, which has been maintained by Yaakov [1].

Now, the latest upstream of popt is 1.8 [2].

A new candidate cygport file is placed at [3].
And, it's been tested on Cygwin AppVeyor CI (ID 1560: [4]).

Generated package files are placed at [5] and [6]:

[1]: https://cygwin.com/git/?p=git/cygwin-packages/popt.git
[2]: https://github.com/rpm-software-management/popt
[3]: https://github.com/cygwin-lem/popt-cygport/tree/n_1.18-1
[4]: https://cygwin.com/cgi-bin2/jobs.cgi?id=1560
  or https://ci.appveyor.com/project/cygwin/scallywag/builds/37059271
[5]: https://cygwin-lem.github.io/popt-cygport/
[6]: https://github.com/cygwin-lem/popt-cygport/tree/n_1.18-1_gh-pages


# An ignorable warning brought by autoreconf-2.69:

```
autoreconf-2.69: configure.ac: tracing
Use of uninitialized value $args[0] in split at /usr/bin/autoreconf-2.69 line 493, <GEN2> line 8.
```

It will disappear when using autoconf v2.69d or later,
fixed at the commit
https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=b0d20c049bda80a9d323326ae5ea3fd5e4857712

# 1.18-testit.patch:

In the upstream CI, the original `testit.sh` will pass the tests.
But, on cygwin `src_test()` will get some failures without this patch.

The diffrences are program names printed in usage,
and so they are not critical and would be acceptable.



Regards, 

Lem


             reply	other threads:[~2020-12-31 12:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-31 12:57 Lemures Lemniscati [this message]
2020-12-31 13:06 ` Lemures Lemniscati

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=20201231215751.5F22.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).