Your message dated Sun, 6 Apr 2025 11:29:49 +0200
with message-id <[email protected]>
and subject line Re: Bug#772248: git-extras: bashism in /bin/sh script
has caused the Debian Bug report #772248,
regarding git-extras: bashism in /bin/sh 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 [email protected]
immediately.)
--
772248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772248
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-extras
Severity: important
Version: 1.9.1-1
User: [email protected]
Usertags: goal-dash
Hi,
I've ran checkbashisms (from the 'devscripts' package) over the whole
archive and I found that your package has a /bin/sh script that uses a
"bashism".
checkbashisms' output:
> possible bashism in ./usr/bin/git-squash line 12 (alternative test command
> ([[ foo ]] should be [ foo ])):
> if [[ $1 == "--me" ]]; then
> possible bashism in ./usr/bin/git-squash line 12 (should be 'b = a'):
> if [[ $1 == "--me" ]]; then
> possible bashism in ./usr/bin/git-refactor line 10 (should be >word 2>&1):
> git checkout -b $branch &> /dev/null
> possible bashism in ./usr/bin/git-info line 26 (unsafe echo with
> backslash):
> echo "## Remote URLs:\n"
> possible bashism in ./usr/bin/git-info line 27 (unsafe echo with
> backslash):
> echo "$(remote_urls)\n"
> possible bashism in ./usr/bin/git-info line 29 (unsafe echo with
> backslash):
> echo "## Remote Branches:\n"
> possible bashism in ./usr/bin/git-info line 30 (unsafe echo with
> backslash):
> echo "$(remote_branches)\n"
> possible bashism in ./usr/bin/git-info line 32 (unsafe echo with
> backslash):
> echo "## Local Branches:\n"
> possible bashism in ./usr/bin/git-info line 33 (unsafe echo with
> backslash):
> echo "$(local_branches)\n"
> possible bashism in ./usr/bin/git-info line 35 (unsafe echo with
> backslash):
> echo "## Most Recent Commit:\n"
> possible bashism in ./usr/bin/git-info line 36 (unsafe echo with
> backslash):
> echo "$(most_recent_commit)\n"
> possible bashism in ./usr/bin/git-info line 37 (unsafe echo with
> backslash):
> echo "Type 'git log' for more commits, or 'git show <commit id>' for full
> commit details.\n"
> possible bashism in ./usr/bin/git-info line 40 (unsafe echo with
> backslash):
> echo "## Configuration (.git/config):\n"
> possible bashism in ./usr/bin/git-info line 41 (unsafe echo with
> backslash):
> echo "$(get_config)\n"
> possible bashism in ./usr/bin/git-feature line 10 (should be >word 2>&1):
> git checkout -b $branch &> /dev/null
> possible bashism in ./usr/bin/git-bug line 10 (should be >word 2>&1):
> git checkout -b $branch &> /dev/null
Not using bash (or a Debian Policy compliant shell interpreter that doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours. Please be aware that dash is the default /bin/sh.
Please closely examine the above output and the script, and determine
what the proper severity of the bug is, and adjust it accordingly. If
it's important or greater please hurry to get this fixed for jessie.
Hints about how to fix bashisms can be found at:
https://wiki.ubuntu.com/DashAsBinSh
Thanks in advance,
Raphael Geissert
--- End Message ---
--- Begin Message ---
Version: 3.0.0-1
On Sat, Dec 06, 2014 at 01:04:49PM +0100, Raphael Geissert wrote:
I've ran checkbashisms (from the 'devscripts' package) over the whole
archive and I found that your package has a /bin/sh script that uses a
"bashism".
This was fixed in 3.0.0 upstream, by referencing bash in the shebangs:
https://github.com/tj/git-extras/commit/7b7913fab141dead7c47170f205f1a93bdf8a0e7
Regards,
Stephen
--- End Message ---
