vyos-build.git/scripts, branch T7032VyOS image build scripts (mirror of https://github.com/vyos/vyos-build.git)
https://git.amelek.net/vyos/vyos-build.git/atom?h=T70322025-01-09T09:05:31+00:00T7032: Add missing libpam-radius-auth build2025-01-09T09:05:31+00:00Viacheslav Hletenkov.gletenko@vyos.io2025-01-09T09:05:31+00:00urn:sha1:528416d4912c513d12443305778f8b56471ef024T7026: Add script build vpp package2025-01-07T20:05:35+00:00Viacheslav Hletenkov.gletenko@vyos.io2025-01-07T20:02:14+00:00urn:sha1:b04538b9b205509e0d3adb016913e8e5d8f8d6c4T7019: use VyOS release train in /etc/os-release codename over Debian release2025-01-05T19:00:49+00:00Christian Breunigchristian@breunig.cc2025-01-05T19:00:49+00:00urn:sha1:f8b88e54bc5a0b9f3466699c94b63decd2502d57
VyOS is based on Debian
* VyOS 1.3 -> Debian Buster (VyOS equuleus)
* VyOS 1.4 -> Debian Bookworm (VyOS sagitta)
* VyOS 1.5 -> Debian Bookworm (and then trixie) (VyOS circinus)
* VyOS rolling -> Debian Bookworm (and then trixie) (VyOS t.b.d.)
When running
vyos@vyos:~$ lsb_release -a
Distributor ID: VyOS
Description: VyOS 1.5-rolling-202501031241 (current)
Release: 1.5-rolling-202501031241
Codename: bookworm
The codename in use is the Debian base distribution. This should be changed to
the VyOS release name.
Merge pull request #876 from c-po/T6999-os-release2025-01-03T19:57:44+00:00Viacheslav Hletenkov.gletenko@vyos.io2025-01-03T19:57:44+00:00urn:sha1:aa4ba3d95e162f1570330ca1787002d4239d583f
Testsuite: T6999: validate content of /etc/os-release in target systemTestsuite: T6999: validate content of /etc/os-release in target system2025-01-03T16:00:52+00:00Christian Breunigchristian@breunig.cc2025-01-03T14:00:49+00:00urn:sha1:dabd5b2a6a6b9550439f9258a0a01dac2d0c0e60
The file /etc/os-release is written during image build, but it's content is not
validated that it can be used by e.g. "lsb_release -a" command.
Kernel: T861: enable lockdown subsystem as UEFI secure boot dependency2025-01-02T10:44:27+00:00Christian Breunigchristian@breunig.cc2025-01-02T10:44:27+00:00urn:sha1:1a593421ecc3ce860a2bc5849aec917febe33fccKernel: T5887: update Linux Kernel to v6.6.692025-01-02T10:43:19+00:00Christian Breunigchristian@breunig.cc2025-01-02T10:41:06+00:00urn:sha1:8013ff21ae5ce6bd09f19f33fb2bb5ce7efddb1eTestsuite: T861: use proper base MAC address from RFC70422025-01-01T19:10:52+00:00Christian Breunigchristian@breunig.cc2025-01-01T19:06:42+00:00urn:sha1:bf01c00d0446564ce8433ad1e916c366d7f8f32d
Commit 085df7615a ("Testsuite: T861: always use 2 VCPUs") also altered the base
MAC address used by QEMU to a locally administered one. Something that looked
"right" in the beginning turned out to break the smoketest platform.
The reason is the locally administered bit is evaluated in [1] and if set and
not on the exclusion list (as it was a Realtek base MAC address before), the
interface in question is not considered persistent and thus not added to the
configuration file upon system startup.
1: https://github.com/vyos/vyos-1x/blob/825743b6bcdf8fa2c263dabaa3fee40ba7a98525/src/helpers/vyos-interface-rescan.py#L73-L74
Merge pull request #872 from c-po/testsuite-update2024-12-31T17:06:25+00:00Christian Breunigchristian@breunig.cc2024-12-31T17:06:25+00:00urn:sha1:72c2a011d7cd53a082a8f5a31c187d12925a6be8
Testsuite: T861: inform smoketest about this environmentTestsuite: T6991: inform smoketest about this environment2024-12-31T13:20:49+00:00Christian Breunigchristian@breunig.cc2024-12-31T13:13:58+00:00urn:sha1:81ae7efbac6cce251092ae91719611007a07a5f7