Public bug reported:
Binary package hint: open-iscsi
as above
ProblemType: Package
Architecture: amd64
Dependencies:
libgcc1 1:4.3.3-5ubuntu4
gcc-4.3-base 4.3.3-5ubuntu4
findutils 4.4.0-2ubuntu4
libc6 2.9-4ubuntu6
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script r
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/28691445/DpkgTerminalLog.gz
--
package open-iscsi 2.0.870.1-0ubuntu3 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/395578
You received this bu
Indeed it should work somehow but we have exactly the same problem on
powerpc too (Ubuntu, SuSE and Fedora all hit the same problems) -
usplash really wants to hook into a vesa framebuffer for some reason and
I can't imagine any that would require anything but the standard linux
framebuffer abstrac
I do not see how this is such a big "licensing" problem - the CDDL and
GPL-2 are "incompatible" but this just means the verbatim ZFS code will
never be accepted into the *mainline kernel*. Ubuntu has a specific
solution to this - the "ubuntu" directory in the kernel tree, which
holds stuff like com
Public bug reported:
* Install Dapper on Pegasos (somehow)
/dev/rtc does not exist for some reason. I had to "mknod /dev/rtc c 10
135" before clock handling would even attempt to work (using the command
line and the Calendar etc.).
Once created, the boot scripts and shutdown scripts still compla
Possibly the real fix is adding the alias to the modules.conf file,
sorry. Then the module would be loaded properly and a device created
automatically. Still, it isn't done by the installer and I fail to see
why any desktop system would not want a realtime hardware clock :)
--
Realtime clock prob
Public bug reported:
I downloaded the last updated Edgy netboot kernel from
http://archive.ubuntu.com/ubuntu/dists/edgy/main/installer-
powerpc/current/images/powerpc/netboot/
First thing I noticed wrong on Pegasos was that the Marvell Gigabit
Ethernet is not listed for the network interfaces. T
Public bug reported:
Binary package hint: xorg
X 7.1.1 on the latest Edgy build breaks on Pegasos because it doesn't
properly scan PCI domains for graphics cards, and therefore misses the
"AGP" slot which is on domain 1.
The error log is quite short;
:
(EE) No devices detected.
Fatal server er
Apparently it's a space issue, and nothing more. It needs to be on the
CD; removing the Pegasos menu would be bad.
--
edgy knot2 missing vmlinuz-chrp.initrd for pegasos
https://launchpad.net/bugs/59607
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
I just saw the bug got updated to "fix released" regarding the Novell
tracker.
I would like to note that the bug itself is NOT fixed. Reverting X to
it's previous implementation removes PCI domain support. It is NOT a
fix, it is a workaround.
Please reinstate some kind of "still broken" state to
Still present in Hardy and probably every future revision since it's not
been dealt with. NewWorld partitions aren't required on Pegasos, Efika
or any other PPC system that doesn't use Apple partitioning. openSuSE
11.0 beta has implemented a check for these systems (via "hwinfo") to
enable Mac boot
I heartily disagree with Philipp, the netboot images do boot on some
systems - Pegasos and Efika are perfectly capable of combining these
images (uncompressed!) and loading them as is GRUB.
Removing netboot images means removing netboot functionality, and right
now that's the best way we can get t
Public bug reported:
Booting the latest Hardy snapshot on Pegasos shows the pata_via driver
is not loaded when it should be.
The pata_via troubles have been fixed as of 2.6.24.3 so it can be safely
re-enabled.
** Affects: linux-kernel-di-powerpc-2.6 (Ubuntu)
Importance: Undecided
S
Public bug reported:
Binary package hint: base-installer
* Boot Edgy Desktop CD on a Genesi Pegasos or ODW
(you will need a vmlinuz-chrp.initrd kernel for this; see
http://www.ppczone.org/ - also remove the BusID and UseFBDev lines from
/etc/X11/xorg.conf once it fails, and "startx" to hit the
Public bug reported:
Binary package hint: xserver-xorg-input-wacom
After changing the X.org config to use /dev/input/event rather than
/dev/wacom (which is NOT present in the LiveCD), I found it is fairly
hard to get the pointer to the side of the screen or below the last
quarter.
I have to make
Public bug reported:
We found that the following lines are present in the /etc/X11/xorg.conf
file on the LiveCD:
BusID "PCI:0:0:5"
UseFBDev "true"
This causes the X startup to fail with an FBIOPUT_VSCREENINFO "invalid
argument" property. Removing BOTH of them allows "startx" to bring up
th
Public bug reported:
Binary package hint: mkvmlinuz
mkvmlinuz is missing from Edgy install CDs.
It is practically a requirement for producing a working Pegasos install.
The most recent available version (v23 upwards, which is in the Debian
package tree and maintained by a Genesi Employee, Sven L
This is still ridiculously broken on Pegasos on release.
--
X does not start on Pegasos in Edgy because of broken PCI domain support
https://launchpad.net/bugs/61410
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
It would be fine for next Edgy release to fix it with the "don't even
try multi-domain support" patch as fixed by Novell and adopted by
RedHat/Fedora.
However multi-domain support should be properly there eventually and any
work to fix it properly would be awesome; every architecture (ppc,
sparc,
Also this bug;
https://bugs.freedesktop.org/show_bug.cgi?id=7248
--
X does not start on Pegasos in Edgy because of broken PCI domain support
https://launchpad.net/bugs/61410
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
armel (and ppc) architectures include the xserver-xorg-video-all package
for graphics.
Inside this metapackage is described every xorg video driver available
in the standard distro; however many of these cards are exceedingly rare
on these platforms. For example, vga and vesa
At Genesi we can confirm it works already on Babbage and Lange, it pops
up as rt2800usb and connects to all wireless networks we've tested (b,
g, n, mixed, unencrypted, WEP and WPA2).
The X86 dependency doesn't seem to cause a problem here...
--
please enable rt3070sta in the imx51 kernel
https:
We have this working at Genesi. We will be submitting patches to SGTL
and the iMX audio support in the next week.
--
no sound devices on babbage board with linux-image-2.6.31-100-imx51
https://bugs.launchpad.net/bugs/420447
You received this bug notification because you are a member of Ubuntu
Bug
Hi Loic,
2.6.31-100.7-imx51 with a changed config.. actually we bumped our ABI
in-house just to be safe (to the wonderfully random yet oddly apt "631")
to ensure that we do not clash with the generic Ubuntu kernel, bumped it
to 2.6.31 mainline, added a lot of our own patches, but it is mostly
2.6.
rt2800usb works fine on the RT3070 though. I thought the whole point of
rt2800usb was to get away from the godawful mess that is the Ralink
mainline sta driver? In 2.6.31 with the support for RT3070 rolled into
rt2800usb, rt3870sta as a driver is practically obselete, and given that
rt2800usb works
Once we've finished testing, we have to make sure it works on all the
Lange revisions *and* a bunch of Babbages.. personally I just have a 5.1
(1.0), 5.1 (1.1), 5.2 (the famous Engadget one) and a Babbage 2.1 (or
maybe it's a 2.0 I can never tell the difference..)
--
no sound devices on babbage b
We're seeing the same problem here with linux-fsl-imx51 on Babbage and
Lange. Seems like there is some weird stuff going on in the USB core
these days... it worked fine in 2.6.28 for both boards, but the Karmic
kernels are a blowout.
--
device descriptor read/64, error -110
https://bugs.launchpad
We fixed something like this by adding consumer supplies in the pmic
driver in arch/arm/mach-mx51/mx51_board_pmic_blah.c to the relevant
regulator blocks.. I'm going to thoroughly test this audio patch and
we'll see if the whole bundle makes everything work nicely. Prepping a
Lange release once we
We had the same audio-as-a-module issues with the MPC5200B AC97 driver -
when built in to the kernel it worked much more reliably than when
loaded as a module (nobody ever knew why and then Jon Smirl wrote a new
driver anyway for ASoC).
BTW I was wondering if it'd be a too intrusive change to rena
x-image-2.6.31-100-imx51
> https://bugs.launchpad.net/bugs/420447
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Matt Sealey
Product Development Analyst, Genesi USA, Inc.
--
no sound devices on babbage board with linux-image-2.6.31-100-imx51
ht
Loic,
Indeed:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d53d9e67b55f6a9fc3f836c5c392eb41ce5676f4
Note the problems, but they do not seem to affect me here (hooray for
wpa_supplicant!) - to get it working all you need is the firmware from
the rt3070sta driver
Part of the problem is the 2.6.31 ALSA SoC subsystem changed vs. 2.6.28
(Jaunty, Freescale BSP) and it's not a "straight port". A little more
work has to be done by the driver in init. The 3 lines I posted should
fix it to the point that if you DO have an i2c bug on your board, you
can see it (othe
Public bug reported:
Having xserver-xorg-input-vmmouse installed in my virtual machine sticks
the mouse pointer to the middle of the screen.
Tried to use ubuntu-bug to report this, but since it relies on Firefox
(and there's no mouse..) it is frustratingly difficult to achieve.
Uninstalling xser
** Attachment added: "udevadmin-mouse0,1.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-vmmouse/+bug/1597447/+attachment/4692411/+files/udevadmin-mouse0%2C1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Installed VM is Ubuntu 16.04 x86-64 (UEFI) and the host is Windows 7
64-bit.
Are we missing a udev rule? Xorg log seems to report that the input1 or
mouse1 device is being ignored since no driver is specified. The current
udev rule only seems to match against "i8042 AUX port".
** Attachment adde
FYI udev monitoring shows no events on the
** Attachment added: "udevadm-event0,1,2,3.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-vmmouse/+bug/1597447/+attachment/4692412/+files/udevadm-event0%2C1%2C2%2C3.txt
--
You received this bug notification because you are a membe
Alternatively installing xserver-xorg-input-libinput seems to supercede
vmmouse and give me mouse back without uninstalling vmmouse itself. That
actually matches my experience with Fedora 23 in the past few days..
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Wouldn't the fix to be to mark the /boot directory using btrfs tools as
not able to create sparse files? Or do that on kernel posthook?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/464743
Title:
er
Public bug reported:
Binary package hint: system-config-printer
If you go to System->Administration->Printing and try and add printers
without being in the Configure Printers group, the applet asks for the
root account and root password.
This is obviously not workable on Ubuntu where root has "n
Please remember ubiquity contains flash-kernel too and there is another
detection script (flash-kernel-installer?) which needs the machine and
subarch added to it.
Those both shipped on the smartbook too.. I can send the patches if
needed but they are plainly obvious additions.
Btw why does ubiqu
I get the same thing. This is pretty silly. Why does hal depend on
smartdimmer, also? This is an nVidia LCD panel tool. Surely HAL should
be able to detect if it's there or not, not have it as a forced
dependency. I run on VirtualBox and Intel graphics machines so
smartdimmer is useless to me.
n.
Public bug reported:
Binary package hint: usb-imagewriter
USB ImageWriter should support compressed images. It is a good idea
because it reduces bandwdith and storage space on the servers, and
allows less disk usage on the host system to write the image out (a
650MB .img file for ARM Netbook coul
Oliver, quick question. We've just found that making sound a module
(which fixes a lot) breaks on the Smartbook for some reason. This is
going to cause a problem re audio group/acls as above.
I am curious how I would check that the devices send the correct uevents
and if they don't, if there is so
Public bug reported:
Binary package hint: xfce4-panel
test system: iMX51 (Efika MX), Maverick built from rootstock on
2010-09-15. Since a few weeks, the Xfce desktop panel has been broken.
After ruling out the obvious things, all I can do is look at this button
that is truncated here.
Basically
Screenshot demonstrating problem
** Attachment added: "screenshot.png"
https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/640701/+attachment/1594727/+files/screenshot.png
--
Xfce "Applications" menu is truncated in panel on Maverick
https://bugs.launchpad.net/bugs/640701
You received
Public bug reported:
Running on armel, Maverick
Opening certain Xfce apps which seem to be all terminal-related (package
manager with output of installation progress, xfce terminal) makes Xorg
CPU usage spike to 100% on idle.
I've tried turning off cursor blinking, changing font settings to no
a
Any chance your contact gave a better timeframe than the next point
release, since that was released already twice (6.0.2) and I'm still
seeing the problem here at a most infuriating rate..
Is there some way of making sure that a new VM install won't have any
problems with this? Once the system is
For the edification of the reporters I can confirm this doesn't just
happen on Chromebook but on an Efika MX running kernel 3.7, using the
imx-drm staging driver. Xorg seems to crash a hell of a lot too, but I
can't tell if it's related. Using xserver-xorg-video-modesetting or
-fbdev makes no diffe
** Changed in: efikamx
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/671027
Title:
Add Efika MX Smartbook/Smarttop support
To manage notifications about this bug go
** Changed in: efikamx
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/650703
Title:
oem-config-prepare works, but oem-config fails to start after reboot
To
Loic:
Feel free to re-enable check_subarch
Also remove any check for "efikasb" as a subarch, since it's all efikamx
now. That's the only reason check_subarch was disabled, because we had
two, and now we have one. For Natty it will stay -efikamx.
As for the extensions and tmpfile stuff, this was
Requesting a super immediate update to Maverick as this is affecting our
distribution support for Efika MX..
** Also affects: efikamx
Importance: Undecided
Status: New
** Changed in: efikamx
Status: New => Confirmed
** Changed in: efikamx
Assignee: (unassigned) =>
*** This bug is a duplicate of bug 650703 ***
https://bugs.launchpad.net/bugs/650703
** This bug has been marked a duplicate of bug 650703
oem-config-prepare works, but oem-config fails to start after reboot
* You can subscribe to bug 650703 by following this link:
https://bugs.launchpad.
(BTW regarding last comment, if you guys approve I will submit a
patch...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/671027
Title:
Add Efika MX Smartbook/Smarttop support
--
ubuntu-bugs mailin
Okay I have some problems with the support committed to flash-kernel,
namely
* it doesn't differentiate between kernel versions, so uImage and uInitrd will
overwrite any older uImage and uInitrd version. This is unfriendly and it is
impossible to tell at a glance (without using mkimage to list t
Additional comment: Loic, PLEASE can we put back "efikamx" subarch
support? It would be a legacy hack but it will mean our current kernels
work. I don't want to have to build a vendor-specific package and track
it for the sake of 2 lines. Neither Maverick nor Natty has or will have
an "mx51" subarc
I was under the impression that flash-kernel, as a subordinate of
update-initramfs or at the very least kernel postinst.d hook, is ALWAYS
called with a version (in fact, standards state that it passes the
kernel version as $1 AND $2 for some funky reason). There's very very
little reason to call it
For reference this is my untested hook for the Efika..
efikamx_flash_kernel() {
tmp=$(tempfile)
printf "Generating kernel u-boot image... " >&2
mkimage -A arm -O linux -T kernel -C none -a 0x90008000 \
-e 0x90008000 -d $kfile "$tmp.uImage" >&2 1>/dev/null
Fix released on packages.efikamx.info
** Changed in: efikamx
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729161
Title:
upower does not handle lid switch events
** Changed in: efikamx
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/650703
Title:
oem-config-prepare works, but oem-config fails to start after reboot
--
u
solved:
https://bugs.freedesktop.org/show_bug.cgi?id=35018
** Affects: efikamx
Importance: High
Assignee: Matt Sealey (mwsealey)
Status: New
** Affects: upower (Ubuntu)
Importance: Undecided
Status: New
** Also affects: efikamx
Importance: Undecided
Status
https://bugs.freedesktop.org/show_bug.cgi?id=35018
** Changed in: efikamx
Importance: Undecided => High
** Changed in: efikamx
Assignee: (unassigned) => Matt Sealey (mwsealey)
** Description changed:
Binary package hint: upower
UPower does not handle lid switch events pr
Please backport to Maverick as well as pulling this for Natty when
required :D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729161
Title:
upower does not handle lid switch events properly
--
ubun
Attaching a patch which I have tested extensively which restores the
-efikamx subarch and also makes the script work to our basic
specifications. I did capitulate to the new "boot.script" method but we
can properly handle kernel versions. It is amazing what a little bit of
'sed' can do.
Also fixes
boot.script to go with the previous patch. Drop it in /boot.
** Attachment added: "boot.script source file"
https://bugs.launchpad.net/efikamx/+bug/671027/+attachment/1890546/+files/boot.script
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Not being able to remove kernels generated is a flaw in the fundamental
way flash-kernel is written. We discussed this. It needs to "act" like
update-initramfs but it doesn't. Adding more and more hacks to work
around it is just that - more and more hacks.
There is one reason and one reason only h
What I'm asking is for you guys to give us a break so we can move on to
other things.. :)
Flash-Kernel NG is almost done, I just have to "port" a bunch of plugins
and find the Debian maintainers so we can drive it upstream. Some of the
things in there I am not sure are even used, and a lot of the
Yes, we run what you might consider a fork of Maverick with about 5
packages different, and about 10 on top.. but the fact is we use the
vast majority of the Ubuntu archive for the convenience of our
customers. The less we change the better the board gets supported. If
Ubuntu wants to support it or
I should also mention, let me reiterate the first comment in this bug,
and our experience with the Linaro "kernel support", that the supplied
boot scripts were totally incorrect behavior for our board. Nobody
consulted us on this. Consider this consulting work for Linaro - we
fixed the boot script
FYI this is happening again: we're starting to prep images with
accelerated graphics by default, and the gdm X server is starting too
fast again, so Ubiquity is failing 3 times out of 5...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Also affects: efikamx
Importance: Undecided
Status: New
** Changed in: efikamx
Status: New => Confirmed
** Changed in: efikamx
Assignee: (unassigned) => Matt Sealey (mwsealey)
** Changed in: efikamx
Importance: Undecided => Medium
--
You received
Here's a funny thing: if the system boots with initramfs (we only fixed
U-Boot for this in November for all boards), oem-config and GDM
cooperate and run fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Still happens here, while we're stuck on 2.6.31, the userspace is
Maverick at today's latest updates. It can't be an HCI 1.1 problem
because this one is 2.1, and it has a default link policy :)
hci0: Type: BR/EDR Bus: USB
BD Address: 00:22:43:D9:D7:84 ACL MTU: 1021:8 SCO MTU: 64:1
Putting in a nudge here as Evolution is incredibly difficult to setup
and configure on a netbook. Given the amount of whitespace in the setup
and Preferences GUI, this is infuriating.
** Also affects: efikamx
Importance: Undecided
Status: New
** Changed in: efikamx
Status: New =>
Oliver, it is our intent that /boot always be an ext2 partition.
We are phasing out support for booting from vfat partitions as
"recommended practise" in so far as it's only in U-Boot to keep old
systems working before migrating partitions to ext2. Once we release
U-Boot 2.0.6 for both boards, eve
BTW commenting our check_running_subarch is also only there because
Smartbook still uses the "efikasb" subarch, and will move to the
"efikamx" subarch shortly.
** Also affects: ubiquity
Importance: Undecided
Status: New
--
Add Efika MX Smartbook/Smarttop support
https://bugs.launchpad.
Adding Ubiquity as being affected as it seems to include flash-kernel.
--
Add Efika MX Smartbook/Smarttop support
https://bugs.launchpad.net/bugs/671027
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Okay it is true that users are in lpadmin. My mistake.
As for audio and video groups, udev must not be working on ARM picking
up "local foreground console users" since webcam and audio simply do not
work without adding users to those groups. The previous explanation for
the bug was that "pulseaudi
hrw just had a problem with this on his custom built kernel and solved
it by loading the module.
I assume then, that udev has to see a plug event from the kernel audio
module being loaded or it will not set the ACLs on it?
This does not explain the video not working: the Smartbook has a USB UVC
w
Should also say in our kernel and the last Lucid Ubuntu kernel audio was
built-in so it would have suffered the same effect.
--
oem-config created users are not in audio or video group
https://bugs.launchpad.net/bugs/669219
You received this bug notification because you are a member of Ubuntu
Bug
Oliver, I have to completely disagree with you that U-Boot source code
is even required for the board - let alone something based on mainline.
This is not some crazy little embedded board like Beagle where the
updates come fast and there are 10 forks, and to be honest we would be
doing a great diss
flash-kernel doesn't support seperate partitions by any design except to
put this in board-specific code. It's not global, it's duplicated every
time it's needed (and in this case it seems only on boards that can only
boot from vfat). We don't feel we need to support it. In any case if the
patch is
I can confirm this happens on the Efika MX Smartbook (armel) too with
the kernel from Genesi's gitorious repository. Our battery is SBS
compliant and publishes all the same power supply attributes as a
standard ACPI SBS battery. There is a custom driver in play (efikasb-
battery) however this doesn
Public bug reported:
Binary package hint: ubiquity
Booting a system which has been "oem-config-prepare quiet" prepped, or
just touching /var/lib/oem-config/run should enable and run a relevant
oem-config frontend on first boot.
However, this does not happen. The scripts for oem-config and gdm
co
Will try the debug thing. No changes have been made to the system since
rootstock and adding packages. Way back in the deep dark past (jaunty?)
this method I used worked fine. I don't think you can blame it on
"modification" of the system. I ran aptitude.
Oliver, there are a couple bugs making oem
After creating a rootstock with xfce about 20 times last week, and
manually hacking the permissions before booting, I can safely say it
does NOT start because GDM manages to get in the way every time. Rob
must be very lucky to have a disgustingly slow SD card on his
Beagleboard which is giving oem-
Okay I guess I am going to run another minimal image up and fetch Xfce
and ubiquity and see what the difference is.
We have a few fiddles to make sure GDM doesn't rocket off and make
itself the owner of vt7 here but it remains to be seen if this is a real
fix or just something we're going to use a
Okay our investigation showed that, empirically, once upstart has
started a job (like gdm), no other job can stop it, even if it is
(starts on) for that job. Actually this means that a system with gdm,
kdm etc. installed they will all fight for a VT and the first one will
get it, however this is a
Just checked out plugininstaller.py line 761 at the crash: it's
"os.symlink" to link /initrd.img to /boot/initrd.img-2.6.31.14-efikamx
I would note that the initrd.img is NOT massaged into a uImage.
The partition /boot is on is vfat, so no symlinks, so an obvious crash,
no?
Rob is Beagle xM stil
Yergh, turns out that upstart hack doesn't work at all. start on
(stopped oem-config) works better but oem-config seems never to
technically finish. This is a nightmare.
Rob, that explains those few lines your fixup script.. :)
We're going to prep an update for all our lines soon that enables
boo
Public bug reported:
Binary package hint: rootstock
rootstock (0.1.99.4) cmdline does not respect TMPDIR
discussion with Oliver Grawert revealed that on line 699:
BUILDDIR=$(mktemp -d)
Should be
BUILDDIR=$(mktemp -d -t)
So that mktemp respects the TMPDIR environment variable.
** Affects: ro
Unfortunately after some testing it seems this simple thing causes a
horrible, horrible problem: TMPDIR is passed on to qemu which means when
packages are installed, they are fed to a TMPDIR that possibly does not
exist on the target system. In my case I have a large disk mounted at
/build and erro
92 matches
Mail list logo
