From: Chris Hofstaedtler <zeha@debian.org>
To: Evgeny Kapun <abacabadabacaba@gmail.com>, 1132887@bugs.debian.org
Cc: util-linux@vger.kernel.org, wanbingjiang@webray.com.cn
Subject: Re: Bug#1132887: script: "script file -c command" stopped working
Date: Tue, 7 Apr 2026 10:17:45 +0200 [thread overview]
Message-ID: <adS9qeW8w0bmUukR@per.namespace.at> (raw)
In-Reply-To: <88e0b54d-3c86-46ca-ab3f-e116073216d6@gmail.com>
Hi,
thank you for the report, CC'ing upstream.
On Tue, Apr 07, 2026 at 07:07:59AM +0300, Evgeny Kapun wrote:
> Package: bsdutils
> Version: 1:2.42-1
>
> If I run script(1) as "script file -c command", it returns an error:
>
> script: unexpected number of arguments
> Try 'script --help' for more information.
>
> It used to work in earlier versions, so now scripts that rely on the old
> behavior are broken.
Can you check if reverting this commit makes it work again?
| commit 7268e79bc5365034a6e5b38ac5d9bf635e2dafc2
| Author: WanBingjiang <wanbingjiang@webray.com.cn>
| AuthorDate: Thu May 29 16:39:46 2025 +0800
| Commit: Karel Zak <kzak@redhat.com>
| CommitDate: Tue Jun 24 12:00:33 2025 +0200
|
| script: support non-option argument as command
|
| [kzak@redhat.com: - don't use POSIXLY_CORRECT, use "+" in getopt_long(),
| - use strv_join() rather than local concat function]
|
| Based-on: https://github.com/util-linux/util-linux/pull/3599
| Fixes: https://github.com/util-linux/util-linux/issues/3481
| Signed-off-by: Karel Zak <kzak@redhat.com>
Best,
Chris
next parent reply other threads:[~2026-04-07 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <88e0b54d-3c86-46ca-ab3f-e116073216d6@gmail.com>
2026-04-07 8:17 ` Chris Hofstaedtler [this message]
2026-04-07 13:26 ` Bug#1132887: script: "script file -c command" stopped working Karel Zak
2026-04-08 13:36 ` Evgeny Kapun
2026-04-10 8:42 ` Chris Hofstaedtler
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=adS9qeW8w0bmUukR@per.namespace.at \
--to=zeha@debian.org \
--cc=1132887@bugs.debian.org \
--cc=abacabadabacaba@gmail.com \
--cc=util-linux@vger.kernel.org \
--cc=wanbingjiang@webray.com.cn \
/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