public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com, Overseers mailing list <overseers@sourceware.org>
Subject: Re: changed behaviour for "cygcheck -p "
Date: Sun, 3 May 2020 15:05:24 -0600	[thread overview]
Message-ID: <b3e585d6-983a-d4be-38d9-602ab99c8451@SystematicSw.ab.ca> (raw)
In-Reply-To: <20200502153643.GD749797@elastic.org>

On 2020-05-02 09:36, Frank Ch. Eigler wrote:
>>> It seems there is a new escape system that is fooling
>>> the search engine
>>> $ cygcheck -p 'bin/mutt'
>> https://cygwin.com/packages/
> 
> I suspect it's not new, but yes, urlescaped %XY characters are not
> correctly handled in package-grep.cgi.  Until it's fixed, you can use
> dots instead of slashes, for example.

The issue is new since the new server, both cygcheck -p, and Cygwin Package
Search which it invokes at https://cygwin.com/packages/..., worked fine
previously, as the common specific search target was /usr/bin/...

Is the new RHEL/Fedora/CentOS system you are using missing url{en,de}code, or
the path to those, or something else invoked in package-grep.cgi?

Maybe update https://sourceware.org/lists.html#what-software to document recent
changes and https://sourceware.org/news.html to track issues and fixes.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

      parent reply	other threads:[~2020-05-03 21:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 10:11 Marco Atzeri
2020-05-02 14:53 ` Brian Inglis
2020-05-02 15:36   ` Frank Ch. Eigler
2020-05-02 15:55     ` Marco Atzeri
2020-05-03 21:05     ` Brian Inglis [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=b3e585d6-983a-d4be-38d9-602ab99c8451@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    --cc=overseers@sourceware.org \
    /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).