Your message dated Mon, 11 Sep 2006 16:26:22 +0200
with message-id <[EMAIL PROTECTED]>
and subject line [Pkg-xen-devel] Bug#376494: xen-utils-3.0: Bashisms in 
/etc/xen/scripts/* make Xen unable to run domUs
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
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
was:

~# xm create -c chen.cfg
Using config file "/etc/xen/chen.cfg".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

        Checking the logs, /var/log/xen-hotplug.log was full of lines
like this:

trap: 53: ERR: bad trap

        I am using dash as /bin/sh, and this is the problem. I've not
checked in detail, but it seems that there are bashisms in the scripts
at /etc/xen/scripts that cause this failure. Changing /bin/sh to
/bin/bash fixes the problem.

        The solution would be changing /bin/sh to /bin/bash in the
scripts, or at least warning the user that /bin/sh needs to be /bin/bash
in order for the scripts to work.



-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.16-1-xen-686
Locale: LANG=es_ES, LC_CTYPE=es_ES (charmap=ISO-8859-1) (ignored: LC_ALL set to 
es_ES)

Versions of packages xen-utils-3.0 depends on:
ii  e2fslibs              1.37-2sarge1       ext2 filesystem libraries
ii  iproute               20041019-3         Professional tools to control the 
ii  libc6                 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an
ii  libncurses5           5.4-4              Shared libraries for terminal hand
ii  python                2.3.5-2            An interactive high-level object-o
ii  udev                  0.093-0bpo1        /dev/ and hotplug management daemo
ii  xen-hypervisor-3.0-i3 3.0.2+hg9681-0bpo1 The Xen Hypervisor for i386
ii  zlib1g                1:1.2.2-4.sarge.2  compression library - runtime

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 3.0.2-3+hg9762-1

On Mon, Jul 03, 2006 at 12:28:42PM +0200, Roberto Suarez Soto wrote:
>       The solution would be changing /bin/sh to /bin/bash in the
> scripts, or at least warning the user that /bin/sh needs to be /bin/bash
> in order for the scripts to work.

This is the implemented solution.

Bastian

-- 
Extreme feminine beauty is always disturbing.
                -- Spock, "The Cloud Minders", stardate 5818.4

--- End Message ---

Reply via email to