<div dir="ltr"><div><div><div><div>Hi,<br><br></div>I have created my own device tar ball. ( Thanks a lot to rootsotck project, it saves my time )<br><br></div>By decompressing the tar ball, I have two directories ( assets, system ) and one file ( hardware.yaml ).<br><br></div>However, when I tried to generate the image file by using ubuntu-device-flash, the log indicates that it failed to read hardware.yaml from device part. Please refer to the following log:<br><i><b><br>Using a custom device tarball<br>Searching for hardware.yaml in device part<br>Failed to read harware.yaml from device part, provisioning may fail: failed to extract a hardware.yaml from the device part: tar: hardware.yaml: Not found in archive<br>tar: Exiting with failure status due to previous errors</b></i><br><br></div>and in the end it shows this:<br><br><i><b>stat /tmp/diskimage271141682/hardware.yaml: no such file or directory<br><br><br></b></i><div>my command to generate the system image shown below:<br></div><div><br><i><b>sudo ubuntu-device-flash core 15.04 --oem=generic-amd64 --channel edge --enable-ssh --device-part=ubuntu-core.device.tar.xz -o custom_snappy.img --developer-mode --verbose --clean-cache<br><br></b></i></div><div><i><b><br></b></i></div><div>I dont know why the log shows it failed to read hardware.yaml even it is in my tarball.<br><br></div><div>Please advise.<br></div><div><i><b><br><br><br></b></i></div><div>Sam Lin<i><b><br></b></i></div><div><div><div><div><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 2, 2015 at 10:34 AM, I-Sheng Lin <span dir="ltr"><<a href="mailto:ckjboy2003@gmail.com" target="_blank">ckjboy2003@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div>Hi,<br><br></div>For the step 1 ( debian-cd[1] ),<br><br></div>from waht I have understood so far, I will need to build the debian-cd image first in order to build the Snappy Ubuntu Core later on. <br><br></div>In the link you provided <a href="https://code.launchpad.net/~ubuntu-cdimage/debian-cd/ubuntu" target="_blank">[1] </a>, the README file mentions I need to edit the PATHs for the mirror.<br><br></div>I dont exactly get the "mirror" means but I assume it is here.<br><br></div><a href="http://ftp.us.debian.org/debian/" target="_blank">Debian_mirror</a><br><br></div>The CONF.sh has some paths needed to modify, for example:<br><br>=====================================================================<br><pre><code># Paths to the mirrors export MIRROR=${MIRROR:-$CDIMAGE_ROOT/ftp}<br><br># Path of the temporary directory export TDIR=$CDIMAGE_ROOT/scratch/$PROJECT/$DIST/$IMAGE_TYPE/tmp</code></pre>=====================================================================<br></div><div>I don't figure out how to configure the path yet.<br><br></div><div>Kindly let me know:<br><br></div><div>1. Does the local package mirror you refer to is the one I paste above ?<br><br></div><div>2. How to edit the CONF.sh file in order to fit building requirement ?<br><br><br></div><div>Thanks<br></div><div><div class="h5"><br><div><div><div><div><div><div><div><div><div><div><div><div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 29, 2015 at 5:57 PM, Oliver Grawert <span dir="ltr"><<a href="mailto:ogra@ubuntu.com" target="_blank">ogra@ubuntu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">hi,<br> <span>Am Donnerstag, den 29.10.2015, 16:57 +0800 schrieb I-Sheng Lin:<br> <br> > This means, I want to build an exactly the same image as what I have<br> > downloaded from the website here Link.<br> ><br> > I would go through your link and please let me know if you have any<br> > idea to do it.<br> <br> </span>sure we do, after all we produce these images ;)<br> note though that this isn't actually trivial ...<br> <br> snappy is built from binary deb packages from the ubuntu archive using<br> our general image build infrastructure (debian-cd [1], ubuntu-cdimage<br> [2], live-build (with all the configuration and extra hooks shipped in<br> the livecd-rootfs [3] package))<br> <br> the list of used .deb packages is provided as .manifest file for each<br> rootfs tarball at [4]<br> <br> so to build *everything* from source you would have to use the debian<br> source packages from the archive and change them, have the above<br> infrastructure in place and provide a local package mirror with your<br> changed packages.<br> <br> the fragments on <a href="http://cdimage.ubuntu.com" rel="noreferrer" target="_blank">cdimage.ubuntu.com</a> then serve as input for the<br> <a href="http://system-image.ubuntu.com" rel="noreferrer" target="_blank">system-image.ubuntu.com</a> server [5] that takes these build fragments and<br> turns them into delta tarballs (rootfs, device and oem-snap) for image<br> based upgrades.<br> ubuntu-device flash then assembled them into an img file based on the<br> json data for your selected channel on <a href="http://system-image.ubuntu.com" rel="noreferrer" target="_blank">system-image.ubuntu.com</a>. which<br> you can then dd to your harddisk (or SD card).<br> <br> there is a small project called rootstock that allows you to replicate<br> the steps [1] - [4] at [6], but that will only give you the cdimage<br> artifacts, so you need some local system-image server and would need to<br> convince ubuntu-device-flash to make use of it...<br> <br> good luck ;)<br> <br> ciao<br> oli<br> <br> [1] <a href="https://code.launchpad.net/~ubuntu-cdimage/debian-cd/ubuntu" rel="noreferrer" target="_blank">https://code.launchpad.net/~ubuntu-cdimage/debian-cd/ubuntu</a><br> [2] <a href="https://code.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline" rel="noreferrer" target="_blank">https://code.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline</a><br> [3] <a href="https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk" rel="noreferrer" target="_blank">https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk</a><br> [4] <a href="http://cdimage.ubuntu.com/ubuntu-core/daily-preinstalled/current/" rel="noreferrer" target="_blank">http://cdimage.ubuntu.com/ubuntu-core/daily-preinstalled/current/</a><br> [5]<br> <a href="https://code.launchpad.net/~ubuntu-system-image/ubuntu-system-image/server" rel="noreferrer" target="_blank">https://code.launchpad.net/~ubuntu-system-image/ubuntu-system-image/server</a><br> [6] <a href="https://code.launchpad.net/~ogra/project-rootstock-ng/trunk" rel="noreferrer" target="_blank">https://code.launchpad.net/~ogra/project-rootstock-ng/trunk</a><br> <div><div><br> <br> --<br> snappy-devel mailing list<br> <a href="mailto:snappy-devel@lists.ubuntu.com" target="_blank">snappy-devel@lists.ubuntu.com</a><br> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snappy-devel" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snappy-devel</a><br> </div></div></blockquote></div><br><div dir="ltr"><div><span></span><span></span><b><span lang="de"></span></b></div></div> </div></div></div></div></div></div></div></div></div></div></div></div></div></div> </blockquote></div><br><br></div></div></div></div></div></div></div></div></div></div>