From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: ssh untest wget untest: unable to extract package and version from 'wget'
Date: Mon, 28 Feb 2022 10:56:53 -0700 [thread overview]
Message-ID: <6bfb8909-a513-1ccd-d583-e96f2146d5c5@SystematicSw.ab.ca> (raw)
In-Reply-To: <16aa2d49-6d14-3cc5-1d87-645778de0ca2@dronecode.org.uk>
On 2022-02-28 04:07, Jon Turney wrote:
> On 28/02/2022 05:43, Brian Inglis wrote:
>> I had problems getting clean tests of upgraded wget locally for some
>> reason, but the build and test worked well on scallywag.
>> So I set SCALLYWAG=deploy, pushed to master, and that worked properly,
>> with calm upload email, and upgraded wget in x86{,_64}/setup.ini the
>> only release under [test].
>> But I cannot run 'untest wget': what have I forgotten, or am I
>> missing, to be able to run this?
>> $ ssh cygwin@cygwin.com untest wget
>> untest: unable to extract package and version from 'wget'
>> $ ssh cygwin@cygwin.com 'untest --help'
>> usage: untest.py [-h] [PACKAGE [PACKAGE ...]]
>> test hint remover
>> positional arguments:
>> PACKAGE
>> optional arguments:
>> -h, --help show this help message and exit
> You must include the version-release you wish to untest as well.
> e.g 'untest wget-1.21.3-1'
> See https://cygwin.com/package-upload.html#untest
Thanks for that example and link: noted for future ref; worked great!
> I'll fix the help text to reflect that.
That would be appreciated, and also maybe if you could please clarify
the current error message text, I might have clued in (or not!) e.g.
"unable to extract package, version, release from 'wget' argument"
[Weird: ssh user@host changed to Gmane mailto link
mailto:cygwin-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org]
--
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 binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2022-02-28 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 5:43 Brian Inglis
2022-02-28 11:07 ` Jon Turney
2022-02-28 17:56 ` 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=6bfb8909-a513-1ccd-d583-e96f2146d5c5@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).