[issue815] hgmerge: uses non-POSIX syntax `type' in /bin/sh script
Vincent Danjean
mercurial-bugs at selenic.com
Fri Nov 2 14:51:18 UTC 2007
New submission from Vincent Danjean <vdanjean.ml at free.fr>:
Hi,
This is the Debian bug #447094 ( http://bugs.debian.org/447094 )
The short story is that 'type' is not allowed (by POSIX) in
#!/bin/sh scripts (in particular hgmerge)
In the debian package, I change hgmerge to be a #!/bin/bash script.
I would like to know if upstream will do the same thing or if this
change will remain specific to Debian.
Best regards,
Vincent
Trent W. Buck wrote:
> Package: mercurial
> Version: 0.9.4-1
> Severity: normal
> File: /usr/bin/hgmerge
> Tags: patch
>
> The `type' builtin is not valid sh syntax: http://bugs.debian.org/397601
>
> It is therefore a policy violation to use it in a script that has a
> #!/bin/sh shebang. The simplest way to fix this is to change the
> shebang to use #!/bin/bash.
>
> -- System Information:
> Debian Release: lenny/sid
> APT prefers unstable
> APT policy: (990, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 2.6.22-2-amd64 (SMP w/1 CPU core)
> Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages mercurial depends on:
> ii libc6 2.6.1-5 GNU C Library: Shared libraries
> ii python 2.4.4-6 An interactive high-level object-o
> ii python-support 0.7.4 automated rebuilding support for p
> ii python2.5 2.5.1-5 An interactive high-level object-o
>
> Versions of packages mercurial recommends:
> ii rcs 5.7-20 The GNU Revision Control System
> ii tk8.4 [wish] 8.4.16-1 Tk toolkit for Tcl and X11, v8.4 -
>
> -- no debconf information
>
>
----------
messages: 4249
nosy: 447094, trentbuck, vdanjean
priority: bug
status: unread
title: hgmerge: uses non-POSIX syntax `type' in /bin/sh script
____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue815>
____________________________________________________
More information about the Mercurial-devel
mailing list