From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com, Overseers mailing list <overseers@sourceware.org>
Subject: Re: Cygwin package search and cygcheck -p urlencoding still broken on new web server
Date: Wed, 15 Jul 2020 22:25:49 -0600 [thread overview]
Message-ID: <9c03bed5-da26-512c-3c31-ed6cd59f8043@SystematicSw.ab.ca> (raw)
In-Reply-To: <f78e2eaf-07d6-a9bd-ee84-e6414131b23b@gmail.com>
On 2020-07-15 14:13, Marco Atzeri via Cygwin wrote:
> Problem: I want to search for
> libssh/libssh.h
> Using https://cygwin.com/packages/
> If I put the name and press Go the URL is changed in
> https://cygwin.com/cgi-bin2/package-grep.cgi?grep=libssh%2Flibssh.h&arch=x86_64
> and the output is
> Found 0 matches for libsshx2Flibssh.h
> ^^^
> Instead if I modify directly the URL in:
> https://cygwin.com/cgi-bin2/package-grep.cgi?grep=libssh/libssh.h&arch=x86_64
> Found 3 matches for libssh/libssh.h
> ....
> I guess that the current incapability is due to spurious urlencode in
> cgi-bin2/package-grep.cgi
> that is modifing the $param_grep
> echo '<li><a href="package-cat.cgi?file='`urlencode
> $partfile`'&grep='`urlencode $param_grep`'">'$file'</a> - '$desc'</li>'
> Could someone double check my guess ?
No change since your report on May 2nd, and my cross-post to overseers:
https://cygwin.com/pipermail/cygwin/2020-May/244684.html
https://sourceware.org/pipermail/overseers/2020q2/017115.html
where Frank suggested replacing badly urlencoded characters by ".":
$ cygcheck -p libssh/libssh.h
Found 0 matches for libsshx2flibssh.h
$ cygcheck -p libssh.libssh.h
Found 3 matches for libssh.libssh.h
libssh-devel-0.7.3-1 - libssh-devel: SSH implementation library (installed
binaries and support files)
libssh-devel-0.7.5-1 - libssh-devel: SSH implementation library
libssh-devel-0.8.7-1 - libssh-devel: SSH implementation library
The previous break appears to have been fixed by or due to Achim:
https://cygwin.com/pipermail/cygwin/2019-November/243112.html
Ping Achim?!
--
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.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-07-16 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 20:13 Broken search on webserver Marco Atzeri
2020-07-16 4:25 ` Brian Inglis [this message]
2020-07-16 7:44 ` Cygwin package search and cygcheck -p urlencoding still broken on new web server Marco Atzeri
2020-07-16 13:42 ` Jon Turney
2020-07-16 18:48 ` Marco Atzeri
2020-07-16 20:22 ` Brian Inglis
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=9c03bed5-da26-512c-3c31-ed6cd59f8043@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).