Your message dated Wed, 17 May 2017 10:49:02 +0300
with message-id <[email protected]>
and subject line Re: Bug#854892: Can't qemu-debootstrap ppc64: /sbin/ldconfig:
Syntax error: word unexpected (expecting ")"
has caused the Debian Bug report #854892,
regarding Can't qemu-debootstrap ppc64: /sbin/ldconfig: Syntax error: word
unexpected (expecting ")"
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.)
--
854892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854892
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-user-static
Version: 1:2.8+dfsg-2
Control: found -1 1:2.1+dfsg-12+deb8u6
sid-amd64# KEEP_DEBOOTSTRAP_DIR=1 qemu-debootstrap --arch ppc64
--keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg sid ppc64
http://ftp.de.debian.org/debian-ports/
[...]
I: Running command: chroot ppc64 /debootstrap/debootstrap --second-stage
I: Keyring file not available at
/usr/share/keyrings/debian-archive-keyring.gpg; switching to https
mirror https://mirrors.kernel.org/debian
W: Failure trying to run: /sbin/ldconfig
W: See //debootstrap/debootstrap.log for details
This log contains:
/sbin/ldconfig: 1: /sbin/ldconfig: Syntax error: word unexpected
(expecting ")")
In jessie qemu, sid-s390x is also affected, but jessie-s390x and
sid-armhf aren't. (In sid qemu, *-s390x fails with a different error,
which I will report separately.)
--- End Message ---
--- Begin Message ---
On Tue, 28 Feb 2017 13:44:55 +0300 Michael Tokarev <[email protected]> wrote:
> It looks like the prob was in the archive, not in qemu.
> At least it works now with either 2.1 or 2.8 qemu just
> fine.
..
> This bug can probably be closed now.
Closing it. If you still have that problem, please reopen this bug.
Thanks,
/mjt
--- End Message ---
