similar to: Bug#701554: xcp-xapi: bashism in /bin/sh script

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

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

Hi Mike and Jon, I have made a patch for blktap's vhdpartx script which is full of bashism. I also uploaded that to the git on alioth. Please apply it upstream. I'll see with the release team if it's worth uploading a fix for Wheezy. Cheers, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name:

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:

https://bugzilla.mindrot.org/show_bug.cgi?id=2010 Bug #: 2010 Summary: bashism in configure seccomp_filter check Classification: Unclassified Product: Portable OpenSSH Version: 6.0p1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Build system

Hi Raphael, btw, are you 2 bugs today a simple coincidence with my linkedIn invitation yesterday? ;-) 2008/10/4 Raphael Geissert <atomo64 at gmail.com>: > Package: nut > Version: 2.2.2-8 > Severity: wishlist > Tags: patch > > Attached is a patch adding "support" for tripplite's avr750u UPS. > Issues: > * productid still needs to be specified in

Package: xcp-xapi Severity: normal Tags: upstream Are there good reasons why xapi by default prefers to bidn to 80 and 443? This will lead to xapi installation/start failure on every server machine that might (and will probably) have apache installed. I know we can remove apache or change its port or change xapi's port (But I've had a hard time to easily find out where to specify the

Package: xcp-xapi Version: 1.3.2-8 Severity: minor During upgrade from 1.3.2-7 to 1.3.2-8 got follwing message on slave host (upgrade was simulatanious on slave and master): ... Setting up xcp-xapi (1.3.2-8) ... The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: INTERNAL_ERROR: [

Package: xcp-xapi Version: 1.3.2-6 Severity: important Tags: upstream xe vm-memory-target-set does not write new target to /local/domain/ID/memory/target. Balloon in guest domain is expecting this value to be changed to do selfballooning. This breaks 'dynamic memory control' feature. Steps to reproduce: 1) Setup any PV virtual machine with static-memory-min < static-memory-max 2)

Package: xcp-xapi Version: 1.3.2-6 Severity: normal After some time of rebooting and toolstack restart found very funny output in 'xe pif-lis': xe pif-list params=currently-attached,device device ( RO) : vif2.0 currently-attached ( RO): false device ( RO) : vif211.0 currently-attached ( RO): false device ( RO) : eth1

Dear release team, I would like update the Wheezy package of xen-api with numerous small fixes. These aren't RC bugs, but I believe they are all worth fixing. I believe that the most important one to fix is #682202. Here's the changelog: * Fixes bashism in install-debian-pv.sh (Closes: #690612). * Fixes bashism in interface-visualise (Closes: #690710). * The /etc/init.d/xcp-squeezed

Package: xcp-xapi Version: 1.3.2-15 Severity: normal I am trying to pass an SRIOV virtual function in a virtual machine but the attempt fails with the following errors shown in the xcp-xapi.log [20130829T19:29:17.909Z|debug|sriov1|314 UNIX /var/lib/xcp/xapi|VM.start R:9e8e10bd31bb|pciops] PCI devices from other-config:pci to attach: 0/0000:04:00.1 [20130829T19:29:18.012Z|debug|sriov1|314 UNIX

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream /usr/lib/xcp/bin/xe-edit-bootloader failing with following message: /usr/lib/xcp/bin/xe-edit-bootloader -u 19f66083-e776-70d1-1808-3712688ad138 Creating dom0 VBD: 0fdb952e-92ff-4b53-dd49-8d54b2268787 Plugging VBD: Waiting for /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e0: . done

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). >

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

Package: logcheck Version: 1.2.20a Severity: serious Tags: patch On a system where sh points to dash and LANG=es_ES, I get this: # apt-get -y --reinstall install logcheck Leyendo lista de paquetes... 0% Leyendo lista de paquetes... 0% Leyendo lista de paquetes... 23% Leyendo lista de paquetes... Hecho Creando ?rbol de dependencias... 0% Creando ?rbol de dependencias... 0% Creando ?rbol de

Hi, I've been toying around with the testsuite for a bit, and after recompiling llvm-gcc a bunch of times and fixing a nasty bashism bug, I actually got it to run and pass most tests. When running, I noticed a very long runtime on the lemon test. At first I suspected an infinite loop, but it turned out the test simply needed around 1000 seconds to run. Some investigation turned out that the

Scott Robbins wrote: > On Tue, Apr 26, 2016 at 07:27:26PM -0700, Alice Wonder wrote: >> >> Some of the BSDs use to have a bourne shell and maybe some do, I don't know. >> > Yup. > >> bash is mostly compatible with bourne (can run most bourne scripts) which is why /bin/sh is a symlink to /bin/bash on GNU and most other *nix systems. > > Bash can run