Your message dated Sun, 28 Apr 2024 04:25:26 +0200
with message-id <71a21685-e50e-4919-a64b-6207df334...@svario.it>
and subject line Re: Bug#496740: script: cannot execute binary file, when file 
is a normal shell script
has caused the Debian Bug report #496740,
regarding script: cannot execute binary file, when file is a normal shell script
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
496740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bash
Version: 3.1dfsg-8
Severity: normal


I just tried to execute a shell script by executing "sh script" where
sh in /bin/bash and script is a shell script consisting of lots of
automatically-generated move commands.

But I got:

   script: script: cannot execute binary file

(the duplication of "script: " seems to be another bug).

Now, the file clearly wasn't a binary file. I played around with locales,
but couldn't quickly find a locale where bash would accept the script (not
sure if the check is locale-dependent or not).

The apparent reason for triggering this bug seems to be the high content
of 8-bit-octets in the file, but since filenames are not locale-dependent
on unix, bash should not force any "binary" interpretation on valid shell
scripts.

(sorry, can't provide the script itself atm., but could probably provide
an anonymised version of it if really needed).

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bash depends on:
ii  base-files                4.0.4          Debian base system miscellaneous f
ii  debianutils               2.15.3         Miscellaneous utilities specific t
hi  libc6                     2.7-12         GNU C Library: Shared libraries
ii  libncurses5               5.6+20080531-1 Shared libraries for terminal hand

bash recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 5.0-6

On Wed, 27 Aug 2008 07:37:28 +0200 Marc Lehmann <debian-report...@plan9.de> wrote:
I just tried to execute a shell script by executing "sh script" where
sh in /bin/bash and script is a shell script consisting of lots of
automatically-generated move commands.

But I got:

   script: script: cannot execute binary file

(the duplication of "script: " seems to be another bug).

The apparent reason for triggering this bug seems to be the high content
of 8-bit-octets in the file, but since filenames are not locale-dependent
on unix, bash should not force any "binary" interpretation on valid shell
scripts.

Hi,

this issue does not seem to affect version 5.0-6 and later of bash. The second issue reported at the end of this bug report ("bash /bin/firefox copies /bin/firefox in /tmp") also seems to have been fixed in hte meantime.

Feel free to open a new bug if you can still reproduce any of these issues.

Regards,

--
Gioele Barabucci

--- End Message ---

Reply via email to