Ged, if you have a local repository that's complete enough to contain all you need, I assume that it would work. I think you just need to edit the debootstrap command to point to your own repo. Look in zlibs/bootstrap.
There are several possible locations of isohdpfx.bin. Maybe we should be finding it instead of hard-coding the location. Look at zlibs/iso.
I'll take a look at that debootstrap command but it isn't a local mirror, it's a caching proxy which uses apt-cacher-ng.
Not sure I'd want to set up a full mirror just for this.
(Yeah, it took me a while to find isohdpfx.bin.
modifying the debootstrap command only affected the package sources for stage 1, so in the end I modified the value of 'mirror' in lib/libdevuansdk/config (which means that source.list gets the same value so I'll need to fix that up near the end of the build). I've burned a CD and it boots and lets me log in OK, so more or less everything seems to be working. Now I need to think a bit more about the packages I need to install.
The image doesn't seem to be bootable directly from a USB stick, just wondering if there's an easy way to achieve that?
It should be bootable from a usb stick. Image the stick with dd like you would with any other isohybrid. That's what isohdpfx.bin is for. What are you getting when you try to boot the usb?
Hmmmm.... I did image the stick as normal. When I try to boot from it the machine just boots from the hard drive, like the stick wasn't there, but I can mount the USB stick partition after the machine has booted from the HDD. The same machine boots fine from the same image on a CD.
Well as long as I know it's supposed to boot I can investigate why it isn't working. It might be something weird with the machine's firmware or something. I'll let you know what I find. Thanks again for the help.
F12, F8, ESC or some other key might get you to a boot device menu where you can choose the usb.
yeah, I did all that. It offers to boot on the stick and then doesn't.
Don't worry, I'll work something out thanks.
I use apt-cacher as well. Been using it for live-build for some years.
Is there some doc somewhere explaining your use of _MIRROR_BINARY?
I briefly played with apt-cacher-ng, but ended up dumping it. I am now using squid-deb-proxy instead.
_MIRROR_BINARY is from my live-build setups.
And my point was that to wire up apt-cacher for live-sdk the url for apt-cacher would be something like : "http://localhost:3142/packages.devuan.org/merged" which would go in libdevuansdk config.
apt-cacher-ng takes a little work to configure it to work for devuan. It doesn't by default come with config for devuan.
@phil - what do you find better with squid-deb-proxy?
Ah, my mistake. I took your "live-build" to mean "live-sdk".
... for live-sdk the url for apt-cacher would be something like : "http://localhost:3142/packages.devuan.org/merged" which would go in libdevuansdk config.
Sure, as per my post that's more or less what I'm doing with live-sdk.
... apt-cacher-ng takes a little work to configure it to work for devuan. It doesn't by default come with config for devuan.
That makes me nervous that I might have missed something. Do you mind posting a complete Devuan apt config?
For me, apt-cacher-ng was flakey, and one of the features simply didn't work. When I was doing some research on the matter I found comments by others who had similar experiences with apt-cacher-ng. That research also led me to squid-deb-proxy, which I decided to try. After I figured out how to configure it, it has been working without problems. I did have a problem with it once, but it was probably my fault -- I installed it on a fresh system and it refused to start up using the old cache. After I deleted the old cache and let it create a new one, everything was fine.
Also, getting live-build to work with squid-deb-proxy was simple.
And that should avoid the problem I had of "http://localhost:3142/packages.devuan.org/merged" ending up in /etc/apt/sources.list!
Here are some more config changes I had to make to get squid-deb-proxy to work.
Adjust the above to fit your situation.
The application dpkg-divert is installed on my base system which is Uubuntu 16.04. I have not been able to figure out what postunpack is, both ducky and google have not been sufficiently friendly to me on this occasion.
What do I need to do to resolve these errors?
postunpack is an error log generated by lib/libdevuansdk/zlibs/bootstrap.
I don't know if anyone has tried live-sdk on anything other than devuan. There are references to devaun in /usr/share/debootstrap/scripts/jessie in the devuan version of debootstrap, but I doubt you'll find them in debian or ubuntu. Maybe it's possible to install devuan debootstrap in ubuntu, and if so, maybe it will work. I don't know.
I have a problem building heads: build_kernel_amd64 gets the kernel successful, but then breaks when trying to compile it. The logfile says quite surprisingly that "make" is missing in chrooted build system. So, how can I add make to the build system?
Samhain, you need to install build-essential. Add it to one of the package lists so that it's installed before the kernel compile happens.
I just started all over again, cloned the heads build-system. "build-essential" is in the list "extra_packages=(" in "build-system/config", so I assume it should be present. Anyway, the build process breaks when trying to compile the kernel.
Ok, kind of success: As you said, "build-essential" is missing in the chroot-environment. I had to install "build-essentiall" and "bc" into [...]/heads/build-system/live-sdk/tmp/devuan-amd64-build/bootstrap, now the kernel is beeing compiled. But where do I need to place these 2 packages, so that the buidscripts will actually add them to the build system?
It needs to be in the base_packages or core_packages list to be included in the bootstrap tarball. You can add it to your blend config. Make sure you use "+=" and not just "=". You want to add to the main list, not replace it.
Thanks, that helped for the kernel. But I still cannot build a valid heads iso, so I question myself when was the last time somebody actually tried to build that beast from git?
I don't know. Last time I built a heads iso was a year ago. Last time I built a plain devuan iso with live-sdk was a couple weeks ago.