From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: self-service removal of test: label from packages
Date: Sun, 23 Aug 2020 16:24:35 +0100 [thread overview]
Message-ID: <b9566673-ce0b-e3a9-a46d-1e67e878068a@dronecode.org.uk> (raw)
In-Reply-To: <efda3a33-9003-93f2-ff50-79e3fdb5397d@dronecode.org.uk>
On 08/05/2020 20:19, Jon Turney wrote:
> On 08/05/2020 19:23, Marco Atzeri via Cygwin-apps wrote:
>> Am 08.05.2020 um 18:55 schrieb David Rothenberger:
>>> Would someone with sourceware access please remove the test tag from
>>> rdiff-backup-2.0.0-2? I couldn't figure out how to do it with cygport.
>
> Unfortunately, a self-service way to do this is still to be implemented,
> so asking here is the right thing to do.
>
> See also https://cygwin.com/package-upload.html#untest
To address this shortcoming, I've added an 'untest' command which
package maintainers can run via ssh, which can be used to remove the
test label from one of your authorized packages.
e.g.
> $ ssh cygwin@sourceware.org untest ninja-1.10.1-1
> untest: Removed test: label from x86/release/ninja/ninja-1.10.1-1-src.hint
> untest: Removed test: label from x86/release/ninja/ninja-1.10.1-1.hint
> untest: Removed test: label from x86/release/ninja/ninja-debuginfo/ninja-debuginfo-1.10.1-1.hint
> untest: Removed test: label from x86_64/release/ninja/ninja-1.10.1-1-src.hint
> untest: Removed test: label from x86_64/release/ninja/ninja-1.10.1-1.hint
> untest: Removed test: label from x86_64/release/ninja/ninja-debuginfo/ninja-debuginfo-1.10.1-1.hint
> untest: 6 out of 6 hints for 'ninja' version '1.10.1-1' modified
prev parent reply other threads:[~2020-08-23 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a38e8fb-79d6-3b12-9f52-4442a692d46c@acm.org>
2020-05-08 18:23 ` Please remote TEST from rdiff-backup-2.0.0-2 Marco Atzeri
2020-05-08 19:19 ` Jon Turney
2020-08-23 15:24 ` Jon Turney [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=b9566673-ce0b-e3a9-a46d-1e67e878068a@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).