Serge, I asked Alex to escalate this because it has required us to make
a devirtualised PPA for a commercial project that involves libreoffice
builds. This has some risk of being an operational problem, because
it's going to be using Ubuntu build resources rather than the usual PPA
ones. I'd appr
I believe that this is with qemu 1.3.0+dfsg-1~exp3ubuntu8~3.IS.12.04 and
Linux 2.6.24-32-xen.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1129571
Title:
libreoffice armhf FTBFS
Status in QEMU:
** Tags added: qemu-user-ubuntu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1077116
Title:
automoc4 segfaults when building in an armhf pbuilder on an amd64 host
Status in QEMU:
New
Status in
** Tags added: qemu-user-ubuntu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1129571
Title:
libreoffice armhf FTBFS
Status in QEMU:
New
Status in “qemu” package in Ubuntu:
Confirmed
Bug desc
Peter: While this is true, is it actually likely to happen? I thought
in our conversations in the past (when I previously attempted to
escalate this class of problems via Linaro) it had been fairly clear
that this was a very difficult task that isn't likely to be scheduled
for the foreseeable futu
Right, I can absolutely understand that. The question would I suppose
be whether you think this is a completely unreasonable thing to put in a
distro patch; I think SUSE are doing so for basically the same reason we
would be, that is, a setup such as PPAs where virtualisation isn't
available direc
** Tags added: qemu-user-ubuntu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1084148
Title:
Qt5 Beta 1 QProcess start and execute causes segmentation fault on
armhf
Status in QEMU:
New
Status
We're now building armhf/arm64 packages on real arm64 hardware in
Launchpad, so, while this problem may well still exist in qemu, it no
longer applies to Launchpad builds.
** Changed in: launchpad-buildd
Status: Triaged => Won't Fix
--
You received this bug notification because you are a
