From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: calm/mksetupini changes
Date: Tue, 24 May 2022 19:05:10 +0900 [thread overview]
Message-ID: <20220524190508.21E0.50F79699@gmail.com> (raw)
In-Reply-To: <135fb374-2d39-2e71-697f-ce0986168c1d@dronecode.org.uk>
On Mon, 23 May 2022 19:37:43 +0100, Jon Turney
> On 23/05/2022 14:09, Lemures Lemniscati wrote:
> > On Sat, 21 May 2022 21:31:46 +0100, Jon Turney
> >> Eventually, this should eliminate packages in the deprecated so report [1] with a rdepends count of zero. To reduce the rdpepends count to zero, packages which depend on a deprecated soversion need to be rebuilt for a newer soversion.
> >>
> >> [1] https://cygwin.com/packages/reports/deprecated_so.html
> >
> > Although libiconv2 is contained in the list above,
> > I don't think it is deprecated.
>
> Haha. I think this is just a bug, and the code which generates that report is getting confused by the test: status of libiconv2.
>
> Thanks for pointing that out. I'll look into fixing it when I can.
All right. And yet another small point...
I've uploaded libiconv 1.17-1 tagged with 'test',
but their statuses are 'stable' in the page of its src package:
https://www.cygwin.com/packages/summary/libiconv-src.html ,
while the ones of generated libiconv packages are 'test':
e.g. https://www.cygwin.com/packages/summary/libiconv-devel.html .
I was confused a bit by the situation :).
Lem
next prev parent reply other threads:[~2022-05-24 10:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 19:26 Jon Turney
2021-06-26 13:29 ` Jon Turney
2022-05-21 20:31 ` Jon Turney
2022-05-23 13:09 ` Lemures Lemniscati
2022-05-23 18:12 ` Achim Gratz
2022-05-23 18:44 ` Achim Gratz
2022-05-24 9:50 ` Lemures Lemniscati
2022-05-23 18:37 ` Jon Turney
2022-05-24 10:05 ` Lemures Lemniscati [this message]
2022-05-24 12:57 ` Jon Turney
2022-05-26 8:55 ` 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=20220524190508.21E0.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).