Re: Building VM-IMAGE(s) from Source

Thank You.

The 'release/15' was my early error - I later switched to 'releng/15.0' ... the fetching of source was not a problem ... but I also needed to set these two in the /usr/src/release/config.conf to 'see' what is fetched because by default they are silenced with '-q' option and the only way to see 'something' is happening is either checking with ps(1) on other terminal or ^T for status w/o them.

  GITCMD="/usr/local/bin/git clone"
  VCSCMD="/usr/local/bin/git clone"

... and if fetching failed ... the 'release.sh' thrown very 'strange' errors - like these:

root@release:/usr/src/release # ./release.sh -c proxy.conf 
load: 0.10  cmd: git 37073 [piperd] 9.59r 0.04u 0.06s 0% 11192k
load: 0.05  cmd: git 37076 [piperd] 432.96r 17.20u 3.23s 4% 334472k
load: 0.26  cmd: git 37076 [piperd] 808.76r 29.21u 5.59s 3% 360796k
error: RPC failed; curl 56 Recv failure: Connection reset by peer
error: 1054 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
umount: /usr/obj/chroot/dev: statfs: No such file or directory
umount: /usr/obj/chroot/dev: unknown file system

So fetching was 'covered' - the building was problematic part ... but I do not want to 'spam' these MLs with long error messages as I already found peace with verimg(8) tool.

Regards,
vermaden




Temat: Re: Building VM-IMAGE(s) from Source
Data: 2026-04-16 3:44
Nadawca: "Maku Bex" <[email protected]>
Adresat: "vermaden" <[email protected]>; 
DW: "[email protected]" <[email protected]>;
"[email protected]" <[email protected]>;
"FreeBSD Current" <[email protected]>; 

> Vermaden,
> 
> Very useful script! Thx.
> 
> Also, I noticed that your custom.conf contains "release/15"
> instead of "releng/15" as a source branch. I'm confident
> you're aware there is no "release/15" branch on the git repo
> so you probably just added it subconsciously. It happens
> when working with FreeBSD (it always tends to push you
> beyond the limits).
> 
> Happy hacking /#\
> 
> On Wed, Apr 15, 2026, 05:26 vermaden <[email protected]> wrote:
> 
>> I was not able to get 'release.sh' to success even a single time
>> - it always failed with different errors - the 'help' I received here
>> also did not pushed things forward ... so I wrote my own
>> verimg(8) tool for similar things as 'release.sh' does.
>> 
>> Here are the details:
>> - https://vermaden.wordpress.com/2026/04/15/freebsd-image-builder-installer-verimg-tool/
>> 
>> Here is the verimg(8) repo:
>> - https://github.com/vermaden/verimg
>> 
>> Maybe someone will find that useful.
>> 
>> Regards,
>> vermaden