From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: Re: untest failing with TypeError: add_packages() got an unexpected keyword argument 'trustedMaint'
Date: Sun, 22 Jan 2023 15:01:49 -0700 [thread overview]
Message-ID: <484533b4-d8ff-374a-e2ec-8ba3a823284a@Shaw.ca> (raw)
In-Reply-To: <0eaee947-2ff1-b452-8a7b-2d84d00fccac@Shaw.ca>
On 2023-01-22 11:46, Brian Inglis via Cygwin-apps wrote:
> On 2023-01-22 03:59, Jon Turney wrote:
>> On 22/01/2023 06:34, Brian Inglis via Cygwin-apps wrote:
>>> On 2023-01-21 16:57, Brian Inglis via Cygwin-apps wrote:
>>>> $ ssh cygwin untest dash-0.5.12-1
>>>> Traceback (most recent call last):
>>>> File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main
>>>> "__main__", mod_spec)
>>>> File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code
>>>> exec(code, run_globals)
>>>> File "/sourceware/cygwin-staging/calm/calm/untest.py", line 83, in <module>
>>>> sys.exit(main())
>>>> File "/sourceware/cygwin-staging/calm/calm/untest.py", line 79, in main
>>>> untest(p)
>>>> File "/sourceware/cygwin-staging/calm/calm/untest.py", line 39, in untest
>>>> if not tool_util.permitted(p):
>>>> File "/sourceware/cygwin-staging/calm/calm/tool_util.py", line 50, in
>>>> permitted
>>>> mlist = maintainers.add_packages(mlist, common_constants.PKGMAINT,
>>>> trustedMaint=common_constants.TRUSTEDMAINT)
>>>> TypeError: add_packages() got an unexpected keyword argument 'trustedMaint'
>> Thanks for reporting this.
>>> Newer version not pushed, built, or installed on site?
>> No, just a bug I introduced. I've had a go at fixing it, please try again now.
> Now no connection, with same session, ssh-agent, key:
> $ ssh cygwin untest dash-0.5.12-1
> kex_exchange_identification: Connection closed by remote host
> Connection closed by 8.43.85.97 port 22
Retried and now working okay:
$ ssh cygwin untest dash-0.5.12-1
untest: Removed test: label from x86_64/release/dash/dash-0.5.12-1-src.hint
untest: Removed test: label from x86_64/release/dash/dash-0.5.12-1.hint
untest: Removed test: label from
x86_64/release/dash/dash-debuginfo/dash-debuginfo-0.5.12-1.hint
untest: 3 out of 3 hints for 'dash' version '0.5.12-1' modified
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
prev parent reply other threads:[~2023-01-22 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 23:57 Brian Inglis
2023-01-22 6:34 ` Brian Inglis
2023-01-22 10:59 ` Jon Turney
2023-01-22 18:46 ` Brian Inglis
2023-01-22 22:01 ` 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=484533b4-d8ff-374a-e2ec-8ba3a823284a@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin-apps@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).