similar to: bashisms in xen init scripts...

Package: xen-utils-3.0 Version: 3.0.2+hg9681-0bpo1 Severity: important Disclaimer: I'm using the packages from www.backports.org here (in the box where the problem manifested), but I've seen that it happens too with the packages straight from sid. When I installed the packages for Xen and created a domU ("chen.cfg"), it couldn't be brougth up. The error that was displayed

Dear R-devel, Recently I ran into trouble installing two separate packages, nloptr and ncdf4, both due to the same issue: they have scripts that have the shebang `#! /bin/sh', but have bashisms in them, i.e. non-POSIX-compliant bash scripts. I use dash [1] as my shell environment, since it's about 4x as fast as bash. It looks like it's recently also become the default shell for

Package: xcp-xapi Version: 1.3.2-14 Severity: important User: debian-release at lists.debian.org Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: >possible bashism in ./usr/lib/xcp/lib/host-restore line

Package: xcp-xapi-debug Version: 1.3.2-11 Severity: normal User: debian-release at lists.debian.org Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: >possible bashism in

Package: xcp-xapi Version: 1.3.2-11 Severity: important User: debian-release at lists.debian.org Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: >possible bashism in

Package: blktap-utils Version: 2.0.90-1 Severity: important User: debian-release at lists.debian.org Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: >possible bashism in ./usr/sbin/vhdpartx line 40

Package: xen-3.0 Version: 3.0.2+hg9697-1 Severity: important Hello, There was a problem while autobuilding your package: > Automatic build of xen-3.0_3.0.2+hg9697-1 on avidan by sbuild/i386 0.49 > Build started at 20060725-0410 > ****************************************************************************** ... > CFLAGS="-O2 -fomit-frame-pointer -DNDEBUG -m32 -march=i686 -Wall

On 06/08/2015 02:43 PM, Laine Stump wrote: >> However, if I changed the destination address from "anywhere" to the >> IP of the host machine, the problem resolved. So I change the script >> to as follows. (Changes are highlighted. For some reason the original >> script didn't work using /bin/sh, but it did with /bin/bash, so I >> changed that too). >

So should I go ahead and make the changes to the script that I suggested? Thanks, BJ On Mon, Jun 8, 2015 at 3:21 PM, Eric Blake <eblake@redhat.com> wrote: > On 06/08/2015 02:43 PM, Laine Stump wrote: > >> However, if I changed the destination address from "anywhere" to the > >> IP of the host machine, the problem resolved. So I change the script >

Patch attached. Steve -- --- Makefile-orig 2006-09-04 14:37:18.000000000 +0100 +++ Makefile 2006-09-04 14:37:34.000000000 +0100 @@ -57,7 +57,7 @@ .PHONY: ioemu ioemuinstall ioemuclean ifndef XEN_NO_IOEMU ioemu ioemuinstall ioemuclean: - [ -f ioemu/config-host.h ] || \ + ( test -f ioemu/config-host.h ) || \ (cd ioemu; ./configure --prefix=usr) $(MAKE) -C

Hi: The following patch replaces a bash-specific substitution with equivalent POSIX /bin/sh substitutions. This allows a Xen-patched Linux to build when /bin/sh is a POSIX shell other than bash. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Thanks, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au> Home Page:

Package: xen-utils-common Version: 3.0.3-0-2 Severity: important patch I ran into this problem when using xen on Debian/Etch. I have several virtual xen instanses, and I name them using their fully qualified DNS domain name. These machines have failed to start automatically when I booted the host machine, and I just recently found out why. During shutdown, I was messages like this: Error:

On 10/19/2018 5:09 AM, Jonathan Billings wrote: > On Fri, Oct 19, 2018 at 01:07:46PM +0200, Simon Matter wrote: >> That's really an important point, because those who started using Linux >> with Linux/systemd will be bound to Linux/systemd with their knowledge, >> switching to a *BSD or other Unix will be difficult. For me, I don't like >> to be limited in such

Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: normal With SE Linux it's desirable to give utilities and daemons the minimum privileges. That includes not permitting general utilities to create directories under /var/run. I think it would be best if /var/run/xen-hotplug was created by an init script such as /etc/init.d/xen (or by systemd-tmpfiles when using systemd units).

Source: xen Version: 4.4.0-4 Severity: normal Xendomains init and default files are taken from debian folder instead source and are not updated for some years. Please update them from upstream source. I did a fast update and test of them available here: https://github.com/Fantu/pkg-xen/commit/4d1914776256d209665d490182cf662f70cda619 -- System Information: Debian Release: jessie/sid APT prefers

Once upon a time, Stephen Harris <lists at spuddy.org> said: > On Sun, Apr 19, 2015 at 09:40:29PM -0400, Tim Dunphy wrote: > > Good tip! But I ran the script with sh +x . I guess that running it with sh > > You should use "bash -x" ("bash" and not "sh" because sh may not be bash > everywhere; eg Ubuntu; "-x" and not "+x"

Package: xen-utils-common Version: 4.0.0-1 Severity: important When xen domUs are saved by running /etc/init.d/xendomains stop the memory images are saved world readable, so that every user on the system can read the memory dumps. The default mode of /var/lib/xen/save is 755, vm images are saved with mode 755. At least the save directory shoudn't be world readable. -- System Information:

Package: xen-utils-common Version: 4.1.2-1 Severity: grave Justification: renders package unusable (Grave because dash is the default /bin/sh) With dash 0.5.5.1-7.4 as /bin/sh, /usr/sbin/xm enters an infinite loop of reexcuting itself. When run with bash, it works correctly. I traced that to /usr/lib/xen-common/bin/xen-toolstack; here's the diff between "/bin/sh -x /usr/sbin/xm"

Package: xen-utils-common Version: 3.4.2-4 Severity: important File: /usr/lib/xen-common/bin/xen-utils-wrapper xm invoke vtpm-common.sh from /etc/xen/hotplug, wich one call gawk, but gawk is not listed as dependence for xen packages. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux

Hi, Here's a patch fixing bashism in !/bin/sh scripts in xen-api. Please apply this upstream as well. Cheers, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Fixes-2-bashism.patch Type: text/x-diff Size: 3639 bytes Desc: not available URL: