<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-build.git/scripts/image-build/build-vyos-image, branch sever-sever-patch-1</title>
<subtitle>VyOS image build scripts (mirror of https://github.com/vyos/vyos-build.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-build.git/atom?h=sever-sever-patch-1</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-build.git/atom?h=sever-sever-patch-1'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/'/>
<updated>2026-07-28T21:56:32+00:00</updated>
<entry>
<title>build: T9140: include version and flavor information in the boot menu</title>
<updated>2026-07-28T21:56:32+00:00</updated>
<author>
<name>Daniil Baturin</name>
<email>daniil@baturin.org</email>
</author>
<published>2026-07-28T21:56:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=a3b7ace20597fd74475b25b9d41af01fceaac22c'/>
<id>urn:sha1:a3b7ace20597fd74475b25b9d41af01fceaac22c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>sbom: T9098: syft should run un squashfs instead of unpacked chroot</title>
<updated>2026-07-16T20:52:17+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-07-16T19:01:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=3db21e81c99ae1e8bf8f24450046c18f53d78d74'/>
<id>urn:sha1:3db21e81c99ae1e8bf8f24450046c18f53d78d74</id>
<content type='text'>
lb (live-build) binary runs binary_rootfs first, then binary_grub-efi.
binary_grub-efi temporarily installs EFI tooling and then runs:
  "apt remove --auto-remove --purge --allow-remove-essential"

That cleanup is safe for the already-generated squashfs, but it mutates
build/chroot and can remove vyos-1x, breaking subsequent work that expects
chroot to remain intact for SBOM generation.

But why unpacking the squashfs?

In an ideal world we could call syft on the compressed squashfs file which is
supported. In our world, we do use a BCJ pre-filter chained with LZMA2 for
compressing the squashfs, which will increase the compression ratio without a
decompression penalty.

  Difference: ~14.3 MB, ~2.7% smaller

This is unsupported by fyft which means we do need to unpack the squashfs first
before checking the files and generating the SBOM file.
</content>
</entry>
<entry>
<title>sbom: T8542: bugfix shadowing cmd() function with cmd variable name</title>
<updated>2026-06-04T20:10:56+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-06-04T20:08:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=3c26a4805c35fac97adfc45b85eff051ca7d3312'/>
<id>urn:sha1:3c26a4805c35fac97adfc45b85eff051ca7d3312</id>
<content type='text'>
Commit 75a495b237 ("sbom: T8542: create during ISO assembly") will shadow any
subsequent calls to vyos.utils.process.cmd() as cmd has be redefined as
variable to hold the CLI command strings for SBOM generation using the syft
binary.

This has been fixed by replacing the cmd variable with another name syft_cmd.
</content>
</entry>
<entry>
<title>sbom: T8542: change result filenames to match ISO image filename</title>
<updated>2026-06-02T19:12:02+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-06-02T19:08:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=30ca4c7bc0abe95d77d67eb091a5659db6535a4a'/>
<id>urn:sha1:30ca4c7bc0abe95d77d67eb091a5659db6535a4a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>sbom: T8542: create during ISO assembly</title>
<updated>2026-06-01T19:10:52+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-05-24T12:19:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=75a495b23738b17c40d93a26253d95e5be9628ad'/>
<id>urn:sha1:75a495b23738b17c40d93a26253d95e5be9628ad</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge pull request #1156 from jestabro/extend-activation-system</title>
<updated>2026-05-01T21:00:19+00:00</updated>
<author>
<name>Daniil Baturin</name>
<email>daniil@vyos.io</email>
</author>
<published>2026-05-01T21:00:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=f8a364a85b57e25bab12715980e541b9064acdd0'/>
<id>urn:sha1:f8a364a85b57e25bab12715980e541b9064acdd0</id>
<content type='text'>
T8445: add support for extension of activation system</content>
</entry>
<entry>
<title>T8445: allow overriding activation init list in flavor files</title>
<updated>2026-04-20T20:24:33+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2026-04-06T15:17:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=033929ee38b284cb2dd8a5c98dc4cc2329744741'/>
<id>urn:sha1:033929ee38b284cb2dd8a5c98dc4cc2329744741</id>
<content type='text'>
</content>
</entry>
<entry>
<title>T8445: add activation init hint during raw image build</title>
<updated>2026-04-20T20:24:33+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2026-04-06T14:52:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=0361cf4cb8b9f261dae0b608d03995b7de0fcf77'/>
<id>urn:sha1:0361cf4cb8b9f261dae0b608d03995b7de0fcf77</id>
<content type='text'>
When building raw images, leave hint to indicate activiation init on
boot.
</content>
</entry>
<entry>
<title>image: T8375: honor already existing boot_settings</title>
<updated>2026-04-20T19:03:25+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-04-20T19:03:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=8b27d2239b0a19ff3301fbb725ebf892f6ca2c82'/>
<id>urn:sha1:8b27d2239b0a19ff3301fbb725ebf892f6ca2c82</id>
<content type='text'>
VyOS flavors might come with boot_settings which already provided additional
serial interface settings if required. Instead of using our own definitions,
re-use what's already existing.

scripts/image-build/build-vyos-image comes with an implicit default for
boot_settings like console number and speed, thus we do not need to redefine
the existing default - again.
</content>
</entry>
<entry>
<title>flavor: T8375: add flavor.json during build into resulting image</title>
<updated>2026-03-31T13:08:56+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-03-30T20:05:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=52c3ea6742aed4058464c8c9cc690b2acadd7cb0'/>
<id>urn:sha1:52c3ea6742aed4058464c8c9cc690b2acadd7cb0</id>
<content type='text'>
In order for amd64 or arm64 images to know their serial console settings, we
embed a new file named "flavor.json" under "/usr/share/vyos" into the resulting
image. The file holds configuration parameters unique to the build flavor.

Corresponding library functions are available via a Python vyos.flavor module.
</content>
</entry>
</feed>
