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: untest failing with TypeError: add_packages() got an unexpected keyword argument 'trustedMaint'
Date: Sun, 22 Jan 2023 10:59:51 +0000 [thread overview]
Message-ID: <26f2ead8-d807-cc05-d6ce-e9dba485013c@dronecode.org.uk> (raw)
In-Reply-To: <440772b0-257a-9302-dfcd-dd53f73a92c7@Shaw.ca>
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.
next prev parent reply other threads:[~2023-01-22 10:59 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 [this message]
2023-01-22 18:46 ` Brian Inglis
2023-01-22 22:01 ` 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=26f2ead8-d807-cc05-d6ce-e9dba485013c@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).