public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: brian Inglis <Brian.Inglis@SystematicSw.ab.ca>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: ssh untest wget untest: unable to extract package and version from 'wget'
Date: Mon, 28 Feb 2022 11:07:20 +0000	[thread overview]
Message-ID: <16aa2d49-6d14-3cc5-1d87-645778de0ca2@dronecode.org.uk> (raw)
In-Reply-To: <8d2144f2-30b0-213e-2dbd-3eb0bc985f14@SystematicSw.ab.ca>

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-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org untest wget
>      untest: unable to extract package and version from 'wget'
>      $ ssh cygwin-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org '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

I'll fix the help text to reflect that.

  reply	other threads:[~2022-02-28 11:07 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 [this message]
2022-02-28 17:56   ` 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=16aa2d49-6d14-3cc5-1d87-645778de0ca2@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=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).